[Bug 632066] Re: systray.py crashed with SIGSEGV in g_type_module_use()
** Tags added: utopic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/632066 Title: systray.py crashed with SIGSEGV in g_type_module_use() To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/632066/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 632066] Re: systray.py crashed with SIGSEGV in g_type_module_use()
Still happening at 14.04. Managed to do apport-retrace and run gdb. This is what the stack trace looks like now. It may be another bug is hiding the first one. info (gdb)Auto-loading safe path done. warning: core file may not match specified executable file. [New LWP 6922] [New LWP 7063] [New LWP 7064] [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/i386-linux-gnu/libthread_db.so.1. Traceback (most recent call last): File /tmp/apport_sandbox_XIhMcU/usr/lib/debug/usr/lib/i386-linux-gnu/libstdc++.so.6.0.19-gdb.py, line 63, in module from libstdcxx.v6.printers import register_libstdcxx_printers ImportError: No module named 'libstdcxx' Core was generated by `/usr/bin/python /usr/bin/hp-systray -x'. Program terminated with signal SIGSEGV, Segmentation fault. #0 setup_context (registry=synthetic pointer, module=synthetic pointer, lineno=synthetic pointer, filename=synthetic pointer, stack_level=1, stack_level@entry=16) at ../Python/_warnings.c:449 449 ../Python/_warnings.c: No such file or directory. (gdb) bt #0 setup_context (registry=synthetic pointer, module=synthetic pointer, lineno=synthetic pointer, filename=synthetic pointer, stack_level=1, stack_level@entry=16) at ../Python/_warnings.c:449 #1 do_warn.29441 (message=message@entry=0xb6a40020, category=category@entry=0xb3b5f78c, stack_level=stack_level@entry=1) at ../Python/_warnings.c:594 #2 0x081f34cf in PyErr_WarnEx (category=category@entry=0xb3b5f78c, text=text@entry=0x97516e0 /usr/lib/i386-linux-gnu/pango/1.8.0/modules/pango-basic-fc.so: cannot open shared object file: No such file or directory, stack_level=stack_level@entry=1) at ../Python/_warnings.c:720 #3 0xb4612aec in _log_func (log_domain=log_domain@entry=0xb3d35a56 Pango, log_level=log_level@entry=G_LOG_LEVEL_WARNING, message=message@entry=0x97516e0 /usr/lib/i386-linux-gnu/pango/1.8.0/modules/pango-basic-fc.so: cannot open shared object file: No such file or directory, user_data=user_data@entry=0xb3b5f78c) at /build/buildd/pygobject-2-2.28.6/gobject/gobjectmodule.c:2316 #4 0xb5f6f2f7 in g_logv (log_domain=log_domain@entry=0xb3d35a56 Pango, log_level=log_level@entry=G_LOG_LEVEL_WARNING, format=format@entry=0xb3d40925 %s, args=args@entry=0xbff769ec \300\027u\t) at /build/buildd/glib2.0-2.40.0/./glib/gmessages.c:1012 #5 0xb5f6f523 in g_log (log_domain=log_domain@entry=0xb3d35a56 Pango, log_level=log_level@entry=G_LOG_LEVEL_WARNING, ---Type return to continue, or q return to quit--- format=format@entry=0xb3d40925 %s) at /build/buildd/glib2.0-2.40.0/./glib/gmessages.c:1071 #6 0xb3d1b7d6 in pango_module_load (module=0x9747ce0) at /build/buildd/pango1.0-1.36.3/./pango/modules.c:225 #7 0xb4b1bdfe in g_type_module_use (module=0x9747ce0) at /build/buildd/glib2.0-2.40.0/./gobject/gtypemodule.c:244 #8 0xb3d1b89b in pango_engine_pair_get_engine (pair=0x973da60) at /build/buildd/pango1.0-1.36.3/./pango/modules.c:321 #9 0xb3d1b967 in append_engines (engine_list=engine_list@entry=0xbff7704c, pair_list=optimised out) at /build/buildd/pango1.0-1.36.3/./pango/modules.c:810 #10 0xb3d1c013 in pango_map_get_engines (map=0x974f408, script=script@entry=PANGO_SCRIPT_COMMON, exact_engines=exact_engines@entry=0xbff77048, fallback_engines=fallback_engines@entry=0xbff7704c) at /build/buildd/pango1.0-1.36.3/./pango/modules.c:862 #11 0xb3d1fe8c in get_engines (fallback_engines=0xbff7704c, exact_engines=0xbff77048, script=optimised out, lang=optimised out, context=optimised out) at /build/buildd/pango1.0-1.36.3/./pango/pango-context.c:1161 #12 get_shaper_and_font (state=state@entry=0xbff76b9c, wc=wc@entry=9679, shape_engine=shape_engine@entry=0xbff76b48, font=font@entry=0xbff76b4c) at /build/buildd/pango1.0-1.36.3/./pango/pango-context.c:1250 ---Type return to continue, or q return to quit--- #13 0xb3d2018c in itemize_state_process_run (state=state@entry=0xbff76b9c) at /build/buildd/pango1.0-1.36.3/./pango/pango-context.c:1485 #14 0xb3d211f7 in pango_itemize_with_base_dir (context=0x97479a0, base_dir=base_dir@entry=PANGO_DIRECTION_LTR, text=0x9748148 ●, start_index=0, length=length@entry=3, attrs=attrs@entry=0x973a1a0, cached_iter=cached_iter@entry=0x973ccc0) at /build/buildd/pango1.0-1.36.3/./pango/pango-context.c:1590 #15 0xb3d28d5f in pango_layout_check_lines (layout=optimised out) at /build/buildd/pango1.0-1.36.3/./pango/pango-layout.c:3998 #16 0xb3d2a116 in pango_layout_get_unknown_glyphs_count ( layout=layout@entry=0xb2f056a8) at /build/buildd/pango1.0-1.36.3/./pango/pango-layout.c:1281 #17 0xb3fd4130 in find_invisible_char (widget=widget@entry=0x973a968) at /build/buildd/gtk+2.0-2.24.23/gtk/gtkentry.c:2259 #18 0xb3fd7c03 in gtk_entry_init (entry=0x973a968) at /build/buildd/gtk+2.0-2.24.23/gtk/gtkentry.c:2282 #19 0xb4b18b43 in g_type_create_instance
[Bug 632066] Re: systray.py crashed with SIGSEGV in g_type_module_use()
Just upgraded to 13.10 and am getting this on every login. It was working fine on 13.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/632066 Title: systray.py crashed with SIGSEGV in g_type_module_use() To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/632066/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 632066] Re: systray.py crashed with SIGSEGV in g_type_module_use()
Can someone at HP have a look? Seems to be a problem with Ubuntu 13.10 which was released yesterday. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/632066 Title: systray.py crashed with SIGSEGV in g_type_module_use() To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/632066/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 632066] Re: systray.py crashed with SIGSEGV in g_type_module_use()
Precise Beta 1 and I'm still affected by this, typically whenever I change the theme. I actually got some help on how to run hp-systray from gdb, and got a backtrace (triggered the crash simply by switching from Ambiance to Radiance in Appearance). Let me know if this helps any, and if there's anything else I can do. ** Attachment added: gdb-hp-systray.txt https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/632066/+attachment/2821468/+files/gdb-hp-systray.txt ** Tags added: precise -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/632066 Title: systray.py crashed with SIGSEGV in g_type_module_use() To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/632066/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 632066] Re: systray.py crashed with SIGSEGV in g_type_module_use()
At the moment I'm currently affected by bug 908805 on Precise, where for me Nautilus crashes just about every single time I start it up, which temporarily reverts the theme back to standard GNOME and seems to reliably reproduce this hplip crash. After I reboot my system, I'll try the above commands again and try to capture the terminal output. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/632066 Title: systray.py crashed with SIGSEGV in g_type_module_use() To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/632066/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 632066] Re: systray.py crashed with SIGSEGV in g_type_module_use()
Yep, I can reliably reproduce this and just got another crash. For me, all I have to do is run the commands as given in comment 11 (or not, since it occurs during normal usage as well), open Nautilus, and wait or go into the Ubuntu One folder. Nautilus then crashes a few seconds later thanks to bug 908805, and that in turn causes this bug to occur. I strongly suspect it has something to do with the hplip-systray indicator being somehow unable to cope with theme changes. Attached is my terminal output. ** Attachment added: terminal output.txt https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/632066/+attachment/2656488/+files/terminal%20output.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/632066 Title: systray.py crashed with SIGSEGV in g_type_module_use() To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/632066/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 632066] Re: systray.py crashed with SIGSEGV in g_type_module_use()
I'm now testing Precise and getting this problem every now and then, seemingly at random. The annoying part about this bug is that I have no idea how to reproduce it, though I'm currently suspecting changing the theme could be part of the problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/632066 Title: systray.py crashed with SIGSEGV in g_type_module_use() To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/632066/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 632066] Re: systray.py crashed with SIGSEGV in g_type_module_use()
Can also be another problem in qt4-x11, adding qt4-x11 package ... ** Also affects: qt4-x11 (Ubuntu) Importance: Undecided Status: New ** Changed in: qt4-x11 (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/632066 Title: systray.py crashed with SIGSEGV in g_type_module_use() To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/632066/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 632066] Re: systray.py crashed with SIGSEGV in g_type_module_use()
A possible cause is bug 805303, which should be fixed. Can you run the following commands in a terminal window: pkill -f hp-systray LIBOVERLAY_SCROLLBAR=0 hp-systray Does hp-systray stay stable now? Does your desktop stay stable when you are running vlc? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/632066 Title: systray.py crashed with SIGSEGV in g_type_module_use() To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/632066/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 632066] Re: systray.py crashed with SIGSEGV in g_type_module_use()
I've been running hp-systray from a terminal since the last crash to try and catch any error messages (couldn't get it to run from gdb), but it did not crash since then. I've just killed that and now I'm running it using the commands you provided above...so far everything seems okay, but I cannot say for sure since I still have no idea how to reliably reproduce this crash. As for vlc, I don't have that installed, and being in the US I am hesitant to install these types of things due to potential software patent issues with the codecs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/632066 Title: systray.py crashed with SIGSEGV in g_type_module_use() To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/632066/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 632066] Re: systray.py crashed with SIGSEGV in g_type_module_use()
...sorry, but I just had this crash happen again this morning while changing my status in Empathy. This bug is still alive and well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/632066 Title: systray.py crashed with SIGSEGV in g_type_module_use() To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/632066/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 632066] Re: systray.py crashed with SIGSEGV in g_type_module_use()
Forgot to note that during the weekend I've been keeping my system fully up to date and had it rebooted a couple of times. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/632066 Title: systray.py crashed with SIGSEGV in g_type_module_use() To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/632066/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 632066] Re: systray.py crashed with SIGSEGV in g_type_module_use()
Can you please do all updates (on the command line sudo apt-get update; sudo apt-get dist-upgrade or with Update Manager), log out and log in again, and then check again? Several bugs got fixed to solve this problem. ** Changed in: hplip (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/632066 Title: systray.py crashed with SIGSEGV in g_type_module_use() To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/632066/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 632066] Re: systray.py crashed with SIGSEGV in g_type_module_use()
I have just rerun Update Manager to get all the latest updates and logged out/in, as you requested. But these crashes are difficult to reproduce and seem to happen completely at random. As such, I have not had a crash just yet, but I will come back once I see one. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/632066 Title: systray.py crashed with SIGSEGV in g_type_module_use() To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/632066/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 632066] Re: systray.py crashed with SIGSEGV in g_type_module_use()
Just happened again in Oneiric Beta 2 while browsing wallpapers in System Settings, causing my HPLIP tray icon to disappear. I'd say this is probably the most common crash I'm seeing on my system now. hplip version 3.11.7-1ubuntu3. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/632066 Title: systray.py crashed with SIGSEGV in g_type_module_use() To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/632066/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 632066] Re: systray.py crashed with SIGSEGV in g_type_module_use()
Still present in Oneiric Beta 1. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/632066 Title: systray.py crashed with SIGSEGV in g_type_module_use() To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/632066/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 632066] Re: systray.py crashed with SIGSEGV in g_type_module_use()
** Visibility changed to: Public ** Also affects: hplip Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/632066 Title: systray.py crashed with SIGSEGV in g_type_module_use() To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/632066/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
