Can't Start Synergy server before login +XFCE4 +lightdm

Everything about X, Gnome, KDE, ... and everything running on it

Can't Start Synergy server before login +XFCE4 +lightdm

Postby Monkadelicd » 2013-09-14 05:41

I am having issues with one of my computers.
I have installed Debian 7.1.0 with XFCE on three old PCs. I had no issues there. I got my software setup and everything seems to be working fine.

Once I restart one of them I get an error message before the login screen is displayed. It also takes an unusually long time to show anything on the screen
The error says "System tray is unavailable, quitting" and there is an "OK" button. Once I click the OK button I am taken to the login screen.

After I login the same thing happens when the desktop loads. There is an unusually long pause with nothing displayed except the desktop background and then the same error box pops up. I click OK and the desktop quickly loads like it normally would.

I've looked in all the logs I could find. The only thing I've found that might be a reference to this is in /var/log/lightdm/lightdm.log. The line says Session XXXX got 1 message(s) from PAM and the immediatly following line says Prompt greeter with 1 message(s). But this only shows up in the greeter section not later on after the greeter quits and I have no idea what PAM is.

I do have a simple Greeter script to start Synergy as well as a Session script to start it again once I'm logged in. All it does is kill any currently running Synergy process before starting it again. There is a "Sleep 1" line between killing and starting Synergy.

I have found in some forum discussions that this error can be because something is trying to start before the System Tray has started and is unable to place itself on the system tray.

This may be an issue with Synergy because it started after I have LightDM run the Greeter script and Session script to start Synergy.

This problem is with a script to start the Synergy server before user login. The Synergy client starts fine on similarly configured PCs (Same software installed, a different PC with the same software config had the same problem with Synergy server) Posts below will describe how I'm starting Synergy.

How can I find out what's giving the error/warning popups?

If anyone can help me out here, please do.

* edited for more clarity in title *
Last edited by Monkadelicd on 2013-09-19 16:14, edited 3 times in total.
Monkadelicd
 
Posts: 23
Joined: 2008-08-06 00:46
Location: DFW, Texas, USA

Re: System tray is unavailable, quitting message

Postby bw123 » 2013-09-14 14:18

don't know if it helps, but pam is an authentication scheme, does your script use any user names that don't exist, or user names that try to access something they shouldn't? you said you checked, but no problems in /var/log/auth.log?

http://www.rjsystems.nl/en/2100-pam-debian.php
wheezy/KDE4, GNU/Linux 3.14-0.bpo.1-amd64
User avatar
bw123
 
Posts: 1839
Joined: 2011-05-09 06:02
Location: TN_USA

Re: System tray is unavailable, quitting message

Postby Monkadelicd » 2013-09-14 21:35

*edited out because I spoke too soon*
Last edited by Monkadelicd on 2013-09-16 02:02, edited 1 time in total.
Monkadelicd
 
Posts: 23
Joined: 2008-08-06 00:46
Location: DFW, Texas, USA

Re: System tray is unavailable, quitting message

Postby Monkadelicd » 2013-09-15 02:18

I spoke too soon. Upon restarting, I had the same issue. I think the issue has something to do with the Synergy server. I've got a script running at the lightdm greeter and the lightdm session so I have synergy at the login screen and right after logging in.

This must be an issue with lightdm or XFCE because I didn't have this issue running SolusOS which uses gdm and Gnome (I think).

To sum up my issue:
When I have Synergy automatically started before logging in with XFCE4 I get a message box saying "System tray is unavailable, quitting"
I have a greeter script and a session script pointed to from /etc/lightdm/lightdm.conf. This worked fine in SolusOS but not in Debian 7.1.0 w/ XFCE4.

My script is as follows (same script for greeter and session):
Code: Select all
#!/bin/sh

#
# This script runs before logging in
#

# kill any running synergy server, wait, start a new server
/usr/bin/killall -9 synergy
sleep 1
/usr/bin/synergy

exit 0

Monkadelicd
 
Posts: 23
Joined: 2008-08-06 00:46
Location: DFW, Texas, USA

