Bug#1012538: knocked out usability - module 'collections' has no attribute 'Callable'

2022-06-08 Thread Tyler Schwend
The Debian packaged version is much older than the current version.

On Wednesday, June 8, 2022, Arnaldo Pirrone  wrote:
> Package: chirp
> Version: 1:20200227+py3+20200213-3
> Severity: grave
> X-Debbugs-Cc: it9...@gmail.com
>
> Just tried using this software to program my radio and found out it
stopped
> working. I remember it was everything fine a few months ago. Probably
this is
> caused by changes in Python 3.10.5
>
>
> -- System Information:
> Debian Release: bookworm/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 5.17.13-xanmod1 (SMP w/4 CPU threads)
> Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
> Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE
not set
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
> Versions of packages chirp depends on:
> ii  python3   3.10.4-1+b1
> ii  python3-future0.18.2-6
> ii  python3-serial3.5-1
> ii  python3-six   1.16.0-3
> ii  python3-wxgtk4.0  4.0.7+dfsg-13
>
> chirp recommends no packages.
>
> chirp suggests no packages.
>
> -- no debconf information
>
>


Bug#969546: freecad: Freecad crashes when placing beam in Arch workbench

2020-09-04 Thread Tyler Schwend
Package: freecad
Version: 0.18.4+dfsg2-5
Severity: normal
Tags: upstream
X-Debbugs-Cc: tylerschw...@gmail.com

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
Attempting to use the Arch workbench in Freecad.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
Open a new document.
Switch to the Arch workbench.
Click the Structure button.
Switch to Beam.
Optionally, set the material and preset.
Place the beam.
   * What was the outcome of this action?
Freecad crashes with the below segfault.
   * What outcome did you expect instead?
A new beam.

*** End of the template - remove these template lines ***
Program received signal SIGSEGV, Segmentation fault.
#0  /lib/x86_64-linux-gnu/libc.so.6(+0x3be30) [0x7f2ef531fe30]
#1  0x7f2ed9773a5f in Shiboken::Object::cppPointers(SbkObject*) from
/usr/lib/x86_64-linux-gnu/libshiboken2.cpython-38-x86_64-linux-gnu.so.5.15+0xdf
#2  /usr/lib/python3/dist-packages/shiboken2/shiboken2.cpython-38-x86_64-linux-
gnu.so(+0x273a) [0x7f2eec17573a]
#3  /usr/lib/x86_64-linux-gnu/libpython3.8.so.1.0(+0xe5f66) [0x7f2ef632cf66]
#4  /usr/lib/x86_64-linux-gnu/libpython3.8.so.1.0(PyVectorcall_Call+0x5c)
[0x7f2ef62e913c]
#5  0x7f2ef73ccd07 in Gui::qt_getCppPointer(Py::Object const&, char const*,
char const*) from /usr/lib/freecad-python3/lib/libFreeCADGui.so+0x2c7
#6  0x7f2ef72fd950 in
Gui::TaskView::TaskDialogPython::TaskDialogPython(Py::Object const&) from
/usr/lib/freecad-python3/lib/libFreeCADGui.so+0x7d0
#7  0x7f2ef72fdd0d in Gui::TaskView::ControlPy::showDialog(Py::Tuple const&)
from /usr/lib/freecad-python3/lib/libFreeCADGui.so+0x8d
#8  0x7f2ef72fe6b1 in
Py::PythonExtension::method_varargs_call_handler(_object*,
_object*) from /usr/lib/freecad-python3/lib/libFreeCADGui.so+0x1b1
#9  /usr/lib/x86_64-linux-gnu/libpython3.8.so.1.0(+0xa19c7) [0x7f2ef62e89c7]
#10  /usr/lib/x86_64-linux-gnu/libpython3.8.so.1.0(_PyObject_MakeTpCall+0xa7)
[0x7f2ef62e9817]
#11  /usr/lib/x86_64-linux-gnu/libpython3.8.so.1.0(+0x7dcd3) [0x7f2ef62c4cd3]
#12  /usr/lib/x86_64-linux-
gnu/libpython3.8.so.1.0(_PyEval_EvalFrameDefault+0x1292) [0x7f2ef62bc552]
#13  /usr/lib/x86_64-linux-gnu/libpython3.8.so.1.0(+0x73073) [0x7f2ef62ba073]
#14  /usr/lib/x86_64-linux-gnu/libpython3.8.so.1.0(PyVectorcall_Call+0x5c)
[0x7f2ef62e913c]
#15  0x7f2ed9279dc8 in PySide::SignalManager::callPythonMetaMethod(QMetaMethod
const&, void**, _object*, bool) from /usr/lib/x86_64-linux-
gnu/libpyside2.cpython-38-x86_64-linux-gnu.so.5.15+0x98
#16  /usr/lib/x86_64-linux-gnu/libpyside2.cpython-38-x86_64-linux-
gnu.so.5.15(+0x142ae) [0x7f2ed927e2ae]
#17  /usr/lib/x86_64-linux-gnu/libQt5Core.so.5(+0x2d6610) [0x7f2ef5968610]
#18  0x7f2ef596c24a in QTimer::timeout(QTimer::QPrivateSignal) from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5+0x3a
#19  /usr/lib/python3/dist-packages/PySide2/QtCore.cpython-38-x86_64-linux-
gnu.so(+0x2b85bf) [0x7f2ed95585bf]
#20  0x7f2ef595ee5f in QObject::event(QEvent*) from /usr/lib/x86_64-linux-
gnu/libQt5Core.so.5+0x1cf
#21  /usr/lib/python3/dist-packages/PySide2/QtCore.cpython-38-x86_64-linux-
gnu.so(+0x2b8167) [0x7f2ed9558167]
#22  0x7f2ef5d2403f in QApplicationPrivate::notify_helper(QObject*, QEvent*)
from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5+0x7f
#23  0x7f2ef7108cf8 in Gui::GUIApplication::notify(QObject*, QEvent*) from
/usr/lib/freecad-python3/lib/libFreeCADGui.so+0x88
#24  0x7f2ef5933b62 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5+0x182
#25  0x7f2ef59886c3 in QTimerInfoList::activateTimers() from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5+0x3e3
#26  /usr/lib/x86_64-linux-gnu/libQt5Core.so.5(+0x2f6f44) [0x7f2ef5988f44]
#27  /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x27d)
[0x7f2ef32255fd]
#28  /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x50880) [0x7f2ef3225880]
#29  /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x2f)
[0x7f2ef322590f]
#30  0x7f2ef59892ff in
QEventDispatcherGlib::processEvents(QFlags) from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5+0x5f
#31  0x7f2ef59324db in QEventLoop::exec(QFlags)
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5+0x12b
#32  0x7f2ef593a782 in QCoreApplication::exec() from /usr/lib/x86_64-linux-
gnu/libQt5Core.so.5+0x92
#33  0x7f2ef709a77b in Gui::Application::runApplication() from
/usr/lib/freecad-python3/lib/libFreeCADGui.so+0x165b
#34  freecad(main+0x6a6) [0x55aaaefdf726]
#35  /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xea) [0x7f2ef530acca]
#36  freecad(_start+0x2a) [0x55aaaefdfa1a]
Segmentation fault



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

