gnome-settings-daemon crashed with signal 5

StacktraceTop:acme_filter_events (xevent=0x0, event=0x8096248, data=0x8102408)
gdk_event_apply_filters (xevent=0xbfb387f8, event=0x8096248, filters=0x81cac50)
gdk_event_translate (display=0x8090010, event=0x8096248, xevent=0xbfb387f8,
_gdk_events_queue (display=0x8090010)
gdk_event_dispatch (source=0x8098298, callback=0, user_data=0x0)

Thanks for your report, do you use an extra monitor also? may you tell us a few steps to reproduce the crash? thanks.

I see this problem as well on a dell latitude X200.

I have an external monitor; however, as far as I can tell this system only allows mirroring of displays, and not a dual monitor/Xinerama setup.

As far as I can tell the crash happens when:
1. laptop is booted outside of media base.
2. laptop is connected to media base.
3. Fn+F8 is pressed to switch to the external monitor.
However, it doesn't seem to happen every time (possibly only the first time the above steps happen, possibly semi-randomly otherwise)

One other possibly related thing that also happens sometimes:
1. Laptop is booted outside of mediabase
2. Laptop is closed.
3. Laptop is connected to mediabase
4. Laptop is opened.
At this point, the built-in display is shifted down by approximately 24 pixels (estimate based on size of upper panel, with garbage graphics appearing at the top. The mouse can be moved outside the desktop area proper, into the garbage area. If I use ctrl+alt+F1 to move to the console and back to X, the display is shifted back to where it should be.

I'm not sure if these two problems are related; they may happen entirely independently.

I don't have a secondary display to attach, but I still do get the same crash upon hitting my 'hotkey display switch' hotkey.
Last line of gnome-settings-daemon console output is this:

** ERROR **: file gnome-settings-multimedia-keys.c: line 749 (do_action): should not be reached
aborting...

Oh, and another note (curse the lack of edit function...): when I repeatedly kill gnome-settings-daemon so it stops respawning, then I can run 'xev' and hit the hotkey, and it tells me the key is 'xf86display'.
Apport didn't automatically post the stack trace to this existing bug, so I've just posted the apport file from /var/crash

Found another relevant datum:

It's not the keypress that does it, it's the video output switching. On my system (Dell Latitude X200), if I place the machine in the mediabase with the lid closed, it will automatically change to the external display. This will also crash gnome-settings-daemon.

Thank you for your bug. Does anybody still get the issue using the current versions?

Dnia 2008-02-09, So o godzinie 10:08 +0000, Sebastien Bacher pisze:
> Thank you for your bug. Does anybody still get the issue using the
> current versions?
It seems to be everything ok now.

For me it's fixed.

For me g-s-d continues to crash. It crashes every time I close and open my laptop lid. I have a lenovo T61 running current hardy AMD64.

-BenRI

If I run gnome-settings-daemon from the terminal with --no-daemon, then I am able to get the following error message.

**
** ERROR:(gsd-media-keys-manager.c:911):do_action: code should not be reached
[1202571033,000,xklavier.c:xkl_engine_start_listen/] The backend does not require manual layout management - but it is provided by the applicationAborted (core dumped)

This may be frequently reported bug - it is also in bug #190003, for example.

Examining the file gsd-media-keys-manager.c, there is actually a 1-line patch that could fix this problem: simply remove "g_assert_not_reached ();"

http://svn.gnome.org/viewvc/gnome-settings-daemon/tags/GNOME_SETTINGS_DAEMON_2_21_90_2/plugins/media-keys/gsd-media-keys-manager.c?view=annotate

In the function "static gboolean do_action (GsdMediaKeysManager *manager, int type)" it is explicitly stated that the daemon should crash on media keys that are unrecognized, instead of doing nothing! Therefore, all that is needed to fix this bug is to change this...

902 case NEXT_KEY:
903 return do_multimedia_player_action (manager, "Next");
904 break;
905 default:
906 g_assert_not_reached ();
907 }
908
909 return FALSE;

... to remove the g_assert_not_reached ();

While crashing when unknown media keys are pressed may help developers, it is not terribly productive for the end user.

-BenRI

Sure enough, the following command fixes this problem:

$ sudo rm -rf /usr/lib/gnome-settings-daemon/plugins/media-keys/

Is this really incomplete? If not, what information is being requested?

No, it's not incomplete, the desktop team just get load on bugs for the number of people looking at them and it's not easy to deal with the load, there is enough informations to send that on bugzilla now

Attaching a patch to fix this.

This bug was fixed in the package gnome-settings-daemon - 2.21.91-0ubuntu4

---------------
gnome-settings-daemon (2.21.91-0ubuntu4) hardy; urgency=low

  * debian/patches/19_extra_keybindings.patch:
    - "Add proper xrandr callback when XF86Display is pressed.",
       thanks Mario Limonciello (lp: #179444)
  * debian/patches/90_from_svn_pulseaudio_correct_use.patch:
    - change from svn to make pulseaudio work correctly

 -- Sebastien Bacher <email address hidden> Thu, 28 Feb 2008 22:09:04 +0100

My crash of gnome-settings-daemon happened after click on icon of Keyboard in gnome-control-center. I have a lot of problems from 2.2.24-10with keyboard - often not detected, I cannot log-in, but I have to report it as a different bug. This crash was in fully working system when I tried to review settings of keyboard in Control center.

Still here with the last couple of dist-upgrades of Hardy.. I was attempting to set the audio utility, but audio settings are still out.

I'm new to Ubuntu I don't know why this applet crashes, it occurs when I boot up the my system. It may not even be the settings I did not read the report!!??

I did report it when it happend so maybe someone will send me the info required to sort the problem out!