Raspberry Pi Forums • STICKY: Buster bug report thread

Page 1 of 18

STICKY: Buster bug report thread

Posted: Wed Jun 26, 2019 2:31 pm

by jamesh

This thread is for preliminary/anecdotal bug reports on the Buster release.

Once bugs are confirmed, you should use the github repo to make an official report.

For Linux kernel issues: https://github.com/raspberrypi/linux/issues
For Firmware issues: https://github.com/raspberrypi/firmware/issues
For Userland issues (demo apps etc) : https://github.com/raspberrypi/userland/issues
For Raspbian issue: TBD
For Desktop issues: TBD

I will curate this thread, so if I don't think a post is relevant it will be deleted without warning.

Re: Buster bug report thread

Posted: Wed Jun 26, 2019 3:14 pm

by PeterO

Thanks James.... My starter for 10

When running twin headed, it seems that minimizing a window on the second monitor and then expanding it does not remove the "[ ..... ]" around the window name in the task bar (which is on the first monitor).

PeterO

Re: Buster bug report thread

Posted: Wed Jun 26, 2019 3:40 pm

by alnaseh

alnaseh wrote: ↑

Wed Jun 26, 2019 1:42 pm

one change from stretch, iwconfig is not working anymore in rc.local without sudo

Code: Select all

+ iwconfig wlan0 power off
Error for wireless request "Set Power Management" (8B2C) :
    SET failed on device wlan0 ; Invalid argument.

Edit: it is not working with sudo as well, it is working manually from the command line

Code: Select all

pi@raspberrypi:~ $ more /tmp/rc.local.log
+ hostname -I
+ _IP=192.168.1.29
+ [ 192.168.1.29  ]
+ printf My IP address is %s\n 192.168.1.29
My IP address is 192.168.1.29
+ sudo iwconfig wlan0 power off
Error for wireless request "Set Power Management" (8B2C) :
    SET failed on device wlan0 ; Invalid argument.
pi@raspberrypi:~ $ iwconfig
wlan0     IEEE 802.11  ESSID:"JR1"
          Mode:Managed  Frequency:2.437 GHz  Access Point: F0:9F:C2:D7:A7:A9
          Bit Rate=72.2 Mb/s   Tx-Power=31 dBm
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Power Management:on
          Link Quality=48/70  Signal level=-62 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:5  Invalid misc:0   Missed beacon:0

lo        no wireless extensions.

pi@raspberrypi:~ $ sudo iwconfig wlan0 power off
pi@raspberrypi:~ $

Re: Buster bug report thread

Posted: Wed Jun 26, 2019 3:42 pm

by alnaseh

alnaseh wrote: ↑
Wed Jun 26, 2019 6:37 am
OK, this is surprising, the OS team adopted the new java 11 in buster as the default java but it is not supported anymore in the old armv6 (pi0).

this is like discontinuing java totally for Pi zero

the topic is been discussed previously in:
https://www.raspberrypi.org/forums/view ... p?t=196887
https://www.raspberrypi.org/forums/view ... 4#p1461934

there is no way out of this except going back to java 8 in buster

alnaseh wrote: ↑

Wed Jun 26, 2019 6:40 am

also please find the installation error:

Code: Select all

update-alternatives: using /usr/lib/jvm/java-11-openjdk-armhf/bin/jmod to provide /usr/bin/jmod (jmod) in auto mode
update-alternatives: using /usr/lib/jvm/java-11-openjdk-armhf/bin/jps to provide /usr/bin/jps (jps) in auto mode
update-alternatives: using /usr/lib/jvm/java-11-openjdk-armhf/bin/jrunscript to provide /usr/bin/jrunscript (jrunscript) in auto mode
update-alternatives: using /usr/lib/jvm/java-11-openjdk-armhf/bin/jshell to provide /usr/bin/jshell (jshell) in auto mode
update-alternatives: using /usr/lib/jvm/java-11-openjdk-armhf/bin/jstack to provide /usr/bin/jstack (jstack) in auto mode
update-alternatives: using /usr/lib/jvm/java-11-openjdk-armhf/bin/jstat to provide /usr/bin/jstat (jstat) in auto mode
update-alternatives: using /usr/lib/jvm/java-11-openjdk-armhf/bin/jstatd to provide /usr/bin/jstatd (jstatd) in auto mode
update-alternatives: using /usr/lib/jvm/java-11-openjdk-armhf/bin/rmic to provide /usr/bin/rmic (rmic) in auto mode
update-alternatives: using /usr/lib/jvm/java-11-openjdk-armhf/bin/serialver to provide /usr/bin/serialver (serialver) in auto mode
update-alternatives: using /usr/lib/jvm/java-11-openjdk-armhf/bin/jhsdb to provide /usr/bin/jhsdb (jhsdb) in auto mode
Setting up ca-certificates-java (20190405) ...
head: cannot open '/etc/ssl/certs/java/cacerts' for reading: No such file or directory
Error occurred during initialization of VM
Server VM is only supported on ARMv7+ VFP
dpkg: error processing package ca-certificates-java (--configure):
 installed ca-certificates-java package post-installation script subprocess returned error exit status 1
