On 04.08.2011 16:27, Greg KH wrote:
On Thu, Aug 04, 2011 at 01:26:00AM -0700, seso wrote:
I had a similar situation - It was not X that was prevented from startup (kdm launched) but logging in with my user just threw me back immediately at the login screen.
In $HOME/.xsession-errors I found the cause - it was libassuan .
libassuan has been updated in tumbleweed and the kde packages in tumbleweed seem to require that new version - or KDE crashes immediately. In my case, the lib was still from the standard opensuse repository. After installing the tumbleweed one, login worked again.
Why wouldn't you have installed the tumbleweed one? You always have to do a 'zypper dup' with Tumbleweed, where some packages move to the Tumbleweed repo as needed (like in this case, it was required.)
So a simple 'zypper dup' should solve this, right?
Why aren't people updating in this manner in the first place?
thanks,
greg k-h
I just found that preserving older kernels in addition to the running one has influence on what gets updated. I tried to change everything to use tumbleweed repo. There were a lot of kernel related conflicts, so I canceled. I uninstalled all (two 2.6.39-versions) older kernels, devels, sources, preload... After this YaST started updating like over a hundred packages from tumbleweed repo. Vahis -- http://waxborg.servepics.com openSUSE 11.2 (x86_64) 2.6.31.14-0.8-default "Evergreen" main host openSUSE 11.4 (x86_64) 2.6.37.6-0.7-desktop in VirtualBox openSUSE 11.4 (i586) 3.0.0-39-desktop "Tumbleweed" in EeePC 900 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org