Your message dated Thu, 28 Jan 2016 23:44:03 -0500
with message-id <[email protected]>
and subject line QT GUI Range widget causes SEGV
has caused the Debian Bug report #726788,
regarding QT GUI Range widget causes SEGV
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
726788: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=726788
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libgnuradio-qtgui3.7.1
Version: 3.7.1-2
Severity: normal
An update to my machine in the last around 12 days or so has caused any
flowgraph
that has a QT GUI Range widget in it to SEGV on startup. I note that around 6
days
ago a set of Qt4 updates were installed by aptitude.
The bug appears easy to reproduce (for me anyway!). Just create a new flowgraph
in GRC
which is a null source link that to a QT GUI Sink and run it, and everything is
fine.
Now add QT GUI Entry widget and/or QT GUI Label and/or QT Tab Widget and
everything
still works when you run it. Now add a QT GUI Range widget and now you get an
instant
SEGV when you run it. Below is the output of gdb when attached to python:
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff5ff7d7a in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
(gdb) where
#0 0x00007ffff5ff7d7a in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#1 0x00007ffff64fd81a in ?? () from
/usr/lib/python2.7/dist-packages/PyQt4/QtCore.so
#2 0x00007ffff54f9f20 in ?? () from
/usr/lib/python2.7/dist-packages/PyQt4/QtGui.so
#3 0x00000000032ea808 in ?? ()
#4 0x00007fffffffdbe8 in ?? ()
#5 0x00007ffff50a9059 in ?? () from
/usr/lib/python2.7/dist-packages/PyQt4/QtGui.so
#6 0x00007fffffffdbe8 in ?? ()
#7 0x00000000037820d0 in ?? ()
#8 0x000000000050e8d0 in ?? ()
#9 0x0000000000902430 in ?? ()
#10 0x0000000000000000 in ?? ()
but its not exactly illuminating!
Thanks,
Matt
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.10-3-amd64 (SMP w/6 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages libgnuradio-qtgui3.7.1 depends on:
ii libboost-date-time1.54.0 1.54.0-3
ii libboost-filesystem1.54.0 1.54.0-3
ii libboost-program-options1.54.0 1.54.0-3
ii libboost-system1.54.0 1.54.0-3
ii libboost-thread1.54.0 1.54.0-3
ii libc6 2.17-93
ii libfftw3-single3 3.3.3-5+b1
ii libgcc1 1:4.8.1-10
ii libgnuradio-blocks3.7.1 3.7.1-2
ii libgnuradio-fft3.7.1 3.7.1-2
ii libgnuradio-filter3.7.1 3.7.1-2
ii libgnuradio-pmt3.7.1 3.7.1-2
ii libgnuradio-runtime3.7.1 3.7.1-2
ii libiceutil35 3.5.0-3
ii liblog4cpp5 1.0-4
ii liborc-0.4-0 1:0.4.18-1
ii libpython2.7 2.7.5-8
ii libqtcore4 4:4.8.5+git121-g2a9ea11+dfsg1-2
ii libqtgui4 4:4.8.5+git121-g2a9ea11+dfsg1-2
ii libqwt5-qt4 5.2.3-1
ii libstdc++6 4.8.1-10
ii libvolk0.0.0 3.7.1-2
ii libzeroc-ice35 3.5.0-3
ii multiarch-support 2.17-93
libgnuradio-qtgui3.7.1 recommends no packages.
libgnuradio-qtgui3.7.1 suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
It appears this was more of a PyQT and PyQWT bug than a gnuradio bug.
This problem does not appear in Debian Jessie released versions.
Upstream issue#604 has been closed for a while.
Bug 731437 was fixed by pyqwt5 5.2.1~cvs20091107+dfsg-7
This bug can be closed in Debian.
-Maitland
--- End Message ---
