Unable to connect to wireless on Slackware Current (25-11-2015)

moesasji · 11-30-2015, 05:43 PM

Yesterday I've installed a fully up-to-date current with the MLED 14.2 template. As this is a laptop I manage my network using NetworkManager, but I am unable to connect to wireless at all at two different places where it normally works fine for this machine. The error-message I get is "No session found for uid 1000", see screenshot below.

As session-management is done by Consolekit this might be an issue introduced by the udev to eudev switch as Keithpeter reports here that he sees the same issue since about 10 days ago.

Any suggestions how to fix this?

frankbell · 12-01-2015, 08:41 PM

Are you saying that it used to connect, but does so no longer?

A web search for "No session found for uid 1000 wireless" will turn up a number of links. I don't know enough about your situation to recommend one, but you may want to take a look.

Drakeo · 12-01-2015, 09:39 PM

you know on a couple of my upgrades I was testing this happen to me.for some reason my machine place my net device as eth1 strange but it does.
and the new /etc/rc.inet1.conf did not have the first two devices set for

Code:

# Config information for eth0:
IPADDR[0]=""
NETMASK[0]=""
USE_DHCP[0]="yes"
DHCP_HOSTNAME[0]=""

# Config information for eth1:
IPADDR[1]=""
NETMASK[1]=""
USE_DHCP[1]="yes"
DHCP_HOSTNAME[1]=""

then on my ktown upgrades it set them all empty.

Code:

# Config information for eth0:
IPADDR[0]=""
NETMASK[0]=""
USE_DHCP[0]=""
DHCP_HOSTNAME[0]=""

# Config information for eth1:
IPADDR[1]=""
NETMASK[1]=""
USE_DHCP[1]=""
DHCP_HOSTNAME[1]=""

and also got one new.conf that had none of them set to yes. this means you want to run netconfig. and let netconfig do it for you.
or edit the /etc/rc.inet1.conf .
This only happen going to current. and when I did slackpkg new-config.
Just like you I rebooted no internet. run netconfig. that may help.
if you chose to use networkmanager then do that.
you will "note" both networkmanager and /etc/rc.inet1.conf have been updated.
make sure you have netdevice privileges. But you will also get that if you have no internet connection.
in a terminal as root run ifconfig and see if your devices are up.
if not ifconfig wlan0 or eth0 up thin run ifconfig and look for your new devices.

moesasji · 12-02-2015, 12:59 AM

Quote:

Originally Posted by frankbell

Are you saying that it used to connect, but does so no longer?

This is a clean install on a machine where wireless used to work fine.

Quote:

Originally Posted by Drakeo

run netconfig. that may help.

I'm using Networkmanager, so I don't see why /etc/rc.d/rc.inet1.conf would matter (but it indeed has USE_DHCP as empty). Anyway rerunning netconfig and rebooting makes no difference.

However I found part of the puzzle in the MLED thread as the connection to wireless works fine if I remove gdm as the login-manager and switch to xdm. With xdm I get a password pop-up instead of this error-message and then I can connect successfully to wireless.

At the moment no clue why this happens when gdm is installed as the login-manager. The only real difference is that the MLED gdm is build in parallel, for the rest the Slackbuild looks very similar to the one from Ponce.

Bottomline is that I'm still very puzzled by this as there is no clear error and/or warning to go on in the logs and/or dmesg.

ponce · 12-02-2015, 01:21 AM

when you got the error you can check if you you have a consolekit session running

Code:

$ ck-list-sessions 
Session1:
        unix-user = '1000'
        realname = 'Matteo Bernardini'
        seat = 'Seat1'
        session-type = ''
        active = TRUE
        x11-display = ':0'
        x11-display-device = '/dev/tty2'
        display-device = '/dev/tty1'
        remote-host-name = ''
        is-local = TRUE
        on-since = '2015-11-30T16:52:23.487633Z'
        login-session-id = '4294967295'

moesasji · 12-02-2015, 01:44 AM

Quote:

Originally Posted by ponce

when you got the error you can check if you you have a consolekit session running

Sometimes I feel so stupid as I checked it was running a single seat, but at that time I didn't spot the real issue. The output of that command:

Code:

[hge@nova:~] $ ck-list-sessions
Session1:
	unix-user = '0'
	realname = '(null)'
	seat = 'Seat1'
	session-type = ''
	active = TRUE
	x11-display = ':0'
	x11-display-device = '/dev/tty7'
	display-device = ''
	remote-host-name = ''
	is-local = TRUE
	on-since = '2015-12-02T08:40:02.007720Z'
	login-session-id = '4294967295'

Essentially it takes the unix-user as the root-user instead of my actual user. That is where the problem is. Still no clue how to fix it though.

ponce · 12-02-2015, 01:49 AM

do you have the same problem with a new user created with adduser (don't forget to press the up arrow when needed)?

moesasji · 12-02-2015, 12:34 PM

Quote:

Originally Posted by ponce

do you have the same problem with a new user created with adduser (don't forget to press the up arrow when needed)?

A newly created user also can't connect to wifi, and gets the same error message.
ck-list-sessions for that newly created user returns a user-id of 0 as well.

moesasji · 12-04-2015, 05:20 PM

Quote:

Originally Posted by ponce

when you got the error you can check if you you have a consolekit session running

Code:

$ ck-list-sessions 
Session1:
        unix-user = '1000'
        realname = 'Matteo Bernardini'
        seat = 'Seat1'
        session-type = ''
        active = TRUE
        x11-display = ':0'
        x11-display-device = '/dev/tty2'
        display-device = '/dev/tty1'
        remote-host-name = ''
        is-local = TRUE
        on-since = '2015-11-30T16:52:23.487633Z'
        login-session-id = '4294967295'

Looking at this output I realized that you are starting the GUI from init-level 3. If I start XFCE4 using startx from the console I can indeed connect to wireless. In that case I also get the correct unix-user='1000' in ck-list-sessions.

The case where wireless doesn't work for me is if I use init-level 4 in combination with gdm; in that case ck-list-sessions list the wrong user, i.e. unix-user=`0` instead of unix-user=`1000`. However if I remove gdm from the system and use xdm instead (=init 4) things work and ck-list-sessions reports the correct user-id.

So the problem must be specific to installing gdm, but I don't see why.

A work-around that gives me wireless under gdm is to change line 109 in /etc/xdg/xfce4/xinitrc to:

Code:

# start xfce4-session normally
  ck-launch-session xfce4-session

This way wireless connects, but this isn't the correct fix as this starts up two sessions, instead of just one and hence gives problems with the power management. The output then is:

Code:

[hge@nova:~] $ ck-list-sessions
Session1:
	unix-user = '0'
	realname = '(null)'
	seat = 'Seat1'
	session-type = ''
	active = TRUE
	x11-display = ':0'
	x11-display-device = '/dev/tty7'
	display-device = ''
	remote-host-name = ''
	is-local = TRUE
	on-since = '2015-12-05T00:09:49.089822Z'
	login-session-id = '4294967295'
Session2:
	unix-user = '1000'
	realname = 'snip'
	seat = 'Seat1'
	session-type = ''
	active = FALSE
	x11-display = ':0'
	x11-display-device = '/dev/tty7'
	display-device = ''
	remote-host-name = ''
	is-local = TRUE
	on-since = '2015-12-05T00:09:49.304138Z'
	login-session-id = '4294967295'

Any suggestions how to properly fix this behavior would be much appreciated.

btw) This behavior still exists after installing the updates from the 3rd of December

moesasji · 12-05-2015, 12:31 PM

I start to suspect that the problem relates to cgmanager as I see the following message in /var/log/syslog

Code:

Dec  5 17:50:07 nova console-kit-daemon[1116]: WARNING: Failed to open connection to cgmanager. Is the cgmanager daemon running? 
Dec  5 17:50:55 nova NetworkManager[1134]: <warn>  disconnected by the system bus.
Dec  5 17:50:55 nova ModemManager[1240]: <warn>  Could not acquire the 'org.freedesktop.ModemManager1' service name

The warning from console-kit-daemon appears just before NetworkManager gets disconnected from the system bus. So it might be that ConsoleKit2 needs cgmanager to work properly in combination with gdm? This makes a it of sense as ConsoleKit2 started using cgmanager in the version that got into current on the 20th of November, which might explain why this is a new issue.

Topic with similar error-message as I see where running cgmanager fixes it, is here for manjaro

Unfortunately cgmanager in current is not up-to-date with fixes for similar issues in newer versions of cgmanager visible in the Debian bugtracker and moreover doesn't have a script in rc.d, which makes it a bit difficult to try.

edit) I've tested what happens if I uninstall cgmanager from my system and reboot. Doing so changes the error-message adding additional information that it can't find a file in /var/run/Consolekit, see attachment. So this problem really has something to do with cgmanager.

