Xfce Forum

Sub domains
 

You are not logged in.

#1 2017-01-23 23:11:47

rayandrews
Member
From: Vancouver B.C. Canada
Registered: 2011-12-30
Posts: 177

XFCE notifications won't start automatically.

$ journalctl -p err -b 1 | grep XFCE                                     
    Jan 11 09:24:59 HP-b6--9-Debian2 systemd[1021]: Failed to start XFCE notifications service.

    $ ps -A | g "xfce4-notifyd"   
    ... not running.
   
    $ cd /usr/lib/systemd/user; ls xfce4*
    xfce4-notifyd.service

    $ systemctl start xfce4-notifyd.service
    Failed to start xfce4-notifyd.service: Unit xfce4-notifyd.service not found.

    $ cd /usr/lib/x86_64-linux-gnu/xfce4/notifyd

    $ ./xfce4-notifyd&

    $ ps -A | grep "xfce4-notifyd"
    10372 pts/13   00:00:00 xfce4-notifyd

    $ cd /usr/lib/systemd/user
   
    $ cat xfce4-notifyd.service

    [Unit]
    Description=XFCE notifications service

    [Service]
    Type=dbus
    BusName=org.freedesktop.Notifications
    ExecStart=/usr/lib/x86_64-linux-gnu/xfce4/notifyd/xfce4-notifyd



So:
The service does not start at boot.
'ps' confirms that it isn't running.
Yet, the service is there.
But I can't start it by hand using systemctl.
But I CAN start it just fine as a normal command ...
As verified by 'ps'.
The contents of the service give no clue as to what's wrong.

What gives?  I don't know much about systemd, am I doing something wrong?

Offline

#2 2017-01-23 23:39:23

rfet35
Member
Registered: 2017-01-23
Posts: 21

Re: XFCE notifications won't start automatically.

I start my notification daemon (dunst) per .xsession

$ cat ~/.xsession
#!/bin/bash

dunst & \
startxfce4

I do use nodm display manager. Not a systemd user though. Hope it helps anyway.

Offline

#3 2017-01-23 23:47:25

rayandrews
Member
From: Vancouver B.C. Canada
Registered: 2011-12-30
Posts: 177

Re: XFCE notifications won't start automatically.

rfet35 wrote:

I start my notification daemon (dunst) per .xsession

$ cat ~/.xsession
#!/bin/bash

dunst & \
startxfce4

I do use nodm display manager. Not a systemd user though. Hope it helps anyway.

God knows.  It seems to be a systemd thing for sure.  Nothing that I know of is broken here, though.

Offline

#4 2017-08-23 00:58:57

krgailey
Member
Registered: 2017-08-23
Posts: 13

Re: XFCE notifications won't start automatically.

Did you ever get this resolved?  I'm having the same issue.  I've figured out that xfce4-notifyd doesn't stay running but about 10 minutes if inactive by design.  Dbus is supposed to load it when needed.  I'm not sure when the notifications stopped working on my machine, but finally figured out that is why network manager will not let me interact with it after connecting VPN until attemps to notify me of the established connection timeout.  I can load xfce-notifyd from terminal and the notifications pop up, network manager applet works again.

From other posts, I've tried sourcing /etc/X11/xinit/xinitrc.d/50-systemd-user.sh in /etc/xdg/xfce4/xinitrc but still not working.  I've seen code for getting xfce4-notifyd to not timeout and continue running, but I'm not sure how to implement that.

Any help troubleshooting or getting xfce4-notifyd to stay on all the time would be appreciated.

Offline

#5 2017-08-23 01:18:35

rayandrews
Member
From: Vancouver B.C. Canada
Registered: 2011-12-30
Posts: 177

Re: XFCE notifications won't start automatically.

Geez, I haven't thought about it.  I can't remember what the original issue was, except for the 'journalctl' command above, which now shows no problem ... so I guess it's resolved but I have no clue how or when or even why I cared ;-/

Offline

#6 2017-08-23 01:23:56

krgailey
Member
Registered: 2017-08-23
Posts: 13

Re: XFCE notifications won't start automatically.

Ok, thanks I'll keep searching for a solution...

Offline

#7 2017-08-23 10:31:37

ToZ
Administrator
From: Canada
Registered: 2011-06-02
Posts: 10,948

Re: XFCE notifications won't start automatically.

krgailey wrote:

From other posts, I've tried sourcing /etc/X11/xinit/xinitrc.d/50-systemd-user.sh in /etc/xdg/xfce4/xinitrc but still not working.  I've seen code for getting xfce4-notifyd to not timeout and continue running, but I'm not sure how to implement that.

Which distro are you using?
Are you using a display manager (DM like lightdm or gdm)? If so, which one?
If you are not using a display manager, how are you starting Xfce?


Please remember to mark your thread [SOLVED] to make it easier for others to find
--- How To Ask For Help | FAQ | Developer Wiki  |  Community | Contribute ---

Offline

#8 2017-08-23 23:57:51

krgailey
Member
Registered: 2017-08-23
Posts: 13

Re: XFCE notifications won't start automatically.

Moderator wrote:

Which distro are you using?
Are you using a display manager (DM like lightdm or gdm)? If so, which one?
If you are not using a display manager, how are you starting Xfce?

I'm using Manjaro x64 (Arch) Xfce, lightdm is installed.  I use Compiz to manage desktop.  Xfce starts from grub (see below), I don't load it manually.
       

echo    'Loading Linux 4.9.39-1-MANJARO x64 ...'
        linux   /vmlinuz-4.9-x86_64 root=UUID=52f6630a-beba-4d48-a8c3-99a1bc90d305 rw  quiet splash resume=UUID=0fc77a43-e668-49ac-b0ab-738da843feb0

I have logged in with test account and the issue still occurs.  I'm not sure if Compiz is active in the test account or not.

Offline

#9 2017-08-24 00:39:35

ToZ
Administrator
From: Canada
Registered: 2011-06-02
Posts: 10,948

Re: XFCE notifications won't start automatically.

First thing to try is to clear your sessions cache. When not logged in, delete the contents of ~/.cache/sessions. Log back in again and see if there is a difference.


If the problem persists, I would suggest disabling lightdm:

sudo systemctl disable lightdm

...and creating the following ~/.xinitrc file:

[[ -f ~/.session-errors ]] && mv ~/.xsession-errors ~/.xsession-errors.old

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

startxfce4 > ~/.xsession-errors 2>&1

...set the file permissions to 0700:

chmod 0700 ~/.xinitrc

...and reboot.

You will prompted with a text login screen. Log in using your credentials and start Xfce via:

startx

See if that makes a difference. If not, post back the contents of the ~/.xsession-errors file.


Note: to revert back to lightdm, run:

sudo systemctl enable lightdm

...and reboot. This will help to see if lightdm is the problem.


Please remember to mark your thread [SOLVED] to make it easier for others to find
--- How To Ask For Help | FAQ | Developer Wiki  |  Community | Contribute ---

Offline

#10 2017-08-25 01:23:01

krgailey
Member
Registered: 2017-08-23
Posts: 13

