Your message dated Sun, 7 Jun 2020 22:35:48 +0200
with message-id <20200607203548.GA17366@sarastro>
and subject line Re: Bug#962381: gqrx-sdr: gqrx segmentation fault at start
time in testing
has caused the Debian Bug report #962381,
regarding gqrx-sdr: gqrx segmentation fault at start time in testing
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 ow...@bugs.debian.org
immediately.)
--
962381: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962381
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gqrx-sdr
Version: 2.12.1-1+b3
Severity: grave
Justification: renders package unusable
gqrx does not start in testing, this renders the package unusable.
The problem is reproducible by spinning up a testing chroot (as of today) and
trying to start gqrx
This is the stacktrace:
***
Thread 1 "gqrx" received signal SIGSEGV, Segmentation fault.
0x00005555555f5a52 in
boost::system::error_category::equivalent(boost::system::error_code const&,
int) const ()
(gdb) thread apply all bt
Thread 3 (Thread 0x7fffecc54700 (LWP 1745241)):
#0 0x00007ffff599cb7f in __GI___poll (fds=0x7fffe00029e0, nfds=3, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1 0x00007ffff36847fe in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x00007ffff368491f in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x00007ffff68637c1 in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4 0x00007ffff680c6db in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5 0x00007ffff664d6f1 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6 0x00007fffefe724e6 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#7 0x00007ffff664e872 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8 0x00007ffff7cd4f27 in start_thread (arg=<optimized out>) at
pthread_create.c:479
#9 0x00007ffff59a731f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
Thread 2 (Thread 0x7fffef132700 (LWP 1745240)):
#0 0x00007ffff599cb7f in __GI___poll (fds=0x7fffef131828, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1 0x00007ffff30cfd02 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2 0x00007ffff30d198a in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3 0x00007fffeffabca0 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4 0x00007ffff664e872 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5 0x00007ffff7cd4f27 in start_thread (arg=<optimized out>) at
pthread_create.c:479
#6 0x00007ffff59a731f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
Thread 1 (Thread 0x7ffff03e8c80 (LWP 1745239)):
#0 0x00005555555f5a52 in
boost::system::error_category::equivalent(boost::system::error_code const&,
int) const ()
#1 0x00007ffff6331e8f in boost::asio::detail::posix_mutex::posix_mutex() ()
from /usr/lib/x86_64-linux-gnu/libgnuradio-blocks.so.3.8.1
#2 0x00007ffff63329c7 in boost::asio::io_context::io_context() () from
/usr/lib/x86_64-linux-gnu/libgnuradio-blocks.so.3.8.1
#3 0x00007ffff635ac5c in ?? () from
/usr/lib/x86_64-linux-gnu/libgnuradio-blocks.so.3.8.1
#4 0x00007ffff635ad39 in gr::blocks::udp_sink::make(unsigned long,
std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >
const&, int, int, bool) () from
/usr/lib/x86_64-linux-gnu/libgnuradio-blocks.so.3.8.1
#5 0x0000555555641ecc in udp_sink_f::udp_sink_f() ()
#6 0x00005555556425ef in make_udp_sink_f() ()
#7 0x00005555556122aa in receiver::receiver(std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> >,
std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char>
>, unsigned int) ()
#8 0x0000555555605cd0 in MainWindow::MainWindow(QString, bool, QWidget*) ()
#9 0x00005555555e9f57 in main ()
***
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.6.0-2-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=en_IE.utf8, LC_CTYPE=en_IE.utf8 (charmap=UTF-8),
LANGUAGE=en_IE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages gqrx-sdr depends on:
ii libboost-program-options1.71.0 1.71.0-6+b2
ii libc6 2.30-8
ii libgcc-s1 10.1.0-3
ii libgnuradio-analog3.8.1 3.8.1.0-1+b3
ii libgnuradio-blocks3.8.1 3.8.1.0-1+b3
ii libgnuradio-digital3.8.1 3.8.1.0-1+b3
ii libgnuradio-fft3.8.1 3.8.1.0-1+b3
ii libgnuradio-filter3.8.1 3.8.1.0-1+b3
ii libgnuradio-osmosdr0.2.0 0.2.0-2+b3
ii libgnuradio-pmt3.8.1 3.8.1.0-1+b3
ii libgnuradio-runtime3.8.1 3.8.1.0-1+b3
ii liblog4cpp5v5 1.1.3-1
ii libpulse0 13.0-5
ii libqt5core5a 5.12.5+dfsg-10+b1
ii libqt5gui5 5.12.5+dfsg-10+b1
ii libqt5network5 5.12.5+dfsg-10+b1
ii libqt5svg5 5.12.5-2
ii libqt5widgets5 5.12.5+dfsg-10+b1
ii libstdc++6 10.1.0-3
ii pulseaudio 13.0-5
gqrx-sdr recommends no packages.
gqrx-sdr suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
On Sun, Jun 07, 2020 at 02:00:44PM -0400, A. Maitland Bottoms wrote:
> On Sun, 07 Jun 2020 10:36:54 +0200
> Antonio Radici <anto...@debian.org> wrote:
>
> > gqrx does not start in testing, this renders the package unusable.
>
> I'm sorry to hear this.
>
> I noticed the -b3 version get upgraded today too, but it works for me
> when I start it....
> (I have a box tracking testing, so no chroot here.)
>
> >
> > The problem is reproducible by spinning up a testing chroot (as of
> > today) and trying to start gqrx
>
> gqrx without hardware can be fragile. For that there are run time
> arguments. `gqrx --reset` and `gqrx --edit` handle initial
> configuration problems. Does it then work for you selecting the input
> device doing `gqrx --edit` ?
>
> What device are you trying to use? Does your chroot expose it correctly
> and with the right permissions?
Sorry I made a mistake when reporting this bug, the 2.12.1-1+b2 version was
actually crashing, then at the time of the reporting I did a dist-upgrade to be
sure and I got the update, which is now not crashing.
I will resolve the bug now, thanks a lot for your assistance and sorry for the
inconvenience.
--- End Message ---
