Your message dated Mon, 03 Feb 2025 20:35:22 -0500
with message-id <[email protected]>
and subject line libuhd4.6.0: Segfault in gqrx related to libuhd 4.6.0
has caused the Debian Bug report #1059874,
regarding libuhd4.6.0: Segfault in gqrx related to libuhd 4.6.0
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.)


-- 
1059874: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059874
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libuhd4.6.0
Version: 4.6.0.0+ds1-5+b1
Severity: important
X-Debbugs-Cc: [email protected]

Dear Maintainer,


   * What led up to the situation?
    when trying to run sdr related softwares, specially gqrx, the system goes 
segfault 

   * What exactly did you do (or not do) that was effective (or
     ineffective)?
    just run gqrx

   * What was the outcome of this action?
    dmesg output showing segfault and traps in gqrx due to libuhd.so.4.6.0

   * What outcome did you expect instead?
    none, just the program gqrx running normally


-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.5.0-5-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), 
LANGUAGE=pt_BR:pt:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libuhd4.6.0 depends on:
ii  libboost-chrono1.83.0         1.83.0-2
ii  libboost-filesystem1.83.0     1.83.0-2
ii  libboost-serialization1.83.0  1.83.0-2
ii  libboost-thread1.83.0         1.83.0-2
ii  libc6                         2.37-12
ii  libgcc-s1                     13.2.0-7
ii  libpython3.11                 3.11.7-2
ii  libstdc++6                    13.2.0-7
ii  libusb-1.0-0                  2:1.0.26-1

libuhd4.6.0 recommends no packages.

Versions of packages libuhd4.6.0 suggests:
pn  uhd-host  <none>

-- no debconf information

--- End Message ---
--- Begin Message ---
Package: uhd
Version: 4.7.0.0+ds1-1

The problem was only noticed in unstable, during a period when binNMU
recompilation was being done to allow a dependency library to
transition.

Now that gqrx has been build to use libuhd4.7.0 the problem reported
here has not been observed. Time to close the bug, as libuhd4.6.0 is no
longer a part of any Debian release.

Thank you for your interest in gqrx, uhd, and improving Debian,
-Maitland

--- End Message ---

Reply via email to