Re: XFCE notifications won't start automatically.

I did the steps you suggested and still have the notification issue.  Here are the contents of ~/.xsession-errors.  I saw some notification timeout errors near the end.  Thank you for the suggestions.

xrdb:  "Xft.hinting" on line 19 overrides entry on line 6
xrdb:  "Xft.hintstyle" on line 22 overrides entry on line 7
Xlib:  extension "RANDR" missing on display ":0".
gpg-agent[827]: WARNING: "--write-env-file" is an obsolete option - it has no effect
gpg-agent: a gpg-agent is already running - not starting a new one

(xfce4-session:816): xfce4-session-WARNING **: gpg-agent returned no PID in the variables

(xfce4-session:816): xfce4-session-WARNING **: xfsm_manager_load_session: Something wrong with /home/krgailey/.cache/sessions/xfce4-session-manjaro-xfce:0, Does it exist? Permissions issue?
Xlib:  extension "RANDR" missing on display ":0.0".
Xlib:  extension "RANDR" missing on display ":0.0".
Xlib:  extension "RANDR" missing on display ":0.0".
Xlib:  extension "RANDR" missing on display ":0.0".
Xlib:  extension "RANDR" missing on display ":0.0".

(xfsettingsd:841): xfsettingsd-CRITICAL **: No RANDR extension found in display :0.0. Display settings won't be applied.
compiz (core) - Info: Loading plugin: core
compiz (core) - Info: Starting plugin: core
compiz (core) - Info: Loading plugin: ccp
Xlib:  extension "RANDR" missing on display ":0.0".
Xlib:  extension "RANDR" missing on display ":0.0".
Xlib:  extension "RANDR" missing on display ":0.0".
compiz (core) - Info: Starting plugin: ccp

(xfsettingsd:841): xfsettingsd-WARNING **: Failed to get the _NET_NUMBER_OF_DESKTOPS property.
compizconfig - Error: error occurred during scandir: No such file or directory

** (xfce4-clipman:846): WARNING **: Unable to register GApplication: An object is already exported for the interface org.gtk.Application at /org/xfce/clipman

(xfce4-clipman:846): GLib-GIO-CRITICAL **: g_application_get_is_remote: assertion 'application->priv->is_registered' failed

(xfce4-clipman:846): GLib-WARNING **: g_set_application_name() called multiple times

(pamac-tray:864): Gdk-CRITICAL **: gdk_window_thaw_toplevel_updates: assertion 'window->update_and_descendants_freeze_count > 0' failed
Xlib:  extension "RANDR" missing on display ":0.0".
Xlib:  extension "RANDR" missing on display ":0.0".
compiz (core) - Info: Loading plugin: composite
compiz (core) - Info: Starting plugin: composite
compiz (core) - Info: Loading plugin: opengl
compiz (core) - Info: Starting plugin: opengl
Compiz (opengl) - Info: GLX_EXT_buffer_age is supported
/usr/bin/dropbox: line 2:   849 Killed                  /usr/bin/dbus-launch /opt/dropbox/dropbox start
compiz (core) - Info: Loading plugin: decor
compiz (core) - Info: Starting plugin: decor
compiz (core) - Info: Loading plugin: resize

(cairo-dock:840): Gtk-WARNING **: Theme parsing error: <data>:7:1467: The :insensitive pseudo-class is deprecated. Use :disabled instead.

(cairo-dock:840): Gtk-WARNING **: Theme parsing error: <data>:7:3649: The :inconsistent pseudo-class is deprecated. Use :indeterminate instead.
compiz (core) - Info: Starting plugin: resize
compiz (core) - Info: Loading plugin: place
compiz (core) - Info: Starting plugin: place
compiz (core) - Info: Loading plugin: move
compiz (core) - Info: Starting plugin: move
compiz (core) - Info: Loading plugin: compiztoolbox
compiz (core) - Info: Starting plugin: compiztoolbox
compiz (core) - Info: Loading plugin: staticswitcher
compiz (core) - Info: Starting plugin: staticswitcher
compiz (core) - Info: Loading plugin: expo
compiz (core) - Info: Starting plugin: expo
compiz (core) - Info: Loading plugin: grid
compiz (core) - Info: Starting plugin: grid
compiz (core) - Info: Loading plugin: regex
compiz (core) - Info: Starting plugin: regex
compiz (core) - Info: Loading plugin: animation
compiz (core) - Info: Starting plugin: animation
compiz (core) - Info: Stopping plugin: animation
compiz (core) - Info: Stopping plugin: regex
compiz (core) - Info: Stopping plugin: grid
compiz (core) - Info: Stopping plugin: expo
compiz (core) - Info: Stopping plugin: staticswitcher
compiz (core) - Info: Stopping plugin: compiztoolbox
compiz (core) - Info: Stopping plugin: move
compiz (core) - Info: Stopping plugin: place
compiz (core) - Info: Stopping plugin: resize
compiz (core) - Info: Stopping plugin: decor
compiz (core) - Info: Loading plugin: imgjpeg
compiz (core) - Info: Starting plugin: imgjpeg
compiz (core) - Info: Starting plugin: compiztoolbox
compiz (core) - Info: Starting plugin: decor
compiz (core) - Info: Starting plugin: move
compiz (core) - Info: Loading plugin: text
compiz (core) - Info: Starting plugin: text
compiz (core) - Info: Loading plugin: vpswitch
compiz (core) - Info: Starting plugin: vpswitch
compiz (core) - Info: Starting plugin: regex
compiz (core) - Info: Loading plugin: cube
compiz (core) - Info: Starting plugin: cube
compiz (core) - Info: Loading plugin: rotate
compiz (core) - Info: Starting plugin: rotate
compiz (core) - Info: Loading plugin: mousepoll
compiz (core) - Info: Starting plugin: mousepoll
compiz (core) - Info: Loading plugin: imgpng
compiz (core) - Info: Starting plugin: imgpng
compiz (core) - Info: Starting plugin: resize
compiz (core) - Info: Starting plugin: staticswitcher
compiz (core) - Info: Starting plugin: place
compiz (core) - Info: Starting plugin: grid
compiz (core) - Info: Loading plugin: workspacenames
compiz (core) - Info: Starting plugin: workspacenames
compiz (core) - Info: Starting plugin: animation
compiz (core) - Info: Starting plugin: expo

(pamac-tray:864): Gdk-CRITICAL **: gdk_window_thaw_toplevel_updates: assertion 'window->update_and_descendants_freeze_count > 0' failed

(xfce4-clipman:846): Gdk-CRITICAL **: gdk_window_thaw_toplevel_updates: assertion 'window->update_and_descendants_freeze_count > 0' failed

