Gadgetguy
Posts: 100
Joined: Fri Aug 15, 2014 2:55 am

Re: Buster bug report thread

Mon Jul 15, 2019 7:53 am

Gadgetguy wrote:
Sun Jun 30, 2019 9:44 pm
I guess this post may not qualify as an official bug report but is more my somewhat subjective but distinct impressions of problems I experienced with Raspbian Buster. I loaded a fresh Buster image onto a 32gb Samsung Evo plus sd for my Raspberry Pi 3B. (It is not my fastest sd card - my sandisk extreme plus 32 gb seems to me to be more responsive on things like web browsing etc. but the samsung evo plus still has a pretty good reputation as a speedy card for the Raspberry Pi.)

As I do in stretch, I allocated 128gb ram to the gpu and used the legacy graphics driver. The comparison I make below is for this same card running stretch versus buster

My “impression” is that the Chromium browser version 72 in Stretch is on a 3B noticeably faster, more fluid and responsive and uses less cpu and ram and consequently runs at a lower cpu temperature than Chromium version 74 in Buster. I find in Buster I get frequent temperature warnings that I rarely get in stretch. Buster loads tabs more slowly switches between tabs with more difficulty, and starts to slow down, freeze or overheat with fewer tabs open. I am wondering if Raspbian Buster’s Chromium browser has been optimized for the new Raspberrry 4 at the expense of the experience on older Pi’s. Will stretch’s Chromium be updated periodically as in the past or will it be frozen.

I have done the Ookla internet speed test a number of times with both OS on this same card and I consistently get much higher internet speeds on the Stretch system. (This test may not be definitive because my internet speeds of late seem to fluctuate even operating on the same system)

I am wondering if anyone else has experienced these problems with older Raspberry Pis on Buster’s Chromium browser using the legacy driver? The Chromium experience on Buster with an older pi using the fkms driver is even more problematic with more frequent freezes and artifacts that stay on the screen untill reboot.

On Stretch I enjoy using vlc player and also omxplayer ( omxplayergui) and they both work well on Buster with the legacy driver. I am wondering if Vlc on stretch will be kept up to date to reflect changes in youtube code etc? I guess if we use fkms on Buster we will lose osd timings and subtitles on omxplayer?


However on Stretch I also use mpv video player (compiled with mmal enabled in ffmpeg) with smplayer as a gui. So far I have not succeeded in getting it to work satisfactorily with hw acceleration in Buster and I don’t want to lose it.

On stretch mpv in smplayer plays just about any video format up to 1080p
( although some in software). By configuring smplayer to open mpv in mpv’s own (overlay) window and by toggling back and forth between full screen and a small defined window I can get gui control of mpv which opens up all kinds of options. Smplayer in addition to using youtube-dl has its own very fast internal youtube code that is kept up to date and by using the open with extension by G Lankow in the Chrome store I am able to speedily and efficiently browse youtube videos and watch them either full screen or in a small overlay window defined as a specific size and at a specific unobtrusive location on the screen so as to permit multi-tasking. To make a long story short I really do not want to lose a functional mpv player on Buster. Has anyone been able to get mpv working in Buster with an older pi?

On Buster using fkms graphics driver and the ffmpeg preinstalled in Buster and the mpv in the buster repository and configuring mpv to use the default gpu driver mpv will play a play a 1080p youtube video albeit at very high cpu usage which quickly results in overheating.

It also “seems” to me that Buster in general is somewhat more prone to overheating in an older Pi.
I do note that glxgears now seems to work fine with the legacy driver.

I look forward to getting a Raspberry Pi 4 at some point but I hope to keep my older Pis working just as well as they did in Stretch.

