KDE frameworks 5.10.0 + Plasma 5.3.1 + Apps 15.04.2

[krisbee]

I tried doing the upgrade on a spare laptop - an HP G72. Not good. There is now nothing available on the desktop. I moved my .kde, .config and .local, but still just had a background on the screen, no toolbar, no response to right click. I could get the runner up with Alt-F2, but as soon as I typed anything into it, it crashed.
I'll run dist-upgrade on it over the next few weeks and see if anything comes back. It's definitely something to beware of at this stage.

I've done an install of "KDE frameworks 5.10.0 + Plasma 5.3.1 + Apps 15.04.2" in a virtual machine and end up with the same result as Pip -  just had a background on the screen, no toolbar, no response to right click etc.

I started with a fully updated siduction KDE install.  Before following the posted upgrade steps, I removed all widgets and reverted theme, style, icons etc back to oxygen.  Wasn't sure if the system was still expected to work with lightdm, or not, but I left that inplace.

[holgerw]

Hello Santa,


I've installed further stuff like kde-standard. Now I have sddm login, but when choosing plasma and trying to login, the start procedere hangs and then I get rests of lx session.

kwin is installed, plasma-desktop is installed. Have I install another meta-package for kf5?

To your questions:

Code: [Select]

update-alternatives --list x-session-manager shows me icewm and startkde

Then I've done

Code: [Select]

update-alternatives --set x-session-manager /usr/bin/startkdeBut after restating sddm and trying to login I get plank panel.

After removeing plank package and a new login I get a crash dialog of kinit5.

Now I'll try to remove .kde directory and a new login.

Kind regards,
  Holger


P.S.: Removing .kde directory does not help. A login ends with sddm breeze screen and a mouse cursor. Then I chose icewm, a login is possible, icwm starts but then I also get a crash dialog from kinit5.

[holgerw]

Hi,

kf5 seems not usable when adding it to a lxde siduction installation. With old kf5 and plasma5.2 stuff this was possible without any trouble.

system is up-to-date

Metapackage plasma-desktop is installed, kwin, sddm, breeze and further stuff is installed, this should be enough to get a working kf5 session.

But I only get a crash dialog of kinit5.

Login lxsession, openbox or icewm works, so it has not to do with wrong xserver configuration.

And it also has not to do with kf5 code, because manjaro and antergos give me a current kf5 and plasma 5.3.1, with is working without any trouble, apart from a bug, when trying to modify special window settings.

My next try will start with an up-to-date siduction kde4 installation. I'll report here.

Kind regards,
  Holger

[holgerw]

Hello,

I've made another test.
1. Installing siduction indian summer KDE 64 bit
2. making dist-upgrade
3. restarting and adding kdenext unstable, making further dist-upgrade
4. adding kdenext kf5 and making further dist-upgrade
5. replacing lightdm with sddm
6. systemctl stop lightdm && systemctl start sddm
7. trying to login
8. only get sddm splash with mouse cursor

Metapackage plasma-desktop is installed, so I've no further idea, what could be wrong here.

Santa, if you need further info, please let me know.

Kind regards,
  Holger

[tmhind2]

In my case I log-in to Plasma and get a crash with a bug report in which I ran (gdb) and got a clean 40 plus entries. The last line reported by (gdb) was "/usr/lib/x86_64-linux-gnu/qt5/plugins/kpackagestructure/plasma-packagestructure_plamsashell.so" with "0x00007fa5d095d6fd in nanosleep () from /lib/x86_64-linux-gnu/libc.so.6 (gdb)". Though I am new to having problems I will continue to look deeper into what I may have done by mistake in causing this problem after my last dist-upgrade, will advise if I find anything.


Regards,
Tom

[Santa]

Hello guys,


due to messages you posted (specially holger's about installing plasma 5 on siduction lxde) I have tested the following: installing kde-standard In a virtual machine with siduction noX december. I had the following issues:
1. I had to install virtualbox-guest-x11 and virtualbox-guest-dkms, otherwise the X server crashes
2. After installing the virtualbox guest additions via the packages mentioned in 1. I tried to start a kde session with startx and I got the nice kde splash screen, then kdeinit crashing and a black screen.


I also noticed 2. is "fixed" when you install kde-full with the recommends enabled; that's the setup I use to test the dist-upgrades, hence why the problem went under the radar.


That being said, summary of the issues reported so far:
- Pip got his desktop empty and kruner crashing.
- tmhind2 got his desktop crashed and a black screen.
- holgerw couldn't make plasma 5 work on top of lxde.
- holgerw upgraded from an indiansummer kde installation,but plasma 5 doesn't start
- reddark got ¿plasma-shell? eating the 100% of the cpu


I think the last one is an upstream issue and all the other ones just the issue I have described in the point 2. above.


Last but not least, a fix for the black screen is on the way, stay tuned.

[tmhind2]

Thanks Santa, I'll sit back and wait for the fix.


Regards, tom

[Pip]

Nice to hear, Santa. I was sure it would be resolved at some point, but this is more rapid than I'd hoped.

[krisbee]

Santa,

With your fixes, will we  be able install KDE5 without having to do a Kde-full for KDE4 first?  Siduction defaults to "APT::Install-Recommends "0";" -  I presume you will test with this setting.

Looking forward to getting KDE5 running.

[Santa]

Santa,

With your fixes, will we  be able install KDE5 without having to do a Kde-full for KDE4 first?  Siduction defaults to "APT::Install-Recommends "0";" -  I presume you will test with this setting.

Looking forward to getting KDE5 running.

Yes, at least you will be able to start plasma. You are suposed to be able to run plasma after installing kde-standard, no matter the situation.

[dibl]

I also noticed 2. is "fixed" when you install kde-full with the recommends enabled ...

Excellent -- thanks for this.  I too had the kdinit and kwin crashes, even with kde-full installed.  After reading this, I went back and installed the kdeaccessibility and kdesdk packages, and one of those (or their dependencies) fixed it.  Working good again.

[holgerw]

Hello @dibl,

thanks for your hint, the installation of kdesdk solved the starting issues on my computer.

Kind regards,
  Holger

[Santa]

The most important problem is fixed in the latest packages available, let's start a new clean thread to discuss any other possible issue:
http://forum.siduction.org/index.php?topic=5593.0