(pa-applet:862): Gdk-CRITICAL **: gdk_window_thaw_toplevel_updates: assertion 'window->update_and_descendants_freeze_count > 0' failed
compiz (decor) - Warn: No default decoration found, placement will not be correct
compiz (decor) - Warn: No default decoration found, placement will not be correct
compiz (decor) - Warn: No default decoration found, placement will not be correct
compiz (decor) - Warn: No default decoration found, placement will not be correct
compiz (decor) - Warn: No default decoration found, placement will not be correct
compiz (decor) - Warn: No default decoration found, placement will not be correct
compiz (decor) - Warn: No default decoration found, placement will not be correct
compiz (decor) - Warn: No default decoration found, placement will not be correct
compiz (decor) - Warn: No default decoration found, placement will not be correct
compiz (decor) - Warn: No default decoration found, placement will not be correct
compiz (decor) - Warn: No default decoration found, placement will not be correct
compiz (decor) - Warn: No default decoration found, placement will not be correct
compiz (decor) - Warn: No default decoration found, placement will not be correct
compiz (decor) - Warn: No default decoration found, placement will not be correct
compiz (decor) - Warn: No default decoration found, placement will not be correct
compiz (decor) - Warn: No default decoration found, placement will not be correct
compiz (decor) - Warn: No default decoration found, placement will not be correct
compiz (decor) - Warn: No default decoration found, placement will not be correct
compiz (decor) - Warn: No default decoration found, placement will not be correct
compiz (decor) - Warn: No default decoration found, placement will not be correct
compiz (decor) - Warn: No default decoration found, placement will not be correct

(nm-applet:861): libnotify-WARNING **: Failed to connect to proxy
Failed to show notification: Error calling StartServiceByName for org.freedesktop.Notifications: Timeout was reached

(nm-applet:861): nm-applet-WARNING **: Failed to show notification: Error calling StartServiceByName for org.freedesktop.Notifications: Timeout was reached

(nm-applet:861): Gdk-CRITICAL **: gdk_window_thaw_toplevel_updates: assertion 'window->update_and_descendants_freeze_count > 0' failed
Xlib:  extension "RANDR" missing on display ":0.0".
Xlib:  extension "RANDR" missing on display ":0.0".

(mousepad:1341): GtkSourceView-CRITICAL **: gtk_source_style_scheme_get_id: assertion 'GTK_IS_SOURCE_STYLE_SCHEME (scheme)' failed

(mousepad:1341): GLib-CRITICAL **: g_variant_new_string: assertion 'string != NULL' failed

(mousepad:1341): GtkSourceView-CRITICAL **: gtk_source_style_scheme_get_id: assertion 'GTK_IS_SOURCE_STYLE_SCHEME (scheme)' failed

(mousepad:1341): GLib-CRITICAL **: g_variant_new_string: assertion 'string != NULL' failed

(mousepad:1341): GtkSourceView-CRITICAL **: gtk_source_style_scheme_get_id: assertion 'GTK_IS_SOURCE_STYLE_SCHEME (scheme)' failed

Offline

#11 2017-08-25 02:04:11

ToZ
Administrator
From: Canada
Registered: 2011-06-02
Posts: 10,948

Re: XFCE notifications won't start automatically.

(nm-applet:861): libnotify-WARNING **: Failed to connect to proxy
Failed to show notification: Error calling StartServiceByName for org.freedesktop.Notifications: Timeout was reached

(nm-applet:861): nm-applet-WARNING **: Failed to show notification: Error calling StartServiceByName for org.freedesktop.Notifications: Timeout was reached

You have an issue with your dbus session setup. What does the following return?

env | grep -i dbus

Are you using "dbus-launch" anywhere in your start up files? Maybe search your system for that string.


Please remember to mark your thread [SOLVED] to make it easier for others to find
--- How To Ask For Help | FAQ | Developer Wiki  |  Community | Contribute ---

Offline

#12 2017-08-26 05:17:16

krgailey
Member
Registered: 2017-08-23
Posts: 13

Re: XFCE notifications won't start automatically.

Let me know if there is better command to search my system for 'dbus launch', but I found one and have the results below.

env | grep -i dbus
================================================
DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus


find / -xdev -type f -print0 | xargs -0 grep -H "dbus-launch"
================================================
/etc/xdg/xfce4/xinitrc:# Use dbus-launch if installed.
/etc/xdg/xfce4/xinitrc:  if which dbus-launch >/dev/null 2>&1; then
/etc/xdg/xfce4/xinitrc:    eval `dbus-launch --sh-syntax --exit-with-session`
/etc/xdg/xfce4/xinitrc:    echo "Could not find dbus-launch; Xfce will not work properly" >&2
/etc/skel/.xinitrc:	echo "dbus-launch ${dbus_args[*]}"
/etc/skel/.xprofile:# if which dbus-launch >/dev/null && test -z "$DBUS_SESSION_BUS_ADDRESS"; then
/etc/skel/.xprofile:#     eval "$(dbus-launch --sh-syntax --exit-with-session)"
/root/.xinitrc:	echo "dbus-launch ${dbus_args[*]}"
/root/.xprofile:# if which dbus-launch >/dev/null && test -z "$DBUS_SESSION_BUS_ADDRESS"; then
/root/.xprofile:#     eval "$(dbus-launch --sh-syntax --exit-with-session)"

/var/lib/pacman/local/dbus-1.10.18-1/files:usr/bin/dbus-launch
/var/lib/pacman/local/dbus-1.10.18-1/files:usr/share/man/man1/dbus-launch.1.gz
/usr/share/doc/HTML/en/kcontrol/khotkeys/index.docbook:<varlistentry id="shortcuts-action-dbus-launch-dbus-browser">
/usr/bin/dropbox:/usr/bin/dbus-launch /opt/dropbox/dropbox start

Binary file /var/cache/man/index.db matches
Binary file /var/log/journal/e05c08622c384c5f9b62c98301fd3a82/system@3643bcfc9bb84a249aec1e6cddd4672b-0000000000000001-0005467bd580b030.journal matches
Binary file /var/log/journal/e05c08622c384c5f9b62c98301fd3a82/system@3643bcfc9bb84a249aec1e6cddd4672b-0000000000025780-0005477d16bc4109.journal matches
Binary file /var/log/journal/e05c08622c384c5f9b62c98301fd3a82/system@3643bcfc9bb84a249aec1e6cddd4672b-0000000000036b06-00054a435e179704.journal matches
Binary file /var/log/journal/e05c08622c384c5f9b62c98301fd3a82/system@00054560f4879956-f69cc30ff123d809.journal~ matches
Binary file /var/log/journal/e05c08622c384c5f9b62c98301fd3a82/system@000545b70b8c2bae-6ef3e78784341615.journal~ matches
Binary file /var/log/journal/e05c08622c384c5f9b62c98301fd3a82/system@0005467bd57b8343-b051c4c84d687374.journal~ matches
Binary file /var/lib/mlocate/mlocate.db matches
Binary file /usr/bin/octopi-notifier matches
Binary file /usr/bin/xfce4-session matches
Binary file /usr/bin/octopi matches
Binary file /usr/bin/dbus-launch matches
Binary file /usr/bin/octopi-cachecleaner matches
Binary file /usr/lib32/libgio-2.0.so.0.5200.2 matches
Binary file /usr/lib32/libdbus-1.so.3.14.11 matches
Binary file /usr/lib/libdbus-1.so.3.14.11 matches
Binary file /usr/lib/libKF5KDELibs4Support.so.5.36.0 matches
Binary file /usr/lib/libKF5DBusAddons.so.5.36.0 matches
Binary file /usr/lib/libgio-2.0.so.0.5200.3 matches
Binary file /usr/lib/libkdeui.so.5.14.34 matches

