OpenSUSE Install :: "Could Not Acquire Name On Session Bus"?
Jan 27, 2010
After upgrading from 11.1 to 11.2 my gnome box starts with a message box stating "Could not acquire name on session bus" directly after the (successful) login.I'm not really sure which applications creates the message box since there is no title on the window.As far as I can see, the everything else on the desktop is fully operational.When investigating the problem I found some kind of recursive calls in the process table (ps -axf):
I'm experiencing a problem when trying to use VNC on my desktop box. Whenever I try to connect, I get a gray screen with the error "could not acquire name on session bus".I've searched the forums, but after trying several solutions, nothing has seemed to work for me.My xstartup file looks like this:
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.
Although Im using SuSE since 7.2 this is my first forum post here. I just plugged in my iPhone with USB and 11.4 created an eth1 interface for the iPhone and also loads the ipheth kernel module. Anyhow I am not able to acquire an IP address using DHCP. The iPhone OS is 4.2.1 and its an iPhone 3G 8GB black
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'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 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".
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 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
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.
I 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.)
I 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).
Need explanation about low level (like assembly level) memory management? Such as, how does a process acquire more memory, sharing memory among processes, etc. I don't want to know how to use malloc or other library functions, but more along the lines of how an example malloc implementation would acquire memory.
Due to all the "fun" I had upgrading spamassassin from 3.2.5 to 3.3.1 on C55 I thought I would detail it here so as to possibly save others from all the frustration I have endured. There are probably a zillion different ways to make this work but this is how I did it and it seems to work well.
1) Acquire spamassassin rpm. I downloaded several different versions from various sites and had problems with all of them so I ended up grabbing the SRPM from Fedora 13 spamassassin-3.3.1-2.fc13.src.rpm. This of course will not load onto C55 as rpmbuild has changed so I loaded it onto a FC13 box and then TARed the SPEC & SOURCES directories, copied them onto a C55 and built SRPM from there.
2) Install on C55 The new spamassassin requires several updated packages to make it happy. a) perl-Mail-DKIM greater than 0.31. I cheated and used this one from FC8 perl-Mail-DKIM-0.32-3.fc8.noarch.rpm b) perl-socket6 that is 2.0 or later. I got this one from DAG perl-Socket6-0.20-1.rf.x86_64.rpm c) perl-NetAddr-IP that is 4.0 or later. Again DAG saved the day perl-NetAddr-IP-4.007-1.rf.x86_64.rpm d) the spamassassin of course :) Actually I built them from the SRPMs as I needed both the 32 and 64 bit packages for various servers.
3) Run sa-update --D to get the latest rules then restart the spamassassin service. For those who do not have access to a FC13 box you can get a copy of the SRPM I made here [URL].
On 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:
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".
For 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.
I've just moved from Ubuntu 9.04 and installed 10.04. I have 5.1 sound set up and selected the Analogue Surround 5.1 in the hardware selection. I'm using on board sound so i have the correct device selected. I have sound but my problem comes when trying to adjust the balance and sub etc. I can move the subwoofer on its own and set the fade on its own but if i try to change the balance the fade moves with it (not always in the same way, sometimes it fades to the rear, some times to the front). Also, when i move the master volume the subwoofer level follows it.Is there a fix for this problem?
Also how can i acquire the sound drivers and settings panel that where in 9.04 if not? will they still be comparable with 10.04?
I am running 6 servers on RHEL4.4 with oracle databases and application on HP ML370 hardware. Since initial installation, I have not applied any patch updates. I would like to start practising Patch Management and would like to know how to start and how to do it. For security reasons, I am not allowed to connect the servers to RHN or RHS hence will appreciate other options of acquiring patch updates in bundled form say on a monthly basis.
I setup the dnsmasq in debian squeeze as dhcp and dns server, for the debian host i assigned the static ip addresses, and configured the xp for dhcp. Windows XP network can't acquire DHCP address from debian squeeze with this error:
Quote:
error unable to contact your dhcp server Request has timed out.
this is the tcpdump output in debian for the xp network:
Quote:
15:12:10.631635 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:07:e9:a8:ea:93 (oui Unknown), length 300 15:13:16.611793 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:07:e9:a8:ea:93 (oui Unknown), length 300 15:13:16.611793 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:07:e9:a8:ea:93 (oui Unknown), length 300 15:12:42.631730 ARP, Request who-has 169.254.202.161 tell 169.254.202.161, length 4615:12:44.613568 ARP, Request who-has
