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 106356 - Crash when running gnome-session-properties
Crash when running gnome-session-properties
Status: RESOLVED DUPLICATE of bug 105834
Product: gnome-panel
Classification: Other
Component: panel
2.2.x
Other other
: High critical
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks: 106355
 
 
Reported: 2003-02-17 23:17 UTC by Kjartan Maraas
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Kjartan Maraas 2003-02-17 23:11:27 UTC 
Package: gnome-panel
Severity: normal
Version: GNOME2.2.0 2.2.0
os_details: Gnome.Org
Synopsis: Crash when running gnome-session-properties
Bugzilla-Product: gnome-panel
Bugzilla-Component: Panel
BugBuddy-GnomeVersion: 2.0 (2.2.0.1)
Description:
Description of Problem:

I just tried to start gnome-session-properties. I do have some local
mods here though and I will attach the diff here so you can see if that
has anything to do with it.

Steps to reproduce the problem:
1. 
2. 
3. 

Actual Results:


Expected Results:


How often does this happen?


Additional Information:



Debugging Information:

Backtrace was generated from '/gnome/head/INSTALL/bin/gnome-panel'

[New Thread 1024 (LWP 599)]
0x40a5d219 in __wait4 () at __wait4:-1
	in __wait4

+ Trace 33938

Thread 1 (Thread 1024 (LWP 599))

  • #0 __wait4
  • #1 __DTOR_END__
    from /lib/i686/libc.so.6
  • #2 waitpid
    at wrapsyscall.c line 172
  • #3 libgnomeui_segv_handle
    at gnome-ui-init.c line 646
  • #4 pthread_sighandler
    at signals.c line 97
  • #5 <signal handler called>
  • #6 __libc_free
    at malloc.c line 3136
  • #7 do_free
    at memintercept.c line 194
  • #8 g_free
    at gmem.c line 186
  • #9 g_strfreev
    at gstrfuncs.c line 2194
  • #10 ditem_execute
    at gnome-desktop-item.c line 1892
  • #11 gnome_desktop_item_launch_on_screen_with_env
    at gnome-desktop-item.c line 1994
  • #12 gnome_desktop_item_launch_on_screen
    at gnome-desktop-item.c line 2089
  • #13 panel_ditem_launch
    at panel-util.c line 82
  • #14 activate_app_def
    at menu.c line 347
  • #15 g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #16 g_closure_invoke
    at gclosure.c line 437
  • #17 signal_emit_unlocked_R
    at gsignal.c line 2822
  • #18 g_signal_emit_valist
    at gsignal.c line 2554
  • #19 g_signal_emit
    at gsignal.c line 2612
  • #20 gtk_widget_activate
    at gtkwidget.c line 3175
  • #21 gtk_menu_shell_activate_item
    at gtkmenushell.c line 914
  • #22 gtk_menu_shell_button_release
    at gtkmenushell.c line 528
  • #23 gtk_menu_button_release
    at gtkmenu.c line 1972
  • #24 _gtk_marshal_BOOLEAN__BOXED
    at gtkmarshalers.c line 82
  • #25 g_type_class_meta_marshal
    at gclosure.c line 514
  • #26 g_closure_invoke
    at gclosure.c line 437
  • #27 signal_emit_unlocked_R
    at gsignal.c line 2860
  • #28 g_signal_emit_valist
    at gsignal.c line 2564
  • #29 g_signal_emit
    at gsignal.c line 2612
  • #30 gtk_widget_event_internal
    at gtkwidget.c line 3143
  • #31 gtk_propagate_event
    at gtkmain.c line 2253
  • #32 gtk_main_do_event
    at gtkmain.c line 1502
  • #33 gdk_event_dispatch
    at gdkevents-x11.c line 2018
  • #34 g_main_dispatch
    at gmain.c line 1653
  • #35 g_main_context_dispatch
    at gmain.c line 2197
  • #36 g_main_context_iterate
    at gmain.c line 2278
  • #37 g_main_loop_run
    at gmain.c line 2498
  • #38 gtk_main
    at gtkmain.c line 1092
  • #39 main
    at main.c line 216
  • #40 __libc_start_main
    at ../sysdeps/generic/libc-start.c line 129 




------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-02-17 18:11 -------

Reassigning to the default owner of the component, gnome-panel-maint@bugzilla.gnome.org.
Comment 1 Elijah Newren 2003-02-18 21:54:55 UTC 
Appears to be a unique stack trace, according to the
simple-dup-finder.  Setting version->2.2.x, marking priority->high &
severity->critical (it's a crasher), adding GNOMEVER2.2 and bugsquad
keywords, and marking as new.  I'll also set the STACKTRACE keyword
since the stack trace has debugging symbols in it.
Comment 2 Kjartan Maraas 2003-02-18 22:25:35 UTC 
Duplicate of report with patch to fix this.

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