Kernel: Linux 5.7.0-2-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=U

Bug#918140: Confirming linux-image-4.17.0-3-amd64 works

2019-01-04 Thread Tyler Schwend
Just confirming that linux-image-4.17.0-3-amd64 is working fine. Almost 24
hours of uptime whereas I couldn't get 2 hours on
linux-image-4.19.0-1-amd64.

I am using the same kernel options on both kernels, so I'm not sure if 4.17
works without disabling APSTE or not.


Bug#918140: linux-image-4.19.0-1-amd64: Samsung PM951 SSD in Dell XPS 15 9550 goes read-only

2019-01-03 Thread Tyler Schwend
Package: src:linux
Version: 4.19.12-1
Severity: critical
Tags: upstream
Justification: breaks the whole system

Dear Maintainer,

Submitting a bug report wherein after a kernel upgrade my laptop's SSD will,
during use or idle, go into read-only mode after minutes or hours of uptime. It
seems this is related to NVME/APSTE features (which I don't understand). Below
are some similar reports for other models:

https://groups.google.com/forum/#!searchin/linux.debian.bugs.dist/apst$20samsung|sort:date/linux.debian.bugs.dist/1AAKPI7rfQA/450TYup-
AQAJ

https://bbs.archlinux.org/viewtopic.php?id=232692

https://askubuntu.com/questions/905710/ext4-fs-error-after-
ubuntu-17-04-upgrade/906105#906105

I had been running an older kernel (because I previously noticed this and
associated it with a kernel upgrade) but over time forgot why I was using an
old kernel. Some docker work required me to update my kernel again, the problem
returned, and I was reminded of why I kept running the old kernel.

I believe that linux-image-4.17.0-3-amd64 works fine for me (possibly now that
I have disabled APSTE) but linux-image-4.19.0-1-amd64 does not. I don't know
what version of kernel I was running previously, but I will boot back to
4.17.03 and use that for a time, and then update the bug report.


   * What led up to the situation?
- Upgrading from an older 4.x kernel. I think 4.17 is fine, but will have to
run for a while to be sure.
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
- No fixes found except for running older kernel.
- Disabling APSTE with nvme_core.default_ps_max_latency_us=0 provides no
relief, though it is reported as disabled by NVME tool.
- There are no firmware updates available for this drive.



-- Package-specific info:
** Version:
Linux version 4.19.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 
8.2.0 (Debian 8.2.0-13)) #1 SMP Debian 4.19.12-1 (2018-12-22)

