SDDM or Plasma6 desktop don't start

Support
, , ,
1

Hello,

Requirements:

I have Searched the forum for my issue and found nothing related or helpful
I have checked the Resources category (Resources Index)
I have reviewed the Wiki for relevant information
I have read the the Release Notes and Errata

OpenMandriva Lx version:
6.0 Rome

Desktop environment (KDE, LXQT…):
KDE Plasma 6

Description of the issue (screenshots if relevant):
Plasma 6 and SDDM always crashes. Although I’ve had it crashed on other distributions as well. Sometimes. But it’s already very weird, I have never seen anywhere that it was directly, well, completely unusable. What causes this to happen? Even Arch didn’t have a similar issue.

Relevant informations (hardware involved, software version, logs or output…):

Machine:
  Type: Laptop System: ASUSTeK product: TUF GAMING FX504GD_FX80GD v: 1.0
    serial: <superuser required>
  Mobo: ASUSTeK model: FX504GD v: 1.0 serial: <superuser required>
    UEFI: American Megatrends v: FX504GD.322 date: 08/23/2021
Battery:
  ID-1: BAT1 charge: 19.3 Wh (73.9%) condition: 26.1/48.1 Wh (54.4%)
    volts: 3.4 min: 11.7 model: ASUS A32-K55 status: discharging
CPU:
  Info: quad core model: Intel Core i5-8300H bits: 64 type: MT MCP
    arch: Coffee Lake rev: A cache: L1: 256 KiB L2: 1024 KiB L3: 8 MiB
  Speed (MHz): avg: 1500 min/max: 800/2300 cores: 1: 1500 2: 1500 3: 1500
    4: 1500 5: 1500 6: 1500 7: 1500 8: 1500 bogomips: 36799
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel CoffeeLake-H GT2 [UHD Graphics 630] vendor: ASUSTeK
    driver: i915 v: kernel arch: Gen-9.5 bus-ID: 00:02.0
  Device-2: NVIDIA GP107M [GeForce GTX 1050 Mobile] vendor: ASUSTeK
    driver: nvidia v: 570.133.07 arch: Pascal bus-ID: 01:00.0
  Device-3: Azurewave USB2.0 HD UVC WebCam driver: uvcvideo type: USB
    bus-ID: 1-7:4
  Display: wayland server: X.org v: 1.21.1.16 with: Xwayland v: 24.1.6
    compositor: kwin_wayland driver: X: loaded: modesetting,nvidia dri: iris
    gpu: i915 resolution: 1920x1080~60Hz
  API: EGL v: 1.5 drivers: iris,nouveau,nvidia,swrast platforms:
    active: gbm,wayland,x11,surfaceless,device inactive: N/A
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: intel mesa v: 25.0.4-arch1.1
    glx-v: 1.4 direct-render: yes renderer: Mesa Intel UHD Graphics 630 (CFL
    GT2)
  Info: Tools: api: eglinfo,glxinfo de: kscreen-console,kscreen-doctor
    gpu: nvidia-settings,nvidia-smi x11: xprop,xrandr
Audio:
  Device-1: Intel Cannon Lake PCH cAVS vendor: ASUSTeK driver: snd_hda_intel
    v: kernel bus-ID: 00:1f.3
  API: ALSA v: k6.14.2-artix1-1 status: kernel-api
  Server-1: PipeWire v: 1.4.2 status: active
Network:
  Device-1: Intel Cannon Lake PCH CNVi WiFi driver: iwlwifi v: kernel
    bus-ID: 00:14.3
  IF: wlan0 state: up mac: <filter>
  Device-2: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    vendor: ASUSTeK driver: r8169 v: kernel port: 3000 bus-ID: 03:00.0
  IF: eth0 state: down mac: <filter>
Bluetooth:
  Device-1: N/A driver: btusb v: 0.8 type: USB bus-ID: 1-14:5
  Report: rfkill ID: hci0 rfk-id: 0 state: up address: see --recommends
Drives:
  Local Storage: total: 1.8 TiB used: 177.3 GiB (9.6%)
  ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 980 500GB size: 465.76 GiB
    temp: 28.9 C
  ID-2: /dev/sda vendor: Western Digital model: WD10SPZX-22Z10T1
    size: 931.51 GiB
  ID-3: /dev/sdb vendor: Kingston model: SA400S37480G size: 447.13 GiB
    type: USB
Partition:
  ID-1: / size: 48.91 GiB used: 27.3 GiB (55.8%) fs: ext4 dev: /dev/sdb2
  ID-2: /boot/efi size: 147.7 MiB used: 283 KiB (0.2%) fs: vfat
    dev: /dev/sdb1
  ID-3: /home size: 171.2 GiB used: 150 GiB (87.6%) fs: ext4 dev: /dev/sdb3
Swap:
  Alert: No swap data was found.
