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 503964 - crash in Panel: using gnome-terminal, an...
crash in Panel: using gnome-terminal, an...
Status: RESOLVED DUPLICATE of bug 446183
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-12-17 02:01 UTC by jonstanley
Modified: 2008-01-08 19:16 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description jonstanley 2007-12-17 02:01:06 UTC 
Version: 2.18.3

What were you doing when the application crashed?
using gnome-terminal, and the whole X session just gave up the ghost.


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.23.8-34.fc7 #1 SMP Thu Nov 22 20:39:56 EST 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Bluecurve
Icon Theme: Bluecurve

Memory status: size: 322015232 vsize: 322015232 resident: 31854592 share: 28258304 rss: 31854592 rss_rlim: 18446744073709551615
CPU usage: start_time: 1197856821 rtime: 8 utime: 6 stime: 2 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 "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496376688 (LWP 11676)]
(no debugging symbols found)
0x000000311b00d945 in waitpid () from /lib64/libpthread.so.0

+ Trace 182078

Thread 1 (Thread 46912496376688 (LWP 11676))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #4 g_hash_table_foreach
    from /lib64/libglib-2.0.so.0
  • #5 gtk_rc_reset_styles
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #6 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #7 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #8 g_cclosure_marshal_VOID__ENUM
    from /lib64/libgobject-2.0.so.0
  • #9 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #10 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #11 g_cclosure_marshal_VOID__ENUM
    from /lib64/libgobject-2.0.so.0
  • #12 g_object_notify
    from /lib64/libgobject-2.0.so.0
  • #13 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #14 gtk_main_do_event
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #15 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgdk-x11-2.0.so.0
  • #16 g_main_context_dispatch
    from /lib64/libglib-2.0.so.0
  • #17 g_cclosure_marshal_VOID__ENUM
    from /lib64/libglib-2.0.so.0
  • #18 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #19 gtk_main
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #20 main
  • #0 waitpid
    from /lib64/libpthread.so.0 


----------- .xsession-errors ---------------------
        \   ^__^
         \  (oo)\_______
            (__)\       )\/\
                ||----w |
                ||     ||
SESSION_MANAGER=local/unix:/tmp/.ICE-unix/11547
Initializing nautilus-open-terminal extension
(gnome-panel:11676): GConf-WARNING **: Directory `/apps/panel/toplevels/bottom_panel_screen1/screen' was not being monitored by GConfClient 0x6c35e0
(gnome-panel:11676): GConf-WARNING **: Directory `/apps/panel/toplevels/top_panel_screen1/screen' was not being monitored by GConfClient 0x6c35e0
(gnome-panel:11676): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7fff163fd000
--------------------------------------------------
Comment 1 André Klapper 2008-01-08 19:16: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 446183 ***