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 343038 - Removing modem monitor applet from panel causes a crash
Removing modem monitor applet from panel causes a crash
Status: RESOLVED INCOMPLETE
Product: gnome-applets
Classification: Other
Component: modemlights
2.14.x
Other Linux
: Normal major
: ---
Assigned To: gnome-applets Maintainers
gnome-applets Maintainers
: 325532 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-05-26 16:44 UTC by Sebastien Bacher
Modified: 2011-01-07 03:54 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description Sebastien Bacher 2006-05-26 16:44:26 UTC
That bug has been opened on https://launchpad.net/distros/ubuntu/+source/gnome-applets/+bug/46165

"Description of the crash:
I had accidentally added several modem applets to the top panel due to a lag between when I hit add and when I received an indication that something happened. I later noticed that the CPU was running at 100%, and after noticing that the modem applets were taking up CPU, I tried to remove one. Removing each one from the panel causes a crash.

Steps to reproduce:
1. Add 2 modem monitor applets to the top panel.
2. Right click on one and try to remove it.
3. Crash.
...
They don't ues 100% CPU from me, but I get a applet crash too, backtrace:

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

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 46912581318640 (LWP 7403)]
0x00002aaaabf0e094 in waitpid () from /lib/libpthread.so.0

Thread 1 (Thread 46912581318640 (LWP 7403))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 libgnomeui_segv_handle
    at gnome-ui-init.c line 820
  • #2 <signal handler called>
  • #3 dispatch_directives
    at modem-applet.c line 564
  • #4 g_timeout_dispatch
    at gmain.c line 3292
  • #5 IA__g_main_context_dispatch
    at gmain.c line 1916
  • #6 g_main_context_iterate
    at gmain.c line 2547
  • #7 IA__g_main_loop_run
    at gmain.c line 2751
  • #8 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #9 bonobo_generic_factory_main_timeout
    from /usr/lib/libbonobo-2.so.0
  • #10 panel_applet_factory_main_closure
    at /build/buildd/gnome-panel-2.14.1/./libpanel-applet/panel-applet.c line 1757
  • #11 main
    at modem-applet.c line 1135
  • #12 __libc_start_main
    from /lib/libc.so.6
  • #13 _start
    at ../sysdeps/x86_64/elf/start.S line 113
  • #0 waitpid
    from /lib/libpthread.so.0

Comment 1 Danielle Madeley 2006-08-07 06:05:12 UTC
*** Bug 325532 has been marked as a duplicate of this bug. ***
Comment 2 Fabio Durán Verdugo 2010-11-25 03:09:23 UTC
I can't reproduce.

This bug was reported against a version which is not supported any more. Developers are no longer working on this version so there will not be any bug fixes for it.
Can you please check again if the issue you reported here still happens in a recent version of GNOME and update this report by adding a comment and adjusting the 'Version' field?

Again thank you for reporting this and sorry that it could not be fixed for the version you originally used here.

Without feedback this report will be closed as INCOMPLETE after 6 weeks.