Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > muc.lists.freebsd.emulation > #12703 > unrolled thread
| Started by | bugzilla-noreply@freebsd.org |
|---|---|
| First post | 2025-11-22 13:28 +0000 |
| Last post | 2026-02-04 00:28 +0000 |
| Articles | 11 — 1 participant |
Back to article view | Back to muc.lists.freebsd.emulation
[Bug 291151] www/linux-chrome: Fails to start on 14.3-RELEASE since latest freebsd-update bugzilla-noreply@freebsd.org - 2025-11-22 13:28 +0000
[Bug 291151] www/linux-chrome: Fails to start on 14.3-RELEASE since latest freebsd-update bugzilla-noreply@freebsd.org - 2025-12-05 23:41 +0000
[Bug 291151] www/linux-chrome: Fails to start on 14.3-RELEASE since latest freebsd-update bugzilla-noreply@freebsd.org - 2026-01-29 14:46 +0000
[Bug 291151] www/linux-chrome: Fails to start on 14.3-RELEASE since latest freebsd-update bugzilla-noreply@freebsd.org - 2026-02-01 01:53 +0000
[Bug 291151] www/linux-chrome: Fails to start on 14.3-RELEASE following freebsd-update bugzilla-noreply@freebsd.org - 2026-02-03 13:22 +0000
[Bug 291151] www/linux-chrome: Fails to start on 14.3-RELEASE following freebsd-update bugzilla-noreply@freebsd.org - 2026-02-03 13:27 +0000
[Bug 291151] www/linux-chrome: Fails to start on 14.3-RELEASE following freebsd-update bugzilla-noreply@freebsd.org - 2026-02-03 15:46 +0000
[Bug 291151] www/linux-chrome: Fails to start on 14.3-RELEASE following freebsd-update bugzilla-noreply@freebsd.org - 2026-02-03 21:35 +0000
[Bug 291151] www/linux-chrome: Fails to start on 14.3-RELEASE following freebsd-update bugzilla-noreply@freebsd.org - 2026-02-03 22:24 +0000
[Bug 291151] www/linux-chrome: Fails to start on 14.3-RELEASE following freebsd-update bugzilla-noreply@freebsd.org - 2026-02-03 23:51 +0000
[Bug 291151] www/linux-chrome: Fails to start on 14.3-RELEASE following freebsd-update bugzilla-noreply@freebsd.org - 2026-02-04 00:28 +0000
| From | bugzilla-noreply@freebsd.org |
|---|---|
| Date | 2025-11-22 13:28 +0000 |
| Subject | [Bug 291151] www/linux-chrome: Fails to start on 14.3-RELEASE since latest freebsd-update |
| Message-ID | <bug-291151-4077@https.bugs.freebsd.org/bugzilla/> |
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=291151
Bug ID: 291151
Summary: www/linux-chrome: Fails to start on 14.3-RELEASE since
latest freebsd-update
Product: Ports & Packages
Version: Latest
Hardware: amd64
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: Individual Port(s)
Assignee: emulation@FreeBSD.org
Reporter: jwb@freebsd.org
Flags: maintainer-feedback?(emulation@FreeBSD.org)
Assignee: emulation@FreeBSD.org
I set up a dedicated media machine with a fresh 14.3-RELEASE install and latest
ports, tested linux-chrome on Netflix. It was working fine until I ran
freebsd-update, and it now crashes on startup:
FreeBSD media.acadix bacon ~ 55: google-chrome
[1122/071816.134720:WARNING:chrome/app/chrome_main_linux.cc:82] Read channel
stable from /usr/local/share/chrome/CHROME_VERSION_EXTRA
[78793:106757:1122/071820.187396:ERROR:base/files/file_path_watcher_inotify.cc:339]
inotify_init() failed: Function not implemented (38)
[78793:78793:1122/071820.488760:ERROR:base/memory/platform_shared_memory_region_posix.cc:226]
Creating shared memory in /dev/shm/.com.google.Chrome.skaCXV failed: Operation
not supported (95)
[78793:78793:1122/071820.488818:ERROR:base/memory/platform_shared_memory_region_posix.cc:229]
Unable to access(W_OK|X_OK) /dev/shm: Permission denied (13)
[78793:78793:1122/071820.535666:FATAL:base/memory/platform_shared_memory_region_posix.cc:231]
This is frequently caused by incorrect permissions on /dev/shm. Try 'sudo
chmod 1777 /dev/shm' to fix.
[1122/071820.624981:ERROR:third_party/crashpad/crashpad/util/linux/ptracer.cc:44]
ptrace: Invalid argument (22)
[1122/071820.653730:WARNING:third_party/crashpad/crashpad/snapshot/linux/process_reader_linux.cc:400]
Couldn't initialize main thread.
[1122/071820.653787:ERROR:third_party/crashpad/crashpad/util/linux/proc_task_reader.cc:47]
format error
[1122/071820.653811:WARNING:third_party/crashpad/crashpad/snapshot/linux/exception_snapshot_linux.cc:391]
thread ID 78793 not found in process
[1122/071820.653876:ERROR:third_party/crashpad/crashpad/snapshot/linux/process_snapshot_linux.cc:129]
thread not found 78793
[1122/071820.654354:ERROR:third_party/crashpad/crashpad/util/linux/proc_task_reader.cc:47]
format error
Trace/BPT trap (core dumped)
After following the suggestion in the error messages:
FreeBSD media.acadix bacon ~ 62: asroot chmod 1777 /compat/linux/dev/shm/
root Password:
FreeBSD media.acadix bacon ~ 63:
google-chrome[1122/072433.741480:WARNING:chrome/app/chrome_main_linux.cc:82]
Read channel stable from /usr/local/share/chrome/CHROME_VERSION_EXTRA
[81522:106783:1122/072433.804682:ERROR:base/files/file_path_watcher_inotify.cc:339]
inotify_init() failed: Function not implemented (38)
[81522:81522:1122/072433.817594:ERROR:base/memory/platform_shared_memory_region_posix.cc:226]
Creating shared memory in /dev/shm/.com.google.Chrome.5gtHTk failed: Operation
not supported (95)
[81522:81522:1122/072433.999941:ERROR:ui/ozone/platform/x11/ozone_platform_x11.cc:249]
Missing X server or $DISPLAY
[81522:81522:1122/072434.005775:ERROR:ui/aura/env.cc:257] The platform failed
to initialize. Exiting.
chmod 1777 /dev/shm made no difference.
--
You are receiving this mail because:
You are the assignee for the bug.
--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
[toc] | [next] | [standalone]
| From | bugzilla-noreply@freebsd.org |
|---|---|
| Date | 2025-12-05 23:41 +0000 |
| Message-ID | <bug-291151-4077-ZWDKUENYGF@https.bugs.freebsd.org/bugzilla/> |
| In reply to | #12703 |
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=291151 --- Comment #1 from Jason W. Bacon <jwb@freebsd.org> --- This appears to be limited to certain (possibly older) hardware. Was there anything in the FreeBSD 14.3 base updates that would thwart an Intel i3? I'm using an old ThinkCentre tiny as a dedicated media machine, because I don't really want Google chrome on machines I use regularly. linux-chrome works on my i5 laptop. However, as I stated earlier, the failure happens after a FreeBSD base update. The latest packages work fine on a fresh 14.3 install before base updates. -- You are receiving this mail because: You are the assignee for the bug. -- Posted automagically by a mail2news gateway at muc.de e.V. Please direct questions, flames, donations, etc. to news-admin@muc.de
[toc] | [prev] | [next] | [standalone]
| From | bugzilla-noreply@freebsd.org |
|---|---|
| Date | 2026-01-29 14:46 +0000 |
| Message-ID | <bug-291151-4077-XXLfQcBXEO@https.bugs.freebsd.org/bugzilla/> |
| In reply to | #12703 |
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=291151
Jason W. Bacon <jwb@freebsd.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |Unable to Reproduce
Status|New |Closed
--- Comment #2 from Jason W. Bacon <jwb@freebsd.org> ---
Closing, as I no longer have this hardware.
--
You are receiving this mail because:
You are the assignee for the bug.
--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
[toc] | [prev] | [next] | [standalone]
| From | bugzilla-noreply@freebsd.org |
|---|---|
| Date | 2026-02-01 01:53 +0000 |
| Message-ID | <bug-291151-4077-uPOW2elguZ@https.bugs.freebsd.org/bugzilla/> |
| In reply to | #12703 |
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=291151
Jason W. Bacon <jwb@freebsd.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|Unable to Reproduce |---
Status|Closed |New
--- Comment #3 from Jason W. Bacon <jwb@freebsd.org> ---
The problem has returned on a newer ThinkCentre Ryzen.
Same symptom: Worked fine until I ran freebsd-update.
Problem persisted after upgrading to 15.0-RELEASE.
It seems freebsd-update is doing something that interferes with linux-chrome
execution.
--
You are receiving this mail because:
You are the assignee for the bug.
--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
[toc] | [prev] | [next] | [standalone]
| From | bugzilla-noreply@freebsd.org |
|---|---|
| Date | 2026-02-03 13:22 +0000 |
| Subject | [Bug 291151] www/linux-chrome: Fails to start on 14.3-RELEASE following freebsd-update |
| Message-ID | <bug-291151-4077-e3LYTtIMdK@https.bugs.freebsd.org/bugzilla/> |
| In reply to | #12703 |
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=291151
Jason W. Bacon <jwb@freebsd.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|www/linux-chrome: Fails to |www/linux-chrome: Fails to
|start on 14.3-RELEASE since |start on 14.3-RELEASE
|latest freebsd-update |following freebsd-update
--
You are receiving this mail because:
You are the assignee for the bug.
--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
[toc] | [prev] | [next] | [standalone]
| From | bugzilla-noreply@freebsd.org |
|---|---|
| Date | 2026-02-03 13:27 +0000 |
| Subject | [Bug 291151] www/linux-chrome: Fails to start on 14.3-RELEASE following freebsd-update |
| Message-ID | <bug-291151-4077-16rBpjSk4q@https.bugs.freebsd.org/bugzilla/> |
| In reply to | #12703 |
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=291151
--- Comment #4 from Jason W. Bacon <jwb@freebsd.org> ---
I found a workaround and narrowed down the cause:
As suggested by the error message, permissions are wrong on
/compat/linux/dev/shm after running freebsd-update, but that's not the whole
story. Permissions on this directory after a fresh linux_base install are
1777, but after the problem arose they are 555.
Running
chmod 1777 /compat/linux/dev/shm
did not help. However, completely removing linux_base and /compat/linux, and
reinstalling linux_base, eliminates the problem.
So it appears that something in freebsd-update is corrupting permissions on
/compat/linux/dev/shm along with something else I haven't identified yet.
--
You are receiving this mail because:
You are the assignee for the bug.
--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
[toc] | [prev] | [next] | [standalone]
| From | bugzilla-noreply@freebsd.org |
|---|---|
| Date | 2026-02-03 15:46 +0000 |
| Subject | [Bug 291151] www/linux-chrome: Fails to start on 14.3-RELEASE following freebsd-update |
| Message-ID | <bug-291151-4077-sOIETbTXNz@https.bugs.freebsd.org/bugzilla/> |
| In reply to | #12703 |
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=291151
Alex S <iwtcex@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |iwtcex@gmail.com
--- Comment #5 from Alex S <iwtcex@gmail.com> ---
(In reply to Jason W. Bacon from comment #4)
> Permissions on this directory after a fresh linux_base install are 1777
That means tmpfs is mounted (see /etc/rc.d/linux).
> but after the problem arose they are 555.
tmpfs is not mounted (you see a dir on devfs).
--
You are receiving this mail because:
You are the assignee for the bug.
--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
[toc] | [prev] | [next] | [standalone]
| From | bugzilla-noreply@freebsd.org |
|---|---|
| Date | 2026-02-03 21:35 +0000 |
| Subject | [Bug 291151] www/linux-chrome: Fails to start on 14.3-RELEASE following freebsd-update |
| Message-ID | <bug-291151-4077-30iKNqtBiP@https.bugs.freebsd.org/bugzilla/> |
| In reply to | #12703 |
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=291151 --- Comment #6 from Jason W. Bacon <jwb@freebsd.org> --- (In reply to Alex S from comment #5) That's possible. Generally I would notice if one of the normal three linux mounts was missing, especially over such a long period and multiple reboots, but there's a chance I overlooked it. /dev/nda0p2 226G 46G 162G 22% / devfs 1.0K 0B 1.0K 0% /dev /dev/nda0p1 260M 1.3M 259M 1% /boot/efi fdescfs 1.0K 0B 1.0K 0% /dev/fd procfs 8.0K 0B 8.0K 0% /proc map -hosts 0B 0B 0B 100% /net linprocfs 8.0K 0B 8.0K 0% /compat/linux/proc tmpfs 7.1G 4.0K 7.1G 0% /compat/linux/dev/shm linsysfs 8.0K 0B 8.0K 0% /compat/linux/sys I'll see if I can reproduce the issue and keep an eye on the mounts. In any case, we'll need to figure out how freebsd-update broke it. -- You are receiving this mail because: You are the assignee for the bug. -- Posted automagically by a mail2news gateway at muc.de e.V. Please direct questions, flames, donations, etc. to news-admin@muc.de
[toc] | [prev] | [next] | [standalone]
| From | bugzilla-noreply@freebsd.org |
|---|---|
| Date | 2026-02-03 22:24 +0000 |
| Subject | [Bug 291151] www/linux-chrome: Fails to start on 14.3-RELEASE following freebsd-update |
| Message-ID | <bug-291151-4077-ms3cHy50xG@https.bugs.freebsd.org/bugzilla/> |
| In reply to | #12703 |
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=291151 --- Comment #7 from Jason W. Bacon <jwb@freebsd.org> --- This was easy to reproduce... 1. Create new 14.3 VM under VirtualBox 2. Run desktop-installer, select a lightweight WM 3. auto-install-linux_base rl9 4. pkg install linux-chrome 5. Test: Success 6. freebsd-update fetch install 7. reboot 8. Test: Failed The problem was not that tmpfs wasn't mounted, but that something else was interfering with it: Before freebsd-update: /dev/ada0p2 15225628 12831208 1176372 92% / devfs 1 0 1 0% /dev fdescfs 1 0 1 0% /dev/fd procfs 8 0 8 0% /proc map -hosts 0 0 0 100% /net linprocfs 8 0 8 0% /compat/linux/proc tmpfs 927344 4 927340 0% /compat/linux/dev/shm linsysfs 8 0 8 0% /compat/linux/sys After freebsd-update: /dev/ada0p2 15225628 13431032 576548 96% / devfs 1 0 1 0% /dev fdescfs 1 0 1 0% /dev/fd procfs 8 0 8 0% /proc linprocfs 8 0 8 0% /compat/linux/proc tmpfs 1215284 4 1215280 0% /compat/linux/dev/shm linsysfs 8 0 8 0% /compat/linux/sys devfs 1 0 1 0% /compat/linux/dev fdescfs 1 0 1 0% /compat/linux/dev/fd map -hosts 0 0 0 100% /net Why devfs is getting mounted on /compat/linux/dev is a mystery at the moment. It's not in fstab: # Device Mountpoint FStype Options Dump Pass# /dev/ada0p2 / ufs rw 1 1 /dev/ada0p3 none swap sw 0 0 # Added by auto-admin from /usr/local/sbin/auto-add-fdesc-mount fdesc /dev/fd fdescfs rw 0 0 # End auto-admin addition # Added by auto-admin from desktop-installer proc /proc procfs rw 0 0 # End auto-admin addition # Added by auto-admin from /usr/local/sbin/auto-install-linux_base linprocfs /compat/linux/proc linprocfs rw 0 0 # End auto-admin addition # Added by auto-admin from /usr/local/sbin/auto-install-linux_base tmpfs /compat/linux/dev/shm tmpfs rw,mode=1777 0 0 # End auto-admin addition # Added by auto-admin from /usr/local/sbin/auto-install-linux_base linsysfs /compat/linux/sys linsysfs rw 0 0 # End auto-admin addition Unmounting /compat/linux/dev/fd and /compat/linux/dev enables google-chrome to function again. -- You are receiving this mail because: You are the assignee for the bug. -- Posted automagically by a mail2news gateway at muc.de e.V. Please direct questions, flames, donations, etc. to news-admin@muc.de
[toc] | [prev] | [next] | [standalone]
| From | bugzilla-noreply@freebsd.org |
|---|---|
| Date | 2026-02-03 23:51 +0000 |
| Subject | [Bug 291151] www/linux-chrome: Fails to start on 14.3-RELEASE following freebsd-update |
| Message-ID | <bug-291151-4077-BNIUQQhfJ0@https.bugs.freebsd.org/bugzilla/> |
| In reply to | #12703 |
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=291151 --- Comment #8 from Alex S <iwtcex@gmail.com> --- You need to get rid of your /compat/linux fstab entries since https://github.com/freebsd/freebsd-src/commit/c13f19c0cfa8fe101cf1e7946474a7793c961d9a. -- You are receiving this mail because: You are the assignee for the bug. -- Posted automagically by a mail2news gateway at muc.de e.V. Please direct questions, flames, donations, etc. to news-admin@muc.de
[toc] | [prev] | [next] | [standalone]
| From | bugzilla-noreply@freebsd.org |
|---|---|
| Date | 2026-02-04 00:28 +0000 |
| Subject | [Bug 291151] www/linux-chrome: Fails to start on 14.3-RELEASE following freebsd-update |
| Message-ID | <bug-291151-4077-qgvVql8Sxf@https.bugs.freebsd.org/bugzilla/> |
| In reply to | #12703 |
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=291151
Jason W. Bacon <jwb@freebsd.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |Not A Bug
Status|New |Closed
--- Comment #9 from Jason W. Bacon <jwb@freebsd.org> ---
Ah, thanks for pointer. This is a good change, even though it bit me in the
***.
Seems to be working as expected now.
--
You are receiving this mail because:
You are the assignee for the bug.
--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
[toc] | [prev] | [standalone]
Back to top | Article view | muc.lists.freebsd.emulation
csiph-web