Bug 270319 – gnome-base/gnome-control-center-2.26.0: gnome-mouse-properties segfaults

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Märt Bakhoff 2009-05-18 16:49:11 UTC]

mart@artemis ~ $ gnome-mouse-properties 
Segmentation fault

Installed: 
gnome-base/gnome-control-center-2.26.0
gnome-base/gconf-2.26.2
x11-libs/gtk+-2.16.1

I did some hacking around and it seems that the problem is in
gnome-control-center-2.26.0/capplets/common/gconf-property-editor.c
345: gconf_entry_free (gconf_entry); // gconf_entry is NULL, don't know why. 
Commenting this line out makes the program work (not much of a fix)

Attaching emerge --info and gdb backtrace

Reproducible: Always

Steps to Reproduce:
1. using ~amd64, run emerge -uDNq world
2. try to use gnome-mouse-properties

[Comment 1 Märt Bakhoff 2009-05-18 16:55:03 UTC]

Created attachment 191701 [details]
gdb log and emerge --info

[Comment 2 Arun Raghavan (RETIRED) 2009-05-18 18:43:52 UTC]

Thanks for debugging this. Could you report this on upstream's Bugzilla (http://bugzilla.gnome.org/) and add a link to that bug in the URL field?

[Comment 3 Märt Bakhoff 2009-05-18 19:44:05 UTC]

Reported upstream, added URL: http://bugzilla.gnome.org/show_bug.cgi?id=583117

Some more ideas (see gdb backtrace): 
In gconf-editor, I don't have the subtree "/desktop/gnome/accessibility/mouse"

1) Add the missing keys to gconf defaults? Maybe is is supposed to be installed
by some accessibility component/use-flag? 

2) Patch gnome-contol-center (gconf_peditor_new in gconf-property-editor.c) to
check whether the key exists and use error reporting. Sound more like upstream
issue. Maybe it's already fixed in >gnome-control-center-2.26.0 ?

[Comment 4 Märt Bakhoff 2009-05-21 05:05:02 UTC]

Upstream reports resolved, fixed. 

[Comment 5 Gilles Dartiguelongue (RETIRED) 2009-06-08 22:34:31 UTC]

*** Bug 272500 has been marked as a duplicate of this bug. ***

[Comment 6 Flo Gravo 2009-06-09 23:24:41 UTC]

Created attachment 194054 [details, diff]
created a patch from the git-sources

[Comment 7 Gilles Dartiguelongue (RETIRED) 2009-06-11 22:51:36 UTC]

Obviously good to go.

[Comment 8 Romain Perier (RETIRED) 2009-06-17 06:08:34 UTC]

please re-sync your tree and re-run gnome-mouse-properties, there are two problems at the origin:
- Firstly gconf crashed, which is now fixd in the tree (gconf-2.26.2-r1)
- g-m-p doesn't must call gconf_entry_free with a NULL pointer, so your patch is correct :)

gconf fixs the crash, but now a Gconf-CRITICAL will be displayed in a terminal when you start g-m-p, your patch should fix the issue, thanks ;)

[Comment 9 peng shao 2009-06-17 06:36:12 UTC]

(In reply to comment #8)
> please re-sync your tree and re-run gnome-mouse-properties, there are two
> problems at the origin:
> - Firstly gconf crashed, which is now fixd in the tree (gconf-2.26.2-r1)
> - g-m-p doesn't must call gconf_entry_free with a NULL pointer, so your patch
> is correct :)
> 
> gconf fixs the crash, but now a Gconf-CRITICAL will be displayed in a terminal
> when you start g-m-p, your patch should fix the issue, thanks ;)
> 


Though I received error message

(gnome-mouse-properties:16609): GConf-CRITICAL **: gconf_entry_unref: assertion `entry != NULL' failed

I still got my gnome-mouse-properties window coming out. It is awesome! Thank you:)

[Comment 10 Romain Perier (RETIRED) 2009-06-17 10:22:46 UTC]

that's why we will probably include the patch, the problem of crash is now solved,
but we can include the patch for QA fix (Gconf-CRITICAL, because usually it's not really proper and it could avoid unnecessary other bugs about that) :)

[Comment 11 Gilles Dartiguelongue (RETIRED) 2009-07-20 23:03:15 UTC]

Fixed without a bump. Thanks for reporting.