NetworkManager key not saved

Issues Related to Networking (Wired and Wireless)

Moderator: Moderators

Post Reply
Jago25_98
Young Hen
Posts: 21
Joined: Sun Nov 20, 2011 22:18

NetworkManager key not saved

Post by Jago25_98 » Tue Nov 20, 2012 18:36

After rebooting I need to reenter the WiFi key. It should be saved but it isn't.

Where can I get more info on NetworkManager to find out why it isn't saving the key after rebooting and check the permissions on the file that stores the info?

I've found some bugs mentioned in my searches but couldn't find a specific fix?
Everytime someone helps me I give $5 to Sabayon. Hopefully this will speed up equo bandwidth. If someone has helped you, why not say thanks and donate to speed it up for all :-)

Fitzcarraldo
Sagely Hen
Posts: 8218
Joined: Sat Mar 10, 2007 5:40
Location: United Kingdom
Contact:

Re: NetworkManager key not saved

Post by Fitzcarraldo » Wed Nov 21, 2012 0:08

KDE? GNOME? Xfce? MATE?

Jago25_98
Young Hen
Posts: 21
Joined: Sun Nov 20, 2011 22:18

Re: NetworkManager key not saved

Post by Jago25_98 » Wed Nov 21, 2012 0:35

Well it's actually XFCE but I thought it was all the same NetworkManager
Everytime someone helps me I give $5 to Sabayon. Hopefully this will speed up equo bandwidth. If someone has helped you, why not say thanks and donate to speed it up for all :-)

Fitzcarraldo
Sagely Hen
Posts: 8218
Joined: Sat Mar 10, 2007 5:40
Location: United Kingdom
Contact:

Re: NetworkManager key not saved

Post by Fitzcarraldo » Wed Nov 21, 2012 2:03

^But the GUI front-end can be different and so can the keyring manager. For example, the KDE front-end is kde-misc/networkmanagement whereas the Xfce GUI front-end is gnome-extra/nm-applet-gtk2; the KDE keyring manager is kde-base/kwallet whereas the keyring manager used in Xfce is gnome-base/gnome-keyring. Are gnome-keyring and libgnome-keyring installed on your machine?

I'm using SL Xfce with a WEP-encrypted network and it stores the password correctly, so let's see what are the differences between the two installations.

Is your installation fully upgraded (equo update && equo upgrade && equo conf update && kernel-switcher switch linux-sabayon-3.6-r3 && equo deptest && equo libtest)?

Are you using a WEP- or a WPA-encrypted network?

Do you have 'Available to all users' ticked in the Wireless Security tab of your network connection?

What are the contents of /etc/conf.d/network, /etc/conf.d/NetworkManager and /etc/conf.d/net?

Have you made any modifications since you installed SL Xfce from the SL Xfce LiveDVD?

Was your installation saving the password initially, or has it never worked?

Do you have, or have you had, another DE installed too?

Do you have autologin enabled?

Fitzcarraldo
Sagely Hen
Posts: 8218
Joined: Sat Mar 10, 2007 5:40
Location: United Kingdom
Contact:

Re: NetworkManager key not saved

Post by Fitzcarraldo » Wed Nov 28, 2012 1:57

Although you have not replied to my previous post, based on your posts in the thread Reducing the 3 passwords to login I have a hunch that you have enabled autologin. If you have, that is likely to be the reason why you are prompted for the wireless password each time you reboot. See e.g. Auto-Unlock Keyring Manager In Ubuntu Intrepid, which also tells you an (insecure) workaround for avoiding the prompt.

Jago25_98
Young Hen
Posts: 21
Joined: Sun Nov 20, 2011 22:18

Re: NetworkManager key not saved

Post by Jago25_98 » Wed Nov 28, 2012 13:21

Hi again Fitz :-)

I'm using XFCE so the keyring manager doesn't have the same dialogs as the gnome keyring/settings dialog to use that fix.
This has been an epic learning foray; pam, xfce, keyring manager, networkmanager, wicd, debian buglists, arch forum posts... :D

I think my best bet to try now might be a consolekit downgrade actually, if I can figure out ow to do that.
I want all this auto login stuff as I'm trying to make the most of that disk encryption. It's related to that post trying to get one password to a browser rather than the 4 I have at present.

Ah, here's an interesting finding - one network key has been saved but the other isn't being saved.

The one that isn't being saved is:
WPA2 personal, TKIP+AES...
ok trying TKIP and WPA1 now.. there is also has a "virtual interface" with same mac address in dd-wrt in addition to the "physical interface" - maybe that's the problem...
ok- tried changing that to wpa1-tkip with no virtual and it didn't connect at all... put the virtual interface back... and it connected without prompting for the key... rebooting to check... aaaaand... no :-(

The one that has been saved is:
WPA/WPA2, WPA-PSK, TKIP

But seeing as changing settings there didn't help I guess that can't be related and must be a diversion.

Code: Select all

$ cat /etc/conf.d/network
# Assign static IP addresses and run custom scripts per interface.
# Seperate commands with ;
# Prefix with ! to run a shell script.
# Use \$int to represent the interface
#ifconfig_eth0="192.168.0.10 netmask 255.255.255.0"

# You also have ifup_eth0 and ifdown_eth0 to run other commands when
# eth0 is started and stopped.
# You should note that we don't stop the network at system shutdown by default.
# If you really need this, then set shutdown_network=YES

# Lastly, the interfaces variable pulls in virtual interfaces that cannot
# be automatically detected.
#interfaces="br0 bond0 vlan0"

# You can also use files instead of variables here if you like:
# /etc/ifconfig.eth0 is equivalent to ifconfig_eth0
# /etc/ip.eth0 is equivalent to ifconfig_eth0
# /etc/ifup.eth0 is equivalent to ifup_eth0
# /etc/ifdown.eth0 is equivalent to ifdown_eth0
# Any files found will automatically be put into the interfaces variable.
# You don't need to escape variables in files, so use $int instead of \$int.

# If you require DHCP, you should install dhcpcd and it to the boot or
# default runlevel.

# NIS users can set the domain name here
#domainname="foobar"

# You can assign a default route
#defaultroute="gw 192.168.0.1"
#defaultroute6="gw 2001:a:b:c"