I hereby retract my above noted bug report(which nobody was paying any attention to anyways!! :lol: After experimentation and/or modifications or updates to my buster os on pi 3b everthing I complained about seems to be somewhat copacetic. I now have mpv and smplayer working with mmal hw acceleration and running chromium no longer seems to generate excessive cpu usage and overheating although with chromium it still seems to operate with higher cpu usage and at a higher temperature than in stretch. At the time of my original comments I had been experiencing some intermittent problems with my internet connection speed which may have been part of the problem and I have also made updates and some modifications on buster that I had enabled on stretch, such as enabling zram, reducing swappiness, and changing my hosts file a la:

"Blocking Unwanted Connections with a Hosts File"

http://winhelp2002.mvps.org/hosts.htm

I now anxiously and hopefully look forward to an rpi optimized kodi on buster. I appreciate the fact that vlc is now playing formats other than h264 albeit partially in software.
Last edited by Gadgetguy on Mon Jul 15, 2019 8:14 am, edited 1 time in total.

gordon77
Posts: 4297
Joined: Sun Aug 05, 2012 3:12 pm

Re: Buster bug report thread

Mon Jul 15, 2019 8:04 am

gordon77 wrote:
Fri Jun 28, 2019 7:52 am
Thonny doesn't work on large python scripts. Fail to load.
It did actually load after 4min 50secs.

I reported this on the Thonny github issues page and are l am very pleased they have worked on it and solved it, much appreciated :D

Ark_42
Posts: 28
Joined: Tue Sep 04, 2012 5:09 pm

Pi zero brcmfmac problem

Mon Jul 15, 2019 12:57 pm

After nearly 24 hours running ok my zero W locked up. after reloading I find the following in /var/log/kern.log with cat kern.log | grep brcm

Jul 15 07:52:29 raspberrypi kernel: [39735.259739] brcmfmac: brcmf_escan_timeout: timer expired
Jul 15 11:09:54 raspberrypi kernel: [51579.996447] brcmfmac: brcmf_sdio_hostmail: mailbox indicates firmware halted
Jul 15 11:10:22 raspberrypi kernel: [51607.931377] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
Jul 15 11:10:22 raspberrypi kernel: [51607.934958] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
Jul 15 11:10:22 raspberrypi kernel: [51607.934985] brcmfmac: brcmf_run_escan: error (-110)
Jul 15 11:10:22 raspberrypi kernel: [51607.935000] brcmfmac: brcmf_cfg80211_scan: scan error (-110)
Jul 15 11:11:22 raspberrypi kernel: [51667.931975] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
Jul 15 11:11:22 raspberrypi kernel: [51667.935561] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
Jul 15 11:11:22 raspberrypi kernel: [51667.935588] brcmfmac: brcmf_run_escan: error (-110)
Jul 15 11:11:22 raspberrypi kernel: [51667.935603] brcmfmac: brcmf_cfg80211_scan: scan error (-110)
Jul 15 11:12:22 raspberrypi kernel: [51727.932584] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
Jul 15 11:12:22 raspberrypi kernel: [51727.936181] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
Jul 15 11:12:22 raspberrypi kernel: [51727.936207] brcmfmac: brcmf_run_escan: error (-110)
Jul 15 11:12:22 raspberrypi kernel: [51727.936224] brcmfmac: brcmf_cfg80211_scan: scan error (-110)
Jul 15 11:13:22 raspberrypi kernel: [51787.933179] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
Jul 15 11:13:22 raspberrypi kernel: [51787.936768] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
Jul 15 11:13:22 raspberrypi kernel: [51787.936794] brcmfmac: brcmf_run_escan: error (-110)
Jul 15 11:13:22 raspberrypi kernel: [51787.936810] brcmfmac: brcmf_cfg80211_scan: scan error (-110)
Jul 15 11:14:22 raspberrypi kernel: [51847.933773] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
Jul 15 11:14:22 raspberrypi kernel: [51847.937337] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
Jul 15 11:14:22 raspberrypi kernel: [51847.937364] brcmfmac: brcmf_run_escan: error (-110)
Jul 15 11:14:22 raspberrypi kernel: [51847.937379] brcmfmac: brcmf_cfg80211_scan: scan error (-110)
Jul 15 11:15:22 raspberrypi kernel: [51907.934358] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
Jul 15 11:15:22 raspberrypi kernel: [51907.937931] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
Jul 15 11:15:22 raspberrypi kernel: [51907.937957] brcmfmac: brcmf_run_escan: error (-110)
Jul 15 11:15:22 raspberrypi kernel: [51907.937973] brcmfmac: brcmf_cfg80211_scan: scan error (-110)
Jul 15 11:16:22 raspberrypi kernel: [51967.934957] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
Jul 15 11:16:22 raspberrypi kernel: [51967.938521] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
Jul 15 11:16:22 raspberrypi kernel: [51967.938547] brcmfmac: brcmf_run_escan: error (-110)

any ideas ?

Richard

beta-tester
Posts: 1249
Joined: Fri Jan 04, 2013 1:57 pm
Location: de_DE

Re: Buster Lite image too large for 2GB SD card

Mon Jul 15, 2019 1:05 pm

PINGeV wrote:
Mon Jul 15, 2019 7:15 am
I wanted to upgrade Raspbian Buster on my old Raspberry Pi 1 with its 2GB SD card.
you can upgrade your running stretch installation to buster, as described "Buster – the new version of Raspbian", with:

Code: Select all

sudo sed -i "s/stretch/buster/g" /etc/apt/sources.list
sudo sed -i "s/stretch/buster/g" /etc/apt/sources.list.d/raspi.list

sudo apt update -y
sudo apt dist-upgrade -y --auto-remove
sudo apt purge -y --auto-remove timidity lxmusic gnome-disk-utility deluge-gtk evince wicd wicd-gtk clipit usermode gucharmap gnome-system-tools pavucontrol

sudo apt autoremove -y --purge
sudo apt autoclean -y
... but you need space to upgrade... ;)

