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

Full log

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

Received: (at 373) by bugs.devuan.org; 31 Jan 2020 14:29:45 +0000
Return-Path: <mark@hindley.org.uk>
Delivered-To: devuanbugs@dyne.org
Received: from tupac3.dyne.org [195.169.149.119]
	by doc.devuan.org with IMAP (fetchmail-6.4.0.beta4)
	for <debbugs@localhost> (single-drop); Fri, 31 Jan 2020 14:29:45 +0000 (UTC)
Received: from mx.hindley.org.uk (mohindley.plus.com [81.174.245.179])
	(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
	(No client certificate requested)
	by vm6.ganeti.dyne.org (Postfix) with ESMTPS id A2032F60B11
	for <373@bugs.devuan.org>; Fri, 31 Jan 2020 15:29:08 +0100 (CET)
Received: from apollo.hindleynet ([192.168.1.3] helo=apollo)
	by mx.hindley.org.uk with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128)
	(Exim 4.84_2)
	(envelope-from <mark@hindley.org.uk>)
	id 1ixXI4-0002zH-QR
	for 373@bugs.devuan.org; Fri, 31 Jan 2020 14:29:03 +0000
Received: from mark by apollo with local (Exim 4.84_2)
	(envelope-from <mark@hindley.org.uk>)
	id 1ixXI0-0007wM-9Z
	for 373@bugs.devuan.org; Fri, 31 Jan 2020 14:28:56 +0000
Date: Fri, 31 Jan 2020 14:28:56 +0000
From: Mark Hindley <mark@hindley.org.uk>
To: 373@bugs.devuan.org
Subject: Re: bug#373: xfce4-notifyd not started at xfce session login
Message-ID: <20200131142856.GU14807@hindley.org.uk>
References: <20200128111609.GA6659@hindley.org.uk>
 <a0f7e93c-ab5d-c222-1a8d-e19c5e69f363@tiscali.it>
 <fb22c443-2b31-b8c8-52f0-b0f4d5bd37fe@tiscali.it>
 <20200129111520.GI14807@hindley.org.uk>
 <a0f7e93c-ab5d-c222-1a8d-e19c5e69f363@tiscali.it>
 <058bcdfb-dcb6-9a33-e427-46b0f2789640@tiscali.it>
 <20200131101926.GR14807@hindley.org.uk>
 <20200131103420.GS14807@hindley.org.uk>
 <a0f7e93c-ab5d-c222-1a8d-e19c5e69f363@tiscali.it>
 <mailman.3806.1580480255.1855.devuan-bugs@lists.dyne.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <mailman.3806.1580480255.1855.devuan-bugs@lists.dyne.org>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-Spam-Status: No, score=-0.0 required=5.0 tests=SPF_PASS autolearn=disabled
	version=3.4.2
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on tupac3.dyne.org

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

Send a report that this bug log contains spam.