Processing triggers for libc-bin (2.28-10+rpi1) ...
Processing triggers for systemd (241-5+rpi1) ...
Processing triggers for man-db (2.8.5-2) ...
Processing triggers for ca-certificates (20190110) ...
Updating certificates in /etc/ssl/certs...
0 added, 0 removed; done.
Running hooks in /etc/ca-certificates/update.d...

Error occurred during initialization of VM
Server VM is only supported on ARMv7+ VFP
E: /etc/ca-certificates/update.d/jks-keystore exited with code 1.
done.
Errors were encountered while processing:
 ca-certificates-java
E: Sub-process /usr/bin/dpkg returned an error code (1)
pi@raspberrypi:~ $ java
Error occurred during initialization of VM
Server VM is only supported on ARMv7+ VFP

Re: Buster bug report thread

Posted: Wed Jun 26, 2019 4:08 pm

by Andyroo

VNC needs to have the screen resolution set by raspi-config before the first connection else it errors.

Re: Buster bug report thread

Posted: Wed Jun 26, 2019 4:27 pm

by bluesign2k

I found myself needing to re-image an SD that I've been using on a Pi Zero-W yesterday and found that Buster was the current available image.
FWIW, I use the "lite" image and after imaging I put my standard wpa_supplicanf.conf file in boot along with and SSH file so I can do a headless setup and only supply power.

I've used this method (and files) countless times and it works perfectly on Pi2, Pi3B+ and Pi Zero-W, however, this now seem to be broken with the current Buster image. Using an old Stretch image and the same file on the same hardware (Pi, SD, powersupply) and everything works fine.
Doing iwconfig confirms connection to the hotspot, but ifconfig occasionally shows an ipv6 address occasionally, but 9 times out of 10, no ip.

In trying to debug I found that dmesg is spammed is endless coppies of:

Code: Select all

[ 1373.354269] ------------[ cut here ]------------
[ 1373.354809] WARNING: CPU: 0 PID: 341 at drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c:5126 brcmf_cfg80211_set_pmk+0x64/0x84 [brcmfmac]
[ 1373.354890] Modules linked in: cmac bnep hci_uart btbcm serdev bluetooth ecdh_generic 8021q garp stp llc evdev brcmfmac brcmutil sha256_generic raspberrypi_hwmon hwmon snd_bcm2835(C) cfg80211 snd_pcm snd_timer snd rfkill bcm2835_codec(C) bcm2835_v4l2(C) v4l2_mem2mem bcm2835_mmal_vchiq(C) v4l2_common videobuf2_vmalloc videobuf2_dma_contig videobuf2_memops videobuf2_v4l2 videobuf2_common videodev media uio_pdrv_genirq uio fixed ip_tables x_tables ipv6
[ 1373.355127] CPU: 0 PID: 341 Comm: wpa_supplicant Tainted: G        WC        4.19.50+ #896
[ 1373.355136] Hardware name: BCM2835
[ 1373.355198] [<c0017edc>] (unwind_backtrace) from [<c0014e24>] (show_stack+0x20/0x24)
[ 1373.355238] [<c0014e24>] (show_stack) from [<c06b8350>] (dump_stack+0x20/0x28)
[ 1373.355281] [<c06b8350>] (dump_stack) from [<c0024450>] (__warn+0xf4/0x11c)
[ 1373.355310] [<c0024450>] (__warn) from [<c00245a8>] (warn_slowpath_null+0x4c/0x58)
[ 1373.355655] [<c00245a8>] (warn_slowpath_null) from [<bf405aec>] (brcmf_cfg80211_set_pmk+0x64/0x84 [brcmfmac])
[ 1373.357349] [<bf405aec>] (brcmf_cfg80211_set_pmk [brcmfmac]) from [<bf23837c>] (nl80211_set_pmk+0x160/0x1f8 [cfg80211])
[ 1373.358666] [<bf23837c>] (nl80211_set_pmk [cfg80211]) from [<c05f6e94>] (genl_rcv_msg+0x238/0x458)
[ 1373.358718] [<c05f6e94>] (genl_rcv_msg) from [<c05f5eb0>] (netlink_rcv_skb+0x100/0x138)
[ 1373.358751] [<c05f5eb0>] (netlink_rcv_skb) from [<c05f6c48>] (genl_rcv+0x30/0x44)
[ 1373.358780] [<c05f6c48>] (genl_rcv) from [<c05f55dc>] (netlink_unicast+0x1a8/0x23c)
[ 1373.358807] [<c05f55dc>] (netlink_unicast) from [<c05f5a24>] (netlink_sendmsg+0x2f0/0x364)
[ 1373.358839] [<c05f5a24>] (netlink_sendmsg) from [<c058a550>] (sock_sendmsg+0x24/0x34)
[ 1373.358865] [<c058a550>] (sock_sendmsg) from [<c058ad3c>] (___sys_sendmsg+0x20c/0x228)
[ 1373.358889] [<c058ad3c>] (___sys_sendmsg) from [<c058be00>] (__sys_sendmsg+0x5c/0xa0)
[ 1373.358917] [<c058be00>] (__sys_sendmsg) from [<c058be60>] (sys_sendmsg+0x1c/0x20)
[ 1373.358944] [<c058be60>] (sys_sendmsg) from [<c0009000>] (ret_fast_syscall+0x0/0x28)
[ 1373.358955] Exception stack(0xd7d81fa8 to 0xd7d81ff0)
[ 1373.358973] 1fa0:                   01bdd228 01c029f0 00000004 beb88fd0 00000000 00000000
[ 1373.358990] 1fc0: 01bdd228 01c029f0 01bdd1b0 00000128 b6f56000 ffffffff 00000001 00000004
[ 1373.359002] 1fe0: 0000006c beb88f88 b6f3b5bc b6aa1980
[ 1373.359017] ---[ end trace e094f89cb609c038 ]---