Please slightly shrink the rootfs partition so the entire image once again fits onto a 2GB SD card.
what are your exact whishes...? each SD card has slightly different bytes available... please tell us your exact bytes count available on your SD card.

PS: Please don't tell me to throw away my SD card and buy a new one. 2GB is plenty.
nooo... i don't do it... but you know, 2GB are far from the minimum requirements. that is 4GB for a very long time already.
SD card size (capacity).

EDIT:
I also tried to shrink the image myself but it didn't boot
how did you tried it?
if you changed the UUID of your partition/-table, as some programs will do, you have to adjust the boot option to yours in the /boot/cmdline.txt file.
"... root=PARTUUID=bd17b13d-02 ..."
and the options in /etc/fstab
PARTUUID=bd17b13d-01 /boot ...
PARTUUID=bd17b13d-02 / ...

otherwise the kernel does not know what to mount.
{ I only give negative feedback }
RPi B (rev1, 256MB), B (rev2, 512MB), B+, 2B, 3B, 3B+, ZeroW, 4B (4GB), ...

tinker2much
Posts: 73
Joined: Wed Jun 20, 2018 12:38 am

Re: Buster bug report thread

Mon Jul 15, 2019 8:14 pm

A "TP-Link Wireless N Nano USB Adapter TL-WN725N" does not work on a Pi Zero under Buster, although it works with Stretch."

As reported above, my previously working wireless dongle isn't working under Buster.

Is there any further information I can provide to help the more knowledgable?

Is there anything that I can do on my own to get around this?

User avatar
PINGeV
Posts: 5
Joined: Fri Feb 23, 2018 7:24 am

Re: Buster Lite image too large for 2GB SD card

Mon Jul 15, 2019 9:26 pm

beta-tester wrote:
Mon Jul 15, 2019 1:05 pm
PINGeV wrote:
Mon Jul 15, 2019 7:15 am
I wanted to upgrade Raspbian Buster on my old Raspberry Pi 1 with its 2GB SD card.
you can upgrade your running stretch installation to buster, as described "Buster – the new version of Raspbian", with:

Code: Select all

sudo sed -i "s/stretch/buster/g" /etc/apt/sources.list
sudo sed -i "s/stretch/buster/g" /etc/apt/sources.list.d/raspi.list

sudo apt update -y
sudo apt dist-upgrade -y --auto-remove
sudo apt purge -y --auto-remove timidity lxmusic gnome-disk-utility deluge-gtk evince wicd wicd-gtk clipit usermode gucharmap gnome-system-tools pavucontrol

sudo apt autoremove -y --purge
sudo apt autoclean -y
... but you need space to upgrade... ;)

Please slightly shrink the rootfs partition so the entire image once again fits onto a 2GB SD card.
what are your exact whishes...? each SD card has slightly different bytes available... please tell us your exact bytes count available on your SD card.
A 2GB card should be guaranteed to have at least 2000000000 bytes. My particular card has 2028994560 bytes according to "lsblk -b" but that doesn't really matter.
PS: Please don't tell me to throw away my SD card and buy a new one. 2GB is plenty.
nooo... i don't do it... but you know, 2GB are far from the minimum requirements. that is 4GB for a very long time already.
SD card size (capacity).
Oh, I didnt see it mentioned on the download page.
EDIT:
I also tried to shrink the image myself but it didn't boot
how did you tried it?
if you changed the UUID of your partition/-table, as some programs will do, you have to adjust the boot option to yours in the /boot/cmdline.txt file.
"... root=PARTUUID=bd17b13d-02 ..."
and the options in /etc/fstab
PARTUUID=bd17b13d-01 /boot ...
PARTUUID=bd17b13d-02 / ...

otherwise the kernel does not know what to mount.
Thats a good clue, thanks!

User avatar
PINGeV
Posts: 5
Joined: Fri Feb 23, 2018 7:24 am

Re: Buster Lite image too large for 2GB SD card

Mon Jul 15, 2019 9:46 pm

beta-tester wrote:
Mon Jul 15, 2019 1:05 pm
I also tried to shrink the image myself but it didn't boot
how did you tried it?
if you changed the UUID of your partition/-table, as some programs will do, you have to adjust the boot option to yours in the /boot/cmdline.txt file.
"... root=PARTUUID=bd17b13d-02 ..."
and the options in /etc/fstab
PARTUUID=bd17b13d-01 /boot ...
PARTUUID=bd17b13d-02 / ...

otherwise the kernel does not know what to mount.
That did the trick. I had to make three changes after using PiShrink from https://github.com/Drewsif/PiShrink

1. edit boot/cmdline.txt to update the PARTUUID
2. edit rootfs/etc/fstab to update the PARTUUID
3. empty rootfs/etc/rc.local to stop the broken partition resizing. It uses the partition resizing provided by Raspbian instead.

k7qo
Posts: 2
Joined: Tue Jul 16, 2019 4:48 pm

Re: Buster bug report thread

Tue Jul 16, 2019 5:08 pm

mgdiff broken

I may have needed to post here first. My apologies if I made a mistake.
Here is output from use of mgdiff. Diff works OK, but I need the graphical display for more complex searches.

pi@raspberrypi ~/rt01 $ mgdiff 001.out.opt new.out
Warning: Cannot convert string "7x13bold" to type FontStruct
Xt Warning: Cannot convert string "variable" to type FontStruct
X Error of failed request: BadName (named color or font does not exist)
Major opcode of failed request: 45 (X_OpenFont)
Serial number of failed request: 532
Current serial number in output stream: 533
pi@raspberrypi ~/rt01 $

or is it user error with x-server?

linux_author
Posts: 248
Joined: Sat Apr 02, 2016 7:04 pm
Location: Gulf of Mexico
Contact: Website

Re: Buster bug report thread

Tue Jul 16, 2019 9:11 pm

