Notifications in the latest KDE5/Plasma/Ktown packages
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,097
Rep:
Once had that problem when using KDE5 and solved it by removing the check marks in the boxes in the Xfce settings. In Xfce go to, "Settings Manager" > "Session and Startup" > "Application Autostart."
You can also do that from within kde by opening a terminal and running,
xfce4-settings-manager
at the prompt.
Last edited by cwizardone; 06-21-2020 at 10:43 AM.
Once had that problem when using KDE5 and solved it by removing the check marks in the boxes in the Xfce settings. In Xfce go to, "Settings Manager" > "Session and Startup" > "Application Autostart."
You can also do that from within kde by opening a terminal and running,
Once had that problem when using KDE5 and solved it by removing the check marks in the boxes in the Xfce settings. In Xfce go to, "Settings Manager" > "Session and Startup" > "Application Autostart."
You can also do that from within kde by opening a terminal and running,
xfce4-settings-manager
at the prompt.
I tried this in hopes that it would be a simpler solution than using the ~/.local folder "fix". Didn't work out for me though, xfce4-notifyd keeps on running in plasma. I switched it back with the .local folder again and reverted the checkboxes in xfce4-settings-manager. Now baloo isn't autostarting anymore. Before mucking about with xfce4 settings it would autostart with a plasma session, afterwards it doesn't even though plasma settings say it does (I noticed baloo because I have been troubleshooting it lately, its running into problems with mutliple instances and hitting inotify limits).
Guess I have to dig into ~/.config now and find whatever files that xfce4-settings-manager created in there. It'd be nice if these two DE's played together a little nicer. I haven't tried any of the newer XFCE packages yet but I'm hopping they improve this bit in the newer versions.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,097
Rep:
There is a box for baloo in the xfce4 settings. Check or uncheck as needed.
The method I outlined worked for me with kde5, which I've since removed from
the computer and won't be installing again. Ever. Each to their own.
Sorry you had a problem.
While I think about it. Have you looked at the kde startup and shutdown/service manager settings?
Last edited by cwizardone; 06-22-2020 at 10:15 AM.
I did try to use the xfce4 settings checkboxes to reapply autostarting baloo but it didn't work as advertised. Perhaps its because I ran the application from the Plasma 5 environment. I didn't want to start a full XFCE session because I have had it dirty up ~/.config in the past.
Anyways, I used 'find' to locate modified ~/.config files from the last hour and it looks like xfce4-settings-manager copied /etc/xdg/autostart/* to ~/.config/autostart/ and wiped the contents of the files in the process. Archwiki tells me that ~/.config/autostart is prioritized over the /etc/xdg/autostart directory, hence nothing autostarting properly (except for xfce4-notifyd, go figure).
I wiped ~/.config/autostart and baloo is back to working as expected. It looks like plasma uses ~/.config/autostart for starting latte-dock (since it put that back in after restarting the session), and /etc/xdg/autostart for starting baloo. If a user disables autostarting baloo in plasma, it write to ~/.config/baloofilerc. XFCE on the other hand does it by using ~/.config/autostart which has a side effect overriding /etc/xdg/autostart, and contradicting what plasma settings want.
Like you said, "to each their own". I'm not trying to blame one or the other but the problem stands that they tend to share and overwrite each other's config files, as seen in this case.
I've been wrestling with a failing notification process since the upgrade to KDE-5_20.06 w/elogind. I'm running X11, not Wayland, and everything else appears OK so far. The send-notify is invoked from a local server when a new email arrives. It has worked with ktown until the latest update. Here's a sample of the error in /var/log/messages when I try to manually initiate a message:
Code:
Jun 22 08:56:50 my_desktop sshd[31005]: Accepted publickey for my_user from 10.10.10.x port 59044 ssh2: RSA SHA256:20gLDihoYgjH8RUrwrTagR/bFL2AuFkhG8yItuWC06Y
Jun 22 08:56:50 my_desktop dbus-daemon[2674]: [session uid=1001 pid=2672] Activating service name='org.freedesktop.Notifications' requested by ':1.177' (uid=1001 pid=31014 comm="notify-send Email Name <email@example.com> Fwd: A")
Jun 22 08:56:55 my_desktop sshd[31012]: Received disconnect from 10.10.10.x port 59044:11: disconnected by user
Jun 22 08:56:55 my_desktop sshd[31012]: Disconnected from user my_user 10.10.10.x port 59044
Jun 22 08:57:50 my_desktop dbus-daemon[2674]: [session uid=1001 pid=2672] Activated service 'org.freedesktop.Notifications' failed: Process org.freedesktop.Notifications exited with status 1
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,097
Rep:
Quote:
Originally Posted by 0XBF
......I'm not trying to blame one or the other but the problem stands that they tend to share and overwrite each other's config files, as seen in this case.
Oh, I agree, but in the past kde5 did more damage to Xfce than the other way around. The last few versions of kde5 haven't caused as much interference.
OTOH, Kde4, which I'm using at the moment, did not change or overwrite the Xfce settings.
I've been wrestling with a failing notification process since the upgrade to KDE-5_20.06 w/elogind. I'm running X11, not Wayland, and everything else appears OK so far. The send-notify is invoked from a local server when a new email arrives. It has worked with ktown until the latest update.
Well I found a workaround and now notifications are displayed on my Plasma desktop from the local server when a new email arrives. In the past I piped a message over ssh and provided "export DISPLAY=:0" before the "notify-send". Now with the latest Plasma I have to get the current desktop DBUS_SESSION_BUS_ADDRESS then export the full value before the "notify-send". The full value looks like this:
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
