Bug#977702: firmware-brcm80211: brcmfmac43455 on RPi4 causes hostapd to fail silently
Package: firmware-brcm80211 Version: 20200918-1~bop10+1 Severity: normal Dear Maintainer, Steps to reproduce: 1. flash latest tested Raspberry Pi 4 image and boot 2. update all packages 3. install hostapd 4. configure the onboard wlan device as an 802.11n AP Expected results: AP works Actual results: hostapd claims the AP is enabled, but it's actually not Work-around: 1. apt purge firmware-brcm80211 2. cp /lib/firmware/brcm/brcmfmac43455.* from a current stable Raspbian install - this appears to work even despite the fact that Raspbian is 32-bit - the driver still throws a warning about a missing brcmfmac43455-sdio.raspberrypi,4-model-b.txt file, but this file is not included with stable Raspbian, and its absence doesn't appear to cause any problems beyond the warning The brcmfmac43455 firmware in firmware-brcm80211 appears to be much older than what Raspbian stable is currently shipping -- System Information: Debian Release: 10.7 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates') Architecture: arm64 (aarch64) Kernel: Linux 5.9.0-0.bpo.2-arm64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_CRAP Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled firmware-brcm80211 depends on no packages. firmware-brcm80211 recommends no packages. Versions of packages firmware-brcm80211 suggests: ii initramfs-tools 0.133+deb10u1
Bug#971607: guacd: new upstream version availble (includes security fixes)
Package: guacd Version: 0.9.9-2 Severity: important Dear Maintainer, There is a new upstream version of guacd available. Version 1.2.0 includes fixes for two CVEs, one of which includes the potential for arbitrary code execution. Thanks! -Russ
Bug#887465: Please update to new upstream version
It looks like upstream guacamole is freerdp2 compatible as of 1.1.0, and 1.2.0 was released a few months ago.
Bug#954466: acmetool: Cannot Bind to IPv4 port 80
Package: acmetool Version: 0.2.1-2 Severity: normal Dear Maintainer, -- Steps to reproduce problem: 1. Install acmetool 0.2.1-2 on Debian Buster 2. # netstat -pa | grep ':http' # ensure there are no results 3. # acmetool quickstart # select either live or staging and "Listener" 4. # acmetool --xlog.severity=debug want example.com -- Expected results (on the console): [DEBUG] acmetool.reshttp: listening on [::]:80 ... [DEBUG] acmetool.reshttp: listening on :80 -- Actual results (on the console): [DEBUG] acmetool.reshttp: listening on [::]:80 ... [DEBUG] acmetool.reshttp: failed to listen on :80: listen tcp :80: bind: address already in use -- Further troubleshooting steps taken: - specifically defining port 80 or 0.0.0.0:80 in /var/lib/acme/conf/target produces the same failure - # nc -l -p 80 # binds sucessfully -- System Information: Debian Release: 10.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable'), (90, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-8-cloud-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages acmetool depends on: ii libc62.28-10 ii libcap2 1:2.25-2 Versions of packages acmetool recommends: ii dialog 1.3-20190211-1 acmetool suggests no packages. -- no debconf information
Bug#954189: acmetool: Buster acmetool stops working in June 1, 2020
For what it's worth, the version currently in Testing (which does support ACMEv2) will install on Buster with no additional dependencies and seems to be working. Hopefully this means a backport? If nothing else, this does present a work-around. -Russ
Bug#928415: fixed in firefox-esr 60.6.2esr-1
Thanks for the quick turn-around! Any idea when this will show up in Stable? -Russ
Bug#928415: firefox-esr: Bugzilla 1548973 All extensions disabled due to expiration of intermediate signing cert
Package: firefox-esr Version: 60.6.1esr-1~deb9u1 Severity: grave Tags: upstream Justification: causes non-serious data loss >From Bugzilla 1548973 https://bugzilla.mozilla.org/show_bug.cgi?id=1548973 Steps to reproduce: Wait until it's past midnight on 2019-05-04 UTC. Actual results: All addons got disabled due not having valid signature. Expected results: If the signature was due to expire, it should have been renewed weeks ago. Not all extensions were disabled. Fakespot and Google Scholar Button were left in their disabled state. Some reports on reddit 1 says that they had their clocks a day forward, but they may be just early canaries for the actual widespread issue. Going backwards in time allows installation from AMO but do not remove the unsupported mark from the add ons already installed.
Bug#850103: xarchiver: Opening .deb uses "ar" command, but "binutils" package (which provides it) is not a suggested package
Package: xarchiver Version: 1:0.5.4-1+deb8u1 Severity: normal Dear Maintainer, I tried to use xarchiver to open a .deb file, but was presented with an error along the lines of 'Can't run the archiver executable: Failed to execute child process "ar" (No such file or directory)'. The "ar" command is provided by the "binutils" package, and installing this package allowed me to open .deb files using xarchiver. Given that xarchiver relies on a command provided by the "binutils" package, I would have expected that it would be a suggested package for xarchiver. Thanks! Sincerely, Russell Ault -- System Information: Debian Release: 8.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages xarchiver depends on: ii libc6 2.19-18+deb8u6 ii libgdk-pixbuf2.0-0 2.31.1-2+deb8u5 ii libglib2.0-02.42.1-1+b1 ii libgtk2.0-0 2.24.25-3+deb8u1 ii libpango-1.0-0 1.36.8-3 Versions of packages xarchiver recommends: ii bzip2 1.0.6-7+b3 ii p7zip-full 9.20.1~dfsg.1-4.1+deb8u2 ii unzip 6.0-16+deb8u2 ii xdg-utils 1.1.0~rc1+git20111210-7.4 ii xz-utils5.1.1alpha+20120614-2+b3 Versions of packages xarchiver suggests: pn arj pn lhasa pn rar pn rpm pn unar pn zip -- no debconf information
Bug#578250: open-iscsi: Encounters connection failure on boot
: [9.572200] Linux agpgart interface v0.103 Jul 21 17:00:54 stokowski kernel: [9.593047] input: Power Button (FF) as /class/input/input0 Jul 21 17:00:54 stokowski kernel: [9.601230] ACPI: Power Button (FF) [PWRF] Jul 21 17:00:54 stokowski kernel: [9.601424] input: Power Button (CM) as /class/input/input1 Jul 21 17:00:54 stokowski kernel: [9.615876] ACPI: Power Button (CM) [PWRB] Jul 21 17:00:54 stokowski kernel: [9.666462] agpgart: Detected an Intel 865 Chipset. Jul 21 17:00:54 stokowski kernel: [9.666462] agpgart: Detected 8060K stolen memory. Jul 21 17:00:54 stokowski kernel: [9.679138] agpgart: AGP aperture is 128M @ 0xf000 Jul 21 17:00:54 stokowski kernel: [9.748113] ACPI: PCI Interrupt :00:1f.5[B] - GSI 17 (level, low) - IRQ 17 Jul 21 17:00:54 stokowski kernel: [ 10.165743] intel8x0_measure_ac97_clock: measured 54607 usecs Jul 21 17:00:54 stokowski kernel: [ 10.165751] intel8x0: clocking to 48000 Jul 21 17:00:54 stokowski kernel: [ 10.272053] input: PC Speaker as /class/input/input2 Jul 21 17:00:54 stokowski kernel: [ 10.641474] parport_pc 00:0d: reported by Plug and Play ACPI Jul 21 17:00:54 stokowski kernel: [ 10.641494] parport0: PC-style at 0x378 (0x778), irq 7 [PCSPP,TRISTATE] Jul 21 17:00:54 stokowski kernel: [ 11.601221] Adding 3919852k swap on /dev/hda2. Priority:-1 extents:1 across:3919852k Jul 21 17:00:54 stokowski kernel: [ 12.027058] EXT3 FS on hda1, internal journal Jul 21 17:00:54 stokowski kernel: [ 12.287194] loop: module loaded Jul 21 17:00:54 stokowski kernel: [ 13.622256] e1000: eth0: e1000_watchdog: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX Jul 21 17:00:54 stokowski rsyslogd: [origin software=rsyslogd swVersion=3.18.6 x-pid=1877 x-info=http://www.rsyslog.com;] restart Jul 21 17:00:54 stokowski kernel: [ 15.149633] NET: Registered protocol family 10 Jul 21 17:00:54 stokowski kernel: [ 15.149633] lo: Disabled Privacy Extensions Jul 21 17:00:55 stokowski kernel: [ 15.467396] Loading iSCSI transport class v2.0-869. Jul 21 17:00:55 stokowski kernel: [ 15.485006] iscsi: registered transport (tcp) Jul 21 17:00:55 stokowski kernel: [ 15.580887] iscsi: registered transport (iser) -Russ --- On Sun, 5/2/10, Ritesh Raj Sarraf r...@researchut.com wrote: From: Ritesh Raj Sarraf r...@researchut.com Subject: Re: Bug#578250: open-iscsi: Encounters connection failure on boot To: Russell Ault russell.a...@yahoo.ca Cc: 578...@bugs.debian.org Received: Sunday, May 2, 2010, 2:00 AM Russell, Can you please confirm how your network is managed ? Is it through ifup scripts or through a separate network management daemon like wicd or network-manager ? Also please post your boot log. Regards, Ritesh -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#578250: open-iscsi: Encounters connection failure on boot
Package: open-iscsi Version: 2.0.870~rc3-0.4 Severity: normal When trying to login to targets (not mounting to /) during boot using the default init.d and rcS.d configurations, iscsiadm reports that it encounters a connection failure; however, this connection failure is not present if the open-iscsi init.d script is restarted after boot, and everything at that point will then mount normally. This problem disappears if the open-iscsi init.d script is moved from rcS.d to rc2.d and started around the same time as, say, OpenSSH (although I don't have a real sense as to what effect this has on other init.d scripts). Either way, it appears that the problem is being caused by the network not being ready by the time the open-iscsi init.d script is started (even though the order in rcS.d appears to be set correctly), causing the connection failure. -- System Information: Debian Release: 5.0.4 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.26-2-686 (SMP w/2 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages open-iscsi depends on: ii libc6 2.7-18lenny2 GNU C Library: Shared libraries open-iscsi recommends no packages. open-iscsi suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#578250: open-iscsi: Encounters connection failure on boot
Networking is DHCP; I don't believe parallel boot is enabled (ini.d rc script: CONCURRENCY=none). -Russ --- On Sun, 4/18/10, Ritesh Raj Sarraf r...@researchut.com wrote: Is this a dhcp or a static network ? And do you have parallel boot enabled ? Regards, Ritesh -- Ritesh Raj Sarraf RESEARCHUT - http://www.researchut.com Necessity is the mother of invention. __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