ShiftPlusOne wrote:
Mon Jul 08, 2019 12:20 pm
linux_author wrote:
Sun Jul 07, 2019 3:54 pm
alas, while gqrx and Buster readily supports the RTL-SDR on my RPi3Bs (works great!), it looks like SDR radio is a no-go on my RPi4 2GB...
It's being looked into:
https://github.com/raspberrypi/linux/issues/3060
update: ordered and received a "NooElec NESDR XTR+ Tiny Extended-Range TCXO-Based RTL-SDR & DVB-T USB Stick (RTL2832U + E4000) w/Antenna and Remote Control," which according to the seller, contains "an ultra-rare E4000 tuner chip," made by Elonics, "the maker of the E4000 integrated circuit," which "went out of business years ago."

So, not a mainstream usb sdr, but I plugged it into my new RPi 4 4GB, and it automagically works well using the previously installed rtl-sdr drivers... shame about the rtl-sdr, which is much more common... but at least i can proceed with my portable Pi Panadapter for ham radio use:

https://kg4zqz.blogspot.com/2019/07/ras ... r-for.html

(as an aside, this stick does not get hot like other sdr thumbs... was barely warm after a half-hour of use)

willie
on the Gulf of Mexico

UPDATE: looks like the issue is fixed - but one has to wonder how long before the merge 'emerges' into a new Raspbian release? anyhow, thanks to the engineers for the support - rtl-sdr users really like the RPi platform and the new RPi 4 is just perfect!
Last edited by linux_author on Thu Jul 18, 2019 11:46 am, edited 2 times in total.

Gadgetguy
Posts: 100
Joined: Fri Aug 15, 2014 2:55 am

Re: Buster bug report thread

Thu Jul 18, 2019 2:04 am

A minor bug, but perhaps indicative of a little problem on raspbian buster
(on the Pi 3 B )is the following:

On raspbian stretch, vlc will play the webm vp9 file listed below with at least the
appearance of fluidity albeit at fairly high cpu usage ~ 70% ( mpv ~30%) whereas
on raspbian buster vlc and mpv play the video filled with artifacts and pixellation and smearing:

https://commons.wikimedia.org/wiki/File ... .webm#file
Last edited by Gadgetguy on Fri Jul 19, 2019 10:02 am, edited 2 times in total.

Hillybilly
Posts: 4
Joined: Sun Mar 01, 2015 8:27 pm

Re: Buster bug report thread

Thu Jul 18, 2019 11:16 am

NetworkManager not functioning in 2019-07-10-raspbian-buster-lite.img. Is in /usr/lib/ but service not found. Not in /etc/. No nmcli or any other tools, no wifi, no update. Makes my Pi zero w like a (small) brick. Help appreciated

ShiftPlusOne
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 6084
Joined: Fri Jul 29, 2011 5:36 pm
Location: The unfashionable end of the western spiral arm of the Galaxy

Re: Buster bug report thread

Thu Jul 18, 2019 11:32 am

The default setup uses dhcpcd, not NetworkManager.

AshleyScirra
Posts: 4
Joined: Tue Jan 05, 2016 2:53 pm

Re: Buster bug report thread

Thu Jul 18, 2019 1:02 pm

I just got my Raspberry Pi 4, flashed a fresh Raspbian Buster, and ensured everything was up-to-date. I was keen to check the WebGL support in Chromium.

It looks like it supports WebGL 2 out of the box which is great, but there is a severe rendering issue that causes WebGL content to appear incorrectly. Try this URL: https://www.scirra.com/demos/c2/sbperftest/index.html

On all other systems it looks correct. On the Raspberry Pi 4 in Chromium it looks like many of the quads render with the wrong texture.

This looks like the graphics driver bug. Is there somewhere else I should report it?

User avatar
GavinW
Posts: 90
Joined: Tue Nov 01, 2011 8:11 pm
Location: UK
Contact: Website

Re: Buster bug report thread

Thu Jul 18, 2019 7:56 pm

