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 445791 - crash in Panel: Gnome-session started wi...
crash in Panel: Gnome-session started wi...
Status: RESOLVED DUPLICATE of bug 403377
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-06-09 15:37 UTC by Leonardo Ferreira Fontenelle
Modified: 2007-06-10 02:06 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description Leonardo Ferreira Fontenelle 2007-06-09 15:37:07 UTC 
Version: 2.18.1

What were you doing when the application crashed?
Gnome-session started without metacity. I clicked on the Terminal launcher on the Panel, and instead of typing metacity<enter> as usual I typed openbox<enter> (I do have it installed). To my very surprise, the Panel crashed!


Distribution: Gentoo Base System release 1.12.9
Gnome Release: 2.18.1 2007-04-19 (Gentoo)
BugBuddy Version: 2.18.1

System: Linux 2.6.20-gentoo-r8 #5 Thu May 17 21:45:40 BRT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 37486592 vsize: 37486592 resident: 14737408 share: 11235328 rss: 14737408 rss_rlim: 4294967295
CPU usage: start_time: 1181402758 rtime: 93 utime: 84 stime: 9 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1224853840 (LWP 5231)]
0xb7fe2410 in __kernel_vsyscall ()

+ Trace 139597

Thread 1 (Thread -1224853840 (LWP 5231))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 libgnomeui_segv_handle
    at gnome-ui-init.c line 872
  • #3 <signal handler called>
  • #4 wnck_workspace_get_width
    at workspace.c line 293
  • #5 wnck_pager_expose_event
    at pager.c line 947
  • #6 _gtk_marshal_BOOLEAN__BOXED
    at gtkmarshalers.c line 84
  • #7 g_type_class_meta_marshal
    at gclosure.c line 567
  • #8 IA__g_closure_invoke
    at gclosure.c line 490
  • #9 signal_emit_unlocked_R
    at gsignal.c line 2478
  • #10 IA__g_signal_emit_valist
    at gsignal.c line 2209
  • #11 IA__g_signal_emit
    at gsignal.c line 2243
  • #12 gtk_widget_event_internal
    at gtkwidget.c line 3915
  • #13 IA__gtk_main_do_event
    at gtkmain.c line 1533
  • #14 gdk_window_process_updates_internal
    at gdkwindow.c line 2338
  • #15 IA__gdk_window_process_all_updates
    at gdkwindow.c line 2401
  • #16 gtk_container_idle_sizer
    at gtkcontainer.c line 1113
  • #17 g_idle_dispatch
    at gmain.c line 3928
  • #18 IA__g_main_context_dispatch
    at gmain.c line 2045
  • #19 g_main_context_iterate
    at gmain.c line 2677
  • #20 IA__g_main_loop_run
    at gmain.c line 2881
  • #21 IA__gtk_main
    at gtkmain.c line 1154
  • #22 main
    at main.c line 98
  • #0 __kernel_vsyscall 


----------- .xsession-errors (45 sec old) ---------------------
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
--------------------------------------------------
Comment 1 Pedro Villavicencio 2007-06-10 02:06:23 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 403377 ***