Offline

#13 2017-08-26 12:19:49

ToZ
Administrator
From: Canada
Registered: 2011-06-02
Posts: 10,948

Re: XFCE notifications won't start automatically.

Hmmm. Is it only the network notifications that aren't working, or is it all notifications?


Please remember to mark your thread [SOLVED] to make it easier for others to find
--- How To Ask For Help | FAQ | Developer Wiki  |  Community | Contribute ---

Offline

#14 2017-08-26 19:35:20

krgailey
Member
Registered: 2017-08-23
Posts: 13

Re: XFCE notifications won't start automatically.

All notifications not working, I just noticed it with the network manager because task bar applets don't respond correctly.  When I lauch xfce4-notifyd in terminal other notifications work.  For instance when a file has completed downloading from qBittorent. Dbus is not loading it when needed and it definitely used to work.

Offline

#15 2017-08-26 23:45:35

ToZ
Administrator
From: Canada
Registered: 2011-06-02
Posts: 10,948

Re: XFCE notifications won't start automatically.

Ok.
Can you post back the results of the following commands:

pstree
find ~ -xdev -type f -print0 | xargs -0 grep -H "xfce4-notifyd"
loginctl session-status

And also, can you run the following command in one terminal window:

dbus-monitor --session interface='org.freedesktop.Notifications'

...and in another terminal window, run:

notify-send test test

...and then post back what was displayed in the first terminal window.


Please remember to mark your thread [SOLVED] to make it easier for others to find
--- How To Ask For Help | FAQ | Developer Wiki  |  Community | Contribute ---

Offline

#16 2017-08-27 05:25:24

krgailey
Member
Registered: 2017-08-23
Posts: 13

Re: XFCE notifications won't start automatically.

pstree results:
=======================================================

