Bug 247450 - x11/mate: mate-settings-daemon crashing on 1.24
Summary: x11/mate: mate-settings-daemon crashing on 1.24
Status: Open
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Some People
Assignee: freebsd-gnome (Nobody)
URL:
Keywords: crash, needs-qa
Depends on:
Blocks:
 
Reported: 2020-06-20 22:21 UTC by rkoberman
Modified: 2020-07-20 18:47 UTC (History)
5 users (show)

See Also:
bugzilla: maintainer-feedback? (gnome)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description rkoberman 2020-06-20 22:21:06 UTC
Updating the multiple ports that makeup mate om 1.22 to 1.24 left an unusable system. Several daemons repeatedly crash leaving the system is a bad state.

mate-settings-daemon continued to crash every few seconds. This is serious as I have a bad key that I map around and also make Caps-Lk into a CTRL. (The latter just because my brain has never accepted the Microsoft keyboard re-work to kill WordPerfect.)

In addition, I have not tested Atril at this time. Also, some other mate ports remain at 1.22 (e.g.Caja, Marco) I'm guessing that these are awaiting the update of glib20. I'm unsure of the impact of this issues.

System is running 12-STABLE r362181 and an almost GERNERIC kernel. (I run 4BSD instead of ULE.)
\
From messages:
Jun 20 14:20:21 rogue gnome-keyring-daemon[56655]: couldn't access control socket: /var/run/user/9381/keyring/control: No such file or directory
Jun 20 14:20:21 rogue gnome-keyring-daemon[56655]: Gkm: using old keyring directory: /home/oberman/.gnome2/keyrings
Jun 20 14:20:21 rogue syslogd: last message repeated 1 times
Jun 20 14:20:21 rogue gnome-keyring-daemon[56655]: couldn't allocate secure memory to keep passwords and or keys from being written to the disk
Jun 20 14:20:21 rogue mate-session[56631]: WARNING: Unable to find provider '' of required component 'dock'
Jun 20 14:20:23 rogue gnome-keyring-daemon[56655]: The PKCS#11 component was already initialized
Jun 20 14:20:23 rogue gnome-keyring-daemon[56655]: The Secret Service was already initialized
Jun 20 14:20:23 rogue mate-session[56631]: WARNING: Could not launch application 'gpk-update-icon.desktop': Unable to start application: Failed to execute child process <E2>M-^@M-^\gpk-update-icon<E2>M-^@M-^] (No such file or directory)
Jun 20 14:20:24 rogue kernel: pid 56656 (mate-settings-daemo), jid 0, uid 9381: exited on signal 11 (core dumped)
Jun 20 14:20:26 rogue kernel: pid 56676 (mate-volume-control), jid 0, uid 9381: exited on signal 6 (core dumped)
Jun 20 14:20:28 rogue kernel: pid 56712 (mate-settings-daemo), jid 0, uid 9381: exited on signal 11 (core dumped)
Jun 20 14:20:23 rogue mate-session[56631]: WARNING: Could not launch application 'gpk-update-icon.desktop': Unable to start application: Failed to execute child process <E2>M-^@M-^\gpk-update-icon<E2>M-^@M-^] (No such file or directory)
Jun 20 14:20:24 rogue kernel: pid 56656 (mate-settings-daemo), jid 0, uid 9381: exited on signal 11 (core dumped)
Jun 20 14:20:26 rogue kernel: pid 56676 (mate-volume-control), jid 0, uid 9381: exited on signal 6 (core dumped)
Jun 20 14:20:28 rogue kernel: pid 56712 (mate-settings-daemo), jid 0, uid 9381: exited on signal 11 (core dumped)
Jun 20 14:20:29 rogue /hp-upgrade[56776]: hp-upgrade[56776]: warning:  distro is not found in AUTH_TYPES
Jun 20 14:20:31 rogue kernel: pid 56741 (mate-settings-daemo), jid 0, uid 9381: exited on signal 11 (core dumped)
Jun 20 14:20:34 rogue kernel: pid 56795 (mate-settings-daemo), jid 0, uid 9381: exited on signal 11 (core dumped)
Jun 20 14:20:37 rogue kernel: pid 56801 (mate-settings-daemo), jid 0, uid 9381: exited on signal 11 (core dumped)
Jun 20 14:20:40 rogue kernel: pid 56808 (mate-settings-daemo), jid 0, uid 9381: exited on signal 11 (core dumped)
Jun 20 14:20:43 rogue kernel: pid 56810 (mate-settings-daemo), jid 0, uid 9381: exited on signal 11 (core dumped)
Jun 20 14:20:46 rogue kernel: pid 56811 (mate-settings-daemo), jid 0, uid 9381: exited on signal 11 (core dumped)
Jun 20 14:20:48 rogue kernel: pid 56818 (mate-settings-daemo), jid 0, uid 9381: exited on signal 11 (core dumped)
Jun 20 14:20:51 rogue mate-session[56631]: WARNING: Child process 56819 was already dead.
Comment 1 Jason W. Bacon freebsd_committer 2020-07-17 00:54:03 UTC
I'm seeing the same crash.

I just ran a test of sysutils/desktop-installer on FreeBSD 12.1 under VirtualBox and chose Mate.

Everything went smoothly, but the desktop background doesn't seem to get set and if I try to open Preferences/Look and Feel/Appearance I get a pop-up "Unable to start the settings manager 'mate-settings-deamon'.
Comment 2 Eric Turgeon freebsd_committer 2020-07-17 12:50:09 UTC
I seen that error before on GhostBSD when compiling audio/libmatemixer without PulseAudio looks like OSS is not working properly with audio/libmatemixer I did not take the time to investigate further.
Comment 3 rkoberman 2020-07-17 17:17:06 UTC
(In reply to Eric Turgeon from comment #2)
I confirm that I have been using OSS (i.e. Pulse and ALSA disabled.)

I will try updating again, first with ALSA. I have had enough bad experiences with Pulse that I really hope to avoid it. This will likely not happen until tomorrow due too available time today.
Comment 4 rkoberman 2020-07-20 18:47:09 UTC
updated to 1.24 again and rebuild libmatemixer with the default pulseaudio. No improvement. The mate-settings-daemon still continuously crashes and restarts.

I will check for other mate ports with non-standard build options.