Sensors:
  System Temperatures: cpu: 50.0 C pch: 56.0 C mobo: N/A
  Fan Speeds (rpm): cpu: 0
2

This might be a graphics issue, something not handling dual graphics properly. Try logging in to Console Mode and then trying these methods to start desktop and see if one works.

startplasma-wayland

startx (not sure if this one even works under Wayland session)

sudo systemctl start sddm

We are looking for something that works, but more important we are looking for error messages that tell us why desktop or sddm or graphics is not starting.

Do you know how to get logs like dmesg and journalctl in to a .txt file you can post here? That is the best information for technical problems. journalctl -b > journalctl-b.txt for example would create a file journalctl-b.txt that you can post here. dmesg > dmesg.txt for that one.

3

Welcome message

Welcome to OpenMandriva and our forum. This forum is for users of OpenMandriva Linux operating systems.

OpenMandriva forums are mainly users helping other users.

You can talk to our developers at OpenMandriva Chat.

Users with problems need to read How to get better results when posting about problems before reporting any issues or problems. The article is not too long and Do Read.

When a new user has a problem please search the OMLx documentation. OpenMandriva wiki, Forum Resource Guide and the “Search” function of the forum.

If you don’t find what you are looking for, try an Internet search. A lot can be found in the documentation or forum posts for other Linux distributions. If the user finds something written for another distro but has a question, ask in OpenMandriva Chat.

For serious technical problems and package/feature requests please submit a bug report here.

Note: We are a small group. All contributors and developers are unpaid volunteers.
You can make OpenMandriva grow and improve by getting involved.

Any help with testing will be appreciated, whether you are a technical expert or not. The more people and hardware we can get involved, the better we can do OMLx releases and packaging. We also do a lot of testing on virtual machines. Developers tend to use Qemu, most user-level testers use VirtualBox..

Some suggestions that we hope will be useful:

We ask that problems reported in the forum or in a bug report be limited to one problem per thread or report.

We suggest that if your problem reported in the forum or in OM-Chat is not resolved within a few days, please file a proper bug report.

If you have not already done so, scroll through the “Big Warning” at the top of this page and read the information or use the links provided.

Before reporting any problems, read this.

We are simply and respectfully trying to make people aware that as a very small group we are volunteering, without remuneration, our time, expertise, etc, to help you.

4

If you have dual monitor disconnect one of them to see if anything will change.

5

Tried to run commands:

startplasma-wayland
Startplasmacompositor: could not start D-Bus. Can you call qdbus?

It started, but not usable, IDK, it maybe OK if not preconfigured. Red background and cursor.

startx

It’s the same issue as in that video I made before.

sudo systemctl start sddm

dmesg.txt (111.6 KB)
journalctl-b.txt (441.0 KB)

I also installed Lxqt, it doesn’t work correctly too.It seems to be much more complicated than just crashing Plasma.

6

I don’t have dual monitor.

1 Like
7

Thanks for providing those logs, very helpful.

Of course it is not the Plasma6 desktop crashing the desktop is not starting or it may be something right before the desktop like sddm or systemd or something in the dual graphics setup that is not being handled correctly. Those all remain true for LXQt. In your journal log sddm-helper-start-x11user looks very unhappy.

A first guess: 2 things you could try, they won’t hurt anything:

  1. Login with Console Mode and run:

sudo systemctl enable sddm.service

If the output shows that command creating a symlink that is likely the problem. If it did create a symlink then reboot and see if system is working properly. If not try:

  1. rpm -e --nodeps sddm and then immediately:
    sudo dnf in sddm --refresh reboot and see if that works.

Meanwhile I am posting your logs to developer chat room and we can see if they have any suggestions.

Note: If you want to know more look in the journlctl-b.txt the parts referring to sddm-helper and sddm-helper-start-x11user that part looks pretty abnormal.

8

Another thing to try is login to Console Mode and run these in sequence:

sudo dnf clean all
sudo dnf dsync --allowerasing

Be sure to note if that 2nd command removes anything and write down what it removes just in case.

Edit: There is no Plasma crash in your logs I changed the title of the thread to “SDDM or Plasma6 desktop don’t start” to be more accurate to the actual problem. This is so if we resolve this other users that may have the same issue can find the thread.

Edit-2: The video makes me think that graphics is not the issue here, but we shall see.

9

Unfortunately, your GTX 1050 is too old to test the nvidia open driver. We see a lot of issues clear up with it. Since nvidia’s goal is to have the open driver be the default for Linux, they may choose to legacy the proprietary driver in the near future. I think the oldest supported card is the GTX 16xx chipset. I think the confusion about multi-monitor is because you have 3 graphics drivers listed.

If you don’t need Wayland, I would suggest using X11 instead. We support that graphics server and offer Wayland as a convenience. We hope people may show up someday to help patch it, but it’s not a priority. I don’t know if LXQT even supports Wayland.

