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

Full log

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

Received: (at 373) by bugs.devuan.org; 31 Jan 2020 22:30:26 +0000
Return-Path: <farmatito@tiscali.it>
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 22:30:25 +0000 (UTC)
Received: from smtp.tiscali.it (santino-notr.mail.tiscali.it [213.205.33.215])
	(using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits))
	(No client certificate requested)
	by vm6.ganeti.dyne.org (Postfix) with ESMTPS id 50CA3F60535
	for <373@bugs.devuan.org>; Fri, 31 Jan 2020 23:27:12 +0100 (CET)
Authentication-Results: vm6.ganeti.dyne.org;
	dkim=pass (1024-bit key; unprotected) header.d=tiscali.it header.i=@tiscali.it header.b="dwq2KsF5";
	dkim-atps=neutral
Received: from [192.168.2.164] ([217.27.115.45])
	by santino.mail.tiscali.it with 
	id xATB2100j0yqAhV01ATBEV; Fri, 31 Jan 2020 22:27:11 +0000
x-auth-user: farmatito@tiscali.it
Subject: Re: [devuan-dev] bug#373: xfce4-notifyd not started at xfce session
 login
To: 373@bugs.devuan.org
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>
 <a0f7e93c-ab5d-c222-1a8d-e19c5e69f363@tiscali.it>
 <20200131142856.GU14807@hindley.org.uk>
From: Tito <farmatito@tiscali.it>
Message-ID: <e2f5bf40-6160-6fe2-1139-59867309d3ea@tiscali.it>
Date: Fri, 31 Jan 2020 23:27:02 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101
 Thunderbird/68.4.1
MIME-Version: 1.0
In-Reply-To: <20200131142856.GU14807@hindley.org.uk>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tiscali.it; s=smtp;
	t=1580509631; bh=zjoJCRkIPv/y0QleJkG1zrlIh3FHM7O1qxrcRFlx6UM=;
	h=Subject:To:References:From:Date:In-Reply-To;
	b=dwq2KsF5qI5RT7KV2916RK+YxeI9EOv8XmU8JPgUFPfv6rnOAZFNI6nWd8K/nNqjy
	 argehIOJKuEiX/SrtGxT5neoRhjFht2ksgMk94Jzw7ckWq0+f6TAvS1EtJfeYHwnj6
	 gHzJ7rakiXC1vwAKHwAhukJlVNYup/7/ytFoy0+c=
X-Spam-Status: No, score=-0.9 required=5.0 tests=DKIM_SIGNED,DKIM_VALID,
	DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,
	SPF_HELO_PASS,SPF_PASS autolearn=disabled version=3.4.2
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on tupac3.dyne.org

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.