Excuse me if this has been raised in another post. I got my Rpi4 today and installed Raspbian Buster (full install). All went well until I ticked OpenBox Configuration Manager in Preferences -> Main Menu Editor and then tried to use it to shuffle the window furniture icons, as I could in Stretch. The result was that windows could not be moved or closed (except from the Menu Bar). I could only get out of this by reinstalling Buster. I suspect that if I was not a total newbie I might not be quite so surprised. Am I right in thinking that Buster's default GUI is not yet totally debugged?
otium negare negotium vanum

Giga_Pi
Posts: 42
Joined: Mon May 20, 2019 9:48 am

Don't want Raspian Buster!

Fri Jul 19, 2019 7:01 am

Question: Does anyone have any logical explanation as to why KDE Plasma doesn't work on Raspian buster with OpenGL turned on, but yet works with Raspian Stretch with OpenGL turned on?

Thanks
Microsoft can't help their neighbors, that's bad, hackers, that's bad!

AmigaGamer
Posts: 93
Joined: Sat Feb 01, 2014 9:02 pm

Libreoffice Base

Sat Jul 20, 2019 12:54 pm

The included LibreOffice suite in the Raspbian image is not detecting a JAVA environment. his is required to create and work with Databases .

libreoffice base, libreoffice-java-common and a java environment are installed as part of the raspbian image . I'm Not sure if this is raspbian specific, or affects all versions of buster - but as its part of the default software suite, i figured it would be worth mentioning here.

Steps to reproduce.
Create a new libreoffice database - hsqldb embedded
follow the wizard through until you create a blank database.
After saving the database you will get a "no java installation can be found error"

Options/Advanced shows no installed JRE environments.

ksea
Posts: 1
Joined: Wed Jan 02, 2019 5:17 pm

Re: Buster bug report thread

Sat Jul 20, 2019 9:37 pm

GavinW wrote:
Thu Jul 18, 2019 7:56 pm
. All went well until I ticked OpenBox Configuration Manager in Preferences -> Main Menu Editor and then tried to use it to shuffle the window furniture icons, as I could in Stretch. The result was that windows could not be moved or closed (except from the Menu Bar).
I just hit the same problem via different route. Using a new image of Buster Lite on a 3B+, with subsequent install via terminal of the desktop environment. Everything seemed to be working fine until from terminal, I typed “obconf” which brought up openbox GUI, then I clicked on the original Pixel theme/settings and closed the GUI. From that point, I can’t close, move, or resize any windows, although the menu bar worked. Rebooting didn’t help. I’m not sure when I’ll have time to attempt reinstalling everything, so I’m posting the bug now.

I had to change the openbox settings, because the minimize window icon (a down arrow) and maximize icon (up arrow) were driving me crazy. I kept hitting the up arrow by mistake to try to minimize the window, since minimizing windows animate up into the dock/taskbar. But the up arrow maximizes the window. I’d recommend keeping the line-box-X convention for windows min/max/close icons.

tinker2much
Posts: 73
Joined: Wed Jun 20, 2018 12:38 am

Re: Buster bug report thread

Sun Jul 21, 2019 3:54 pm

This was my problem:
A "TP-Link Wireless N Nano USB Adapter TL-WN725N" does not work on a Pi Zero under Buster, although it works with Stretch."

I found the solution to the problem at this thread:
Re: (UPDATE) Drivers for TL-WN725N V2 - 3.6.11+ -> 4.xx.xx+

Thanks to MeEngman for this solution.

User avatar
sapnho
Posts: 216
Joined: Sun Sep 14, 2014 3:49 pm
Location: Frankfurt am Main
Contact: Website

Re: Buster bug report thread

Sun Jul 21, 2019 5:59 pm

Code: Select all

vcgencmd display_power 0
doesn't work on Buster + Pi 4. It works with Buster + Pi 3.
www.TheDigitalPictureFrame.com
Build a really great digital picture frame with the Raspberry Pi.
With lots of great tips from this forum.

