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 327898 - trashapplet crashes when restarting (killing) panel
trashapplet crashes when restarting (killing) panel
Status: RESOLVED DUPLICATE of bug 322730
Product: gnome-applets
Classification: Other
Component: trash applet
2.13.x
Other other
: High critical
: ---
Assigned To: gnome-applets Maintainers
gnome-applets Maintainers
: 327899 327992 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-01-20 18:31 UTC by Danilo Piazzalunga
Modified: 2006-02-14 18:26 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14


Description Danilo Piazzalunga 2006-01-20 18:31:41 UTC 
Distribution: Ubuntu 6.04 (dapper)
Package: gnome-applets
Severity: normal
Version: GNOME2.13.5 2.13.x
Gnome-Distributor: Ubuntu
Synopsis: trashapplet crashes when restarting (killing) panel
Bugzilla-Product: gnome-applets
Bugzilla-Component: trash applet
Bugzilla-Version: 2.13.x
BugBuddy-GnomeVersion: 2.0 (2.13.2)
Description:
When the panel is restarted (e.g. after killing it), every applet used
to restart itself without complaining.

With gnome-panel 2.13.5 and gnome-applets 2.13.2 (packages from Ubuntu
Dapper), trashapplet crashes.


Debugging Information:

Backtrace was generated from '/usr/libexec/trashapplet'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1224427840 (LWP 5744)]
[New Thread -1227224144 (LWP 5745)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 65423

Thread 2 (Thread -1227224144 (LWP 5745))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 ORBit_adaptor_setup
    from /usr/lib/libORBit-2.so.0
  • #5 ORBit_handle_request
    from /usr/lib/libORBit-2.so.0
  • #6 giop_connection_handle_input
    from /usr/lib/libORBit-2.so.0
  • #7 link_connection_set_max_buffer
    from /usr/lib/libORBit-2.so.0
  • #8 link_servers_move_io_T
    from /usr/lib/libORBit-2.so.0
  • #9 IA__g_main_context_dispatch
    at gmain.c line 1916
  • #10 g_main_context_iterate
    at gmain.c line 2547
  • #11 IA__g_main_loop_run
    at gmain.c line 2751
  • #12 link_thread_io_context
    from /usr/lib/libORBit-2.so.0
  • #13 g_thread_create_proxy
    at gthread.c line 582
  • #14 start_thread
    from /lib/tls/i686/cmov/libpthread.so.0
  • #15 clone
    from /lib/tls/i686/cmov/libc.so.6 




------- Bug created by bug-buddy at 2006-01-20 18:31 -------
Comment 1 Christian Kirbach 2006-01-20 18:46:39 UTC 
*** Bug 327899 has been marked as a duplicate of this bug. ***
Comment 2 Christian Kirbach 2006-01-20 18:55:17 UTC 
can you install the liborbit debug package please, and repost the stack trace?

Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.

trace matches Bug 146075
Comment 3 Christian Kirbach 2006-01-20 18:58:50 UTC 
please post further comments to the other report

*** This bug has been marked as a duplicate of 322730 ***
Comment 4 Karsten Bräckelmann 2006-02-14 18:26:26 UTC 
*** Bug 327992 has been marked as a duplicate of this bug. ***