systemd─┬─ModemManager───2*[{ModemManager}]
        ├─NetworkManager─┬─dhclient
        │                └─2*[{NetworkManager}]
        ├─Thunar─┬─VirtualBox───36*[{VirtualBox}]
        │        └─2*[{Thunar}]
        ├─VBoxSVC───14*[{VBoxSVC}]
        ├─VBoxXPCOMIPCD
        ├─accounts-daemon───2*[{accounts-daemon}]
        ├─avahi-daemon───avahi-daemon
        ├─bluetoothd
        ├─colord───2*[{colord}]
        ├─compiz─┬─gtk-window-deco───3*[{gtk-window-deco}]
        │        └─{compiz}
        ├─crond
        ├─cupsd
        ├─2*[dbus-daemon]
        ├─dropbox───59*[{dropbox}]
        ├─kactivitymanage───5*[{kactivitymanage}]
        ├─lightdm─┬─Xorg───{Xorg}
        │         ├─lightdm─┬─sh───xfce4-session─┬─blueman-applet───3*[{blueman+
        │         │         │                    ├─cairo-dock───2*[{cairo-dock}+
        │         │         │                    ├─msm_notifier───2*[{msm_notif+
        │         │         │                    ├─nm-applet───3*[{nm-applet}]
        │         │         │                    ├─octopi-notifier───2*[{octopi+
        │         │         │                    ├─pa-applet───2*[{pa-applet}]
        │         │         │                    ├─pamac-tray───2*[{pamac-tray}+
        │         │         │                    ├─polkit-gnome-au───2*[{polkit+
        │         │         │                    ├─udiskie───2*[{udiskie}]
        │         │         │                    ├─xfce4-clipman───2*[{xfce4-cl+
        │         │         │                    └─2*[{xfce4-session}]
        │         │         └─2*[{lightdm}]
        │         └─2*[{lightdm}]
        ├─mount.ntfs
        ├─nmbd
        ├─ntpd───{ntpd}
        ├─pacmanhelper───{pacmanhelper}
        ├─polkitd───5*[{polkitd}]
        ├─rtkit-daemon───2*[{rtkit-daemon}]
        ├─smbd─┬─cleanupd
        │      ├─lpqd
        │      └─smbd-notifyd
        ├─ssh-agent
        ├─systemd─┬─(sd-pam)
        │         ├─at-spi-bus-laun─┬─dbus-daemon
        │         │                 └─3*[{at-spi-bus-laun}]
        │         ├─at-spi2-registr───2*[{at-spi2-registr}]
        │         ├─dbus-daemon
        │         ├─dconf-service───2*[{dconf-service}]
        │         ├─gconfd-2
        │         ├─gpg-agent
        │         ├─gvfs-afc-volume───3*[{gvfs-afc-volume}]
        │         ├─gvfs-gphoto2-vo───2*[{gvfs-gphoto2-vo}]
        │         ├─gvfs-mtp-volume───2*[{gvfs-mtp-volume}]
        │         ├─gvfs-udisks2-vo───2*[{gvfs-udisks2-vo}]
        │         ├─gvfsd───2*[{gvfsd}]
        │         ├─gvfsd-computer───2*[{gvfsd-computer}]
        │         ├─gvfsd-fuse───5*[{gvfsd-fuse}]
        │         ├─gvfsd-metadata───2*[{gvfsd-metadata}]
        │         ├─gvfsd-trash───2*[{gvfsd-trash}]
        │         ├─obexd
        │         ├─pulseaudio───2*[{pulseaudio}]
        │         └─xfconfd
        ├─systemd-journal
        ├─systemd-logind
        ├─systemd-udevd
        ├─teamviewerd───18*[{teamviewerd}]
        ├─udisksd───4*[{udisksd}]
        ├─upowerd───2*[{upowerd}]
        ├─wpa_supplicant
        ├─xfce4-panel─┬─firefox───61*[{firefox}]
        │             ├─panel-2-actions───2*[{panel-2-actions}]
        │             ├─panel-6-systray
        │             ├─panel-8-whisker───2*[{panel-8-whisker}]
        │             └─2*[{xfce4-panel}]
        ├─xfce4-power-man───2*[{xfce4-power-man}]
        ├─xfce4-terminal─┬─bash───pstree
        │                └─3*[{xfce4-terminal}]
        ├─xfdesktop───2*[{xfdesktop}]
        └─xfsettingsd───2*[{xfsettingsd}]

find ~ -xdev -type f -print0 | xargs -0 grep -H "xfce4-notifyd" results  (only removed bash history and text files I had notes in to save space):
=======================================================================================================

/home/krgailey/IDrive/user_profile/krgailey/Backup/Scheduled/LOGS/BACKUP Wed Mar 15 02:00:02 2017_SUCCESS:[Wed Mar 15 02:04:42 2017] [INCREMENTAL Backup] [SUCCESS] [/home/krgailey/.config/xfce4/xfconf/xfce-perchannel-xml/xfce4-notifyd.xml][674 bytes]
/home/krgailey/IDrive/user_profile/krgailey/Backup/Scheduled/LOGS/BACKUP Sun Feb 12 21:07:02 2017_ABORTED:[Mon Feb 13 18:52:29 2017] [FULL Backup] [SUCCESS] [/home/krgailey/.config/xfce4/xfconf/xfce-perchannel-xml/xfce4-notifyd.xml][625 bytes]
Binary file /home/krgailey/Downloads/2015-05-05-raspbian-wheezy.img matches
Binary file /home/krgailey/.mozilla/firefox/manjaro.default/places.sqlite matches
Binary file /home/krgailey/.mozilla/firefox/manjaro.default/formhistory.sqlite matches
/home/krgailey/.config/menus/xfce-applications.menu:			<Filename>xfce4-notifyd-config.desktop</Filename>
/home/krgailey/.config/xfce4/xfconf/xfce-perchannel-xml/xfce4-notifyd.xml:<channel name="xfce4-notifyd" version="1.0">
/home/krgailey/.config/xfce4/panel/whiskermenu-8.rc:recent=exo-terminal-emulator.desktop,org.kde.kwrite.desktop,ccsm.desktop,thunderbird.desktop,libreoffice-writer.desktop,virtualbox.desktop,qbittorrent.desktop,xfce4-notifyd-config.desktop,manjaro-settings-manager.desktop,compiz-gtk-decorator-theme.desktop
Binary file /home/krgailey/.thumbnails/normal/39e01b2806de402766d6e4e063ced15c.png matches
Binary file /home/krgailey/.local/share/kactivitymanagerd/resources/database-wal matches
Binary file /home/krgailey/.local/share/zeitgeist/activity.sqlite-wal matches
Binary file /home/krgailey/.cache/calibre/icon-theme-cache.pickle matches
Binary file /home/krgailey/.cache/mozilla/firefox/manjaro.default/cache2/entries/8976F8D5FE0F05F72F4A09E2BB502B94D6234E8B matches
Binary file /home/krgailey/.cache/mozilla/firefox/manjaro.default/cache2/entries/BAFA321A6BE2A37AFC6F0321EA47918824BBDE0D matches
Binary file /home/krgailey/.cache/mozilla/firefox/manjaro.default/cache2/entries/603AB526F8B2E86766DE690650DFFB6E31C420CA matches

dbus monitor results:
====================================================

As I loaded the dbus-monitor with the '--session interface' information it  immediately displayed the text below before the ^C/Break.  When I executed the 'notify-send test test', nothing new appeared in the monitoring terminal.

[ ~]$ dbus-monitor --session interface='org.freedesktop.Notifications'
signal time=1503805677.101881 sender=org.freedesktop.DBus -> destination=:1.1114 serial=2 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameAcquired
   string ":1.1114"
signal time=1503805677.101903 sender=org.freedesktop.DBus -> destination=:1.1114 serial=4 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameLost
   string ":1.1114"
^C

I loaded the dbus-monitor alone the first two lines appeared immediately as seen above.  I then saw some traffic when I executed the 'notify-send test test'.  I saw some more traffic at the end, when the prompt returned in the terminal where I issued the send test or when the timeout occurred.

[ ~]$ dbus-monitor
signal time=1503806233.395514 sender=org.freedesktop.DBus -> destination=:1.1127 serial=2 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameAcquired
   string ":1.1127"
signal time=1503806233.395535 sender=org.freedesktop.DBus -> destination=:1.1127 serial=4 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameLost
   string ":1.1127"
method call time=1503806263.903447 sender=:1.1128 -> destination=org.freedesktop.DBus serial=1 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=Hello
method return time=1503806263.903458 sender=org.freedesktop.DBus -> destination=:1.1128 serial=1 reply_serial=1
   string ":1.1128"
signal time=1503806263.903468 sender=org.freedesktop.DBus -> destination=(null destination) serial=2831 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameOwnerChanged
   string ":1.1128"
   string ""
   string ":1.1128"
signal time=1503806263.903477 sender=org.freedesktop.DBus -> destination=:1.1128 serial=2 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameAcquired
   string ":1.1128"
method call time=1503806263.903681 sender=:1.1128 -> destination=org.freedesktop.DBus serial=2 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=AddMatch
   string "type='signal',sender='org.freedesktop.Notifications',interface='org.freedesktop.Notifications',path='/org/freedesktop/Notifications'"
method return time=1503806263.903700 sender=org.freedesktop.DBus -> destination=:1.1128 serial=3 reply_serial=2
method call time=1503806263.903731 sender=:1.1128 -> destination=org.freedesktop.DBus serial=3 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=AddMatch
   string "type='signal',sender='org.freedesktop.DBus',interface='org.freedesktop.DBus',member='NameOwnerChanged',path='/org/freedesktop/DBus',arg0='org.freedesktop.Notifications'"
method return time=1503806263.903747 sender=org.freedesktop.DBus -> destination=:1.1128 serial=4 reply_serial=3
method call time=1503806263.903946 sender=:1.1128 -> destination=org.freedesktop.DBus serial=4 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=StartServiceByName
   string "org.freedesktop.Notifications"
   uint32 0
method call time=1503806263.943712 sender=:1.1129 -> destination=org.freedesktop.DBus serial=1 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=Hello
method return time=1503806263.943728 sender=org.freedesktop.DBus -> destination=:1.1129 serial=1 reply_serial=1
   string ":1.1129"
signal time=1503806263.943735 sender=org.freedesktop.DBus -> destination=(null destination) serial=2832 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameOwnerChanged
   string ":1.1129"
   string ""
   string ":1.1129"
signal time=1503806263.943741 sender=org.freedesktop.DBus -> destination=:1.1129 serial=2 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameAcquired
   string ":1.1129"
method call time=1503806263.943913 sender=:1.1129 -> destination=org.freedesktop.DBus serial=2 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameHasOwner
   string "org.freedesktop.Notifications"
method return time=1503806263.943924 sender=org.freedesktop.DBus -> destination=:1.1129 serial=3 reply_serial=2
   boolean false
method call time=1503806263.944048 sender=:1.1129 -> destination=org.freedesktop.DBus serial=3 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=AddMatch
   string "type='signal',sender='org.freedesktop.DBus',interface='org.freedesktop.DBus',member='NameOwnerChanged',arg0='org.freedesktop.Notifications',arg1=''"
signal time=1503806288.923946 sender=org.freedesktop.DBus -> destination=:1.1128 serial=5 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameLost
   string ":1.1128"
signal time=1503806288.923965 sender=org.freedesktop.DBus -> destination=(null destination) serial=2833 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameOwnerChanged
   string ":1.1128"
   string ":1.1128"
   string ""
method call time=1503806288.924334 sender=:1.1130 -> destination=org.freedesktop.DBus serial=1 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=Hello
method return time=1503806288.924345 sender=org.freedesktop.DBus -> destination=:1.1130 serial=1 reply_serial=1
   string ":1.1130"
signal time=1503806288.924350 sender=org.freedesktop.DBus -> destination=(null destination) serial=2834 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameOwnerChanged
   string ":1.1130"
   string ""
   string ":1.1130"
signal time=1503806288.924358 sender=org.freedesktop.DBus -> destination=:1.1130 serial=2 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameAcquired
   string ":1.1130"
method call time=1503806288.924538 sender=:1.1130 -> destination=org.freedesktop.DBus serial=2 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=AddMatch
   string "type='signal',sender='org.freedesktop.Notifications',interface='org.freedesktop.Notifications',path='/org/freedesktop/Notifications'"
method return time=1503806288.924547 sender=org.freedesktop.DBus -> destination=:1.1130 serial=3 reply_serial=2
method call time=1503806288.924599 sender=:1.1130 -> destination=org.freedesktop.DBus serial=3 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=AddMatch
   string "type='signal',sender='org.freedesktop.DBus',interface='org.freedesktop.DBus',member='NameOwnerChanged',path='/org/freedesktop/DBus',arg0='org.freedesktop.Notifications'"
method return time=1503806288.924607 sender=org.freedesktop.DBus -> destination=:1.1130 serial=4 reply_serial=3
method call time=1503806288.924610 sender=:1.1130 -> destination=org.freedesktop.DBus serial=4 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=StartServiceByName
   string "org.freedesktop.Notifications"
   uint32 0
signal time=1503806313.949856 sender=org.freedesktop.DBus -> destination=:1.1130 serial=6 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameLost
   string ":1.1130"
signal time=1503806313.949875 sender=org.freedesktop.DBus -> destination=(null destination) serial=2835 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameOwnerChanged
   string ":1.1130"
   string ":1.1130"
   string ""
method call time=1503806324.116776 sender=:1.1129 -> destination=org.freedesktop.DBus serial=4 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=RemoveMatch
   string "type='signal',sender='org.freedesktop.DBus',interface='org.freedesktop.DBus',member='NameOwnerChanged',arg0='org.freedesktop.Notifications',arg1=''"
method call time=1503806324.116813 sender=:1.1129 -> destination=org.freedesktop.DBus serial=5 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=RemoveMatch
   string "type='signal',sender='org.freedesktop.DBus',interface='org.freedesktop.DBus',member='NameOwnerChanged',arg0='org.freedesktop.DBus'"
error time=1503806324.116820 sender=org.freedesktop.DBus -> destination=:1.1129 error_name=org.freedesktop.DBus.Error.MatchRuleNotFound reply_serial=5
   string "The given match rule wasn't found and can't be removed"
signal time=1503806324.116889 sender=org.freedesktop.DBus -> destination=:1.1129 serial=7 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameLost
   string ":1.1129"
signal time=1503806324.116898 sender=org.freedesktop.DBus -> destination=(null destination) serial=2836 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameOwnerChanged
   string ":1.1129"
   string ":1.1129"
   string ""

Offline

#17 2017-08-27 13:34:55

ToZ
Administrator
From: Canada
Registered: 2011-06-02
Posts: 10,948

Re: XFCE notifications won't start automatically.

You forgot to post the results of:

loginctl session-status

And can you also post back the status of the xfce4-notifyd service:

systemctl --user status xfce4-notifyd

Please remember to mark your thread [SOLVED] to make it easier for others to find
--- How To Ask For Help | FAQ | Developer Wiki  |  Community | Contribute ---

Offline

#18 2017-08-27 18:55:11

krgailey
Member
Registered: 2017-08-23
Posts: 13

Re: XFCE notifications won't start automatically.

Sorry I overlooked that one.  Here are the other two things you asked for.  Since I was seeing lightdm listed below, I threw in a status on it, since I disabled it earlier and never reenabled it.  I got some interesting messages about two services allocated to the same bus below the lightdm status, may mean nothing, but just in case.

$ loginctl session-status results:

c1 - krgailey (1000)
           Since: Thu 2017-08-24 20:15:22 CDT; 2 days ago
          Leader: 767 (lightdm)
            Seat: seat0; vc7
         Display: :0
         Service: lightdm-autologin; type x11; class user
         Desktop: xfce
           State: active
            Unit: session-c1.scope
                  ├─  767 lightdm --session-child 13 16
                  ├─  795 /bin/sh /etc/xdg/xfce4/xinitrc -- /etc/X11/xinit/xserv
                  ├─  816 xfce4-session
            Unit: session-c1.scope
                  ├─  767 lightdm --session-child 13 16
                  ├─  795 /bin/sh /etc/xdg/xfce4/xinitrc -- /etc/X11/xinit/xserv
                  ├─  816 xfce4-session
                  ├─  826 /usr/bin/ssh-agent -s
                  ├─  831 compiz
                  ├─  835 xfce4-panel
                  ├─  837 Thunar --daemon
                  ├─  839 xfdesktop
                  ├─  840 cairo-dock
                  ├─  841 xfsettingsd
                  ├─  842 /usr/bin/python /usr/bin/udiskie
                  ├─  846 xfce4-clipman
                  ├─  847 msm_notifier
                  ├─  850 octopi-notifier
                  ├─  854 /usr/bin/dbus-daemon --fork --print-pid 4 --print-addr
                  ├─  858 python /usr/bin/blueman-applet
                  ├─  861 nm-applet
                  ├─  862 pa-applet
                  ├─  863 /usr/lib/polkit-gnome/polkit-gnome-authentication-agen
                  ├─  864 pamac-tray
                  ├─  870 /usr/lib/xfce4/panel/wrapper-1.0 /usr/lib/xfce4/panel/
                  ├─  894 xfce4-power-manager
                  ├─  926 /usr/lib/xfce4/panel/wrapper-1.0 /usr/lib/xfce4/panel/
                  ├─  930 /usr/lib/xfce4/panel/wrapper-1.0 /usr/lib/xfce4/panel/
                  ├─ 1144 /home/krgailey/.dropbox-dist/dropbox-lnx.x86_64-33.4.2
                  ├─ 1225 /usr/bin/gtk-window-decorator
                  ├─ 1656 /usr/bin/kactivitymanagerd start-daemon
                  ├─21575 /usr/lib/virtualbox/VirtualBox --comment Windows 7 Pro
                  ├─21580 /usr/lib/virtualbox/VBoxXPCOMIPCD
                  ├─21585 /usr/lib/virtualbox/VBoxSVC --auto-shutdown
                  ├─23345 /usr/lib/firefox/firefox
                  ├─30932 /usr/bin/xfce4-terminal
                  ├─30936 bash
                  ├─30942 loginctl session-status
                  └─30943 loginctl session-status
                  ├─  850 octopi-notifier
                  ├─  854 /usr/bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session
                  ├─  858 python /usr/bin/blueman-applet
                  ├─  861 nm-applet
                  ├─  862 pa-applet
                  ├─  863 /usr/lib/polkit-gnome/polkit-gnome-authentication-agent-1
                  ├─  864 pamac-tray
                  ├─  870 /usr/lib/xfce4/panel/wrapper-1.0 /usr/lib/xfce4/panel/plugins/libwhiskermenu.so 8 12582949 whiskermenu Whisker Menu Show a menu to easily access installed applicati
                  ├─  894 xfce4-power-manager
                  ├─  926 /usr/lib/xfce4/panel/wrapper-1.0 /usr/lib/xfce4/panel/plugins/libsystray.so 6 12582950 systray Notification Area Area where notification icons appear
                  ├─  930 /usr/lib/xfce4/panel/wrapper-1.0 /usr/lib/xfce4/panel/plugins/libactions.so 2 12582951 actions Action Buttons Log out, lock or other system actions
                  ├─ 1144 /home/krgailey/.dropbox-dist/dropbox-lnx.x86_64-33.4.23/dropbox /newerversion start
                  ├─ 1225 /usr/bin/gtk-window-decorator
                  ├─ 1656 /usr/bin/kactivitymanagerd start-daemon
                  ├─21575 /usr/lib/virtualbox/VirtualBox --comment Windows 7 Pro --startvm 1832b2e7-06a5-4db4-b04d-6ebe2b0e5d6b
                  ├─21580 /usr/lib/virtualbox/VBoxXPCOMIPCD
                  ├─21585 /usr/lib/virtualbox/VBoxSVC --auto-shutdown
                  ├─23345 /usr/lib/firefox/firefox
                  ├─30932 /usr/bin/xfce4-terminal
                  ├─30936 bash
                  ├─30942 loginctl session-status
                  └─30943 loginctl session-status

Aug 26 22:42:30 manjaro-xfce kwrite[23456]: qt.svg: link SVGCleanerId_0 hasn't been detected!
Aug 26 22:45:32 manjaro-xfce sudo[23483]: krgailey : TTY=pts/0 ; PWD=/home/krgailey ; USER=root ; COMMAND=/usr/bin/su
Aug 26 22:45:32 manjaro-xfce sudo[23483]: pam_unix(sudo:session): session opened for user root by (uid=0)
Aug 26 22:45:32 manjaro-xfce su[23485]: (to root) root on pts/0
Aug 26 22:45:32 manjaro-xfce su[23485]: pam_unix(su:session): session opened for user root by (uid=0)
Aug 26 22:46:09 manjaro-xfce su[23485]: pam_unix(su:session): session closed for user root
Aug 26 22:46:09 manjaro-xfce sudo[23483]: pam_unix(sudo:session): session closed for user root
Aug 27 00:27:42 manjaro-xfce kwrite[23456]: qt.svg: link SVGCleanerId_0 hasn't been detected!
Aug 27 00:28:09 manjaro-xfce kwrite[23456]: org.kde.knotifications: Audio notification requested, but sound file from notifyrc file was not found, aborting audio notification
Aug 27 08:16:50 manjaro-xfce msm_notifier[847]: "qt5-translations"

$ systemctl --user status xfce4-notifyd results:

● xfce4-notifyd.service - XFCE notifications service
   Loaded: loaded (/usr/lib/systemd/user/xfce4-notifyd.service; static; vendor preset: enabled)
   Active: inactive (dead)

$ systemctl status lightdm

● lightdm.service - Light Display Manager
   Loaded: error (Reason: File exists)
   Active: inactive (dead)
     Docs: man:lightdm(1)

Aug 26 14:37:46 manjaro-xfce systemd[1]: lightdm.service: Two services allocated for the same bus name org.freedesktop.DisplayManager, refusing operation.
Aug 27 13:48:30 manjaro-xfce systemd[1]: lightdm.service: Two services allocated for the same bus name org.freedesktop.DisplayManager, refusing operation.

Last edited by krgailey (2017-08-27 18:57:55)

Offline

#19 2017-08-27 20:45:33

ToZ
Administrator
From: Canada
Registered: 2011-06-02
Posts: 10,948

Re: XFCE notifications won't start automatically.

krgailey wrote:

$ systemctl --user status xfce4-notifyd results:

● xfce4-notifyd.service - XFCE notifications service
   Loaded: loaded (/usr/lib/systemd/user/xfce4-notifyd.service; static; vendor preset: enabled)
   Active: inactive (dead)

This is not right. The service should be active and running. Here is mine:

$ systemctl --user status xfce4-notifyd
● xfce4-notifyd.service - XFCE notifications service
   Loaded: loaded (/usr/lib/systemd/user/xfce4-notifyd.service; static; vendor p
   Active: active (running) since Wed 2017-08-23 06:18:56 EDT; 4 days ago
 Main PID: 543 (xfce4-notifyd)
   CGroup: /user.slice/user-1000.slice/user@1000.service/xfce4-notifyd.service
           └─543 /usr/lib/xfce4/notifyd/xfce4-notifyd

Aug 23 06:18:56 archie systemd[385]: Starting XFCE notifications service...
Aug 23 06:18:56 archie systemd[385]: Started XFCE notifications service.

Try starting the service:

systemctl --user start xfce4-notifyd.service

...and check the status:

systemctl --user status xfce4-notifyd.service

..if it's active and running, then does:

notify-send test test

...work?

Can you also post back:

sudo updatedb && locate xfce4-notifyd.service

EDIT: A few more:

systemctl --user -t target

...and:

systemctl --user list-dependencies default.target

...and are they all green? (especially dbus.socket)

And finally:

cat /usr/share/dbus-1/services/org.xfce.xfce4-notifyd.Notifications.service

Please remember to mark your thread [SOLVED] to make it easier for others to find
--- How To Ask For Help | FAQ | Developer Wiki  |  Community | Contribute ---

Offline

#20 2017-08-27 22:30:51

krgailey
Member
Registered: 2017-08-23
Posts: 13

Re: XFCE notifications won't start automatically.

$ systemctl --user start xfce4-notifyd.service
[krgailey@manjaro-xfce ~]$ systemctl --user status xfce4-notifyd.service
● xfce4-notifyd.service - XFCE notifications service
   Loaded: loaded (/usr/lib/systemd/user/xfce4-notifyd.service; static; vendor p
   Active: active (running) since Sun 2017-08-27 16:30:30 CDT; 31s ago
 Main PID: 32003 (xfce4-notifyd)
   CGroup: /user.slice/user-1000.slice/user@1000.service/xfce4-notifyd.service
           └─32003 /usr/lib/xfce4/notifyd/xfce4-notifyd

Aug 27 16:30:30 manjaro-xfce systemd[778]: Starting XFCE notifications service..
Aug 27 16:30:30 manjaro-xfce systemd[778]: Started XFCE notifications service.

[krgailey@manjaro-xfce ~]$ notify-send test test

It worked!

I had tried this in the past, but did not include the " --user " in the command which when not used returns "Unit xfce4-notifyd.service could not be found."  Thinking dbus was supposed to load it, I didn't pursue it further.  Got my hopes up, but I waited about 30 minutes and tried to get a notification again.  It didn't work.  See below service had returned to "inactive (dead).

$ systemctl --user status xfce4-notifyd.service
● xfce4-notifyd.service - XFCE notifications service
   Loaded: loaded (/usr/lib/systemd/user/xfce4-notifyd.service; static; vendor p
   Active: inactive (dead)

Aug 27 16:30:30 manjaro-xfce systemd[778]: Starting XFCE notifications service..
Aug 27 16:30:30 manjaro-xfce systemd[778]: Started XFCE notifications service.

Here are the additional items you requested.

$ sudo updatedb && locate xfce4-notifyd.service
[sudo] password for krgailey: 
/usr/lib/systemd/user/xfce4-notifyd.service
$ systemctl --user -t target
UNIT           LOAD   ACTIVE SUB    DESCRIPTION                                
basic.target   loaded active active Basic System                               
default.target loaded active active Default                                    
paths.target   loaded active active Paths                                      
sockets.target loaded active active Sockets                                    
timers.target  loaded active active Timers                                     

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.

5 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.

The following were all green except for the xdg-user-dirs-update.service, which was white.

$ systemctl --user list-dependencies default.target
default.target
● ├─xdg-user-dirs-update.service
● └─basic.target
●   ├─paths.target
●   ├─sockets.target
●   │ ├─dbus.socket
●   │ ├─dirmngr.socket
●   │ ├─gpg-agent-browser.socket
●   │ ├─gpg-agent-extra.socket
●   │ ├─gpg-agent-ssh.socket
●   │ ├─gpg-agent.socket
●   │ └─pulseaudio.socket
●   └─timers.target


$ cat /usr/share/dbus-1/services/org.xfce.xfce4-notifyd.Notifications.service
[D-BUS Service]
Name=org.freedesktop.Notifications
Exec=/usr/lib/xfce4/notifyd/xfce4-notifyd
SystemdService=xfce4-notifyd.service

Offline

#21 2017-08-28 00:58:06

ToZ
Administrator
From: Canada
Registered: 2011-06-02
Posts: 10,948

Re: XFCE notifications won't start automatically.

We're getting closer...

xfce4-notifyd should be started (and restarted as needed) via dbus but that is not happening on your system. Is there anything in your journal:

journalctl -b --user -u xfce4-notifyd
journalctl -b --user -u dbus.service | grep notifyd

EDIT: Can you also post the contents of /var/log/lightdm/lightdm.log as well as the results of:

cat /etc/lightdm/Xsession | grep xinitrc

...and

ls /etc/X11/xinit/xinitrc.d

Please remember to mark your thread [SOLVED] to make it easier for others to find
--- How To Ask For Help | FAQ | Developer Wiki  |  Community | Contribute ---

Offline

#22 2017-08-28 03:15:37

krgailey
Member
Registered: 2017-08-23
Posts: 13

Re: XFCE notifications won't start automatically.

It looks like the only thing in the journal is where I've started the service today.

journalctl -b --user -u xfce4-notifyd

-- Logs begin at Mon 2017-01-02 01:33:56 CST, end at Sun 2017-08-27 20:16:50 CDT. --
Aug 27 16:30:30 manjaro-xfce systemd[778]: Starting XFCE notifications service...
Aug 27 16:30:30 manjaro-xfce systemd[778]: Started XFCE notifications service.
Aug 27 17:23:01 manjaro-xfce systemd[778]: Starting XFCE notifications service...
Aug 27 17:23:01 manjaro-xfce systemd[778]: Started XFCE notifications service.
Aug 27 17:42:25 manjaro-xfce systemd[778]: Starting XFCE notifications service...
Aug 27 17:42:25 manjaro-xfce systemd[778]: Started XFCE notifications service.
Aug 27 17:55:57 manjaro-xfce systemd[778]: Starting XFCE notifications service...
Aug 27 17:55:57 manjaro-xfce systemd[778]: Started XFCE notifications service.
Aug 27 18:12:01 manjaro-xfce systemd[778]: Starting XFCE notifications service...
Aug 27 18:12:01 manjaro-xfce systemd[778]: Started XFCE notifications service.

Nothing returned for dbus.service

$ journalctl -b --user -u dbus.service | grep notifyd
$
$ cat /etc/lightdm/Xsession | grep xinitrc
# Run all system xinitrc shell scripts
xinitdir="/etc/X11/xinit/xinitrc.d"

$ ls /etc/X11/xinit/xinitrc.d
40-libcanberra-gtk-module.sh  50-systemd-user.sh

It is strange your xfce4-notifyd.service has been running for 4 days.  Mine only stays running for 10 minutes.

Thank you for your help!

Last edited by krgailey (2017-08-28 03:24:11)

Offline

#23 2017-08-28 23:07:18

ToZ
Administrator
From: Canada
Registered: 2011-06-02
Posts: 10,948

Re: XFCE notifications won't start automatically.

It is strange your xfce4-notifyd.service has been running for 4 days.  Mine only stays running for 10 minutes.

Sorry about that. I posted back on my system that is running the latest git version of Xfce and xfce4-notifyd has had a recent change where it no longer stops after 10 minutes but runs continously now. I get the same result as yours from both my normal Arch install and from a Manjaro live cd that I just downloaded. In these cases, xfce4-notifyd starts when called.

I'm not sure I know why dbus is not starting that service. Everything looks good in what you posted above, except xfce4-notifyd does not start when called.

Can you try re-installing dbus and xfce4-notifyd?

Have you made any manual edits or overrides to the default systemd service files?


Please remember to mark your thread [SOLVED] to make it easier for others to find
--- How To Ask For Help | FAQ | Developer Wiki  |  Community | Contribute ---

Offline

#24 2017-08-28 23:49:48

krgailey
Member
Registered: 2017-08-23
Posts: 13

Re: XFCE notifications won't start automatically.

Interesting, I'd be happy if I could have mine run all the time.  I wonder if the change to have it run all the time is to avoid issues like mine.

I have already reinstalled dbus and xfce4-notifyd, probably twice.

I haven't made any manual edits, except maybe some config files trying to troubleshoot the issue at hand.

I think I'll eventually back up and start over, if I get to a point I can't stand loading it manually when needed.

Thank you for all of your assistance and for checking everything out!

Offline

#25 2017-08-29 00:36:59

ToZ
Administrator
From: Canada
Registered: 2011-06-02
Posts: 10,948

Re: XFCE notifications won't start automatically.

krgailey wrote:

Interesting, I'd be happy if I could have mine run all the time.  I wonder if the change to have it run all the time is to avoid issues like mine.

If I recall from the commit, no one could remember why it was programmed to do that, so it was removed.

I have already reinstalled dbus and xfce4-notifyd, probably twice.

I haven't made any manual edits, except maybe some config files trying to troubleshoot the issue at hand.

I think I'll eventually back up and start over, if I get to a point I can't stand loading it manually when needed.

Thank you for all of your assistance and for checking everything out!

Sorry I couldn't find the issue. It's a real head scratcher.


Please remember to mark your thread [SOLVED] to make it easier for others to find
--- How To Ask For Help | FAQ | Developer Wiki  |  Community | Contribute ---

Offline

Board footer

Powered by FluxBB