Thanks John. Well, for your crash, it looks like your crash is related to passing a menu message along dbus (see below). This isn't terribly diagnostic, but my best guess would be that the problem is occurring when indicator- weather is updating it appearance due to some change in weather conditions. Whether it's just changing the icon, or changing the displayed temperature (if that option is enabled), both, or perhaps some other appearance change, is not clear.
It's hard to know if the problem is in the Python code, some Python extension, libdbusmenu itself, or possibly libgobject (I tend to doubt the latter, tho'). Ideally, libdbusmenu should catch a bad message or invalid reference and return an error rather than letting a segfault occur. I imagine libdbusmenu is "newer-ish", so it might not be as thoroughly tested as it eventually will be. Ha! As I was writing this, I noticed the indicator weather icon update. First, both the icon and the temp briefly disappeared, and then just the icon came back with definitely a different icon than had just been there. The new icon was shifted right, however, because ONLY the new icon appeared, not the temperature (so I don't know if the temperature changed or stayed the same -- although restarting the indicator shows the same temperature). At any rate, the icon then disappeared and a crash report was generated, which can be found under Bug #908513. It was a SIGABRT rather than a SIGSEGV, but I these two crash might be related nonetheless (I'll do further forensics on my own crash momentarily). I should note also that now, after restarting indicator-weather, my weather indicator is now the (relatively meaningless) orange / white indicator (see attached screenshot, although now at 1:19am CST the indicator looks normal again). [Yeah, the screen capture app Shutter isn't showing up in the indicator area either -- I had to use PrintScreen button. Shutter's disappeared a good bit before, too. So, this may all just be related to more generalized problems with the relatively new indicator API in Unity. Just speculation on my part, however.] Back to John's crash: Here's the output from the stack backtrace that lead to my comments above: root@s3:~# apport-retrace -g _usr_bin_indicator-weather.1000.crash GNU gdb (Ubuntu/Linaro 7.3-0ubuntu2) 7.3-2011.08 Copyright (C) 2011 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". For bug reporting instructions, please see: <http://bugs.launchpad.net/gdb-linaro/>. Reading symbols from /usr/bin/python2.7...(no debugging symbols found)...done. warning: core file may not match specified executable file. [New LWP 1884] [New LWP 3863] [New LWP 1937] [New LWP 1939] warning: Can't read pathname for load map: Input/output error. [Thread debugging using libthread_db enabled] Core was generated by `/usr/bin/python /usr/bin/indicator-weather'. Program terminated with signal 11, Segmentation fault. #0 0x00007f10ef7f954c in g_type_check_instance_cast () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 (gdb) bt #0 0x00007f10ef7f954c in g_type_check_instance_cast () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #1 0x00007f10e531226c in ?? () from /usr/lib/libdbusmenu-glib.so.4 #2 0x00007f10e5313bb8 in ?? () from /usr/lib/libdbusmenu-glib.so.4 #3 0x00007f10ef514a5d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x00007f10ef515258 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x00007f10ef515792 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x00007f10eca02db7 in gtk_main () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 #7 0x00007f10ed0b6056 in ?? () from /usr/lib/python2.7/dist-packages/gtk-2.0/gtk/_gtk.so #8 0x00000000004b7114 in PyEval_EvalFrameEx () #9 0x00000000004b6d77 in PyEval_EvalFrameEx () #10 0x00000000004bcd2d in PyEval_EvalCodeEx () #11 0x00000000004bd802 in PyEval_EvalCode () #12 0x00000000004dcc22 in ?? () #13 0x00000000004dd7e4 in PyRun_FileExFlags () #14 0x00000000004de2ee in PyRun_SimpleFileExFlags () #15 0x00000000004ee6dd in Py_Main () #16 0x00007f10f075c30d in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6 #17 0x000000000041cb69 in _start () (gdb) EOF ** Attachment added: "Screenshot at 2011-12-25 01:10:58.png" https://bugs.launchpad.net/weather-indicator/+bug/821832/+attachment/2646307/+files/Screenshot%20at%202011-12-25%2001%3A10%3A58.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/821832 Title: indicator-weather disappears from panel randomly To manage notifications about this bug go to: https://bugs.launchpad.net/weather-indicator/+bug/821832/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
