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 327971 - Crash when running 'killall gnome-panel'
Crash when running 'killall gnome-panel'
Status: RESOLVED DUPLICATE of bug 326283
Product: gnome-applets
Classification: Other
Component: Disk Mounter (drivemount)
2.13.x
Other Linux
: Normal critical
: ---
Assigned To: gnome-applets Maintainers
gnome-applets Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-01-21 13:31 UTC by Kjartan Maraas
Modified: 2006-01-26 10:33 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Kjartan Maraas 2006-01-21 13:31:48 UTC 
Crashed when running the above command. Backtrace from gdb:

(gdb) thread apply all bt

+ Trace 65448

Thread 2 (Thread -1211311200 (LWP 2571))

  • #0 ??
  • #1 ??
    from /lib/libpthread.so.0
  • #2 gbi_idle_handler
    at bonobo-canvas-item.c line 712
  • #3 <signal handler called>
  • #4 ORBit_adaptor_find
    at orbit-adaptor.c line 164
  • #5 ORBit_handle_request
    at orbit-adaptor.c line 255
  • #6 giop_connection_handle_input
    at giop-recv-buffer.c line 1282
  • #7 link_connection_io_handler
    at linc-connection.c line 1367
  • #8 link_source_dispatch
    at linc-source.c line 159
  • #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_io_thread_fn
    at linc.c line 394
  • #13 g_thread_create_proxy
    at gthread.c line 582
  • #14 start_thread
    at pthread_create.c line 261
  • #15 ??
    from /lib/libc.so.6 






Comment 1


Vincent Untz





          2006-01-25 07:43:43 UTC
        



Looks similar to bug 328512.






Comment 2


Michael Meeks





          2006-01-26 10:33:57 UTC
        



sure - it's a dup: though why this starts happening now I have no idea.

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