OpenSUSE Install :: Warning: Cannot Open ConsoleKit Session
Dec 28, 2010
I am currently running Suse 11.3. I continue to get the following error when logging into the KDE login manager with my user account
"Warning: Cannot open ConsoleKit session: Unable to open session. The name
org.freedesktop.ConsoleKit was not provided by any .service files."
After acknowledging the error, it resets back to the login manager screen. If I login with root, I get the same message, but it continues on and logins into the session
The following message comes up when I boot up: Logging in user Warning: Cannot open ConsoleKit session: Unable to open session: Launch helper exited with unknown return code 0. When I press OK, the system completes the start up and everything looks normal. But when I try to connect to internet, I get the following message:
KNetworkManager cannot start because the installation is misconfigured. System DBUS policy does not allow it to provide user settings; contact your system administrator or distribution. KNetworkManager will not start automatically in future. If I reboot the system, I logg in successfully. So far the problem has appeared approximately upon every second time I boot up. Rebooting the system seems to take care of it.
Don't know what info is of interest. I'm using
Opensuse 11.2 KDE 4.4.2 (Factory) After upgrade from 4.4.1 to 4.4.2 it worked fine for a week or so.
I do a clean install of slackware64 13.1 beta1 with KDE and switch default runlevel to 4 in /etc/inittab.
I try to login in kdm, I always come back to the login....
I try this with default runlevel 3 and an .xinitrc with "ck-launch-session startkde" .. works without problems, so I switch back to default runlevel 4, now i can login and only get the error "Cannot open ConsoleKit session: Unable to open session..."
I have upgraded suse from 11.3 to 11.4 as described here (command line) SDB:System upgrade - openSUSE.
When I rebooted computer I get message: "Loggining in myname Warning: Cannot open ConsoleKit session: Unable to open session: Lunch helper exited with unknown return code 127" The same problem is in safe mode. Mouse and keyboard are "death".
Since doing an update (Kubuntu 10.04), this message appears when attempting to log in;
Quote:
Warning: cannot open ConsoleKit session: Unable to open session: the permission of the setuid helper is not correct.
After clicking ok on the above warning, the system logs in, but gives 2 error messages;
- removed sound devices
- KNetworkManager cannot start because the installation is misconfigured. System DBUS policy does not allow it to provide user settings. contact your system administrator or distribution. KNetworkManager will not start automatically in future.
I just reinstalled my OpenSuse 11.3 with the GNOME desktop. As soon as I was done installing and I was on a fresh desktop, I installed the Yast updates that were available, rebooted, and now I can't login to any of my User accounts. Whenever I try to login, it tells me that it is "Unable to Open Session".o any of you know how I can fix this without having to reinstall all over again
I upgraded to Slackware 13.37 following the instructions in UPGRADE.TXT and now Firefox, Thunderbird, Seamonkey and Google Chrome all fail to run. If I start them from the command line, I get:
Code:
/usr/lib/firefox-4.0.1/firefox-bin: symbol lookup error: /usr/lib/libgio-2.0.so.0: undefined symbol: g_cclosure_marshal_VOID__VARIANT libgio appears to be there:
Code:
root@shannon:/home/tsgilvary# ls -l /usr/lib/libgio-2.0.so.0 lrwxrwxrwx 1 root root 22 May 21 19:51 /usr/lib/libgio-2.0.so.0 -> libgio-2.0.so.0.2800.6
I'm also getting an error message logging into KDE that says "ConsoleKit could not be started. ConsoleKit returned an unknown error of 127" which may or may not be related.I have tried uninstalling and re-installing Firefox through slackpkg. I have also tried reinstalling the glib2 package, also through slackpkg. I ran slackpkg clean-system and removed anything I didn't install myself (lmms and openoffice remain). No joy.
For example, the gparted application menu item doesn't work; using it means that there is almost no filesystem support. The only way to get it to work is to open a terminal, run 'su -', and then open it from there.As another example, I tried creating a nautilus script to open files as root with a command like this:
Code:
for uri in $NAUTILUS_SCRIPT_SELECTED_URIS; do gnomesu -c "gnome-open '$uri'" done
When I try using it, it just fails. Typing out the command in the terminal gives this (tested on a text file):
Code:
No protocol specified (gedit:13672): Gtk-WARNING **: cannot open display: :0
I'm pretty sure the problem is that it's granting privileges, but not using the full root environment, or something along those lines.
I've been searching for a permanent solution for some time now, but the threads containing the same error message never seem to be about the same issue.I want to:I'm not trying anything fancy, all I want to do is open a write-protected file with gedit as root, like so:
Code:
# sudo gedit /usr/bin/deadbeef
..but every time I try, no matter the file, I get this error message:
Code:
(gedit: [process #] ): Gtk-WARNING **: cannot open display
I already know: I can circumvent this by going:
Code:
# xhost +local:root # sudo su # export DISPLAY=:0.0
Gnome Forum have told me that changing the appearance of gdm I run: sudo -u gdm dbus-launch gnome-appearance-properties but I get this error: (Gnome-properties-Appearance: 18 047): Gtk-WARNING **: can not open display:
I have installed virtualbox on opensuse 11.2 64bit.
When I go to open a machine it says
"Failed to open a session for the virtual machine Windows XP. The virtual machine 'Windows XP' has terminated unexpectedly during startup with exit code 1."
" Result Code: NS_ERROR_FAILURE (0x80004005) Component: Machine Interface:
[Code].....
as root. Users of Ubuntu, Fedora or Mandriva should install the DKMS package first. This package keeps track of Linux kernel changes and recompiles the vboxdrv kernel module if necessary."
I have been updating my system and making a few changes and now I have a serious problem with GNOME (as far a I understand). In the Desktop if I try to start some applications such as the text editor gedit it crashes and won't start. Some applictions start from the menu some don't (e.g. services) and others start and then crash if I try to example manipulate them (e.g. open a file in openoffice).
In the case of gedit if I try to run it from the command line as root I get the following
# gedit
(gedit:6475): GnomeUI-WARNING **: While connecting to session manager: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed.Illegal instruction [code]....
When I try to start the services (i.e. /usr/bin/system-config-services) I get:
I have installed ubuntu Server 9.10 [ubuntu-9.10-server-i386]in ma machine. After giving the command startx i couldnt goto gui . It saying x session : warning: x rdb command not found resource not merged.
Have you guys had this weird nautilus error? When I su to root and run "nautilus" in terminal, errors popped out:
Code: (nautilus:3979): EggSMClient-WARNING **: Failed to connect to the session manager: None of the authentication protocols specified are supported(nautilus:3979): Eel-WARNING **: GConf error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
I've recently installed Fedora 14 (x86_64) on my Alienware m15x laptop which has a NVIDIA GTX 260m onboard. Now I have followed leigh123linux's guide to installing those drivers on F14. The installation is a success and everything seems to be in working order, until the system randomly logs the user out and/or restarts the session with no warning. The screen goes black and the nvidia logo appears and then its back to the login screen again. This can happen many times with no apparent stop insight. This does not happen with the default F14 drivers that come with the installation, I have tried several re installations of the Fedora OS and several re installations of the NVIDIA driver, i still have the same problems.
I'm a new openSUSE user. Thought of giving some other distros a try, so I started with openSUSE.
I installed the Xfce packages and when I went to go install a panel plugin, it said that it needed to install some other stuff, including an update of xfce4-session to xfdesktop. After I did this, I could no longer see 'Xfce session' in the "Sessions" part of the log-in menu when I tried to log-in again.
I need some help install and configure my vnc session at my Opensuse.
Right now I have installed nx client which works fine and is listening on port 5901.
I also want vnc to use when I want to check exactly what is going on my work's computer (when I go home)
I am reading the tutorial here:
And I would like to ask you the following
1.
Code:
For VNC client connection remember to open ports 5901-> in the firewall. (1 port/Xsession.) nxserver is listening to 5901. How to configure vnc to listen to 5902.
2. The guide also refers that
Code:
Here we "Prestart" vnc sessions for specific users, therefore no login screen is presented. This uses more resources as the VNC Session is running even when no client is connected to the session watching it. But there in lies it's advantage, "watching a session" and "using a session" are not the same thing! This method is very usefull for starting long running programs before going home. Once home you can re-connect to the session and see how things are going.
I usually shut down openSUSE in KDE by clicking the shutdown icon and selecting "Turn Off Computer". When I boot back into openSUSE, my session resumes automatically without it asking for my password.While I don't mind KDE resuming my session because it saves time, me not having to reenter my password is a security risk. How do I turn off the autologin?
I was working normally and the GUI just failed, all I could still see were any open windows. I rebooted the machine from tty1 and now I can't login anymore under my normal user accounts.
I enter my credentials, it appears to login, and immediately goes back to the login screen. Note that under tty1 I can still login with my user account and do everything.
I can still login with root in the gui.
/var/log/messages says this
Code:machine checkproc: checkproc: can not get session id for process 9839!
I've got a somewhat anemic box, resource-wise, set up in the office where any authorized user plus a guest account can log on. Guest is tightly restricted, but we get a lot of people passing through who need one-time or occasional access - this isn't the big problem. What's causing me problems is that a user will log in, walk away or go to the john and the screen locks. Next user (or this one comes back) and winds up doing another login. At the end of a week or so, I may have a couple of dozen sessions listed when I ask for "users". Since some of these session contain open applications they eat up an awful lot of a marginal amount of available memory. How do I kill the entire session (as root) for a user? Gotta be simple but it's not obvious to me.
