On Thu 12.May'11 at 8:24:13 +0200, Dominique Leuenberger wrote:
On Thu, 2011-05-12 at 12:26 +0800, FJKong wrote:
Do you guys meet this before?
Gtk-Message: Failed to load module "gnomesegvhandler" Segmentation fault
The segfault is unrelated to the message before (this would have just been a 'debugger' kicking in, which would not have saved you).
There is much more context needed than those two lines.
How do you reproduce the segfault? Possibly running the application causing it in gdb and producing a backtrace.
Dominique
-- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-gnome+help@opensuse.org
... ... ... ... Try: zypper install -C "debuginfo(build-id)=1006157020de7ed002be6edd6af53683f174d420" Missing separate debuginfo for /usr/lib/libvorbisenc.so.2 Try: zypper install -C "debuginfo(build-id)=aab4cad4c2b04fac6d5c25a9f0cc8c6c1d2034e7" Gtk-Message: Failed to load module "gnomesegvhandler" Program received signal SIGSEGV, Segmentation fault. 0xb6c936d0 in XF86DRIQueryExtension () from /usr/lib/libGL.so.1 (gdb) bt #0 0xb6c936d0 in XF86DRIQueryExtension () from /usr/lib/libGL.so.1 #1 0x00000078 in ?? () #2 0xb7555b2d in ?? () from /lib/libc.so.6 Backtrace stopped: previous frame inner to this frame (corrupt stack?) (gdb) -- Novell Making IT Work As One www.novell.com -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-gnome+help@opensuse.org