Bug#833264: wpasupplicant: DHCPOffer not recognized after upgrade on 1 August 2016
Package: wpasupplicant Version: 2.3-2.4 Severity: important Since yesterdays update of wpasupplicant it is impossible to accept a valid DHCPOffer on this computer. Other computers in the network have no issue. Downgrading to the version of wpasupplicant in 'testing' solves the issue. I put wpasupplicant on 'hold' with apt-mark, all other packages are Debian Sid. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.6.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages wpasupplicant depends on: ii adduser 3.115 ii libc6 2.23-4 ii libdbus-1-3 1.10.8-1 ii libnl-3-200 3.2.27-1 ii libnl-genl-3-200 3.2.27-1 ii libpcsclite1 1.8.17-1 ii libreadline6 6.3-8+b4 ii libssl1.0.2 1.0.2h-1 ii lsb-base 9.20160629 wpasupplicant recommends no packages. Versions of packages wpasupplicant suggests: pn libengine-pkcs11-openssl pn wpagui -- no debconf information
Bug#960772: [Debian-lego-team] nbc NXC compiler bug
Thank you! The problem is solved with the next version of this program. This can be found here: https://sourceforge.net/p/bricxcc/code/HEAD/tree/x64/ greetings, paul On Sat, May 16, 2020 at 3:09 PM Petter Reinholdtsen wrote: > > Package: nbc > Version: 1.2.1.r4+dfsg-9 > > Hi. > > Moving your request to the bug tracker, to make sure it is tracked there. > > > [Paul Cobbaut] > > Hello, > > > > I humbly believe there is a compiler bug in nbc in Debian. The line: > > > > RemoteStopProgram(SLAVE_CONN); > > > > does not compile. I have frequent Bluetooth communication between two NXT > > bricks, and that all works fine. It is just this one line that always > fails > > to compile. I have tried many variations on this line, in different > > locations in the program, but to no avail. > > > > See also: > > > https://bricks.stackexchange.com/questions/14766/mindstorms-nxt-nxc-remotestopprogram-fails-compilation?noredirect=1#comment17516_14766 > > > > I understand this is an old program, and that a fix may not be coming. > > > > greetings, > > paul > > -- > Happy hacking > Petter Reinholdtsen >
Bug#871949: Info received (network-manager: Wifi disconnects and reconnects often)
The problem seems solved. I changed the ipv6 settings in the NetworkManager GUI to use EUI64 and now there are no more disconnects. (I also kept doing aptitude update && aptitude upgrade daily.) paul
Bug#871949: journalctl
Hello kind people of Debian, reportbug did not ask me for the relevant journalctl entry... so here it is attached. I am a Debian sysadmin (not a developer sorry). This is on my personal MacBookPro. paul Mar 03 13:08:47 MBDebian systemd-timesyncd[658]: Initial synchronization to time server 193.136.152.71:123 (3.debian.pool.ntp.org). Mar 03 13:08:52 MBDebian wpa_supplicant[741]: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=9c:97:26:41:43:81 reason=2 Mar 03 13:08:52 MBDebian systemd-networkd[399]: wlp3s0: Lost carrier Mar 03 13:08:52 MBDebian systemd-timesyncd[658]: No network connectivity, watching for changes. Mar 03 13:08:52 MBDebian wpa_supplicant[741]: wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD Mar 03 13:08:52 MBDebian NetworkManager[10419]: [1614773332.4201] device (wlp3s0): supplicant interface state: completed -> disconnected Mar 03 13:08:52 MBDebian NetworkManager[10419]: [1614773332.4201] device (p2p-dev-wlp3s0): supplicant management interface state: completed -> disconnected Mar 03 13:08:52 MBDebian NetworkManager[10419]: [1614773332.5204] device (wlp3s0): supplicant interface state: disconnected -> scanning Mar 03 13:08:52 MBDebian NetworkManager[10419]: [1614773332.5204] device (p2p-dev-wlp3s0): supplicant management interface state: disconnected -> scanning Mar 03 13:09:00 MBDebian wpa_supplicant[741]: wlp3s0: Trying to associate with SSID 'WiFi-2.4-4381' Mar 03 13:09:00 MBDebian NetworkManager[10419]: [1614773340.4633] device (wlp3s0): supplicant interface state: scanning -> associating Mar 03 13:09:00 MBDebian NetworkManager[10419]: [1614773340.4633] device (p2p-dev-wlp3s0): supplicant management interface state: scanning -> associating Mar 03 13:09:01 MBDebian wpa_supplicant[741]: wlp3s0: CTRL-EVENT-ASSOC-REJECT bssid=00:00:00:00:00:00 status_code=16 Mar 03 13:09:01 MBDebian NetworkManager[10419]: [1614773341.9339] device (wlp3s0): supplicant interface state: associating -> disconnected Mar 03 13:09:01 MBDebian NetworkManager[10419]: [1614773341.9340] device (p2p-dev-wlp3s0): supplicant management interface state: associating -> disconnected Mar 03 13:09:02 MBDebian NetworkManager[10419]: [1614773342.4345] device (wlp3s0): supplicant interface state: disconnected -> scanning Mar 03 13:09:02 MBDebian NetworkManager[10419]: [1614773342.4345] device (p2p-dev-wlp3s0): supplicant management interface state: disconnected -> scanning Mar 03 13:09:03 MBDebian wpa_supplicant[741]: wlp3s0: Trying to associate with SSID 'WiFi-2.4-4381' Mar 03 13:09:03 MBDebian NetworkManager[10419]: [1614773343.8647] device (wlp3s0): supplicant interface state: scanning -> associating Mar 03 13:09:03 MBDebian NetworkManager[10419]: [1614773343.8647] device (p2p-dev-wlp3s0): supplicant management interface state: scanning -> associating Mar 03 13:09:05 MBDebian wpa_supplicant[741]: wlp3s0: CTRL-EVENT-ASSOC-REJECT bssid=00:00:00:00:00:00 status_code=16 Mar 03 13:09:05 MBDebian NetworkManager[10419]: [1614773345.3004] device (wlp3s0): supplicant interface state: associating -> disconnected Mar 03 13:09:05 MBDebian NetworkManager[10419]: [1614773345.3005] device (p2p-dev-wlp3s0): supplicant management interface state: associating -> disconnected Mar 03 13:09:06 MBDebian NetworkManager[10419]: [1614773346.3346] device (wlp3s0): supplicant interface state: disconnected -> scanning Mar 03 13:09:06 MBDebian NetworkManager[10419]: [1614773346.3347] device (p2p-dev-wlp3s0): supplicant management interface state: disconnected -> scanning Mar 03 13:09:07 MBDebian wpa_supplicant[741]: wlp3s0: Trying to associate with SSID 'WiFi-2.4-4381' Mar 03 13:09:07 MBDebian NetworkManager[10419]: [1614773347.7739] device (wlp3s0): supplicant interface state: scanning -> associating Mar 03 13:09:07 MBDebian NetworkManager[10419]: [1614773347.7739] device (p2p-dev-wlp3s0): supplicant management interface state: scanning -> associating Mar 03 13:09:07 MBDebian NetworkManager[10419]: [1614773347.9589] device (wlp3s0): link timed out. Mar 03 13:09:07 MBDebian NetworkManager[10419]: [1614773347.9589] device (wlp3s0): state change: activated -> failed (reason 'supplicant-timeout', sys-iface-state: 'managed') Mar 03 13:09:07 MBDebian NetworkManager[10419]: [1614773347.9594] manager: NetworkManager state is now DISCONNECTED Mar 03 13:09:07 MBDebian NetworkManager[10419]: [1614773347.9604] device (wlp3s0): Activation: failed for connection 'WiFi-2.4-4381' Mar 03 13:09:07 MBDebian NetworkManager[10419]: [1614773347.9616] device (wlp3s0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') Mar 03 13:09:07 MBDebian avahi-daemon[692]: Withdrawing address record for fd8a:7ce6:e7a0:0:10e:4e60:bf79:7005 on wlp3s0. Mar 03 13:09:07 MBDebian dbus-daemon[694]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.122' (uid=0 pid=10419
Bug#871949: journalctl
Hello kind people of Debian, I think this attachment may also be of interest. It is the output of journalctl | grep CTRL-EVENT-DISCONNECTED | tail -30 It shows the disconnects interval, which is often (but not always) close to one hour. That's why I though DHCP lease time and uninstalled isc-dhcp-client. It didn't help. paul root@MBDebian~# journalctl | grep CTRL-EVENT-DISCONNECTED | tail -30 Mar 03 14:10:52 MBDebian wpa_supplicant[741]: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=9c:97:26:41:43:81 reason=2 Mar 03 15:11:46 MBDebian wpa_supplicant[741]: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=9c:97:26:41:43:81 reason=2 Mar 03 15:12:53 MBDebian wpa_supplicant[741]: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=9c:97:26:41:43:81 reason=2 Mar 03 16:13:34 MBDebian wpa_supplicant[741]: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=9c:97:26:41:43:81 reason=2 Mar 03 16:14:44 MBDebian wpa_supplicant[741]: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=9c:97:26:41:43:81 reason=2 Mar 03 16:18:55 MBDebian wpa_supplicant[741]: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=9c:97:26:41:43:81 reason=0 locally_generated=1 Mar 03 16:46:29 MBDebian wpa_supplicant[741]: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=9c:97:26:41:43:81 reason=2 Mar 03 16:46:45 MBDebian wpa_supplicant[741]: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=9c:97:26:41:43:81 reason=3 locally_generated=1 Mar 03 17:47:16 MBDebian wpa_supplicant[741]: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=9c:97:26:41:43:81 reason=2 Mar 03 17:48:23 MBDebian wpa_supplicant[741]: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=9c:97:26:41:43:81 reason=2 Mar 03 18:49:19 MBDebian wpa_supplicant[741]: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=9c:97:26:41:43:81 reason=2 Mar 03 18:50:30 MBDebian wpa_supplicant[741]: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=9c:97:26:41:43:81 reason=2 Mar 03 19:51:23 MBDebian wpa_supplicant[741]: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=9c:97:26:41:43:81 reason=2 Mar 03 19:52:33 MBDebian wpa_supplicant[741]: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=9c:97:26:41:43:81 reason=2 Mar 03 20:01:19 MBDebian wpa_supplicant[741]: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=9c:97:26:41:43:81 reason=3 locally_generated=1 Mar 03 20:53:27 MBDebian wpa_supplicant[795]: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=9c:97:26:41:43:81 reason=2 Mar 03 20:54:37 MBDebian wpa_supplicant[795]: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=9c:97:26:41:43:81 reason=2 Mar 03 20:57:41 MBDebian wpa_supplicant[795]: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=9c:97:26:41:43:81 reason=2 Mar 03 21:58:31 MBDebian wpa_supplicant[795]: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=9c:97:26:41:43:81 reason=2 Mar 03 21:59:43 MBDebian wpa_supplicant[795]: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=9c:97:26:41:43:81 reason=2 Mar 03 22:06:52 MBDebian wpa_supplicant[795]: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=9c:97:26:41:43:81 reason=2 Mar 03 22:19:00 MBDebian wpa_supplicant[795]: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=9c:97:26:41:43:81 reason=0 locally_generated=1 Mar 03 23:07:54 MBDebian wpa_supplicant[795]: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=9c:97:26:41:43:81 reason=2 Mar 03 23:09:05 MBDebian wpa_supplicant[795]: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=9c:97:26:41:43:81 reason=2 Mar 04 00:09:57 MBDebian wpa_supplicant[795]: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=9c:97:26:41:43:81 reason=2 Mar 04 00:11:08 MBDebian wpa_supplicant[795]: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=9c:97:26:41:43:81 reason=2 Mar 04 00:16:53 MBDebian wpa_supplicant[795]: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=9c:97:26:41:43:81 reason=2 Mar 04 00:18:30 MBDebian wpa_supplicant[795]: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=9c:97:26:41:43:81 reason=3 locally_generated=1 Mar 04 09:19:06 MBDebian wpa_supplicant[774]: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=9c:97:26:41:43:81 reason=2 Mar 04 09:20:17 MBDebian wpa_supplicant[774]: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=9c:97:26:41:43:81 reason=2
Bug#871949: network-manager: Wifi disconnects and reconnects often
Package: network-manager Version: 1.30.0-1 Followup-For: Bug #871949 X-Debbugs-Cc: paul.cobb...@gmail.com Dear Maintainer, * What led up to the situation? The disconnecting and reconnecting of the wifi happened also in the past (several months ago), but suddenly stopped. I update Debian every day. Some two weeks ago it started again. This is the same computer for three years now, same wifi, same location, same modem/router, same ISP, nothing changes except for the aptitude upgrade. * What exactly did you do (or not do) that was effective (or ineffective)? I googled the problem a lot the past few days. I added "wifi,powersafe=2' to NetworkManager.conf (because this is suggested in a forum). I reinstalled broadcom-sta-dkms. Yesterday I uninstalled dhclient (isc-dhcp-client), but that also makes no difference. I upgrade Debian every day. * What was the outcome of this action? No difference, the wifi keeps disconnecting (and reconnecting) often. * What outcome did you expect instead? A stable wifi connection, these interrupts are distracting. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-3-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages network-manager depends on: ii adduser 3.118 ii dbus 1.12.20-2 ii libaudit11:3.0-2 ii libbluetooth35.55-3 ii libc62.31-9 ii libcurl3-gnutls 7.74.0-1.1 ii libglib2.0-0 2.66.7-1 ii libgnutls30 3.7.0-5 ii libjansson4 2.13.1-1.1 ii libmm-glib0 1.14.10-0.1 ii libndp0 1.6-1+b1 ii libnewt0.52 0.52.21-4+b3 ii libnm0 1.30.0-1 ii libpsl5 0.21.0-1.2 ii libreadline8 8.1-1 ii libselinux1 3.1-3 ii libsystemd0 247.3-1 ii libteamdctl0 1.31-1 ii libudev1 247.3-1 ii libuuid1 2.36.1-7 ii policykit-1 0.105-30 ii udev 247.3-1 ii wpasupplicant2:2.9.0-20 Versions of packages network-manager recommends: ii dnsmasq-base [dnsmasq-base] 2.84-1 ii iptables 1.8.7-1 ii libpam-systemd 247.3-1 ii modemmanager 1.14.10-0.1 ii ppp 2.4.9-1+1 ii wireless-regdb 2020.04.29-2 Versions of packages network-manager suggests: pn isc-dhcp-client pn libteam-utils -- Configuration Files: /etc/NetworkManager/NetworkManager.conf changed: [main] plugins=ifupdown,keyfile wifi.powersafe=2 [ifupdown] managed=false -- no debconf information
Bug#1068794: sane-utils: (x)scanimage only works once, a second scan right after the first one fails
We managed to solve this bug upstream. https://gitlab.com/sane-project/backends/-/issues/742 Paul
Bug#1068794: sane-utils: (x)scanimage only works once, a second scan right after the first one fails
Package: sane-utils Version: 1.2.1-2 Severity: normal X-Debbugs-Cc: debianbugreport_20240411+s...@cobbaut.be Dear Maintainer, * What led up to the situation? Using a Kyocera ECOSYS M5526cdw printer to scan hundreds of pages. Using the flatbed, not the document feeder. Any scan of a page works fine, but I have to wait about two minutes before scanning the next page, otherwise it fails with "device busy". * What exactly did you do (or not do) that was effective (or ineffective)? scanimage, with or without the --batch option, only allows for one scan. A second scan will fail, providing it is done within about two minutes. For example this command will scan perfectly: $ scanimage -d 'escl:http://192.168.178.32:9095/eSCL' --format jpeg --mode Gray -o page1.jpg This command, executed after flipping the page on the scanner, fails as follows: $ scanimage -d 'escl:http://192.168.178.32:9095/eSCL' --format jpeg --mode Gray -o page2.jpg scanimage: sane_start: Device busy 503 Service Unavailable 503 Service Unavailable 503 Service Unavailable 503 Service Unavailable Using the vendor kyocera-sane package makes no difference. Using 'escl:http://192.168.178.32:9095' or 'escl:http://192.168.178.32:9096' as the device name makes no difference. The result is identical when using xscanimage in GIMP 2.10 or xsane in GIMP 2.8. According to one Reddit user on r/Debian it is a known problem. * What outcome did you expect instead? I was hoping to use a script to quickly scan hundreds of pages into jpg. for i in $(seq -w 12 100) do scanimage --format jpeg --mode Gray -o page$i.jpg #sleep 120 done But the script only works when the sleep 120 command is included, which limits my scanning ability to 30 pages per hour. -- System Information: Debian Release: 12.5 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-28-amd64 (SMP w/24 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=C.UTF-8, LC_CTYPE=C.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 sane-utils depends on: ii adduser3.134 ii debconf [debconf-2.0] 1.5.82 ii init-system-helpers1.65.2 ii libavahi-client3 0.8-10 ii libavahi-common3 0.8-10 ii libc6 2.36-9+deb12u4 ii libieee1284-3 0.2.11-14 ii libjpeg62-turbo1:2.1.5-2 ii libpng16-161.6.39-2 ii libsane1 1.2.1-2 ii libsystemd0252.22-1~deb12u1 ii libusb-1.0-0 2:1.0.26-1 ii libxml22.9.14+dfsg-1.3~deb12u1 ii update-inetd 4.53 sane-utils recommends no packages. Versions of packages sane-utils suggests: ii avahi-daemon 0.8-10 ii unpaper 7.0.0-0.1 -- Configuration Files: /etc/sane.d/saned.conf changed: 192.168.178.0/24 -- debconf information: sane-utils/saned_run: false sane-utils/saned_scanner_group: true
Bug#1068794: sane-utils: (x)scanimage only works once, a second scan right after the first one fails
On 4/12/24 18:55, Jörg Frings-Fürst wrote: Please contact the developers directly at [2]. Done. They already had an issue for it. https://gitlab.com/sane-project/backends/-/issues/742 Paul