# ifconfig under Linux is not that powerful and doesn't easily handle
# multiple addresses
# On the other hand, ip (iproute2) is quite powerful and is also supported
#ip_eth0="192.168.0.10/24; 192.168.I'm using XFCE so the keyring manager doesn't have the same dialogs as the gnome keyring/settings dialog to use that fix. 

[code]
$ cat /etc/conf.d/network
# Assign static IP addresses and run custom scripts per interface.
# Seperate commands with ;
# Prefix with ! to run a shell script.
# Use \$int to represent the interface
#ifconfig_eth0="192.168.0.10 netmask 255.255.255.0"

# You also have ifup_eth0 and ifdown_eth0 to run other commands when
# eth0 is started and stopped.
# You should note that we don't stop the network at system shutdown by default.
# If you really need this, then set shutdown_network=YES

# Lastly, the interfaces variable pulls in virtual interfaces that cannot
# be automatically detected.
#interfaces="br0 bond0 vlan0"

# You can also use files instead of variables here if you like:
# /etc/ifconfig.eth0 is equivalent to ifconfig_eth0
# /etc/ip.eth0 is equivalent to ifconfig_eth0
# /etc/ifup.eth0 is equivalent to ifup_eth0
# /etc/ifdown.eth0 is equivalent to ifdown_eth0
# Any files found will automatically be put into the interfaces variable.
# You don't need to escape variables in files, so use $int instead of \$int.

# If you require DHCP, you should install dhcpcd and it to the boot or
# default runlevel.

# NIS users can set the domain name here
#domainname="foobar"

# You can assign a default route
#defaultroute="gw 192.168.0.1"
#defaultroute6="gw 2001:a:b:c"

# ifconfig under Linux is not that powerful and doesn't easily handle
# multiple addresses
# On the other hand, ip (iproute2) is quite powerful and is also supported
#ip_eth0="192.168.0.10/24; 192.168.10.10/24"

# You can also use ip to add the default route.
#defaultiproute="via 192.168.0.1"
#defaultiproute6="via 2001:a:b:c"

# ip doesn't handle MTU like ifconfig, but we can do it like so
#ifup_eth0="ip link set \$int mtu 1500"

# Create a bonded interface
#interfaces="bond0"
#ifup_bond0="modprobe bonding; ifconfig \$int up; ifenslave \$int bge0"
#ifconfig_bond0="192.168.0.10 netmask 255.255.255.0"
#ifdown_bond0="rmmod bonding"

# Create tap interface and a bridge interface.
# We add the tap to the bridge.
# An external program, like dhcpcd, will configure the IP on the bridge
#interfaces="tun0 br0"
#ifup_tun0="tunctl -t \$int"
#ifdown_tun0="tunctl -d \$int"
#ifup_br0="brctl addbr \$int; brctl add \$int eth1; brtctl add \$int eth2"
#ifdown_br0="ifconfig \$int down; btctl delbr \$int"

# Create VLAN
#interfaces="eth0_2 eth0_3 eth0_4"
#ifup_eth0="vconfig add \$int 2; vconfig add \$int 3; vconfig add \$int 4"
#ifconfig_eth0_2="192.168.2.10 netmask 255.255.255.0"
#ifconfig_eth0_3="192.168.3.10 netmask 255.255.255.0"
#ifconfig_eth0_4="192.168.4.10 netmask 255.255.255.0"
#ifdown_eth0="vconfig rem \$int.2; vconfig rem \$int.3; vconfig rem \$int.4"

# Normally you would use wpa_supplicant to configure wireless, but you can
# use iwconfig also
#ifup_wlan0="iwconfig \$int key s:secretkey enc open essid foobar"

Code: Select all

$ cat /etc/conf.d/NetworkManager
# If NetworkManager does not establish a connection within $INACTIVE_TIMEOUT
# seconds after starting, the service will be marked as inactive, and it will
# continue to wait for a connection in background mode.
INACTIVE_TIMEOUT=1

Code: Select all

$ cat /etc/fstab

#
# /etc/fstab
# Created by anaconda on Mon Oct 29 22:45:33 2012
#
# Accessible filesystems, by reference, are maintained under '/dev/disk'
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info
#
/dev/mapper/vg_idpp1377-lv_root /                       ext4    defaults        1 1
UUID=(censored) /boot                   ext4    defaults        1 2
/dev/mapper/vg_idpp1377-lv_swap swap                    swap    defaults        0 0
tmpfs                   /dev/shm                tmpfs   defaults        0 0
devpts                  /dev/pts                devpts  gid=5,mode=620  0 0
sysfs                   /sys                    sysfs   defaults        0 0
proc                    /proc                   proc    defaults        0 0
Some more info. Found a big related to this on te debian buglist but can't seem to get any of the fixes to work for me. The only one I would like to try is downgrading consolekit... trying to figure out how to do that now.

/etc/pam.d $ cat lxdm
#%PAM-1.0
auth substack system-auth
auth optional pam_gnome_keyring.so
account include system-auth
session optional pam_keyinit.so force revoke
session include system-auth
session required pam_loginuid.so
#session optional pam_console.so
session optional pam_gnome_keyring.so auto_start

$ ps aux |grep lxdm
root 10095 0.0 0.1 56136 2440 ? Ss 22:09 0:00 /usr/sbin/lxdm-binary


$ cat /etc/pam.d/xdm
# File autogenerated by pamd_mimic in pam eclass


auth include system-local-login
account include system-local-login
session include system-local-login


emerge --search ck-connector
Searching...
[ Results for search key : ck-connector ]
[ Applications found : 0 ]

Code: Select all

/etc/pam.d $ ls comm*
ls: cannot access comm*: No such file or directory
[email protected] /etc/pam.d $ ls
chage      groupdel   lxdm      pops       sshd                    system-login
chfn       groupmems  newusers  ppp        start-stop-daemon       system-remote-login
chgpasswd  groupmod   other     samba      su                      system-services
chpasswd   imap       passwd    saslauthd  sudo                    useradd
chsh       imap4      polkit-1  schroot    system-auth             userdel
cron       imap4s     pop       screen     system-auth-winbind     usermod
cups       imaps      pop3      shadow     system-config-keyboard  xdm
groupadd   login      pop3s     smtp       system-local-login      xscreensaver
[email protected] /etc/pam.d $ 

Code: Select all