edit2) Without cgmanager installed ck-list-sessions no longer works, i.e. it gives a segmentation-fault. A very clear sign that cgmanager gets used.

Code:

[hge@nova:~] $ ck-list-sessions 

(ck-list-sessions:1788): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory.
This indicates a bug in someone's code. You must ensure an error is NULL before it's set.
The overwriting error message was: Error calling StartServiceByName for org.freedesktop.ConsoleKit: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Launch helper exited with unknown return code 127
Segmentation fault

ponce · 12-05-2015, 12:57 PM

if you want to try a newer cgmanager you can build one from the script here (that includes rc.cgmanager and rc.cgproxy init scripts pushed upstream by our Chris Willing)

http://ponce.cc/slackware/testing/new_cgstuff/

to enable it at boot don't forget also to apply the patch at the init scripts that you can find there and reboot.

but I think your problem is unrelated: I got the newer cgmanager already installed here and I got the same behaviour with gdm.
it might be because that has been kept back at a particular version (the newer ones require systemd) and now doesn't play well with the other newer stuff: it most probably would need patches but at a rapid look I wasn't able to find what breaks it.

the easier advice that I feel to give is to move to another display manager, like xdm, kdm or lxdm.

but consider that as you installed gdm (that is not a part of Slackware) as a part of MLED and you reported this problem first in the MLED thread, I think the most appropriate place to report and discuss this again is the new mailing list for the MLED project, see here

Quote:

Starting from now, the mailing list is the "official" MLED channel for getting help, reading announcements, discussing the project, etc. I won't answer any MLED-related questions here on LQ. Please use the mailing list for that.

moesasji · 12-05-2015, 02:10 PM

Quote:

Originally Posted by ponce

But consider that as you installed gdm (that is not a part of Slackware) as a part of MLED and you reported this problem first in the MLED thread, I think the most appropriate place to report and discuss this again is the new mailing list for the MLED project, see here

Thanks for the feedback Ponce. If you've tried it already it means I'm at the point where I need to give up as there is no clear way forward beyond moving to another login-manager that fits the criteria. Anyway by getting this far I learned a lot more about how things tie together, which was fun.

btw) I made this a separate thread as this same problem must also happen for gdm when build using the slackbuild from slackbuilds.org. In terms of subscribing to Kikinovak's new mailing-list; that is not my thing as I'm already drowning in far more emails than I can cope with in my day-to-day work.

edit) Just to confirm: upgrading cgmanager indeed makes no difference. The problem is indeed still there.

kikinovak · 12-08-2015, 06:19 AM

Quote:

Originally Posted by ponce

but consider that as you installed gdm (that is not a part of Slackware) as a part of MLED and you reported this problem first in the MLED thread, I think the most appropriate place to report and discuss this again is the new mailing list for the MLED project, see here

I partly disagree. My GDM comes straight from SBo and is only patched with my own artwork. So this isn't a totally wrong place to discuss it. I've noted it, and I suggest we discuss this eventually on the SlackBuilds.org mailing list. It's on my TODO list, and I'll investigate this further.

On a side note: Jeremy from LQ has been so nice to setup a dedicated Microlinux/MLED forum, and I've added a corresponding page on the MLED project site, so the die-hard Slackers don't get annoyed at users looking for MLED-specific help here. This will probably take a few days or weeks to settle, so I'm asking for a bit of patience.

Cheers,

Niki

kikinovak · 12-08-2015, 06:21 AM

Quote:

Originally Posted by moesasji

btw) I made this a separate thread as this same problem must also happen for gdm when build using the slackbuild from slackbuilds.org. In terms of subscribing to Kikinovak's new mailing-list; that is not my thing as I'm already drowning in far more emails than I can cope with in my day-to-day work.

Indeed, see my response to Matteo. As for mailing lists, that's what mail filters are for. I'm a member of several high traffic mailing lists, and that's never been a problem. Otherwise, use the new forum (see my post just above).

Cheers,

Niki