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 472358 - Crash in panel_profile_delete_object()
Crash in panel_profile_delete_object()
Status: RESOLVED OBSOLETE
Product: gnome-panel
Classification: Other
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Panel Maintainers
Panel Maintainers
: 477269 478720 480983 487952 515254 520810 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-08-31 22:34 UTC by justingrif
Modified: 2010-05-25 14:14 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description justingrif 2007-08-31 22:34:05 UTC 
Version: 2.18.3

What were you doing when the application crashed?
using vncconncet to hit my listening vnc viewer..i was also logged in localy on the same display i am guessing because it started crashing when i did that..i logged out locally and just left the vncviewer open	


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

System: Linux 2.6.22.4-65.fc7 #1 SMP Tue Aug 21 22:36:56 EDT 2007 i686
X Vendor: AT&T Laboratories Cambridge
X Vendor Release: 3332
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 39911424 vsize: 39911424 resident: 22626304 share: 16125952 rss: 22626304 rss_rlim: 4294967295
CPU usage: start_time: 1188555557 rtime: 226 utime: 168 stime: 58 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 -1208731936 (LWP 2648)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 159484

Thread 1 (Thread -1208731936 (LWP 2648))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 strcmp
    from /lib/libc.so.6
  • #5 panel_profile_remove_from_list
  • #6 panel_profile_delete_object
  • #7 ??
  • #8 g_cclosure_marshal_VOID
    from /lib/libgobject-2.0.so.0
  • #9 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #10 ??
    from /lib/libgobject-2.0.so.0
  • #11 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #12 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #13 gtk_dialog_response
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #16 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #17 ??
    from /lib/libgobject-2.0.so.0
  • #18 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #19 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #20 gtk_button_clicked
    from /usr/lib/libgtk-x11-2.0.so.0
  • #21 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #22 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #23 ??
    from /lib/libgobject-2.0.so.0
  • #24 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #25 ??
    from /lib/libgobject-2.0.so.0
  • #26 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #27 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #28 gtk_button_released
    from /usr/lib/libgtk-x11-2.0.so.0
  • #29 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #30 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #31 ??
    from /lib/libgobject-2.0.so.0
  • #32 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #33 ??
    from /lib/libgobject-2.0.so.0
  • #34 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #35 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #36 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #37 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #38 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #39 ??
    from /usr/lib/libgdk-x11-2.0.so.0
  • #40 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #41 ??
    from /lib/libglib-2.0.so.0
  • #42 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #43 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #44 main
  • #0 __kernel_vsyscall 






Comment 1


Vincent Untz





          2007-09-02 13:56:28 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!

It's not the first time I see a bug like this one, so keeping as NEEDINFO. But please, really a better stack trace would be helpful.

(bugsquad: don't close the bug, thanks)






Comment 2


Vincent Untz





          2007-09-16 08:51:10 UTC
        



*** Bug 477269 has been marked as a duplicate of this bug. ***






Comment 3


Susana





          2007-10-02 21:38:02 UTC
        



*** Bug 478720 has been marked as a duplicate of this bug. ***






Comment 4


Susana





          2007-10-02 21:38:08 UTC
        



*** Bug 480983 has been marked as a duplicate of this bug. ***






Comment 5


André Klapper





          2007-10-28 15:34:30 UTC
        



*** Bug 487952 has been marked as a duplicate of this bug. ***






Comment 6


Philip Withnall





          2008-02-08 20:51:11 UTC
        



*** Bug 515254 has been marked as a duplicate of this bug. ***






Comment 7


Philip Withnall





          2008-03-06 18:46:31 UTC
        



*** Bug 520810 has been marked as a duplicate of this bug. ***






Comment 8


Tobias Mueller





          2009-01-22 22:23:45 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!


Vincent: Obviously no new bugs since almost a year. Maybe we can close this bug as OBSOLETE?






Comment 9


Vincent Untz





          2009-06-20 22:13:51 UTC
        



(In reply to comment #8)
> Vincent: Obviously no new bugs since almost a year. Maybe we can close this bug
> as OBSOLETE?

No. See bug 578850.






Comment 10


Tobias Mueller





          2010-04-04 17:15:04 UTC
        



Again, no new bugs and no new traces. Also no dups downstream. I propose to close it as OBSOLETE then.






Comment 11


Tobias Mueller





          2010-05-25 14:14:57 UTC
        



Closing as OBSOLETE as per last comment