sudo console-kit-daemon --debug --no-daemon
console-kit-daemon[17864]: DEBUG: Debugging enabled
console-kit-daemon[17864]: DEBUG: initializing console-kit-daemon 0.4.6
console-kit-daemon[17864]: DEBUG: Creating thread for log writing
console-kit-daemon[17864]: DEBUG: Creating seat /org/freedesktop/ConsoleKit/Seat1 with 0 devices
console-kit-daemon[17864]: DEBUG: Current VT: tty7
console-kit-daemon[17864]: DEBUG: VT 1:on
console-kit-daemon[17864]: DEBUG: VT 2:on
console-kit-daemon[17864]: DEBUG: VT 3:on
console-kit-daemon[17864]: DEBUG: VT 4:on
console-kit-daemon[17864]: DEBUG: VT 5:on
console-kit-daemon[17864]: DEBUG: VT 6:on
console-kit-daemon[17864]: DEBUG: VT 7:on
console-kit-daemon[17864]: DEBUG: VT 8:off
console-kit-daemon[17864]: DEBUG: VT 9:off
console-kit-daemon[17864]: DEBUG: VT 10:off
console-kit-daemon[17864]: DEBUG: VT 11:off
console-kit-daemon[17864]: DEBUG: VT 12:on
console-kit-daemon[17864]: DEBUG: VT 13:off
console-kit-daemon[17864]: DEBUG: VT 14:off
console-kit-daemon[17864]: DEBUG: VT 15:off
console-kit-daemon[17864]: DEBUG: VT 16:off
console-kit-daemon[17864]: DEBUG: Creating thread for vt 1
console-kit-daemon[17864]: DEBUG: Creating thread for vt 2
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 1
console-kit-daemon[17864]: DEBUG: Creating thread for vt 3
console-kit-daemon[17864]: DEBUG: Creating thread for vt 4
console-kit-daemon[17864]: DEBUG: Creating thread for vt 5
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 3
console-kit-daemon[17864]: DEBUG: Creating thread for vt 6
console-kit-daemon[17864]: DEBUG: Creating thread for vt 8
console-kit-daemon[17864]: DEBUG: Creating thread for vt 9
console-kit-daemon[17864]: DEBUG: Creating thread for vt 10
console-kit-daemon[17864]: DEBUG: Creating thread for vt 11
console-kit-daemon[17864]: DEBUG: Creating thread for vt 12
console-kit-daemon[17864]: DEBUG: Creating thread for vt 13
console-kit-daemon[17864]: DEBUG: Creating thread for vt 14
console-kit-daemon[17864]: DEBUG: Creating thread for vt 15
console-kit-daemon[17864]: DEBUG: Creating thread for vt 16
console-kit-daemon[17864]: DEBUG: Creating thread for vt 17
console-kit-daemon[17864]: DEBUG: Creating thread for vt 18
console-kit-daemon[17864]: DEBUG: Creating thread for vt 19
console-kit-daemon[17864]: DEBUG: Creating thread for vt 20
console-kit-daemon[17864]: DEBUG: Creating thread for vt 21
console-kit-daemon[17864]: DEBUG: Creating thread for vt 22
console-kit-daemon[17864]: DEBUG: Creating thread for vt 23
console-kit-daemon[17864]: DEBUG: Creating thread for vt 24
console-kit-daemon[17864]: DEBUG: Creating thread for vt 25
console-kit-daemon[17864]: DEBUG: Creating thread for vt 26
console-kit-daemon[17864]: DEBUG: Creating thread for vt 27
console-kit-daemon[17864]: DEBUG: Creating thread for vt 28
console-kit-daemon[17864]: DEBUG: Creating thread for vt 29
console-kit-daemon[17864]: DEBUG: Creating thread for vt 30
console-kit-daemon[17864]: DEBUG: Creating thread for vt 31
console-kit-daemon[17864]: DEBUG: Creating thread for vt 32
console-kit-daemon[17864]: DEBUG: Creating thread for vt 33
console-kit-daemon[17864]: DEBUG: Creating thread for vt 34
console-kit-daemon[17864]: DEBUG: Creating thread for vt 35
console-kit-daemon[17864]: DEBUG: Creating thread for vt 36
console-kit-daemon[17864]: DEBUG: Creating thread for vt 37
console-kit-daemon[17864]: DEBUG: Creating thread for vt 38
console-kit-daemon[17864]: DEBUG: Creating thread for vt 39
console-kit-daemon[17864]: DEBUG: Creating thread for vt 40
console-kit-daemon[17864]: DEBUG: Creating thread for vt 41
console-kit-daemon[17864]: DEBUG: Creating thread for vt 42
console-kit-daemon[17864]: DEBUG: Creating thread for vt 43
console-kit-daemon[17864]: DEBUG: Creating thread for vt 44
console-kit-daemon[17864]: DEBUG: Creating thread for vt 45
console-kit-daemon[17864]: DEBUG: Creating thread for vt 46
console-kit-daemon[17864]: DEBUG: Creating thread for vt 47
console-kit-daemon[17864]: DEBUG: Creating thread for vt 48
console-kit-daemon[17864]: DEBUG: Creating thread for vt 49
console-kit-daemon[17864]: DEBUG: Creating thread for vt 50
console-kit-daemon[17864]: DEBUG: Creating thread for vt 51
console-kit-daemon[17864]: DEBUG: Creating thread for vt 52
console-kit-daemon[17864]: DEBUG: Creating thread for vt 53
console-kit-daemon[17864]: DEBUG: Creating thread for vt 54
console-kit-daemon[17864]: DEBUG: Creating thread for vt 55
console-kit-daemon[17864]: DEBUG: Creating thread for vt 56
console-kit-daemon[17864]: DEBUG: Creating thread for vt 57
console-kit-daemon[17864]: DEBUG: Creating thread for vt 58
console-kit-daemon[17864]: DEBUG: Creating thread for vt 59
console-kit-daemon[17864]: DEBUG: Creating thread for vt 60
console-kit-daemon[17864]: DEBUG: Creating thread for vt 61
console-kit-daemon[17864]: DEBUG: Creating thread for vt 62
console-kit-daemon[17864]: DEBUG: Added seat: /org/freedesktop/ConsoleKit/Seat1
console-kit-daemon[17864]: DEBUG: Running programs in /etc/ConsoleKit/run-seat.d for action seat_added
console-kit-daemon[17864]: DEBUG: Running programs in /usr/lib/ConsoleKit/run-seat.d for action seat_added
console-kit-daemon[17864]: DEBUG: Emitting seat-added: /org/freedesktop/ConsoleKit/Seat1
console-kit-daemon[17864]: DEBUG: Writing log for event: 1354056520.156 type=SEAT_ADDED : seat-id='Seat1' seat-kind=0
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 4
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 2
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 5
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 6
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 9
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 8
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 10
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 11
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 12
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 13
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 14
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 15
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 16
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 17
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 18
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 19
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 20
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 22
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 21
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 23
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 24
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 25
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 27
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 26
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 29
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 30
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 28
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 31
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 32
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 33
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 35
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 36
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 37
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 45
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 47
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 38
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 39
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 40
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 41
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 42
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 50
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 43
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 34
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 44
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 46
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 48
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 49
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 52
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 56
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 57
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 53
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 59
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 54
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 55
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 51
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 58
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 60
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 62
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 61
console-kit-daemon[17864]: DEBUG: Cleaning up /var/run/console
console-kit-daemon[17864]: DEBUG: Removing tag file: /var/run/console/jjj
console-kit-daemon[17864]: DEBUG: NameOwnerChanged: service_name='org.freedesktop.ConsoleKit', old_service_name='' new_service_name=':1.87'
console-kit-daemon[17864]: DEBUG: CkManager: get session for unix process: 10740
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: get session for cookie
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: Unable to lookup cookie for caller - failing
console-kit-daemon[17864]: DEBUG: CkManager: get session for unix process: 10768
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: get session for cookie
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: Unable to lookup cookie for caller - failing
console-kit-daemon[17864]: DEBUG: CkManager: get session for unix process: 10768
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: get session for cookie
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: Unable to lookup cookie for caller - failing
console-kit-daemon[17864]: DEBUG: CkManager: get session for unix process: 10768
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: get session for cookie
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: Unable to lookup cookie for caller - failing
console-kit-daemon[17864]: DEBUG: CkManager: get session for unix process: 10768
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: get session for cookie
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: Unable to lookup cookie for caller - failing
console-kit-daemon[17864]: DEBUG: CkManager: get session for unix process: 10768
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: get session for cookie
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: Unable to lookup cookie for caller - failing
console-kit-daemon[17864]: DEBUG: CkManager: get session for unix process: 10768
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: get session for cookie
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: Unable to lookup cookie for caller - failing
console-kit-daemon[17864]: DEBUG: CkManager: get session for unix process: 10768
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: get session for cookie
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: Unable to lookup cookie for caller - failing
console-kit-daemon[17864]: DEBUG: CkManager: get session for unix process: 10768
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: get session for cookie
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: Unable to lookup cookie for caller - failing
console-kit-daemon[17864]: DEBUG: CkManager: get session for unix process: 10768
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: get session for cookie
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: Unable to lookup cookie for caller - failing
console-kit-daemon[17864]: DEBUG: CkManager: get session for unix process: 10768
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: get session for cookie
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: Unable to lookup cookie for caller - failing
console-kit-daemon[17864]: DEBUG: CkManager: get session for unix process: 10768
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: get session for cookie
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: Unable to lookup cookie for caller - failing
console-kit-daemon[17864]: DEBUG: CkManager: get session for unix process: 10768
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: get session for cookie
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: Unable to lookup cookie for caller - failing
console-kit-daemon[17864]: DEBUG: CkManager: get session for unix process: 10768
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: get session for cookie
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: Unable to lookup cookie for caller - failing
console-kit-daemon[17864]: DEBUG: CkManager: get session for unix process: 10768
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: get session for cookie
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: Unable to lookup cookie for caller - failing
console-kit-daemon[17864]: DEBUG: CkManager: get session for unix process: 10768
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: get session for cookie
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: Unable to lookup cookie for caller - failing
console-kit-daemon[17864]: DEBUG: CkManager: get session for unix process: 10740
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: get session for cookie
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: Unable to lookup cookie for caller - failing
console-kit-daemon[17864]: DEBUG: CkManager: get session for unix process: 10740
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: get session for cookie
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: Unable to lookup cookie for caller - failing
console-kit-daemon[17864]: DEBUG: CkManager: get session for unix process: 10740
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: get session for cookie
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: Unable to lookup cookie for caller - failing
console-kit-daemon[17864]: DEBUG: CkManager: get session for unix process: 10740
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: get session for cookie
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: Unable to lookup cookie for caller - failing
console-kit-daemon[17864]: DEBUG: CkManager: get session for unix process: 10740
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: get session for cookie
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: Unable to lookup cookie for caller - failing

/var/log/messages

Code: Select all

Nov 27 22:13:18 localhost avahi-daemon[10418]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.152.
Nov 27 22:13:18 localhost avahi-daemon[10418]: New relevant interface wlan0.IPv4 for mDNS.
Nov 27 22:13:18 localhost avahi-daemon[10418]: Registering new address record for 192.168.1.152 on wlan0.IPv4.
Nov 27 22:13:18 localhost NetworkManager[10314]: <info> (wlan0): DHCPv4 state changed preinit -> bound
Nov 27 22:13:18 localhost NetworkManager[10314]: <info>   address 192.168.1.152
Nov 27 22:13:18 localhost NetworkManager[10314]: <info>   prefix 24 (255.255.255.0)
Nov 27 22:13:18 localhost NetworkManager[10314]: <info>   gateway 192.168.1.1
Nov 27 22:13:18 localhost NetworkManager[10314]: <info>   nameserver '192.168.1.1'
Nov 27 22:13:18 localhost NetworkManager[10314]: <info>   domain name 'rv'
Nov 27 22:13:18 localhost NetworkManager[10314]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
Nov 27 22:13:18 localhost NetworkManager[10314]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Commit) started...
Nov 27 22:13:19 localhost NetworkManager[10314]: <info> (wlan0): writing resolv.conf to /sbin/resolvconf
Nov 27 22:13:19 localhost NetworkManager[10314]: <info> Clearing nscd hosts cache.
Nov 27 22:13:19 localhost NetworkManager[10314]: <info> (wlan0): device state change: ip-config -> activated (reason 'none') [70 100 0]
Nov 27 22:13:19 localhost NetworkManager[10314]: <info> Policy set 'belkin.77bc' (wlan0) as default for IPv4 routing and DNS.
Nov 27 22:13:19 localhost NetworkManager[10314]: <info> Activation (wlan0) successful, device activated.
Nov 27 22:13:19 localhost NetworkManager[10314]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Commit) complete.
Nov 27 22:13:19 localhost dbus[9403]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
Nov 27 22:13:19 localhost dbus[9403]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Nov 27 22:13:25 localhost NetworkManager[10314]: <info> (wlan0): IP6 addrconf timed out or failed.
Nov 27 22:13:25 localhost NetworkManager[10314]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
Nov 27 22:13:25 localhost NetworkManager[10314]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) started...
Nov 27 22:13:25 localhost NetworkManager[10314]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) complete.
Nov 27 22:13:39 localhost nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/10-openrc-status' exited with error status 1.
Nov 27 22:17:05 localhost sudo:      jjj : TTY=pts/0 ; PWD=/home/jjj ; USER=root ; COMMAND=/bin/tail /var/log/messages
Nov 27 22:17:05 localhost sudo: pam_unix(sudo:session): session opened for user root by jjj(uid=0)
Nov 27 22:17:05 localhost sudo: pam_unix(sudo:session): session closed for user root
Nov 27 22:17:11 localhost sudo:      jjj : TTY=pts/0 ; PWD=/home/jjj ; USER=root ; COMMAND=/bin/tail /var/log/messages
Nov 27 22:17:11 localhost sudo: pam_unix(sudo:session): session opened for user root by jjj(uid=0)
Nov 27 22:17:11 localhost sudo: pam_unix(sudo:session): session closed for user root
Nov 27 22:17:19 localhost sudo:      jjj : TTY=pts/0 ; PWD=/home/jjj ; USER=root ; COMMAND=/bin/tail -n100 /var/log/messages
Nov 27 22:17:19 localhost sudo: pam_unix(sudo:session): session opened for user root by jjj(uid=0)
ps -ef | grep keyring
jjj 10692 1 0 22:09 ? 00:00:00 /usr/bin/gnome-keyring-daemon --daemonize --login
jjj 13288 11251 0 22:18 pts/0 00:00:00 grep --colour=auto keyring

