Login Issues on 20150515.. Plasma 5.3 update

English Install/Boot/Login
#1

After Updating to the latest snapshot (20150515), Plasma desktop is crashing… unable to login… it gives an error - “Unable to find a system tray… exiting”… then tried it on a new user and even then it was unable to login but there was no “unable to find a system tray” error… just that exiting message… and “plasma has crashed…” dialog box…" Gnome login was working well… my graphics card is ATI 5700.
I tried changing the display manager to SDDM to see if that helps… but nothing, and now SDDM doesn’t allow me to login to any other desktop environment except KDE plasma… so I can’t even go to terminal/yast and add or remove any packages…
how can we login to an alternate environment from SDDM? if that is possible, then I can change the display manager… or else… how do I change my display manager back to KDM?

I also logged in to ICEWM before changing to SDDM and “startkde” command from there started Plasma5, but it crashed with “Plasma has crashed…” dialog box…

Also, for Plasma5, should I first disable the graphics from motherboard? or what packages could be conflicting?

#2

The display manager should not matter.

but nothing, and now SDDM doesn’t allow me to login to any other desktop environment except KDE plasma… so I can’t even go to terminal/yast and add or remove any packages…
how can we login to an alternate environment from SDDM?

Just select it at the login screen?

if that is possible, then I can change the display manager… or else… how do I change my display manager back to KDM?

How did you change to sddm in the first place?
Normally on openSUSE /etc/sysconfig/displaymanager is used to specify the display manager to be used. So change that back to kdm or whatever, you can do that in text mode too if needed.

If you ran “systemctl enable sddm.service” (like apparently some people seem to think is necessary), you’d have to enable the standard display-manager.service:

sudo systemctl enable display-manager.service

Again, you can do that in text mode, use Ctrl+Alt+F1 to switch to a text mode console.

I also logged in to ICEWM before changing to SDDM and “startkde” command from there started Plasma5, but it crashed with “Plasma has crashed…” dialog box…

What output did you get in the xterm?

Also, for Plasma5, should I first disable the graphics from motherboard?

No.
Plasma5 uses the same graphics stack as the rest of the system, so it should just work.

But as it uses more advanced features, a graphics driver problem might surface.
What does “glxinfo|grep render” say? (you might have to install Mesa-demo-x first)
You might want to try out the proprietary fglrx driver, the latest beta version should work on Tumbleweed too.
But you’d have to use Sebastian Siebert’s latest script to install it:
https://www.sebastian-siebert.de/

As GNOME works, Plasma5 should too though, I’d say.

or what packages could be conflicting?

No idea.
Normally none.

Hard to guess though.

#3

This morning, I upgraded a Tumbleweed install that was still on KDE4. My previous upgrade had been to one that I had already switched to Plasma 5.

Upgrading KDE4: I started by making the wrong choices in the conflict resolution dialog in zypper. At the third prompt, I realized that I was doing it wrong, so cancelled out and started over.

Once updated and rebooted, Plasma 5 was a mess. It seems to have kept some old KDE 4 settings that is should have dumped, and failed to keep some settings that it should have migrated. When I next boot into that system (it’s a different partition on my main desktop), I’ll clean out most of the settings files (user settings under $HOME) and make a fresh start.

I’m thinking that some folk must have found this very confusing.

#4

There is one particular conflict I know of (plasma-nm-xxx), that one should be fixed already but it will take some time until that’s in the repo.

Once updated and rebooted, Plasma 5 was a mess. It seems to have kept some old KDE 4 settings that is should have dumped, and failed to keep some settings that it should have migrated. When I next boot into that system (it’s a different partition on my main desktop), I’ll clean out most of the settings files (user settings under $HOME) and make a fresh start.

Can you provide more details, please?
What settings do you mean?

I’m using KDE4 and Plasma5 in parallel since over a year, and haven’t seen anything in Plasma5 (the desktop) “messed up”.
Mostly I’m using different users though, but I also logged into Plasma5 with my KDE4 user account already a few times.

And Plasma5 actually ignores KDE4’s settings, applications should migrate their settings though.

That said, the KDE4 application style settings are indeed changed by systemsettings5, that’s on purpose to make KDE4 applications look native in Plasma5.

#5

Yeah, that one was a little confusing, but if if you just accepted the zypper recommendations to deinstall, it installed the versions automatically.

#6

This is the first one I saw, and it confused me because usually the first option is the one to follow:


Problem: patterns-openSUSE-kde_plasma-20150505-1.1.x86_64 requires plasma5-session, but this requirement cannot be provided
  uninstallable providers: plasma5-session-5.3.0-1.1.noarch[CruzerA]
                   plasma5-session-5.3.0-1.1.noarch[Factory]
 Solution 1: keep obsolete patterns-openSUSE-kde4_basis-20150408-2.1.x86_64
 Solution 2: deinstallation of plasma-nm-openvpn-0.9.3.5-1.2.x86_64
 Solution 3: break patterns-openSUSE-kde_plasma-20150505-1.1.x86_64 by ignoring some of its dependencies

