Problem with KDE Plasma Wayland
Page 1 of 1 (9 posts)
Tags:
None
Registered Member 
|
Good Morning I am on the OS Nobara Project based on Fedora, I have an AMD GPU RX 5700 XT (but I don't think it is a gpu issue). For that to be clear I will do it as a list.
My problems : Wayland session do not start after login it take me back to login page it is a loop to login page X11 session After login and splash screen I got a black screen with my mouse visible What I did : Trying to launch wayland and x11 session as root with startx and startplasma-wayland) it work Trying to launch wayland and x11 with my user (not working) When blocking on black screen in x11 killing process of x11 and relogin with my normal user and it work and when I log one time at X11 session then killing process and starting a wayland session it is working. Reinstall wayland (not solvign my problem) Reinstall x11 (not solving my problem) Reinstall KDE (not solving my problem) Deleting on my normal user everything who got a reference to dbus kde x11 wayland in /home/myuser/.config|.local|.cache and in the home (not working) My logs : Launching with my user session wayland : QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-thimoty' startplasmacompositor: Could not start D-Bus. Can you call qdbus? Maybe a right problem but didn' find out for the moment With my user a X11 session : /usr/libexec/Xorg.wrap: Only console users are allowed to run the X server (Right problem there too ?) Logs of 1 hours of me tryng to fix my kde : https://controlc.com/eadba292 So finally my problem it is that I have to log in the X11 session physically and remoting in ssh kill X11 process and reconnect because if I don't do that I have a blackscreen or a loop login but plasma is working but not totally. If someone could help me I will thank you him so much. I hope someone could help me. I worked 2 days on this problem and can't figure out why isn't working and the worst it is I finished installed my computer 4 days ago, so my goal it is not to reinstall my os and figured out how to fix that problem because I really don't understand why kde stop work properly 2 days ago. Have a good day guys ! |
|
Registered Member
|
Hi!
First to mention: Never ever start a graphical program as root. The underlying framework (Qt in this case) does not support this and you can mess up a lot of permissions. This is often resulting in a login-loop. So check your users permissions and fix them in a virtual tty if necessary:
Next to check is the journal with `journalctl` and plausible filters, e.g. `journalctl -b -p warning` for all warnings and errors since last boot to get known problems on your system. |
|
Registered Member
|
Hi, first thank you for you answer.
So the only things I found are download I did so that don't have impact after using "find $HOME ! -user $USER -ls :
So I have checked for warning about KDE, plasma or wayland related there is some but nothing I understand look like minor warning >> Warning logs : https://controlc.com/940e9d5a And for error I got this, but ntohing about kde or wayland :
|
|
Registered Member
|
That looks "interesting". There are a lot of dbus-errors and as dbus is the main process communication bus you should investigate this first. Have a look at your distribution related help first as this could be related on how this distro starts up and works (I don't know it, never even heard of it 'til now
 )The logs: You should check the failed units. They can run anyway after retrying, so use `systemctl status UNITNAME` to get some basic information. Your plasmashell isn't running:
|
|
Registered Member
|
Hi thank you again for you answer so I looked for what you told me So I checked my directory about dbus services everything is there :
But the things I find out in the log that kde is calling the path of service : Service file '/usr/share//dbus-1/services but with 2 slash "//" : /user/share// << here I tried to a systemctl status and an example of service like with dolphin who is : org.kde.dolphin.FileManager1.service But the system can't find it so my question is the following where in the system can I add the path of called service for dbus and where can I change the path of called dbus in kde ? |
|
Registered Member
|
DBus is not the same as systemd-units. The unit to check is the autostart service like mentioned in the error log:
To get a single state you can use `systemctl --user status app-com.nextcloud.desktopclient.nextclo ... rt.service`, but it would be easier to check for failed only:
Your distribution seems to use dbus-broker instead of the classic dbus.service. So check for both as they cannot run in parallel afaik.
That isn't a problem at all as duplicated slashs are stripped down automatically. Entering `ls ////usr//////share` is the same as `ls /usr/share` |
|
Registered Member
|
So finally find out the problem that was not about dbus. After reinstalling 2 times Nobara Project and reinstall 2 times Fedora 35 and reinstalling my software I use for each installation. I figured out where is the problem. So for people with KDE on Fedora 35 or 36 (Nobara Project is on fedora 36) do not install tigervnc-server that the soft who make login loop and make crahs kde plasma I figured out when reinstalling and testing each packet. Hope that help, iswitched to fedora 35 because it is more stable finally. Good bye and thank you for help guys.
|
|
Registered Member
|
Thanks for sharing. Do you have some log information with crash details, eg. journalctl output or a link to the bugreport?
|
|
Registered Member
|
Hi, unfortunally tigervnc did not write logs, so I don't have, sorry. And that is why I took so much time to find out what made it crash. |
Page 1 of 1 (9 posts)
Bookmarks
Who is online
Registered users: abc72656, Bing [Bot], daret, Google [Bot], Sogou [Bot], Yahoo [Bot]
