LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 02-23-2020, 03:50 PM   #1
wirelessmc
Member
 
Registered: Aug 2008
Posts: 59

Rep: Reputation: 10
Notifications in the latest KDE5/Plasma/Ktown packages


I upgraded my *64-current installation and then upgraded to the latest KDE5/Plasma packages (February release) and this seemed to have broken Notifications. I am not sure if something went wrong during the upgrade or if this is an issue with the latest Plasma packages. I'm guessing it's not the later.

When I try to configure Notifications in Settings the following dialogue comes up in the 'Notifications - System Settings' window:

"Notifications are currently provided by 'Xfce Xfce Notify Daemon' instead of Plasma."

I use the Notifications mainly to make sure my sound is configured correctly since my sound is a bit complicated with nvidia proprietary drivers.

Anyone else having this issue with the latest Plasma packages?

I figured I would post here before posting on Eric's blog page "Alien Pastures'.
 
Old 02-23-2020, 04:10 PM   #2
gegechris99
Member
 
Registered: Oct 2005
Location: France
Distribution: Slackware current 64bit
Posts: 977
Blog Entries: 5

Rep: Reputation: 191Reputation: 191
I don't have any issue with configuration of Notifications with KDE5 "February Release". Also I don't have any XFCE-related packages in my -current system.

When did you upgrade to latest KDE5/Plasma packages?

This week-end, lots of alienbob's KDE5 packages are being updated that are not yet listed in ktown Changelog. If you upgraded today (Sunday 23rd February) it means that you didn't upgrade to "February Release" but to a newer version that may not yet be ready or was incomplete due to mirroring delays.
 
Old 02-23-2020, 05:15 PM   #3
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 8,063

Rep: Reputation: 6825Reputation: 6825Reputation: 6825Reputation: 6825Reputation: 6825Reputation: 6825Reputation: 6825Reputation: 6825Reputation: 6825Reputation: 6825Reputation: 6825
Quote:
Originally Posted by gegechris99 View Post
I don't have any issue with configuration of Notifications with KDE5 "February Release". Also I don't have any XFCE-related packages in my -current system.

When did you upgrade to latest KDE5/Plasma packages?

This week-end, lots of alienbob's KDE5 packages are being updated that are not yet listed in ktown Changelog. If you upgraded today (Sunday 23rd February) it means that you didn't upgrade to "February Release" but to a newer version that may not yet be ready or was incomplete due to mirroring delays.
All kinds of packages were updated this weekend, and all of it is mentioned in the ChangeLog.txt:
Code:
+--------------------------+
Sun Feb 23 19:00:04 UTC 2020
kde/plasma/plasma-workspace: rebuilt (64bit) because an explodepkg/makepkg
  stripped the last character of some of the .qml files.  This is a tar bug
  in Slackware 14.2, search for 'tar truncated 100 characters'.

+--------------------------+
Sun Feb 23 00:09:20 UTC 2020
kde/frameworks/kwayland: rebuilt against wayland.
kde/frameworks/plasma-framework: rebuilt against wayland.
kde/plasma: updated to 5.18.1
kde/plasma-extra/kdeconnect-framework: rebuilt against wayland.
Note: the 'testing' repository contains PAM support and is meant to be used
  with the PAM packages in Slackware-current's '/testing'!
 
1 members found this post helpful.
Old 02-24-2020, 06:02 AM   #4
gegechris99
Member
 
Registered: Oct 2005
Location: France
Distribution: Slackware current 64bit
Posts: 977
Blog Entries: 5

Rep: Reputation: 191Reputation: 191
Code:
kde/plasma: updated to 5.18.1
My bad. I didn't see that this Changelog entry referred to plasma directory.
 
Old 02-24-2020, 06:41 AM   #5
chrisretusn
Senior Member
 
Registered: Dec 2005
Location: Philippines
Distribution: Slackware64-current
Posts: 1,207

Rep: Reputation: 492Reputation: 492Reputation: 492Reputation: 492Reputation: 492
I see the same issue. I have upgraded my ktown (Sun Feb 23 19:00:04 UTC 2020). I am using the PAMified repository.

Last edited by chrisretusn; 02-25-2020 at 01:51 AM.
 
Old 02-24-2020, 07:52 AM   #6
wirelessmc
Member
 
Registered: Aug 2008
Posts: 59

Original Poster
Rep: Reputation: 10
I had the 5.18.0 packages and just upgraded to the latest 5.18.1 packages which I downloaded (via rsync) yesterday - Feb 23 06:49 PDT.

This unfortunately did not fix the above issue with Notifications. Instead the upgrade threw another wrinkle into the mix with the following error now appearing in my panel system tray:

Error loading QML file: file:///usr/share/plasma/plasmoids/org.kde.plasma.private.systemtray/contents/ui/main.qml:386:19: Type ExpandedRepresentation unavailable
file:///usr/share/plasma/plasmoids/org.kde.plasma.private.systemtray/contents/ui/ExpandedRepresentation.qml:134:9: PlasmoidPopupsContainer is not a type

Something insidious appears to have gone wrong with my installation. I will try removing all of kde/ktown and xfce packages and reinstalling.
 
Old 02-24-2020, 08:36 AM   #7
Timothy Miller
Moderator
 
Registered: Feb 2003
Location: Arizona, USA
Distribution: Debian, Arch, Void
Posts: 3,457

Rep: Reputation: 1132Reputation: 1132Reputation: 1132Reputation: 1132Reputation: 1132Reputation: 1132Reputation: 1132Reputation: 1132Reputation: 1132
Quote:
Originally Posted by wirelessmc View Post
I had the 5.18.0 packages and just upgraded to the latest 5.18.1 packages which I downloaded (via rsync) yesterday - Feb 23 06:49 PDT.

This unfortunately did not fix the above issue with Notifications. Instead the upgrade threw another wrinkle into the mix with the following error now appearing in my panel system tray:

Error loading QML file: file:///usr/share/plasma/plasmoids/org.kde.plasma.private.systemtray/contents/ui/main.qml:386:19: Type ExpandedRepresentation unavailable
file:///usr/share/plasma/plasmoids/org.kde.plasma.private.systemtray/contents/ui/ExpandedRepresentation.qml:134:9: PlasmoidPopupsContainer is not a type

Something insidious appears to have gone wrong with my installation. I will try removing all of kde/ktown and xfce packages and reinstalling.
Don't know if it's the cause of all the issues, but this issue at least is a known issue..see https://www.linuxquestions.org/quest...9/#post6093332
 
Old 02-24-2020, 01:36 PM   #8
davjohn
Member
 
Registered: Jan 2017
Posts: 39

Rep: Reputation: Disabled
I had the same problem. If you have xfce installed, service "org.freedesktop.Notifications" is provided by Plasma and xfce4-notifyd. I don't know if there is a way to set priority, but I solved it by copying plasma service file to local directory:

Code:
mkdir -p ~/.local/share/dbus-1/services/ && cp /usr/share/dbus-1/services/org.kde.plasma.Notifications.service ~/.local/share/dbus-1/services/
 
Old 02-24-2020, 07:54 PM   #9
wirelessmc
Member
 
Registered: Aug 2008
Posts: 59

Original Poster
Rep: Reputation: 10
Update...

After spending entirely too much time on this (upgrading to the latest Plasma5 packages, bricking my system and installing a new kernel) the eventual solution for me was to remove the 'xfce4-notifyd-0.4.4-x86_64-1' package. There must be a way to not start the xfce4-notify daemon from startplasma-x11 but I haven't figured that out yet. I don't think I will spend very much time figuring that out either. I might try davjohn's solution above.

Operating System: Slackware 14.2
KDE Plasma Version: 5.18.1
KDE Frameworks Version: 5.67.0
Qt Version: 5.13.2
Kernel Version: 5.4.21
OS Type: 64-bit
Processors: 8 × Intel® Core™ i7-6700 CPU @ 3.40GHz
 
1 members found this post helpful.
Old 02-25-2020, 04:03 PM   #10
0XBF
Member
 
Registered: Nov 2018
Location: Winnipeg
Distribution: Slackware
Posts: 188

Rep: Reputation: 138Reputation: 138
I had a similar issue with xfce4-notifyd taking over my notifications system while running KDE plasma. It manifested a little differently though: in my case notifications used to work properly, then xfce notifications took over (perhaps after running an xfce session? it was installed from the beginning though). The system settings widget in plasma still showed settings for plasma notifications, but the settings didn't do anything since xfce4-notifyd was running instead.

Doing a "grep Name=org.freedesktop.Notifications /usr/share/dbus-1/services/*" shows both "org.kde.plasma.Notifications.service" and "org.xfce.xfce4-notifyd.Notifications.service" file trying to set freedesktop.Notifications. I'm guessing thats a conflict and that dbus is arbitrarily picking the xfce file to use at startup. This is the same as davjohn described. I fixed it the same way, making the "~/.local/share/dbus-1/services/" directory and then just linking the plasma service file over using:
Code:
ln -s /usr/share/dbus-1/services/org.kde.plasma.Notifications.service .local/share/dbus-1/services/org.kde.plasma.Notifications.service
from my home directory. Dbus should prioritize the local directory first, allowing the proper service to be run. Credit to this redhat forum for some info on the problem. https://bugzilla.redhat.com/show_bug.cgi?id=1471560#c31

Edit: I should add that the fix is user specific. You could rename/remove the file in /usr/share/dbus-1/services you dont want, but that doesn't seem like a good fix to me, since it would affect using xfce4 later if you would switch back. Maybe someone else will chime in with a more elegant solution...

Last edited by 0XBF; 02-25-2020 at 04:08 PM.
 
2 members found this post helpful.
Old 02-26-2020, 09:19 AM   #11
wirelessmc
Member
 
Registered: Aug 2008
Posts: 59

Original Poster
Rep: Reputation: 10
Thanks to both 0XBF and davjohn for your responses. I have reinstalled the 'xfce4-notifyd-0.4.4-x86_64-1' package for now and used your approach for forcing Plasma Notifications. Yes this is indeed a band-aid fix for something that clearly got broken with the latest Plasma release. I say that because I have not seen this issue with previous Plasma releases. The notification service is indeed user specific and should be set by the Desktop you are running. I suspect this ultimately should be corrected by setting the notification service in the Desktop startup scripts. i.e. /usr/bin/startplasma-[x11|wayland] and /usr/bin/startxfce4
 
Old 02-27-2020, 06:56 AM   #12
0XBF
Member
 
Registered: Nov 2018
Location: Winnipeg
Distribution: Slackware
Posts: 188

Rep: Reputation: 138Reputation: 138
I finally updated from the January release to the February release and took the fix off temporarily to check the behavior. Now I get the same issues that wirelessmc described in post #1, where the system settings reports that xfce4-notifyd is in control and greys everything out. Previous builds showed the control panel working, although xfce4-notifyd was still the notification service used. IIRC this started to occur a few releases back, perhaps around last fall.

I'm surprised that there are not other reports of this occurring. As long as a user has plasma and xfce installed this should show up. However, I only noticed it since I had themed plasma differently and told it to pop up in the top left of the screen, while xfce4 notifications come up in the top right for me, with a different theme. It was the fact that notifications weren't appearing where I wanted that caused me to look deeper into this.
 
Old 06-21-2020, 03:12 AM   #13
pchristy
Member
 
Registered: Oct 2012
Location: UK
Distribution: Slackware
Posts: 492

Rep: Reputation: Disabled
Just run into this for the first time, following the latest round of updates! Never noticed it before!

Adding the script described above to .local has provided a fix for the moment (and many thanks for it!), but surely there must be a proper way of doing this?

--
Pete
 
Old 06-21-2020, 05:35 AM   #14
gmgf
Senior Member
 
Registered: Jun 2012
Location: Bergerac, France
Distribution: Slackware
Posts: 1,795

Rep: Reputation: 709Reputation: 709Reputation: 709Reputation: 709Reputation: 709Reputation: 709Reputation: 709
It's, fixed on news, (R.Workman) packages here:

http://slackware.uk/people/rlworkman/current/x86_64/

http://slackware.uk/people/rlworkman.../ChangeLog.txt

BUT WARNING HERE:

https://www.linuxquestions.org/quest...ml#post6136286
 
Old 06-21-2020, 08:53 AM   #15
titopoquito
Senior Member
 
Registered: Jul 2004
Location: Lower Rhine region, Germany
Distribution: Slackware64 14.2 and current, SlackwareARM current
Posts: 1,615

Rep: Reputation: 138Reputation: 138
I had a simliar problem some time ago, but the other way around - in XFCE the plasma notification daemon kicked in which led to unwanted delays (link: https://www.linuxquestions.org/quest...es-4175669162/).
I wonder how the appropriate notification daemon is selected/activated and if there is a proper solution without using the fix in ~/.local.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] The KDE Plasma 5.34.4 was released 10 days ago and it is not in KTown yet. What happened with the "greatest and mightest" thing? ZhaoLin1457 Slackware 63 08-13-2018 10:37 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 06:28 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration