cups-proxyd[2318]: segfault at 18 ip 00005975fb88bd75

Bug #2065405 reported by Etienne Lorrain
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
cups (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

dmesg shows, ubuntu-24.04 just updated and no more booting to graphic, more details in the attached tgz:
It might be apparmor fault, or the other problems before in dmesg attached...

[ 5.391769] show_signal: 175 callbacks suppressed
[ 5.391770] traps: gdm3[2173] trap int3 ip:7285a1f066a1 sp:7ffdddd5cf10 error:0 in libglib-2.0.so.0.8000.0[7285a1ec2000+a0000]
[ 5.412320] audit: type=1400 audit(1715335404.407:186): apparmor="DENIED" operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=2251 comm="snap-confine" capability=12 capname="net_admin"
[ 5.412324] audit: type=1400 audit(1715335404.407:187): apparmor="DENIED" operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=2251 comm="snap-confine" capability=38 capname="perfmon"
[ 5.667941] audit: type=1326 audit(1715335404.663:188): auid=4294967295 uid=0 gid=0 ses=4294967295 subj=snap.cups.cupsd pid=2317 comm="cupsd" exe="/snap/cups/1047/sbin/cupsd" sig=0 arch=c000003e syscall=93 compat=0 ip=0x70f5f208da9b code=0x50000
[ 5.902432] Bluetooth: RFCOMM TTY layer initialized
[ 5.902436] Bluetooth: RFCOMM socket layer initialized
[ 5.902440] Bluetooth: RFCOMM ver 1.11
[ 6.666335] audit: type=1326 audit(1715335405.661:189): auid=4294967295 uid=0 gid=0 ses=4294967295 subj=snap.cups.cupsd pid=2318 comm="cups-proxyd" exe="/snap/cups/1047/sbin/cups-proxyd" sig=0 arch=c000003e syscall=314 compat=0 ip=0x7b88291e988d code=0x50000
[ 6.935390] fbcon: Taking over console
[ 6.936953] Console: switching to colour frame buffer device 240x67
[ 7.485887] r8169 0000:0b:00.0 enp11s0: Link is Up - 1Gbps/Full - flow control off
[ 7.711372] cups-proxyd[2318]: segfault at 18 ip 00005975fb88bd75 sp 00007ffeb2abfb70 error 4 in cups-proxyd[5975fb888000+7000] likely on CPU 28 (core 12, socket 0)
[ 7.711384] Code: 83 3d ee b2 00 00 00 41 54 55 48 89 fd 53 0f 85 f4 00 00 00 48 8d 1d 69 3d 00 00 48 63 45 1c 48 89 df 48 c1 e0 05 48 03 45 08 <48> 8b 50 18 8b 70 14 e8 0f d0 ff ff 44 8b 65 18 48 89 c7 45 85 e4
[ 8.278587] traps: gdm3[2576] trap int3 ip:71bcaf7b16a1 sp:7ffd0797dc40 error:0 in libglib-2.0.so.0.8000.0[71bcaf76d000+a0000]
[ 9.711404] traps: gdm3[2636] trap int3 ip:7b4bc456d6a1 sp:7fff0fc29d20 error:0 in libglib-2.0.so.0.8000.0[7b4bc4529000+a0000]
[ 11.146862] traps: gdm3[2675] trap int3 ip:743a31d656a1 sp:7ffe515ac6a0 error:0 in libglib-2.0.so.0.8000.0[743a31d21000+a0000]
[ 12.574764] traps: gdm3[2712] trap int3 ip:74eb70fec6a1 sp:7ffe64dae640 error:0 in libglib-2.0.so.0.8000.0[74eb70fa8000+a0000]
[ 71.176574] audit: type=1400 audit(1715335470.457:190): apparmor="DENIED" operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=2892 comm="snap-confine" capability=12 capname="net_admin"
[ 71.176585] audit: type=1400 audit(1715335470.457:191): apparmor="DENIED" operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=2892 comm="snap-confine" capability=38 capname="perfmon"
[ 981.636089] sd 6:0:0:0: [sda] 7759872 512-byte logical blocks: (3.97 GB/3.70 GiB)
[ 981.637873] sda: detected capacity change from 0 to 7759872
[ 981.640768] sda: sda1

Revision history for this message
Etienne Lorrain (etienne-lorrain) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in cups (Ubuntu):
status: New → Confirmed
Revision history for this message
lioncub (lioncub) wrote :
Download full text (15.2 KiB)

/etc/cups/cupsd.conf with LogLevel debug
debug log:
```
2024-05-10T21:37:29.451316+05:00 home systemd[1]: Started cups.path - CUPS Scheduler.
2024-05-10T21:37:29.451414+05:00 home systemd[1]: Listening on cups.socket - CUPS Scheduler.
2024-05-10T21:37:30.510367+05:00 home systemd[1]: Starting cups.service - CUPS Scheduler...
2024-05-10T21:37:30.514362+05:00 home systemd[1]: Started snap.cups.cups-browsed.service - Service for snap application cups.cups-browsed.
2024-05-10T21:37:30.515438+05:00 home systemd[1]: Started snap.cups.cupsd.service - Service for snap application cups.cupsd.
2024-05-10T21:37:30.569987+05:00 home systemd[1]: Started cups.service - CUPS Scheduler.
2024-05-10T21:37:30.804911+05:00 home cups.cups-browsed[1450]: + mkdir -p /var/snap/cups/1047/var/log
2024-05-10T21:37:30.805066+05:00 home cups.cupsd[1453]: + mkdir -p /var/snap/cups/1047/var/spool/tmp
2024-05-10T21:37:30.899651+05:00 home cups.cups-browsed[1450]: + mkdir -p /var/snap/cups/1047/var/cache
2024-05-10T21:37:30.899697+05:00 home cups.cupsd[1453]: + mkdir -p /var/snap/cups/1047/var/run/certs
2024-05-10T21:37:30.900751+05:00 home cups.cups-browsed[1450]: + mkdir -p /var/snap/cups/1047/var/run
2024-05-10T21:37:30.900871+05:00 home cups.cupsd[1453]: + mkdir -p /var/snap/cups/1047/var/log
2024-05-10T21:37:30.901845+05:00 home cups.cups-browsed[1450]: + mkdir -p /var/snap/cups/common/etc/cups
2024-05-10T21:37:30.901889+05:00 home cups.cupsd[1453]: + mkdir -p /var/snap/cups/1047/var/cache/fontconfig
2024-05-10T21:37:30.902908+05:00 home cups.cups-browsed[1450]: + CONF=/var/snap/cups/common/etc/cups/cups-browsed.conf
2024-05-10T21:37:30.902930+05:00 home cups.cups-browsed[1450]: + CLIENTCONF=/var/snap/cups/common/etc/cups/client.conf
2024-05-10T21:37:30.902945+05:00 home cups.cups-browsed[1450]: + DAEMON=cups-browsed
2024-05-10T21:37:30.902957+05:00 home cups.cups-browsed[1450]: + export LC_ALL=C.UTF-8
2024-05-10T21:37:30.902969+05:00 home cups.cups-browsed[1450]: + export LANG=C.UTF-8
2024-05-10T21:37:30.902980+05:00 home cups.cups-browsed[1450]: + TMPDIR=/var/snap/cups/1047/tmp
2024-05-10T21:37:30.902992+05:00 home cups.cups-browsed[1450]: + mkdir -p /var/snap/cups/1047/tmp
2024-05-10T21:37:30.903012+05:00 home cups.cupsd[1453]: + mkdir -p /var/snap/cups/common/etc/cups/ppd
2024-05-10T21:37:30.904170+05:00 home cups.cupsd[1453]: + mkdir -p /var/snap/cups/common/etc/cups/ssl
2024-05-10T21:37:30.905185+05:00 home cups.cupsd[1453]: + mkdir -p /var/snap/cups/common/run
2024-05-10T21:37:30.906250+05:00 home cups.cupsd[1453]: + mkdir -m 0755 -p /run/cups
2024-05-10T21:37:30.907276+05:00 home cups.cupsd[1453]: + export LC_ALL=C.UTF-8
2024-05-10T21:37:30.907298+05:00 home cups.cupsd[1453]: + export LANG=C.UTF-8
2024-05-10T21:37:30.907311+05:00 home cups.cupsd[1453]: + export TMPDIR=/var/snap/cups/1047/tmp
2024-05-10T21:37:30.907323+05:00 home cups.cupsd[1453]: + mkdir -p /var/snap/cups/1047/tmp
2024-05-10T21:37:30.911642+05:00 home cups.cups-browsed[1450]: + CUPSSTARTED=0
2024-05-10T21:37:30.911676+05:00 home cups.cupsd[1453]: + CUPSTMPDIR=/var/snap/cups/1047/var/spool/tmp
2024-05-10T21:37:30.911691+05:00 home cups.cupsd[1453]: + [ -d /var/snap/cups/1047/tmp ]
2024-05-10T21:3...

Revision history for this message
Etienne Lorrain (etienne-lorrain) wrote :

For information, ubuntu-24.04 has updated Linux kernel from 6.5.0-28 to 6.8.0-31

The problem reported is only with newer 6.8.0-31, and also failure to reach a working system is only with new kernel.

The previous Linux kernel is still available in the Grub menu, and choosing "6.5.0-28-generic" to boot does bring a working system, with the only line containing "cups" in dmesg being:
[ 5.404257] audit: type=1400 audit(1715587151.264:47): apparmor="DENIED" operation="capable" class="cap" profile="/usr/sbin/cupsd" pid=1039 comm="cupsd" capability=12 capname="net_admin"

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug report. You are focusing the cups issue which is a printing component but from the description the most problematic problem is

[ 8.278587] traps: gdm3[2576] trap int3 ip:71bcaf7b16a1 sp:7ffd0797dc40 error:0 in libglib-2.0.so.0.8000.0[71bcaf76d000+a0000]

which is the login manager not starting

could you Look in /var/crash for crash files and if found run:
    ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

If that step failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us.

Revision history for this message
Etienne Lorrain (etienne-lorrain) wrote :

Unfortunately /var/crash is empty, maybe due to the failure to start.
sudo cat /var/lib/whoopsie/whoopsie-id
ad33826e2f810e105835159dfb99f6a96d895ef0f2572f8db1cf7693a913ff9e35a336244664aaa184f4ed2f0f925f99e481379028b0c7eba2bd9df9363ca035
So there seem to be stuff at:
https://errors.ubuntu.com/user/ad33826e2f810e105835159dfb99f6a96d895ef0f2572f8db1cf7693a913ff9e35a336244664aaa184f4ed2f0f925f99e481379028b0c7eba2bd9df9363ca035

But I can't read that myself, hopefully you are:
Sorry, you are not a member of a group that is allowed to see the data from error reports. Please fill out this form to request access.

Revision history for this message
Kent (revek) wrote :

I have this problem. I have the cups error but think the main problem is the problem with libglib-2.0.so.0.8000.0. Its a fresh install(13 days) on a laptop with a 1st generation I3.

I have two crash files which I ran ubuntu-bug on and sent them. Since I have no GUI it did not launch a web browser to fill out the report. Is there a ID in the report on the two crash files I have?

The filenames are _usr_libexec_gdm-session-worker.0.crash and _usr_sbin_gdm3.0.crash.

Since it may be of help my whoopsie id is
9bf8a2458c673c7d3326545c891233e751b5f207a81c39a8e01cb9a8b23759736495296ec45c53034c53473d6e3cf09635a95ebbc5e6d38f1458ec526f2b6a3e

Revision history for this message
Etienne Lorrain (etienne-lorrain) wrote :

Hi Kent,

you should be able to still run a previous version of the kernel with the boot menu, like what I do, and you can see if your problems are listed at: https://errors.ubuntu.com/user/9bf8a2458c673c7d3326545c891233e751b5f207a81c39a8e01cb9a8b23759736495296ec45c53034c53473d6e3cf09635a95ebbc5e6d38f1458ec526f2b6a3e
I can see "No errors have been reported from this system " for your whoopsie, maybe you did not allow automatic upload, I have some report there because I did...

I did not investigate the login manager not starting with the newer kernel myself, lack of time...
It would probably be good to create a new bug number for that, keeping that bug report for cups-proxyd

Revision history for this message
Kent (revek) wrote :

I didn't have the old kernel since it was a new install. I solved it by switching to pure debian on that laptop.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.