After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 337667 - Theme Preferences crashes on switching themes with Compiz
Theme Preferences crashes on switching themes with Compiz
Status: RESOLVED DUPLICATE of bug 333276
Product: gnome-control-center
Classification: Core
Component: [obsolete] theme-manager
2.14.x
Other other
: High critical
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-04-07 18:17 UTC by Tomer Chachamu
Modified: 2006-04-07 22:06 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description Tomer Chachamu 2006-04-07 18:17:48 UTC
Distribution: Ubuntu 6.06 (dapper)
Package: control-center
Severity: major
Version: GNOME2.14.0 2.14.x
Gnome-Distributor: Ubuntu
Synopsis: Theme Preferences crashes on switching themes
Bugzilla-Product: control-center
Bugzilla-Component: theme-manager
Bugzilla-Version: 2.14.x
BugBuddy-GnomeVersion: 2.0 (2.14.0)
Description:
Description of the crash:
"Custom theme" was selected. I clicked on "Clearlooks" and it hung for
about a minute before showing me the crash window. The "Theme
Preferences" still has the Human theme border, but other windows are the
blue Clearlooks with full window borders - including the bottom panel
which has the title "Bottom Expanded Edge Panel" and the top panel which
has a thick border.

How often does this happen?
I will try to reproduce it now.

Additional Information:

I am using Dapper Drake with Compiz and XGL.


Debugging Information:

Backtrace was generated from '/usr/bin/gnome-theme-manager'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1224971904 (LWP 15733)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1224971904 (LWP 15733))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 strcmp
    from /lib/tls/i686/cmov/libc.so.6
  • #5 main
  • #0 __kernel_vsyscall




------- Bug created by bug-buddy at 2006-04-07 18:17 -------

Comment 1 Tomer Chachamu 2006-04-07 18:20:42 UTC
I just tried reproducing by switching to another theme (Crux).

This time, Bug Buddy immediately came up. By the way, Crux is really ugly.

Backtrace was generated from '/usr/bin/gnome-theme-manager'

(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)
[Thread debugging using libthread_db enabled]
[New Thread -1225578112 (LWP 16030)]
(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)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1225578112 (LWP 16030))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 strcmp
    from /lib/tls/i686/cmov/libc.so.6
  • #5 main
  • #0 __kernel_vsyscall

Comment 2 Tomer Chachamu 2006-04-07 18:23:01 UTC
I just logged in and out. The window borders on the panels disappeared, but when I switched theme again (back to Clearlooks) they appeared again, and there was another crash.

Now I'll try without Compiz.
Comment 3 Tomer Chachamu 2006-04-07 18:30:32 UTC
Compiz is the cause.
Comment 4 Sergej Kotliar 2006-04-07 22:06:42 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 333276 ***