gconf-editor crashed with SIGSEGV in gdk_window_set_cursor()

[Adam Jeżewski]

Binary package hint: gconf-editor

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=8.04
DISTRIB_CODENAME=hardy
DISTRIB_DESCRIPTION="Ubuntu hardy (development branch)"
Alpha 5

How to reproduce the bug:
1. Open gconf-editor
2. Open search dialog (CTRL+F)
3. Type something (for example "desktop")
4. Press the "Search" button
5. During search, close the search dialog

ProblemType: Crash
Architecture: i386
Date: Sat Feb 23 12:23:59 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/gconf-editor
NonfreeKernelModules: nvidia
Package: gconf-editor 2.20.0-2ubuntu1
PackageArchitecture: i386
ProcCmdline: gconf-editor
ProcCwd: /home/echinos
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=pl_PL.UTF-8
Signal: 11
SourcePackage: gconf-editor
Stacktrace:
 #0 0xb7b4a359 in gdk_window_set_cursor () from /usr/lib/libgdk-x11-2.0.so.0
 #1 0x0805dceb in ?? ()
 #2 0xaaaaaaaa in ?? ()
 #3 0x00000000 in ?? ()
StacktraceTop:
 gdk_window_set_cursor () from /usr/lib/libgdk-x11-2.0.so.0
 ?? ()
 ?? ()
 ?? ()
Title: gconf-editor crashed with SIGSEGV in gdk_window_set_cursor()
Uname: Linux desktop 2.6.24-8-generic #1 SMP Thu Feb 14 20:40:45 UTC 2008 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin plugdev video
SegvAnalysis:
 Segfault happened at: 0xb7b4a359 <gdk_window_set_cursor+41>: mov (%esi),%edx
 PC (0xb7b4a359) ok
 source "(%esi)" (0xaaaaaaaa) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading unknown VMA

[Apport retracing service (apport)]

StacktraceTop:IA__gdk_window_set_cursor (window=0xaaaaaaaa, cursor=0x0)
gconf_search_dialog_search (button=0x8266888, dialog=0x8270068)
IA__g_cclosure_marshal_VOID__VOID (closure=0x8271928, return_value=0x0, n_param_values=1,
IA__g_closure_invoke (closure=0x8271928, return_value=0x0, n_param_values=1,
signal_emit_unlocked_R (node=0x80a8878, detail=0, instance=0x8266888, emission_return=0x0,

[Pedro Villavicencio (pedro)]

Thanks for your bug report. This bug has been reported to the developers of the software. You can track it and make comments here: http://bugzilla.gnome.org/show_bug.cgi?id=518601

[Adam Petaccia (mighmos)]

I've just encountered this bug as well. I cancelled a find and started clicking in the tree listing when it happened.

[Stéphane Maniaci (stephh)]

Same comment as Adam.