[Dx-packages] [Bug 1286580] Re: unity-panel-service crashed with SIGSEGV in _gtk_marshal_BOOLEAN__BOXED()
Hm, to clarity: "The indicator-session opens, and often the menu stays stuck open for a while."...as the panel crashes. That's how I first know the crash has happened again What I wanted to convey was that the rightmost indicator menu opens, and then the crash freezes it; my continued right-arrow inpuds. Not every time. Whether that means that particular indicator is involved, or the next one, date/time, that never opens--or whether that means anything--I am not knowledgeable enough to say. Thank you. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1286580 Title: unity-panel-service crashed with SIGSEGV in _gtk_marshal_BOOLEAN__BOXED() Status in Unity: New Status in “unity” package in Ubuntu: New Bug description: I tried to open the panel menus. Probably by keyboard first. The panel froze & crashed. No unusual circumstances that I noticed. I don't know if this will be relevant, but: since recently trying KDE packages on this machine, KDE's settings seemed to have fouled up Unity's, when I returned. Many of the indicator icons were wrong or missing. Attempts to clear the settings, remove KDE packages, and restart, didn't make any difference. But after this crash, weeks later, the usual icons were finally restored. Seems strange. Thanks. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: unity-services 7.1.2+13.10.20131014.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4 Uname: Linux 3.11.0-18-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sat Mar 1 00:14:03 2014 ExecutablePath: /usr/lib/unity/unity-panel-service MarkForUpload: True ProcCmdline: /usr/lib/unity/unity-panel-service ProcEnviron: PATH=(custom, no user) LANGUAGE=en_US XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f8097fa93a6:mov0x10(%rdx),%ecx PC (0x7f8097fa93a6) ok source "0x10(%rdx)" (0x0010) not located in a known VMA region (needed readable region)! destination "%ecx" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libido3-0.1.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: unity-panel-service crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: Upgraded to saucy on 2014-01-16 (43 days ago) UserGroups: adm cdrom dip lpadmin nopasswdlogin plugdev sambashare sudo wireshark To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1286580/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1286580] Re: unity-panel-service crashed with SIGSEGV in _gtk_marshal_BOOLEAN__BOXED()
I have continued to get this crash, periodically. I think the circumstance that triggers it is, generally at least: 1. opening the app menus in the panel via keyboard shortcuts, then 2. hitting left-arrow to wrap around and access the indicator menus Doing the above does not reproduce the crash every time. I have not seen it happen, I think, when I hit right-arrow, to start on the leftmost indicator applet. Just the left-to-wrap-right move. The indicator-session opens, and often the menu stays stuck open for a while. Incidentally, this behavior is a workaround for the loss of HUD access to indicator menus. (I suppose it may be what I did before the HUD arrived; I don't remember clearly.) Thanks, Marco! -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1286580 Title: unity-panel-service crashed with SIGSEGV in _gtk_marshal_BOOLEAN__BOXED() Status in Unity: New Status in “unity” package in Ubuntu: New Bug description: I tried to open the panel menus. Probably by keyboard first. The panel froze & crashed. No unusual circumstances that I noticed. I don't know if this will be relevant, but: since recently trying KDE packages on this machine, KDE's settings seemed to have fouled up Unity's, when I returned. Many of the indicator icons were wrong or missing. Attempts to clear the settings, remove KDE packages, and restart, didn't make any difference. But after this crash, weeks later, the usual icons were finally restored. Seems strange. Thanks. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: unity-services 7.1.2+13.10.20131014.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4 Uname: Linux 3.11.0-18-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sat Mar 1 00:14:03 2014 ExecutablePath: /usr/lib/unity/unity-panel-service MarkForUpload: True ProcCmdline: /usr/lib/unity/unity-panel-service ProcEnviron: PATH=(custom, no user) LANGUAGE=en_US XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f8097fa93a6:mov0x10(%rdx),%ecx PC (0x7f8097fa93a6) ok source "0x10(%rdx)" (0x0010) not located in a known VMA region (needed readable region)! destination "%ecx" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libido3-0.1.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: unity-panel-service crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: Upgraded to saucy on 2014-01-16 (43 days ago) UserGroups: adm cdrom dip lpadmin nopasswdlogin plugdev sambashare sudo wireshark To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1286580/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1286580] Re: unity-panel-service crashed with SIGSEGV in _gtk_marshal_BOOLEAN__BOXED()
** Information type changed from Private to Public -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1286580 Title: unity-panel-service crashed with SIGSEGV in _gtk_marshal_BOOLEAN__BOXED() Status in Unity: New Status in “unity” package in Ubuntu: New Bug description: I tried to open the panel menus. Probably by keyboard first. The panel froze & crashed. No unusual circumstances that I noticed. I don't know if this will be relevant, but: since recently trying KDE packages on this machine, KDE's settings seemed to have fouled up Unity's, when I returned. Many of the indicator icons were wrong or missing. Attempts to clear the settings, remove KDE packages, and restart, didn't make any difference. But after this crash, weeks later, the usual icons were finally restored. Seems strange. Thanks. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: unity-services 7.1.2+13.10.20131014.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4 Uname: Linux 3.11.0-18-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sat Mar 1 00:14:03 2014 ExecutablePath: /usr/lib/unity/unity-panel-service MarkForUpload: True ProcCmdline: /usr/lib/unity/unity-panel-service ProcEnviron: PATH=(custom, no user) LANGUAGE=en_US XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f8097fa93a6:mov0x10(%rdx),%ecx PC (0x7f8097fa93a6) ok source "0x10(%rdx)" (0x0010) not located in a known VMA region (needed readable region)! destination "%ecx" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libido3-0.1.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: unity-panel-service crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: Upgraded to saucy on 2014-01-16 (43 days ago) UserGroups: adm cdrom dip lpadmin nopasswdlogin plugdev sambashare sudo wireshark To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1286580/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1054321] Re: indicator-datetime-service crashed with signal 5 in g_wakeup_new()
I don't recall this indicator crashing in quite some time, so letting this expire seems fine. Thanks. -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1054321 Title: indicator-datetime-service crashed with signal 5 in g_wakeup_new() Status in “indicator-datetime” package in Ubuntu: Incomplete Bug description: Upgraded to indicator-datetime 12.10.1-0ubuntu1 today -- this crash under that version was the first time this process has ever crashed on my machines. No visible cause, or effect. it has recurred once, over a few day's span. The most notable thing I can see about the crash is over 1000 threads in the thread stacktrace. This was first filed as bug 1053830, but apparently something in the data there wasn't right. The core dump was 65M, and the LP message was "size does not fit in an int", so I'm guessing that was too big. This is a re-submission without the core dump; I cut it out of the crash file. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: indicator-datetime 12.10.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-15.22-generic 3.5.4 Uname: Linux 3.5.0-15-generic x86_64 ApportVersion: 2.5.2-0ubuntu4 Architecture: amd64 Date: Fri Sep 21 01:02:07 2012 ExecutablePath: /usr/lib/indicator-datetime/indicator-datetime-service ProcCmdline: /usr/lib/indicator-datetime/indicator-datetime-service ProcCwd: / ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=en_US.UTF-8 Signal: 5 SourcePackage: indicator-datetime StacktraceTop: g_wakeup_new () at /build/buildd/glib2.0-2.33.14/./glib/gwakeup.c:163 g_cancellable_make_pollfd (cancellable=cancellable@entry=0x7f206c0022c0, pollfd=pollfd@entry=0x7f20564d05e0) at /build/buildd/glib2.0-2.33.14/./gio/gcancellable.c:406 socket_source_new (cancellable=0x7f206c0022c0, condition=(G_IO_IN | G_IO_ERR | G_IO_HUP), socket=0x7f206c003a80) at /build/buildd/glib2.0-2.33.14/./gio/gsocket.c:3270 g_socket_create_source (socket=0x7f206c003a80, condition=condition@entry=(G_IO_IN | G_IO_ERR | G_IO_HUP), cancellable=cancellable@entry=0x7f206c0022c0) at /build/buildd/glib2.0-2.33.14/./gio/gsocket.c:3335 _g_socket_read_with_control_messages (socket=0x7f206c003a80, buffer=0x7f205400aa00, count=16, messages=0x7f206c00f950, num_messages=0x7f206c00f958, io_priority=, cancellable=0x7f206c0022c0, callback=0x7f207f8f5620 <_g_dbus_worker_do_read_cb>, user_data=0x7f206c00f8c0) at /build/buildd/glib2.0-2.33.14/./gio/gdbusprivate.c:200 Title: indicator-datetime-service crashed with signal 5 in g_wakeup_new() UpgradeStatus: Upgraded to quantal on 2012-06-14 (98 days ago) UserGroups: adm cdrom dip lpadmin nopasswdlogin plugdev sambashare sudo XsessionErrors: (indicator-multiload:4573): GLib-GIO-CRITICAL **: GApplication subclass 'Main' failed to chain up on ::startup (from start of override function) (eog:6874): EOG-CRITICAL **: eog_list_store_length: assertion `EOG_IS_LIST_STORE (store)' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1054321/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1013171] Re: Many package hooks not ported to python3
This report was already getting too big for Launchpad to handle quickly,
and is all marked fixed. In these cases I'm usually advised to leave
the closed report as it is, and handle the new occurrence with the new
bug. You can certainly put a link to this bug, there, for informational
purposes. Maybe I can get to that.
Thanks!
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-applet in Ubuntu.
Matching subscriptions: dx-packages, dx-packages
https://bugs.launchpad.net/bugs/1013171
Title:
Many package hooks not ported to python3
Status in “apache2” package in Ubuntu:
Fix Released
Status in “apport” package in Ubuntu:
Fix Released
Status in “apport-symptoms” package in Ubuntu:
Fix Released
Status in “bluez” package in Ubuntu:
Fix Released
Status in “cairo-dock” package in Ubuntu:
Fix Released
Status in “chromium-browser” package in Ubuntu:
Fix Released
Status in “compiz” package in Ubuntu:
Fix Released
Status in “connman” package in Ubuntu:
Fix Released
Status in “dkms” package in Ubuntu:
Fix Released
Status in “gnome-control-center” package in Ubuntu:
Fix Released
Status in “gnome-settings-daemon” package in Ubuntu:
Fix Released
Status in “indicator-applet” package in Ubuntu:
Fix Released
Status in “libatasmart” package in Ubuntu:
Fix Released
Status in “lxpanel” package in Ubuntu:
Fix Released
Status in “mdadm” package in Ubuntu:
Fix Released
Status in “mysql-5.5” package in Ubuntu:
Fix Released
Status in “mythtv” package in Ubuntu:
Fix Released
Status in “nautilus” package in Ubuntu:
Fix Released
Status in “network-manager” package in Ubuntu:
Fix Released
Status in “shadow” package in Ubuntu:
Fix Released
Status in “udisks2” package in Ubuntu:
Fix Released
Status in “unity” package in Ubuntu:
Fix Released
Status in “xdiagnose” package in Ubuntu:
Fix Released
Status in “apache2” source package in Quantal:
Fix Released
Status in “apport” source package in Quantal:
Fix Released
Status in “apport-symptoms” source package in Quantal:
Fix Released
Status in “bluez” source package in Quantal:
Fix Released
Status in “cairo-dock” source package in Quantal:
Fix Released
Status in “chromium-browser” source package in Quantal:
Fix Released
Status in “compiz” source package in Quantal:
Fix Released
Status in “connman” source package in Quantal:
Fix Released
Status in “dkms” source package in Quantal:
Fix Released
Status in “gnome-control-center” source package in Quantal:
Fix Released
Status in “gnome-settings-daemon” source package in Quantal:
Fix Released
Status in “indicator-applet” source package in Quantal:
Fix Released
Status in “libatasmart” source package in Quantal:
Fix Released
Status in “lxpanel” source package in Quantal:
Fix Released
Status in “mdadm” source package in Quantal:
Fix Released
Status in “mysql-5.5” source package in Quantal:
Fix Released
Status in “mythtv” source package in Quantal:
Fix Released
Status in “nautilus” source package in Quantal:
Fix Released
Status in “network-manager” source package in Quantal:
Fix Released
Status in “shadow” source package in Quantal:
Fix Released
Status in “udisks2” source package in Quantal:
Fix Released
Status in “unity” source package in Quantal:
Fix Released
Status in “xdiagnose” source package in Quantal:
Fix Released
Bug description:
Since the description here is the only post that can be updated, it
seems the best place to keep a changing list of packages that need
examining. (The original description was brief, and about only one
package.)
We've fixed all the packages that found in the apt logs uploaded in
the first round of breakage. Now I've tried to review all the other
apport hooks I could find in Quantal. Working from the archive's
Contents file, I got the list of packages that have files under
/usr/share/apport/package-hooks . I skipped the packages already
fixed above, and those that were on my system, during the first round
of breakage, and had no problems. For the rest, I downloaded the
debs, extracted the apport hooks, and ran '2to3' on them. I've posted
patches for every package that broke under python3.
Thanks - Edward Donovan
These packages didn't break during the apport upgrade that forced a
recompile, but they get warnings from the 2to3 tool:
compiz-core
eclipse-platform
gnome-control-center-data
gnome-settings-daemon
grub-common
nautilus-data
unity-common
apache2.2-common
Now we have a bug report for at least gnome-control-center, bug
1018537, which I've duped here. So these may need patching, too.
Hm...from a preliminary look, a number of those use the same code:
if report.has_key("Stacktrace")
which generates an exception with python3. We're probably going to
want to change those to
if "Stacktrace"
