Mailinglist Archive: opensuse-bugs (4297 mails)

< Previous Next >
[Bug 1041499] New: xfce4-notifyd fails to start via systemd unit file
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Tue, 30 May 2017 00:06:53 +0000
  • Message-id: <bug-1041499-21960@http.bugzilla.opensuse.org/>
http://bugzilla.opensuse.org/show_bug.cgi?id=1041499


Bug ID: 1041499
Summary: xfce4-notifyd fails to start via systemd unit file
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: Other
OS: Other
Status: NEW
Severity: Major
Priority: P5 - None
Component: Xfce
Assignee: bnc-team-xfce@xxxxxxxxxxxxxxxxxxxxxx
Reporter: pfhllnts@xxxxxxxxxxxx
QA Contact: qa-bugs@xxxxxxx
Found By: ---
Blocker: ---

Created attachment 726842
--> http://bugzilla.opensuse.org/attachment.cgi?id=726842&action=edit
strace logfile

Xfce notifications and applications depending on them such as
xfce4-power-manager are currently broken in Tumbleweed because xfce4-notifyd
fails to start:

pief@e7450:~> systemctl --user start xfce4-notifyd.service
Job for xfce4-notifyd.service failed because the control process exited with
error code.
See "systemctl status xfce4-notifyd.service" and "journalctl -xe" for
details.
pief@e7450:~> systemctl --user status xfce4-notifyd.service
● xfce4-notifyd.service - XFCE notifications service
Loaded: loaded (/usr/lib/systemd/user/xfce4-notifyd.service; static;
vendor preset: enabled)
Active: failed (Result: exit-code) since Tue 2017-05-30 02:00:33 CEST; 1s
ago
Process: 16794 ExecStart=/usr/lib/xfce4/notifyd/xfce4-notifyd (code=exited,
status=1/FAILURE)
Main PID: 16794 (code=exited, status=1/FAILURE)

Mai 30 02:00:33 e7450.bs3.hollants.com systemd[2389]: Starting XFCE
notifications service...
Mai 30 02:00:33 e7450.bs3.hollants.com xfce4-notifyd[16794]: No protocol
specified
Mai 30 02:00:33 e7450.bs3.hollants.com xfce4-notifyd[16794]: Unable to init
server: Could not connect: Connection refused
Mai 30 02:00:33 e7450.bs3.hollants.com systemd[2389]: xfce4-notifyd.service:
Main process exited, code=exited, status=1/FAILURE
Mai 30 02:00:33 e7450.bs3.hollants.com systemd[2389]: Failed to start XFCE
notifications service.
Mai 30 02:00:33 e7450.bs3.hollants.com systemd[2389]: xfce4-notifyd.service:
Unit entered failed state.
Mai 30 02:00:33 e7450.bs3.hollants.com systemd[2389]: xfce4-notifyd.service:
Failed with result 'exit-code'.

It starts successfully, however, when started manually.

Adding strace in xfce4-notifyd's unit file shows that it appears to expect
broadwayd to be running when started via the unit file:

[...]
futex(0x7f33c514c4a8, FUTEX_WAKE_PRIVATE, 2147483647) = 0
futex(0x7f33c514c4a8, FUTEX_WAKE_PRIVATE, 2147483647) = 0
futex(0x7f33c514c4a8, FUTEX_WAKE_PRIVATE, 2147483647) = 0
futex(0x7f33c514c4a8, FUTEX_WAKE_PRIVATE, 2147483647) = 0
connect(5, {sa_family=AF_UNIX, sun_path=@"/run/user/1000/broadway1.socket"},
34) = -1 ECONNREFUSED (Connection refused)
open("/usr/lib64/charset.alias", O_RDONLY) = -1 ENOENT (No such file or
directory)
futex(0x7f33c514c4a8, FUTEX_WAKE_PRIVATE, 2147483647) = 0
futex(0x7f33c514c4a8, FUTEX_WAKE_PRIVATE, 2147483647) = 0
close(5) = 0
write(2, "Unable to init server: Could not"..., 61) = 61
[...]

And indeed, with "broadwayd :0" running in a separate terminal xfce4-notifyd
starts successfully. But this clearly can't be the intent?

--
You are receiving this mail because:
You are on the CC list for the bug.
< Previous Next >