You are not logged in.
- Topics: Active | Unanswered
#1 2017-11-23 13:19:58
- latgarf
- Member
- Registered: 2012-12-14
- Posts: 32
Failed to start XFCE notifications service.
My network-manager-applet icon in system tray is not always responsive to mouse clicking on it. Upon boot it takes minutes before it connects to wifi. Then, during operation, it can sporadically become unclickable, but after some minutes self-fixes.
While troubleshooting this problem, I found the following in journalctl:
Nov 23 12:41:38 itg dbus-daemon[467]: [session uid=1000 pid=467] Activating via systemd: service name='org.freedesktop.Notifications' unit='xfce4-notifyd.service' requested by ':1.7' (uid=1000 pid=443 comm="cbat
Nov 23 12:41:38 itg systemd[383]: Starting XFCE notifications service...
Nov 23 12:41:38 itg xfce4-notifyd[490]: Unable to init server: Could not connect: Connection refused
Nov 23 12:41:38 itg xfce4-notifyd[490]: cannot open display:
Nov 23 12:41:38 itg systemd[383]: xfce4-notifyd.service: Main process exited, code=exited, status=1/FAILURE
Nov 23 12:41:38 itg systemd[383]: xfce4-notifyd.service: Failed with result 'exit-code'.
Nov 23 12:41:38 itg systemd[383]: Failed to start XFCE notifications service.My $DISPLAY environment variable is:
$ echo $DISPLAY
:0I use naked openbox.
In order to make network manager work, I have these packages installed:
networkmanager
network-manager-applet
gnome-keyring
gnome-icon-theme
xfce4-notifyd
xfce4-power-managerHow do I further troubleshoot the problem?
Last edited by latgarf (2017-11-23 15:20:20)
Offline
#2 2017-11-23 14:13:05
- seth
- Member
- Registered: 2012-09-03
- Posts: 51,037
Re: Failed to start XFCE notifications service.
Output of "hostnamectl"?
Tried to run "xfce4-notifyd" directly?
About your network issues, consult your journal (in doubt as root or compare the timestamps in dmesg)
Offline
#3 2017-11-23 15:40:53
- latgarf
- Member
- Registered: 2012-12-14
- Posts: 32
Re: Failed to start XFCE notifications service.
Tried to run "xfce4-notifyd" directly?
$ /usr/lib/xfce4/notifyd/xfce4-notifyd
** (xfce4-notifyd:2528): WARNING **: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.$ systemctl --user start xfce4-notifyd.service
Job for xfce4-notifyd.service failed because the control process exited with error code.
See "systemctl --user status xfce4-notifyd.service" and "journalctl --user -xe" for details.This shows the cyclical nature:
$ journalctl -b --user -u xfce4-notifyd
-- Logs begin at Thu 2017-08-24 16:04:37 UTC, end at Thu 2017-11-23 15:09:48 UTC. --
Nov 23 12:41:38 itg systemd[383]: Starting XFCE notifications service...
Nov 23 12:41:38 itg xfce4-notifyd[490]: Unable to init server: Could not connect: Connection refused
Nov 23 12:41:38 itg xfce4-notifyd[490]: cannot open display:
Nov 23 12:41:38 itg systemd[383]: xfce4-notifyd.service: Main process exited, code=exited, status=1/FAILURE
Nov 23 12:41:38 itg systemd[383]: xfce4-notifyd.service: Failed with result 'exit-code'.
Nov 23 12:41:38 itg systemd[383]: Failed to start XFCE notifications service.
Nov 23 12:56:26 itg systemd[383]: Starting XFCE notifications service...
Nov 23 12:56:26 itg xfce4-notifyd[980]: Unable to init server: Could not connect: Connection refused
Nov 23 12:56:26 itg xfce4-notifyd[980]: cannot open display:
Nov 23 12:56:26 itg systemd[383]: xfce4-notifyd.service: Main process exited, code=exited, status=1/FAILURE
Nov 23 12:56:26 itg systemd[383]: xfce4-notifyd.service: Failed with result 'exit-code'.
Nov 23 12:56:26 itg systemd[383]: Failed to start XFCE notifications service.
Nov 23 12:58:26 itg systemd[383]: Starting XFCE notifications service...
Nov 23 12:58:26 itg xfce4-notifyd[1088]: Unable to init server: Could not connect: Connection refused
Nov 23 12:58:26 itg xfce4-notifyd[1088]: cannot open display:
Nov 23 12:58:26 itg systemd[383]: xfce4-notifyd.service: Main process exited, code=exited, status=1/FAILURE
Nov 23 12:58:26 itg systemd[383]: xfce4-notifyd.service: Failed with result 'exit-code'.
Nov 23 12:58:26 itg systemd[383]: Failed to start XFCE notifications service.
Nov 23 13:50:17 itg systemd[383]: Starting XFCE notifications service...
Nov 23 13:50:17 itg xfce4-notifyd[1800]: Unable to init server: Could not connect: Connection refused
Nov 23 13:50:17 itg xfce4-notifyd[1800]: cannot open display:
Nov 23 13:50:17 itg systemd[383]: xfce4-notifyd.service: Main process exited, code=exited, status=1/FAILURE
Nov 23 13:50:17 itg systemd[383]: xfce4-notifyd.service: Failed with result 'exit-code'.
Nov 23 13:50:17 itg systemd[383]: Failed to start XFCE notifications service.
Nov 23 14:04:29 itg systemd[383]: Starting XFCE notifications service...
Nov 23 14:04:29 itg xfce4-notifyd[1994]: Unable to init server: Could not connect: Connection refused
Nov 23 14:04:29 itg xfce4-notifyd[1994]: cannot open display:
Nov 23 14:04:29 itg systemd[383]: xfce4-notifyd.service: Main process exited, code=exited, status=1/FAILURE
Nov 23 14:04:29 itg systemd[383]: xfce4-notifyd.service: Failed with result 'exit-code'.
Nov 23 14:04:29 itg systemd[383]: Failed to start XFCE notifications service.
Nov 23 14:24:14 itg systemd[383]: Starting XFCE notifications service...
Nov 23 14:24:14 itg xfce4-notifyd[2227]: Unable to init server: Could not connect: Connection refused
Nov 23 14:24:14 itg xfce4-notifyd[2227]: cannot open display:
Nov 23 14:24:14 itg systemd[383]: xfce4-notifyd.service: Main process exited, code=exited, status=1/FAILURE
Nov 23 14:24:14 itg systemd[383]: xfce4-notifyd.service: Failed with result 'exit-code'.
Nov 23 14:24:14 itg systemd[383]: Failed to start XFCE notifications service.
Nov 23 14:57:19 itg systemd[383]: Starting XFCE notifications service...
Nov 23 14:57:19 itg systemd[383]: xfce4-notifyd.service: Main process exited, code=exited, status=1/FAILURE
Nov 23 14:57:19 itg systemd[383]: xfce4-notifyd.service: Failed with result 'exit-code'.
Nov 23 14:57:19 itg systemd[383]: Failed to start XFCE notifications service.
Nov 23 15:07:37 itg systemd[383]: Starting XFCE notifications service...
Nov 23 15:07:37 itg xfce4-notifyd[2737]: Unable to init server: Could not connect: Connection refused
Nov 23 15:07:37 itg xfce4-notifyd[2737]: cannot open display:
Nov 23 15:07:37 itg systemd[383]: xfce4-notifyd.service: Main process exited, code=exited, status=1/FAILURE
Nov 23 15:07:37 itg systemd[383]: xfce4-notifyd.service: Failed with result 'exit-code'.
Nov 23 15:07:37 itg systemd[383]: Failed to start XFCE notifications service.
Nov 23 15:09:48 itg systemd[383]: Starting XFCE notifications service...
Nov 23 15:09:48 itg xfce4-notifyd[2763]: Unable to init server: Could not connect: Connection refused
Nov 23 15:09:48 itg xfce4-notifyd[2763]: cannot open display:
Nov 23 15:09:48 itg systemd[383]: xfce4-notifyd.service: Main process exited, code=exited, status=1/FAILURE
Nov 23 15:09:48 itg systemd[383]: xfce4-notifyd.service: Failed with result 'exit-code'.
Nov 23 15:09:48 itg systemd[383]: Failed to start XFCE notifications service.Output of "hostnamectl"?
$ hostnamectl
Static hostname: itg
Icon name: computer-laptop
Chassis: laptop
Machine ID: 0123456789abcdef0123456789abcdef
Boot ID: 0123456789abcdef0123456789abcdef
Operating System: Arch Linux
Kernel: Linux 4.13.12-1-ARCH
Architecture: x86-64Offline
#4 2017-11-24 08:54:01
- seth
- Member
- Registered: 2012-09-03
- Posts: 51,037
Re: Failed to start XFCE notifications service.
"loginctl session-status"? Do you use startx/xinit?
Offline
#5 2017-11-24 10:20:05
- latgarf
- Member
- Registered: 2012-12-14
- Posts: 32
Re: Failed to start XFCE notifications service.
$ loginctl session-status
c1 - my_username (1000)
Since: Thu 2017-11-23 12:41:37 UTC; 21h ago
Leader: 370 (login)
Seat: seat0; vc1
TTY: tty1
Service: login; type tty; class user
State: active
Unit: session-c1.scope
├─ 370 login -- my_username
├─ 389 /bin/sh /usr/bin/startx
├─ 418 xinit /home/my_username/.xinitrc -- /etc/X11/xinit/xserverrc :0 vt1 -auth /tmp/serverauth.NSwTBv55cv
├─ 419 /usr/lib/xorg-server/Xorg -nolisten tcp :0 vt1 -auth /tmp/serverauth.NSwTBv55cv
├─ 421 xf86-video-intel-backlight-helper intel_backlight
├─ 425 sh /home/my_username/.xinitrc
├─ 427 /usr/bin/openbox --startup /usr/lib/openbox/openbox-autostart OPENBOX
├─ 438 tint2
├─ 440 /usr/bin/nm-applet
├─ 2185 dbus-launch --autolaunch e821e3716d9840068e071e9b38da411a --binary-syntax --close-stderr
├─ 2186 /usr/bin/dbus-daemon --syslog-only --fork --print-pid 5 --print-address 7 --session
├─ 2188 /usr/lib/at-spi-bus-launcher
├─ 2193 /usr/bin/dbus-daemon --config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork --print-address 3
├─ 2195 /usr/lib/at-spi2-registryd --use-gnome-session
├─14678 loginctl session-status
└─14679 lessI use startx:
~/.bash_profile
[[ -f ~/.bashrc ]] && . ~/.bashrc
[[ -z $DISPLAY && $XDG_VTNR -eq 1 ]] && exec startx~/.xinitrc
#!/bin/bash
export DE=openbox
if [ -z "$DBUS_SESSION_BUS_ADDRESS" ]; then
eval "$(dbus-launch --sh-syntax --exit-with-session)"
fi
/usr/bin/xdg-usr-dirs-update
/usr/bin/openbox-session > ~/.openbox_startup.log 2>&1Offline
#6 2017-11-24 10:26:19
- seth
- Member
- Registered: 2012-09-03
- Posts: 51,037
Re: Failed to start XFCE notifications service.
https://wiki.archlinux.org/index.php/Xinit#xinitrc
See the second note. Replace the "dbus-launch" call.
Offline
#7 2017-11-24 12:13:45
- latgarf
- Member
- Registered: 2012-12-14
- Posts: 32
Re: Failed to start XFCE notifications service.
When using this updated ~/.xinitrc
#!/bin/bash
export DE=openbox
if [ -d /etc/X11/xinit/xinitrc.d ] ; then
for f in /etc/X11/xinit/xinitrc.d/?*.sh ; do
[ -x "$f" ] && . "$f"
done
unset f
fi
/usr/bin/xdg-usr-dirs-update
/usr/bin/openbox-session > ~/.openbox_startup.log 2>&1core is dumped:
$ journalctl -b --user -u xfce4-notifyd
-- Logs begin at Thu 2017-08-24 16:04:37 UTC, end at Fri 2017-11-24 12:01:18 UTC. --
Nov 24 11:53:38 itg systemd[379]: Starting XFCE notifications service...
Nov 24 11:53:38 itg systemd[379]: Started XFCE notifications service.
Nov 24 11:53:38 itg systemd[379]: xfce4-notifyd.service: Main process exited, code=dumped, status=11/SEGV
Nov 24 11:53:38 itg systemd[379]: xfce4-notifyd.service: Failed with result 'core-dump'.
Nov 24 11:53:38 itg systemd-coredump[501]: Process 462 (xfce4-notifyd) of user 1000 dumped core.
Stack trace of thread 462:
#0 0x00007fac23794fb0 malloc_consolidate (libc.so.6)
#1 0x00007fac23797f52 _int_malloc (libc.so.6)
#2 0x00007fac2379a67a __libc_calloc (libc.so.6)
#3 0x00007fac23d69062 g_malloc0 (libglib-2.0.so.0)
#4 0x00007fac24048b16 g_type_class_ref (libgobject-2.0.so.0)
#5 0x00007fac2402d256 g_object_new_valist (libgobject-2.0.so.0)
#6 0x00007fac2402da4a g_object_new (libgobject-2.0.so.0)
#7 0x000055656073d01d n/a (xfce4-notifyd)
#8 0x000055656073a355 n/a (xfce4-notifyd)
#9 0x00007fac1de491c8 ffi_call_unix64 (libffi.so.6)
#10 0x00007fac1de48c2a ffi_call (libffi.so.6)
#11 0x00007fac2403184b g_cclosure_marshal_generic (libgobject-2.0.so.0)
#12 0x00007fac240286f5 g_closure_invoke (libgobject-2.0.so.0)
#13 0x00007fac2403c0b0 n/a (libgobject-2.0.so.0)
#14 0x00007fac24041bd1 g_signal_emitv (libgobject-2.0.so.0)
#15 0x0000556560737224 n/a (xfce4-notifyd)
#16 0x00007fac24375053 n/a (libgio-2.0.so.0)
#17 0x00007fac2434817a n/a (libgio-2.0.so.0)
#18 0x00007fac23d580be g_main_context_dispatch (libglib-2.0.so.0)
#19 0x00007fac23d59f69 n/a (libglib-2.0.so.0)
#20 0x00007fac23d5af42 g_main_loop_run (libglib-2.0.so.0)
#21 0x00007fac2581627f gtk_main (libgtk-3.so.0)
#22 0x0000556560735de1 n/a (xfce4-notifyd)
#23 0x00007fac23737f6a __libc_start_main (libc.so.6)
#24 0x0000556560735eba n/a (xfce4-notifyd)
Stack trace of thread 491:
#0 0x00007fac23802f7b __poll (libc.so.6)
#1 0x00007fac23d59ed3 n/a (libglib-2.0.so.0)
#2 0x00007fac23d59fae g_main_context_iteration (libglib-2.0.so.0)
#3 0x00007fac23d5a002 n/a (libglib-2.0.so.0)
#4 0x00007fac23d4e1eb n/a (libglib-2.0.so.0)
#5 0x00007fac23ad608a start_thread (libpthread.so.0)
#6 0x00007fac2380d47f __clone (libc.so.6)
Stack trace of thread 492:
#0 0x00007fac23807e79 syscall (libc.so.6)
#1 0x00007fac23d81f2f g_cond_wait_until (libglib-2.0.so.0)
#2 0x00007fac23d74393 n/a (libglib-2.0.so.0)
#3 0x00007fac23d48f2e n/a (libglib-2.0.so.0)
#4 0x00007fac23d4e1eb n/a (libglib-2.0.so.0)
#5 0x00007fac23ad608a start_thread (libpthread.so.0)
#6 0x00007fac2380d47f __clone (libc.so.6)
Stack trace of thread 495:
#0 0x00007fac23802f7b __poll (libc.so.6)
#1 0x00007fac23d59ed3 n/a (libglib-2.0.so.0)
#2 0x00007fac23d5af42 g_main_loop_run (libglib-2.0.so.0)
#3 0x00007fac242c5208 n/a (libgio-2.0.so.0)
#4 0x00007fac23d4e1eb n/a (libglib-2.0.so.0)
#5 0x00007fac23ad608a start_thread (libpthread.so.0)
#6 0x00007fac2380d47f __clone (libc.so.6)
Nov 24 11:53:46 itg systemd[379]: Starting XFCE notifications service...
Nov 24 11:53:46 itg systemd[379]: Started XFCE notifications service.
Nov 24 11:53:46 itg xfce4-notifyd[738]: gdk_window_get_origin: assertion 'GDK_IS_WINDOW (window)' failedBut otherwise, all seems to function smoothly, unlike before.
Offline
#8 2017-11-24 13:10:04
- seth
- Member
- Registered: 2012-09-03
- Posts: 51,037
Re: Failed to start XFCE notifications service.
Could be some early notification handling while the daemon is initilizing? Unfortunately the xfce4-notifyd symbols are stripped (or at least n/a for some reason)
=> You'll likely have to build it debug enabled to get an idea what's going on here - the present backtrace is too generic :-(
Offline