Re: System tray is unavailable, quitting message

Postby Monkadelicd » 2013-09-15 14:53

I commented out all commands in the greeter script and the session script just to see what would happen.

Turns out if I don't do anything with Synergy in the scripts I boot with no messages and quickly.

Is it possible that killall is hanging up? Or is this a Synergy thing?
Monkadelicd
 
Posts: 23
Joined: 2008-08-06 00:46
Location: DFW, Texas, USA

Re: System tray is unavailable, quitting message

Postby confuseling » 2013-09-15 15:40

What happens if you sleep for longer, 10 seconds or so?
The Forum's search box is terrible. Use site specific search, e.g.
https://www.google.com/search?q=site%3A ... terms+here
confuseling
 
Posts: 1997
Joined: 2009-10-21 01:03

Re: System tray is unavailable, quitting message

Postby Monkadelicd » 2013-09-15 19:29

I tried increasing sleep to 3 with no effect.
I tried 5 with no effect.
I tried 7 with no effect.
I got up to 10 with no effect. I am posting some logs below to see if they have any clues. I'm not sure what information is useful in them.

syslog for bootup with sleep 7 in script:
Code: Select all
Sep 15 14:15:36 HP-LAB avahi-daemon[2615]: Successfully called chroot().
Sep 15 14:15:36 HP-LAB avahi-daemon[2615]: Successfully dropped remaining capabilities.
Sep 15 14:15:36 HP-LAB avahi-daemon[2615]: Loading service file /services/udisks.service.
Sep 15 14:15:36 HP-LAB kernel: [   13.554860] Bluetooth: RFCOMM TTY layer initialized
Sep 15 14:15:36 HP-LAB kernel: [   13.554875] Bluetooth: RFCOMM socket layer initialized
Sep 15 14:15:36 HP-LAB kernel: [   13.554882] Bluetooth: RFCOMM ver 1.11
Sep 15 14:15:36 HP-LAB avahi-daemon[2615]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::21a:4bff:fe48:c6cf.
Sep 15 14:15:36 HP-LAB avahi-daemon[2615]: New relevant interface eth0.IPv6 for mDNS.
Sep 15 14:15:36 HP-LAB avahi-daemon[2615]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.1.20.
Sep 15 14:15:36 HP-LAB avahi-daemon[2615]: New relevant interface eth0.IPv4 for mDNS.
Sep 15 14:15:36 HP-LAB avahi-daemon[2615]: Network interface enumeration completed.
Sep 15 14:15:36 HP-LAB avahi-daemon[2615]: Registering new address record for fe80::21a:4bff:fe48:c6cf on eth0.*.
Sep 15 14:15:36 HP-LAB avahi-daemon[2615]: Registering new address record for 192.168.1.20 on eth0.IPv4.
Sep 15 14:15:36 HP-LAB avahi-daemon[2615]: Registering HINFO record with values 'I686'/'LINUX'.
Sep 15 14:15:36 HP-LAB bluetoothd[2609]: Failed to init alert plugin
Sep 15 14:15:36 HP-LAB bluetoothd[2609]: Failed to init time plugin
Sep 15 14:15:37 HP-LAB kernel: [   13.605520] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Sep 15 14:15:37 HP-LAB kernel: [   13.605530] Bluetooth: BNEP filters: protocol multicast
Sep 15 14:15:37 HP-LAB bluetoothd[2609]: Failed to init gatt_example plugin
Sep 15 14:15:37 HP-LAB kernel: [   13.848340] lp0: using parport0 (interrupt-driven).
Sep 15 14:15:37 HP-LAB kernel: [   13.902133] ppdev: user-space parallel port driver
Sep 15 14:15:37 HP-LAB udev-configure-printer: add /module/lp
Sep 15 14:15:37 HP-LAB udev-configure-printer: add /devices/pnp0/00:07/printer/lp0
Sep 15 14:15:37 HP-LAB udev-configure-printer: Failed to get parent
Sep 15 14:15:37 HP-LAB udev-configure-printer: Failed to get parent
Sep 15 14:15:37 HP-LAB avahi-daemon[2615]: Server startup complete. Host name is HP-LAB.local. Local service cookie is 546314975.
Sep 15 14:15:38 HP-LAB NetworkManager[2719]: <info> NetworkManager (version 0.9.4.0) is starting...
Sep 15 14:15:38 HP-LAB NetworkManager[2719]: <info> Read config file /etc/NetworkManager/NetworkManager.conf
Sep 15 14:15:38 HP-LAB dbus[2573]: [system] Activating service name='org.freedesktop.PolicyKit1' (using servicehelper)
Sep 15 14:15:38 HP-LAB polkitd[2761]: started daemon version 0.105 using authority implementation `local' version `0.105'
Sep 15 14:15:38 HP-LAB dbus[2573]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
Sep 15 14:15:38 HP-LAB avahi-daemon[2615]: Service "HP-LAB" (/services/udisks.service) successfully established.
Sep 15 14:15:38 HP-LAB NetworkManager[2719]:    SCPlugin-Ifupdown: init!
Sep 15 14:15:38 HP-LAB NetworkManager[2719]:    SCPlugin-Ifupdown: update_system_hostname
Sep 15 14:15:38 HP-LAB NetworkManager[2719]:    SCPluginIfupdown: guessed connection type (eth0) = 802-3-ethernet
Sep 15 14:15:38 HP-LAB NetworkManager[2719]:    SCPlugin-Ifupdown: update_connection_setting_from_if_block: name:eth0, type:802-3-ethernet, id:Ifupdown (eth0), uuid: 681b428f-beaf-8932-dce4-687ed5bae28e
Sep 15 14:15:38 HP-LAB NetworkManager[2719]:    SCPlugin-Ifupdown: addresses count: 1
Sep 15 14:15:38 HP-LAB NetworkManager[2719]:    SCPlugin-Ifupdown: No dns-nameserver configured in /etc/network/interfaces
Sep 15 14:15:38 HP-LAB NetworkManager[2719]:    SCPlugin-Ifupdown: adding eth0 to iface_connections
Sep 15 14:15:38 HP-LAB NetworkManager[2719]:    SCPlugin-Ifupdown: adding iface eth0 to well_known_interfaces
Sep 15 14:15:38 HP-LAB NetworkManager[2719]:    SCPlugin-Ifupdown: autoconnect
Sep 15 14:15:38 HP-LAB NetworkManager[2719]:    SCPluginIfupdown: management mode: unmanaged
Sep 15 14:15:38 HP-LAB NetworkManager[2719]:    SCPlugin-Ifupdown: devices added (path: /sys/devices/pci0000:00/0000:00:1c.1/0000:3f:00.0/net/eth0, iface: eth0)
Sep 15 14:15:38 HP-LAB NetworkManager[2719]:    SCPluginIfupdown: locking wired connection setting
Sep 15 14:15:38 HP-LAB NetworkManager[2719]:    SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/lo, iface: lo)
Sep 15 14:15:38 HP-LAB NetworkManager[2719]:    SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/lo, iface: lo): no ifupdown configuration found.
Sep 15 14:15:38 HP-LAB NetworkManager[2719]:    SCPlugin-Ifupdown: end _init.
Sep 15 14:15:38 HP-LAB NetworkManager[2719]: <info> Loaded plugin ifupdown: (C) 2008 Canonical Ltd.  To report bugs please use the NetworkManager mailing list.
Sep 15 14:15:38 HP-LAB NetworkManager[2719]: <info> Loaded plugin keyfile: (c) 2007 - 2010 Red Hat, Inc.  To report bugs please use the NetworkManager mailing list.
Sep 15 14:15:38 HP-LAB NetworkManager[2719]:    Ifupdown: get unmanaged devices count: 1
Sep 15 14:15:38 HP-LAB NetworkManager[2719]:    SCPlugin-Ifupdown: (154332344) ... get_connections.
Sep 15 14:15:38 HP-LAB NetworkManager[2719]:    SCPlugin-Ifupdown: (154332344) ... get_connections (managed=false): return empty list.
Sep 15 14:15:38 HP-LAB NetworkManager[2719]:    Ifupdown: get unmanaged devices count: 1
Sep 15 14:15:38 HP-LAB NetworkManager[2719]: <info> trying to start the modem manager...
Sep 15 14:15:38 HP-LAB dbus[2573]: [system] Activating service name='org.freedesktop.ModemManager' (using servicehelper)
Sep 15 14:15:38 HP-LAB NetworkManager[2719]: <info> monitoring kernel firmware directory '/lib/firmware'.
Sep 15 14:15:38 HP-LAB NetworkManager[2719]: <info> monitoring ifupdown state file '/run/network/ifstate'.
Sep 15 14:15:38 HP-LAB NetworkManager[2719]: <info> WiFi enabled by radio killswitch; enabled by state file
Sep 15 14:15:38 HP-LAB NetworkManager[2719]: <info> WWAN enabled by radio killswitch; enabled by state file
Sep 15 14:15:38 HP-LAB NetworkManager[2719]: <info> WiMAX enabled by radio killswitch; enabled by state file
Sep 15 14:15:38 HP-LAB NetworkManager[2719]: <info> Networking is enabled by state file
Sep 15 14:15:38 HP-LAB NetworkManager[2719]: <warn> failed to allocate link cache: (-10) Operation not supported
Sep 15 14:15:38 HP-LAB NetworkManager[2719]: <info> (eth0): carrier is ON
Sep 15 14:15:38 HP-LAB NetworkManager[2719]: <info> (eth0): new Ethernet device (driver: 'tg3' ifindex: 2)
Sep 15 14:15:38 HP-LAB NetworkManager[2719]: <info> (eth0): exported as /org/freedesktop/NetworkManager/Devices/0
Sep 15 14:15:38 HP-LAB modem-manager[2765]: <info>  ModemManager (version 0.5.2.0) starting...
Sep 15 14:15:38 HP-LAB dbus[2573]: [system] Successfully activated service 'org.freedesktop.ModemManager'
Sep 15 14:15:38 HP-LAB NetworkManager[2719]: <info> modem-manager is now available
Sep 15 14:15:38 HP-LAB modem-manager[2765]: <info>  Loaded plugin MotoC
Sep 15 14:15:38 HP-LAB modem-manager[2765]: <info>  Loaded plugin Samsung
Sep 15 14:15:38 HP-LAB modem-manager[2765]: <info>  Loaded plugin ZTE
Sep 15 14:15:39 HP-LAB modem-manager[2765]: <info>  Loaded plugin Linktop
Sep 15 14:15:39 HP-LAB modem-manager[2765]: <info>  Loaded plugin Gobi
Sep 15 14:15:39 HP-LAB modem-manager[2765]: <info>  Loaded plugin Sierra
Sep 15 14:15:39 HP-LAB modem-manager[2765]: <info>  Loaded plugin Generic
Sep 15 14:15:39 HP-LAB modem-manager[2765]: <info>  Loaded plugin Novatel
Sep 15 14:15:39 HP-LAB modem-manager[2765]: <info>  Loaded plugin Nokia
Sep 15 14:15:39 HP-LAB modem-manager[2765]: <info>  Loaded plugin AnyData
Sep 15 14:15:39 HP-LAB modem-manager[2765]: <info>  Loaded plugin SimTech
Sep 15 14:15:39 HP-LAB modem-manager[2765]: <info>  Loaded plugin Ericsson MBM
Sep 15 14:15:39 HP-LAB modem-manager[2765]: <info>  Loaded plugin X22X
Sep 15 14:15:39 HP-LAB modem-manager[2765]: <info>  Loaded plugin Huawei
Sep 15 14:15:39 HP-LAB modem-manager[2765]: <info>  Loaded plugin Option
Sep 15 14:15:39 HP-LAB modem-manager[2765]: <info>  Loaded plugin Option High-Speed
Sep 15 14:15:39 HP-LAB modem-manager[2765]: <info>  Loaded plugin Wavecom
Sep 15 14:15:39 HP-LAB modem-manager[2765]: <info>  Loaded plugin Longcheer
Sep 15 14:15:39 HP-LAB acpid: client connected from 2756[0:0]
Sep 15 14:15:39 HP-LAB acpid: 1 client rule loaded
Sep 15 14:15:46 HP-LAB kernel: [   23.128012] eth0: no IPv6 routers present
Sep 15 14:16:12 HP-LAB dbus[2573]: [system] Activating service name='org.freedesktop.ConsoleKit' (using servicehelper)
Sep 15 14:16:12 HP-LAB dbus[2573]: [system] Successfully activated service 'org.freedesktop.ConsoleKit'
Sep 15 14:16:13 HP-LAB acpid: client 2756[0:0] has disconnected
Sep 15 14:16:13 HP-LAB dbus[2573]: [system] Activating service name='org.freedesktop.UPower' (using servicehelper)
Sep 15 14:16:14 HP-LAB dbus[2573]: [system] Successfully activated service 'org.freedesktop.UPower'
Sep 15 14:16:15 HP-LAB anacron[2998]: Anacron 2.3 started on 2013-09-15
Sep 15 14:16:15 HP-LAB anacron[2998]: Normal exit (0 jobs run)
Sep 15 14:17:01 HP-LAB /USR/SBIN/CRON[3125]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)


