Your message dated Sat, 18 Feb 2017 15:29:47 +0100
with message-id <1487428187.2676.9.ca...@debian.org>
and subject line Re: [Pkg-xfce-devel] Bug#842712: Bug#842712: xfce4-notifyd:
fails to start because of missing DISPLAY variable
has caused the Debian Bug report #842712,
regarding xfce4-notifyd: fails to start because of missing DISPLAY variable
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
842712: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842712
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xfce4-notifyd
Version: 0.3.3-1
Severity: normal
xfce4-notifyd does not work which also affects xfce4-pulseaudio-plugin
(probably also others). The relevant system log is:
xfce4-notifyd[3009]: Unable to init server: Could not connect: Connection
refused
xfce4-notifyd[3009]: cannot open display:
systemd[1583]: xfce4-notifyd.service: Main process exited, code=exited,
status=1/FAILURE
systemd[1583]: Failed to start XFCE notifications service.
systemd[1583]: xfce4-notifyd.service: Unit entered failed state.
systemd[1583]: xfce4-notifyd.service: Failed with result 'exit-code'.
If I run /usr/lib/x86_64-linux-gnu/xfce4/notifyd/xfce4-notify or add the line
Environment="DISPLAY=:0.0" to xfce4-notifyd.service, everything works as
expected.
This is probably related to an update (though that is a rather old one) in
dbus. Before that one the DISPLAY variable was passed to any service of type
dbus, afterwards that was no longer the case. See:
https://bugs.archlinux.org/task/46374
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (500, 'testing'), (2, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages xfce4-notifyd depends on:
ii libc6 2.24-5
ii libcairo2 1.14.6-1+b1
ii libgdk-pixbuf2.0-0 2.36.0-1
ii libglib2.0-0 2.50.1-1
ii libgtk-3-0 3.22.2-1
ii libnotify4 0.7.7-1
ii libx11-6 2:1.6.3-1
ii libxfce4ui-2-0 4.12.1-2
ii libxfce4util7 4.12.1-2
ii libxfconf-0-2 4.12.0-3
Versions of packages xfce4-notifyd recommends:
ii libnotify-bin 0.7.7-1
xfce4-notifyd suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
On Tue, 2016-11-01 at 12:25 +0100, Simon Frei wrote:
> So problems also appeared with gnome-keyring. It is probably due to a
> recent (auto)installation of dbus-user-session. I added
>
> dbus-update-activation-environment --systemd --all
>
> in shell initialisation and all problems disappear, I even get more
> notifications now (e.g. from icedove). So this is clearly not a
> xfce4-notifyd problem and this can be closed - sorry for the
> inconvenience and thanks for your help.
Ok, I'm closing
>
> On 31/10/16 17:17, Yves-Alexis Perez wrote:
> >
> > I'm not sure what is your setup, but it works just fine here.
> It would be great if you could tell me whether you have
> dbus-user-session installed.
Yes.
--
Yves-Alexis
signature.asc
Description: This is a digitally signed message part
--- End Message ---
_______________________________________________
Pkg-xfce-devel mailing list
Pkg-xfce-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-xfce-devel
