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
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 definite
Broke for me recently too. I had to add this to my .xinitrc:
systemctl --user start xfce4-notifyd.service
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
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
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
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
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/xin
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
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.
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 so
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
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
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: WaitForN
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: dbu
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 w
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 vari
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]: Activat
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
>
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]: Activa
On 06/26/2017 12:22 PM, Jérôme M. Berger wrote:
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 .
On 06/26/2017 01:07 PM, David Rosenstrauch wrote:
> Is there some way to enable more detailed logging in dbus?
d-feet [0] makes it debugging Dbus easier. It can be used to inspect
Dbus interface of running programs and invoke methods on those interfaces.
Ubuntu's wiki has a more ugly way of debug
On 06/26/2017 06:30 PM, David Rosenstrauch wrote:
> Any idea how to resolve the conflict between these 2 notification
> services? (Without being forced to remove half of KDE?)
>
> For example, dbus seems to be selecting the kde plasma notification
> service to respond to the org.freedesktop.Not
On 06/26/2017 01:32 PM, Jérôme M. Berger wrote:
On 06/26/2017 06:30 PM, David Rosenstrauch wrote:
Any idea how to resolve the conflict between these 2 notification
services? (Without being forced to remove half of KDE?)
For example, dbus seems to be selecting the kde plasma notification
servic
Op 26 jun. 2017 20:19 schreef "David Rosenstrauch" :
On 06/26/2017 01:32 PM, Jérôme M. Berger wrote:
> On 06/26/2017 06:30 PM, David Rosenstrauch wrote:
>
>> Any idea how to resolve the conflict between these 2 notification
>> services? (Without being forced to remove half of KDE?)
>>
>
A fair b
On 06/26/2017 03:56 PM, Guus Snijders via arch-general wrote:
Op 26 jun. 2017 20:19 schreef "David Rosenstrauch" :
On 06/26/2017 01:32 PM, Jérôme M. Berger wrote:
On 06/26/2017 06:30 PM, David Rosenstrauch wrote:
Any idea how to resolve the conflict between these 2 notification
services? (W
Op 26 jun. 2017 22:32 schreef "David Rosenstrauch" :
On 06/26/2017 03:56 PM, Guus Snijders via arch-general wrote:
> [...]
> In short: they use dbus permissions for blacklisting.
> [...]
>
> A deny policy (on the KDE notification) for your user should solve the
> problem without hacking through d
On 06/26/2017 04:58 PM, Guus Snijders via arch-general wrote:
Op 26 jun. 2017 22:32 schreef "David Rosenstrauch" :
On 06/26/2017 03:56 PM, Guus Snijders via arch-general wrote:
[...]
In short: they use dbus permissions for blacklisting.
[...]
A deny policy (on the KDE notification) for your u
28 matches
Mail list logo
