Sync Updates for Week 30, 2023

RegularJogger

algent just tried reinstalling budgie-desktop as you suggested - unfortunately the issue persists.

AhmedBenhamouda

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

EbonJaeger

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. :/

inkbug

AhmedBenhamouda

I had the very same issue (Solus Plasma), however, the steps in EbonJaeger 's post corrected the issue.

EbonJaeger

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

EbonJaeger thank you but same problem occurred

[deleted]

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.

[deleted]

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.

AhmedBenhamouda

AhmedBenhamouda I think that I have to reinstall Solus again and will waiting for the next update to upgrade my system

[deleted]

I would like to thank you all for reporting/troubleshooting and helping, good luck!
I wish I could help more.

hakimjonas

On solus budgie, not using any other applets than what a normal installation provides

nolan

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.

nolan

nolan checking for brocken packages

I should say I was in TTY ctrl+alt+[function key]

nolan

regarding to the boot issue, I took a picture [too big here]
it said:

[!!!!!!] Failed to start up manager.
[  15.188781] systemd[1]: Feezing execution.

was the only in the screen.

I thought it could be some issue it the bios (uefi configuration) I guess I disabled secure boot or something else, I managed to boot selecting the disc drive instead of the solus boot manager(uefi), Checked for broken packages and as I said

nolan font-weather-icons-otf

was broken, reinstalled it with --reinstall , rebooted and selecting the disck drive again, booted to desktop as normal, shut down and boot a few times to ensure it was OK, no problems after that.

Then followed the guide for enabling secure boot in an existing installation, I updated clr-boot-manager clr-boot-manager update maybe it fixed the problem? I'm not sure at this point.

ReillyBrogan

For people experiencing issues (it sounds like mostly Budgie users?) it would be great to report the following:

Whether you're on the LTS or current kernel
DE (Budgie, GNOME, Plasma, Other?)
GPU and GPU driver
Whether or not you have secure boot enabled

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.

nolan

ReillyBrogan Whether you're on the LTS or current kernel
DE (Budgie, GNOME, Plasma, Other?)
GPU and GPU driver
Whether or not you have secure boot enabled

Kernel: 6.3.12-244.current
DE: Budgie
CPU: Intel Core i3-3110M
GPU: Intel 3rd Gen Core processor Graphics - driver: i915 - API: OpenGL v: 4.2 Mesa 23.1.4 renderer: Mesa Intel HD Graphics 4000 (IVB GT2)
Secure Boot: Was disabled, I enabled it following the guide for existing installs. Now it boots correctly as I already enrolled the cert wen clr-boot-manager, version: 3.2.12, release: 29 was available in the stable repo.

[deleted]

ReillyBrogan
Warning ahead, can't troubleshoot as I don't have the problematic install
The following refers to my previous install which had issues with this update.

Whether you're on the LTS or current kernel

Current (Shannon)
6.3.12-244.current
Trying the previous stable one didn't help after the update

DE (Budgie, GNOME, Plasma, Other?)

Budgie 10.7.2

GPU and GPU driver

Intel® UHD Graphics 620 (KBL GT2)
I believe the drivers were, non formally, that mesa and that i915. (default, updated with the system)

I believe the following was true also for the previous install:
driver: i915
loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915
resolution: 1366x768_60Hz
API: OpenGL v: 4.6 Mesa 23.1.4 renderer: Mesa Intel UHD Graphics 620 (KBL
GT2)

Whether or not you have secure boot enabled.

I didn't have secure boot enabled (and still don't)
I do have a UEFI/GPT/Solus automatic full disk (previous time with Luks, LVM) installation.

Also, had Luks and LVM (now I don't use).

Could login, but couldn't use the desktop once logged in. Mouse cursor moved and that's it. icon panels were missing, mouse clicks didn't do anything or were not captured etc (non formal description). I didn't know enough/though to check keyboard by then.

AhmedBenhamouda

ReillyBrogan tried that
This is what I have

nolan

Staudey no, but it works now.

ReillyBrogan

nolan Which issues did you have specifically? And which ones have you resolved?

[deleted]

[deleted]
I forgot:

on chroot, made the 1st steps as written and then I had eopkg check with no broken package. I did notice the upgrade removed package, no idea if that is OK, it could be.

Anyway in time I was asked to in instruction, I did trigger the things which are triggered after update as was asked, I think I exit as had to, and rebooted, (I don't remember the orders, but those I followed,) instruction said don't reroll unless issue was not solved by those previous steps and a reboot, it didn't solve the issue, but from that point I messed up by my fault before even getting to try the actual reroll.

CPU I forgot to add (the rest of the info, above)
CPU:
Info: quad core model: Intel Core i5-8250U bits: 64 type: MT MCP cache:
L2: 1024 KiB

EbonJaeger

For Budgie people having login problems where you get the Oh No screen, what we really need are journal logs which should point us in the right direction.

Attempt to log in
Get to Oh No screen
Switch to a TTY (Ctrl+Alt+F2)
journalctl -xe and look for errors; most probably a SEGFAULT

The trick will be figuring out how to post the logs, given you can't start a Budgie session... The best you can do might be to take a picture of the screen with a phone and use that to post to the forums. Not ideal, but...

If anyone else has a better idea to get logs, please share.

[deleted]

EbonJaeger
Regarding method of getting (existing) logs. I had a way. It's not a recommendation, it's for those who may install anyway unless one else who fits to recommend, recommends it.

I think I could copy some logs while using a USB live with storage and also decided to take some logs to storage on the session while I was chrooting. Maybe such could be done from an OS on other disk as well, regardless of chrooting maybe too. Somehow. I don't know regarding permissions.
But it was easier for me and maybe it is easier than remembering the command but I did that only as a last resort since I'm going to install something else on the system soon anyway.

(my backup is OS agnostic as far as I know, so I am not afraid, though it takes some work and apps etc are not backed up in the way I chose, it can still bring back an OS like solus of any flavour/mint/mx, maybe zorin maybe even spiral etc, to function nicely in not so long time after an installation.)

nolan

No SEGFAULT fortunately

nolan

nolan I'm on desktop now, no problems on my end at the time.
EDIT: the dates are wrong, it's not today [29] it's yesterday [28] that is useless now.

« Previous Page Next Page »