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".
when i start my pc i have an error: Consolekit session error, unknown return code 0 when i click Ok it then starts my session
View 7 Replies View RelatedI 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..."
Here are some logs
syslog
Code:
Code:
My Fedora 12 box got that error after some updates on it.
I can login but it's prompting that error and everything will be a black space.
But still no good.
According to the log messages, the ConsoleKit session isn't initializing. I can't paste the logs here coz it's on another laptop.
I could think of just upgrading it to Fedora 13 but there's no way I can backup all of my files on it. Is it just safe to upgrade it?
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 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.
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
View 1 Replies View RelatedI am having a brain fade, I have an putty session connected ( X11 forwarding enabled) what is the command to start a gui session ( Opensuse 11.0).
View 3 Replies View RelatedI'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.
What do I need to do to fix this issue?
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?
View 4 Replies View RelatedI 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.
View 3 Replies View RelatedI got a workstation with openSuse 10.3 pre-installed. After I did the Online Update from YaST2 and rebooted the machine as requested by YaST2, the system came to fail starting up an X session.
Below are excerpts of the message appeared on the screen at the end of the boot process. (I transcripted it from the screen by hand.)
Code:
Waiting for mandatory devices: eth1 __NSC__
10 9 8 7 5 4 3 2 1
eth1 devices: Intel Corporation 82573L Gigabit Ethernet Controller
eth1 DHCP4 client (dhcpcd) is running
[Code].....
what is causing the failure of the X session and how to fix the problem? I would be glad if you give me any hints or pointers.
I would like to know which command should I enter in the execute dialog (opened with Alt+F2) so the dialog to close session and change the user opens.
View 5 Replies View RelatedI installed openSUSE 11.4 on HP elitebook 2560p few days ago (using KDE live CD). In general system is working fine, but steel I cannot resolve couple of really annoying issues: 1. I've created encrypted partitions for swap and home during OS installation. As result the system keep asking for passwords for each of encrypted partitions before show login screen. That leads to situation when I have to type 3 passwords during each boot/reboot. I was using the same configuration (swap and home were encrypted) on Ubuntu 11.04 and there both encrypted partitions were mount automatically with no password typing after login to the system. Could you please tell how I can configure the same behavior on openSUSE 11.4 ?
2. I've enabled auto screen lock after 5 mins being inactive. As result when I going back to laptop and to unlock the screen the system shows login screen (default login screen with user selection). But when user and password filled in I click login it creates entire new KDE session. Therefore all staff that was open before screen lock is gone. However old session is still in the system (it appears in output from 'w' command).
i want to upgrade to 11.2, however, i am very cautious about losing my files. there are files on this system which i absolutely can not afford to lose, and they are only on this system. which method of upgrade will be the best, best as in safest.
View 9 Replies View RelatedIs it possible to use the upgrade feature of 11.3 to upgrade from 11.0?
View 9 Replies View RelatedI usually run the default gnome session but also installed kde and enjoy popping over every now and then.
Now, after the lucid upgrade, things are not happy. There is just a black screen after the login.
My cairo dock comes up, but no other panels.
The only other thing I see is TokBox.
Not a pretty sight at all.
I cannot start the desktop session: After upgrading from 10.04 to 10.10 (dual-boot system) via Alt+F2 as suggested on [URL]. Grub loads fine after reboot (booting Windows works, Upgrade without errors). If I boot Ubuntu (no matter which Kernel, etc.), I end up in shell (black screen + prompt, stating the new Ubuntu version) and being asked to log in. Entering my name and pw results in the shell prompt changing to my name, but nothing else. So how do I start the desktop session? Repairing packages had no effect...
View 5 Replies View RelatedHardware:Asus A8V Mainboard - Via Chrome9 Onboard K8M890(CE) ChipsetAdditional PCIe Ati/AMD Radeon HD 2400 Pro Graphics Card.Two Keyboards, two Mice. Three Monitors.So this is a heterogene (Via+Ati) Multiseat environment with 3 Monitors. (the Ati uses two by its own )I followed the following howto:http://multiseatonlinux.blogspot.com...g-up-base.htmlSoftware: Ubuntu 10.4 Modified Packages: consolekit gdm libck-connector0 libpam-ck-connector libck-connector-devBut Martijns howto doesn't work here. Either it's one Screen online or none.I had to tweak Martijns configuration to get it running.xorg.conf:Instead of two configs for two layouts I created one xorg.conf holding two different layouts.ConsoleKit:I have to use the original /etc/ConsoleKit/displays.d/Local.display.Else I get an error in Xorg.x.log:
Code:
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 9, (OK)
[code]....
is ther someone so gentle to tell me if the two desktops i have installed on my machine, which are the hardy heron gnome and kde are two separate identities? i need to know this as today i was offered by the update manager in kde to upgrade to the new release. i do not know if upgrading the kubuntu side, will affect and perhaps mess up the ubuntu side too. can i upgrade to the new release or have i better to wait for the next long term release of ubuntu?
View 2 Replies View RelatedOn my 11.3 desktop I was annoyed by what I thought was the screen saver locking my session after an idle period, requiring my password to unlock. Well, I didn't want this behaviour and it wasn't supposed to do that, I had disabled every place in the desktop configuration that seemed to be related. I even looked into the KDE4 rc files with a text editor and they all seemed to be in order.
Eventually after some searching I found the answer: It's the setting "lock screen on resume" in the advanced settings > power daemon. Once I turned it off, it was fine; this desktop doesn't need suspend+resume anyway.
It seems that this is not a case of counterintuitive naming; it seems that in some configurations there is a bug where a stray event can trigger a screen lock by the powersaved (?). I don't really understand it, but you can start your investigation here if you are interested:
KDE4 screen lock problem
I was about to test the new KDE 4.7 on my (default Gnome machine.) All I did was the following:
1. Add some repositories:
Core: Index of /repositories/KDE:/Release:/47/openSUSE_11.4
Extra: Index of /repositories/KDE:/Extra/KDE_Release_47_openSUSE_11.4
2. Go in to Yast; Software Manager.
3. Change the dropbox originaly set to "Groups" in the upper left corner to "Pattern". Voila; There you have two nice and tidy options to check both "KDE Base System" and "KDE Desktop Environment" However: Once I check the KDE 4.7 Base System I get a dependency break. The missing part is "kdebase4-session >= 4.7.0".
Of course I can probably go out and find this somewhere else. But I thought it would be better to add it to the repository for future users. Maybe there is a legitimate reason for it to not be there at this moment - or maybe someone just forgot to put it there. Probably this is not an issue if you are upgrading from a previous KDE environment, maybe this package has been distributed before? This is probably not the correct place to put this info, what I really wanted to do was to send in a "bug report" or something similar.
Note: There is no Dependency break once checking "KDE Desktop Environment".
Does anyone knows how to do this for all users with one command?Or which file i have to edit to do this?
View 9 Replies View RelatedFor a while now whenever I log off/shutdown I always get a dialogue asking me to abort an active session.Its a root user session on vt3. The strange thing is I can not get to that session for love nor money, going to tty3 I just have a login prompt, I've tried logging in and then logging out but whenever I go to close down again I always get the same dialogue.
I've only just noticed recently that on the login screen (KDE) In the Menu > Switch User dialogue I have the option to switch to a root session on vt3 or the current graphical session on vt7. Yes, I've tried switching to the session there on vt3 and again same as above when switching manually to tty3.
I've recently upgraded from 11.0 to 11.2 64-bit, this is one of the issues I was hoping to get rectified in the upgrade, but I think instead a setting/lock file must be causing confusion somewhere.
Somehow we are at the new stage hal deprecated and its changes is not easy for newbies to follows. also changing sudoers is a dirty and not safe trick So: The need for zenity script with these feature:
@ Consolekit
@Logout
@shoutdown
@restart
@suspend
@my be cancel
is really being felt. So if someone how is able to change the old zentiy openbox script comes forward and do the job;
I was running 8.something on my ubuntu server. Today I decided to upgrade releases! So I started it, all via ssh cos the box is about 800 miles away and it was going just fine. However - I went away from the pc for about a hour, and my ssh session died. On reconnect it starts a new ssh session - and I dont know how to reconnect to the upgrade process and finish it off.
View 9 Replies View Related