For the timebeing I've gone back to Stretch, but am happy to try re-imaging another card to try suggestions for a fix on Buster.

Re: Buster bug report thread

Posted: Wed Jun 26, 2019 5:53 pm

by Silverlock

Short problem description: Audio truncation on playback

Steps taken to produce:

Downloaded the 2019-06-20 Raspbian Buster Lite zip file.

Verified the sha256 sum.

Unzipped the img file and dd'd it to a 16GB SanDisk Ultra uSD card.

Inserted the card into a 3B with only the following plugged in: HDMI monitor, USB keyboard and speakers in the 3.5mm jack.

Powered up the system and logged in.

Entered the following command:

Code: Select all

aplay /usr/share/sounds/alsa/Front_Center.wav

Listened as the speakers played "Front cen", cutting off the end of "center".

Reproduced the problem with various other wav files in the /usr/share/sounds/alsa directory. Playback on all files was truncated to various degrees.

This problem first cropped up in the 4.19.42-v7+ kernel (2019-05-17) and has been reported by more than one user there. And it seems that it's still there in Buster.

Re: Buster bug report thread

Posted: Wed Jun 26, 2019 6:34 pm

by Ernst

Montala wrote: ↑
Wed Jun 26, 2019 6:16 pm
Anyway, the first install went off well (using my own Logitech K400 keyboard & trackpad) although the updating took a fair time, and I made sure to select the UK keyboard option. However, when it loaded into 'Buster' this had reverted to a US Keyboard (@ sign in the wrong place!) which I had to change to the UK option. I was then offered a choice of Character set (I think that's right) but wasn't sure which one to choose!

I have hijacked the above quote because this might be related to something I noticed while installing Buster.
On initial startup I selected Germany but English language, a bit later while trying to access another Pi using ssh I got some error messages concerning locale. I finally fixed the problem by editing /etc/default/locale to set LANG=en_GB.UTF-8.

The image used was: 2019-06-20-raspbian-buster.img. The initial contents of the file /etc/default/locale was:

Code: Select all

#  File generated by update-locale
LANG=en_GB.UTF-8

I selected country Germany, language German, Time zone Berlin, but selected "English language" and deselected "US keyboard.

: P4560347.JPG (185.64 KiB) Viewed 45975 times

Immediately the file /etc/default/locale changed to:
/etc/default/locale:

Code: Select all

#  File generated by update-locale
LANG=en_US.UTF-8
LC_ALL=en_US.UTF-8
LANGUAGE=en_US.UTF-8

With the image 2019-06-20-raspbian-buster-lite.img the contents of /etc/default/locale is as expected:

Code: Select all

#  File generated by update-locale
LANG=en_GB.UTF-8

[Complaint Mode]
For many years I have had discussions at higher levels with Microsoft (and other companies) that country does not imply language and does not imply date format. My residence is in Germany, but I am not a German national, my mother language is not German or English, for historic reasons my preferred language is English but not US english and not South African English, as there is no universal English I normally use UK English, my normal keyboard is German. Why can't I select Country=Germany, Language=UK English, Date Format= UK English, Time Zone=Berlin. And why can I not select the keyboard (German) at this point ?
[/Complaint Mode]

Another test with country Germany, language German, Time zone Berlin, but not "English language" and not "US keyboard. resulted in

Code: Select all

#  File generated by update-locale
LANG=de_DE.UTF-8
LANGUAGE=de_DE.UTF-8
LC_ALL=de_DE.UTF-8

and the keyboard changed to german.

Reminds me of this Alan Parsons song "Damned If I do"

Re: Buster bug report thread

Posted: Thu Jun 27, 2019 6:09 am

by cjan

during boot got this message for minutes then go on
*helper to synchronize boot up for ifupdown
1. Rip2B
2. fresh buster install
3. wifi 8291cu module

Re: Buster bug report thread

Posted: Thu Jun 27, 2019 2:51 pm

by hippy

Using gpiod / libgpiod, what is reported by the gpiod related commands is not the same as reported by the gpio utility. here the UART (14,15) has been enabled for userland use with enable_uart=1

Code: Select all

pi@Pi3B:~/extensions $ gpioinfo
gpiochip0 - 54 lines:
        line   0:      unnamed       unused   input  active-high 
        ... and the exact same all the way to ...
        line  53:      unnamed       unused   input  active-high

Code: Select all

pi@Pi3B:~/extensions $ gpio allreadall
+-----+------+-------+      +-----+------+-------+
| Pin | Mode | Value |      | Pin | Mode | Value |
+-----+------+-------+      +-----+------+-------+
|   0 | OUT  | Low   |      |  27 | IN   | Low   |
|   1 | IN   | High  |      |  28 | IN   | Low   |
|   2 | IN   | High  |      |  29 | IN   | High  |
|   3 | IN   | High  |      |  30 | IN   | Low   |
|   4 | IN   | High  |      |  31 | IN   | Low   |
|   5 | IN   | High  |      |  32 | ALT3 | High  |
|   6 | IN   | High  |      |  33 | ALT3 | High  |
|   7 | IN   | High  |      |  34 | ALT3 | High  |
|   8 | IN   | High  |      |  35 | ALT3 | High  |
|   9 | IN   | Low   |      |  36 | ALT3 | High  |
|  10 | IN   | Low   |      |  37 | ALT3 | High  |
|  11 | IN   | Low   |      |  38 | ALT3 | High  |
|  12 | IN   | Low   |      |  39 | ALT3 | High  |
|  13 | IN   | Low   |      |  40 | ALT0 | Low   |
|  14 | ALT5 | High  |      |  41 | ALT0 | Low   |
|  15 | ALT5 | High  |      |  42 | ALT0 | High  |
|  16 | IN   | Low   |      |  43 | ALT0 | Low   |
|  17 | IN   | Low   |      |  44 | IN   | High  |
|  18 | IN   | Low   |      |  45 | IN   | High  |
|  19 | IN   | Low   |      |  46 | IN   | High  |
|  20 | IN   | Low   |      |  47 | OUT  | High  |
|  21 | IN   | Low   |      |  48 | ALT0 | Low   |
|  22 | IN   | Low   |      |  49 | ALT0 | High  |
|  23 | IN   | Low   |      |  50 | ALT0 | High  |
|  24 | IN   | Low   |      |  51 | ALT0 | High  |
|  25 | IN   | Low   |      |  52 | ALT0 | High  |
|  26 | IN   | Low   |      |  53 | ALT0 | High  |
+-----+------+-------+      +-----+------+-------+

Re: Buster bug report thread

Posted: Thu Jun 27, 2019 6:56 pm

by fd_

Thanks for all your efforts for the new hardware and OS - greatly appreciated!

I just flashed Buster Lite on a fresh SD card and put it into my Pi Zero W. It does boot fine, reports to resize the Boot Partition and boots again. The boot process is also working the second time, but it’s the automatically started update process that’s worrying me a bit: it has been running for multiple hours now, with no more information than something along the lines of “Checking and downloading updates” (seems I can issue commands while the setup is still running, and I made the mistake of running dmesg, so I no longer see the original message). It never reported to have completed. This is the second run of going through the setup process, I rebooted the first one impatiently, and the result was a system with garbled keyboard layout names, so I reflashed.

Is the setup process of a fresh install supposed to take that long? Does it report when it’s finished? Is there any way to see what exactly it’s doing behind the scenes (and get a more fine grained progress report)?

Re: Buster bug report thread

Posted: Thu Jun 27, 2019 8:02 pm

by mark.carline

I am trying to get this Aeotec Z-Stick Gen5, Z-Wave Plus USB to work on Buster:

https://www.amazon.co.uk/Aeotec-Z-Stick ... th=1&psc=1

I don't see this device appear when i connect it:

/dev/ttyACM0

It talks to the device via a serial connection and i then use it via Home Assistant. Has something changed for USB drivers?

I'm going to cross post this over on the HA forum for awareness.
https://community.home-assistant.io/t/t ... rk.carline

I opened this guthub bug report:
https://github.com/raspberrypi/linux/issues/3027

Thanks!

Re: Buster bug report thread

Posted: Thu Jun 27, 2019 8:51 pm

by kevin.shumaker

Not sure if this is the right place, if not would appreciate a point in the right direction.
Using Pi3B.
Using pi-gen dated today, git clone
Using Ubuntu 19.04 fully updated on VBox VM, 100GB local storage, 4GB RAM, 4 core processors.
Ran buld.sh with the following config:
IMG_NAME='KLS'
BASE_DIR=/opt/pi-gen
WORK_DIR=$BASE_DIR/work
DEPLOY_DIR=$BASE_DIR/deploy
DEPLOY_ZIP=1
USE_QEMU=0
FIRST_USER_NAME='pi'
FIRST_USER_PASS='<password>'
WPA_ESSID='<SSID>'
WPA_PASSWORD='<password'
WPA_COUNTRY='US'
ENABLE_SSH=1
Run through build all 3 standard images, no errors or failures.
Burn image using Win32DiskImager to 32GB USB, again, no errors
Insert into PI and boot.
First boot and resize work, auto reboots.
When Desktop comes up in regular or full images, get gray & white desktop, all images/icons/etc are missing showing the broken paper with the red x upper left corner where apps are.
ssh in, run raspi-config edit hostname, enable VNC, reboot
Same screen. First icon iw Chromium, next is folders, next is terminal.

Re: Buster bug report thread

Posted: Thu Jun 27, 2019 9:02 pm

by fd_

fd_ wrote: ↑
Thu Jun 27, 2019 6:56 pm
Thanks for all your efforts for the new hardware and OS - greatly appreciated!

I just flashed Buster Lite on a fresh SD card and put it into my Pi Zero W. It does boot fine, reports to resize the Boot Partition and boots again. The boot process is also working the second time, but it’s the automatically started update process that’s worrying me a bit: it has been running for multiple hours now, with no more information than something along the lines of “Checking and downloading updates” (seems I can issue commands while the setup is still running, and I made the mistake of running dmesg, so I no longer see the original message). It never reported to have completed. This is the second run of going through the setup process, I rebooted the first one impatiently, and the result was a system with garbled keyboard layout names, so I reflashed.

Is the setup process of a fresh install supposed to take that long? Does it report when it’s finished? Is there any way to see what exactly it’s doing behind the scenes (and get a more fine grained progress report)?

I eventually rebooted after some 4 hours, and the result is again that keyboard layout selection is completely garbled (some layout names are displayed in French, some in Dutch, some as black squares, really strange):

Here are the steps that allow me to reproduce the issue:

1) Download the Buster Lite Image from the official website (The checksum does match for my download)
2) Use Etcher on macOS to flash the image (I let Etcher extract the zip for me)
3) Remove and reinsert the card in the MacBook SD slot to mount the boot partition in macOS
4) Duplicate the LICENSE.broadcom file, then rename the duplicate to “ssh” and delete its contents
5) Eject the card and insert into the Pi Zero W (Pi has Internet connection via USB hub + Ethernet dongle)
6) Power up the Pi
7) The Pi will get stuck at “[OK] Started Daily apt upgrade and clean activities.”
At this point, it is possible to use a USB keyboard (attached to aforementioned hub) to log in and issue commands. This allowed me to verify that the Pi has Internet Access (Ping Google.com) and (after having waited for ~4 hours), to reboot via sudo reboot
8) Steps Continue below screenshot

