PDA

View Full Version : Strange behaviour on context menu Eye of Gnome, Gthumb, Gimp


CentralX
November 12th, 2006, 03:04 PM
Hello everyone,

I noticed a bug which is probably related to the latest gandalfn compiz-freedesktop-dev version. When minimizing Eye of Gnome, The Gimp or Gthumb to gnome-panel and right clicking on it to bring up the context menu, gnome panel crashes producing the following bug report:


Memory status: size: 62808064 vsize: 0 resident: 62808064 share: 0 rss: 19058688 rss_rlim: 0
CPU usage: start_time: 1163290087 rtime: 0 utime: 2373 stime: 0 cutime:2159 cstime: 0 timeout: 214 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/gnome-panel'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1224972624 (LWP 25274)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0xb7fd6410 in ?? ()
#0 0xb7fd6410 in ?? ()
#1 0xbfb4aad8 in ?? ()
#2 0x00000000 in ?? ()

Thread 1 (Thread -1224972624 (LWP 25274)):
#0 0xb7fd6410 in ?? ()
No symbol table info available.
#1 0xbfb4aad8 in ?? ()
No symbol table info available.
#2 0x00000000 in ?? ()
No symbol table info available.
#0 0xb7fd6410 in ?? ()


This doesn't happen when just pure metacity is loaded, so perhaps it might be related to compiz-freedesktop. I'm using the following package versions:

compiz-freedesktop 0.3.3-0gandalfn7
compiz-freedesktop-gnome 0.3.3-0gandalfn7
compiz-freedesktop-extra 0.3.3-0gandalfn9
gnome-compiz-manager 0.9.11pre1-1gandalfn1
gnome-compiz-manager-extra 0.1.3-0gandalfn1

I'm also using NVIDIA driver version 96.29 on Gnome 2.16.1, Ubuntu Edgy 6.10. My system is a Dell Inspiron 5150 (P4 3.06Ghz HT, 512MB) with GeForce 5200FX Go.

Does someone also have this bug or is it known?

Thanks in advance,

CentralX

RYX
November 17th, 2006, 08:47 PM
Hi CentralX. I can not reproduce this bug the way you described. I have a very similar system setup, but I am using a self-compiled compiz 0.3.2 from go-compiz.org. So it really seems to be related to gandalfn's release.

Sorcerer
November 18th, 2006, 09:11 AM
Happens also with gnome-terminal and Firefox.
Ubuntu Edgy, i915 graphics.

CentralX
November 18th, 2006, 02:32 PM
In the stable release of gandalfn (0.2.2) this bug doesn't occur. I know they switched recently from gnome-window-decorator to gtk-window-decorator (don't know however if there's much difference between the two) so perhaps it is related to some glitches in gtk-window-decorator in gandalfn's release?

I also noticed that it mainly happens when some big images are loaded in these programs (like gimp and gThumb... etc).

Maybe I'll try to compile compiz from source and see what happens... I'll report back when I know more... :)