auth.log for bootup at sleep 7:
Code: Select all
Sep 15 14:16:11 HP-LAB lightdm: pam_unix(lightdm:session): session opened for user lightdm by (uid=0)
Sep 15 14:16:11 HP-LAB lightdm: pam_ck_connector(lightdm:session): nox11 mode, ignoring PAM_TTY :0
Sep 15 14:16:14 HP-LAB dbus[2573]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.12" (uid=108 pid=2926 comm="/usr/sbin/lightdm-gtk-greeter ") interface="org.freedesktop.DBus.Properties" member="GetAll" error name="(unset)" requested_reply="0" destination=":1.10" (uid=0 pid=2853 comm="/usr/sbin/console-kit-daemon --no-daemon ")
Sep 15 14:16:20 HP-LAB login[2842]: pam_unix(login:session): session opened for user root by LOGIN(uid=0)
Sep 15 14:16:20 HP-LAB login[3077]: ROOT LOGIN  on '/dev/tty1'
Sep 15 14:17:01 HP-LAB CRON[3124]: pam_unix(cron:session): session opened for user root by (uid=0)
Sep 15 14:17:01 HP-LAB CRON[3124]: pam_unix(cron:session): session closed for user root


lightdm.log after bootup at sleep 7:
Code: Select all
[+0.02s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.02s] DEBUG: Starting Light Display Manager 1.2.2, UID=0 PID=2687
[+0.02s] DEBUG: Loaded configuration from /etc/lightdm/lightdm.conf
[+0.02s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
[+0.12s] DEBUG: Registered seat module xlocal
[+0.12s] DEBUG: Registered seat module xremote
[+0.12s] DEBUG: Adding default seat
[+0.12s] DEBUG: Starting seat
[+0.12s] DEBUG: Starting new display for greeter
[+0.12s] DEBUG: Starting local X display
[+0.13s] DEBUG: Could not run plymouth --ping: Failed to execute child process "plymouth" (No such file or directory)
[+0.13s] DEBUG: Using VT 7
[+0.24s] DEBUG: Activating VT 7
[+0.25s] DEBUG: Logging to /var/log/lightdm/x-0.log
[+0.64s] DEBUG: Writing X server authority to /var/run/lightdm/root/:0
[+0.64s] DEBUG: Launching X Server
[+0.64s] DEBUG: Launching process 2756: /usr/bin/X :0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+0.64s] DEBUG: Waiting for ready signal from X server :0
[+0.64s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+0.64s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0
[+2.30s] DEBUG: Got signal 10 from process 2756
[+2.30s] DEBUG: Got signal from X server :0
[+2.30s] DEBUG: Connecting to XServer :0
[+2.31s] DEBUG: Starting greeter
[+2.31s] DEBUG: Started session 2772 with service 'lightdm', username 'lightdm'
[+2.49s] DEBUG: Session 2772 authentication complete with return value 0: Success
[+2.49s] DEBUG: Greeter authorized
[+2.50s] DEBUG: org.freedesktop.Accounts does not exist, falling back to passwd file
[+2.50s] DEBUG: Launching process 2774: /home/daryl/lightdmgreeter.sh
[+33.90s] DEBUG: Process 2774 exited with return value 0
[+33.90s] DEBUG: Exit status of /home/daryl/lightdmgreeter.sh: 0
[+33.90s] DEBUG: Logging to /var/log/lightdm/x-0-greeter.log
[+33.99s] DEBUG: Session 2772 running command /usr/sbin/lightdm-gtk-greeter
[+34.95s] DEBUG: Greeter connected version=1.2.2
[+34.95s] DEBUG: Greeter connected, display is ready
[+34.95s] DEBUG: New display ready, switching to it
[+34.95s] DEBUG: Activating VT 7
[+36.87s] DEBUG: Greeter start authentication
[+36.87s] DEBUG: Started session 2973 with service 'lightdm', username '(null)'
[+36.88s] DEBUG: Session 2973 got 1 message(s) from PAM
[+36.88s] DEBUG: Prompt greeter with 1 message(s)
Monkadelicd
 
Posts: 23
Joined: 2008-08-06 00:46
Location: DFW, Texas, USA

Re: System tray is unavailable, quitting message

Postby bw123 » 2013-09-15 23:11

i don't often use killall, but what is switch "-9" for? what happens if you sleep before the killall line?
wheezy/KDE4, GNU/Linux 3.14-0.bpo.1-amd64
User avatar
bw123
 
Posts: 1839
Joined: 2011-05-09 06:02
Location: TN_USA

Re: System tray is unavailable, quitting message

Postby Monkadelicd » 2013-09-16 01:32

To my understanding the -9 switch to killall tells the process to end immediately without waiting for the process's normal shutdown procedure.
This means that there is no chance that the process will intercept or interrupt the kill command.

I tried to move the sleep command to the first line. No difference.

Thanks for the suggestions.
Monkadelicd
 
Posts: 23
Joined: 2008-08-06 00:46
Location: DFW, Texas, USA

Re: Starting Synergy server before login in XFCE4

Postby confuseling » 2013-09-16 18:43

You could of course try installing gdm3. Even if you don't want to switch permanently, it might help narrow down the problem.
The Forum's search box is terrible. Use site specific search, e.g.
https://www.google.com/search?q=site%3A ... terms+here
confuseling
 
Posts: 1997
Joined: 2009-10-21 01:03

Re: Starting Synergy server before login in XFCE4

Postby Monkadelicd » 2013-09-18 23:32

I installed gdm3 and added the appropriate lines to /etc/gdm3/Init/Default and /etc/gdm3/PostLogin/Default.
After restarted, Synergy worked fine at the login screen.

I reverted back to lightdm, restarted and I still have have the same issue.

I thought I was having trouble with Synergy in lightdm because I was using the command
Code: Select all
synergy

to start the server instead of
Code: Select all
synergys -c <location-of-config-file>

but it still isn't working after changing that. Using 'synergys' just causes the system to hang and not load the desktop.
Synergy doesn't seem to work until I login.
Monkadelicd
 
Posts: 23
Joined: 2008-08-06 00:46
Location: DFW, Texas, USA

Re: Can't Start Synergy server before login +XFCE4 +lightdm

Postby Monkadelicd » 2013-09-21 14:27

Has anyone done this successfully? Synergy server on XFCE4 with lightdm. Starting synergy before login?

Please help me out. I just don't know if this is a synergy issue or lightdm issue or how to figure out which it is.
Monkadelicd
 
Posts: 23
Joined: 2008-08-06 00:46
Location: DFW, Texas, USA


Return to Desktop & Multimedia

Who is online

Users browsing this forum: No registered users and 9 guests

fashionable