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 352182 - Panel crashes when editing properties
Panel crashes when editing properties
Status: RESOLVED DUPLICATE of bug 350425
Product: gnome-panel
Classification: Other
Component: panel
2.15.x
Other All
: Normal critical
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-08-20 20:34 UTC by Frédéric Bellaiche
Modified: 2006-08-20 22:35 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16

Attachments
Full stack strace (last one's been truncated) (124.89 KB, text/plain)
2006-08-20 20:37 UTC, Frédéric Bellaiche 		Details

Description Frédéric Bellaiche 2006-08-20 20:34:09 UTC 
Steps to reproduce:
1. Edit the properties of a launcher (right-clicking from menu)
2. 
3. 


Stack trace:
Stacktrace from bug-buddy

Memory status: size: 39354368 vsize: 0 resident: 39354368 share: 0 rss: 16347136 rss_rlim: 0
CPU usage: start_time: 1156105034 rtime: 0 utime: 161 stime: 0 cutime:146 cstime: 0 timeout: 15 it_real_value: 0 frequency: 0

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 -1226328400 (LWP 6013)]
0xffffe410 in ?? ()

+ Trace 70761

Thread 1 (Thread -1226328400 (LWP 6013))

  • #0 ??
  • #1 ??
  • #2 ??
  • #3 ??
  • #4 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #5 libgnomeui_segv_handle
    at gnome-ui-init.c line 867
  • #6 <signal handler called>
  • #7 ??
  • #8 ??
  • #9 ??
  • #10 ??
  • #11 *__GI_raise
    at ../nptl/sysdeps/unix/sysv/linux/raise.c line 67
  • #12 *__GI_abort
    at abort.c line 88
  • #13 IA__g_logv
    at gmessages.c line 497
  • #14 IA__g_log
    at gmessages.c line 517
  • #15 IA__g_return_if_fail_warning
    at gmessages.c line 532
  • #16 gnome_icon_selection_clear
    at gnome-icon-sel.c line 501
  • #17 entry_activated
    at gnome-icon-entry.c line 395
  • #18 IA__g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #19 IA__g_closure_invoke
    at gclosure.c line 490
  • #20 signal_emit_unlocked_R
    at gsignal.c line 2438
  • #21 IA__g_signal_emit_valist
    at gsignal.c line 2197
  • #22 IA__g_signal_emit
    at gsignal.c line 2241
  • #23 IA__gtk_widget_activate
    at gtkwidget.c line 3932
  • #24 entry_changed
    at gnome-icon-entry.c line 520
  • #25 IA__g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #26 IA__g_closure_invoke
    at gclosure.c line 490
  • #27 signal_emit_unlocked_R
    at gsignal.c line 2508
  • #28 IA__g_signal_emit_valist
    at gsignal.c line 2197
  • #29 IA__g_signal_emit_by_name
    at gsignal.c line 2265
  • #30 gtk_entry_real_insert_text
    at gtkentry.c line 2427
  • #31 _gtk_marshal_VOID__STRING_INT_POINTER
    at gtkmarshalers.c line 1145
  • #32 g_type_iface_meta_marshal
    at gclosure.c line 590
  • #33 IA__g_closure_invoke
    at gclosure.c line 490
  • #34 signal_emit_unlocked_R
    at gsignal.c line 2476
  • #35 IA__g_signal_emit_valist
    at gsignal.c line 2197
  • #36 IA__g_signal_emit_by_name
    at gsignal.c line 2265
  • #37 gtk_entry_insert_text
    at gtkentry.c line 2127
  • #38 IA__gtk_editable_insert_text
    at gtkeditable.c line 110
  • #39 IA__gtk_entry_set_text
    at gtkentry.c line 4134
  • #40 gtk_combo_update_entry
    at gtkcombo.c line 695
  • #41 IA__g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #42 IA__g_closure_invoke
    at gclosure.c line 490
  • #43 signal_emit_unlocked_R
    at gsignal.c line 2438 


Other information:
Comment 1 Frédéric Bellaiche 2006-08-20 20:37:58 UTC 
Created attachment 71264 [details]
Full stack strace (last one's been truncated)

This is the full stack trace given by bug-buddy.
Comment 2 Sergej Kotliar 2006-08-20 22:35:13 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 350425 ***