LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Software (https://www.linuxquestions.org/questions/linux-software-2/)
-   -   Dual crash: /sbin/plymouthd and /usr/lib/gnome-settings-daemon/gsd-print-notifications (https://www.linuxquestions.org/questions/linux-software-2/dual-crash-sbin-plymouthd-and-usr-lib-gnome-settings-daemon-gsd-print-notifications-4175652299/)

EigenFunctions 04-17-2019 09:04 AM

Dual crash: /sbin/plymouthd and /usr/lib/gnome-settings-daemon/gsd-print-notifications
 
I have one recurring crash and one new crash:
Code:

ProblemType: Crash
Architecture: amd64
Date: Wed Apr 17 09:04:18 2019
DistroRelease: Ubuntu 18.04
ExecutablePath: /sbin/plymouthd
ExecutableTimestamp: 1536707038
ProcCmdline: @sbin/plymouthd --mode=boot --pid-file=/run/plymouth/pid --attach-to-session
ProcCwd: /

ProblemType: Crash
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 16 21:24:18 2019
DistroRelease: Ubuntu 18.04
ExecutablePath: /usr/lib/gnome-settings-daemon/gsd-print-notifications
ExecutableTimestamp: 1548448261
ProcCmdline: /usr/lib/gnome-settings-daemon/gsd-print-notifications
ProcCwd: /home/ldurfee

The "plymouthd" issue I see often. I don't know what it means or how to fix it.

The second, "gsd-print-notifications", has something to do with printing (the two printers are on my LAN) and I am having problems with printing (for some time now). Printing used to be fast and now it is slow. It waits about 10secs after each page before it prints. I don't know if this crash is related or not.

Can anyone help?

business_kid 04-18-2019 04:28 AM

Not with that little information. We'd need logs. You could be missing a lib, or something could be going belly up which throws you that message in X. In the print one, I suspect cups might be puking, and that's python scripts. So a script will barf, and a long daisy chain of scripts falls over. But your problem was the first one.
Things to do: Check dmesg & logs for information. You're looking for an error (not warnings) and the context
Code:

sudo dmesg |grep -iC10 Error
might check dmesg when a crash occurs. Check /var/log also, and surf to http://locathost:631 to have a look at the printing setup. You can do stuff in there.

EigenFunctions 04-18-2019 05:33 AM

1 Attachment(s)
Thanks very much for the help, it is appreciated.

Here is the result of the first ("error" lines only):
Code:

$ sudo dmesg |grep -iC10 Error
        :
[    0.892499] RAS: Correctable Errors collector initialized.
        :
[  11.602377] EXT4-fs (sda2): re-mounted. Opts: errors=remount-ro
        :
[  23.800530] pcieport 0000:00:1c.5: AER: Multiple Corrected error received: id=00e5
[  23.800557] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
[  23.800577] pcieport 0000:00:1c.5:  device [8086:9d15] error status/mask=00002041/00002000
[  23.800591] pcieport 0000:00:1c.5:    [ 0] Receiver Error        (First)
        :
[  23.963249] ath10k_pci 0000:02:00.0: Direct firmware load for ath10k/pre-cal-pci-0000:02:00.0.bin failed with error -2
[  23.963258] ath10k_pci 0000:02:00.0: Direct firmware load for ath10k/cal-pci-0000:02:00.0.bin failed with error -2
[  23.992044] ath10k_pci 0000:02:00.0: Direct firmware load for ath10k/QCA9377/hw1.0/firmware-6.bin failed with error -2
:

I looked at one log
Code:

$ egrep "^Apr.+18" /var/log/syslog | egrep -i "error" | wc -l
15767

With than many lines for one date (15,767), I don't know how to pare it down.

However, I did find this error:
Code:

Apr 18 05:41:09 tarsus org.gnome.Nautilus[2329]: NameError: global name 'SEPARATOR' is not defined
Apr 18 05:41:09 tarsus nautilus-autostart.desktop[2709]: NameError: global name 'SEPARATOR' is not defined

Which occurred many times:
Code:

$ egrep "^Apr.+18" /var/log/syslog | egrep "NameError.+SEPARATOR" | wc -l
3403

There is an uploaded image of error messages attached and here is the text:
Code:

5:37:18 AM gnome-session-b: GLib-CRITICAL: g_child_watch_add_full: assertion 'pid > 0' failed
 5:37:17 AM bluetoothd: Failed to set mode: Blocked through rfkill (0x12)
 5:37:14 AM kernel: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
 5:37:09 AM pulseaudio: [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files
 4:40:59 AM anacron: Can't find sendmail at /usr/sbin/sendmail, not mailing output
 4:35:47 AM bluetoothd: Failed to set mode: Blocked through rfkill (0x12)
 4:35:46 AM spice-vdagent: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
 4:35:32 AM gnome-session-b: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.ScreenSaver exited with status 1
 4:35:21 AM wpa_supplicant: dbus: Failed to construct signal
 4:35:11 AM bluetoothd: Failed to set mode: Blocked through rfkill (0x12)
 4:34:54 AM systemd-udevd: Error calling EVIOCSKEYCODE on device node '/dev/input/event6' (scan code 0x90008, key code 150): Invalid argument
 4:34:53 AM kernel: dell_smbios: Unable to run on non-Dell system
 4:34:53 AM kernel: pcieport 0000:00:1c.5:    [ 6] Bad TLP             
 4:34:32 AM kernel: Couldn't get size: 0x800000000000000e
 4:34:32 AM kernel: Problem loading UEFI:db X.509 certificate (-65)

I hope that helps.

I'll look at the printer issue in the next posting.

business_kid 04-19-2019 03:58 AM

I don't know what to say to you. Kernel errors can be critical. You have few worth talking about except the pcie issue. I'd check that. I don't have Plymouth's in slackware and everything works. I think it's part of gnome. Printer errors are low priority.
Now that you have error messages, Google them. Also try an update & upgrade with apt-get in case that sorts it.

EigenFunctions 05-03-2019 07:41 PM

business_kid:

The problem of crashes seemed to have cleared up w/o me doing anything. Moving the crash reports out of the folder seems to help that it doesn't report the crash again.

The printing problem persists and in fact is worse. There are major print speed issues as well as scaling issues with two different PDF applications (not however with Apache OpenOffice). I'll submit these issues with a different posting.

In any event, thanks for your help.

business_kid 05-04-2019 05:58 AM

Glad to hear that. Upgrades often fix crashes, because the bug is reported and they fix it. Slackware doesn't do continual upgrades, but an update is never tested as well as a release. On this bit
Quote:

egrep "^Apr.+18" /var/log/syslog | egrep -i "error" | wc -l
15767

With than many lines for one date (15,767), I don't know how to pare it down.
I would try
Code:

tail -n 100 /var/log/syslog |less
which gives you a few screenfuls of the most recent stuff.


All times are GMT -5. The time now is 07:41 PM.