Great update (1.7 GB) with just one issue. I used an headset with Creative BT-W3 Bluetooth Audio Transmitter. Because I don't have any bluetooth on my MOBO. It worked well until now, but with PipeWire, I have no more sound in the headset. Could you help me ?
$ inxi -A
Audio:
[…]
Device-4: Creative BT-W3 driver: hid-generic,snd-usb-audio,usbhid
type: USB
[…]
API: ALSA v: k6.3.12-244.current status: kernel-api
Server-1: PipeWire v: 0.3.75 status: activeSo far so good!
Do you remember what applets you had active in your budgie-panel?
Staudey as far as I remember, mine has these on:
keyboard language indicator/switcher
keyboard lock keys indicator
budgie menu
icon task list
systray, network, volume (sorry, don’t remember if these are separate or not)
notifications
clock
raven trigger
Also, on a related note, I tried to roll the update back via tty for now, but eopkg throws a system error: Repo item libatk-32bit not found
On my Lenovo Thinkpad P15s (Gen 2) Nvidia drivers do not work after update. I just get a black screen upon bootup.
I belive I have a T500 card. along with the Intel® Xe Graphics (TGL GT2)
I had to disable the driver manually in boot options to log in and then remove them.
I have tried reinstalling them but got the same result.
Bonus info that may not be relevant: it's not a clean installation after 4.4 but rather an updated one. I guess the only real difference is I think I have nautilus.
algent just tried reinstalling budgie-desktop as you suggested - unfortunately the issue persists.
Well, unable to boot after update on Budgie, just this error message
[!!!!!!] Failed to start up manager
[83.359621] systemd[1]: freezing execution
What should I do?
Thanks
Could everyone experiencing the issue starting Budgie Desktop please list the applets you have running on the panel? Hoping to find a common denominator.
Also, any logs from journalctl relating to budgie-panel (probably; it could be another component) would be very helpful.
(@nolan @[deleted] @RegularJogger @SiewYan)
AhmedBenhamouda One workaround is to follow the steps here to chroot into your system and run sudo eopkg it --reinstall systemd. It would be really great to get any kind of information about why this is happening, but I don't know how to do so. :/
Noting ahead I can't fullfil the request since I don't have that installed anymore.
HOWEVER I can try to identify mine in the list of others. Using budgie as well.
RegularJogger
I had those ALL:
"keyboard language indicator/switcher
keyboard lock keys indicator
budgie menu
icon task list
systray, network, volume (sorry, don’t remember if these are separate or not)
notifications
clock
raven trigger"
I'm sure of that. Considering what I had more, it's not surprising though that those were installed.
Hopefully people will be able to find the culprit if any.
Also had telegram, terminal, software center (default), firefox (default), rythmbox (defaults) and celluloid (default) and also thunderbird and launch nemo (default) if not noted, discord, battery (default?) - with battery percentage (non default to show), element, budgie screenshot/other type of budgie screenshot, probably geany, possibly gimp who knows maybe vlc (probably not this time), or lutris (probably not this time), gedit, could be calculator, and many things which should not be there probably. (temperature of cores from budgie, celtic magic from budgie, virtualbox, steam, system settings, showtime from budgie, maybe contrast from budgie maybe show desktop from budgie, don't remember what else) also, status and user indicator (both are probably default), but I thought it was not (and had not) gnome extensions. order is random since I try to recall and edit rapidly.
As said before, could be I've made an error...
As also said, I can't know the list and not having that installation anymore.
Used: laptop, budgie, luks (not using now), LVM (not using now). Intel. If needed will elaborate but as one other commented it might not likely to help much now since I don't know the origin of the issue (me/not me etc) and while it works great now on a newly installed and vanilla upgraded system and previously not, I did change the installation much.
Panel issue (no icon and - ) /unknown mouse issue (can't click/be captured anywhere) as noted. Faintly recalling not the first time I see a similar thing, but this time it was the worst and not in a specific context and couldn't do anything beside moving the mouse cursor or cold boot, I think, after logging in, and even cold restart didn't help.
Can no longer troubleshoot as noted - not same installation and now things are OK.
EbonJaeger thank you but same problem occurred
I would like to thank you all for reporting/troubleshooting and helping, good luck!
I wish I could help more.
On solus budgie, not using any other applets than what a normal installation provides
AhmedBenhamouda I think that I have to reinstall Solus again and will waiting for the next update to upgrade my system
nolan the desktop fails to load and falls back to the login screen (budgie widgets thing?)
it seems to be fixed, managed to boot, some how, I thing some how secure boot fails, I had to select the HDD instead of the uefi entry.
checking for brocken packages only font-weather-icons-otf was brocken, reinstalled (--reinstall) and it seems to work now, I can't verify if it was the cause.
For people experiencing issues (it sounds like mostly Budgie users?) it would be great to report the following:
For debugging purposes you can edit the kernel arguments by holding the down key while booting. The most recent -current kernel is 6.3.12-244. You can try to boot with an older kernel to see if that helps (please report back which ones work for you). You can also try hitting e over the boot entry to change the kernel options. If you're using a nvidia GPU we recently added the nvidia-drm.modeset=1 parameter, try deleting that and see if that helps. You can also remove quiet loglevel=3 splash systemd.show_status=false to get more verbose logging which can help debug the issue.
For people who are not able to log into a session are you still able to switch to a different TTY and log in there (hitting CTRL+ALT+F3 for example)? That will help us understand where exactly this issue is happening.