That’s as far as it boots up. No input was entered to this point.

8) Reboot
9) Log in using default credentials (via the Pi itself, ssh is not actually used)
10) Start raspi-config
11) Choose Localisation Options > Change Keyboard Layout
12) Layout names are partly in French, partly in Spanish (or is it Italian?), partly black squares; It’s impossible to find the correct configuration without proper labels. See image above.

Re: Buster bug report thread

Posted: Thu Jun 27, 2019 9:36 pm

by rpdom

It's a known issue with Debian. Being worked on.

Re: Buster bug report thread

Posted: Fri Jun 28, 2019 6:26 am

by mina

Hi,

It seems that the utility nft is not present in the Buster image.

However if I remove, then reinstall iptables, it is correctly installed. See transcript below (on a fresh image, after sudo apt-get update && sudo apt-get dist-upgrade).

Code: Select all

pi@raspberrypi:~ $ sudo iptables -L
Chain INPUT (policy ACCEPT)
target     prot opt source               destination         

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination         

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination         
pi@raspberrypi:~ $ nft
-bash: nft: command not found
pi@raspberrypi:~ $ sudo apt-get remove iptables
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages will be REMOVED:
  iptables
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
After this operation, 1,567 kB disk space will be freed.
Do you want to continue? [Y/n] 
(Reading database ... 37607 files and directories currently installed.)
Removing iptables (1.8.2-4) ...
Processing triggers for man-db (2.8.5-2) ...
pi@raspberrypi:~ $ sudo apt-get install iptables
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following additional packages will be installed:
  libjansson4 libnftables0 nftables
