gnome logs out after pause? [feisty]
John Dangler
jdangler at atlantic.net
Sat Mar 10 17:21:20 UTC 2007
On Sat, 2007-03-10 at 12:12 -0500, Matt Price wrote:
> On Sat, 2007-03-10 at 11:19 -0500, John Dangler wrote:
> > On Fri, 2007-03-09 at 23:18 -0500, Matt Price wrote:
> > > On Fri, 2007-03-09 at 18:33 +0000, Gabriel Dragffy wrote:
> > > > > > also found this in Xorg.0.log.old (but none of the other Xorg*log*
> > > > > files, oddly enough: > >> SetGrabKeysState - disabled >> >>
> > > > Backtrace: >> 0: /usr/bin/X(xf86SigHandler+0x81) [0x80c5d81] >> 1:
> > > > [0xb7f60420] >> >> Fatal server error: >> Caught signal 11. Server
> > > > aborting > > any hints? thanks, > > matt > >
> > > >
> > > > I think the general consensus would be that you are running pre-release
> > > > software and would expect problems. Your best bet would be to search
> > > > launchpad.net for similar issues. If you don't find any then you could
> > > > report a bug, describe the problem, attach info such as you posted
> > > > above, the output of lspci -vv and lspci -vvn, and logs from /var/log
> > > > and see if others can reproduce it.
> > > >
> > > ok, did some more testing/searching and i don't think it has much to do
> > > with running beta software; it's due to a known xorg bug which was fixed
> > > upstream a while a go, which affects all 3d stuff under certain
> > > conditions, which seem to be attained more easily and reliably under
> > > gnome than under other desktops. in my case, the 10-minute crash cycle
> > > was almost certainly caused by the SCREENSAVER coming on (!) and tryng
> > > to execute some 3d code. i've disabled the screensaver and i thnk it
> > > will work fine now. of course, this means all 3d stuff is broken on my
> > > desktop -- a total bummer. some references are:
> > > http://www.nvnews.net/vbulletin/showthread.php?t=78275 (esp #9), which
> > > details some xorg.log errors you might see )
> > > http://forums.suselinuxsupport.de/index.php?showtopic=50585
> > > http://forum.beryl-project.org/viewtopic.php?f=47&t=2258 (suggests
> > > starting beryl with --force-nvidia, which i haven't done; may or may not
> > > work, doesn't solve the broader problem)
> > > https://launchpad.net/ubuntu/+source/xorg-server/+bug/60288 (ubuntu bug
> > > report)
> > > https://bugs.freedesktop.org/show_bug.cgi?id=8537 (the upstream bug)
> > > https://bugs.freedesktop.org/show_bug.cgi?id=1753 (or maybe this is
> > > really the upstream bug?)
> > > http://ubuntuforums.org/newreply.php?do=postreply&t=354697 (a recent
> > > forum thread with reports from edgy and feisty users)
> > > http://linuxfud.wordpress.com/2006/09/29/ubuntu-crashes-on-start-and-returns-to-the-login-screen/ (a similar issue )
> > > http://gnomesupport.org/forums/viewtopic.php?t=12299 (another indication
> > > this is a gnome-specific issue, even if the bug is really in xorg)
> > > http://bugs.beryl-project.org/ticket/684 (beryl discussion of this bug)
> > >
> > > hope this helps someone else, i have a workaround (don't run any 3d, and
> > > make sure screensaver is diabled) but am not wholly satisfied.
> > >
> > > matt
> > Matt~
> > I wasn't either. I lived with that mess under Dapper for the longest
> > time, and narrowed it down to a couple of screensavers (which I
> > removed). I eventually turned off the screensaver (as you did), since I
> > never got a satisfactory answer from anyone else on this.
> > >
> > >
> >
> i seem to have more or less figured everything out now -- though i guess
> that the bug is IN xorg, it can be triggered by nvidia's nonfree driver
> relatively easily; but whatever the difficulty is, reinstalling the
> nvidia driver can fix it, at least temporarily. I think this may also
> locate the cause of longer-term problems I had in diagnosing and fixing
> problems with nvidia on this laptop from dapper onwards, including
> problems with suspending the laptop. so you mighyt want to try that, at
> least if you're using nvidis.
>
> but of course it al depends on what exactly you're doing that activates
> this particular bug -- which hopefully will in any cae be fixed soon in
> feisty.
> matt
I did the same thing. I reinstalled an updated version of the nVidia
driver, built a new nvidia kernel, and installed it, but it didn't help.
Since I'm not big on screensavers anyway, I just turned them off. I'm
on Edgy now, and haven't seen the problem (mostly because I shut off the
screensaver immediately after the install), but it would be nice to find
a permanent fix for this, since eventually I've switched all of my
machines to Ubuntu, and I'd like to have either a screensaver and/or
lockout on my office system.
>
> >
More information about the ubuntu-users
mailing list