GNOME Bugzilla – Bug 654012
gnome-control-center crashed with SIGSEGV in gnome_rr_screen_get_output_by_name()
Last modified: 2011-08-25 04:48:06 UTC
this bug report has been filed here: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/805146 Backtrace: ".
+ Trace 227661
Thread 1 (Thread 16971)
I can't reproduce this. The code is wrong, I just can't figure *why*. On the g-c-c side we are using gnome_rr_screen_get_output_by_name() without ever setting a name. On the libgnome-desktop side we have a name field in GnomeRROutputInfoPrivate but there's only the initialization to NULL and we don't even provide a way to set it. Giovanni, you last touched this code, do you know what's going on ?
Created attachment 191328 [details] [review] gnome-rr.c: use g_strcmp0() instead of strcmp() to prevent a potential crash
That's most likely the wrong patch...
(In reply to comment #1) > I can't reproduce this. The code is wrong, I just can't figure *why*. > > On the g-c-c side we are using gnome_rr_screen_get_output_by_name() without > ever setting a name. On the libgnome-desktop side we have a name field in > GnomeRROutputInfoPrivate but there's only the initialization to NULL and we > don't even provide a way to set it. Giovanni, you last touched this code, do > you know what's going on ? GnomeRROutputInfo is not GnomeRROutput. The former is a configuration entry inside GnomeRRConfig, the latter is a wrapper aroung XRandR info. GnomeRROutput->name is set at line 1463 of gnome-rr.c from XRandR data, and I didn't touch it.
(In reply to comment #3) > That's most likely the wrong patch... Was being lazy :-) (In reply to comment #4) > GnomeRROutputInfo is not GnomeRROutput. The former is a configuration entry > inside GnomeRRConfig, the latter is a wrapper aroung XRandR info. > GnomeRROutput->name is set at line 1463 of gnome-rr.c from XRandR data, and I > didn't touch it. Right, I think I've grokked it now. I don't see how XRRGetOutputInfo() can return us a NULL for name without crashing itself though. It might be interesting to know if this is always reproducible for the reporter and if so, what's the output of 'xrandr' there.
I'm asking for that information on the downstream report.
I don't see any update in downstream bug. Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!