The following NEW packages will be installed:
  iptables libjansson4 libnftables0 nftables
0 upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
Need to get 597 kB of archives.
After this operation, 2,320 kB of additional disk space will be used.
Do you want to continue? [Y/n] 
<SNIP>
pi@raspberrypi:~ $ sudo nft -v
nftables v0.9.0 (Fearless Fosdick)

Re: Buster bug report thread

Posted: Fri Jun 28, 2019 7:40 am

by jojopi

mina wrote: ↑
Fri Jun 28, 2019 6:26 am
The following additional packages will be installed:
libjansson4 libnftables0 nftables

The iptables package recommends nftables, but does not require it. Whether recommended packages are included depends on method and options such as --no-install-recommends.

This is not a bug, unless you are saying that nft is too important to be left out of the image. I do not think it was in the stretch images either.

Re: Buster bug report thread

Posted: Fri Jun 28, 2019 7:52 am

by gordon77

Thonny doesn't work on large python scripts. Fail to load.

Re: Buster bug report thread

Posted: Fri Jun 28, 2019 8:21 am

by fd_

rpdom wrote: ↑
Thu Jun 27, 2019 9:36 pm
It's a known issue with Debian. Being worked on.

Could you clarify which of the bugs reported above you're referring to here? If it's the one I posted above, I'm wondering whether it's the "[OK] Started Daily apt upgrade and clean activities" getting stuck, the garbled keyboard language selection or the combination of the two?

Re: Buster bug report thread

Posted: Fri Jun 28, 2019 8:34 am

by rpdom

fd_ wrote: ↑
Fri Jun 28, 2019 8:21 am