Arch is not a true Rolling distribution:
https://openmandriva.pkgs.org/rolling/openmandriva-nonfree-release-x86_64/nvidia-kmod-desktop-575.51.02-1_6.14.2_3-omv2590.x86_64.rpm.html

https://archlinux.org/packages/extra/x86_64/nvidia/

Our version is newer.

Please also see where they have confirmed what nvidia has decided for the state of their driver:

https://wiki.archlinux.org/title/NVIDIA#Installation

10

@Sainosaur’s dmesg.txt shows this:

[Thu May  8 20:04:40 2025] nouveau 0000:01:00.0: Enabling HDA controller
[Thu May  8 20:06:06 2025] nouveau 0000:01:00.0: Enabling HDA controller
[Thu May  8 20:06:19 2025] nouveau 0000:01:00.0: Enabling HDA controller
[Thu May  8 20:07:06 2025] nouveau 0000:01:00.0: Enabling HDA controller
[Thu May  8 20:07:31 2025] Non-volatile memory driver v1.3
[Thu May  8 20:07:32 2025] nouveau 0000:01:00.0: Enabling HDA controller
[Thu May  8 20:07:33 2025] st: Version 20160209, fixed bufsize 32768, s/g segs 256
[Thu May  8 20:07:33 2025] sd 4:0:0:0: Attached scsi generic sg0 type 0
[Thu May  8 20:07:33 2025] sd 6:0:0:0: Attached scsi generic sg1 type 0
[Thu May  8 20:07:33 2025] sd 5:0:0:0: Attached scsi generic sg2 type 0
[Thu May  8 20:07:33 2025] warning: `hwinfo' uses wireless extensions which will stop working for Wi-Fi 7 hardware; use nl80211
[Thu May  8 20:08:01 2025] nouveau 0000:01:00.0: Enabling HDA controller
[Thu May  8 20:08:31 2025] nouveau 0000:01:00.0: Enabling HDA controller
[Thu May  8 20:09:24 2025] nouveau 0000:01:00.0: Enabling HDA controller
[Thu May  8 20:10:11 2025] nouveau 0000:01:00.0: Enabling HDA controller
[Thu May  8 20:10:41 2025] nouveau 0000:01:00.0: Enabling HDA controller
[Thu May  8 20:10:56 2025] nouveau 0000:01:00.0: Enabling HDA controller
[Thu May  8 20:11:25 2025] traps: Thread (pooled)[66460] trap int3 ip:7fae505a474b sp:7fae25718370 error:0
[Thu May  8 20:11:25 2025] traps: Thread (pooled)[66458] trap int3 ip:7fae505a474b sp:7fae2671a370 error:0
[Thu May  8 20:11:25 2025]  in libglib-2.0.so.0.8400.1[11a74b,7fae5053b000+c1000]
[Thu May  8 20:11:25 2025]  in libglib-2.0.so.0.8400.1[11a74b,7fae5053b000+c1000]

[Thu May  8 20:11:41 2025] nouveau 0000:01:00.0: Enabling HDA controller
[Thu May  8 20:12:02 2025] nouveau 0000:01:00.0: Enabling HDA controller

Looks like it is using or trying to use nouveau.

1 Like
11

I got the sense from one developer that sddm was not the problem and maybe, maybe this is related to graphics. He did suggest that you try X11 rather than Wayland. To do that:

sudo dnf in task-plasma6-x11

If this works and you get an sddm login screen you select the Plasma X11 session in the lower right corner of that login screen.

13

Yes, the problem is indeed the graphics. To be more precise, in the nouveau driver. It often worked badly for me and caused bad experiences in other distributions.

The actual solution:

  1. Load to console mode
  2. Install proprietary driver with this command
    $ sudo dnf install --enablerepo rolling-x86_64-non-free nvidia-dmks-kmod nvidia-settings

After reboot and now I have no problems with any desktop environment or display manager. Except for the blackened Welcome. I read that the proprietary driver is not officially supported by your distribution. So will there be any problems with it afterwards?

1 Like
14

The latest versions have already added support for 10 series cards. Do you think it is worth switching?

15

Glad you got this working. I learned a bit chasing this issue.

1 Like
16

Thank you so much. The developers of the distribution should have added a boot with a proprietary nVidia driver to the Live system and a section for installing it in the console on the Wiki, it’s not very obvious how to do it, I had to dig through the forum and sections of the Wiki not directly related to the driver.

17

You will need to confirm that with the link in this post:

The long standing support matrix for these cards was GTX 16xx or higher cards support the open driver.

18

The post is closed. I can only send links here.

19

If you have more recent documents, go ahead and install it if you want to test it. That’s why it is there.

20

None of those links have anything to do with nvidia drivers. That has to do with Vulkan support.