Re: KDE Neon Developer Unstable - plasmashell crashing on start

Thanks for the fast replys. Will wait for the new packages ;-) One further question. What is the real difference between developer stable / unstable? My understanding was, that (for example) a change to qt5.10 will first be done in unstable and when everything is in place it will be rolled out

Re: KDE Neon Developer Unstable - plasmashell crashing on start

Yeah, there is ongoing migration to qt5.10 So it is known that it is broken... I hope to get this fixed sooner, only few rebuilds remianing On Thu, Feb 22, 2018 at 10:38 PM, Jörn M wrote: > Hello, > > today I noticed that KDE Neon developer unstable updates to Qt 5.10. > The

Re: KDE Neon Developer Unstable - plasmashell crashing on start

Short correction, I'm using: KDE neon developer stable Am 22.02.2018 18:08 schrieb "Jörn M" : > Hello, > > today I noticed that KDE Neon developer unstable updates to Qt 5.10. > The currently rolled out packages leave my system in an unusable state: > > - plasmashell

Re: KDE Neon Developer Unstable - plasmashell crashing on start

Bhushan is current landing Qt 5.10 which is why the dev editions are currently in flux. On Thu, Feb 22, 2018 at 6:08 PM, Jörn M wrote: > Hello, > > today I noticed that KDE Neon developer unstable updates to Qt 5.10. > The currently rolled out packages leave my system in an

Re: KDE Neon Developer Unstable - plasmashell crashing on start

Can confirm; I'm seeing the same thing. Nate On 02/22/2018 10:08 AM, Jörn M wrote: Hello, today I noticed that KDE Neon developer unstable updates to Qt 5.10. The currently rolled out packages leave my system in an unusable state: - plasmashell crashes: ~> plasmashell org.kde.plasmaquick:

KDE Neon Developer Unstable - plasmashell crashing on start

Hello, today I noticed that KDE Neon developer unstable updates to Qt 5.10. The currently rolled out packages leave my system in an unusable state: - plasmashell crashes: ~> plasmashell org.kde.plasmaquick: Applet preload policy set to 1 plasmashell: relocation error: