Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > muc.lists.freebsd.emulation > #12834

[Bug 291151] www/linux-chrome: Fails to start on 14.3-RELEASE following freebsd-update

From bugzilla-noreply@freebsd.org
Newsgroups muc.lists.freebsd.emulation
Subject [Bug 291151] www/linux-chrome: Fails to start on 14.3-RELEASE following freebsd-update
Date 2026-02-03 22:24 +0000
Organization Newsgate at muc.de e.V.
Message-ID <bug-291151-4077-ms3cHy50xG@https.bugs.freebsd.org/bugzilla/> (permalink)
References <bug-291151-4077@https.bugs.freebsd.org/bugzilla/>

Show all headers | View raw


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

Back to muc.lists.freebsd.emulation | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

[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

csiph-web