FYI, sent of kf5-5.31.0 and plasma-5.8.6 to -testing (both kde-testing and updates-testing) repos yesterday ,
f25 kf5: https://bodhi.fedoraproject.org/updates/FEDORA-2017-0f6aa187ff
f25 plasma: https://bodhi.fedoraproject.org/updates/FEDORA-2017-5460cc282a
f24 kf5: https://bodhi.fedoraproject.org/updates/FEDORA-2017-4ce7411a87
f24 plasma: https://bodhi.fedoraproject.org/updates/FEDORA-2017-c262a33752
epel7 kf5: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-18d82f816f
For f25/f24, please test and offer feedback, thanks.
-- Rex
On Friday, 24 February 2017 17:28:04 GMT Rex Dieter wrote:
FYI, sent of kf5-5.31.0 and plasma-5.8.6 to -testing (both kde-testing and updates-testing) repos yesterday ,
For f25/f24, please test and offer feedback, thanks.
Been using these since you released them last night and have found no issues so far on this F25 box, Karma left.
Thanks to all involved..
Colin
On 02/25/17 01:28, Rex Dieter wrote:
FYI, sent of kf5-5.31.0 and plasma-5.8.6 to -testing (both kde-testing and updates-testing) repos yesterday ,
Been using this for about a day now with no observed issues.
I do wish someone would patch DigitalClock.qml already so you don't have a tiny clock in the systray.
On Fri, Feb 24, 2017 at 9:28 AM, Rex Dieter rdieter@math.unl.edu wrote:
FYI, sent of kf5-5.31.0 and plasma-5.8.6 to -testing (both kde-testing and updates-testing) repos yesterday ,
Hey Rex, Immediately after the upgrade started receiving the "black screen" issue others have reported. :-( Sending this note from lxqt. kde for me right now is unusable.
On 02/25/17 22:37, Gerald B. Cox wrote:
On Fri, Feb 24, 2017 at 9:28 AM, Rex Dieter <rdieter@math.unl.edu mailto:rdieter@math.unl.edu> wrote:
FYI, sent of kf5-5.31.0 and plasma-5.8.6 to -testing (both kde-testing and updates-testing) repos yesterday ,
Hey Rex, Immediately after the upgrade started receiving the "black screen" issue others have reported. :-( Sending this note from lxqt. kde for me right now is unusable.
FWIW, on an older system which was behind on updates I updated everything simultaneously. There was a kernel update and others thrown into the mix. After a reboot I had a "black screen" and a bunch of errors in my Xorg.0.log that I failed to save. :-(
Anyway I disabled the kde-testing and updates-testing repos and did a "dnf distro-sync". This gave me a usable system again.
I then enabled kde-testing and updated and rebooted. Now everything still works.
Not sure why....
By going though the updates, one by one I found the culprits: Packages Altered: Upgraded libkworkspace5-5.8.5-5.fc25.x86_64 @updates Upgrade 5.8.6-2.fc25.x86_64 @updates-testing Upgraded plasma-lookandfeel-fedora-5.8.5-5.fc25.noarch @updates Upgrade 5.8.6-2.fc25.noarch @updates-testing Upgraded plasma-workspace-5.8.5-5.fc25.x86_64 @updates Upgrade 5.8.6-2.fc25.x86_64 @updates-testing Upgraded plasma-workspace-common-5.8.5-5.fc25.x86_64 @updates Upgrade 5.8.6-2.fc25.x86_64 @updates-testing Upgraded plasma-workspace-drkonqi-5.8.5-5.fc25.x86_64 @updates Upgrade 5.8.6-2.fc25.x86_64 @updates-testing Upgraded plasma-workspace-geolocation-5.8.5-5.fc25.x86_64 @updates Upgrade 5.8.6-2.fc25.x86_64 @updates-testing Upgraded plasma-workspace-geolocation-libs-5.8.5-5.fc25.x86_64 @updates Upgrade 5.8.6-2.fc25.x86_64 @updates-testing Upgraded plasma-workspace-libs-5.8.5-5.fc25.x86_64 @updates Upgrade 5.8.6-2.fc25.x86_64 @updates-testing Upgraded sddm-breeze-5.8.5-5.fc25.noarch @updates Upgrade 5.8.6-2.fc25.noarch @updates-testing
I didn't narrow it down any further because of package dependencies, but if you dnf downgrade the above packages, you'll eliminate the black screen issue. I'll create a bug...
On Sat, Feb 25, 2017 at 6:54 AM, Ed Greshko ed.greshko@greshko.com wrote:
On 02/25/17 22:37, Gerald B. Cox wrote:
On Fri, Feb 24, 2017 at 9:28 AM, Rex Dieter <rdieter@math.unl.edu mailto:rdieter@math.unl.edu> wrote:
FYI, sent of kf5-5.31.0 and plasma-5.8.6 to -testing (both kde-testing and updates-testing) repos yesterday ,
Hey Rex, Immediately after the upgrade started receiving the "black screen" issue others have reported. :-( Sending this note from lxqt. kde for me right now is unusable.
FWIW, on an older system which was behind on updates I updated everything simultaneously. There was a kernel update and others thrown into the mix. After a reboot I had a "black screen" and a bunch of errors in my Xorg.0.log that I failed to save. :-(
Anyway I disabled the kde-testing and updates-testing repos and did a "dnf distro-sync". This gave me a usable system again.
I then enabled kde-testing and updated and rebooted. Now everything still works.
Not sure why....
-- Fedora Users List - The place to go to get others to do the work for you _______________________________________________ kde mailing list -- kde@lists.fedoraproject.org To unsubscribe send an email to kde-leave@lists.fedoraproject.org
On Sat, Feb 25, 2017 at 7:53 AM, Gerald B. Cox gbcox@bzb.us wrote:
I didn't narrow it down any further because of package dependencies, but if you dnf downgrade the above packages, you'll eliminate the black screen issue. I'll create a bug...
On 02/25/17 23:53, Gerald B. Cox wrote:
By going though the updates, one by one I found the culprits: Packages Altered: Upgraded libkworkspace5-5.8.5-5.fc25.x86_64 @updates Upgrade 5.8.6-2.fc25.x86_64 @updates-testing Upgraded plasma-lookandfeel-fedora-5.8.5-5.fc25.noarch @updates Upgrade 5.8.6-2.fc25.noarch @updates-testing Upgraded plasma-workspace-5.8.5-5.fc25.x86_64 @updates Upgrade 5.8.6-2.fc25.x86_64 @updates-testing Upgraded plasma-workspace-common-5.8.5-5.fc25.x86_64 @updates Upgrade 5.8.6-2.fc25.x86_64 @updates-testing Upgraded plasma-workspace-drkonqi-5.8.5-5.fc25.x86_64 @updates Upgrade 5.8.6-2.fc25.x86_64 @updates-testing Upgraded plasma-workspace-geolocation-5.8.5-5.fc25.x86_64 @updates Upgrade 5.8.6-2.fc25.x86_64 @updates-testing Upgraded plasma-workspace-geolocation-libs-5.8.5-5.fc25.x86_64 @updates Upgrade 5.8.6-2.fc25.x86_64 @updates-testing Upgraded plasma-workspace-libs-5.8.5-5.fc25.x86_64 @updates Upgrade 5.8.6-2.fc25.x86_64 @updates-testing Upgraded sddm-breeze-5.8.5-5.fc25.noarch @updates Upgrade 5.8.6-2.fc25.noarch @updates-testing
I didn't narrow it down any further because of package dependencies, but if you dnf downgrade the above packages, you'll eliminate the black screen issue. I'll create a bug...
FWIW, as I said, I originally had a blank screen. After which I downgraded, rebooted, upgraded, rebooted and now everything is OK. I have
[egreshko@acer ~]$ rpm -q libkworkspace5 libkworkspace5-5.8.6-2.fc25.x86_64 [egreshko@acer ~]$ rpm -q plasma-lookandfeel-fedora plasma-lookandfeel-fedora-5.8.6-2.fc25.noarch [egreshko@acer ~]$ rpm -q plasma-workspace plasma-workspace-5.8.6-2.fc25.x86_64
installed and all is OK.
Same problem here, blank screen, and plasmashell from yakuake says: plasmashell plasmashell: symbol lookup error: plasmashell: undefined symbol: _ZN6Plasma6Corona2 1screenGeometryChangedEi
I can start apps from yakuake, this is from the same session.
Redgards Mustafa
Am 25.02.2017 um 23:12 schrieb Mustafa Muhammad:
Same problem here, blank screen, and plasmashell from yakuake says: plasmashell plasmashell: symbol lookup error: plasmashell: undefined symbol: _ZN6Plasma6Corona2 1screenGeometryChangedEi
I can start apps from yakuake, this is from the same session
please mention F24 or F25
just because i have running this updates on F24 from where they are built and nothing (except translations for KDE4 apps got still worser) is broken on Intel IvyBridge with modesetting driver and no dedicated GPU
On Sun, Feb 26, 2017 at 1:45 AM, Reindl Harald h.reindl@thelounge.net wrote:
Am 25.02.2017 um 23:12 schrieb Mustafa Muhammad:
Same problem here, blank screen, and plasmashell from yakuake says: plasmashell plasmashell: symbol lookup error: plasmashell: undefined symbol: _ZN6Plasma6Corona2 1screenGeometryChangedEi
I can start apps from yakuake, this is from the same session
please mention F24 or F25
This is on F25, two systems, a desktop with Haswell and a laptop with Sandy Bridge, only Intel GPUs, default drivers.
just because i have running this updates on F24 from where they are built and nothing (except translations for KDE4 apps got still worser) is broken on Intel IvyBridge with modesetting driver and no dedicated GPU
kde mailing list -- kde@lists.fedoraproject.org To unsubscribe send an email to kde-leave@lists.fedoraproject.org
My update was only from updates-testing, now after enabling kde-testing, dostro-sync gave me kf5 5.31, once updated, everything works fine, so I confirm we need kf 5.31 before plasma 5.8.6
Regards
On Sun, Feb 26, 2017 at 1:12 AM, Mustafa Muhammad mustafa1024m@gmail.com wrote:
Same problem here, blank screen, and plasmashell from yakuake says: plasmashell plasmashell: symbol lookup error: plasmashell: undefined symbol: _ZN6Plasma6Corona2 1screenGeometryChangedEi
I can start apps from yakuake, this is from the same session.
Redgards Mustafa
On Sat, Feb 25, 2017 at 2:46 PM, Mustafa Muhammad mustafa1024m@gmail.com wrote:
My update was only from updates-testing, now after enabling kde-testing, dostro-sync gave me kf5 5.31, once updated, everything works fine, so I confirm we need kf 5.31 before plasma 5.8.6
Regards
Still not in updates testing... at least we know what they problem is... now if someone could only figure it out and fix it... seems we are always having bodhi issues...
On Friday, February 24, 2017 12:28:04 PM EST Rex Dieter wrote:
FYI, sent of kf5-5.31.0 and plasma-5.8.6 to -testing (both kde-testing and updates-testing) repos yesterday ,
Using kde-testing, all went well on f25 upgrade. Seems fine; no complaints so far.
did that: $ dnf install plasma-workspace-5.8.6 kwin-5.8.6 --enablerepo=updates-testing
still black screen.
Frédéric
tested something larger:
$ dnf update plasma* kf5* --enablerepo=updates-testing
still black screen.
Frédéric
On 02/28/17 15:29, Frédéric Bron wrote:
tested something larger:
$ dnf update plasma* kf5* --enablerepo=updates-testing
still black screen.
I'm pretty sure....your other posts on the "users" list confirm the issue to be selinux related.
Frédéric Bron wrote:
did that: $ dnf install plasma-workspace-5.8.6 kwin-5.8.6 --enablerepo=updates-testing
still black screen.
Do you use 3rd-party (video) drivers? If so, may be selinux-policy issue:
https://bodhi.fedoraproject.org/updates/FEDORA-2017-e06f91350b
-- rex
On 02/28/17 20:50, Rex Dieter wrote:
Frédéric Bron wrote:
did that: $ dnf install plasma-workspace-5.8.6 kwin-5.8.6 --enablerepo=updates-testing
still black screen.
Do you use 3rd-party (video) drivers? If so, may be selinux-policy issue:
https://bodhi.fedoraproject.org/updates/FEDORA-2017-e06f91350b
Yes he is, and yes that was the problem. It has all been sorted out on the "users" list.
Am 28.02.2017 um 14:25 schrieb Ed Greshko:
On 02/28/17 20:50, Rex Dieter wrote:
Frédéric Bron wrote:
did that: $ dnf install plasma-workspace-5.8.6 kwin-5.8.6 --enablerepo=updates-testing
still black screen.
Do you use 3rd-party (video) drivers? If so, may be selinux-policy issue:
https://bodhi.fedoraproject.org/updates/FEDORA-2017-e06f91350b
Yes he is, and yes that was the problem. It has all been sorted out on the "users" list
it would be really great if people always mention when they use 3rd party blobs *unasked* from the very begin and in case of graphi troubles in doubt assume that as reason
On 02/28/17 21:34, Reindl Harald wrote:
it would be really great if people always mention when they use 3rd party blobs *unasked* from the very begin and in case of graphi troubles in doubt assume that as reason
He did actually mention it on the users list.
On Friday, February 24, 2017 12:28:04 PM EST Rex Dieter wrote:
FYI, sent of kf5-5.31.0 and plasma-5.8.6 to -testing (both kde-testing and updates-testing) repos yesterday ,
Well, I did have a small problem on my desktop machine (no problems on my laptop).
My log filled up with these messages every second[*]. I had walked away for several hours and came back to huge memory consumption (korgac was up to 11+ GB and swap was over half filled on a 16 GB machine). I finally noticed that several akonadi agents were duplicated in the akonadiconsole. I removed them and rebooted and all is now well. Actually, I disabled kde-testing first and did a dnf distro-sync first to downgrade, but the problem was still there. That's when I found the duplicate agents, removed them, and updated again.
I have no idea how this happened, but it was immediately after updating using kde-testing and rebooting. I didn't collect any real information -- just removed the duplicated agents.
Shrug.
________________________ [*] Feb 27 16:26:01 vfr akonadi_kalarm_resource[3340]: org.kde.pim.kalarmresource: KCalCore::Event has no alarms: "b485bdb9-1e23-4506-9325-a88939dbc2a9" Feb 27 16:26:01 vfr akonadi_kalarm_resource[3340]: org.kde.pim.kalarmresource: KCalCore::Event has no alarms: "236edc49-9dbd-4f8f-9b82-03e048a678f1" Feb 27 16:26:01 vfr akonadi_kalarm_resource[3340]: org.kde.pim.kalarmresource: KCalCore::Event has no alarms: "2c18e3e9-3004-4a98-88df-37f697288c8f" Feb 27 16:26:01 vfr akonadi_kalarm_resource[3340]: org.kde.pim.kalarmresource: KCalCore::Event has no alarms: "libkcal-668562259.70" Feb 27 16:26:01 vfr akonadi_kalarm_resource[3340]: org.kde.pim.kalarmresource: KCalCore::Event has no alarms: "57bbe403-fa4b-46e5-9304-693deca257ba" Feb 27 16:26:01 vfr akonadi_kalarm_resource[3340]: org.kde.pim.kalarmresource: KCalCore::Event has no alarms: "704067cf-5ea4-46f4-b805-8fd59ae10952"