Devuan bug report logs - #373
xfce4-notifyd not started at xfce session login

Reply or subscribe to this bug.

Toggle useless messages

---

Message #5 received at submit@bugs.devuan.org (full text, mbox, reply):

Package: xfce4-notifyd
Version: 0.4.3-1

Incorrect behavior:
in Devuan beowulf xfce4-notifyd 0.4.3-1 is not started at user login into the xfce
desktop as it provides only /usr/lib/systemd/user/xfce4-notifyd.service
but not .desktop file in  /etc/xdg/autostart/ nor in $HOME/.config/autostart.

Expected behavior: xfce4-notifyd should be running in a xfce session to provide
notification messages to the user.

Fix: Adding this .desktop file in $HOME/.config/autostart fixed it for me:

___________________CUT HERE_______________________

[Desktop Entry]
Encoding=UTF-8
Version=0.9.4
Type=Application
Name=xfce4-notifyd
Comment=Xfce4 Notification Daemon
Exec=/usr/lib/x86_64-linux-gnu/xfce4/notifyd/xfce4-notifyd
OnlyShowIn=XFCE;
StartupNotify=false
Terminal=false
Hidden=false

GenericName=Xfce4 Notification Daemon
___________________AND HERE________________________
 

dpkg -L xfce4-notifyd
/usr
/usr/bin
/usr/bin/xfce4-notifyd-config
/usr/lib
/usr/lib/systemd
/usr/lib/systemd/user
/usr/lib/systemd/user/xfce4-notifyd.service
/usr/lib/x86_64-linux-gnu
/usr/lib/x86_64-linux-gnu/xfce4
/usr/lib/x86_64-linux-gnu/xfce4/notifyd
/usr/lib/x86_64-linux-gnu/xfce4/notifyd/xfce4-notifyd
/usr/lib/x86_64-linux-gnu/xfce4/panel
/usr/lib/x86_64-linux-gnu/xfce4/panel/plugins
/usr/lib/x86_64-linux-gnu/xfce4/panel/plugins/libnotification-plugin.so
/usr/share
/usr/share/applications
/usr/share/applications/xfce4-notifyd-config.desktop
/usr/share/dbus-1
/usr/share/dbus-1/services
/usr/share/dbus-1/services/org.xfce.xfce4-notifyd.Notifications.service
/usr/share/doc
/usr/share/doc/xfce4-notifyd
/usr/share/doc/xfce4-notifyd/NEWS.gz
/usr/share/doc/xfce4-notifyd/README
/usr/share/doc/xfce4-notifyd/TODO
/usr/share/doc/xfce4-notifyd/changelog.Debian.gz
/usr/share/doc/xfce4-notifyd/changelog.gz
/usr/share/doc/xfce4-notifyd/copyright
/usr/share/icons
/usr/share/icons/hicolor
/usr/share/icons/hicolor/16x16
/usr/share/icons/hicolor/16x16/apps
/usr/share/icons/hicolor/16x16/apps/xfce4-notifyd.png
/usr/share/icons/hicolor/24x24
/usr/share/icons/hicolor/24x24/apps
/usr/share/icons/hicolor/24x24/apps/xfce4-notifyd.png
/usr/share/icons/hicolor/32x32
/usr/share/icons/hicolor/32x32/apps
/usr/share/icons/hicolor/32x32/apps/xfce4-notifyd.png
/usr/share/icons/hicolor/48x48
/usr/share/icons/hicolor/48x48/apps
/usr/share/icons/hicolor/48x48/apps/xfce4-notifyd.png
/usr/share/icons/hicolor/scalable
/usr/share/icons/hicolor/scalable/apps
/usr/share/icons/hicolor/scalable/apps/xfce4-notifyd.svg
/usr/share/icons/hicolor/scalable/status
/usr/share/icons/hicolor/scalable/status/notification-disabled-new-symbolic.svg
/usr/share/icons/hicolor/scalable/status/notification-disabled-symbolic.svg
/usr/share/icons/hicolor/scalable/status/notification-new-symbolic.svg
/usr/share/icons/hicolor/scalable/status/notification-symbolic.svg
/usr/share/lintian
/usr/share/lintian/overrides
/usr/share/lintian/overrides/xfce4-notifyd
/usr/share/locale
/usr/share/locale/ar
/usr/share/locale/ar/LC_MESSAGES
/usr/share/locale/ar/LC_MESSAGES/xfce4-notifyd.mo
/usr/share/locale/ast
/usr/share/locale/ast/LC_MESSAGES
/usr/share/locale/ast/LC_MESSAGES/xfce4-notifyd.mo
/usr/share/locale/be
/usr/share/locale/be/LC_MESSAGES
/usr/share/locale/be/LC_MESSAGES/xfce4-notifyd.mo
/usr/share/locale/bg
/usr/share/locale/bg/LC_MESSAGES
/usr/share/locale/bg/LC_MESSAGES/xfce4-notifyd.mo
/usr/share/locale/ca
/usr/share/locale/ca/LC_MESSAGES
/usr/share/locale/ca/LC_MESSAGES/xfce4-notifyd.mo
/usr/share/locale/cs
/usr/share/locale/cs/LC_MESSAGES
/usr/share/locale/cs/LC_MESSAGES/xfce4-notifyd.mo
/usr/share/locale/da
/usr/share/locale/da/LC_MESSAGES
/usr/share/locale/da/LC_MESSAGES/xfce4-notifyd.mo
/usr/share/locale/de
/usr/share/locale/de/LC_MESSAGES
/usr/share/locale/de/LC_MESSAGES/xfce4-notifyd.mo
/usr/share/locale/el
/usr/share/locale/el/LC_MESSAGES
/usr/share/locale/el/LC_MESSAGES/xfce4-notifyd.mo
/usr/share/locale/en_AU
/usr/share/locale/en_AU/LC_MESSAGES
/usr/share/locale/en_AU/LC_MESSAGES/xfce4-notifyd.mo
/usr/share/locale/en_GB
/usr/share/locale/en_GB/LC_MESSAGES
/usr/share/locale/en_GB/LC_MESSAGES/xfce4-notifyd.mo
/usr/share/locale/es
/usr/share/locale/es/LC_MESSAGES
/usr/share/locale/es/LC_MESSAGES/xfce4-notifyd.mo
/usr/share/locale/eu
/usr/share/locale/eu/LC_MESSAGES
/usr/share/locale/eu/LC_MESSAGES/xfce4-notifyd.mo
/usr/share/locale/fi
/usr/share/locale/fi/LC_MESSAGES
/usr/share/locale/fi/LC_MESSAGES/xfce4-notifyd.mo
/usr/share/locale/fr
/usr/share/locale/fr/LC_MESSAGES
/usr/share/locale/fr/LC_MESSAGES/xfce4-notifyd.mo
/usr/share/locale/gl
/usr/share/locale/gl/LC_MESSAGES
/usr/share/locale/gl/LC_MESSAGES/xfce4-notifyd.mo
/usr/share/locale/he
/usr/share/locale/he/LC_MESSAGES
/usr/share/locale/he/LC_MESSAGES/xfce4-notifyd.mo
/usr/share/locale/hr
/usr/share/locale/hr/LC_MESSAGES
/usr/share/locale/hr/LC_MESSAGES/xfce4-notifyd.mo
/usr/share/locale/hu
/usr/share/locale/hu/LC_MESSAGES
/usr/share/locale/hu/LC_MESSAGES/xfce4-notifyd.mo
/usr/share/locale/id
/usr/share/locale/id/LC_MESSAGES
/usr/share/locale/id/LC_MESSAGES/xfce4-notifyd.mo
/usr/share/locale/is
/usr/share/locale/is/LC_MESSAGES
/usr/share/locale/is/LC_MESSAGES/xfce4-notifyd.mo
/usr/share/locale/it
/usr/share/locale/it/LC_MESSAGES
/usr/share/locale/it/LC_MESSAGES/xfce4-notifyd.mo
/usr/share/locale/ja
/usr/share/locale/ja/LC_MESSAGES
/usr/share/locale/ja/LC_MESSAGES/xfce4-notifyd.mo
/usr/share/locale/kk
/usr/share/locale/kk/LC_MESSAGES
/usr/share/locale/kk/LC_MESSAGES/xfce4-notifyd.mo
/usr/share/locale/ko
/usr/share/locale/ko/LC_MESSAGES
/usr/share/locale/ko/LC_MESSAGES/xfce4-notifyd.mo
/usr/share/locale/lt
/usr/share/locale/lt/LC_MESSAGES
/usr/share/locale/lt/LC_MESSAGES/xfce4-notifyd.mo
/usr/share/locale/lv
/usr/share/locale/lv/LC_MESSAGES
/usr/share/locale/lv/LC_MESSAGES/xfce4-notifyd.mo
/usr/share/locale/ms
/usr/share/locale/ms/LC_MESSAGES
/usr/share/locale/ms/LC_MESSAGES/xfce4-notifyd.mo
/usr/share/locale/nb
/usr/share/locale/nb/LC_MESSAGES
/usr/share/locale/nb/LC_MESSAGES/xfce4-notifyd.mo
/usr/share/locale/nl
/usr/share/locale/nl/LC_MESSAGES
/usr/share/locale/nl/LC_MESSAGES/xfce4-notifyd.mo
/usr/share/locale/oc
/usr/share/locale/oc/LC_MESSAGES
/usr/share/locale/oc/LC_MESSAGES/xfce4-notifyd.mo
/usr/share/locale/pa
/usr/share/locale/pa/LC_MESSAGES
/usr/share/locale/pa/LC_MESSAGES/xfce4-notifyd.mo
/usr/share/locale/pl
/usr/share/locale/pl/LC_MESSAGES
/usr/share/locale/pl/LC_MESSAGES/xfce4-notifyd.mo
/usr/share/locale/pt
/usr/share/locale/pt/LC_MESSAGES
/usr/share/locale/pt/LC_MESSAGES/xfce4-notifyd.mo
/usr/share/locale/pt_BR
/usr/share/locale/pt_BR/LC_MESSAGES
/usr/share/locale/pt_BR/LC_MESSAGES/xfce4-notifyd.mo
/usr/share/locale/ro
/usr/share/locale/ro/LC_MESSAGES
/usr/share/locale/ro/LC_MESSAGES/xfce4-notifyd.mo
/usr/share/locale/ru
/usr/share/locale/ru/LC_MESSAGES
/usr/share/locale/ru/LC_MESSAGES/xfce4-notifyd.mo
/usr/share/locale/si
/usr/share/locale/si/LC_MESSAGES
/usr/share/locale/si/LC_MESSAGES/xfce4-notifyd.mo
/usr/share/locale/sk
/usr/share/locale/sk/LC_MESSAGES
/usr/share/locale/sk/LC_MESSAGES/xfce4-notifyd.mo
/usr/share/locale/sl
/usr/share/locale/sl/LC_MESSAGES
/usr/share/locale/sl/LC_MESSAGES/xfce4-notifyd.mo
/usr/share/locale/sq
/usr/share/locale/sq/LC_MESSAGES
/usr/share/locale/sq/LC_MESSAGES/xfce4-notifyd.mo
/usr/share/locale/sr
/usr/share/locale/sr/LC_MESSAGES
/usr/share/locale/sr/LC_MESSAGES/xfce4-notifyd.mo
/usr/share/locale/sv
/usr/share/locale/sv/LC_MESSAGES
/usr/share/locale/sv/LC_MESSAGES/xfce4-notifyd.mo
/usr/share/locale/th
/usr/share/locale/th/LC_MESSAGES
/usr/share/locale/th/LC_MESSAGES/xfce4-notifyd.mo
/usr/share/locale/tr
/usr/share/locale/tr/LC_MESSAGES
/usr/share/locale/tr/LC_MESSAGES/xfce4-notifyd.mo
/usr/share/locale/ug
/usr/share/locale/ug/LC_MESSAGES
/usr/share/locale/ug/LC_MESSAGES/xfce4-notifyd.mo
/usr/share/locale/uk
/usr/share/locale/uk/LC_MESSAGES
/usr/share/locale/uk/LC_MESSAGES/xfce4-notifyd.mo
/usr/share/locale/vi
/usr/share/locale/vi/LC_MESSAGES
/usr/share/locale/vi/LC_MESSAGES/xfce4-notifyd.mo
/usr/share/locale/zh_CN
/usr/share/locale/zh_CN/LC_MESSAGES
/usr/share/locale/zh_CN/LC_MESSAGES/xfce4-notifyd.mo
/usr/share/locale/zh_TW
/usr/share/locale/zh_TW/LC_MESSAGES
/usr/share/locale/zh_TW/LC_MESSAGES/xfce4-notifyd.mo
/usr/share/man
/usr/share/man/man1
/usr/share/man/man1/xfce4-notifyd-config.1.gz
/usr/share/themes
/usr/share/themes/Bright
/usr/share/themes/Bright/xfce-notify-4.0
/usr/share/themes/Bright/xfce-notify-4.0/gtk.css
/usr/share/themes/Default
/usr/share/themes/Default/xfce-notify-4.0
/usr/share/themes/Default/xfce-notify-4.0/gtk.css
/usr/share/themes/Retro
/usr/share/themes/Retro/xfce-notify-4.0
/usr/share/themes/Retro/xfce-notify-4.0/gtk.css
/usr/share/themes/Smoke
/usr/share/themes/Smoke/xfce-notify-4.0
/usr/share/themes/Smoke/xfce-notify-4.0/gtk.css
/usr/share/themes/ZOMG-PONIES!
/usr/share/themes/ZOMG-PONIES!/xfce-notify-4.0
/usr/share/themes/ZOMG-PONIES!/xfce-notify-4.0/gtk.css
/usr/share/xfce4
/usr/share/xfce4/panel
/usr/share/xfce4/panel/plugins
/usr/share/xfce4/panel/plugins/notification-plugin.desktop

---

Message #8 received at 373@bugs.devuan.org (full text, mbox, reply):

Control: tags -1 moreinfo

Tito,

Thanks. 

Unfortunately I can't reproduce this. In my beowulf VM xfce4-notifyd is started
automatically by DBus activation.

Do you have any message relating to it in .xsession-errors or .xfce4-session.verbose-log?

Thanks

Mark

---

Message #15 received at 373@bugs.devuan.org (full text, mbox, reply):

[Message part 1 (text/plain, inline)]

On Wed, 22 Jan 2020 18:14:06 +0000 Mark Hindley <mark@hindley.org.uk> wrote:
> Control: tags -1 moreinfo
> 
> Tito,
> 
> Thanks. 
> 
> Unfortunately I can't reproduce this. In my beowulf VM xfce4-notifyd is started
> automatically by DBus activation.
> 
> Do you have any message relating to it in .xsession-errors or .xfce4-session.verbose-log?
> 
> Thanks
> 
> Mark

Hi,
sorry for the late response. Attached you will find the
.xsession-errors and .xfce4-session.verbose-log for a newly
setup test user and also my dpkg --get-selections list.
For the new user xfce4-notifyd is not started automatically.
At a first glance I see nothing suspicious.

Ciao,
Tito

[xsession-errors (text/plain, attachment)]

[dpkg_selections.txt (text/plain, attachment)]

[xfce4-session.verbose.log (text/x-log, attachment)]

---

Message #18 received at 373@bugs.devuan.org (full text, mbox, reply):

Tito,

Thanks. The only thing that catches my eye is you have kdeconnect installed.
I am not familiar with it, but does it listen on the 
org.freedesktop.Notifications dbus interface?

What does this command produce?

 busctl --user status org.freedesktop.Notifications

Mark

---

Message #23 received at 373@bugs.devuan.org (full text, mbox, reply):

[Message part 1 (text/plain, inline)]

On Tue, 28 Jan 2020 11:16:09 +0000 Mark Hindley <mark@hindley.org.uk> wrote:
> Tito,
> 
> Thanks. The only thing that catches my eye is you have kdeconnect installed.
> I am not familiar with it, but does it listen on the 
> org.freedesktop.Notifications dbus interface?
> 
> What does this command produce?
> 
>  busctl --user status org.freedesktop.Notifications
> 
> Mark

Hi,

At xfce4 start without starting xfce4-notifyd manually:

busctl --user status org.freedesktop.Notifications
Failed to get credentials: No such device or address


When xfce4-notifyd is started manually:

busctl --user status org.freedesktop.Notifications
PID=15600
PPID=15597
TTY=pts/0
UID=1002
EUID=1002
SUID=1002
FSUID=1002
GID=1002
EGID=1002
SGID=1002
FSGID=1002
SupplementaryGIDs=1002
Comm=xfce4-notifyd
Exe=/usr/lib/x86_64-linux-gnu/xfce4/notifyd/xfce4-notifyd
CommandLine=/usr/lib/x86_64-linux-gnu/xfce4/notifyd/xfce4-notifyd
Label=kernel
CGroup=/8
Session=8
AuditLoginUID=1002
AuditSessionID=8
UniqueName=:1.62
EffectiveCapabilities=
PermittedCapabilities=
InheritableCapabilities=
BoundingCapabilities=cap_chown cap_dac_override cap_dac_read_search
        cap_fowner cap_fsetid cap_kill cap_setgid
        cap_setuid cap_setpcap cap_linux_immutable cap_net_bind_service
        cap_net_broadcast cap_net_admin cap_net_raw cap_ipc_lock
        cap_ipc_owner cap_sys_module cap_sys_rawio cap_sys_chroot
        cap_sys_ptrace cap_sys_pacct cap_sys_admin cap_sys_boot
        cap_sys_nice cap_sys_resource cap_sys_time cap_sys_tty_config
        cap_mknod cap_lease cap_audit_write cap_audit_control
        cap_setfcap cap_mac_override cap_mac_admin cap_syslog
        cap_wake_alarm cap_block_suspend cap_audit_read

Attached you will find also a strace of the xfce4-notifyd manually
started until completion of the busctl command.

Hope this helps.
Tito

[strace.txt (text/plain, attachment)]

---

Message #26 received at 373@bugs.devuan.org (full text, mbox, reply):

On Tue, Jan 28, 2020 at 03:40:42PM +0100, Tito wrote:
> On Tue, 28 Jan 2020 11:16:09 +0000 Mark Hindley <mark@hindley.org.uk> wrote:
> >Tito,
> >
> >Thanks. The only thing that catches my eye is you have kdeconnect installed.
> >I am not familiar with it, but does it listen on the
> >org.freedesktop.Notifications dbus interface?
> >
> >What does this command produce?
> >
> > busctl --user status org.freedesktop.Notifications
> >
> >Mark
> 
> Hi,
> 
> At xfce4 start without starting xfce4-notifyd manually:
> 
> busctl --user status org.freedesktop.Notifications
> Failed to get credentials: No such device or address
> 
> 
> When xfce4-notifyd is started manually:

Hmmm. that is all as I would expect.

Without xfce4-notifyd running,

 busctl --user | grep Notifications

should list org.freedesktop.Notifications as (activatable). Does it?

If so, I am unsure why xfce4 is not activating it on startup. Do you have
something in Settings -> Notifications preventing it?

The other thing I wonder is if it is not running at startup because no
notifications have been sent? I think the DBus service will only be activated as
required. So without xfce4-notifyd running, if I send a notification
(notify-send 'Test message'), xfce4-notifyd is activated and the notification
appears.

Does it behave like that for you?

Mark

---

Message #31 received at 373@bugs.devuan.org (full text, mbox, reply):

On 1/29/20 12:15 PM, Mark Hindley wrote:
> On Tue, Jan 28, 2020 at 03:40:42PM +0100, Tito wrote:
>> On Tue, 28 Jan 2020 11:16:09 +0000 Mark Hindley <mark@hindley.org.uk> wrote:
>>> Tito,
>>>
>>> Thanks. The only thing that catches my eye is you have kdeconnect installed.
>>> I am not familiar with it, but does it listen on the
>>> org.freedesktop.Notifications dbus interface?
>>>
>>> What does this command produce?
>>>
>>> busctl --user status org.freedesktop.Notifications
>>>
>>> Mark
>>
>> Hi,
>>
>> At xfce4 start without starting xfce4-notifyd manually:
>>
>> busctl --user status org.freedesktop.Notifications
>> Failed to get credentials: No such device or address
>>
>>
>> When xfce4-notifyd is started manually:
> 
> Hmmm. that is all as I would expect.
> 
> Without xfce4-notifyd running,
> 
>   busctl --user | grep Notifications
> 
> should list org.freedesktop.Notifications as (activatable). Does it?
Hi,
Yes:

busctl --user | grep Notifications
org.freedesktop.Notifications  - -    -   (activatable) -

> If so, I am unsure why xfce4 is not activating it on startup. Do you have
> something in Settings -> Notifications preventing it?

The test was done with a new user and xfce's default configs.

> The other thing I wonder is if it is not running at startup because no
> notifications have been sent? I think the DBus service will only be activated as
> required. So without xfce4-notifyd running, if I send a notification
> (notify-send 'Test message'), xfce4-notifyd is activated and the notification
> appears.
> 
> Does it behave like that for you?

No, notify-send sits there for 50 seconds and then exits but no notification pops up:

time notify-send "test message"

real    0m50.059s
user    0m0.005s
sys     0m0.003s


OTOH if I start a KDE session for the same test user notifications work,
so XFCE and KDE are doing things differently.

Tito

> 
> Mark
> 

---

Message #34 received at 373@bugs.devuan.org (full text, mbox, reply):

On Wed, Jan 29, 2020 at 02:31:42PM +0100, Tito wrote:
> >Does it behave like that for you?
> 
> No, notify-send sits there for 50 seconds and then exits but no notification
> pops up:

And if you have started xfce4-notifyd manually does the notify-send message
appear normally?

To be honest, I am still unlcear why your setup is not working (yet).

Let's explore some other avenues.

What display manager are you using or are you starting from the terminal with
startx? I notice you have both slim and sddm installed.

Mark

---

Message #37 received at 373@bugs.devuan.org (full text, mbox, reply):

On Fri, Jan 31, 2020 at 10:19:26AM +0000, Mark Hindley wrote:
> To be honest, I am still unlcear why your setup is not working (yet).
> 
> Let's explore some other avenues.
> 
> What display manager are you using or are you starting from the terminal with
> startx? I notice you have both slim and sddm installed.

A few other things to explore.

Do you think this is the same as Debian #899377
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899377)

Are there any message in /var/log/daemon.log  relating to failed DBus activation
start of xfce4-notifyd?

I also notice that you have plasma-workspace installed as does the reporter in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899377#32. He also provides a
workaround.

Mark

---

Message #42 received at 373@bugs.devuan.org (full text, mbox, reply):

On 1/31/20 11:34 AM, Mark Hindley wrote:
> On Fri, Jan 31, 2020 at 10:19:26AM +0000, Mark Hindley wrote:
>> To be honest, I am still unlcear why your setup is not working (yet).
>>
>> Let's explore some other avenues.
>>
>> What display manager are you using or are you starting from the terminal with
>> startx? I notice you have both slim and sddm installed.

I've tried them all: lightdm, sddm and slim but it did not make
any difference for this bug.

> A few other things to explore.
> 
> Do you think this is the same as Debian #899377
> (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899377)

Hi,
yes this looks the same due to plasma-desktop being installed
and if I recall correctly notifications were working before
installing it.
 
> Are there any message in /var/log/daemon.log  relating to failed DBus activation
> start of xfce4-notifyd?

Yes at the end: Jan 31 14:21:18 devuan dbus-daemon[4160]: [session uid=1002 pid=4158] Activated service 'org.freedesktop.Notifications' failed: Process org.freedesktop.Notifications exited with status 1
but with no hints about the reason of failure.

Jan 31 14:20:08 devuan sddm: CODE_FILE=unknown:CODE_LINE=0:unknown:Adding new display on vt 7 ...
Jan 31 14:20:08 devuan sddm: CODE_FILE=unknown:CODE_LINE=0:unknown:Loading theme configuration from ""
Jan 31 14:20:08 devuan sddm: CODE_FILE=unknown:CODE_LINE=0:unknown:Display server starting...
Jan 31 14:20:08 devuan sddm: CODE_FILE=unknown:CODE_LINE=0:unknown:Running: /usr/bin/X -nolisten tcp -auth /var/run/sddm/{5d5b9ab0-2ee8-4586-87e4-c890ed2bcb0e} -background none -noreset -displayfd 18 -seat seat0 vt7
Jan 31 14:20:09 devuan sddm: CODE_FILE=unknown:CODE_LINE=0:unknown:Setting default cursor
Jan 31 14:20:09 devuan sddm: CODE_FILE=unknown:CODE_LINE=0:unknown:Running display setup script  "/usr/share/sddm/scripts/Xsetup"
Jan 31 14:20:09 devuan sddm: CODE_FILE=unknown:CODE_LINE=0:unknown:Display server started.
Jan 31 14:20:09 devuan sddm: CODE_FILE=unknown:CODE_LINE=0:unknown:Socket server starting...
Jan 31 14:20:09 devuan sddm: CODE_FILE=unknown:CODE_LINE=0:unknown:Socket server started.
Jan 31 14:20:09 devuan sddm: CODE_FILE=unknown:CODE_LINE=0:unknown:Loading theme configuration from "/usr/share/sddm/themes/maldives/theme.conf"
Jan 31 14:20:09 devuan sddm: CODE_FILE=unknown:CODE_LINE=0:unknown:Greeter starting...
Jan 31 14:20:09 devuan sddm: CODE_FILE=unknown:CODE_LINE=0:unknown:Adding cookie to "/var/run/sddm/{5d5b9ab0-2ee8-4586-87e4-c890ed2bcb0e}"
Jan 31 14:20:09 devuan sddm-helper: CODE_FILE=unknown:CODE_LINE=0:unknown:[PAM] Starting...
Jan 31 14:20:09 devuan sddm-helper: CODE_FILE=unknown:CODE_LINE=0:unknown:[PAM] Authenticating...
Jan 31 14:20:09 devuan sddm-helper: CODE_FILE=unknown:CODE_LINE=0:unknown:[PAM] returning.
Jan 31 14:20:09 devuan sddm: CODE_FILE=unknown:CODE_LINE=0:unknown:Greeter session started successfully
Jan 31 14:20:09 devuan sddm-greeter: CODE_FILE=unknown:CODE_LINE=0:unknown:High-DPI autoscaling not Enabled
Jan 31 14:20:09 devuan sddm-greeter: CODE_FILE=unknown:CODE_LINE=0:unknown:Reading from "/usr/share/xsessions/plasma.desktop"
Jan 31 14:20:09 devuan sddm-greeter: CODE_FILE=unknown:CODE_LINE=0:unknown:Reading from "/usr/share/xsessions/xfce.desktop"
Jan 31 14:20:09 devuan sddm-greeter: CODE_FILE=unknown:CODE_LINE=0:unknown:Loading theme configuration from "/usr/share/sddm/themes/maldives/theme.conf"
Jan 31 14:20:09 devuan sddm-greeter: CODE_FILE=unknown:CODE_LINE=0:unknown:Connected to the daemon.
Jan 31 14:20:09 devuan sddm: CODE_FILE=unknown:CODE_LINE=0:unknown:Message received from greeter: Connect
Jan 31 14:20:09 devuan sddm-greeter: CODE_FILE=unknown:CODE_LINE=0:unknown:Loading file:///usr/share/sddm/themes/maldives/Main.qml...
Jan 31 14:20:10 devuan sddm-greeter: CODE_FILE=unknown:CODE_LINE=0:unknown:Adding view for "DVI-I-1" QRect(0,0 1920x1080)
Jan 31 14:20:10 devuan sddm-greeter: CODE_FILE=unknown:CODE_LINE=0:unknown:Message received from daemon: Capabilities
Jan 31 14:20:10 devuan sddm-greeter: CODE_FILE=unknown:CODE_LINE=0:unknown:Message received from daemon: HostName
Jan 31 14:20:17 devuan sddm-greeter: CODE_FILE=unknown:CODE_LINE=0:unknown:Reading from "/usr/share/xsessions/xfce.desktop"
Jan 31 14:20:17 devuan sddm: CODE_FILE=unknown:CODE_LINE=0:unknown:Message received from greeter: Login
Jan 31 14:20:17 devuan sddm: CODE_FILE=unknown:CODE_LINE=0:unknown:Reading from "/usr/share/xsessions/xfce.desktop"
Jan 31 14:20:17 devuan sddm: CODE_FILE=unknown:CODE_LINE=0:unknown:Reading from "/usr/share/xsessions/xfce.desktop"
Jan 31 14:20:17 devuan sddm: CODE_FILE=unknown:CODE_LINE=0:unknown:Session "/usr/share/xsessions/xfce.desktop" selected, command: "startxfce4"
Jan 31 14:20:17 devuan sddm-helper: CODE_FILE=unknown:CODE_LINE=0:unknown:[PAM] Starting...
Jan 31 14:20:17 devuan sddm-helper: CODE_FILE=unknown:CODE_LINE=0:unknown:[PAM] Authenticating...
Jan 31 14:20:17 devuan sddm-helper: CODE_FILE=unknown:CODE_LINE=0:unknown:[PAM] Preparing to converse...
Jan 31 14:20:17 devuan sddm-helper: CODE_FILE=unknown:CODE_LINE=0:unknown:[PAM] Conversation with 1 messages
Jan 31 14:20:17 devuan sddm-helper: CODE_FILE=unknown:CODE_LINE=0:unknown:[PAM] returning.
Jan 31 14:20:17 devuan sddm: CODE_FILE=unknown:CODE_LINE=0:unknown:Authenticated successfully
Jan 31 14:20:17 devuan sddm-greeter: CODE_FILE=unknown:CODE_LINE=0:unknown:Message received from daemon: LoginSucceeded
Jan 31 14:20:17 devuan sddm-helper: CODE_FILE=unknown:CODE_LINE=0:unknown:Starting: "/etc/sddm/Xsession \"startxfce4\""
Jan 31 14:20:17 devuan sddm-helper: CODE_FILE=unknown:CODE_LINE=0:unknown:Adding cookie to "/home/test/.Xauthority"
Jan 31 14:20:17 devuan sddm: CODE_FILE=unknown:CODE_LINE=0:unknown:Session started
Jan 31 14:20:17 devuan sddm-helper: CODE_FILE=unknown:CODE_LINE=0:unknown:[PAM] Closing session
Jan 31 14:20:17 devuan sddm-helper: CODE_FILE=unknown:CODE_LINE=0:unknown:[PAM] Ended.
Jan 31 14:20:17 devuan sddm: CODE_FILE=unknown:CODE_LINE=0:unknown:Auth: sddm-helper exited successfully
Jan 31 14:20:17 devuan sddm: CODE_FILE=unknown:CODE_LINE=0:unknown:Greeter stopped.
Jan 31 14:20:17 devuan dbus-daemon[4160]: [session uid=1002 pid=4158] Activating service name='org.a11y.Bus' requested by ':1.3' (uid=1002 pid=4180 comm="xfce4-session " label="kernel")
Jan 31 14:20:17 devuan dbus-daemon[4160]: [session uid=1002 pid=4158] Successfully activated service 'org.a11y.Bus'
Jan 31 14:20:17 devuan dbus-daemon[4160]: [session uid=1002 pid=4158] Activating service name='org.xfce.Xfconf' requested by ':1.3' (uid=1002 pid=4180 comm="xfce4-session " label="kernel")
Jan 31 14:20:17 devuan dbus-daemon[4160]: [session uid=1002 pid=4158] Successfully activated service 'org.xfce.Xfconf'
Jan 31 14:20:18 devuan dbus-daemon[4160]: [session uid=1002 pid=4158] Activating service name='org.gtk.vfs.Daemon' requested by ':1.9' (uid=1002 pid=4201 comm="Thunar --sm-client-id 20589a729-5b9b-4525-81f1-bb8" label="kernel")
Jan 31 14:20:18 devuan dbus-daemon[4160]: [session uid=1002 pid=4158] Successfully activated service 'org.gtk.vfs.Daemon'
Jan 31 14:20:18 devuan dbus-daemon[4160]: [session uid=1002 pid=4158] Activating service name='org.freedesktop.thumbnails.Thumbnailer1' requested by ':1.16' (uid=1002 pid=4225 comm="xfdesktop --display :0.0 --sm-client-id 25a4b624b-" label="kernel")
Jan 31 14:20:18 devuan dbus-daemon[4160]: [session uid=1002 pid=4158] Activating service name='org.freedesktop.Notifications' requested by ':1.19' (uid=1002 pid=4233 comm="xfce4-power-manager --restart --sm-client-id 2aa7c" label="kernel")
Jan 31 14:20:18 devuan dbus-daemon[2447]: [system] Activating service name='org.freedesktop.PackageKit' requested by ':1.60' (uid=1002 pid=4254 comm="package-update-indicator " label="kernel") (using servicehelper)
Jan 31 14:20:18 devuan PackageKit: daemon start
Jan 31 14:20:18 devuan rtkit-daemon[3454]: Successfully made thread 4292 of process 4292 (n/a) owned by '1002' high priority at nice level -11.
Jan 31 14:20:18 devuan rtkit-daemon[3454]: Supervising 4 threads of 2 processes of 2 users.
Jan 31 14:20:19 devuan dbus-daemon[2447]: [system] Successfully activated service 'org.freedesktop.PackageKit'
Jan 31 14:20:19 devuan dbus-daemon[4160]: [session uid=1002 pid=4158] Activating service name='org.gtk.vfs.UDisks2VolumeMonitor' requested by ':1.18' (uid=1002 pid=4235 comm="/usr/lib/x86_64-linux-gnu/tumbler-1/tumblerd " label="kernel")
Jan 31 14:20:19 devuan dbus-daemon[4160]: [session uid=1002 pid=4158] Successfully activated service 'org.gtk.vfs.UDisks2VolumeMonitor'
Jan 31 14:20:19 devuan dbus-daemon[4160]: [session uid=1002 pid=4158] Activating service name='org.gtk.vfs.GPhoto2VolumeMonitor' requested by ':1.18' (uid=1002 pid=4235 comm="/usr/lib/x86_64-linux-gnu/tumbler-1/tumblerd " label="kernel")
Jan 31 14:20:19 devuan dbus-daemon[4160]: [session uid=1002 pid=4158] Successfully activated service 'org.gtk.vfs.GPhoto2VolumeMonitor'
Jan 31 14:20:19 devuan dbus-daemon[4160]: [session uid=1002 pid=4158] Activating service name='org.gtk.vfs.AfcVolumeMonitor' requested by ':1.18' (uid=1002 pid=4235 comm="/usr/lib/x86_64-linux-gnu/tumbler-1/tumblerd " label="kernel")
Jan 31 14:20:19 devuan dbus-daemon[4160]: [session uid=1002 pid=4158] Successfully activated service 'org.gtk.vfs.AfcVolumeMonitor'
Jan 31 14:20:19 devuan dbus-daemon[4160]: [session uid=1002 pid=4158] Activating service name='org.gtk.vfs.GoaVolumeMonitor' requested by ':1.18' (uid=1002 pid=4235 comm="/usr/lib/x86_64-linux-gnu/tumbler-1/tumblerd " label="kernel")
Jan 31 14:20:19 devuan dbus-daemon[4160]: [session uid=1002 pid=4158] Successfully activated service 'org.gtk.vfs.GoaVolumeMonitor'
Jan 31 14:20:19 devuan dbus-daemon[4160]: [session uid=1002 pid=4158] Activating service name='org.gtk.vfs.MTPVolumeMonitor' requested by ':1.18' (uid=1002 pid=4235 comm="/usr/lib/x86_64-linux-gnu/tumbler-1/tumblerd " label="kernel")
Jan 31 14:20:19 devuan dbus-daemon[4160]: [session uid=1002 pid=4158] Successfully activated service 'org.gtk.vfs.MTPVolumeMonitor'
Jan 31 14:20:19 devuan dbus-daemon[4160]: [session uid=1002 pid=4158] Successfully activated service 'org.freedesktop.thumbnails.Thumbnailer1'
Jan 31 14:20:19 devuan dbus-daemon[4160]: [session uid=1002 pid=4158] Activating service name='org.gtk.vfs.Metadata' requested by ':1.15' (uid=1002 pid=4225 comm="xfdesktop --display :0.0 --sm-client-id 25a4b624b-" label="kernel")
Jan 31 14:20:19 devuan dbus-daemon[4160]: [session uid=1002 pid=4158] Successfully activated service 'org.gtk.vfs.Metadata'
Jan 31 14:20:19 devuan NetworkManager: src/settings/nm-agent-manager.c:352:n/a:<info>  [1580476819.5317] agent-manager: req[0x5647a66ad180, :1.68/org.freedesktop.nm-applet/1002]: agent registered
Jan 31 14:20:19 devuan rtkit-daemon[3454]: Supervising 4 threads of 2 processes of 2 users.
Jan 31 14:20:19 devuan rtkit-daemon[3454]: Successfully made thread 4347 of process 4292 (n/a) owned by '1002' RT at priority 5.
Jan 31 14:20:19 devuan rtkit-daemon[3454]: Supervising 5 threads of 2 processes of 2 users.
Jan 31 14:20:19 devuan rtkit-daemon[3454]: Supervising 5 threads of 2 processes of 2 users.
Jan 31 14:20:19 devuan rtkit-daemon[3454]: Successfully made thread 4348 of process 4292 (n/a) owned by '1002' RT at priority 5.
Jan 31 14:20:19 devuan rtkit-daemon[3454]: Supervising 6 threads of 2 processes of 2 users.
Jan 31 14:20:28 devuan bluetoothd[2498]: Endpoint unregistered: sender=:1.42 path=/MediaEndpoint/A2DPSource
Jan 31 14:20:28 devuan bluetoothd[2498]: Endpoint unregistered: sender=:1.42 path=/MediaEndpoint/A2DPSink
Jan 31 14:21:18 devuan dbus-daemon[4160]: [session uid=1002 pid=4158] Activated service 'org.freedesktop.Notifications' failed: Process org.freedesktop.Notifications exited with status 1
Jan 31 14:24:20 devuan dbus-daemon[4160]: [session uid=1002 pid=4158] Activating service name='org.freedesktop.Notifications' requested by ':1.34' (uid=1002 pid=4273 comm="nm-applet " label="kernel")


> I also notice that you have plasma-workspace installed as does the reporter in
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899377#32. He also provides a
> workaround.

I did try other notification services: dunst and growl that did work,  but they do not integrate well
with xfce's notification settings.

Removing /usr/share/dbus-1/services/org.kde.plasma.Notifications.service don't seem a viable option to me.

I cannot believe that this dbus services are started alphabetically without checking if they belong
to the current DE...

Other solutions I can think off:
1) use a system wide notification daemon for all DE's, rather complicated needs work to integrate well.
2) start the daemons in /etc/xdg/autostart where they can be selected correctly with
   NotShowIn=GNOME;KDE;Unity;MATE; etc.
   this is a minor change that could be attempted even at devuan level to ensure that different DE's
   installed play along nice.
I will test n.2 and report.

Tito

> Mark
> 

---

Message #47 received at 373@bugs.devuan.org (full text, mbox, reply):

Control: tags -1 debian

On Fri, Jan 31, 2020 at 03:04:13PM +0100, Where all about bugs in Devuan packages is reported wrote:
> >Do you think this is the same as Debian #899377
> >(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899377)
> 
> Hi,
> yes this looks the same due to plasma-desktop being installed
> and if I recall correctly notifications were working before
> installing it.
> >Are there any message in /var/log/daemon.log  relating to failed DBus activation
> >start of xfce4-notifyd?
> 
> Yes at the end: Jan 31 14:21:18 devuan dbus-daemon[4160]: [session uid=1002 pid=4158] Activated service 'org.freedesktop.Notifications' failed: Process org.freedesktop.Notifications exited with status 1
> but with no hints about the reason of failure.

Yes, this looks the same.

I know there is no solution to the underlying cause in Debian's #899377 either.
 
> >I also notice that you have plasma-workspace installed as does the reporter in
> >https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899377#32. He also provides a
> >workaround.
> 
> I did try other notification services: dunst and growl that did work,  but they do not integrate well
> with xfce's notification settings.
> 
> Removing /usr/share/dbus-1/services/org.kde.plasma.Notifications.service don't seem a viable option to me.
> 
> I cannot believe that this dbus services are started alphabetically without checking if they belong
> to the current DE...

Can you modify /usr/share/dbus-1/services/org.kde.plasma.Notifications.service
to check if kde is running?

> Other solutions I can think off:
>
> 1) use a system wide notification daemon for all DE's, rather complicated needs work to integrate well.
> 2) start the daemons in /etc/xdg/autostart where they can be selected correctly with
>    NotShowIn=GNOME;KDE;Unity;MATE; etc.
>    this is a minor change that could be attempted even at devuan level to ensure that different DE's
>    installed play along nice.

I really doubt we can or would implement this in Devuan. The issue is that these
are not forked packages. We use them directly from Debian. We have no control
over them.

I think your best course of action is to add your voice to #899377 and push for
a resolution there.

Sorry not to be able to be more helpful.

Mark

---

Message #54 received at 373@bugs.devuan.org (full text, mbox, reply):

On 1/31/20 3:28 PM, Mark Hindley wrote:
> Control: tags -1 debian
> 
> On Fri, Jan 31, 2020 at 03:04:13PM +0100, Where all about bugs in Devuan packages is reported wrote:
>>> Do you think this is the same as Debian #899377
>>> (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899377)
>>
>> Hi,
>> yes this looks the same due to plasma-desktop being installed
>> and if I recall correctly notifications were working before
>> installing it.
>>> Are there any message in /var/log/daemon.log  relating to failed DBus activation
>>> start of xfce4-notifyd?
>>
>> Yes at the end: Jan 31 14:21:18 devuan dbus-daemon[4160]: [session uid=1002 pid=4158] Activated service 'org.freedesktop.Notifications' failed: Process org.freedesktop.Notifications exited with status 1
>> but with no hints about the reason of failure.
> 
> Yes, this looks the same.
> 
> I know there is no solution to the underlying cause in Debian's #899377 either.
>   
>>> I also notice that you have plasma-workspace installed as does the reporter in
>>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899377#32. He also provides a
>>> workaround.
>>
>> I did try other notification services: dunst and growl that did work,  but they do not integrate well
>> with xfce's notification settings.
>>
>> Removing /usr/share/dbus-1/services/org.kde.plasma.Notifications.service don't seem a viable option to me.
>>
>> I cannot believe that this dbus services are started alphabetically without checking if they belong
>> to the current DE...
> 
> Can you modify /usr/share/dbus-1/services/org.kde.plasma.Notifications.service
> to check if kde is running?
> 
>> Other solutions I can think off:
>>
>> 1) use a system wide notification daemon for all DE's, rather complicated needs work to integrate well.
>> 2) start the daemons in /etc/xdg/autostart where they can be selected correctly with
>>     NotShowIn=GNOME;KDE;Unity;MATE; etc.
>>     this is a minor change that could be attempted even at devuan level to ensure that different DE's
>>     installed play along nice.
> 
> I really doubt we can or would implement this in Devuan. The issue is that these
> are not forked packages. We use them directly from Debian. We have no control
> over them.
> 
> I think your best course of action is to add your voice to #899377 and push for
> a resolution there.
> 
> Sorry not to be able to be more helpful.
> 
> Mark

Hi,
just for the record, adding this file:

________________Cut here_______________________________
[Desktop Entry]
Encoding=UTF-8
Version=0.9.4
Type=Application
Name=xfce4-notifyd
Comment=Xfce4 Notification Daemon
Exec=/usr/lib/x86_64-linux-gnu/xfce4/notifyd/xfce4-notifyd
OnlyShowIn=XFCE;
StartupNotify=false
Terminal=false
Hidden=false
GenericName=Xfce4 Notification Daemon
________________and here________________________________


in /etc/xdg/autostart/xfce4-notifyd.desktop

fixes it for me and does not break KDE.
Even if run with systemd this cannot harm
because the daemon exits if another instance
is running.

$ /usr/lib/x86_64-linux-gnu/xfce4/notifyd/xfce4-notifyd
Another notification daemon is running, exiting

Tito

---

Send a report that this bug log contains spam.

---