xfce4-notifyd issues

classic Classic list List threaded Threaded
28 messages Options
12
Reply | Threaded
Open this post in threaded view
|

xfce4-notifyd issues

David Rosenstrauch
Seems like some recent package update has either caused xfce4-notifyd to
not autostart or to crash after starting.  Anyone else seeing this,
and/or have any idea what might be the cause?

Thanks,

DR
Reply | Threaded
Open this post in threaded view
|

Re: xfce4-notifyd issues

David Rosenstrauch
On 06/20/2017 10:10 PM, David Rosenstrauch wrote:
> Seems like some recent package update has either caused xfce4-notifyd to
> not autostart or to crash after starting.  Anyone else seeing this,
> and/or have any idea what might be the cause?

Not sure if it's having autostart issues, but it definitely seems to be
crashing for some reason:

[darose@darosedm ~]$ ps ax | grep notify
  3168 pts/1    S+     0:00 grep notify
[darose@darosedm ~]$ systemctl --user start xfce4-notifyd.service
[darose@darosedm ~]$ ps ax | grep notify
  3173 ?        Ssl    0:00 /usr/lib/xfce4/notifyd/xfce4-notifyd
  3179 pts/1    S+     0:00 grep notify
[darose@darosedm ~]$ date
Tue Jun 20 22:32:49 EDT 2017


[darose@darosedm ~]$ ps ax | grep notify
  3511 pts/1    S+     0:00 grep notify
[darose@darosedm ~]$ date
Tue Jun 20 22:51:28 EDT 2017


Anyone have any idea what's happening - or how to debug?  I don't see
anything in the messages.log.

Thanks,

DR
Reply | Threaded
Open this post in threaded view
|

Re: xfce4-notifyd issues

arch general mailing list-2
In reply to this post by David Rosenstrauch
Broke for me recently too. I had to add this to my .xinitrc:

systemctl --user start xfce4-notifyd.service
Reply | Threaded
Open this post in threaded view
|

Re: xfce4-notifyd issues

David Rosenstrauch
On 06/21/2017 08:17 AM, David Barri via arch-general wrote:
> Broke for me recently too. I had to add this to my .xinitrc:
>
> systemctl --user start xfce4-notifyd.service
>

1) Any idea what's responsible?

2) From what I can see the issue isn't just startup.  If you see my
previous email, it looks like the notifyd is crashing for some reason.

DR
Reply | Threaded
Open this post in threaded view
|

Re: xfce4-notifyd issues

Bjoern Franke
In reply to this post by arch general mailing list-2
Am 21.06.2017 um 14:17 schrieb David Barri via arch-general:
> Broke for me recently too. I had to add this to my .xinitrc:
>
> systemctl --user start xfce4-notifyd.service
>

Which DE are you using? With XFCE, it's autostarted here, not need for
systemctl --user.

Regards
Bjoern
Reply | Threaded
Open this post in threaded view
|

Re: xfce4-notifyd issues

David Rosenstrauch
On 06/21/2017 03:07 PM, Bjoern Franke wrote:

> Am 21.06.2017 um 14:17 schrieb David Barri via arch-general:
>> Broke for me recently too. I had to add this to my .xinitrc:
>>
>> systemctl --user start xfce4-notifyd.service
>>
>
> Which DE are you using? With XFCE, it's autostarted here, not need for
> systemctl --user.
>
> Regards
> Bjoern

I (the original reporter) am running XFCE.

I've done a bit of research on the issue.  Seems like what's happening is:

a) Apparently xfce4-notifyd intentionally (!) shuts itself down after 10
mins of inactivity (see
https://bugzilla.xfce.org/show_bug.cgi?id=12754).  However, it's had
this behavior for quite some time (since v0.3.0 - we're now at 0.3.6),
so I don't think this is the source of the issue.

b) It looks like what changed recently is that for some reason dbus is
no longer able to automatically restart xfce4-notifyd when a
notification happens.  See what I get when I issue "notify-send 'test'":

Jun 21 15:08:16 darosedm dbus-daemon[628]: Activating service
name='org.freedesktop.Notifications'
Jun 21 15:09:16 darosedm plasma_waitforname[7097]:
org.kde.knotifications: WaitForName: Service was not registered within
timeout
Jun 21 15:09:16 darosedm dbus-daemon[628]: Activated service
'org.freedesktop.Notifications' failed: Process
org.freedesktop.Notifications exited with status 1

I haven't quite pinned down what's causing the restart to fail yet.  If
anyone has any relevant info, please do share.

Thanks,

DR
Reply | Threaded
Open this post in threaded view
|

Re: xfce4-notifyd issues

arch general mailing list-2
On 21-06-2017 20:16, David Rosenstrauch wrote:

> On 06/21/2017 03:07 PM, Bjoern Franke wrote:
>> Am 21.06.2017 um 14:17 schrieb David Barri via arch-general:
>>> Broke for me recently too. I had to add this to my .xinitrc:
>>>
>>> systemctl --user start xfce4-notifyd.service
>>>
>>
>> Which DE are you using? With XFCE, it's autostarted here, not need for
>> systemctl --user.
>>
>> Regards
>> Bjoern
>
> I (the original reporter) am running XFCE.
>
> I've done a bit of research on the issue.  Seems like what's happening is:
>
> a) Apparently xfce4-notifyd intentionally (!) shuts itself down after 10
> mins of inactivity (see
> https://bugzilla.xfce.org/show_bug.cgi?id=12754).  However, it's had
> this behavior for quite some time (since v0.3.0 - we're now at 0.3.6),
> so I don't think this is the source of the issue.
>
> b) It looks like what changed recently is that for some reason dbus is
> no longer able to automatically restart xfce4-notifyd when a
> notification happens.  See what I get when I issue "notify-send 'test'":
>
> Jun 21 15:08:16 darosedm dbus-daemon[628]: Activating service
> name='org.freedesktop.Notifications'
> Jun 21 15:09:16 darosedm plasma_waitforname[7097]:
> org.kde.knotifications: WaitForName: Service was not registered within
> timeout
> Jun 21 15:09:16 darosedm dbus-daemon[628]: Activated service
> 'org.freedesktop.Notifications' failed: Process
> org.freedesktop.Notifications exited with status 1
>
> I haven't quite pinned down what's causing the restart to fail yet.  If
> anyone has any relevant info, please do share.
>

It's working fine here.

I don't use a login manager, I login from a tty and I haven't changed
any configuration in a long while. I also don't do anything special to
launch xfce or anything else.

my .xinitrc has:

if [ -d /etc/X11/xinit/xinitrc.d ]; then
  for f in /etc/X11/xinit/xinitrc.d/*; do
    [ -x "$f" ] && . "$f"
  done
  unset f
fi
exec startxfce4

and that's all.

--
Mauro Santos
Reply | Threaded
Open this post in threaded view
|

Re: xfce4-notifyd issues

David Rosenstrauch

On 06/21/2017 05:41 PM, Mauro Santos via arch-general wrote:

> It's working fine here.
>
> I don't use a login manager, I login from a tty and I haven't changed
> any configuration in a long while. I also don't do anything special to
> launch xfce or anything else.
>
> my .xinitrc has:
>
> if [ -d /etc/X11/xinit/xinitrc.d ]; then
>    for f in /etc/X11/xinit/xinitrc.d/*; do
>      [ -x "$f" ] && . "$f"
>    done
>    unset f
> fi
> exec startxfce4
>
> and that's all.
>

Useful data point - thanks.  I am using a login manager (lightdm), which
launches startxfce4.  Perhaps there's something got messed up with that
combination.

Thanks,

DR
Reply | Threaded
Open this post in threaded view
|

Re: xfce4-notifyd issues

arch general mailing list-2
Hello,
** David Rosenstrauch [2017-06-22 21:52:28 -0400]:

>
> On 06/21/2017 05:41 PM, Mauro Santos via arch-general wrote:
>> It's working fine here.
>>
>> I don't use a login manager, I login from a tty and I haven't changed
>> any configuration in a long while. I also don't do anything special to
>> launch xfce or anything else.
>>
>> my .xinitrc has:
>>
>> if [ -d /etc/X11/xinit/xinitrc.d ]; then
>>    for f in /etc/X11/xinit/xinitrc.d/*; do
>>      [ -x "$f" ] && . "$f"
>>    done
>>    unset f
>> fi
>> exec startxfce4
>>
>> and that's all.
>>
>
> Useful data point - thanks.  I am using a login manager (lightdm), which
> launches startxfce4.  Perhaps there's something got messed up with that
> combination.

Try sddm.

> Thanks,
>
> DR

---
WBR. Vladimir Lomov

--
"Gort, klaatu nikto barada."
-- The Day the Earth Stood Still
Reply | Threaded
Open this post in threaded view
|

Re: xfce4-notifyd issues

David Rosenstrauch
On 06/23/2017 03:53 AM, Vladimir Lomov via arch-general wrote:
> ** David Rosenstrauch [2017-06-22 21:52:28 -0400]:
>> Useful data point - thanks.  I am using a login manager (lightdm), which
>> launches startxfce4.  Perhaps there's something got messed up with that
>> combination.
>
> Try sddm.

Perhaps.  To be honest, I don't think lightdm is responsible for the
issue either.  (It hasn't been updated since March.)  There's obviously
*something* that changed recently that's causing this behavior.  I'm not
sure what - or how to fix.  But there's some evidence this might get
fixed on the XFCE side soon.

Thanks,

DR
Reply | Threaded
Open this post in threaded view
|

Re: xfce4-notifyd issues

arch general mailing list-2
Hello,
** David Rosenstrauch [2017-06-23 09:27:41 -0400]:

> On 06/23/2017 03:53 AM, Vladimir Lomov via arch-general wrote:
>> ** David Rosenstrauch [2017-06-22 21:52:28 -0400]:
>>> Useful data point - thanks.  I am using a login manager (lightdm), which
>>> launches startxfce4.  Perhaps there's something got messed up with that
>>> combination.
>>
>> Try sddm.
>
> Perhaps.  To be honest, I don't think lightdm is responsible for the issue
> either.  (It hasn't been updated since March.)  There's obviously
> *something* that changed recently that's causing this behavior.  I'm not
> sure what - or how to fix.  But there's some evidence this might get fixed
> on the XFCE side soon.

I used to use lightdm for some time but from time to time I faced with very
*strange* message from various programs about connection to dbus (they
refered to /tmp/dbus-XXXXX, saying "Connection failed" or something like
that, but dbus is started by systemd and it's socket is in /run NOT in
/tmp). I tried to investigate this problem but without any success.

Moreover, I found some problem with how lightdm initialize session (I
don't remember details, though I filed a bug report for that) but AFAIU
it wasn't fixed. I switched to sddm and don't see any more any messages
about dbus in /tmp.

> Thanks,
>
> DR

---
WBR, Vladimir Lomov

--
When women kiss it always reminds one of prize fighters shaking hands.
                -- H.L. Mencken, "Sententiae"
Reply | Threaded
Open this post in threaded view
|

Re: xfce4-notifyd issues

David Rosenstrauch
In reply to this post by David Rosenstrauch
On 06/23/2017 09:27 AM, David Rosenstrauch wrote:

> On 06/23/2017 03:53 AM, Vladimir Lomov via arch-general wrote:
>> ** David Rosenstrauch [2017-06-22 21:52:28 -0400]:
>>> Useful data point - thanks.  I am using a login manager (lightdm), which
>>> launches startxfce4.  Perhaps there's something got messed up with that
>>> combination.
>>
>> Try sddm.
>
> Perhaps.  To be honest, I don't think lightdm is responsible for the
> issue either.  (It hasn't been updated since March.)  There's obviously
> *something* that changed recently that's causing this behavior.  I'm not
> sure what - or how to fix.  But there's some evidence this might get
> fixed on the XFCE side soon.

FYI, I just tested under sddm and I still see the same issue.  For
whatever reason, xfce4-notifyd does not get started in response to
attempts to launch service 'org.freedesktop.Notifications':

Jun 23 16:55:27 darosedm dbus-daemon[723]: Activating service
name='org.freedesktop.Notifications'
Jun 23 16:56:27 darosedm plasma_waitforname[1988]:
org.kde.knotifications: WaitForName: Service was not registered within
timeout
Jun 23 16:56:27 darosedm dbus-daemon[723]: Activated service
'org.freedesktop.Notifications' failed: Process
org.freedesktop.Notifications exited with status 1

DR
Reply | Threaded
Open this post in threaded view
|

Re: xfce4-notifyd issues

Jérôme M. Berger
On 06/23/2017 10:58 PM, David Rosenstrauch wrote:
> Jun 23 16:55:27 darosedm dbus-daemon[723]: Activating service
> name='org.freedesktop.Notifications'
> Jun 23 16:56:27 darosedm plasma_waitforname[1988]:
> org.kde.knotifications: WaitForName: Service was not registered within
> timeout

        Why does it say that it is waiting for org.*kde*.knotifications and not
org.freedesktop.Notifications? I'm betting there is some kind of
configuration conflict between knotifyd and xfce-notifyd. I would grep
for those two strings inside /usr/share/dbus-1/services to check if
there is not a stale service file causing the trouble.

                Jerome
--
mailto:[hidden email]
http://jeberger.free.fr
Diaspora*: https://framasphere.org/u/jeberger


signature.asc (227 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: xfce4-notifyd issues

L. Rose


Am 24.06.2017 um 08:30 schrieb Jérôme M. Berger:

> On 06/23/2017 10:58 PM, David Rosenstrauch wrote:
>> Jun 23 16:55:27 darosedm dbus-daemon[723]: Activating service
>> name='org.freedesktop.Notifications'
>> Jun 23 16:56:27 darosedm plasma_waitforname[1988]:
>> org.kde.knotifications: WaitForName: Service was not registered within
>> timeout
> Why does it say that it is waiting for org.*kde*.knotifications and not
> org.freedesktop.Notifications? I'm betting there is some kind of
> configuration conflict between knotifyd and xfce-notifyd. I would grep
> for those two strings inside /usr/share/dbus-1/services to check if
> there is not a stale service file causing the trouble.
>
> Jerome
I'm using xfce4 with lightdm, everything working fine here.
Reply | Threaded
Open this post in threaded view
|

Re: xfce4-notifyd issues

Paul Franke
In reply to this post by David Rosenstrauch
> 1) Any idea what's responsible?
>
> 2) From what I can see the issue isn't just startup.  If you see my
> previous email, it looks like the notifyd is crashing for some reason.

Maybe, xfce4-notifyd crashes on startup due to not set DISPLAY
environment variable?

Please, check for DISPLAY using: dbus-update-activation-environment
--verbose --all

If not, make sure /etc/X11/xinit/xinitrc.d/50-systemd-user.sh gets
sourced on startup of Xorg in some way.
Reply | Threaded
Open this post in threaded view
|

Re: xfce4-notifyd issues

David Rosenstrauch
In reply to this post by Jérôme M. Berger


On 06/24/2017 02:30 AM, Jérôme M. Berger wrote:

> On 06/23/2017 10:58 PM, David Rosenstrauch wrote:
>> Jun 23 16:55:27 darosedm dbus-daemon[723]: Activating service
>> name='org.freedesktop.Notifications'
>> Jun 23 16:56:27 darosedm plasma_waitforname[1988]:
>> org.kde.knotifications: WaitForName: Service was not registered within
>> timeout
>
> Why does it say that it is waiting for org.*kde*.knotifications and not
> org.freedesktop.Notifications? I'm betting there is some kind of
> configuration conflict between knotifyd and xfce-notifyd. I would grep
> for those two strings inside /usr/share/dbus-1/services to check if
> there is not a stale service file causing the trouble.
>
> Jerome

My guess is because I have many KDE packages installed, even though I'm
not running KDE.  (My DE is XFCE.)

I did that grep, but didn't see anything suspicious:

[darose@darosedm services]$ find . -type f | xargs grep notify
./org.kde.knotify.service:Name=org.kde.knotify
./org.kde.knotify.service:Exec=/usr/bin/knotify4
./org.xfce.xfce4-notifyd.Notifications.service:Exec=/usr/lib/xfce4/notifyd/xfce4-notifyd
./org.xfce.xfce4-notifyd.Notifications.service:SystemdService=xfce4-notifyd.service

Thanks,

DR
Reply | Threaded
Open this post in threaded view
|

Re: xfce4-notifyd issues

David Rosenstrauch
In reply to this post by Paul Franke
On 06/25/2017 09:03 AM, Paul Franke wrote:

>> 1) Any idea what's responsible?
>>
>> 2) From what I can see the issue isn't just startup.  If you see my
>> previous email, it looks like the notifyd is crashing for some reason.
>
> Maybe, xfce4-notifyd crashes on startup due to not set DISPLAY
> environment variable?
>
> Please, check for DISPLAY using: dbus-update-activation-environment
> --verbose --all
>
> If not, make sure /etc/X11/xinit/xinitrc.d/50-systemd-user.sh gets
> sourced on startup of Xorg in some way.

I've come to the conclusion that xfce4-notifyd isn't crashing on
startup, but rather it's intentionally shutting down on inactivity.
(See https://bugzilla.xfce.org/show_bug.cgi?id=12754)  And the problem
isn't that it's shutting down, but rather that it's not able to
successfully restart itself.

The DISPLAY variable does seem to be getting set correctly in my console
sessions:

$ dbus-update-activation-environment --verbose --all 2>&1 | grep DISPLAY
dbus-update-activation-environment: setting DISPLAY=:0.0

But perhaps it's not getting set for non-interactive/non-login sessions
somehow.  I'll look into that.

Thanks,

DR
Reply | Threaded
Open this post in threaded view
|

Re: xfce4-notifyd issues

David Rosenstrauch
In reply to this post by David Rosenstrauch
On 06/23/2017 04:58 PM, David Rosenstrauch wrote:

> FYI, I just tested under sddm and I still see the same issue.  For
> whatever reason, xfce4-notifyd does not get started in response to
> attempts to launch service 'org.freedesktop.Notifications':
>
> Jun 23 16:55:27 darosedm dbus-daemon[723]: Activating service
> name='org.freedesktop.Notifications'
> Jun 23 16:56:27 darosedm plasma_waitforname[1988]:
> org.kde.knotifications: WaitForName: Service was not registered within
> timeout
> Jun 23 16:56:27 darosedm dbus-daemon[723]: Activated service
> 'org.freedesktop.Notifications' failed: Process
> org.freedesktop.Notifications exited with status 1

Does anyone know how I might go about debugging how/why this failure is
happening?

Jun 23 16:56:27 darosedm dbus-daemon[723]: Activated service
'org.freedesktop.Notifications' failed: Process
org.freedesktop.Notifications exited with status 1

Is there some way to enable more detailed logging in dbus?

Thanks,

DR
Reply | Threaded
Open this post in threaded view
|

Re: xfce4-notifyd issues

Jérôme M. Berger
In reply to this post by David Rosenstrauch
On 06/26/2017 04:32 PM, David Rosenstrauch wrote:
> My guess is because I have many KDE packages installed, even though I'm
> not running KDE.  (My DE is XFCE.)
>
> I did that grep, but didn't see anything suspicious:
>
> [darose@darosedm services]$ find . -type f | xargs grep notify
>
        Wrong grep. Try:
> grep org.freedesktop.Notifications -r /usr/share/dbus-1/services

and especially:
> grep org.kde.knotifications -r /usr/share/dbus-1/services

        The second one in particular should not return anything but I'm betting
in your case it will...

                Jerome
--
mailto:[hidden email]
http://jeberger.free.fr
Diaspora*: https://framasphere.org/u/jeberger


signature.asc (227 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: xfce4-notifyd issues

David Rosenstrauch
In reply to this post by David Rosenstrauch

On 06/23/2017 04:58 PM, David Rosenstrauch wrote:

> FYI, I just tested under sddm and I still see the same issue.  For
> whatever reason, xfce4-notifyd does not get started in response to
> attempts to launch service 'org.freedesktop.Notifications':
>
> Jun 23 16:55:27 darosedm dbus-daemon[723]: Activating service
> name='org.freedesktop.Notifications'
> Jun 23 16:56:27 darosedm plasma_waitforname[1988]:
> org.kde.knotifications: WaitForName: Service was not registered within
> timeout
> Jun 23 16:56:27 darosedm dbus-daemon[723]: Activated service
> 'org.freedesktop.Notifications' failed: Process
> org.freedesktop.Notifications exited with status 1

I finally see what happened.  The file
"/usr/share/dbus-1/services/org.kde.plasma.Notifications.service",
provided by package plasma-workspace is new, and is conflicting with
file org.xfce.xfce4-notifyd.Notifications.service.  When I move it out
of the way, xfce4-notifyd launches properly:

Jun 26 12:19:31 darosedm dbus-daemon[640]: Activating via systemd:
service name='org.freedesktop.Notifications' unit='xfce4-notifyd.service'
Jun 26 12:19:31 darosedm systemd[614]: Starting XFCE notifications
service...
Jun 26 12:19:31 darosedm dbus-daemon[640]: Successfully activated
service 'org.freedesktop.Notifications'
Jun 26 12:19:31 darosedm systemd[614]: Started XFCE notifications service.
Jun 26 12:20:12 darosedm dbus-daemon[640]: Reloaded configuration

Now I just need to figure out how to resolve the conflict.

DR
12