Can you provide more details, please?
What settings do you mean?

The kickoff menu looked pretty much like the old KDE4 menu. There was a “configure desktop”. There were no favorites. I had to use ALT-F2 to start the proper settings. I had the old “Applications”, “Computer”, “Recently Used” and “Leave” at the bottom.

After I set the panel to auto-hide, I was no longer able to bring up that menu (or any menu).

#7

Ok. I just tested this in a VM today, and the patterns got just removed automatically without a conflict.

Maybe caused by your installation medium still in the list? “CruzerA” would sound like that.

The kickoff menu looked pretty much like the old KDE4 menu. There was a “configure desktop”. There were no favorites. I had to use ALT-F2 to start the proper settings. I had the old “Applications”, “Computer”, “Recently Used” and “Leave” at the bottom.

So you still had “Kickoff”, which should migrate the Favorites settings since recently.

I’m not sure why you had Kickoff though, the openSUSE default is Kicker now.
Maybe you didn’t install some openSUSE branding package (plasma5-workspace-branding-openSUSE)? The upstream default still is Kickoff AFAIK.

After I set the panel to auto-hide, I was no longer able to bring up that menu (or any menu).

Hm. There was a problem with this in 5.2, but that should be fixed now.

Just to be clear here: you cannot bring up the panel? Or you cannot bring up the menu afterwards?

#8

That’s the 20150515 DVD installer iso. I downloaded for a clean install on one box. So I used it as an auxilliary repo when updating another (to reduce network traffic).

Just to be clear here: you cannot bring up the panel? Or you cannot bring up the menu afterwards?

Just the menu. The panel shows. I can click on the “K” for the menu, but nothing happens.

#9

Thank you! Display manager issue solved… even though I chose SDDM from yast, but it was somehow showing a generic display manager, so now back to KDM.

This is the output of glxinfo|grep render:

direct rendering: Yes
    GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer,
    GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer,
OpenGL renderer string: Gallium 0.4 on AMD JUNIPER
    GL_NV_conditional_render, GL_NV_depth_clamp, GL_NV_packed_depth_stencil,
    GL_NV_conditional_render, GL_NV_depth_clamp, GL_NV_fog_distance,
    GL_OES_element_index_uint, GL_OES_fbo_render_mipmap,

Using the built in AMD drivers. My graphics card is AMD Radeon 5700HD and I am using a Desktop PC.

The Output of startkde is here…

http://pastebin.com/1fawKszM

Also, installed the plasma-nm5, which wasn’t installed by default…

#10

I figured out the problem… it was due to some more missing packages, which should have been installed by default… like plasma-activity5 and so on… so after that, things are working well so far :slight_smile:

#11

Well, another snapshot has been published yesterday, so…

Just the menu. The panel shows. I can click on the “K” for the menu, but nothing happens.

That’s strange.
And it only happens when the panel is configured to slide out?

I’ll try to reproduce it…

#12

Yes, I know that. But not much changed. So most of what is on the DVD installer iso is still up to date. And “zypper dup” should be able to take care of that, using the Tumbleweed repo (named “Factory” in that output) for anything newer. It still reduces network load both here and on the selected mirror.

And it only happens when the panel is configured to slide out?

Yes, assuming that “slide out” means the same as “auto hide”.

I suppose I could turn auto-hide off and see if the menu comes back.

It’s probably hard to reproduce. I’m pretty sure it won’t happen if I delete a bunch of settings files and start over.

#13

Ok, but still, IMHO that conflict shouldn’t occur if you don’t have an outdated repo/DVD.

If it still does, it might be worth a bug report.

Yes, assuming that “slide out” means the same as “auto hide”.

Yes, that’s what I meant.

I did try with that, and I cannot reproduce the problem here…

#14

The message that it associated with “CruzerA”, it also associated with “Factory” which is the Tumbleweed OSS repo. As a cross check, “/etc/os-release” was updated to 20150516 which had to be from “Factory”.

In any case, this was likely a one-time event, so not worth a bug report. That particular Tumbleweed system was originally installed as Factory on June 30 last year. It has probably built up some debris by now, which might be involved.

#15

I just re-read your error message and noticed that I actually misinterpreted it, sorry.

Actually it means that plasma5-session cannot be installed because of plasma-nm-openvpn, i.e. the KDE4 plasma-nm openvpn plugin.
plasma5-session requires plasma-nm5, which cannot be installed without removing plasma-nm-openvpn, because the latter one requires plasma-nm which is replaced by plasma-nm5.

You have to choose “Solution 2: deinstallation of plasma-nm-openvpn-0.9.3.5-1.2.x86_64”.

Actually it is/was the same issue that the plasma-nm5-xxx packages didn’t obsolete plasma-nm-xxx by mistake.
As this has been fixed in the meantime, it was a “one-time event” obviously.