Hi,
I updated my system to Plasma 5.4.3. After I reboot sddm theme was automatically changed. Half of the system tray applets aren't loaded. No system app can be launched anymore. It says KDEInit couldn't launch 'app'.
On Saturday 14 Nov 2015 10:01:42 PM Sudhir Khanger wrote:
Hi,
I updated my system to Plasma 5.4.3. After I reboot sddm theme was automatically changed. Half of the system tray applets aren't loaded. No system app can be launched anymore. It says KDEInit couldn't launch 'app'.
Installing kf5 5.16 from updates-testing didn't help.
On 11/15/2015 12:31 AM, Sudhir Khanger wrote:
I updated my system to Plasma 5.4.3. After I reboot sddm theme was automatically changed. Half of the system tray applets aren't loaded. No system app can be launched anymore. It says KDEInit couldn't launch 'app'.
Yeah, this is a "disaster". (F22 x64)
It seems I had been running 5.4.2 stuff and I updated to 5.4.3. Thinking that maybe some libs were being kept in memory I rebooted. Yeah, the sddm theme changed and I was able to login. I got a message telling me the "boot image crashed". There was no mixer in the systray and while the clock was "there" noting was visible. I could hover over the area and it would show me a list of the timezones I had defined but the showed like "Taipei %2" and "London %2".
I really needed to get some work done so I did
dnf downgrade --allowerasing plasma-breeze plasma-breeze-common plasma-desktop plasma-desktop-doc plasma-milou plasma-nm plasma-nm-mobile plasma-nm-openconnect plasma-nm-openvpn plasma-nm-pptp plasma-nm-strongswan plasma-nm-vpnc plasma-systemsettings plasma-workspace plasma-workspace-common plasma-workspace-drkonqi plasma-workspace-geolocation plasma-workspace-geolocation-libs plasma-workspace-libs
And things are "working" but I'm back to 5.3.0 versions of plasma and lost some functionality such as there is no "24 hr" setting for the clock.
Can we get 5.4.2 back and kill the 5.4.3 stuff?
On 11/15/2015 04:15 PM, Ed Greshko wrote:
Can we get 5.4.2 back and kill the 5.4.3 stuff?
Oh, and I'm back to having to run "killall -9 drkonqi" again and I use "Folder View" and my home folder and trash are now missing from my desktop and I can't figure out how to get them back.
On 11/15/2015 04:19 PM, Ed Greshko wrote:
On 11/15/2015 04:15 PM, Ed Greshko wrote:
Can we get 5.4.2 back and kill the 5.4.3 stuff?
Oh, and I'm back to having to run "killall -9 drkonqi" again and I use "Folder View" and my home folder and trash are now missing from my desktop and I can't figure out how to get them back.
OK... After manually downloading and manually erasing stuff I finally did...
root@meimei ~]# dnf install --allowerasing ./plasma-workspace-drkonqi-5.4.2-4.fc22.x86_64.rpm ./plasma-workspace-common-5.4.2-4.fc22.x86_64.rpm ./plasma-workspace-5.4.2-4.fc22.x86_64.rpm ./libkworkspace5-5.4.2-4.fc22.x86_64.rpm ./plasma-workspace-libs-5.4.2-4.fc22.x86_64.rpm ./sddm-breeze-5.4.2-4.fc22.noarch.rpm ./plasma-workspace-geolocation-5.4.2-4.fc22.x86_64.rpm plasma-workspace-geolocation-libs-5.4.2-4.fc22.x86_64.rpm ./plasma-breeze-5.4.2-2.fc22.x86_64.rpm ./plasma-breeze-common-5.4.2-2.fc22.noarch.rpm ./kde-style-breeze-5.4.2-2.fc22.x86_64.rpm ./plasma-desktop-5.4.2-2.fc22.x86_64.rpm ./plasma-desktop-doc-5.4.2-2.fc22.noarch.rpm ./plasma-systemsettings-5.4.2-1.fc22.x86_64.rpm ./kf5-baloo-5.15.0-1.fc22.x86_64.rpm ./kf5-baloo-libs-5.15.0-1.fc22.x86_64.rpm
and I'm back to a "working" desktop with my Home and Trash folders back....
Damn, this is painful....
---- On Sun, 15 Nov 2015 13:45:16 +0530 Ed Greshko <ed.greshko@greshko.com> wrote ---- I really needed to get some work done so I did
dnf downgrade --allowerasing plasma-breeze plasma-breeze-common plasma-desktop plasma-desktop-doc plasma-milou plasma-nm plasma-nm-mobile plasma-nm-openconnect plasma-nm-openvpn plasma-nm-pptp plasma-nm-strongswan plasma-nm-vpnc plasma-systemsettings plasma-workspace plasma-workspace-common plasma-workspace-drkonqi plasma-workspace-geolocation plasma-workspace-geolocation-libs plasma-workspace-libs
$ sudo dnf downgrade --allowerasing plasma-breeze plasma-breeze-common plasma-desktop plasma-desktop-doc plasma-milou plasma-nm plasma-nm-mobile plasma-nm-openconnect plasma-nm-openvpn plasma-nm-pptp plasma-nm-strongswan plasma-nm-vpnc plasma-systemsettings plasma-workspace plasma-workspace-common plasma-workspace-drkonqi plasma-workspace-geolocation plasma-workspace-geolocation-libs plasma-workspace-libs Last metadata expiration check performed 0:23:27 ago on Tue Nov 17 08:06:22 2015. Package plasma-desktop-doc of lowest version already installed, cannot downgrade it. No match for available package: plasma-nm-mobile-5.3.0-1.fc22.x86_64 No match for available package: plasma-nm-mobile-5.4.3-1.fc22.x86_64 No match for available package: plasma-nm-strongswan-5.3.0-1.fc22.x86_64 No match for available package: plasma-nm-strongswan-5.4.3-1.fc22.x86_64 Error: package plasma-workspace-5.4.3-1.fc22.x86_64 requires plasmashell >= 5.4, but none of the providers can be installed
Regards, Sudhir Khanger, sudhirkhanger.com.
On 11/17/2015 11:01 AM, Sudhir Khanger wrote:
---- On Sun, 15 Nov 2015 13:45:16 +0530 *Ed Greshko ed.greshko@greshko.com* wrote ----
I really needed to get some work done so I did dnf downgrade --allowerasing plasma-breeze plasma-breeze-common plasma-desktop plasma-desktop-doc plasma-milou plasma-nm plasma-nm-mobile plasma-nm-openconnect plasma-nm-openvpn plasma-nm-pptp plasma-nm-strongswan plasma-nm-vpnc plasma-systemsettings plasma-workspace plasma-workspace-common plasma-workspace-drkonqi plasma-workspace-geolocation plasma-workspace-geolocation-libs plasma-workspace-libs
$ sudo dnf downgrade --allowerasing plasma-breeze plasma-breeze-common plasma-desktop plasma-desktop-doc plasma-milou plasma-nm plasma-nm-mobile plasma-nm-openconnect plasma-nm-openvpn plasma-nm-pptp plasma-nm-strongswan plasma-nm-vpnc plasma-systemsettings plasma-workspace plasma-workspace-common plasma-workspace-drkonqi plasma-workspace-geolocation plasma-workspace-geolocation-libs plasma-workspace-libs Last metadata expiration check performed 0:23:27 ago on Tue Nov 17 08:06:22 2015. Package plasma-desktop-doc of lowest version already installed, cannot downgrade it. No match for available package: plasma-nm-mobile-5.3.0-1.fc22.x86_64 No match for available package: plasma-nm-mobile-5.4.3-1.fc22.x86_64 No match for available package: plasma-nm-strongswan-5.3.0-1.fc22.x86_64 No match for available package: plasma-nm-strongswan-5.4.3-1.fc22.x86_64 Error: package plasma-workspace-5.4.3-1.fc22.x86_64 requires plasmashell >= 5.4, but none of the providers can be installed
I suppose I should have said YMMV.
Anyway things are working well with the following waiting to be updated...
kde-style-breeze.x86_64 5.4.3-2.fc22 updates libkworkspace5.x86_64 5.4.3-1.fc22 updates plasma-breeze.x86_64 5.4.3-2.fc22 updates plasma-breeze-common.noarch 5.4.3-2.fc22 updates plasma-desktop.x86_64 5.4.3-1.fc22 updates plasma-desktop-doc.noarch 5.4.3-1.fc22 updates plasma-milou.x86_64 5.4.3-1.fc22 updates plasma-nm.x86_64 5.4.3-1.fc22 updates plasma-nm-mobile.x86_64 5.4.3-1.fc22 updates plasma-nm-openconnect.x86_64 5.4.3-1.fc22 updates plasma-nm-openvpn.x86_64 5.4.3-1.fc22 updates plasma-nm-pptp.x86_64 5.4.3-1.fc22 updates plasma-nm-strongswan.x86_64 5.4.3-1.fc22 updates plasma-nm-vpnc.x86_64 5.4.3-1.fc22 updates plasma-systemsettings.x86_64 5.4.3-1.fc22 updates plasma-workspace.x86_64 5.4.3-1.fc22 updates plasma-workspace-common.x86_64 5.4.3-1.fc22 updates plasma-workspace-drkonqi.x86_64 5.4.3-1.fc22 updates plasma-workspace-geolocation.x86_64 5.4.3-1.fc22 updates plasma-workspace-geolocation-libs.x86_64 5.4.3-1.fc22 updates plasma-workspace-libs.x86_64 5.4.3-1.fc22 updates sddm-breeze.noarch 5.4.3-1.fc22 updates
But I may do what was suggested elsewhere in update from updates-testing for the plasma and kf5 stuff. Just need to wait until I can be assured of the time to recover if things go horribly wrong....
---- On Tue, 17 Nov 2015 09:19:12 +0530 Ed Greshko<ed.greshko@greshko.com> wrote ----
But I may do what was suggested elsewhere in update from updates-testing for the plasma and kf5 stuff. Just need to wait until I can be assured of the time to recover if things go horribly wrong....
Updating to kf5-5.16 and plasma-workspace from updates-testing and nuking current user didn't solve the problem for me.
Regards, Sudhir Khanger, sudhirkhanger.com.
F23: after latest kde* update my desktop computer is not usable at all: I get a black screen after the login. Now I am busy but as soon as possible I will give a look to the system logs. I wonder what happened to the testing process....
On Sunday 15 Nov 2015 10:59:23 Germano Massullo wrote:
F23: after latest kde* update my desktop computer is not usable at all: I get a black screen after the login. Now I am busy but as soon as possible I will give a look to the system logs.
Not much help to you, but the updates installed OK and everything works fine on this x86_64 F23 Desktop box running just a single monitor. The updates have been installed for a few days now and this is my main machine here so it gets a lot of use/testing.
Plasma 5.4.3, kf-5 5.16, qt-5.5 Nvidia/Nouveau
I wonder what happened to the testing process....
Difficult one.. I cherry pick what I can as others do from Koji and leave karma, the problem I guess is varying types of Hardware that is used and the limited amount of testers.
Apart from the creeping up of the RAM and sometimes I hit Swap, which sadly no time to look further into that yet :-( This is the only real issue for me. Also no more crashes or freezes or loss of Virtual Desktops since the fixes that went into Kwin a few weeks back.
As I said not much help to you but thought I would share my positive experience. I am more than pleased with "5" which has come a long way this year.
And as usual thanks to the OP's who provide these updates and for all there hard work.
Coin
"After login, screen is black and it shows only the mouse pointer" -> https://bugs.kde.org/show_bug.cgi?id=353963
I have the same problem, though on F22.
1. Killing "plasmashell --shut-up" and restarting the process sometimes brings the desktop back, but no KDE software will run.
2. kf5-kded and kmix each consume 100% cpu, and killing these allows me to launch konsole and other programs.
3. DNF has a rollback function, but the needed packages are no longer present in the repos, so it's of little help.
Having just moved to Fedora from OpenSUSE three weeks ago, I would be curious to know what normally happens in scenarios like these? Is this likely to be fixed in an imminent update or are we isolated cases and on our own?
On 11/16/2015 11:54 AM, Germano Massullo wrote:
"After login, screen is black and it shows only the mouse pointer" -> https://bugs.kde.org/show_bug.cgi?id=353963
2015-11-16 12:10 GMT+01:00 Tom Back three@tomback.org:Is this
likely to be fixed in an imminent update or are we isolated cases and on our own?
Actually nobody is taking care of that bugreport, so do not expect to get it fixed soon
P.S. If you provide logs and other infos in the bugreport, it will likely being more attentioned than now
On Monday 16 Nov 2015 12:10:36 PM Tom Back wrote:
- DNF has a rollback function, but the needed packages are no longer
present in the repos, so it's of little help.
Yep, that makes dnf undo or rollback useless but dnf devs think missing packages is not their problem in spite of the fact that it is a requirement for dnf rollback or undo to work. I don't know how that logic works for them.
Having just moved to Fedora from OpenSUSE three weeks ago, I would be curious to know what normally happens in scenarios like these? Is this likely to be fixed in an imminent update or are we isolated cases and on our own?
I have been as conservative as possible on this system. It's pretty sad and frustrating that Fedora has to break regularly. A few weeks ago CopyQ and ownCloud started crashing until that kf5-filesystemblahblah package was fixed. Now this had to happen.
I am seriously losing faith in distros that promote the latest and greatest software philosophy.
Sudhir Khanger wrote:
Yep, that makes dnf undo or rollback useless but dnf devs think missing packages is not their problem in spite of the fact that it is a requirement for dnf rollback or undo to work. I don't know how that logic works for them.
A big part of the problem is the totally insane keepcache=0 default in Fedora. This is a CRITICAL DATA LOSS bug by design! keepcache MUST default to 1!
Kevin Kofler
On Saturday, November 14, 2015 10:01:42 PM Sudhir Khanger wrote:
Hi,
I updated my system to Plasma 5.4.3. After I reboot sddm theme was automatically changed. Half of the system tray applets aren't loaded. No system app can be launched anymore. It says KDEInit couldn't launch 'app'.
I found a similar situation on F22. It appeared to be that kmix and konversation could not use their systray icons. The workaround for me was to replace kmix with plasma-pa (which works very well), and to disable konversation from starting at logon. -A
On Monday 16 Nov 2015 6:03:19 AM Anthony Messina wrote:
The workaround for me was to replace kmix with plasma-pa (which works very well), and to disable konversation from starting at logon.
I already use plasma-pm and I always start with a fresh session so no program like Konversation starts after login on my system.