Fedora for Desktop Systems

Ask Fedora
, , , , , , , , ,
1

This is somewhat rant and other part problems. I have used Fedora for a lot of years now and can’t understand why my system still has problems waking up after sleep! This problem has been around since at least F29 and I’m now on F39. Every time I get a good combination of something (no idea what maybe kernel) my system will work great until an update reverts back to not waking up. Only way to get system back is hard reset (power off/on). Most recent example is the current kernel update I applied over last weekend. Before that I was having no problem with waking up, now it will not wake up without power recycle.

Problem two after that update the system no longer remembers the applications I had open and where they were positioned in my desktop. It such an aggravation to have to complete reset up my desktop every time I reboot or log in. I realize that so many use laptops and this may not be a big issue but there are still I would expect a large number of users who use desktops. I’m on F39 running X11 which has remembered application placement for at least 20 years if not more and I thought it was still supported in F39 at least it has been until this past update.

I know KDE is planning to go to Wayland for F40 and I’m not pleased with that as so much is still not supported in Wayland. Will have to find another solution to my computing needs at that point.

My system is home built consisting of:

Tue Jun 04 09:57:50[root@odyssey: ~]
SU: # inxi -Fzx
System:
  Kernel: 6.8.11-200.fc39.x86_64 arch: x86_64 bits: 64 compiler: gcc
    v: 2.40-14.fc39
  Console: pty pts/4 Distro: Fedora Linux 39 (Workstation Edition)
Machine:
  Type: Desktop Mobo: ASUSTeK model: ROG STRIX X570-E GAMING v: Rev X.0x
    serial: <filter> UEFI: American Megatrends v: 5013 date: 03/18/2024
Battery:
  Device-1: hidpp_battery_0 model: Logitech Wireless Keyboard K540/K545
    charge: 100% (should be ignored) status: discharging
  Device-2: hidpp_battery_1 model: Logitech Wireless Mouse
    charge: 55% (should be ignored) status: discharging
CPU:
  Info: 16-core model: AMD Ryzen 9 3950X bits: 64 type: MT MCP arch: Zen 2
    rev: 0 cache: L1: 1024 KiB L2: 8 MiB L3: 64 MiB
  Speed (MHz): avg: 2281 high: 3500 min/max: 2200/4761 boost: enabled cores:
    1: 2200 2: 2200 3: 2200 4: 2200 5: 2200 6: 3500 7: 2200 8: 2200 9: 2200
    10: 2200 11: 3500 12: 2200 13: 2200 14: 2200 15: 2200 16: 2200 17: 2200
    18: 2200 19: 2200 20: 2200 21: 2200 22: 2200 23: 2200 24: 2200 25: 2200
    26: 2200 27: 2200 28: 2200 29: 2200 30: 2200 31: 2200 32: 2200
    bogomips: 223557
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3
Graphics:
  Device-1: NVIDIA TU106 [GeForce GTX 1650] vendor: ASUSTeK driver: nvidia
    v: 550.78 arch: Turing bus-ID: 0a:00.0
  Display: server: X.Org v: 1.20.14 with: Xwayland v: 23.2.6 driver: X:
    loaded: nvidia unloaded: fbdev,modesetting,nouveau,vesa
    gpu: nvidia,nvidia-nvswitch resolution: 3840x2160~30Hz
  API: EGL v: 1.5 drivers: nvidia,swrast platforms:
    active: gbm,x11,surfaceless,device inactive: wayland,device-1
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 550.78
    glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce GTX 1650/PCIe/SSE2
  API: Vulkan v: 1.3.275 drivers: N/A surfaces: xcb,xlib devices: 2
Audio:
  Device-1: NVIDIA TU106 High Definition Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel bus-ID: 0a:00.1
  Device-2: AMD Starship/Matisse HD Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel bus-ID: 0c:00.4
  API: ALSA v: k6.8.11-200.fc39.x86_64 status: kernel-api
  Server-1: PipeWire v: 1.0.7 status: n/a (root, process)
Network:
  Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel bus-ID: 04:00.0
  IF: wlp4s0 state: down mac: <filter>
  Device-2: Realtek RTL8125 2.5GbE vendor: ASUSTeK driver: r8169 v: kernel
    port: e000 bus-ID: 05:00.0
  IF: enp5s0 state: down mac: <filter>
  Device-3: Intel I211 Gigabit Network vendor: ASUSTeK driver: igb v: kernel
    port: d000 bus-ID: 06:00.0
  IF: enp6s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IF-ID-1: virbr0 state: down mac: <filter>
Bluetooth:
  Device-1: Intel AX200 Bluetooth driver: btusb v: 0.8 type: USB bus-ID: 1-6:3
  Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.2
    lmp-v: 11
Drives:
  Local Storage: total: 8.19 TiB used: 1.51 TiB (18.4%)
  ID-1: /dev/nvme0n1 vendor: Corsair model: Force MP600 size: 931.51 GiB
    temp: 40.9 C
  ID-2: /dev/sda vendor: Seagate model: ST4000DM004-2CV104 size: 3.64 TiB
    temp: 30 C
  ID-3: /dev/sdb vendor: Seagate model: ST4000DM004-2CV104 size: 3.64 TiB
    temp: 27 C
Partition:
  ID-1: / size: 97.87 GiB used: 60.12 GiB (61.4%) fs: ext4 dev: /dev/nvme0n1p3
  ID-2: /boot size: 769.8 MiB used: 391.8 MiB (50.9%) fs: ext4
    dev: /dev/nvme0n1p2
  ID-3: /boot/efi size: 249.7 MiB used: 19 MiB (7.6%) fs: vfat
    dev: /dev/nvme0n1p1
  ID-4: /home size: 1.97 TiB used: 1.28 TiB (64.9%) fs: ext4 dev: /dev/sda1
Swap:
  ID-1: swap-1 type: zram size: 8 GiB used: 0 KiB (0.0%) dev: /dev/zram0
  ID-2: swap-2 type: partition size: 50 GiB used: 0 KiB (0.0%)
    dev: /dev/nvme0n1p4
Sensors:
  System Temperatures: cpu: 30.0 C mobo: 32.0 C gpu: nvidia temp: 32 C
  Fan Speeds (rpm): fan-1: 1260 fan-2: 505 fan-3: 0 fan-4: 0 fan-5: 0
    fan-6: 0 gpu: nvidia fan: 27%
Info:
  Memory: total: 32 GiB available: 31.24 GiB used: 3.81 GiB (12.2%)
  Processes: 561 Uptime: 36m Init: systemd target: graphical (5)
  Packages: 28 Compilers: clang: 17.0.6 gcc: 13.3.1 Shell: Bash v: 5.2.26
    inxi: 3.3.34
Tue Jun 04 10:30:32[root@odyssey: ~]
SU: #

Any help restoring things to a workable configuration would be appreciated.

Forgive the rant, but I’ve had about as much as I can stand.

2

You can still install X11 on F40

1 Like
3

I had sleep issues too on an AMD Thinkpad T495.

Now on my Clevo NV41MZ with Novacustom Coreboot, all intel, I have no issues at all, never.

If this is about kernels, try to just use the official LTS kernel from this COPR.

If that one works, it will work for the next 2 years

Are you using workstation or KDE? and yes, even on KDE you can still install X11 manually, it is still in the repos, if it gets dropped there will likely be a COPR.

Kwin-x11 is feature frozen since 2018, so maintaining the build using the current spec should not be hard.

If you want to keep the legacy software extra long, you might want to switch to CentOS Stream or RHEL.

GNOME upstream might drop X11 support once they get the keyboard input portal fixed. And Fedora will not support X11 longer than GNOME.

CentOS, Debian etc meanwhile will support these old packages for quite some time.

4

I’m running an install of Fedora workstation with KDE Plasma Desktop

1 Like
5

I’m not sure it’s about kernel but it always seem to happen after a new kernel install. Not on every kernel, on some everything works fine. I also noticed while trying to investigate the problem after a power cycle, I see that things on cron haven’t been running for hours; ex. system activity reporting - system activity doesn’t show any output in the form of sa?? reports.

6

It’s only Fedora that’s pushing for Wayland-only on Plasma 6. openSUSE TW defaults to X11 with Plasma 6.

7

If you are having kernel issues with waking up from sleep, The first thing I would recommend to do is to

  • Report it as a Bug. it can’t get fixed if no one says anything about it.
  • Reboot, Default into a working kernel. Keep said kernel over updates as a fall back.

Isn’t this more of a Gnome/Wayland problem ? It’s gonna take time for things to come about in Wayland/land, but it needs to happen and development is coming along.

KDE Plasma can still run on X11. . .

You have to speak up if you have issues, it the only way to get things fixed in Open Source.

8

I’ve spoken up about the issue of not waking up, several years ago I was told no one else was having the issue. So instead of being a squeaky wheel I stopped complaining and in fact the problem got some better. I could go for weeks sometimes and not see the issue and then update and back to problems. I been told to search the journalctl logs for errors – There are no errors reported In fact the logs show no updates until the system is booted. No cron jobs run. It’s like the system is frozen.

My other issue of system not remembering the applications open and their position on workspaces has just started with latest update applied this past weekend. I get a completely blank desktop except for my wallpaper when I login. When I add the applications back each one comes up in the middle of the screen on whatever workspace I’m on. This is extremely aggravating. I spend time getting the workspaces set up before I’m able to do anything productive.

9

Blockquote

It’s only Fedora that’s pushing for Wayland-only on Plasma 6.

Blockquote

That’s good to know.

10

I know this has been re-hashed a lot, but in short: we’re pushing for it now because X11 has no future. Or, rather, the future of X11 is Wayland. I know that not everything works perfectly, but as long as we keep pretending that X11 is going to continue to be a viable option forever, it’s hard to get everything to work. So, someone needs to take the step, and that’s part of what Fedora does.

Sleep/power/suspend/wake issues are incredibly complex. Behavior depends on your specific hardware, the exact firmware versions, peripherals and their firmware (and, even in the same nominal model of laptop, these can differ). Plus kernel version, and external kernel drivers, too.

So, it’s not surprising that there are rare issues that other people can’t reproduce. It doesn’t mean they aren’t real problems — but unfortunately it does sometimes mean there aren’t easy fixes.

2 Likes