You are not logged in.
Hello!
I am running the following setup:
- NetworkManager
- SLiM
- Notion (Ion3 fork)
- No systemd
NetworkManager used to work fine, however a few weeks ago it stopped working. I cannot connect to new WiFi accesspoints anymore (or change the settings of already existing connections). Whenever I attempt to do so, I get the following error messages:
** (nm-applet:3145): WARNING **: Failed to add/activate connection: (32) Not authorized to control networking.
** (nm-applet:3145): WARNING **: Failed to add/activate connection: (32) Not authorized to control networking.ck-list-sessions gives me the following:
~ > ck-list-sessions
Session2:
unix-user = '1000'
realname = 'Henrik'
seat = 'Seat1'
session-type = 'x11'
active = TRUE
x11-display = ':0.0'
x11-display-device = '/dev/tty7'
display-device = ''
remote-host-name = ''
is-local = TRUE
on-since = '2012-08-30T02:58:24.348377Z'
login-session-id = '2'messages.log shows the following errors when starting nm-applet
Aug 30 11:07:26 localhost NetworkManager[436]: <error> [1346296046.568527] [nm-manager-auth.c:87] pk_authority_get(): Failed to initialize PolicyKit: (1) Error initializing authority: Could not connect: No such file or directory
Aug 30 11:07:26 localhost NetworkManager[436]: <error> [1346296046.578784] [nm-manager-auth.c:87] pk_authority_get(): Failed to initialize PolicyKit: (1) Error initializing authority: Could not connect: No such file or directoryThe user is in the wheel group. I know SLiM is deprecated, however simply using startx does not work either.
As previously stated, this setup used to work fine before. I suppose some update must have broken it. Any ideas?
Thanks in advance.
Last edited by hrkfdn (2012-08-29 19:14:52)
Offline
I would be interested to see your slim.conf, and .xinitrc.
I assume you have seen the NetworkManager ArchWiki entry. It details a problem that sounds like yours, but it looks like you have already taken the steps recommended in it.
Last edited by Morrad (2012-08-29 23:59:03)
Offline
it needs a polkit agent. install polkit-gnome and be sure that after logging into your destkop that /usr/lib/polkit-gnome/polkit-gnome-authentication-agent-1 is running.
Give what you have. To someone, it may be better than you dare to think.
Offline
I would be interested to see your slim.conf, and .xinitrc.
I assume you have seen the NetworkManager ArchWiki entry. It details a problem that sounds like yours, but it looks like you have already taken the steps recommended in it.
~ > cat .xinitrc
#!/bin/sh
xmodmap ~/.Xmodmap&
xbindkeys&
trayion -iconsize 18&
urxvtd&
nm-applet&
exec notion/etc > cat slim.conf
# Path, X server and arguments (if needed)
# Note: -xauth $authfile is automatically appended
default_path /bin:/usr/bin:/usr/local/bin
default_xserver /usr/bin/X
xserver_arguments -nolisten tcp vt07
# Commands for halt, login, etc.
halt_cmd /sbin/shutdown -h now
reboot_cmd /sbin/shutdown -r now
console_cmd /usr/bin/xterm -C -fg white -bg black +sb -T "Console login" -e /bin/sh -c "/bin/cat /etc/issue; exec /bin/login"
#suspend_cmd /usr/sbin/suspend
# Full path to the xauth binary
xauth_path /usr/bin/xauth
# Xauth file for server
authfile /var/run/slim.auth
# Activate numlock when slim starts. Valid values: on|off
# numlock on
# Hide the mouse cursor (note: does not work with some WMs).
# Valid values: true|false
# hidecursor false
# This command is executed after a succesful login.
# you can place the %session and %theme variables
# to handle launching of specific commands in .xinitrc
# depending of chosen session and slim theme
#
# NOTE: if your system does not have bash you need
# to adjust the command according to your preferred shell,
# i.e. for freebsd use:
# login_cmd exec /bin/sh - ~/.xinitrc %session
#login_cmd exec /bin/bash -login ~/.xinitrc %session
login_cmd exec dbus-launch /bin/bash -login ~/.xinitrc %session
# Commands executed when starting and exiting a session.
# They can be used for registering a X11 session with
# sessreg. You can use the %user variable
#
# sessionstart_cmd some command
# sessionstop_cmd some command
# Start in daemon mode. Valid values: yes | no
# Note that this can be overriden by the command line
# options "-d" and "-nodaemon"
# daemon yes
# Available sessions (first one is the default).
# The current chosen session name is replaced in the login_cmd
# above, so your login command can handle different sessions.
# see the xinitrc.sample file shipped with slim sources
sessions xfce4,icewm-session,wmaker,blackbox
# Executed when pressing F11 (requires imagemagick)
screenshot_cmd import -window root /slim.png
# welcome message. Available variables: %host, %domain
welcome_msg Welcome to %host
# Session message. Prepended to the session name when pressing F1
# session_msg Session:
# shutdown / reboot messages
shutdown_msg The system is halting...
reboot_msg The system is rebooting...
# default user, leave blank or remove this line
# for avoid pre-loading the username.
#default_user simone
# Focus the password field on start when default_user is set
# Set to "yes" to enable this feature
#focus_password no
# Automatically login the default user (without entering
# the password. Set to "yes" to enable this feature
#auto_login no
# current theme, use comma separated list to specify a set to
# randomly choose from
current_theme default
# Lock file
lockfile /var/lock/slim.lock
# Log file
logfile /var/log/slim.logdbus-launch is being executed because the changed login_cmd variable. ck-launch-session shouldn't be necessary anymore. there is an active ck-session and the dbus-daemon is running as well..
it needs a polkit agent. install polkit-gnome and be sure that after logging into your destkop that /usr/lib/polkit-gnome/polkit-gnome-authentication-agent-1 is running.
according to the wiki it doesn't. anyway, i have tried it. same problem:
~ > /usr/lib/polkit-gnome/polkit-gnome-authentication-agent-1
(polkit-gnome-authentication-agent-1:16096): polkit-gnome-1-WARNING **: Error getting authority: Error initializing authority: Could not connect: No such file or directoryit's really weird, because as i said before: this setup used to work just fine ![]()
Offline
hrkfdn:
Looking at your .xinitrc, there are a couple things you can try. Note that I have a similar setup to yours (slim, xmonad) that I only recently switched over to systemd. I link this in the hope that it may help.
First, even though you think you don't need ck-launch-session in your exec line, you may want to add it anyway just to see if it helps.
Next, try throwing the boilerplate at the top of my xinitrc sourcing all files in /etc/X11/xinit/xinit.d. This should also be in /etc/skel/.xinitrc.
There may be an error caused by the start order between dbus and consolekit. Consolekit needs to come up first. Check out the xinitrc entry on Archwiki for details (and the linked bug report, complaining about broken consolekit permissions).
Good luck. Let us know what happens.
Offline
hrkfdn:
Looking at your .xinitrc, there are a couple things you can try. Note that I have a similar setup to yours (slim, xmonad) that I only recently switched over to systemd. I link this in the hope that it may help.
First, even though you think you don't need ck-launch-session in your exec line, you may want to add it anyway just to see if it helps.
Next, try throwing the boilerplate at the top of my xinitrc sourcing all files in /etc/X11/xinit/xinit.d. This should also be in /etc/skel/.xinitrc.
There may be an error caused by the start order between dbus and consolekit. Consolekit needs to come up first. Check out the xinitrc entry on Archwiki for details (and the linked bug report, complaining about broken consolekit permissions).
Good luck. Let us know what happens.
I've tried all of your suggestions to no avail. I also made sure ConsoleKit is being started first. Same error messages in the log ![]()
As it says "No such file or directory" I am assuming there is a socket missing or something like that. It's not really being exactly verbose, though..
Offline
Damn.
One last thing to check: in your slim.conf, try changing your login_cmd to not use dbus_launch along with the changes to your .xinitrc that I suggested earlier.
Assuming this doesn't do anything for you, let me aim to get way more information (possibly too much).
Put your configuration back to how it was before (as you included previously), and then post (or pastebin and link) your:
/etc/rc.conf
Entire contents of message.log starting from a boot.
Same for ~/.xsession-errors
List of all groups you belong to on your system
List of all packages installed
Pacman log going back to a point where you know the setup was working
Anything else you feel may be relevant.
The answer is (probably) in there somewhere ![]()
Last edited by Morrad (2012-08-31 16:25:29)
Offline