Removing modem monitor applet from panel causes a crash

[Adam Pond]

Binary package hint: gnome-applets

Severity: medium

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.

[Daniel Holbach (dholbach)]

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
#0 0x00002aaaabf0e094 in waitpid () from /lib/libpthread.so.0
#1 0x00002aaaaad2a6d7 in libgnomeui_segv_handle (signum=11)
    at gnome-ui-init.c:820
#2 <signal handler called>
#3 dispatch_directives (applet=0x5b30b0) at modem-applet.c:564
#4 0x00002aaaabc95a7b in g_timeout_dispatch (source=0x687c00, callback=0,
    user_data=0x20) at gmain.c:3292
#5 0x00002aaaabc93bdd in IA__g_main_context_dispatch (context=0x562b70)
    at gmain.c:1916
#6 0x00002aaaabc96ea5 in g_main_context_iterate (context=0x562b70, block=1,
    dispatch=1, self=<value optimized out>) at gmain.c:2547
#7 0x00002aaaabc9716a in IA__g_main_loop_run (loop=0x5741f0) at gmain.c:2751
#8 0x00002aaaadbec395 in bonobo_main () from /usr/lib/libbonobo-2.so.0
#9 0x00002aaaadbea861 in bonobo_generic_factory_main_timeout ()
   from /usr/lib/libbonobo-2.so.0
#10 0x00002aaaaabcb614 in panel_applet_factory_main_closure (
    iid=0x4056d0 "OAFIID:GNOME_ModemApplet_Factory",
    applet_type=<value optimized out>, closure=<value optimized out>)
    at /build/buildd/gnome-panel-2.14.1/./libpanel-applet/panel-applet.c:1757
#11 0x00000000004048de in main (argc=<value optimized out>,
    argv=0x7fffffe01038) at modem-applet.c:1135
#12 0x00002aaaac03449b in __libc_start_main () from /lib/libc.so.6
#13 0x0000000000402f4a in _start () at ../sysdeps/x86_64/elf/start.S:113

Thread 1 (Thread 46912581318640 (LWP 7403)):
#0 0x00002aaaabf0e094 in waitpid () from /lib/libpthread.so.0
No symbol table info available.
#1 0x00002aaaaad2a6d7 in libgnomeui_segv_handle (signum=11)
    at gnome-ui-init.c:820
 estatus = 0
 in_segv = 1
 sa = {__sigaction_handler = {sa_handler = 0, sa_sigaction = 0},
  sa_mask = {__val = {8962473, 140737486259280, 64, 33, 0, 140737486259312,
      160, 129, 7, 8962550, 140737486259576, 7119232, 8973104, 6988608,
      46912508490209, 6408624}}, sa_flags = -1406875584, sa_restorer = 0x2}
 pid = -512
#2 <signal handler called>
No symbol table info available.
#3 dispatch_directives (applet=0x5b30b0) at modem-applet.c:564
 priv = (ModemAppletPrivate *) 0x5b33b0
 directive = <value optimized out>
 doc = <value optimized out>
 dir = <value optimized out>
 elem = (GSList *) 0x0
#4 0x00002aaaabc95a7b in g_timeout_dispatch (source=0x687c00, callback=0,
    user_data=0x20) at gmain.c:3292
 timeout_source = <value optimized out>
#5 0x00002aaaabc93bdd in IA__g_main_context_dispatch (context=0x562b70)
    at gmain.c:1916
No locals.
#6 0x00002aaaabc96ea5 in g_main_context_iterate (context=0x562b70, block=1,
    dispatch=1, self=<value optimized out>) at gmain.c:2547
 got_ownership = <value optimized out>
 max_priority = 2147483647
 timeout = 40
 some_ready = 1
 nfds = <value optimized out>
 allocated_nfds = <value optimized out>
 fds = <value optimized out>
 __PRETTY_FUNCTION__ = "g_ma...

[Adam Pond (adpond)]

The percentage of CPU that may have been because I am on a relatively low-spec'd computer.

I'm sure that 100% of the CPU was not being used by the applet, but there was some CPU being used which I thought was odd, and was the catalyst to me finding the bug.

Thanks for confirming.

[Sebastien Bacher (seb128)]

I've forwarded it upstream: http://bugzilla.gnome.org/show_bug.cgi?id=343038

[Jérôme Guelfucci (jerome-guelfucci-deactivatedaccount)]

Do you still have this issue with the latest stable release of Ubuntu ?