Bug#762630: radiotray: Segmentation fault after upgrade to GNOME 3.14: Attempt to unlock mutex that was not locked

2014-09-24 Thread Elías Alejandro
Hello,
Ubuntu seems that reported the same before[0], also attaching a patch[1].
and it was already reported to upstream[2]. Currently I'm using xfce can
you please test that patch?
just remove gtk.gdk.threads_init() from: src/SysTray.py.

[0] https://bugs.launchpad.net/ubuntu/+source/radiotray/+bug/1359564
[1] https://launchpadlibrarian.net/183620304/SysTray.patch
[2]
https://bitbucket.org/carlmig/radio-tray/issue/220/crashed-with-attempt-to-unlock-mutex-that


Best regards,

--
Elías Alejandro

On Tue, Sep 23, 2014 at 3:56 PM, Paul Menzel pm.deb...@googlemail.com
wrote:

 Package: radiotray
 Version: 0.7.3-1
 Severity: grave
 Tags: upstream
 Justification: renders package unusable

 Dear Debian folks,


 upgrading GNOME Shell from 3.12.2-3 to 3.13.92-1 (3.14-1) – and the
 related packages – RadioTray crashes with `SIGABRT`. The core dump file
 does not help.

 Core was generated by `/usr/bin/python /usr/bin/radiotray'.
 Program terminated with signal SIGABRT, Aborted.
 #0  0xb771dd4c in __kernel_vsyscall ()
 (gdb) t a a bt

 Thread 1 (LWP 11731):
 #0  0xb771dd4c in __kernel_vsyscall ()
 #1  0xb74d8267 in ?? ()
 #2  0xb7651000 in ?? ()
 Backtrace stopped: previous frame inner to this frame (corrupt
 stack?)

 The only error message I see is: `Attempt to unlock mutex that was not
 locked`.


 Thanks,

 Paul

 -- System Information:
 Debian Release: jessie/sid
   APT prefers unstable
   APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')
 Architecture: i386 (i686)

 Kernel: Linux 3.16-2-686-pae (SMP w/2 CPU cores)
 Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
 Shell: /bin/sh linked to /bin/bash

 Versions of packages radiotray depends on:
 ii  gstreamer0.10-plugins-base  0.10.36-2
 ii  gstreamer0.10-plugins-good  0.10.31-3+nmu4
 ii  gstreamer0.10-plugins-ugly  0.10.19-2.1
 ii  python  2.7.8-1
 ii  python-dbus 1.2.0-2+b3
 ii  python-glade2   2.24.0-4
 ii  python-gobject  3.12.2-1
 ii  python-gst0.10  0.10.22-3
 ii  python-gtk2 2.24.0-4
 ii  python-lxml 3.4.0-1
 ii  python-notify   0.1.1-3
 ii  python-xdg  0.25-4

 radiotray recommends no packages.

 radiotray suggests no packages.

 -- no debconf information



Bug#762630: radiotray: Segmentation fault after upgrade to GNOME 3.14: Attempt to unlock mutex that was not locked

2014-09-23 Thread Paul Menzel
Package: radiotray
Version: 0.7.3-1
Severity: grave
Tags: upstream
Justification: renders package unusable

Dear Debian folks,


upgrading GNOME Shell from 3.12.2-3 to 3.13.92-1 (3.14-1) – and the
related packages – RadioTray crashes with `SIGABRT`. The core dump file
does not help.

Core was generated by `/usr/bin/python /usr/bin/radiotray'.
Program terminated with signal SIGABRT, Aborted.
#0  0xb771dd4c in __kernel_vsyscall ()
(gdb) t a a bt

Thread 1 (LWP 11731):
#0  0xb771dd4c in __kernel_vsyscall ()
#1  0xb74d8267 in ?? ()
#2  0xb7651000 in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

The only error message I see is: `Attempt to unlock mutex that was not locked`.


Thanks,

Paul

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 3.16-2-686-pae (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages radiotray depends on:
ii  gstreamer0.10-plugins-base  0.10.36-2
ii  gstreamer0.10-plugins-good  0.10.31-3+nmu4
ii  gstreamer0.10-plugins-ugly  0.10.19-2.1
ii  python  2.7.8-1
ii  python-dbus 1.2.0-2+b3
ii  python-glade2   2.24.0-4
ii  python-gobject  3.12.2-1
ii  python-gst0.10  0.10.22-3
ii  python-gtk2 2.24.0-4
ii  python-lxml 3.4.0-1
ii  python-notify   0.1.1-3
ii  python-xdg  0.25-4

radiotray recommends no packages.

radiotray suggests no packages.

-- no debconf information


signature.asc
Description: This is a digitally signed message part