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 419945 - crash in Panel: i chose a different them...
crash in Panel: i chose a different them...
Status: RESOLVED DUPLICATE of bug 422966
Product: gnome-panel
Classification: Other
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-03-19 00:06 UTC by kfirufk
Modified: 2007-07-03 12:23 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description kfirufk 2007-03-19 00:06:29 UTC
Version: 2.18.0

What were you doing when the application crashed?
i chose a different theme using the gnome-control-center
i chose theme Nuvola, nice theme :)


Distribution: Gentoo Base System version 1.12.9
Gnome Release: 2.18.0 2007-03-17 (Gentoo)
BugBuddy Version: 2.18.0

System: Linux 2.6.20-ck1 #1 Wed Feb 28 23:04:13 GMT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Nuvola
Icon Theme: Nuvola

Memory status: size: 138084352 vsize: 138084352 resident: 21626880 share: 13524992 rss: 21626880 rss_rlim: 18446744073709551615
CPU usage: start_time: 1174260375 rtime: 195 utime: 175 stime: 20 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47686704011680 (LWP 5848)]
0x00002b5eeb790ad5 in waitpid () from /lib/libpthread.so.0

Thread 1 (Thread 47686704011680 (LWP 5848))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 ??
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 g_str_hash
    from /usr/lib/libglib-2.0.so.0
  • #4 g_hash_table_remove
    from /usr/lib/libglib-2.0.so.0
  • #5 ??
    from /usr/lib/libgnome-menu.so.2
  • #6 ??
    from /usr/lib/libgnome-menu.so.2
  • #7 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #8 ??
    from /usr/lib/libglib-2.0.so.0
  • #9 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #10 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #11 main
  • #0 waitpid
    from /lib/libpthread.so.0


----------- .xsession-errors (41 sec old) ---------------------
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x1e0000d specified for 0x1e00040 (GTK MENUBA).
Window manager warning: Lost connection to the display ':0.0';
most likely the X server was shut down or you killed/destroyed
the window manager.
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x1e0000d specified for 0x1e00040 (GTK MENUBA).
Bonobo-Activation-Message: Reset cache
Bonobo-Activation-Message: Reset cache
Bonobo-Activation-Message: Reset cache
Bonobo-Activation-Message: Reset cache
(gnome-panel:5848): GConf-WARNING **: Client received notify for unknown connection ID 1275068491
(gnome-panel:5848): GConf-WARNING **: Client received notify for unknown connection ID 1275068491
(gnome-panel:5848): GConf-WARNING **: Client received notify for unknown connection ID 1275068491
--------------------------------------------------
Comment 1 Vincent Untz 2007-03-19 08:12:26 UTC
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Comment 2 kfirufk 2007-03-19 09:03:58 UTC
I'll recompile with debug symbols and open a bug if the problem persists.
Comment 3 Vincent Untz 2007-03-26 13:20:06 UTC
Just reopen this bug if the problem persists, there's no need to open a new bug.
Thanks
Comment 4 Diego Escalante Urrelo (not reading bugmail) 2007-06-06 00:09:30 UTC
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot
to solve the problem, so it will be hard for the developers to fix that crash.
Can you get us a stack trace with debugging symbols? Please see
http://live.gnome.org/GettingTraces for more information on how to do so and
reopen this bug or report a new one. Thanks in advance!

(Since bugzilla policy for bad_stacktrace is now to mark as INCOMPLETE. Mass
changing all of these. Search for "dieguito-doing-incomplete-spam" to delete
all this from your inbox.)
Comment 5 Karsten Bräckelmann 2007-07-03 12:23:04 UTC
Thanks for taking the time to report this bug.

This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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