2014-08-21 06:41:23 |
acllos |
bug |
|
|
added bug |
2014-08-21 06:46:59 |
acllos |
description |
after 15/august/2014 updates, radiotray crashes while trying to initialize in the traybar (of mate-desktop).
the crash appears to be gtk2/pygtk related:
in IA__gtk_main () at /build/buildd/gtk+2.0-2.24.24/gtk/gtkmain.c:1270
is a call to GDK_THREADS_LEAVE
if (g_main_loop_is_running (main_loops->data))
{
GDK_THREADS_LEAVE ();
which in turn triggers a call to g_mutex_unlock_slowpath.
it appears that in the last glib(s) the gmutex implementation was rewritten and there's now a check on wathever the mutex was already locked or already unlocked ("Attempt to unlock mutex that was not locked").
so, many superflous but otherwise harmless calls to unlock a gmutex are now causing crashes, and radiotray in combination with the latest pygtk/libgtk2/glib appears to be such a case
ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: radiotray 0.7.3-1ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1
Uname: Linux 3.16.0-9-generic x86_64
ApportVersion: 2.14.6-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Thu Aug 21 07:40:16 2014
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/radiotray
ExecutableTimestamp: 1368129423
InstallationDate: Installed on 2014-08-19 (1 days ago)
InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - Alpha amd64 (20140731)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/radiotray
ProcCwd: /usr/lib/python2.7/dist-packages/radiotray
Signal: 6
SourcePackage: radiotray
StacktraceTop:
raise () from /lib/x86_64-linux-gnu/libc.so.6
abort () from /lib/x86_64-linux-gnu/libc.so.6
g_mutex_unlock_slowpath (mutex=<optimized out>, prev=<optimized out>) at /build/buildd/glib2.0-2.41.2/./glib/gthread-posix.c:1327
IA__gtk_main () at /build/buildd/gtk+2.0-2.24.24/gtk/gtkmain.c:1270
_wrap_gtk_main (self=<optimized out>) at /build/buildd/pygtk-2.24.0/gtk/gtk.override:1240
Title: radiotray crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo |
after 15/august/2014 updates, radiotray crashes while trying to initialize in the traybar (of mate-desktop).
the crash appears to be gtk2/pygtk related:
in IA__gtk_main () at /build/buildd/gtk+2.0-2.24.24/gtk/gtkmain.c:1270
is a call to GDK_THREADS_LEAVE
if (g_main_loop_is_running (main_loops->data))
{
GDK_THREADS_LEAVE ();
which in turn triggers a call to g_mutex_unlock_slowpath.
it appears that in the last glib(s) (2.41+) the gmutex implementation was rewritten and there's now a check on wathever the mutex was already locked or already unlocked ("Attempt to unlock mutex that was not locked").
so, many superflous but otherwise harmless calls to unlock a gmutex are now causing crashes, and radiotray in combination with the latest pygtk/libgtk2/glib appears to be such a case
ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: radiotray 0.7.3-1ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1
Uname: Linux 3.16.0-9-generic x86_64
ApportVersion: 2.14.6-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Thu Aug 21 07:40:16 2014
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/radiotray
ExecutableTimestamp: 1368129423
InstallationDate: Installed on 2014-08-19 (1 days ago)
InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - Alpha amd64 (20140731)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/radiotray
ProcCwd: /usr/lib/python2.7/dist-packages/radiotray
Signal: 6
SourcePackage: radiotray
StacktraceTop:
raise () from /lib/x86_64-linux-gnu/libc.so.6
abort () from /lib/x86_64-linux-gnu/libc.so.6
g_mutex_unlock_slowpath (mutex=<optimized out>, prev=<optimized out>) at /build/buildd/glib2.0-2.41.2/./glib/gthread-posix.c:1327
IA__gtk_main () at /build/buildd/gtk+2.0-2.24.24/gtk/gtkmain.c:1270
_wrap_gtk_main (self=<optimized out>) at /build/buildd/pygtk-2.24.0/gtk/gtk.override:1240
Title: radiotray crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo |
|
2014-08-21 06:47:38 |
acllos |
description |
after 15/august/2014 updates, radiotray crashes while trying to initialize in the traybar (of mate-desktop).
the crash appears to be gtk2/pygtk related:
in IA__gtk_main () at /build/buildd/gtk+2.0-2.24.24/gtk/gtkmain.c:1270
is a call to GDK_THREADS_LEAVE
if (g_main_loop_is_running (main_loops->data))
{
GDK_THREADS_LEAVE ();
which in turn triggers a call to g_mutex_unlock_slowpath.
it appears that in the last glib(s) (2.41+) the gmutex implementation was rewritten and there's now a check on wathever the mutex was already locked or already unlocked ("Attempt to unlock mutex that was not locked").
so, many superflous but otherwise harmless calls to unlock a gmutex are now causing crashes, and radiotray in combination with the latest pygtk/libgtk2/glib appears to be such a case
ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: radiotray 0.7.3-1ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1
Uname: Linux 3.16.0-9-generic x86_64
ApportVersion: 2.14.6-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Thu Aug 21 07:40:16 2014
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/radiotray
ExecutableTimestamp: 1368129423
InstallationDate: Installed on 2014-08-19 (1 days ago)
InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - Alpha amd64 (20140731)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/radiotray
ProcCwd: /usr/lib/python2.7/dist-packages/radiotray
Signal: 6
SourcePackage: radiotray
StacktraceTop:
raise () from /lib/x86_64-linux-gnu/libc.so.6
abort () from /lib/x86_64-linux-gnu/libc.so.6
g_mutex_unlock_slowpath (mutex=<optimized out>, prev=<optimized out>) at /build/buildd/glib2.0-2.41.2/./glib/gthread-posix.c:1327
IA__gtk_main () at /build/buildd/gtk+2.0-2.24.24/gtk/gtkmain.c:1270
_wrap_gtk_main (self=<optimized out>) at /build/buildd/pygtk-2.24.0/gtk/gtk.override:1240
Title: radiotray crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo |
after 15/august/2014 updates, radiotray crashes while trying to initialize in the traybar (of mate-desktop).
the crash appears to be gtk2/pygtk related:
in IA__gtk_main () at /build/buildd/gtk+2.0-2.24.24/gtk/gtkmain.c:1270
is a call to GDK_THREADS_LEAVE
if (g_main_loop_is_running (main_loops->data))
{
GDK_THREADS_LEAVE ();
which in turn triggers a call to g_mutex_unlock_slowpath.
it appears that in the last glib(s) (2.41+) the gmutex implementation was rewritten and there's now a check on whatever the mutex was already locked or already unlocked ("Attempt to unlock mutex that was not locked").
so, many superflous but otherwise harmless calls to unlock a gmutex are now causing crashes, and radiotray in combination with the latest pygtk/libgtk2/glib appears to be such a case
ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: radiotray 0.7.3-1ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1
Uname: Linux 3.16.0-9-generic x86_64
ApportVersion: 2.14.6-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Thu Aug 21 07:40:16 2014
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/radiotray
ExecutableTimestamp: 1368129423
InstallationDate: Installed on 2014-08-19 (1 days ago)
InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - Alpha amd64 (20140731)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/radiotray
ProcCwd: /usr/lib/python2.7/dist-packages/radiotray
Signal: 6
SourcePackage: radiotray
StacktraceTop:
raise () from /lib/x86_64-linux-gnu/libc.so.6
abort () from /lib/x86_64-linux-gnu/libc.so.6
g_mutex_unlock_slowpath (mutex=<optimized out>, prev=<optimized out>) at /build/buildd/glib2.0-2.41.2/./glib/gthread-posix.c:1327
IA__gtk_main () at /build/buildd/gtk+2.0-2.24.24/gtk/gtkmain.c:1270
_wrap_gtk_main (self=<optimized out>) at /build/buildd/pygtk-2.24.0/gtk/gtk.override:1240
Title: radiotray crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo |
|
2014-08-21 06:48:01 |
acllos |
description |
after 15/august/2014 updates, radiotray crashes while trying to initialize in the traybar (of mate-desktop).
the crash appears to be gtk2/pygtk related:
in IA__gtk_main () at /build/buildd/gtk+2.0-2.24.24/gtk/gtkmain.c:1270
is a call to GDK_THREADS_LEAVE
if (g_main_loop_is_running (main_loops->data))
{
GDK_THREADS_LEAVE ();
which in turn triggers a call to g_mutex_unlock_slowpath.
it appears that in the last glib(s) (2.41+) the gmutex implementation was rewritten and there's now a check on whatever the mutex was already locked or already unlocked ("Attempt to unlock mutex that was not locked").
so, many superflous but otherwise harmless calls to unlock a gmutex are now causing crashes, and radiotray in combination with the latest pygtk/libgtk2/glib appears to be such a case
ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: radiotray 0.7.3-1ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1
Uname: Linux 3.16.0-9-generic x86_64
ApportVersion: 2.14.6-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Thu Aug 21 07:40:16 2014
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/radiotray
ExecutableTimestamp: 1368129423
InstallationDate: Installed on 2014-08-19 (1 days ago)
InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - Alpha amd64 (20140731)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/radiotray
ProcCwd: /usr/lib/python2.7/dist-packages/radiotray
Signal: 6
SourcePackage: radiotray
StacktraceTop:
raise () from /lib/x86_64-linux-gnu/libc.so.6
abort () from /lib/x86_64-linux-gnu/libc.so.6
g_mutex_unlock_slowpath (mutex=<optimized out>, prev=<optimized out>) at /build/buildd/glib2.0-2.41.2/./glib/gthread-posix.c:1327
IA__gtk_main () at /build/buildd/gtk+2.0-2.24.24/gtk/gtkmain.c:1270
_wrap_gtk_main (self=<optimized out>) at /build/buildd/pygtk-2.24.0/gtk/gtk.override:1240
Title: radiotray crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo |
after 15/august/2014 updates, radiotray crashes while trying to initialize in the traybar (of mate-desktop).
the crash appears to be gtk2/pygtk related:
in IA__gtk_main () at /build/buildd/gtk+2.0-2.24.24/gtk/gtkmain.c:1270
is a call to GDK_THREADS_LEAVE
if (g_main_loop_is_running (main_loops->data))
{
GDK_THREADS_LEAVE ();
which in turn triggers a call to g_mutex_unlock_slowpath.
it appears that in the last glib(s) (2.41+) the gmutex implementation was rewritten and there's a check now on whatever the mutex was already locked or already unlocked ("Attempt to unlock mutex that was not locked").
so, many superflous but otherwise harmless calls to unlock a gmutex are now causing crashes, and radiotray in combination with the latest pygtk/libgtk2/glib appears to be such a case
ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: radiotray 0.7.3-1ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1
Uname: Linux 3.16.0-9-generic x86_64
ApportVersion: 2.14.6-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Thu Aug 21 07:40:16 2014
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/radiotray
ExecutableTimestamp: 1368129423
InstallationDate: Installed on 2014-08-19 (1 days ago)
InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - Alpha amd64 (20140731)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/radiotray
ProcCwd: /usr/lib/python2.7/dist-packages/radiotray
Signal: 6
SourcePackage: radiotray
StacktraceTop:
raise () from /lib/x86_64-linux-gnu/libc.so.6
abort () from /lib/x86_64-linux-gnu/libc.so.6
g_mutex_unlock_slowpath (mutex=<optimized out>, prev=<optimized out>) at /build/buildd/glib2.0-2.41.2/./glib/gthread-posix.c:1327
IA__gtk_main () at /build/buildd/gtk+2.0-2.24.24/gtk/gtkmain.c:1270
_wrap_gtk_main (self=<optimized out>) at /build/buildd/pygtk-2.24.0/gtk/gtk.override:1240
Title: radiotray crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo |
|
2014-08-21 06:55:27 |
Apport retracing service |
bug |
|
|
added subscriber Crash bug triagers for Ubuntu packages |
2014-08-21 06:55:31 |
Apport retracing service |
attachment added |
|
Stacktrace.txt https://bugs.launchpad.net/bugs/1359564/+attachment/4183065/+files/Stacktrace.txt |
|
2014-08-21 06:55:33 |
Apport retracing service |
attachment added |
|
ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1359564/+attachment/4183066/+files/ThreadStacktrace.txt |
|
2014-08-21 06:55:37 |
Apport retracing service |
radiotray (Ubuntu): status |
New |
Invalid |
|
2014-08-21 06:55:41 |
Apport retracing service |
attachment removed |
CoreDump.gz https://bugs.launchpad.net/bugs/1359564/+attachment/4183050/+files/CoreDump.gz |
|
|
2014-08-21 06:55:43 |
Apport retracing service |
tags |
amd64 apport-crash need-amd64-retrace utopic |
amd64 apport-crash utopic |
|
2014-08-21 06:58:12 |
acllos |
description |
after 15/august/2014 updates, radiotray crashes while trying to initialize in the traybar (of mate-desktop).
the crash appears to be gtk2/pygtk related:
in IA__gtk_main () at /build/buildd/gtk+2.0-2.24.24/gtk/gtkmain.c:1270
is a call to GDK_THREADS_LEAVE
if (g_main_loop_is_running (main_loops->data))
{
GDK_THREADS_LEAVE ();
which in turn triggers a call to g_mutex_unlock_slowpath.
it appears that in the last glib(s) (2.41+) the gmutex implementation was rewritten and there's a check now on whatever the mutex was already locked or already unlocked ("Attempt to unlock mutex that was not locked").
so, many superflous but otherwise harmless calls to unlock a gmutex are now causing crashes, and radiotray in combination with the latest pygtk/libgtk2/glib appears to be such a case
ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: radiotray 0.7.3-1ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1
Uname: Linux 3.16.0-9-generic x86_64
ApportVersion: 2.14.6-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Thu Aug 21 07:40:16 2014
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/radiotray
ExecutableTimestamp: 1368129423
InstallationDate: Installed on 2014-08-19 (1 days ago)
InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - Alpha amd64 (20140731)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/radiotray
ProcCwd: /usr/lib/python2.7/dist-packages/radiotray
Signal: 6
SourcePackage: radiotray
StacktraceTop:
raise () from /lib/x86_64-linux-gnu/libc.so.6
abort () from /lib/x86_64-linux-gnu/libc.so.6
g_mutex_unlock_slowpath (mutex=<optimized out>, prev=<optimized out>) at /build/buildd/glib2.0-2.41.2/./glib/gthread-posix.c:1327
IA__gtk_main () at /build/buildd/gtk+2.0-2.24.24/gtk/gtkmain.c:1270
_wrap_gtk_main (self=<optimized out>) at /build/buildd/pygtk-2.24.0/gtk/gtk.override:1240
Title: radiotray crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo |
after 15/august/2014 updates, radiotray crashes while trying to initialize in the traybar (of mate-desktop).
the crash appears to be gtk2/pygtk related:
in IA__gtk_main () at /build/buildd/gtk+2.0-2.24.24/gtk/gtkmain.c:1270
is a call to GDK_THREADS_LEAVE
if (g_main_loop_is_running (main_loops->data))
{
GDK_THREADS_LEAVE ();
which in turn triggers a call to g_mutex_unlock_slowpath.
it appears that in the last glib(s) (2.41+) the gmutex implementation was rewritten and there's a check now on whatever the mutex was already locked or already unlocked ("Attempt to unlock mutex that was not locked").
so, many superfluous but otherwise harmless calls to unlock a gmutex are now causing crashes, and radiotray in combination with the latest pygtk/libgtk2/glib appears to be such a case
ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: radiotray 0.7.3-1ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1
Uname: Linux 3.16.0-9-generic x86_64
ApportVersion: 2.14.6-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Thu Aug 21 07:40:16 2014
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/radiotray
ExecutableTimestamp: 1368129423
InstallationDate: Installed on 2014-08-19 (1 days ago)
InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - Alpha amd64 (20140731)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/radiotray
ProcCwd: /usr/lib/python2.7/dist-packages/radiotray
Signal: 6
SourcePackage: radiotray
StacktraceTop:
raise () from /lib/x86_64-linux-gnu/libc.so.6
abort () from /lib/x86_64-linux-gnu/libc.so.6
g_mutex_unlock_slowpath (mutex=<optimized out>, prev=<optimized out>) at /build/buildd/glib2.0-2.41.2/./glib/gthread-posix.c:1327
IA__gtk_main () at /build/buildd/gtk+2.0-2.24.24/gtk/gtkmain.c:1270
_wrap_gtk_main (self=<optimized out>) at /build/buildd/pygtk-2.24.0/gtk/gtk.override:1240
Title: radiotray crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo |
|
2014-08-21 07:09:37 |
acllos |
radiotray (Ubuntu): status |
Invalid |
New |
|
2014-08-30 23:30:40 |
acllos |
information type |
Private |
Public |
|
2014-08-31 00:17:05 |
acllos |
attachment added |
|
tentative patch https://bugs.launchpad.net/ubuntu/+source/radiotray/+bug/1359564/+attachment/4191180/+files/SysTray.patch |
|
2014-08-31 00:24:00 |
Ubuntu Foundations Team Bug Bot |
tags |
amd64 apport-crash utopic |
amd64 apport-crash patch utopic |
|
2014-08-31 00:24:08 |
Ubuntu Foundations Team Bug Bot |
bug |
|
|
added subscriber Ubuntu Review Team |
2014-08-31 10:39:22 |
Xavier Guillot |
bug |
|
|
added subscriber Xavier Guillot |
2014-09-07 18:34:16 |
Launchpad Janitor |
radiotray (Ubuntu): status |
New |
Confirmed |
|
2014-09-09 22:11:23 |
acllos |
attachment added |
|
radiotray-debian.patch https://bugs.launchpad.net/ubuntu/+source/radiotray/+bug/1359564/+attachment/4199990/+files/radiotray-debian.patch |
|
2014-10-07 00:29:06 |
Logan Rosen |
marked as duplicate |
|
1376229 |
|
2015-09-01 09:10:20 |
Vitalii |
information type |
Public |
Public Security |
|
2015-09-01 09:10:26 |
Vitalii |
information type |
Public Security |
Public |
|