OpenSUSE Install :: Cannot Open ConsoleKit Session: Unable To Open Session
Apr 11, 2010
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
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..."
Since doing an update (Kubuntu 10.04), this message appears when attempting to log in;
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 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".
Just installed Fedora 12 on a P4 IBM. Everything installed fine. Then, I rebooted, installed updates, and installed a few simple programs (emacs, ssh server). I rebooted since some kernel updates had been made. I can't login anymore. I get a brief message at GDM that says "unable to open session" after I enter my password. Root also doesn't work, but I figured out that root logins are disabled. I found something that recommended disabling selinux, so I reboot with selinux=0 parameter. That still didn't fix the problem, but did initiate selinux to re-label everything on the next boot.
My next thought was that maybe my password got corrupted, so I went into single usermode. I ran passwd justin, so I know that my password is correct. I still can't login via GDM or on a tty.
EDIT: I was also thinking I might need to uninstall something that I did; however, networking is disabled in single usermode, and if I init 3, then I get a login prompt that I can't open. Is there a way that I can enable root login? That might be a starting point to see if it's my user account or a general login problem.
After finally getting libptp2 to compile I find that ptpcam does not work. This has worked perfectly fine before with the same camera using Slackware 12.0, I am now using Slackware 13.1 and ptpcam will simply not work. The error is as follows:
x86_1# ptpcam -l Listing devices... bus/dev vendorID/prodID device model ERROR: Could not open session! Try to reset the camera.
I have tried to reset with "ptpcam -r", I have also tried to disconnect and reconnect the camera to the USB system, I have tried to reboot the computer, I have tried to use different versions of libptp2 -- all to no avail. The strace shows the issue is apparently a failed ioctl(), although I have no idea why it fails:
I have verified that the camera is working in Windows 7 on the same physical computer and I can see the camera from lsusb and dmesg output when I connect it to the USB system. This system is Slackware 13.1, Linux x86_1 126.96.36.199-smp #2 SMP Wed May 12 22:47:36 CDT 2010 i686 Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz GenuineIntel GNU/Linux.
I can follow instructions but can't make leaps of logic. I installed F14 and managed to get it working correctly on one of our laptops but when i installed xguest it created the guest account on the login but give me a "unable to open session" message when i try to log in.
i wanna use the x11-forwarding feature to connect me to an open session. is that possible? i have a linux-machine on which runs the jdownloader. the jdownloader is only as java-gui-only-tools available. so it runs always on a open x11-session on the linux-machine. i wanna configure this tool from everywhere. how can i make this? (if it is possible i wanna use x11-forwarding).
My server (CentOS 5.5) is a ldap client authenticate to LDAP server (Successfully authenticate) I use pam for ssh. I can ssh successfully with any users on system. But I cannot su - from ssh. It display the error: Could not open session. I look to log file and it shows: # tail -f /var/log/secure
After following a tutorial to install a pxe server for debian network install I can't log in my user session on gnome anymore
I got an error saying : /$home/.dmrc was ignored, can't save session and language the file must belong to the user and has persmission 644
I remember on my last session i got some icons on my home folder with a little lock icon on them i tried to remove them successfully using the command line but i still can't login. however i can successfully login with another user.
I am trying to install Fedora 14 or 15 into a 2008 R2 Hyper-V environment. I can successfully run the install and log into the system as a user. I need to install the integration components so the mouse works. However, I can't find a way to get a terminal window open so I can mount an .iso with the installers.
I stream my local police station dispatch on the web using an icecast/darkice configuration [URL]. The downside of using this software is that once you initiate darkice, a terminal has to be open - the process does not run in the background.
I tried placing a monitor on my server (ouch, that hurt) and keeping darkice alive that way, but my mail server kicks the process. Now, I set the KeepAlive variable to something outrageous and keep an ssh session open on my desktop box to keep the stream going. Screen does not work as Postfix boots that as well.
I have a question regarding runlevels, shutdown procedure and KDM. I am on a freshly installed Slackware64 13.37 multilib system. The default runlevel in /etc/inittab is set to 3: multiuser w/o X.
Now, I log in as root and issue the command:
As expected, KDM starts up, and I log in to KDE (or another WM/DE) as a normal users. When I am finished, I either issues
In Konsole or click on Shutdown in the KDE menu. The shutdown process is initiated, as expected, but then it stops, and a window alerts me, that there is a session open by user 'root'. If I click OK, the machine is finally shut down.
Now, if I interpret this correctly, the behaviour of Slackware64 13.37 has changed here, compared to 13.1. In previous versions, the root seesion was closed, when I changed the runlevel to 4 with the telinit command. Now, the session remains open, obviously.
My question is: Is this the correct behaviour, and isn't this a security whole? An unnoticed (!) open root session while I am surfing the web as an unprivileged user in KDE could be dangerous, I think...
Is it misconfiguration in my system, or is this the way it should be?
I'm using wmctrl on an Ubuntu machine to manage windows from a script, that I run inside a (gnu) screen.
If I start the screen session from the local machine, wmctrl works fine, including if I completely close the terminal window and issue the wmctrl commands when connecting to the screen remotely via ssh. Conversely, if I connect remotely with ssh and start a screen, wmctrl doesn't work (returns "Cannot open display") even if I attach that screen session locally from the Ubuntu Terminal.
I guess there is some hidden screen parameter that doesn't get set in a way that allows accessing the display when it's launched remotely -- any ideas what it is and how to modify it from within a remote ssh-screen session so that that the script can access the windows?