Instability problem

Questions about other topics - please check if your question fits better in another category before posting here
Forum rules
Before you post please read how to get help
Post Reply
dan1
Level 1
Level 1
Posts: 1
Joined: Sat Aug 24, 2019 9:18 am

Instability problem

Post by dan1 » Sat Aug 24, 2019 9:28 am

Recently, I have had Linux Mint crash twice in a short space of time. I'm not sure what I can do to fix the problem. Here's a log of the errors I've received. I typed
journalctl -p 0..3
into the console:

Code: Select all

Aug 24 13:18:11 linux-mint-pc lightdm[1543]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
Aug 24 13:18:11 linux-mint-pc lightdm[1543]: PAM adding faulty module: pam_kwallet5.so
Aug 24 13:18:16 linux-mint-pc kernel: Could not find key with description: [36695416aafd7f5b]
Aug 24 13:18:16 linux-mint-pc kernel: Could not find valid key in user session keyring for sig specified in mount option: [36695416aafd7f5b]
Aug 24 13:18:16 linux-mint-pc kernel: Error parsing options; rc = [-2]
Aug 24 13:18:19 linux-mint-pc pulseaudio[1939]: [pulseaudio] pid.c: Daemon already running.
Aug 24 13:18:44 linux-mint-pc pulseaudio[1821]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes incl
-- Reboot --
Aug 24 14:14:42 linux-mint-pc systemd-udevd[769]: Invalid rule /etc/udev/rules.d/60-brother-brscan4-libsane-type1.rules:9: unknown key 'SYSFS{idVendor}'
Aug 24 14:14:42 linux-mint-pc systemd-udevd[769]: Invalid rule /etc/udev/rules.d/60-brother-libsane-type1-inst.rules:14: unknown key 'SYSFS{idVendor}'
Aug 24 14:14:44 linux-mint-pc lightdm[1426]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
Aug 24 14:14:44 linux-mint-pc lightdm[1426]: PAM adding faulty module: pam_kwallet.so
Aug 24 14:14:44 linux-mint-pc lightdm[1426]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
Aug 24 14:14:44 linux-mint-pc lightdm[1426]: PAM adding faulty module: pam_kwallet5.so
Aug 24 14:14:44 linux-mint-pc lightdm[1537]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
Aug 24 14:14:44 linux-mint-pc lightdm[1537]: PAM adding faulty module: pam_kwallet.so
Aug 24 14:14:44 linux-mint-pc lightdm[1537]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
Aug 24 14:14:44 linux-mint-pc lightdm[1537]: PAM adding faulty module: pam_kwallet5.so
Aug 24 14:14:49 linux-mint-pc kernel: Could not find key with description: [36695416aafd7f5b]
Aug 24 14:14:49 linux-mint-pc kernel: Could not find valid key in user session keyring for sig specified in mount option: [36695416aafd7f5b]
Aug 24 14:14:49 linux-mint-pc kernel: Error parsing options; rc = [-2]
Aug 24 14:14:52 linux-mint-pc pulseaudio[1933]: [pulseaudio] pid.c: Daemon already running.
Aug 24 14:15:17 linux-mint-pc pulseaudio[1814]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes incl
Any help would be greatly appreciated.

Gary Darkebear
Level 1
Level 1
Posts: 4
Joined: Sat Aug 24, 2019 8:56 am

Re: Instability problem

Post by Gary Darkebear » Thu Aug 29, 2019 8:03 pm

I have the same or a very similar error and system crash and reboot with a new install of 19.2.

Code: Select all

'[pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Since I'm totally new to all this I'm also looking to how to chase it down and solve it.

It is possibly evoked in my case from a news feed in Firefox. Two crashes today.

...one search had a suggested fix:

sudo systemctl enable bluetooth

...another suggested:

sudo systemctl disable --now bluetooth.service
viewtopic.php?f=47&t=276996&p=1589626&h ... h#p1589626

Is either the right approach?
One seems to be enabling the other to disable.

...as a follow-up: I implemented the link solution above to add an item into the 'start' menu items to make a command to turn-off the bluetooth stuff that seemed to possibly be associated with the two crashes of Mint 19.2 I've had happen yet that seemed associated with errors looking for pulseaudio.
I'm new to Linux and just trying to not get put-off by problems as I learn going ahead, so just so far I've not experienced a problem with doing the above 'fix'.
It all works after - Firefox runs as before and I get sound and it has not yet crashed again - but I need to run it longer.

I only experienced one other crash when I first installed 19.2 that happened after I brought up the resource monitor tool to see why my PC was running so much quieter than in Win 7; lower CPU activity - however after resizing the Resource App a few times to shrink it the PC rebooted and that was the first unhandled exception to the OS I experienced.

Post Reply

Return to “Other topics”