** Command line:
BOOT_IMAGE=/vmlinuz-4.19.0-1-amd64 root=/dev/mapper/func--platform--vg-root ro 
quiet nvme_core.default_ps_max_latency_us=0

** Tainted: OE (12288)
 * Out-of-tree module has been loaded.
 * Unsigned module has been loaded.

** Kernel log:
[3.661043] Bluetooth: L2CAP socket layer initialized
[3.661055] Bluetooth: SCO socket layer initialized
[3.666339] usbcore: registered new interface driver btusb
[3.690698] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[3.690699] Bluetooth: BNEP filters: protocol multicast
[3.690702] Bluetooth: BNEP socket layer initialized
[3.713324] input: HDA Intel PCH Headphone Mic as 
/devices/pci:00/:00:1f.3/sound/card0/input20
[3.713365] input: HDA Intel PCH HDMI/DP,pcm=3 as 
/devices/pci:00/:00:1f.3/sound/card0/input21
[3.713400] input: HDA Intel PCH HDMI/DP,pcm=7 as 
/devices/pci:00/:00:1f.3/sound/card0/input22
[3.713450] input: HDA Intel PCH HDMI/DP,pcm=8 as 
/devices/pci:00/:00:1f.3/sound/card0/input23
[3.713507] input: HDA Intel PCH HDMI/DP,pcm=9 as 
/devices/pci:00/:00:1f.3/sound/card0/input24
[3.715654] input: HDA Intel PCH HDMI/DP,pcm=10 as 
/devices/pci:00/:00:1f.3/sound/card0/input25
[3.736832] input: Logitech Unifying Device. Wireless PID:2011 Keyboard as 
/devices/pci:00/:00:14.0/usb1/1-2/1-2.3/1-2.3:1.2/0003:046D:C52B.0008/0003:046D:2011.000A/input/input26
[3.737036] input: Logitech Unifying Device. Wireless PID:2011 Consumer 
Control as 
/devices/pci:00/:00:14.0/usb1/1-2/1-2.3/1-2.3:1.2/0003:046D:C52B.0008/0003:046D:2011.000A/input/input27
[3.737096] input: Logitech Unifying Device. Wireless PID:2011 System 
Control as 
/devices/pci:00/:00:14.0/usb1/1-2/1-2.3/1-2.3:1.2/0003:046D:C52B.0008/0003:046D:2011.000A/input/input28
[3.737154] hid-generic 0003:046D:2011.000A: input,hidraw7: USB HID v1.11 
Keyboard [Logitech Unifying Device. Wireless PID:2011] on usb-:00:14.0-2.3:4
[3.738701] input: Logitech Unifying Device. Wireless PID:4055 Mouse as 
/devices/pci:00/:00:14.0/usb1/1-2/1-2.3/1-2.3:1.2/0003:046D:C52B.0008/0003:046D:4055.000B/input/input32
[3.738766] hid-generic 0003:046D:4055.000B: input,hidraw8: USB HID v1.11 
Mouse [Logitech Unifying Device. Wireless PID:4055] on usb-:00:14.0-2.3:1
[3.752683] input: Logitech K520 as 
/devices/pci:00/:00:14.0/usb1/1-2/1-2.3/1-2.3:1.2/0003:046D:C52B.0008/0003:046D:2011.000C/input/input36
[3.781508] Bluetooth: hci0: BCM: chip id 102
[3.782508] Bluetooth: hci0: BCM: features 0x2f
[3.798526] Bluetooth: hci0: func-platform
[3.799513] Bluetooth: hci0: BCM (001.001.005) build 0422
[3.801782] bluetooth hci0: firmware: direct-loading firmware 
brcm/BCM-0a5c-6410.hcd
[3.847890] logitech-hidpp-device 0003:046D:2011.000C: input,hidraw9: USB 
HID v1.11 Keyboard [Logitech K520] on usb-:00:14.0-2.3:2
[3.854718] input: Logitech K520 as 
/devices/pci:00/:00:14.0/usb1/1-2/1-2.3/1-2.3:1.2/0003:046D:C52B.0008/0003:046D:2011.000D/i