ha, now BCM4352 802.11ac works again. Maybe did it need more than one reboot?
Anyway: solved.

    I just updated my installation of the XFCE-Beta I have installed on this little Dell 3162.

    I had not turned it on for two weeks.

    Everything is till working normally - thanks for your hard work.

    brent always

    I noticed a long time ago that sometimes a reboot wouldn't set things right by itself, but a full shutdown followed by an ordinary statup would. That was at a time when things like audio cards, video cards, and network cards were separate things that were plugged into a motherboard, not just chipsets. Rebooting the OS didn't necessarily cut power to those accessories and cause them to re-initialize.

    The most common example back in the day was a network card that got confused for some reason, and stayed confused after a reboot, but worked fine once the computer was turned off and then restarted.

    Depending on a computer's architecture, that may still be true today. I've formed a habit such that if a single reboot doesn't cure a problem that I expected it to, I'll do a full shutdown and restart. I can't remember a time when that hasn't worked for me.

        WetGeek I reboot everyday but if that dont work I go into coma mode for awhile...rofl

          Everything went fine on my laptop. I even noticed that a little glitch happening when going into the GNOME session (screen went blue for 0,5sec) is now gone ^^ Thank you for your hard work!

          WetGeek I noticed a long time ago that sometimes a reboot wouldn't set things right by itself, but a full shutdown followed by an ordinary statup would. That was at a time when things like audio cards, video cards, and network cards were separate things that were plugged into a motherboard, not just chipsets. Rebooting the OS didn't necessarily cut power to those accessories and cause them to re-initialize.

          The most common example back in the day was a network card that got confused for some reason, and stayed confused after a reboot, but worked fine once the computer was turned off and then restarted.

          Depending on a computer's architecture, that may still be true today. I've formed a habit such that if a single reboot doesn't cure a problem that I expected it to, I'll do a full shutdown and restart. I can't remember a time when that hasn't worked for me.

          we used to call that "getting the gremlins out" when you completely unpowered it, no electricity. you are right that is also effective

              brent The IT Crowd - "Have you tried turning it off and back on again?"
              😆

                I am still having issues with the workplace switcher but I also didn't see any Budgie updates. I think the fix is in Budgie 10.9.2. Do we know when we will be getting that update?

                We just downgraded Mesa to 23.3.6 in order to fix an issue that Nvidia users have logging into a Wayland session.

                  ReillyBrogan
                  Some late changes after Mesa 23.3.6 also broke RadeonSI, so some essential VAAPI decoders got missed on Radeon RX6600:

                        VAProfileVP9Profile0            : VAEntrypointVLD
      VAProfileVP9Profile2            : VAEntrypointVLD
      VAProfileAV1Profile0            : VAEntrypointVLD

                  Mesa downgrade to 23.3.6 fixed it.

                      SilverBird775 Yes, I noticed yesterday that Mesa had changed the meaning of the video-codecs build argument to mean "what codecs should we build support for" when it used to mean "what non-free codecs should we build support for". Because of this change in what that build argument meant our Mesa 24.0 builds did not build support for the free codecs (AV1/VP9), only the non-free ones. I already had it fixed locally and had the Nvidia issue been one that we could easily patch I would have instead cherry-picked a new build of 24.0 with the codecs fixes and Nvidia fixed. Unfortunately the Nvidia issue requires upstream Mesa to fix it so I just reverted to 23.3 instead.

                      Once the Nvidia issue is fixed we'll roll out 24.0 with all codecs enabled.

                          I also have the Virtualbox usb issue. I did use to work but today tried to use a USB device in a VM to find they are all greyed out. Checked I was still part of the vboxusers group and thats all ok.

                          I need to roll back the kernel to see at which point it stops.

                          Fritzing cherry-picked to fix an issue with it crashing upon launch, and systemd cherry-picked to fix an issue with X11 sessions AND an issue with Virtualbox USB device passthrough.

                          Might be a little niche but I noticed with Friday's update, the one that brought us Mesa 24.0.0, the free shooter Xonotic began to crash the moment any game starts. I synced again few hours later where we downgraded to Mesa 23.3.6, and now the game runs fine, the crash doesn't happen. On 24.0.0 it would launch and get to the point where you're in a game, but it crashes the moment the countdown goes down or I shoot.

                          I also noticed (but didn't manage to bring evidence) that the xorg capture sources Window Capture and Screen Capture in OBS weren't working, they were showing up as a black screen. Also solved when we downgraded. obs-vkcapture (which was updated on that first Friday sync) remained working.

                            ring0 Do you have a Nvidia GPU? If so that crash is exactly the reason we downgraded.

                                It's an old game so no big deal I just thought I'd bring it up in case it could be a sign of something or something like that. But that black screen issue on OBS is familiar, I've seen it resolved with things related to xdg-desktop-portal but I don't know much about it other than I needed to install it on Arch to get OBS working there.

                                Kinda unrelated but to do with OBS update issues, one time (on arch) there was an update to obs-vkcapture that caused some games to crash the moment the source was added, I updated and after encountering the issue updated again shortly after to find the dev just put out a patch to solve it. I went looking for the commit just to confirm and found it, he gave a pretty detailed description of the issue. I don't know much about all this stuff honestly but the terms etc I do know come from looking stuff like this up when it happens lol

                                  My video glitches have returned with this last update
                                  I did not do the mesa rollback tho.
                                  Intel graphics