User avatar
jjsanderson
Posts: 18
Joined: Wed Oct 17, 2012 11:45 am

Re: Buster bug report thread

Tue Jul 23, 2019 10:22 am

Sir FICO wrote:
Sat Jun 29, 2019 10:25 pm
netatalk for connection to apple mac computers fails. It can be installed with 'sudo apt-get install netatalk'. The mac 'finder' will show the rpi computer under the Network and will allow a 'connect as' login. However after the login the finder just says 'not connected'. I did not have any problems with stretch so I assume a buster issue.
This may not apply to your situation, but in general:

The default file sharing system on Mac OS X is Samba, as of a few years ago. You can still do AFP/netatalk stuff (I think even in 10.14/Mojave?), but my experience has been that SMB shares are faster, more reliable, and quicker to set up. I've typically followed the official docs to set this up at the Pi end: https://www.raspberrypi.org/documentati ... s/samba.md (no configuration is needed for a Mac client).

I typically also install avahi-daemon (via apt), which allows the Pi to announce itself to my LAN.

User avatar
jjsanderson
Posts: 18
Joined: Wed Oct 17, 2012 11:45 am

Re: Buster bug report thread

Tue Jul 23, 2019 10:43 am

jojopi wrote:
Sat Jun 29, 2019 9:17 am
The Debian package policykit-1 provides a file /etc/polkit-1/localauthority.conf.d/51-debian-sudo.conf that says:

Code: Select all

[Configuration]
AdminIdentities=unix-group:sudo
In the corresponding Raspbian package, this file is missing. The omission means that admin users cannot reboot or install packages, or are required to provide the root password when they should either be trusted or allowed to authenticate with their own credentials. It is a particular problem when no root password is set.

It seems that RPF/T images have long ago worked around this by adding unix-user:pi to 60-desktop-policy.conf. However, that is really an awful hack and would never have been necessary without the upstream Raspbian issue. It may also be a reason why people who create or rename users find they do not work as well as "pi".

Looking at the source package, the problem appears to be that there is logic in "rules" to check whether "dpkg-vendor --is" Debian or Ubuntu, and the "Raspbian" system falls down a crack.
Possibly related:

I'm seeing sporadic errors on boot with an error dialogue reading "No session for PID ####", where PID is invariably associated with lxpolkit, and hence (I believe) lxsession. The dialogue can be closed without issue, and everything appears to work happily ... except the system shutdown/restart dialogue, the buttons for which are unresponsive. Shutdown/restart can only be achieved from the terminal.

The error comes and goes across boot sessions, without any pattern I can discern.

There are several previous threads about this, across many years. Many such threads here at the Pi boards involve VNC, however I've not touched anything VNC in my setup (which is Buster, full, with recommended apps). Example threads:

User avatar
RogerW
Posts: 286
Joined: Sat Dec 20, 2014 12:15 pm
Location: London UK

Re: Buster bug report thread

Wed Jul 24, 2019 9:15 am

sudo apt-get install pigpio fails on buster lite.

I have a C program that needs libpigpio.so which does not appear to be included with buster lite. On stretch install pigpio worked. On buster I get "Temporary failure resolving....". I have tried several times and tried the suggested options but it still fails.

User avatar
algorithm
Posts: 185
Joined: Mon Nov 25, 2013 9:09 pm
Location: Flatland

Re: Buster bug report thread

Tue Jul 30, 2019 11:46 am

Not sure whether this is Buster or Pi 4. I am trying to use my Pi 4 headless via VNC at 1080p resolution but I get 1024x768. "tvservice -m CEA" does recognise the preferred mode I set in config.txt, but the driver apparently discards that info and invents a new mode that isn't even listed. How do I get 1080p without a monitor attached?

config.txt:

Code: Select all