Code: Select all

equo search consolekit
invalid filesystem encoding ANSI_X3.4-1968, must be UTF-8.
Make sure to set LC_ALL, LANG, LANGUAGE to valid UTF-8 values.
Please execute:
  LC_ALL=en_US.UTF-8 /usr/bin/equo search consolekit
Cannot automatically recover from this.
>>  @@ Searching...
>>      @@ Package: sys-auth/consolekit-0.4.5_p20120320-r1 branch: 5, [sabayon-weekly] 
>>         Available:     version: 0.4.5_p20120320-r1 ~ tag: NoTag ~ revision: 0
>>         Installed:     version: 0.4.5_p20120320-r1 ~ tag: NoTag ~ revision: 0
>>         Slot:          0
>>         Homepage:      http://www.freedesktop.org/wiki/Software/ConsoleKit 
>>         Description:   Framework for defining and tracking 
>>                        users, login sessions and seats. 
>>         License:       GPL-2
>>  Keywords:  consolekit
>>  Found:     1 entry
More info:

http://forum.xfce.org/viewtopic.php?id=7458
https://bbs.archlinux.org/viewtopic.php ... 19#p886519
http://forums.fedoraforum.org/showthread.php?t=270843
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=597937

Fixes:
- use Gnome
- replace NetworkManager with wicd (only an option if you don't need the other functionality) wicd-gtk crashes for me...
- Downgrade consolekit to 0.4.1-4
- mess with xdm/gdm/startx/lxdm managers and pam
- Editing /etc/sysconfig/network-scripts/keys-<name> is not reboot persistent10.10/24"

# You can also use ip to add the default route.
#defaultiproute="via 192.168.0.1"
#defaultiproute6="via 2001:a:b:c"

# ip doesn't handle MTU like ifconfig, but we can do it like so
#ifup_eth0="ip link set \$int mtu 1500"

# Create a bonded interface
#interfaces="bond0"
#ifup_bond0="modprobe bonding; ifconfig \$int up; ifenslave \$int bge0"
#ifconfig_bond0="192.168.0.10 netmask 255.255.255.0"
#ifdown_bond0="rmmod bonding"

# Create tap interface and a bridge interface.
# We add the tap to the bridge.
# An external program, like dhcpcd, will configure the IP on the bridge
#interfaces="tun0 br0"
#ifup_tun0="tunctl -t \$int"
#ifdown_tun0="tunctl -d \$int"
#ifup_br0="brctl addbr \$int; brctl add \$int eth1; brtctl add \$int eth2"
#ifdown_br0="ifconfig \$int down; btctl delbr \$int"

# Create VLAN
#interfaces="eth0_2 eth0_3 eth0_4"
#ifup_eth0="vconfig add \$int 2; vconfig add \$int 3; vconfig add \$int 4"
#ifconfig_eth0_2="192.168.2.10 netmask 255.255.255.0"
#ifconfig_eth0_3="192.168.3.10 netmask 255.255.255.0"
#ifconfig_eth0_4="192.168.4.10 netmask 255.255.255.0"
#ifdown_eth0="vconfig rem \$int.2; vconfig rem \$int.3; vconfig rem \$int.4"

# Normally you would use wpa_supplicant to configure wireless, but you can
# use iwconfig also
#ifup_wlan0="iwconfig \$int key s:secretkey enc open essid foobar"
[/code]

Code: Select all

$ cat /etc/conf.d/NetworkManager
# If NetworkManager does not establish a connection within $INACTIVE_TIMEOUT
# seconds after starting, the service will be marked as inactive, and it will
# continue to wait for a connection in background mode.
INACTIVE_TIMEOUT=1

Code: Select all

$ cat /etc/fstab

#
# /etc/fstab
# Created by anaconda on Mon Oct 29 22:45:33 2012
#
# Accessible filesystems, by reference, are maintained under '/dev/disk'
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info
#
/dev/mapper/vg_idpp1377-lv_root /                       ext4    defaults        1 1
UUID=(censored) /boot                   ext4    defaults        1 2
/dev/mapper/vg_idpp1377-lv_swap swap                    swap    defaults        0 0
tmpfs                   /dev/shm                tmpfs   defaults        0 0
devpts                  /dev/pts                devpts  gid=5,mode=620  0 0
sysfs                   /sys                    sysfs   defaults        0 0
proc                    /proc                   proc    defaults        0 0
Some more info. Found a big related to this on te debian buglist but can't seem to get any of the fixes to work for me. The only one I would like to try is downgrading consolekit... trying to figure out how to do that now.

/etc/pam.d $ cat lxdm
#%PAM-1.0
auth substack system-auth
auth optional pam_gnome_keyring.so
account include system-auth
session optional pam_keyinit.so force revoke
session include system-auth
session required pam_loginuid.so
#session optional pam_console.so
session optional pam_gnome_keyring.so auto_start

$ ps aux |grep lxdm
root 10095 0.0 0.1 56136 2440 ? Ss 22:09 0:00 /usr/sbin/lxdm-binary


$ cat /etc/pam.d/xdm
# File autogenerated by pamd_mimic in pam eclass


auth include system-local-login
account include system-local-login
session include system-local-login


emerge --search ck-connector
Searching...
[ Results for search key : ck-connector ]
[ Applications found : 0 ]

Code: Select all

/etc/pam.d $ ls comm*
ls: cannot access comm*: No such file or directory
[email protected] /etc/pam.d $ ls
chage      groupdel   lxdm      pops       sshd                    system-login
chfn       groupmems  newusers  ppp        start-stop-daemon       system-remote-login
chgpasswd  groupmod   other     samba      su                      system-services
chpasswd   imap       passwd    saslauthd  sudo                    useradd
chsh       imap4      polkit-1  schroot    system-auth             userdel
cron       imap4s     pop       screen     system-auth-winbind     usermod
cups       imaps      pop3      shadow     system-config-keyboard  xdm
groupadd   login      pop3s     smtp       system-local-login      xscreensaver
[email protected] /etc/pam.d $ 

Code: Select all

sudo console-kit-daemon --debug --no-daemon
console-kit-daemon[17864]: DEBUG: Debugging enabled
console-kit-daemon[17864]: DEBUG: initializing console-kit-daemon 0.4.6
console-kit-daemon[17864]: DEBUG: Creating thread for log writing
console-kit-daemon[17864]: DEBUG: Creating seat /org/freedesktop/ConsoleKit/Seat1 with 0 devices
console-kit-daemon[17864]: DEBUG: Current VT: tty7
console-kit-daemon[17864]: DEBUG: VT 1:on
console-kit-daemon[17864]: DEBUG: VT 2:on
console-kit-daemon[17864]: DEBUG: VT 3:on
console-kit-daemon[17864]: DEBUG: VT 4:on
console-kit-daemon[17864]: DEBUG: VT 5:on
console-kit-daemon[17864]: DEBUG: VT 6:on
console-kit-daemon[17864]: DEBUG: VT 7:on
console-kit-daemon[17864]: DEBUG: VT 8:off
console-kit-daemon[17864]: DEBUG: VT 9:off
console-kit-daemon[17864]: DEBUG: VT 10:off
console-kit-daemon[17864]: DEBUG: VT 11:off
console-kit-daemon[17864]: DEBUG: VT 12:on
console-kit-daemon[17864]: DEBUG: VT 13:off
console-kit-daemon[17864]: DEBUG: VT 14:off
console-kit-daemon[17864]: DEBUG: VT 15:off
console-kit-daemon[17864]: DEBUG: VT 16:off
console-kit-daemon[17864]: DEBUG: Creating thread for vt 1
console-kit-daemon[17864]: DEBUG: Creating thread for vt 2
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 1
console-kit-daemon[17864]: DEBUG: Creating thread for vt 3
console-kit-daemon[17864]: DEBUG: Creating thread for vt 4
console-kit-daemon[17864]: DEBUG: Creating thread for vt 5
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 3
console-kit-daemon[17864]: DEBUG: Creating thread for vt 6
console-kit-daemon[17864]: DEBUG: Creating thread for vt 8
console-kit-daemon[17864]: DEBUG: Creating thread for vt 9
console-kit-daemon[17864]: DEBUG: Creating thread for vt 10
console-kit-daemon[17864]: DEBUG: Creating thread for vt 11
console-kit-daemon[17864]: DEBUG: Creating thread for vt 12
console-kit-daemon[17864]: DEBUG: Creating thread for vt 13
console-kit-daemon[17864]: DEBUG: Creating thread for vt 14
console-kit-daemon[17864]: DEBUG: Creating thread for vt 15
console-kit-daemon[17864]: DEBUG: Creating thread for vt 16
console-kit-daemon[17864]: DEBUG: Creating thread for vt 17
console-kit-daemon[17864]: DEBUG: Creating thread for vt 18
console-kit-daemon[17864]: DEBUG: Creating thread for vt 19
console-kit-daemon[17864]: DEBUG: Creating thread for vt 20
console-kit-daemon[17864]: DEBUG: Creating thread for vt 21
console-kit-daemon[17864]: DEBUG: Creating thread for vt 22
console-kit-daemon[17864]: DEBUG: Creating thread for vt 23
console-kit-daemon[17864]: DEBUG: Creating thread for vt 24
console-kit-daemon[17864]: DEBUG: Creating thread for vt 25
console-kit-daemon[17864]: DEBUG: Creating thread for vt 26
console-kit-daemon[17864]: DEBUG: Creating thread for vt 27
console-kit-daemon[17864]: DEBUG: Creating thread for vt 28
console-kit-daemon[17864]: DEBUG: Creating thread for vt 29
console-kit-daemon[17864]: DEBUG: Creating thread for vt 30
console-kit-daemon[17864]: DEBUG: Creating thread for vt 31
console-kit-daemon[17864]: DEBUG: Creating thread for vt 32
console-kit-daemon[17864]: DEBUG: Creating thread for vt 33
console-kit-daemon[17864]: DEBUG: Creating thread for vt 34
console-kit-daemon[17864]: DEBUG: Creating thread for vt 35
console-kit-daemon[17864]: DEBUG: Creating thread for vt 36
console-kit-daemon[17864]: DEBUG: Creating thread for vt 37
console-kit-daemon[17864]: DEBUG: Creating thread for vt 38
console-kit-daemon[17864]: DEBUG: Creating thread for vt 39
console-kit-daemon[17864]: DEBUG: Creating thread for vt 40
console-kit-daemon[17864]: DEBUG: Creating thread for vt 41
console-kit-daemon[17864]: DEBUG: Creating thread for vt 42
console-kit-daemon[17864]: DEBUG: Creating thread for vt 43
console-kit-daemon[17864]: DEBUG: Creating thread for vt 44
console-kit-daemon[17864]: DEBUG: Creating thread for vt 45
console-kit-daemon[17864]: DEBUG: Creating thread for vt 46
console-kit-daemon[17864]: DEBUG: Creating thread for vt 47
console-kit-daemon[17864]: DEBUG: Creating thread for vt 48
console-kit-daemon[17864]: DEBUG: Creating thread for vt 49
console-kit-daemon[17864]: DEBUG: Creating thread for vt 50
console-kit-daemon[17864]: DEBUG: Creating thread for vt 51
console-kit-daemon[17864]: DEBUG: Creating thread for vt 52
console-kit-daemon[17864]: DEBUG: Creating thread for vt 53
console-kit-daemon[17864]: DEBUG: Creating thread for vt 54
console-kit-daemon[17864]: DEBUG: Creating thread for vt 55
console-kit-daemon[17864]: DEBUG: Creating thread for vt 56
console-kit-daemon[17864]: DEBUG: Creating thread for vt 57
console-kit-daemon[17864]: DEBUG: Creating thread for vt 58
console-kit-daemon[17864]: DEBUG: Creating thread for vt 59
console-kit-daemon[17864]: DEBUG: Creating thread for vt 60
console-kit-daemon[17864]: DEBUG: Creating thread for vt 61
console-kit-daemon[17864]: DEBUG: Creating thread for vt 62
console-kit-daemon[17864]: DEBUG: Added seat: /org/freedesktop/ConsoleKit/Seat1
console-kit-daemon[17864]: DEBUG: Running programs in /etc/ConsoleKit/run-seat.d for action seat_added
console-kit-daemon[17864]: DEBUG: Running programs in /usr/lib/ConsoleKit/run-seat.d for action seat_added
console-kit-daemon[17864]: DEBUG: Emitting seat-added: /org/freedesktop/ConsoleKit/Seat1
console-kit-daemon[17864]: DEBUG: Writing log for event: 1354056520.156 type=SEAT_ADDED : seat-id='Seat1' seat-kind=0
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 4
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 2
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 5
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 6
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 9
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 8
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 10
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 11
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 12
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 13
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 14
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 15
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 16
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 17
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 18
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 19
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 20
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 22
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 21
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 23
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 24
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 25
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 27
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 26
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 29
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 30
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 28
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 31
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 32
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 33
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 35
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 36
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 37
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 45
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 47
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 38
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 39
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 40
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 41
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 42
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 50
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 43
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 34
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 44
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 46
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 48
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 49
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 52
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 56
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 57
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 53
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 59
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 54
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 55
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 51
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 58
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 60
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 62
console-kit-daemon[17864]: DEBUG: VT_WAITACTIVE for vt 61
console-kit-daemon[17864]: DEBUG: Cleaning up /var/run/console
console-kit-daemon[17864]: DEBUG: Removing tag file: /var/run/console/jjj
console-kit-daemon[17864]: DEBUG: NameOwnerChanged: service_name='org.freedesktop.ConsoleKit', old_service_name='' new_service_name=':1.87'
console-kit-daemon[17864]: DEBUG: CkManager: get session for unix process: 10740
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: get session for cookie
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: Unable to lookup cookie for caller - failing
console-kit-daemon[17864]: DEBUG: CkManager: get session for unix process: 10768
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: get session for cookie
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: Unable to lookup cookie for caller - failing
console-kit-daemon[17864]: DEBUG: CkManager: get session for unix process: 10768
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: get session for cookie
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: Unable to lookup cookie for caller - failing
console-kit-daemon[17864]: DEBUG: CkManager: get session for unix process: 10768
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: get session for cookie
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: Unable to lookup cookie for caller - failing
console-kit-daemon[17864]: DEBUG: CkManager: get session for unix process: 10768
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: get session for cookie
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: Unable to lookup cookie for caller - failing
console-kit-daemon[17864]: DEBUG: CkManager: get session for unix process: 10768
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: get session for cookie
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: Unable to lookup cookie for caller - failing
console-kit-daemon[17864]: DEBUG: CkManager: get session for unix process: 10768
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: get session for cookie
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: Unable to lookup cookie for caller - failing
console-kit-daemon[17864]: DEBUG: CkManager: get session for unix process: 10768
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: get session for cookie
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: Unable to lookup cookie for caller - failing
console-kit-daemon[17864]: DEBUG: CkManager: get session for unix process: 10768
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: get session for cookie
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: Unable to lookup cookie for caller - failing
console-kit-daemon[17864]: DEBUG: CkManager: get session for unix process: 10768
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: get session for cookie
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: Unable to lookup cookie for caller - failing
console-kit-daemon[17864]: DEBUG: CkManager: get session for unix process: 10768
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: get session for cookie
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: Unable to lookup cookie for caller - failing
console-kit-daemon[17864]: DEBUG: CkManager: get session for unix process: 10768
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: get session for cookie
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: Unable to lookup cookie for caller - failing
console-kit-daemon[17864]: DEBUG: CkManager: get session for unix process: 10768
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: get session for cookie
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: Unable to lookup cookie for caller - failing
console-kit-daemon[17864]: DEBUG: CkManager: get session for unix process: 10768
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: get session for cookie
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: Unable to lookup cookie for caller - failing
console-kit-daemon[17864]: DEBUG: CkManager: get session for unix process: 10768
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: get session for cookie
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: Unable to lookup cookie for caller - failing
console-kit-daemon[17864]: DEBUG: CkManager: get session for unix process: 10768
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: get session for cookie
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: Unable to lookup cookie for caller - failing
console-kit-daemon[17864]: DEBUG: CkManager: get session for unix process: 10740
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: get session for cookie
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: Unable to lookup cookie for caller - failing
console-kit-daemon[17864]: DEBUG: CkManager: get session for unix process: 10740
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: get session for cookie
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: Unable to lookup cookie for caller - failing
console-kit-daemon[17864]: DEBUG: CkManager: get session for unix process: 10740
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: get session for cookie
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: Unable to lookup cookie for caller - failing
console-kit-daemon[17864]: DEBUG: CkManager: get session for unix process: 10740
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: get session for cookie
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: Unable to lookup cookie for caller - failing
console-kit-daemon[17864]: DEBUG: CkManager: get session for unix process: 10740
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: get session for cookie
console-kit-daemon[17864]: DEBUG: uid = 105
console-kit-daemon[17864]: DEBUG: pid = 9505
console-kit-daemon[17864]: DEBUG: CkManager: Unable to lookup cookie for caller - failing

/var/log/messages

Code: Select all

Nov 27 22:13:18 localhost avahi-daemon[10418]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.152.
Nov 27 22:13:18 localhost avahi-daemon[10418]: New relevant interface wlan0.IPv4 for mDNS.
Nov 27 22:13:18 localhost avahi-daemon[10418]: Registering new address record for 192.168.1.152 on wlan0.IPv4.
Nov 27 22:13:18 localhost NetworkManager[10314]: <info> (wlan0): DHCPv4 state changed preinit -> bound
Nov 27 22:13:18 localhost NetworkManager[10314]: <info>   address 192.168.1.152
Nov 27 22:13:18 localhost NetworkManager[10314]: <info>   prefix 24 (255.255.255.0)
Nov 27 22:13:18 localhost NetworkManager[10314]: <info>   gateway 192.168.1.1
Nov 27 22:13:18 localhost NetworkManager[10314]: <info>   nameserver '192.168.1.1'
Nov 27 22:13:18 localhost NetworkManager[10314]: <info>   domain name 'rv'
Nov 27 22:13:18 localhost NetworkManager[10314]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
Nov 27 22:13:18 localhost NetworkManager[10314]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Commit) started...
Nov 27 22:13:19 localhost NetworkManager[10314]: <info> (wlan0): writing resolv.conf to /sbin/resolvconf
Nov 27 22:13:19 localhost NetworkManager[10314]: <info> Clearing nscd hosts cache.
Nov 27 22:13:19 localhost NetworkManager[10314]: <info> (wlan0): device state change: ip-config -> activated (reason 'none') [70 100 0]
Nov 27 22:13:19 localhost NetworkManager[10314]: <info> Policy set 'belkin.77bc' (wlan0) as default for IPv4 routing and DNS.
Nov 27 22:13:19 localhost NetworkManager[10314]: <info> Activation (wlan0) successful, device activated.
Nov 27 22:13:19 localhost NetworkManager[10314]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Commit) complete.
Nov 27 22:13:19 localhost dbus[9403]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
Nov 27 22:13:19 localhost dbus[9403]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Nov 27 22:13:25 localhost NetworkManager[10314]: <info> (wlan0): IP6 addrconf timed out or failed.
Nov 27 22:13:25 localhost NetworkManager[10314]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
Nov 27 22:13:25 localhost NetworkManager[10314]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) started...
Nov 27 22:13:25 localhost NetworkManager[10314]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) complete.
Nov 27 22:13:39 localhost nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/10-openrc-status' exited with error status 1.
Nov 27 22:17:05 localhost sudo:      jjj : TTY=pts/0 ; PWD=/home/jjj ; USER=root ; COMMAND=/bin/tail /var/log/messages
Nov 27 22:17:05 localhost sudo: pam_unix(sudo:session): session opened for user root by jjj(uid=0)
Nov 27 22:17:05 localhost sudo: pam_unix(sudo:session): session closed for user root
Nov 27 22:17:11 localhost sudo:      jjj : TTY=pts/0 ; PWD=/home/jjj ; USER=root ; COMMAND=/bin/tail /var/log/messages
Nov 27 22:17:11 localhost sudo: pam_unix(sudo:session): session opened for user root by jjj(uid=0)
Nov 27 22:17:11 localhost sudo: pam_unix(sudo:session): session closed for user root
Nov 27 22:17:19 localhost sudo:      jjj : TTY=pts/0 ; PWD=/home/jjj ; USER=root ; COMMAND=/bin/tail -n100 /var/log/messages
Nov 27 22:17:19 localhost sudo: pam_unix(sudo:session): session opened for user root by jjj(uid=0)
ps -ef | grep keyring
jjj 10692 1 0 22:09 ? 00:00:00 /usr/bin/gnome-keyring-daemon --daemonize --login
jjj 13288 11251 0 22:18 pts/0 00:00:00 grep --colour=auto keyring

