Wit Wilinski: could you file a bug report as stated above?
Pedro Villavicencio : for me, it didn't create any .crash file. Maybe
because I never install any bug reporting system.. Anyway, I'm unable to
provide different bugreport than this one.
--
gnome-settings-daemon segfaults
https://bugs.lau
So, what happened to the bug report? I just upgraded my system to newest
version (Hardy repos) and gnome-settings-daemon crashed. strace revealed
that it was because missing xscreensaver. My fix for now was to remove
screensaver plugin from /usr/lib/gnome-settings-daemon/plugins/
--
gnome-setting
Thank you for taking the time to report this bug and helping to make
Ubuntu better. However, your crash report is either missing or
challenging to deal with as a ".crash" file. Please follow these
instuctions to have apport report a new bug about your crash that can be
dealt with by the automatic r
I found a workaround:
Open configuration editor and look for apps->
gnome-settings-daemon->screensaver and disable start-screensaver
apps-> gnome-settings-daemon->plugins->screensaver and disable active. Then
logged of and on and it seems to be normal.
--
gnome-settings-daemon segfaults
https:/
I get the same problem in Hardy with the newest version
2.21.90.1-0ubuntu3.
This is the message in terminal:
[EMAIL PROTECTED]:~$ gnome-settings-daemon
** (gnome-settings-daemon:11680): DEBUG: Successfully connected to D-Bus
** (gnome-settings-daemon:11680): DEBUG: Starting settings manager
** (gn
