Linux Freezing randomly with fresh installs, can't find errors

General system Newbie
21

Like @smokey said, it is DE-specific.

TL;DR: You don’t have to worry about x11 not being supported. It will be available for a few more years.

There are 3 fully-featured DEs (KDE, Gnome and Cinnamon) and several others that are close to full-featured (Xfce, Budgie, Pantheon, etc.).

Of the top 3, Cinnamon is the slowest in terms of development, but this is intentional. They don’t like breaking things just because some people want the newest thing on the block. This means that they will likely be supporting x11 for years to come, or at least offer it as a fallback.

This is also true for the others that are close to fully-featured. They are all intentionally slow with their implementations of Wayland. These DEs focus on uniformity and UX, so they don’t want things looking weird and glitchy.

It’s just Fedora (Red Hat) and Ubuntu (Canonical) pushing the idea of only using Wayland and funding KDE and Gnome to focus on it as much as possible.

However, these two are static-release distros, and all their users are using different versions of their distro. Some are using KDE 5.27, some are using KDE 6, and whatever equivalent numbers Gnome users are using. This means that they will be supporting x11 for at least another 3 years.

image

Aside from x11 DEs, there are also x11 WMs like Openbox, i3, Bspwm, DWM (all x11) that will probably have support for a long time.

So, you don’t need to worry about that. The rollout will take a while to happen, there’ll be some years of transitioning from x11 to Wayland, and even after it’s complete, x11 will still be supported for some time.

2 Likes
22

Well you are talking about ubuntu and debian support, but i do use KDE, which i love the most. For me to use kde even after x11 drops, i hope there are ways to use wayland, and i really think there are some tweaks to do, to avoid the freezing, i just dont know what guide to follow or what exactly to try.

Also update: i have been using EOS for a very long time today and not a single freeze, so yes it was wayland, the troublemaker for all 3 of the linux distros that i tried :slight_smile:

Thank you very much :slight_smile:

1 Like
23

Yes @anon62796363 , my nvidia and everything is up to date, no system logs indicating anything about this problem but it seems to be a wayland issue, perhaps it’s not compatible with my gpu (rtx 3060 gpu mobile)

24

if is wayland try x11 it may help

1 Like
25

Yes i have been trying x11 as ddnn suggested, its been working great. im just scared of using it long term as support will drop some time.

1 Like
26

dont worry by the time when support drop it will work

2 Likes
27

For the record: It’s mostly an Nvidia problem. Wayland is not the main issue.

Glad it’s working now. All the best in your EndeavourOS! :vulcan_salute: :enos_flag:

28

Update: i have tried installing nvidia-dkms-beta, which seems to fix compatibility with wayland, I can use wayland but ofcourse, cant fix something without breaking something else.
Now my audio output is not available anymore that is connected to my monitor, which is connected with hdmi to my laptops nvidia gpu.

29

You may just be missing some other packages, like maybe nvidia-utils-beta.

What’s the output of:

pacman -Q | grep -A 2 -E nvidia

Also, you mean nvidia-beta-dkms, right?

30

yes i do have the nvidia-utils-beta, and yes i meant nvidia-beta-dkms .
the output:

nvidia-beta-dkms 555.52.04-1
nvidia-exec 0.2.9-1
nvidia-hook 1.5-2
nvidia-inst 24-1
nvidia-settings-beta 555.52.04-2
nvidia-utils-beta 555.52.04-2
31

Seems you have all the packages you need.

Have you rebooted since installing the dkms package? Whether you have or not, go to the folder below and rename it to “wireplumber-bkp”, then reboot.

.local/state/wireplumber

If this doesn’t work, please post the output of:

pacman -Q | grep -A 2 -E "(wire|wayland)"
1 Like
32

Oh wow! renaming the directory to “wireplumber-bkp” really worked! could you explain this magic to me?

if you were still interested in the output:

egl-wayland 2:1.1.13-2
eglexternalplatform 1.1-3
ell 0.66-1
--
gst-plugin-pipewire 1:1.0.7-2
gst-plugins-bad 1.24.3-1
gst-plugins-bad-libs 1.24.3-1
--
kpipewire 6.0.5-1
kpmcore 24.05.1-1
kpty 6.3.0-1
--
kwayland 6.0.5-1
kwayland-integration 6.0.5-1
kwayland5 5.116.0-1
kwidgetsaddons 6.3.0-1
kwin 6.0.5-2
--
lib32-wayland 1.22.0-1
lib32-xz 5.6.2-1
lib32-zlib 1.3.1-1
--
libpipewire 1:1.0.7-2
libplacebo 6.338.2-7
libplasma 6.0.5-1
--
libwireplumber 0.5.3-1
libwnck3 43.0-3
libwpe 1.16.0-1
--
pipewire 1:1.0.7-2
pipewire-alsa 1:1.0.7-2
pipewire-audio 1:1.0.7-2
pipewire-jack 1:1.0.7-2
pipewire-pulse 1:1.0.7-2
pixman 0.43.4-1
pkcs11-helper 1.30.0-1
--
qt5-wayland 5.15.14+kde+r58-1
qt5-webchannel 5.15.14+kde+r3-1
qt5-webengine 5.15.17-4
--
qt6-wayland 6.7.1-1
qt6-webchannel 6.7.1-1
qt6-webengine 6.7.1-1
--
wayland 1.23.0-1
wayland-utils 1.2.0-1
webkit2gtk 2.44.2-1
webkit2gtk-4.1 2.44.2-1
--
wireplumber 0.5.3-1
wmctrl 1.07-6
woff2 1.0.2-5
--
xorg-xwayland 24.1.0-1
xorgproto 2024.1-2
xsettingsd 1.0.2-1
--
xwaylandvideobridge 0.4.0-2
xxhash 0.8.2-1
xz 5.6.2-1
1 Like
33

That folder is where pipewire/wireplumber stores your user-specific settings. So, when you changed the driver for Nvidia, it was still using the old settings. By removing the folder, you forced pipewire to recreate it with the new default settings.

And poof! Magic! :magic_wand:

1 Like
34

AHA, i knew something was off when i couldnt find anything about wireplumber-bkp! i just noticed the wireplumber folder get regenerated indeed. So when installing the nvidia beta drivers, pipewire/wireplumber had to be refreshed :slight_smile: okay i understand, you’ve been of so much help to me, i’m so happy I can keep using EOS and thankful for your help!

1 Like
35

You’re welcome. Glad I was able to help.
:heart_hands:

1 Like
36

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.