Code: Select all

equo search consolekit
invalid filesystem encoding ANSI_X3.4-1968, must be UTF-8.
Make sure to set LC_ALL, LANG, LANGUAGE to valid UTF-8 values.
Please execute:
  LC_ALL=en_US.UTF-8 /usr/bin/equo search consolekit
Cannot automatically recover from this.
>>  @@ Searching...
>>      @@ Package: sys-auth/consolekit-0.4.5_p20120320-r1 branch: 5, [sabayon-weekly] 
>>         Available:     version: 0.4.5_p20120320-r1 ~ tag: NoTag ~ revision: 0
>>         Installed:     version: 0.4.5_p20120320-r1 ~ tag: NoTag ~ revision: 0
>>         Slot:          0
>>         Homepage:      http://www.freedesktop.org/wiki/Software/ConsoleKit 
>>         Description:   Framework for defining and tracking 
>>                        users, login sessions and seats. 
>>         License:       GPL-2
>>  Keywords:  consolekit
>>  Found:     1 entry
More info:

http://forum.xfce.org/viewtopic.php?id=7458
https://bbs.archlinux.org/viewtopic.php ... 19#p886519
http://forums.fedoraforum.org/showthread.php?t=270843
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=597937

Fixes:
- use Gnome
- replace NetworkManager with wicd (only an option if you don't need the other functionality) wicd-gtk crashes for me...
- Downgrade consolekit to 0.4.1-4
- mess with xdm/gdm/startx/lxdm managers and pam
- Editing /etc/sysconfig/network-scripts/keys-<name> is not reboot persistent
Everytime someone helps me I give $5 to Sabayon. Hopefully this will speed up equo bandwidth. If someone has helped you, why not say thanks and donate to speed it up for all :-)

Post Reply