GNOME Bugzilla – Bug 135464
Invoking disconnect command crashes ALL applets
Last modified: 2005-01-09 07:21:09 UTC
Hi! I use debian sarge together with gnome 2.4. Kernel is 2.4.22. Glibc is 2.3.2.ds1-11. Gnome applets is 2.4.0-4. If I invoke connect command clicking on modemlights applet (command is pon in my case) and then invoke disconnect command (poff) BEFORE the instant when connection is esteblished (when modemlight is yellow but not green yet) ALL running gnome-applets crash. This is debian bug #220796. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=220796 Thanks for your work!
Is this fully reproduceable, also with newer versions, can you try and provide us a stacktrace of some applets that are running ?
Created attachment 24795 [details] stacktrace for modemlights applet
That isn't a stacktrace, although i understand that 'strace' and stracktrace might look related to each other. A stacktrace can be obtained by running the applet within gdb. Then add the applet from menu in panel. Make it crash and type 'where' in gdb.
Hi. You can find detailed instructions on how to obtain a stack trace here: http://bugzilla.gnome.org/getting-traces.cgi Notes: Changed priority to high
Created attachment 24827 [details] backtrace
Excellent. Thank you. I will now reopen this bug.
The stacktrace doesn't contain line numbers and is thus not very helpful (i doubt if it is helpful even with line numbers but still). Could you try upgrading to gnome 2.4.2, or an very new version from the 2.5.x serie and see if this is still reproducable
The same problem is reproducable with gnome-applets 2.4.2-2 from debian unstable.
Serge could you try doing the following: Download a new source tree of gnome-applets. Compile. (you don't need to do make install so don't worry about screwing up your nice and clean debian install). Go into the 'modemlights' type 'gdb ./modemlights_applet2' after that 'run' Wait a few seconds till the applet runs within gdb. (probably indicated by the following lines showing up) - Bonobo accessibility support initialized GTK Accessibility Module initialized Atk Accessibilty bridge initialized - After this runs. Add an applet from the panel context menu. This will invoke an instance from the running process. Reproduce the crash and type 'where'. The applets are compiled with debug symbols on so this stacktrace will probably provide more information, which is the reason i am asking you to do this ;). You also might want to attach the scripts you use to this bug. (Obviously removing personal information if there is any). Thank you for helping us and trying to get this nailed.
OK, I will do it in several days. I just discovered that when ALL applets receive SIGTERM and die bonobo-activation-server also receives SIGTERM.
$ gdb modemlights_applet2 GNU gdb 5.3-debian Copyright 2002 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-linux"... (gdb) run Starting program: /usr/lib/gnome-panel/modemlights_applet2 [New Thread 16384 (LWP 32159)] Program received signal SIGTERM, Terminated.
+ Trace 44652
Thread 16384 (LWP 32159)
Continuing. Cannot find user-level thread for LWP 32159: generic error
This is for gnome-applets 2.4.2. modemlights.c:1526 is PANEL_APPLET_BONOBO_FACTORY ("OAFIID:GNOME_ModemLightsApplet_Factory",
This is quite odd. It would be nice if Kevin or Mark commented on this. I have no idea what is going on.
Do you have any ideas about the bug? Can I help somehow?
I think the best thing to do is wait till 2.6, update your gnome platform to 2.6 and check if this is still valid. If so we need to investigate this. 2.6 will be released within a month probably so that is quite soon. I have no further clue about this at this moment, sorry.
Dennis: Thanks for helping Serge track down some additional information for the maintainers. For future reference, if you don't know what additional kind of information to get from the reporter, the correct thing to do is to reopen the bug. Otherwise, the maintainers tend to concentrate on bugs that might have enough information for them to solve (which tends to exclude bugs marked as NEEDINFO, or at least drop them in priority). Serge: What compiling flags did you use when building? It appears that you either left off the -g flag (which is the flag needed to get debugging symbols), or else you strip'ed the binaries of the debugging symbols. Is there any chance you could double check to see which of these two happened so that we can get a stack trace with debugging symbols? The crash appears to be occurring in gtk+ functions, so debugging symbols may be critical. I would try to duplicate, but I have no modem or dialup connection. Having a single applet crash take down all other applets to crash really ought to be looked into, so I'm reopening and adding the TARGET2.6.0 keyword. Someone let me know if I'm in error to do so.
It would be great if Serge could make an 2.5.x build and see if it's reproduceable with those. Elijah Newren, thanks for heads up, you're right on this matter.
Backtrace with more debuginfo (for 2.4.2) (gdb) cont Continuing. Program received signal SIGTERM, Terminated.
+ Trace 44949
Thread 16384 (LWP 5607)
Just for case: when I start the applet from terminal (under gdb for example) crash happens only with this applet, not with all running applets. If applets is started by gnome panel then all applets crashes.
I have used above libglib2.0-dbg 2.2.3-1 from debian/sarge.
If you're capable and willing to do so. Could you try to upgrade to the latest 2.5.x platform and check if it's still valid there ?
Serge, can you upgrade to 2.6 and verify if this is still happening ? Thank you!
Serge, could you please report back to us ? Thanks!
The bug still presents with debian 2.6.2.1-1 package.
Hmm, I never saw this when using the modemlights applet. But I don't use pon/poff, I use custom scripts I wrote many years ago. The debian bug report talks about it failing with this incantation: pty '(sleep 10; kill -STOP $$; sleep 1; kill -CONT $$) & exec ssh -x -t -enone -lmyusername myserver.domain.com /usr/sbin/pppd' And talks about it specifically failing when using PTYs. I can think of reasons it might fail. I don't understand how it kills all the applets though, unless it can somehow take out bonobo. I'll try and replicate this later on.
modemlights was rewritten for G10.