rpdom wrote: ↑
Thu Jun 27, 2019 9:36 pm
It's a known issue with Debian. Being worked on.
Could you clarify which of the bugs reported above you're referring to here? If it's the one I posted above, I'm wondering whether it's the "[OK] Started Daily apt upgrade and clean activities" getting stuck, the garbled keyboard language selection or the combination of the two?

Certainly. I should have made that clear in my original post. It was your one about the keyboard layout being scrambled.

Re: Buster bug report thread

Posted: Fri Jun 28, 2019 8:45 am

by fd_

rpdom wrote: ↑
Fri Jun 28, 2019 8:34 am
Certainly. I should have made that clear in my original post. It was your one about the keyboard layout being scrambled.

Thanks! I'll use ssh for now then. One last question about the "[OK] Started Daily apt upgrade and clean activities" thing: Did this actually get stuck or is there just no more message following as the boot procedure is finished after that?

Re: Buster bug report thread

Posted: Fri Jun 28, 2019 12:03 pm

by mina

jojopi wrote: ↑
Fri Jun 28, 2019 7:40 am

mina wrote: ↑
Fri Jun 28, 2019 6:26 am
The following additional packages will be installed:
libjansson4 libnftables0 nftables
The iptables package recommends nftables, but does not require it. Whether recommended packages are included depends on method and options such as --no-install-recommends.

This is not a bug, unless you are saying that nft is too important to be left out of the image. I do not think it was in the stretch images either.

Thanks for the clarification, did not know as I was completely confused not to find installed by default the tool mentioned in the documentation to configure iptables. I don't say it is important, just that it's a bit confusing. Thanks again.

Re: Buster bug report thread

Posted: Fri Jun 28, 2019 1:37 pm

by greenpid

Chromium is "Aw Snap!" error page too much. example page www.zdnet.com even the forum pages have had the same error.

