GUI dissapearing

[yohhan]

After i updated my nvidia drivers and rebooted my computer, a lot of gui parts started dissapearing, i dont know if this is the correct way to name it but take a look.
Here are some videos demonstrating the issue:
( note: i am only hovering my mouse over them )

This problem as of now has only appeared on console, extension manager, settings, tweaks, and some other applications.
chromium, spotify, steam and other applications that i downloaded manually are not affected…( manually as in sudo pacman -S and yay -S )

May i note too that the booting takes more time than before the nvidia drivers were installed

[Bink]

Hello again @yohhan

These sorts of glitches remind me of Wayland + Nvidia issues. Log in with an X11 session instead, and see if the issue persists. Unfortunately, I’m not familiar with how to do that with Gnome, I’m more familiar with KDE/Plasma. Hopefully it’s just an option on the login screen like Plasma?

With respect to the slower boot now the correct Nvidia drivers are installed, just how much slower is it? Do you note it getting stuck on a particular point?

You might share your bootlog, although that does not necessarily give us insight into where it gets stuck, unless it explicitly throws an error of some sort there.

This will generate your bootlog, then put it online and provide you with a shareable link to paste here. Alternatively, you can insert the log output directly here as pre-formatted text.

journalctl -k -b -0 | eos-sendlog

[yohhan]

hi again @Bink !

the boot is weird actually, i insert my password, then then screen goes blue (“no signal”) then the computer starts, i dont know if its hardware problem because yesterday i changed some cables in my tv but, idk, maybe its not hardware, right?

I’d rather share the output link because its more accessible to you and me
https://0x0.st/Xfb3.txt

[Bink]

@yohhan

the boot is weird actually, i insert my password, then then screen goes blue (“no signal”) then the computer starts, i dont know if its hardware problem because yesterday i changed some cables in my tv

If you have multiple displays connected, perhaps the boot process is appearing primarily on only one of those, while the other momentarily loses signal. If, to help diagnose this issue, you want to see the boot process on a particular display, it would be simplest to just temporarily disconnect all other displays.

The slowness looks like it might be here (line 955 of your bootlog), because 26 seconds pass between the systemd-journald error, and the next line:

jul 25 23:20:50 yonau kernel: rfkill: input handler disabled
jul 25 23:20:55 yonau systemd-journald[404]: File /var/log/journal/2190cdc657aa4ebdbf1fb39b620069de/user-1000.journal corrupted or uncleanly shut down, renaming and replacing.
jul 25 23:21:21 yonau kernel: rfkill: input handler enabled
jul 25 23:21:24 yonau kernel: rfkill: input handler disabled

[Bink]

Have you needed to hard reset?

[yohhan]

if by displays you mean monitors… i only have 1 monitor
and no, i didnt hard reset because after a little while the computer just goes back to normal

[Bink]

To clarify, I was speaking broadly with needing to hard reset. Like, if a game doesn’t launch properly and locks up the system completely… etc.

The error thrown by systemd-journald suggests data corruption, and an unclean shutdown or reset is one way those occur.

[yohhan]

ohh, well i might have because today, i had a blackout in my city but i dont know if that counts as a hard reset

[Bink]

It does count

If we can put the boot issue aside for a moment, were you able to try logging in using X11?

[yohhan]

im sorry but i dont even know whats the difference between a normal session and a X11 session could you explain a bit pls?

[Bink]

Super brief back story:

• X11 is a long standing windowing system for graphical user interfaces under Linux and BSD. It’s been around nearly as long as me, so it’s clinging onto the good ol’ days and the way things used to be. Turns out that involves a whole lot of baggage though.
• Wayland is being developed by the same people, as a complete replacement of X11. It’s a fundamental shift in development and use, so it’s been a rough transition to this as a new system.

Wayland for daily use under Linux is still quite a new thing, and as such, is still rather buggy. This is especially the case, when it comes to Nvidia GPU’s.
KDE/Plasma is now leveraging Wayland as default, but you can switch to X11 when logging in.
Gnome, if I’m not mistaken, is also leveraging Wayland by default, but I’m not familiar with how to switch to X11 with that.

You’re using an older Nvidia GPU which is unlikely, I believe, to ever receive full Wayland support, because you’re restricted to using legacy drivers. Nvidia GPU’s using the official drivers only really got Wayland support very recently, and even then it’s still prone to lots of issues.

[yohhan]

oh thats interesting, im probably going to do a little research on how i can change it to X11, anyways, how would you change it on a kde/plasma desktop? maybe it is similar to Gnome

[Bink]

Based on the display details you shared in the earlier thread, it does confirm you’re using Wayland.

Steam not launching games properly

ok so, im pretty sure i used “sudo pacman -S steam” [Screenshot from 2024-07-24 21-21-27] here are the commands you told me to do, (i have no idea how to read those but i think i have a Geforce GT 730) I didnt really understand how to install proton-ge, i did the command but it didnt show on the steam compatibility tool, asides from all those tips, none of them worked (btw im sorry if my english is bad, its not my first language)

You may need to start a new thread in the Gnome category, to get some answers on how to use X11.

[yohhan]

oh okay!! ill try it out

[Bink]

As for the systemd-journald error, it relates to your systems logging feature.

You can test the integrity of your journal files using this command:

sudo journalctl --verify

That should tell you if there is any current corruption. If there is corruption, you could try jumping to step 4 below (restarting the service) and running this test again to see if the corruption persists.

If the corruption persists, one way to resolve it may be to start with a clean slate. I will caution though, that this process will essentially reset your system logs. They may, or may not be important to you.

If you’d like to pursue this option, these are the steps:

1. Write journal data sitting in memory, to disk:

sudo journalctl --flush

2. Archive all current journal data, so it can be cleaned:

sudo journalctl --rotate

3. Clear all journal data older than 1 second:

sudo journalctl --vacuum-time=1s

4. And now for good measure, restart the systemd-journald service:

sudo systemctl restart systemd-journald

[yohhan]

okay so i did the 4 steps even though it said “PASS”.
Is that it? that should fix the boot process time?

[Bink]

It was aimed at addressing the boot issue, yes. I suspect this was the cause, but I wouldn’t say I’m certain. Hopefully it helps.

[yohhan]

i just tested it out and well… didnt change much

[Bink]

Hmm… perhaps related to rfkill, which is a utility for enabling/disabling wireless devices. I can see you’re wired into your network there. Do you have a WiFi or Bluetooth adaptor?

This thread suggests the exact same 26 seconds of boot hang, as a result of rfkill on a system with no wireless adaptor.

Very slow boot due to rfkill - How to disable rfkill?

That’s on Ubuntu mind you, so I’m not sure if the offered fixes would translate to Arch.

[Bink]

That said, I have three Endeavour OS systems of different calibre, without WiFi and bluetooth, and they don’t suffer from this particular issue. Of note though, when I check my bootlog on my workstation (one of those systems), there’s no mention of rfkill at all.

So perhaps it’s in error that it’s even running?