Hi – I have openSUSE 12.2 with KDE 4.8.5 “release 2”. I updated my installation today with the usual “zypper dup” and got about 30-40 changes, I didn’t really look to see what was coming in, I assumed just the ususal stuff to fix bugs in a new release of 12.2
After that, every 1/2 hour or so the screen flips out and I end up at the KDE login screen.
It has happened in the following situations:
when I go to the website of my local post office in Goole Chrome (repeatable)
when the screensaver comes on (repeatable)
when I lock the screen to take a break (repeatable)
spontaneously while I’m not operating anyting at all (repeatable)
spontaneously while I’m working at the keyboard (repeatable)
On 09/18/2012 05:56 PM, nightwishfan wrote:
>
> Try to look in ~/.xsession-errors~/.xsession-errors.old
> /var/log/Xorg.0.log and /var/log/Xorg.0.log.old for info.
>
>
Aha. Your post showed concern re xsessions and xorg. And the file
…xsession-errors had all sorts of warnings (that I didn’t understand).
All of that prompted me to reinstall Nvidia drivers. And that fixed it.
Thank you a lot (because I need the computer so I was going to flip to
my stored image of 12.1 till I could sort it, which would have made me
unhappy deluxe).
On 09/18/2012 09:16 AM, swerdna wrote:
> the usual “zypper dup”
zypper dup is not “the usual” way to run in “usual stuff to fix bugs”
for a non-Tumbleweed system…but, i know you know that, but maybe the
next person to read this thread will think "hey i been doing it wrong,
this moderator says it is the usual way!
these are the usual ways to update openSUSE 12.2:
zypper patch
YaST Online Updater
the mail list just mentioned that factory is hosed…so, if you have any factory repos enabled you are probably gonna need to reset all
your reops to sane settings and then do a zypper ref and then zypper dup
to get back to 12.2
if you have no factory then i don’t know except to say you can back
level all the updates you duped in…this should give you a list to
consider:
tail -n50 /var/log/zypp/history
but that is only 50 lines long, be sure to look at all of “today’s”
dated packages…
Good point dd, it was a bit reckless, particularly since I didn’t have a good look at the info zypper gave me before I pulled the trigger. Probably most folk should use Yast Online Update as you suggested.
For readers: this error was not due to how the update was done, it was probably due to badness in the repos (whatever that means).
John, in yesterdays updates I saw the package xorg-x11-server. It replaces some of the symlinks created by the NVIDIA driver install. Since I read another post describing issues which seemed X related to me, I decided to immediately perform a reinstall of the NVIDIA kernel module package. Which resulted in no errors/weird behaviour at all.
On 09/19/2012 07:36 AM, Knurpht wrote:
>
> John, in yesterdays updates I saw the package xorg-x11-server. It
> replaces some of the symlinks created by the NVIDIA driver install.
> Since I read another post describing issues which seemed X related to
> me, I decided to immediately perform a reinstall of the NVIDIA kernel
> module package. Which resulted in no errors/weird behaviour at all.
>
>
I noted when I re-installed Nvidia that it gave me a complain message
about symlinks and then the Nvidia installer replaced them. That’s
exactly the issue — case solved – thanks Gertjan