Have removed the "odblober" whicjh is added for everyone as this was giving error reports saying it had to restart. but still having the problem using the browers on a pi4 1GB ram. (up todate (update/upgrade) done 20 mins ago . 14:40 28/6/19

Re: Buster bug report thread

Posted: Fri Jun 28, 2019 5:17 pm

by PeterO

When booting a twin headed setup, it seems sensitive to both monitors being powered up (i.e. not in stand-by/sleep mode) If HDMI-1's monitor is sleeping then no video is seen on HDMI-0's monitor. I don't know if linux has started or not. Next time it happens I'll try pinging it from another machine.

PeterO

Re: Buster bug report thread

Posted: Fri Jun 28, 2019 5:35 pm

by globiboulga666

Hi,

EDIT : it's a DHCPCD5 problem. I had to remove it, and install Wicd instead.

WiFi handling problem with new Raspbian 10 Buster new version of the Network Manager : it cannot handle anymore USB WiFi Dongle TP-Link TL-WN722N (V2) (while was working fine with Raspbian 9 Stretch).

Despite the fact this WiFi dongle is still working fine by manual commands !!

It's based on Realtek rtl8188eu, and it still works fine by manual wpa_supplicant command for connecting to WiFi so it seems to be related to a regression into the Network Manager. However, this regression doesn't appear to cause issue on an Ralink USB WiFi dongle (Tenda W311U : Ralink Technology, Corp. RT2870/RT3070 Wireless Adapter), and no issue with the integrated WiFi module of RPi 3 and +.

It's not about kernel, firmware-realtek, or wpasupplicant :
After rpi-update to 4.19.56-v7+ on both Raspbian 9 and 10, no change. No differences between Raspbian 9 and 10 firmware realtek files : /lib/firmware/rtlwifi/rtl8188* files are the same (checkum compared). It's not a failure inside wpasupplicant : it works both on Raspbian 9 and 10 with manual wpa_supplicant command :

Code: Select all

root@Pi2-Cam-Crypte:~# wpa_supplicant -Dwext -iwlan0 -c /etc/wpa_supplicant/wpa_supplicant.conf
Successfully initialized wpa_supplicant
rfkill: Cannot get wiphy information
ioctl[SIOCSIWAP]: Operation not permitted
ioctl[SIOCSIWENCODEEXT]: Invalid argument
ioctl[SIOCSIWENCODEEXT]: Invalid argument
wlan0: Trying to associate with 30:b5:c2:7f:46:16 (SSID='WeeFee-2.4GHz' freq=2412 MHz)
Failed to add supported operating classes IE
wlan0: Association request to the driver failed
wlan0: Associated with 30:b5:c2:7f:46:16
wlan0: WPA: Key negotiation completed with 30:b5:c2:7f:46:16 [PTK=CCMP GTK=CCMP]
wlan0: CTRL-EVENT-CONNECTED - Connection to 30:b5:c2:7f:46:16 completed [id=0 id_str=]
(here, it's connected)

For more informations :

Code: Select all

root@Pi2-Cam-Crypte:~# lsusb
Bus 001 Device 005: ID 2357:010c TP-Link TL-WN722N v2
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Code: Select all

root@Pi2-Cam-Crypte:~# lsmod
Module                  Size  Used by
r8188eu               438272  0
lib80211               16384  1 r8188eu
fuse                  110592  3
ctr                    16384  0
aes_arm_bs             20480  0
crypto_simd            16384  1 aes_arm_bs
cryptd                 24576  1 crypto_simd
ccm                    20480  0
8021q                  32768  0
garp                   16384  1 8021q
stp                    16384  1 garp
llc                    16384  2 garp,stp
arc4                   16384  0
rt2800usb              28672  0
rt2800lib             102400  1 rt2800usb
rt2x00usb              24576  1 rt2800usb
rt2x00lib              57344  3 rt2800lib,rt2800usb,rt2x00usb
mac80211              692224  3 rt2800lib,rt2x00lib,rt2x00usb
sha256_generic         20480  0
cfg80211              614400  3 rt2x00lib,mac80211,r8188eu
rfkill                 28672  2 cfg80211
crc_ccitt              16384  1 rt2800lib
snd_bcm2835            24576  2
raspberrypi_hwmon      16384  0
bcm2835_codec          36864  0
hwmon                  16384  1 raspberrypi_hwmon
snd_pcm               102400  1 snd_bcm2835
bcm2835_v4l2           45056  0
v4l2_mem2mem           24576  1 bcm2835_codec
v4l2_common            16384  1 bcm2835_v4l2
bcm2835_mmal_vchiq     32768  2 bcm2835_codec,bcm2835_v4l2
snd_timer              32768  1 snd_pcm
videobuf2_vmalloc      16384  1 bcm2835_v4l2
videobuf2_dma_contig    20480  1 bcm2835_codec
videobuf2_memops       16384  2 videobuf2_dma_contig,videobuf2_vmalloc
snd                    73728  7 snd_timer,snd_bcm2835,snd_pcm
videobuf2_v4l2         24576  3 bcm2835_codec,bcm2835_v4l2,v4l2_mem2mem
videobuf2_common       45056  4 bcm2835_codec,bcm2835_v4l2,v4l2_mem2mem,videobuf2_v4l2
videodev              200704  6 bcm2835_codec,v4l2_common,videobuf2_common,bcm2835_v4l2,v4l2_mem2mem,videobuf2_v4l2
media                  36864  2 videodev,v4l2_mem2mem
uio_pdrv_genirq        16384  0
uio                    20480  1 uio_pdrv_genirq
fixed                  16384  0
i2c_dev                20480  0
ip_tables              24576  0
x_tables               32768  1 ip_tables
ipv6                  450560  26

Before manual connection :

Code: Select all

pi@Pi2-Cam-Crypte:~ $ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether b8:27:eb:93:c3:4a brd ff:ff:ff:ff:ff:ff
    inet 192.168.28.105/24 brd 192.168.28.255 scope global noprefixroute eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::b9d1:d4a0:6d1c:9ee1/64 scope link 
       valid_lft forever preferred_lft forever
3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether c0:25:e9:1f:7c:a9 brd ff:ff:ff:ff:ff:ff

Code: Select all

root@Pi2-Cam-Crypte:~# iwlist scan
wlan0     Scan completed :
          Cell 01 - Address: 30:B5:C2:7F:46:16
                    ESSID:"WeeFee-2.4GHz"
                    Protocol:IEEE 802.11bgn
                    Mode:Master
                    Frequency:2.412 GHz (Channel 1)
                    Encryption key:on
                    Bit Rates:130 Mb/s
                    Extra:rsn_ie=30140100000fac040100000fac040100000fac020000
                    IE: IEEE 802.11i/WPA2 Version 1
                        Group Cipher : CCMP
                        Pairwise Ciphers (1) : CCMP
                        Authentication Suites (1) : PSK
                    Quality=0/100  Signal level=60/100  
          Cell 02 - Address: 18:1E:78:52:55:C8
                    ESSID:"Livebox-55C8"
                    Protocol:IEEE 802.11bgn
                    Mode:Master
                    Frequency:2.412 GHz (Channel 1)
                    Encryption key:on
                    Bit Rates:144 Mb/s
                    Extra:wpa_ie=dd1a0050f20101000050f20202000050f2040050f20201000050f202
                    IE: WPA Version 1
                        Group Cipher : TKIP
                        Pairwise Ciphers (2) : CCMP TKIP
                        Authentication Suites (1) : PSK
                    Extra:rsn_ie=30180100000fac020200000fac04000fac020100000fac020c00
                    IE: IEEE 802.11i/WPA2 Version 1
                        Group Cipher : TKIP
                        Pairwise Ciphers (2) : CCMP TKIP
                        Authentication Suites (1) : PSK
                    IE: Unknown: DD8F0050F204104A0001101044000102103B00010310470010383F384C3E3FFC39FC3C4A3F383F384C10210008536167656D636F6D10230016536167656D636F6D46617374333936355F4C42322E381024000C53475F4C42335F312E322E33104200094C4B313530353046461054000800060050F204000110110000100800020006103C0001011049000600372A000120
                    Quality=0/100  Signal level=23/100  
          Cell 03 - Address: 52:33:8E:E9:A8:71
                    ESSID:"orange"
                    Protocol:IEEE 802.11bgn
                    Mode:Master
                    Frequency:2.437 GHz (Channel 6)
                    Encryption key:off
                    Bit Rates:130 Mb/s
                    Quality=0/100  Signal level=23/100  
          Cell 04 - Address: BC:C3:42:68:0F:E8
                    ESSID:"orange"
                    Protocol:IEEE 802.11bgn
                    Mode:Master
                    Frequency:2.437 GHz (Channel 6)
                    Encryption key:off
                    Bit Rates:108 Mb/s
                    Quality=0/100  Signal level=23/100  
          Cell 05 - Address: 5C:33:8E:E9:A8:71
                    ESSID:"Livebox-1b65"
                    Protocol:IEEE 802.11bgn
                    Mode:Master
                    Frequency:2.437 GHz (Channel 6)
                    Encryption key:on
                    Bit Rates:130 Mb/s
                    Extra:wpa_ie=dd1a0050f20101000050f20202000050f2040050f20201000050f202
                    IE: WPA Version 1
                        Group Cipher : TKIP
                        Pairwise Ciphers (2) : CCMP TKIP
                        Authentication Suites (1) : PSK
                    Extra:rsn_ie=30180100000fac020200000fac04000fac020100000fac020000
                    IE: IEEE 802.11i/WPA2 Version 1
                        Group Cipher : TKIP
                        Pairwise Ciphers (2) : CCMP TKIP
                        Authentication Suites (1) : PSK
                    IE: Unknown: DD210050F204104A00011010440001021011000F4C697665626F782046545448207632
                    Quality=0/100  Signal level=23/100  
          Cell 06 - Address: 72:5D:51:9B:28:25
                    ESSID:"SFR WiFi Mobile"
                    Protocol:IEEE 802.11bgn
                    Mode:Master
                    Frequency:2.462 GHz (Channel 11)
                    Encryption key:on
                    Bit Rates:144 Mb/s
                    Extra:rsn_ie=30140100000fac040100000fac040100000fac010000
                    IE: IEEE 802.11i/WPA2 Version 1
                        Group Cipher : CCMP
                        Pairwise Ciphers (1) : CCMP
                        Authentication Suites (1) : 802.1x
                    Quality=0/100  Signal level=23/100  
          Cell 07 - Address: E4:5D:51:9B:28:26
                    ESSID:"SFR_2820"
                    Protocol:IEEE 802.11bgn
                    Mode:Master
                    Frequency:2.462 GHz (Channel 11)
                    Encryption key:on
                    Bit Rates:144 Mb/s
                    Extra:wpa_ie=dd1a0050f20101000050f20202000050f2040050f20201000050f202
                    IE: WPA Version 1
                        Group Cipher : TKIP
                        Pairwise Ciphers (2) : CCMP TKIP
                        Authentication Suites (1) : PSK
                    Extra:rsn_ie=30180100000fac020200000fac04000fac020100000fac020c00
                    IE: IEEE 802.11i/WPA2 Version 1
                        Group Cipher : TKIP
                        Pairwise Ciphers (2) : CCMP TKIP
                        Authentication Suites (1) : PSK
                    IE: Unknown: DD8D0050F204104A0001101044000102103B00010310470010000000000000000000000000000000001021000D4E42365641432D4658432D72301023000D4E42365641432D4658432D72301024000D4E42365641432D4658432D72301042000C4534354435313942323832301054000800060050F2040001101100085346525F32383230100800020480103C000101
                    Quality=0/100  Signal level=23/100  
          Cell 08 - Address: 72:5D:51:9B:28:27
                    ESSID:"SFR WiFi FON"
                    Protocol:IEEE 802.11bgn
                    Mode:Master
                    Frequency:2.462 GHz (Channel 11)
                    Encryption key:off
                    Bit Rates:144 Mb/s
                    Quality=0/100  Signal level=23/100  

lo        Interface doesn't support scanning.

eth0      Interface doesn't support scanning.

root@Pi2-Cam-Crypte:~#

After manual connection with wpa_supplicant command :

Code: Select all

pi@Pi2-Cam-Crypte:~ $ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether b8:27:eb:93:c3:4a brd ff:ff:ff:ff:ff:ff
    inet 192.168.28.105/24 brd 192.168.28.255 scope global noprefixroute eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::b9d1:d4a0:6d1c:9ee1/64 scope link 
       valid_lft forever preferred_lft forever
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether c0:25:e9:1f:7c:a9 brd ff:ff:ff:ff:ff:ff
    inet 192.168.28.115/24 brd 192.168.28.255 scope global noprefixroute wlan0
       valid_lft forever preferred_lft forever
    inet6 fe80::e289:613a:e255:1ffb/64 scope link 
       valid_lft forever preferred_lft forever

Code: Select all

pi@Pi2-Cam-Crypte:~ $ iwconfig
wlan0     IEEE 802.11bgn  ESSID:"WeeFee-2.4GHz"  Nickname:"<WIFI@REALTEK>"
          Mode:Managed  Frequency:2.412 GHz  Access Point: 30:B5:C2:7F:46:16   
          Bit Rate:65 Mb/s   Sensitivity:0/0  
          Retry:off   RTS thr:off   Fragment thr:off
          Power Management:off
          Link Quality=100/100  Signal level=84/100  Noise level=0/100
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

lo        no wireless extensions.

eth0      no wireless extensions.

Does anyone know what changed about WiFi configuration between Raspbian 9 and Raspbian 10 ? Because something was working better before !
Thanks in advance.