$ grep -Ev '^(#|$)' /boot/config.txt 
hdmi_force_hotplug=1
hdmi_group=1
hdmi_mode=16
dtoverlay=pi3-disable-bt
dtparam=audio=on
[pi4]
dtoverlay=vc4-fkms-v3d
max_framebuffers=2
[all]
tvservice:

Code: Select all

$ tvservice -s
state 0x6 [DVI CUSTOM RGB full 4:3], 1024x768 @ 60.00Hz, progressive
$ tvservice -m CEA
Group CEA has 5 modes:
           mode 4: 1280x720 @ 60Hz 16:9, clock:74MHz progressive 
  (prefer) mode 16: 1920x1080 @ 60Hz 16:9, clock:148MHz progressive 
           mode 95: 3840x2160 @ 30Hz 16:9, clock:297MHz progressive 
           mode 97: 3840x2160 @ 60Hz 16:9, clock:594MHz progressive 
           mode 107: 3840x2160 @ 60Hz 64:27 (21:9), clock:594MHz progressive 
$ tvservice -m DMT
Group DMT has 1 modes:
           mode 4: 640x480 @ 60Hz 4:3, clock:25MHz progressive

jamesh
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 24147
Joined: Sat Jul 30, 2011 7:41 pm

Re: Buster bug report thread

Tue Jul 30, 2019 2:10 pm

algorithm wrote:
Tue Jul 30, 2019 11:46 am
Not sure whether this is Buster or Pi 4. I am trying to use my Pi 4 headless via VNC at 1080p resolution but I get 1024x768. "tvservice -m CEA" does recognise the preferred mode I set in config.txt, but the driver apparently discards that info and invents a new mode that isn't even listed. How do I get 1080p without a monitor attached?

config.txt:

Code: Select all

$ grep -Ev '^(#|$)' /boot/config.txt 
hdmi_force_hotplug=1
hdmi_group=1
hdmi_mode=16
dtoverlay=pi3-disable-bt
dtparam=audio=on
[pi4]
dtoverlay=vc4-fkms-v3d
max_framebuffers=2
[all]
tvservice:

Code: Select all

$ tvservice -s
state 0x6 [DVI CUSTOM RGB full 4:3], 1024x768 @ 60.00Hz, progressive
$ tvservice -m CEA
Group CEA has 5 modes:
           mode 4: 1280x720 @ 60Hz 16:9, clock:74MHz progressive 
  (prefer) mode 16: 1920x1080 @ 60Hz 16:9, clock:148MHz progressive 
           mode 95: 3840x2160 @ 30Hz 16:9, clock:297MHz progressive 
           mode 97: 3840x2160 @ 60Hz 16:9, clock:594MHz progressive 
           mode 107: 3840x2160 @ 60Hz 64:27 (21:9), clock:594MHz progressive 
$ tvservice -m DMT
Group DMT has 1 modes:
           mode 4: 640x480 @ 60Hz 4:3, clock:25MHz progressive
Instead of that HDMI stuff, try

Code: Select all

framebuffer_width=1920
framebuffer_height=1080
#dtoverlay=vc4-fkms-v3d   <--- May  or may not need this. 
Principal Software Engineer at Raspberry Pi (Trading) Ltd.
Contrary to popular belief, humorous signatures are allowed. Here's an example...
“I think it’s wrong that only one company makes the game Monopoly.” – Steven Wright

SkullKill
Posts: 7
Joined: Tue Jul 30, 2019 1:23 pm

Re: Buster bug report thread

Wed Jul 31, 2019 5:22 am

bluesign2k wrote:
Wed Jun 26, 2019 4:27 pm
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.

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.
globiboulga666 wrote:
Fri Jun 28, 2019 5:35 pm
Hi,

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).
issue with connecting to a WPA2 enterprise with peap-mschapv2 authentication wifi network
looks like this is related to a bug between wpa_supplicant 2.8 and broadcom-wl driver?


got a workaround for this, until it is fixed,

https://www.raspberrypi.org/forums/view ... 4#p1510664

Return to “Raspbian”