Meerkat freezes when idle and corrupt after reboot

Asked by iapx86

Same exact problem with both 32 and 64 bit 10.10 Maverick Meerkat on Lenovo T61.

This problem is being entered into this forum using
an ubuntu 32 bit 9.10 launched from a different hard disk on the same Lenovo T61
which has been operational without problem since 9.10 was published.

Two completely different installs on the same T61 over several days:
ubuntu-10.10-desktop-i386.iso
ubuntu-10.10-desktop-amd64.iso

common install sequence:
completed standard install from CD
completed System>Administration>Update Manager
completed synaptic install of a few python libraries
completed install of gvim and a few other utilities
completed install of truecrypt
modified fstab to mount network drives

32bit install:
completed install Oracle VirtualBox
used clones of existing Sun VirtualBox disks that work without error on ubuntu 9.10

64bit install:
completed install KVM
generated two virtual disks with working systems

What goes wrong:
After system is stable and working perfectly
The machine is left idle for a significant period of time (many minutes).
When activity resumes, the screen is entirely black with a mouse cursor that works.
If the time has been short, the login:password box appears, and all is well.
If the time has been long, no keyboard or mouse actions make the box appear, ever.

What has been tried:

Keyboard input:
Basic: Left, Right, Up, Down, Backspace, Delete, F1-F12, Esc, ThinkVantage, each alphanumeric key, all alphanumeric keys
Ctrl: with Basic
Alt: with Basic
Ctrl-Alt: with Basic
and everything else I could think up.

Mouse input:
Left button, middle button, right button, multiple buttons.

Lid:
Closed and opened quickly
Closed for a minute and opened

Power button:
Tap, Press and Release.
Finally, Press for 5 seconds to force power off.

What happens after power is back on:
Everything appears normal at first.
No virtual machines are launched.
After some minutes, maybe half an hour of python development, without idle time,
* gvim fails to save a file,
* task bar disappears and cannot be invoked,
* .viminfo disappears
* application title bars disappear
* desktop icons disappear
* application menus still work
* Ctrl-Alt Left, Right fail so screen navigation is unavailable
* nothing else works
The only plausible action, holding power down for 5 seconds, is the only remedy.

What happens after power is back on the 2nd time:
Files are missing, system is untrustworthy.

Causes considered:
Screen Saver, Suspend, or Hibernate may have some flaw exposed on my T61.
File system may have not flushed, and is in an unrecoverable state when power is cycled.

Since many days of experiments have been performed trying to identify and avoid the problem,
I have come to distrust 10.10 on my T61 for now.
I appeal to the community to inform me how to configure and use 10.10 with trust.

Things I will do in anticipation of your response:
The T61 10.10 disk will be reinstalled from scratch with KVM and some synaptic module installs
then I will reboot back to 9.10 and wait for advice.

Question information

Language:
English Edit question
Status:
Open
For:
Ubuntu ubiquity Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
delance (olivier-delance) said :
#1

Could you disable screen saver ? Or at least check you have any power saving option, except screen.
VirtualBox is, which is normal for an hypervisor, intrusive about kernel and can introduce such bug.
I'm using 10.10 without any problem with VBox 3 and now 4, but have not the same hardware configuration.
You could also you check behaviour of LTS 10.04 which is a long term version.
When you have issue, could you also try Ctrl+Alt+F1 and report if you get a terminal with a prompt.

Revision history for this message
Sam_ (and-sam) said :
#2

Try running it without visual effects.
Disable compiz (Visual effects=None), mentioned there.
http://ubuntu-ky.ubuntuforums.org/showthread.php?p=7129470

If this is your laptop
http://www.lapspecs.com/wiki/lenovo+thinkpad+t61
these pages may incl. some useful hints to look up.
http://www.linlap.com/wiki/IBM-Lenovo+Thinkpad+T61
http://www.thinkwiki.org/wiki/ThinkWiki

Enough swap and RAM?
http://kubuntuforums.net/forums/index.php?topic=3114933

Maybe installing 'hibernate' helps.
http://packages.ubuntu.com/maverick/hibernate

> Finally, Press for 5 seconds to force power off

Rather use MagicSysRq.
http://www.ubuntugeek.com/how-to-use-magic-system-request-keys-in-ubuntu-linux.html

I'd also run MEM test, fsck and in case plug-off usb.

This user even has installation issues.
Bug #700899

Revision history for this message
iapx86 (jlettvin) said :
#3

Thank you for your many hints.
I will try all these out over the weekend.
Building the machine from scratch and then following advice takes time
and I want to let you know I will report back my results.

On Fri, Jan 28, 2011 at 1:18 PM, Samantha (aka Sam) <
<email address hidden>> wrote:

> Your question #143192 on ubiquity in ubuntu changed:
> https://answers.launchpad.net/ubuntu/+source/ubiquity/+question/143192
>
> Status: Open => Answered
>
> Samantha (aka Sam) proposed the following answer:
> Try running it without visual effects.
> Disable compiz (Visual effects=None), mentioned there.
> http://ubuntu-ky.ubuntuforums.org/showthread.php?p=7129470
>
> If this is your laptop
> http://www.lapspecs.com/wiki/lenovo+thinkpad+t61
> these pages may incl. some useful hints to look up.
> http://www.linlap.com/wiki/IBM-Lenovo+Thinkpad+T61
> http://www.thinkwiki.org/wiki/ThinkWiki
>
> Enough swap and RAM?
> http://kubuntuforums.net/forums/index.php?topic=3114933
>
> Maybe installing 'hibernate' helps.
> http://packages.ubuntu.com/maverick/hibernate
>
> > Finally, Press for 5 seconds to force power off
>
> Rather use MagicSysRq.
>
> http://www.ubuntugeek.com/how-to-use-magic-system-request-keys-in-ubuntu-linux.html
>
> I'd also run MEM test, fsck and in case plug-off usb.
>
> This user even has installation issues.
> Bug #700899
>
> --
> If this answers your question, please go to the following page to let us
> know that it is solved:
>
> https://answers.launchpad.net/ubuntu/+source/ubiquity/+question/143192/+confirm?answer_id=1
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
> https://answers.launchpad.net/ubuntu/+source/ubiquity/+question/143192
>
> You received this question notification because you are a direct
> subscriber of the question.
>

--
This e-mail is from Jonathan D. Lettvin, and may contain information that is
confidential or privileged. If you are not the intended recipient, do not
read, copy or distribute the e-mail or any attachments. Instead, please
notify the sender and delete the e-mail and any attachments. Thank you.

Jonathan D. Lettvin

Revision history for this message
iapx86 (jlettvin) said :
#4

Here are the actions I have taken to mitigate the problem.
I will not know whether the problem is fixed until it crashes again.

1. Visual effects=None (I don't like fancy shmancy stuff and this was
already true)
2. Yes, T61 just as you identified, I upgraded my BIOS after following these
links.
3. No other obvious mitigation advice down those links.
4. Swap 12GB, RAM 3GB so there is enough.
5. Installed hibernate as suggested (from synaptics).
6. THANK YOU FOR MagicSysRq! It may be the lifesaver if it happens again.
7. Didn't understand "I'd also run MEM test, fsck and in case plug-off usb."

BIOS upgrade from:
http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-67989

Please leave this issue open until I have allowed the system to go idle a
few times
to see that the problem is resolved.

I will return to this forum on Monday after cycling through hibernate a few
times.
If all is well then, this can be closed.

On Fri, Jan 28, 2011 at 8:18 PM, iapx86 <
<email address hidden>> wrote:

> Your question #143192 on ubiquity in ubuntu changed:
> https://answers.launchpad.net/ubuntu/+source/ubiquity/+question/143192
>
> Status: Answered => Open
>
> You are still having a problem:
> Thank you for your many hints.
> I will try all these out over the weekend.
> Building the machine from scratch and then following advice takes time
> and I want to let you know I will report back my results.
>
> On Fri, Jan 28, 2011 at 1:18 PM, Samantha (aka Sam) <
> <email address hidden>> wrote:
>
> > Your question #143192 on ubiquity in ubuntu changed:
> > https://answers.launchpad.net/ubuntu/+source/ubiquity/+question/143192
> >
> > Status: Open => Answered
> >
> > Samantha (aka Sam) proposed the following answer:
> > Try running it without visual effects.
> > Disable compiz (Visual effects=None), mentioned there.
> > http://ubuntu-ky.ubuntuforums.org/showthread.php?p=7129470
> >
> > If this is your laptop
> > http://www.lapspecs.com/wiki/lenovo+thinkpad+t61
> > these pages may incl. some useful hints to look up.
> > http://www.linlap.com/wiki/IBM-Lenovo+Thinkpad+T61
> > http://www.thinkwiki.org/wiki/ThinkWiki
> >
> > Enough swap and RAM?
> > http://kubuntuforums.net/forums/index.php?topic=3114933
> >
> > Maybe installing 'hibernate' helps.
> > http://packages.ubuntu.com/maverick/hibernate
> >
> > > Finally, Press for 5 seconds to force power off
> >
> > Rather use MagicSysRq.
> >
> >
> http://www.ubuntugeek.com/how-to-use-magic-system-request-keys-in-ubuntu-linux.html
> >
> > I'd also run MEM test, fsck and in case plug-off usb.
> >
> > This user even has installation issues.
> > Bug #700899
> >
> > --
> > If this answers your question, please go to the following page to let us
> > know that it is solved:
> >
> >
> https://answers.launchpad.net/ubuntu/+source/ubiquity/+question/143192/+confirm?answer_id=1
> >
> > If you still need help, you can reply to this email or go to the
> > following page to enter your feedback:
> > https://answers.launchpad.net/ubuntu/+source/ubiquity/+question/143192
> >
> > You received this question notification because you are a direct
> > subscriber of the question.
> >
>
>
> --
> This e-mail is from Jonathan D. Lettvin, and may contain information that
> is
> confidential or privileged. If you are not the intended recipient, do not
> read, copy or distribute the e-mail or any attachments. Instead, please
> notify the sender and delete the e-mail and any attachments. Thank you.
>
> Jonathan D. Lettvin
>
> You received this question notification because you are a direct
> subscriber of the question.
>

--
This e-mail is from Jonathan D. Lettvin, and may contain information that is
confidential or privileged. If you are not the intended recipient, do not
read, copy or distribute the e-mail or any attachments. Instead, please
notify the sender and delete the e-mail and any attachments. Thank you.

Jonathan D. Lettvin

Revision history for this message
iapx86 (jlettvin) said :
#5

No need to wait until Monday.
The problem recurred even before the machine was idle.

I was using synaptics to install gvim, scipy, and mayavi2.
Suddenly synaptics was unable to access packages and
the icon for firefox disappeared along with all other panel icons and menu
icons.
I could bring up the menu with items to shutdown or reboot
but no menu items worked.
This was a behavior I may not have reported well from my previous crashes.

MagicSysRq to the rescue. THANK YOU!
I rebooted to a working system (unlike before).

However, Maverick Meerkat is scaring me with potential untrustworthy
instability on my T61.
So, now that the experiments failed, and idle is not the only problem,

what next?

On Fri, Jan 28, 2011 at 11:12 PM, iapx86 <
<email address hidden>> wrote:

> Your question #143192 on ubiquity in ubuntu changed:
> https://answers.launchpad.net/ubuntu/+source/ubiquity/+question/143192
>
> You gave more information on the question:
> Here are the actions I have taken to mitigate the problem.
> I will not know whether the problem is fixed until it crashes again.
>
> 1. Visual effects=None (I don't like fancy shmancy stuff and this was
> already true)
> 2. Yes, T61 just as you identified, I upgraded my BIOS after following
> these
> links.
> 3. No other obvious mitigation advice down those links.
> 4. Swap 12GB, RAM 3GB so there is enough.
> 5. Installed hibernate as suggested (from synaptics).
> 6. THANK YOU FOR MagicSysRq! It may be the lifesaver if it happens again.
> 7. Didn't understand "I'd also run MEM test, fsck and in case plug-off
> usb."
>
> BIOS upgrade from:
> http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-67989
>
> Please leave this issue open until I have allowed the system to go idle a
> few times
> to see that the problem is resolved.
>
> I will return to this forum on Monday after cycling through hibernate a few
> times.
> If all is well then, this can be closed.
>
> On Fri, Jan 28, 2011 at 8:18 PM, iapx86 <
> <email address hidden>> wrote:
>
> > Your question #143192 on ubiquity in ubuntu changed:
> > https://answers.launchpad.net/ubuntu/+source/ubiquity/+question/143192
> >
> > Status: Answered => Open
> >
> > You are still having a problem:
> > Thank you for your many hints.
> > I will try all these out over the weekend.
> > Building the machine from scratch and then following advice takes time
> > and I want to let you know I will report back my results.
> >
> > On Fri, Jan 28, 2011 at 1:18 PM, Samantha (aka Sam) <
> > <email address hidden>> wrote:
> >
> > > Your question #143192 on ubiquity in ubuntu changed:
> > > https://answers.launchpad.net/ubuntu/+source/ubiquity/+question/143192
> > >
> > > Status: Open => Answered
> > >
> > > Samantha (aka Sam) proposed the following answer:
> > > Try running it without visual effects.
> > > Disable compiz (Visual effects=None), mentioned there.
> > > http://ubuntu-ky.ubuntuforums.org/showthread.php?p=7129470
> > >
> > > If this is your laptop
> > > http://www.lapspecs.com/wiki/lenovo+thinkpad+t61
> > > these pages may incl. some useful hints to look up.
> > > http://www.linlap.com/wiki/IBM-Lenovo+Thinkpad+T61
> > > http://www.thinkwiki.org/wiki/ThinkWiki
> > >
> > > Enough swap and RAM?
> > > http://kubuntuforums.net/forums/index.php?topic=3114933
> > >
> > > Maybe installing 'hibernate' helps.
> > > http://packages.ubuntu.com/maverick/hibernate
> > >
> > > > Finally, Press for 5 seconds to force power off
> > >
> > > Rather use MagicSysRq.
> > >
> > >
> >
> http://www.ubuntugeek.com/how-to-use-magic-system-request-keys-in-ubuntu-linux.html
> > >
> > > I'd also run MEM test, fsck and in case plug-off usb.
> > >
> > > This user even has installation issues.
> > > Bug #700899
> > >
> > > --
> > > If this answers your question, please go to the following page to let
> us
> > > know that it is solved:
> > >
> > >
> >
> https://answers.launchpad.net/ubuntu/+source/ubiquity/+question/143192/+confirm?answer_id=1
> > >
> > > If you still need help, you can reply to this email or go to the
> > > following page to enter your feedback:
> > > https://answers.launchpad.net/ubuntu/+source/ubiquity/+question/143192
> > >
> > > You received this question notification because you are a direct
> > > subscriber of the question.
> > >
> >
> >
> > --
> > This e-mail is from Jonathan D. Lettvin, and may contain information that
> > is
> > confidential or privileged. If you are not the intended recipient, do not
> > read, copy or distribute the e-mail or any attachments. Instead, please
> > notify the sender and delete the e-mail and any attachments. Thank you.
> >
> > Jonathan D. Lettvin
> >
> > You received this question notification because you are a direct
> > subscriber of the question.
> >
>
>
> --
> This e-mail is from Jonathan D. Lettvin, and may contain information that
> is
> confidential or privileged. If you are not the intended recipient, do not
> read, copy or distribute the e-mail or any attachments. Instead, please
> notify the sender and delete the e-mail and any attachments. Thank you.
>
> Jonathan D. Lettvin
>
> You received this question notification because you are a direct
> subscriber of the question.
>

--
This e-mail is from Jonathan D. Lettvin, and may contain information that is
confidential or privileged. If you are not the intended recipient, do not
read, copy or distribute the e-mail or any attachments. Instead, please
notify the sender and delete the e-mail and any attachments. Thank you.

Jonathan D. Lettvin

Revision history for this message
delance (olivier-delance) said :
#6

The fact that icons disappear is strange. It seems that your gnome-panel is unstable. So I change my mind, and think more about a software issue.

When you have issue, could you also try Ctrl+Alt+F1 and report if you get a terminal with a prompt.
If you get a prompt, log in and type command:
    sudo reboot -h
to properly shut down computer and avoid a mess in file system.

And please, avoid answering with previous message included. It makes thread less easy to read.

Revision history for this message
iapx86 (jlettvin) said :
#7

My apologies for thread impoliteness.

I think that something worse is going on than unrestored idle and gnome-panel.

The file system seems to disappear.
This could explain both the idle and icon problems, since both need filesystem access.
When the problem occurs while I am working, I can see an iconless menu
and I have attempted to launch Applications>Accessories>Terminal without success.
The system simply seems to ignore the request, and nothing happens.

Yet the MagicSysRq sequences work, (in particular S sync and U unmount/remount read-only).
When the machine is rebooted, everything looks normal,
but given enough time, the icons and filesystem will disappear again.
So, the file system seems to be there for MagicSysRq, but not for X?

At least MagicSysRq enables me to recover without file system corruption
as was the case when I started this thread.
But this is only a matter of time, since I need to eventually reinstall KVM
and if, as I have discovered, the problem occurs during a guest system install/configuration,
that guest system will become unusable.
It is a horrible waste of days to cycle through all this configuration and lose it all again and again.
Last time, configuring ubuntu 10.10 as a KVM guest took 5 hours for the initial install.
For whatever reason, even turning on hardware virtualization didn't help, it still used QEMU.

To respond to your suggestion though,
I had reported in the initial thread that I had tried Ctrl+Alt+F1,
there was no terminal with a prompt, just a black screen with a movable mouse cursor.

Will it help to know that the drive on which 10.10 is configured is a Seagate GoFlex 1.0TB?
It is connected by USB as an external drive and appears as /dev/sdb, and ubuntu on sdb1.
I am grasping at straws here.
I feel stumped, and will try anything to fix this.

Revision history for this message
Sam_ (and-sam) said :
#8

MEM test is availabe via boot menu, if you don't see it press 'Shift' key.
https://help.ubuntu.com/community/SystemAdministration/Fsck
https://help.ubuntu.com/community/TestingStorageMedia

> drive on which 10.10 .... by USB as an external drive

Just a while ago about Seagate GoFlex.
https://answers.launchpad.net/ubuntu/+question/140323

Review log files in /var/log (system administration -> log file viewer) after the crash.
Previous log files are e.g. syslog.1, Xorg.0.log.old.
In case paste it there.
http://paste.ubuntu.com/

Please post output when external drive is plugged in:
sudo fdisk -l

## where l is lower case of L

Consider to add this line to Grub. (etc/default/grub)
GRUB_DISABLE_OS_PROBER=true
https://help.ubuntu.com/community/Grub2#Configuring%20GRUB%202

FYI.
https://help.ubuntu.com/community/Video
https://help.ubuntu.com/community/KVM
https://wiki.ubuntu.com/kvm

Revision history for this message
iapx86 (jlettvin) said :
#9

Thank you for your continuing attention to my inquiry.
I hope you do not mind if I keep this open.

I had hoped my problems were over after I made a few adjustments.
1) I turned on hardware virtualization
2) I eliminated every use of suspend I could find

However, my hopes are slightly dashed.
Through the miracle of Alt-SysRq+R+E+I+S+U+B
I have managed to maintain an intact file system through the latest freeze,
and yet, the freeze happened.

It looks the same as before, a black screen and a moveable mouse
and nothing else.

Disappearing icons hasn't occurred since the last time I wrote about it here.

I have actually gotten some work done other than configuration!

I considered using GRUB_DISABLE_OS_PROBER=true
but, after reviewing the reasons for doing so, I couldn't see why
it would have any effect positive or negative on my problems.

My MEM test is without error.

Here are the requested logs and command results:

Jan 30 11:23 I just had to Alt-SysRq+R+E+I+S+U+B because after idle, the password box didn't appear.
Since I was asked for some log contents, here are the tail ends of the two requested.
I do not see evidence of failure, but I am novice in reviewing these.
Also included are the results from sudo fdisk -l

/var/log/syslog.1:

Jan 30 06:17:01 jlettvin-ThinkPad-T61-64bit CRON[2299]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Jan 30 06:25:01 jlettvin-ThinkPad-T61-64bit CRON[2462]: (root) CMD (test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily ))
Jan 30 06:25:22 jlettvin-ThinkPad-T61-64bit rsyslogd: [origin software="rsyslogd" swVersion="4.2.0" x-pid="1023" x-info="http://www.rsyslog.com"] rsyslogd was HUPed, type 'lightweight'.

/var/log/Xorg.0.log.old:

[ 4437.963] (II) NOUVEAU(0): EDID vendor "IBM", prod id 10375
[ 4437.963] (II) NOUVEAU(0): Printing DDC gathered Modelines:
[ 4437.963] (II) NOUVEAU(0): Modeline "1680x1050"x0.0 120.60 1680 1712 1760 1888 1050 1051 1054 1065 -hsync -vsync (63.9 kHz)
[ 4437.963] (II) NOUVEAU(0): Modeline "1680x1050"x0.0 100.53 1680 1712 1760 1888 1050 1051 1054 1065 -hsync -vsync (53.2 kHz)
[ 22342.517] (II) NOUVEAU(0): EDID vendor "IBM", prod id 10375
[ 22342.517] (II) NOUVEAU(0): Printing DDC gathered Modelines:
[ 22342.517] (II) NOUVEAU(0): Modeline "1680x1050"x0.0 120.60 1680 1712 1760 1888 1050 1051 1054 1065 -hsync -vsync (63.9 kHz)
[ 22342.517] (II) NOUVEAU(0): Modeline "1680x1050"x0.0 100.53 1680 1712 1760 1888 1050 1051 1054 1065 -hsync -vsync (53.2 kHz)
[ 23925.779] (II) NOUVEAU(0): EDID vendor "IBM", prod id 10375
[ 23925.779] (II) NOUVEAU(0): Printing DDC gathered Modelines:
[ 23925.779] (II) NOUVEAU(0): Modeline "1680x1050"x0.0 120.60 1680 1712 1760 1888 1050 1051 1054 1065 -hsync -vsync (63.9 kHz)
[ 23925.779] (II) NOUVEAU(0): Modeline "1680x1050"x0.0 100.53 1680 1712 1760 1888 1050 1051 1054 1065 -hsync -vsync (53.2 kHz)
[ 25520.496] (II) NOUVEAU(0): EDID vendor "IBM", prod id 10375
[ 25520.496] (II) NOUVEAU(0): Printing DDC gathered Modelines:
[ 25520.496] (II) NOUVEAU(0): Modeline "1680x1050"x0.0 120.60 1680 1712 1760 1888 1050 1051 1054 1065 -hsync -vsync (63.9 kHz)
[ 25520.496] (II) NOUVEAU(0): Modeline "1680x1050"x0.0 100.53 1680 1712 1760 1888 1050 1051 1054 1065 -hsync -vsync (53.2 kHz)
[ 25924.832] (II) NOUVEAU(0): EDID vendor "IBM", prod id 10375
[ 25924.833] (II) NOUVEAU(0): Printing DDC gathered Modelines:
[ 25924.833] (II) NOUVEAU(0): Modeline "1680x1050"x0.0 120.60 1680 1712 1760 1888 1050 1051 1054 1065 -hsync -vsync (63.9 kHz)
[ 25924.833] (II) NOUVEAU(0): Modeline "1680x1050"x0.0 100.53 1680 1712 1760 1888 1050 1051 1054 1065 -hsync -vsync (53.2 kHz)
[ 26387.070] (II) NOUVEAU(0): EDID vendor "IBM", prod id 10375
[ 26387.070] (II) NOUVEAU(0): Printing DDC gathered Modelines:
[ 26387.070] (II) NOUVEAU(0): Modeline "1680x1050"x0.0 120.60 1680 1712 1760 1888 1050 1051 1054 1065 -hsync -vsync (63.9 kHz)
[ 26387.070] (II) NOUVEAU(0): Modeline "1680x1050"x0.0 100.53 1680 1712 1760 1888 1050 1051 1054 1065 -hsync -vsync (53.2 kHz)
[ 27928.792] (II) NOUVEAU(0): EDID vendor "IBM", prod id 10375
[ 27928.793] (II) NOUVEAU(0): Printing DDC gathered Modelines:
[ 27928.793] (II) NOUVEAU(0): Modeline "1680x1050"x0.0 120.60 1680 1712 1760 1888 1050 1051 1054 1065 -hsync -vsync (63.9 kHz)
[ 27928.793] (II) NOUVEAU(0): Modeline "1680x1050"x0.0 100.53 1680 1712 1760 1888 1050 1051 1054 1065 -hsync -vsync (53.2 kHz)
[ 35856.563] (II) NOUVEAU(0): EDID vendor "IBM", prod id 10375
[ 35856.563] (II) NOUVEAU(0): Printing DDC gathered Modelines:
[ 35856.564] (II) NOUVEAU(0): Modeline "1680x1050"x0.0 120.60 1680 1712 1760 1888 1050 1051 1054 1065 -hsync -vsync (63.9 kHz)
[ 35856.564] (II) NOUVEAU(0): Modeline "1680x1050"x0.0 100.53 1680 1712 1760 1888 1050 1051 1054 1065 -hsync -vsync (53.2 kHz)
[ 41628.155] (II) NOUVEAU(0): EDID vendor "IBM", prod id 10375
[ 41628.156] (II) NOUVEAU(0): Printing DDC gathered Modelines:
[ 41628.156] (II) NOUVEAU(0): Modeline "1680x1050"x0.0 120.60 1680 1712 1760 1888 1050 1051 1054 1065 -hsync -vsync (63.9 kHz)
[ 41628.156] (II) NOUVEAU(0): Modeline "1680x1050"x0.0 100.53 1680 1712 1760 1888 1050 1051 1054 1065 -hsync -vsync (53.2 kHz)
[ 41982.279] (II) NOUVEAU(0): EDID vendor "IBM", prod id 10375
[ 41982.279] (II) NOUVEAU(0): Printing DDC gathered Modelines:
[ 41982.279] (II) NOUVEAU(0): Modeline "1680x1050"x0.0 120.60 1680 1712 1760 1888 1050 1051 1054 1065 -hsync -vsync (63.9 kHz)
[ 41982.279] (II) NOUVEAU(0): Modeline "1680x1050"x0.0 100.53 1680 1712 1760 1888 1050 1051 1054 1065 -hsync -vsync (53.2 kHz)

jlettvin@jlettvin-ThinkPad-T61-64bit:~/Desktop/Configuration$ sudo fdisk -l

Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x5e40ca20

   Device Boot Start End Blocks Id System
/dev/sda1 * 1 30401 244196001 7 HPFS/NTFS
/dev/sda2 30402 60801 244188000 5 Extended
/dev/sda5 30402 59672 235119276 83 Linux
/dev/sda6 59673 60801 9068661 82 Linux swap / Solaris

Disk /dev/sdb: 1000.2 GB, 1000204885504 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000dedca

   Device Boot Start End Blocks Id System
/dev/sdb1 1 120146 965065728 83 Linux
/dev/sdb2 120146 121602 11694081 5 Extended
/dev/sdb5 120146 121602 11694080 82 Linux swap / Solaris

Revision history for this message
Sam_ (and-sam) said :
#10

Thanks for posting log files, unfortunately nothing obvious.
Sure these are log files from the time the crash happened?

After reboot there should remain also .xsession-errors.old from the time a crash happened.
If yes, please post it.

Did you try disabling screensaver as delance suggested?

Verify if there is another driver offered in
system administration -> additional drivers

In case deactivate Nouveau and maybe disable KMS.
Reference.
https://help.ubuntu.com/community/BinaryDriverHowto/Nvidia
https://wiki.ubuntu.com/X/Troubleshooting/NvidiaDriverSwitching
https://wiki.ubuntu.com/X/KernelModeSetting
https://wiki.ubuntu.com/X/Testing/NouveauEvaluation

Revision history for this message
iapx86 (jlettvin) said :
#11

Thank you Sam,

I was careful to put the time of action signatures on the logs and my own actions.

The logs were the latest up-to-date information, at the tail of the files you requested.
My return to action was many hours later, when the system refused to respond.
I have no way of knowing if those are the "most recent" other than what you request.

As there was no .xsession-errors.old in /var/log, and I did:
sudo find / -name .xsession-errors.old
and found one in /home/jlettvin for which I have put the tail at the end of this message.

I have run system administration>additional drivers, and installed the recommended driver.
It removed many of the settings I had set, like reducing my workspaces from 8 to 4.
Fortunately, it didn't change any screensaver settings other than
Visual Effects got changed from None to Normal, but I have changed it back to None.

Re: DeLance's suggestions:
Ctrl-Alt-F1 does (usually but not always) get me a login screen,
but when I attempt to use it, it doesn't respond.
Magic SysRq is my exclusive route back to sanity.
I have attempted every manner of screensaver prevention I could think up.
I even have "shutdown" as my computer's response to any significant event.
I still can only choose 'blank screen' for the lid being closed.
The other alternatives are suspend or hibernate, both of which
force me back to Magic SysRq.

I have just now added nomodeset to my grub GRUB_CMDLINE_LINUX_DEFAULT
and will reboot with hopes.

Here is the tail end of /home/jlettvin/.xsession-errors.old:
*** NSPlugin Wrapper *** WARNING:(/build/buildd/nspluginwrapper-1.2.2/src/npw-wrapper.c:1854):invoke_NPP_Destroy: assertion failed: (rpc_method_invoke_possible(plugin->connection))
*** NSPlugin Wrapper *** WARNING:(/build/buildd/nspluginwrapper-1.2.2/src/npw-wrapper.c:1854):invoke_NPP_Destroy: assertion failed: (rpc_method_invoke_possible(plugin->connection))
*** NSPlugin Wrapper *** WARNING:(/build/buildd/nspluginwrapper-1.2.2/src/npw-wrapper.c:1854):invoke_NPP_Destroy: assertion failed: (rpc_method_invoke_possible(plugin->connection))
*** NSPlugin Wrapper *** WARNING:(/build/buildd/nspluginwrapper-1.2.2/src/npw-wrapper.c:1854):invoke_NPP_Destroy: assertion failed: (rpc_method_invoke_possible(plugin->connection))
*** NSPlugin Wrapper *** ERROR: NPObject 0x7f897ae25b50 is no longer valid!

(gnome-power-manager:1758): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
Window manager warning: CurrentTime used to choose focus window; focus window may not be correct.
Window manager warning: Got a request to focus the no_focus_window with a timestamp of 0. This shouldn't happen!
** Message: applet now removed from the notification area
gnome-settings-daemon: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
nm-applet: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
gdu-notification-daemon: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
bluetooth-applet: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
evolution-alarm-notify: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
applet.py: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
update-notifier: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
Shutting down nautilus-gdu extension

--- Hash table keys for warning below:
--> Jonathan D. Lettvin
--> l2065
--> l64512
--> inode/directory
--> jlettvin

(nautilus:1793): Eel-WARNING **: "unique eel_ref_str" hash table still has 5 elements at quit time (keys above)

(nautilus:1793): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 12 elements at quit time
XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0"
      after 59075 requests (59074 known processed) with 0 events remaining.

Revision history for this message
iapx86 (jlettvin) said :
#12

In the last half hour I had three "icon disappearing, panel disappearing" crashes.
I thought perhaps I was going to experience only the need to Magic reboot from time to time.
I was wrong.

I installed many many packages including python libraries, mediawiki, apache, and more.
I installed google chrome because I had an instinct that crashes might be associated with firefox.
But that was a mistake too.

The last two crashes happened when I was bookmarking or browsing in google chrome.
I am back in firefox now and expecting another crash soon.

So, none of the changes I have made in the trail of queries/responses above have worked.
Are there any next things to try?

Revision history for this message
iapx86 (jlettvin) said :
#13

Hello from 9.10,

That last crash I just experienced (after the last message I left here) left my system crippled.
I will perform any experiments suggested in this forum but
I can't afford to commit to working in 10.10 until the problem is resolved.

That last crash happened while I was doing simple edits in gvim.
I await advice, but the problem is unsolved.

Revision history for this message
Sam_ (and-sam) said :
#14

Behind disappearing 'icons' are applets (or other apps) which is stated by xsession-errors, e.g.
nm-applet: Fatal IO error 11

We need to know why Xserver is crashing, also stated by xsession-errors
> XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0"

There are more log files regarding X, so you need to search them to find some hints, e.g.
/var/log/Xorg.1.log

Also take a look at /var/crash
If it does contain crash files, you can cd to the directory and report via CLI e.g.
ubuntu-bug <name_of_crash_file.crash>

or just double click on it if possible via GUI method.
https://wiki.ubuntu.com/Apport

According to websearch it's maybe related to OpenGL, they're ongoing changes in drivers, so this would need a review from an X expert like Brian.
Although no chance to trace without log files since 'somehow' driver+compiz+Xserver don't like each other.
Example this Bug #519265 although it's about error 104 it looks a bit familiar.

Anyway, if you'd like to experiment then try this ppa.
https://launchpad.net/~xorg-edgers/+archive/ppa

You could also try to remove gnome-screensaver and see if it gets better without.
http://packages.ubuntu.com/maverick/gnome-screensaver

Since you seem to change Ubuntu version please provide the version each time on which you're currently proceeding the steps, thanks.

https://wiki.ubuntu.com/X/Troubleshooting/

Revision history for this message
iapx86 (jlettvin) said :
#15

All problems are exclusive to ubuntu 10.10.
No other problems.

I seek comfort and relief by booting from an old 9.10.
I will reboot back to 10.10 tomorrow to try your solutions.
These will be reported back to you ASAP

Sent from my iPhone

On Feb 1, 2011, at 6:17 PM, "Samantha \(aka Sam\)" <email address hidden> wrote:

>

Revision history for this message
iapx86 (jlettvin) said :
#16

Hi Sam and all keepers of this forum,

As I said in my previous entry, I use ubuntu 9.10 on one disk
to view the filesystem of ubuntu 10.10 on another disk.
I will reboot into 10.10 to try your latest recommendations.
None of what I ask questions about concerns ubuntu 9.10.

Here are the answers to the latest questions:

1) Below is the .xsession-errors from the latest crash
2) There is no file /var/log/Xorg.1.log but I have included the /var/log/Xorg.0.log below
2a) Also included /var/log/Xorg.0.log.old
3) /var/crash is an empty directory
4) I will install apport as I reboot into 10.10 in a few minutes
5) URL https://launchpad.net/~xorg-edgers/+archive/ppa failed with a timeout error
6) I will use synaptics to remove gnome-screensaver

Here is a curious thought:
Could some of my problems arise from samba?
I mount several shares of a local network drive
and .xsession-errors complains about failure of
/var/lib/samba/usershares
so I will choose to not attach these during the next boot.
These are current samba shares in my fstab:
//192.168.2.114/jqx /var/jqx cifs user=jlettvin,noauto,rw 0 0
//192.168.2.114/RosaSharon /var/RosaSharon cifs password=,user=jlettvin,noauto,rw 0 0
//192.168.2.114/share /var/share cifs password=,user=jlettvin,noauto,rw 0 0
//192.168.2.114/www /var/www cifs password=,user=jlettvin,noauto,rw 0 0
//192.168.2.114/tc /var/tc username=jlettvin,cifs user,noauto,rw 0 0

$cat /home/jlettvin/.xsession-errors:
/etc/gdm/Xsession: Beginning session setup...
Setting IM through im-switch for locale=en_US.
Start IM through /etc/X11/xinit/xinput.d/all_ALL linked to /etc/X11/xinit/xinput.d/default.
GNOME_KEYRING_CONTROL=/tmp/keyring-be1IOJ
SSH_AUTH_SOCK=/tmp/keyring-be1IOJ/ssh
GNOME_KEYRING_CONTROL=/tmp/keyring-be1IOJ
SSH_AUTH_SOCK=/tmp/keyring-be1IOJ/ssh
GNOME_KEYRING_CONTROL=/tmp/keyring-be1IOJ
SSH_AUTH_SOCK=/tmp/keyring-be1IOJ/ssh

(polkit-gnome-authentication-agent-1:1901): GLib-GObject-WARNING **: cannot register existing type `_PolkitError'

(polkit-gnome-authentication-agent-1:1901): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
** Message: adding killswitch idx 0 state KILLSWITCH_STATE_UNBLOCKED
** Message: adding killswitch idx 1 state KILLSWITCH_STATE_UNBLOCKED
** Message: killswitch 0 is KILLSWITCH_STATE_UNBLOCKED
** Message: killswitch 1 is KILLSWITCH_STATE_UNBLOCKED
** Message: killswitches state KILLSWITCH_STATE_UNBLOCKED
** Message: killswitch 0 is KILLSWITCH_STATE_UNBLOCKED
** Message: killswitch 1 is KILLSWITCH_STATE_UNBLOCKED
** Message: killswitches state KILLSWITCH_STATE_UNBLOCKED
** Message: applet now removed from the notification area
** (nm-applet:1908): DEBUG: old state indicates that this was not a disconnect 0
Initializing nautilus-gdu extension

(nautilus:1904): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed
** Message: applet now embedded in the notification area
Nautilus-Share-Message: Called "net usershare info" but it failed: 'net usershare' returned error 255: net usershare: cannot open usershare directory /var/lib/samba/usershares. Error No such file or directory
Please ask your system administrator to enable user sharing.

** (gnome-settings-daemon:1876): WARNING **: Got less number of items in credentials hash table than expected!

** (gnome-screensaver:2047): WARNING **: screensaver already running in this session
*** NSPlugin Viewer *** WARNING: unhandled variable 18 (<unknown variable>) in NPN_GetValue()
*** NSPlugin Viewer *** WARNING: unhandled variable 18 (<unknown variable>) in NPN_GetValue()
*** NSPlugin Viewer *** WARNING: unhandled variable 18 (<unknown variable>) in NPN_GetValue()
** (update-notifier:2204): DEBUG: aptdaemon on bus: 0
** (update-notifier:2204): DEBUG: Skipping reboot required
*** NSPlugin Viewer *** WARNING: unhandled variable 18 (<unknown variable>) in NPN_GetValue()
*** NSPlugin Viewer *** WARNING: unhandled variable 18 (<unknown variable>) in NPN_GetValue()
*** NSPlugin Viewer *** WARNING: unhandled variable 18 (<unknown variable>) in NPN_GetValue()

$cat /var/log/Xorg.0.log
[ 25.936]
X.Org X Server 1.9.0
Release Date: 2010-08-20
[ 25.936] X Protocol Version 11, Revision 0
[ 25.936] Build Operating System: Linux 2.6.24-28-server x86_64 Ubuntu
[ 25.936] Current Operating System: Linux jlettvin-ThinkPad-T61-64bit 2.6.35-25-generic #44-Ubuntu SMP Fri Jan 21 17:40:44 UTC 2011 x86_64
[ 25.936] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.35-25-generic root=UUID=cd51a206-911b-475d-8ad7-f547b0a4a40b ro quiet splash nomodeset
[ 25.936] Build Date: 09 January 2011 12:14:27PM
[ 25.936] xorg-server 2:1.9.0-0ubuntu7.3 (For technical support please see http://www.ubuntu.com/support)
[ 25.936] Current version of pixman: 0.18.4
[ 25.937] Before reporting problems, check http://wiki.x.org
 to make sure that you have the latest version.
[ 25.937] Markers: (--) probed, (**) from config file, (==) default setting,
 (++) from command line, (!!) notice, (II) informational,
 (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 25.937] (==) Log file: "/var/log/Xorg.0.log", Time: Mon Jan 31 17:50:53 2011
[ 25.937] (==) Using config file: "/etc/X11/xorg.conf"
[ 25.937] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 25.937] (==) No Layout section. Using the first Screen section.
[ 25.937] (**) |-->Screen "Default Screen" (0)
[ 25.937] (**) | |-->Monitor "<default monitor>"
[ 25.937] (==) No device specified for screen "Default Screen".
 Using the first device section listed.
[ 25.937] (**) | |-->Device "Default Device"
[ 25.937] (==) No monitor specified for screen "Default Screen".
 Using a default monitor configuration.
[ 25.937] (==) Automatically adding devices
[ 25.937] (==) Automatically enabling devices
[ 25.937] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[ 25.937] Entry deleted from font path.
[ 25.937] (==) FontPath set to:
 /usr/share/fonts/X11/misc,
 /usr/share/fonts/X11/100dpi/:unscaled,
 /usr/share/fonts/X11/75dpi/:unscaled,
 /usr/share/fonts/X11/Type1,
 /usr/share/fonts/X11/100dpi,
 /usr/share/fonts/X11/75dpi,
 /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType,
 built-ins
[ 25.937] (==) ModulePath set to "/usr/lib/xorg/extra-modules,/usr/lib/xorg/modules"
[ 25.937] (II) The server relies on udev to provide the list of input devices.
 If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 25.937] (II) Loader magic: 0x7d17a0
[ 25.937] (II) Module ABI versions:
[ 25.937] X.Org ANSI C Emulation: 0.4
[ 25.937] X.Org Video Driver: 8.0
[ 25.937] X.Org XInput driver : 11.0
[ 25.937] X.Org Server Extension : 4.0
[ 25.939] (--) PCI:*(0:1:0:0) 10de:0429:17aa:20d8 rev 161, Mem @ 0xd6000000/16777216, 0xe0000000/268435456, 0xd4000000/33554432, I/O @ 0x00002000/128
[ 25.939] (II) Open ACPI successful (/var/run/acpid.socket)
[ 25.939] (II) "extmod" will be loaded by default.
[ 25.939] (II) "dbe" will be loaded by default.
[ 25.939] (II) "glx" will be loaded. This was enabled by default and also specified in the config file.
[ 25.939] (II) "record" will be loaded by default.
[ 25.939] (II) "dri" will be loaded by default.
[ 25.939] (II) "dri2" will be loaded by default.
[ 25.939] (II) LoadModule: "glx"
[ 25.939] (II) Loading /usr/lib/xorg/extra-modules/libglx.so
[ 25.954] (II) Module glx: vendor="NVIDIA Corporation"
[ 25.954] compiled for 4.0.2, module version = 1.0.0
[ 25.954] Module class: X.Org Server Extension
[ 25.954] (II) NVIDIA GLX Module 260.19.06 Mon Sep 13 04:54:41 PDT 2010
[ 25.954] (II) Loading extension GLX
[ 25.954] (II) LoadModule: "extmod"
[ 26.163] (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
[ 26.163] (II) Module extmod: vendor="X.Org Foundation"
[ 26.163] compiled for 1.9.0, module version = 1.0.0
[ 26.163] Module class: X.Org Server Extension
[ 26.163] ABI class: X.Org Server Extension, version 4.0
[ 26.163] (II) Loading extension MIT-SCREEN-SAVER
[ 26.163] (II) Loading extension XFree86-VidModeExtension
[ 26.163] (II) Loading extension XFree86-DGA
[ 26.163] (II) Loading extension DPMS
[ 26.163] (II) Loading extension XVideo
[ 26.164] (II) Loading extension XVideo-MotionCompensation
[ 26.164] (II) Loading extension X-Resource
[ 26.164] (II) LoadModule: "dbe"
[ 26.164] (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
[ 26.164] (II) Module dbe: vendor="X.Org Foundation"
[ 26.164] compiled for 1.9.0, module version = 1.0.0
[ 26.164] Module class: X.Org Server Extension
[ 26.164] ABI class: X.Org Server Extension, version 4.0
[ 26.164] (II) Loading extension DOUBLE-BUFFER
[ 26.164] (II) LoadModule: "record"
[ 26.164] (II) Loading /usr/lib/xorg/modules/extensions/librecord.so
[ 26.164] (II) Module record: vendor="X.Org Foundation"
[ 26.164] compiled for 1.9.0, module version = 1.13.0
[ 26.164] Module class: X.Org Server Extension
[ 26.164] ABI class: X.Org Server Extension, version 4.0
[ 26.164] (II) Loading extension RECORD
[ 26.164] (II) LoadModule: "dri"
[ 26.165] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so
[ 26.165] (II) Module dri: vendor="X.Org Foundation"
[ 26.165] compiled for 1.9.0, module version = 1.0.0
[ 26.165] ABI class: X.Org Server Extension, version 4.0
[ 26.165] (II) Loading extension XFree86-DRI
[ 26.165] (II) LoadModule: "dri2"
[ 26.165] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
[ 26.165] (II) Module dri2: vendor="X.Org Foundation"
[ 26.165] compiled for 1.9.0, module version = 1.2.0
[ 26.165] ABI class: X.Org Server Extension, version 4.0
[ 26.165] (II) Loading extension DRI2
[ 26.165] (II) LoadModule: "nvidia"
[ 26.165] (II) Loading /usr/lib/xorg/extra-modules/nvidia_drv.so
[ 26.166] (II) Module nvidia: vendor="NVIDIA Corporation"
[ 26.166] compiled for 4.0.2, module version = 1.0.0
[ 26.166] Module class: X.Org Video Driver
[ 26.166] (II) NVIDIA dlloader X Driver 260.19.06 Mon Sep 13 04:31:43 PDT 2010
[ 26.166] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[ 26.166] (++) using VT number 7

[ 26.167] (II) Loading sub module "fb"
[ 26.167] (II) LoadModule: "fb"
[ 26.167] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 26.167] (II) Module fb: vendor="X.Org Foundation"
[ 26.167] compiled for 1.9.0, module version = 1.0.0
[ 26.167] ABI class: X.Org ANSI C Emulation, version 0.4
[ 26.167] (II) Loading sub module "wfb"
[ 26.167] (II) LoadModule: "wfb"
[ 26.167] (II) Loading /usr/lib/xorg/modules/libwfb.so
[ 26.168] (II) Module wfb: vendor="X.Org Foundation"
[ 26.168] compiled for 1.9.0, module version = 1.0.0
[ 26.168] ABI class: X.Org ANSI C Emulation, version 0.4
[ 26.168] (II) Loading sub module "ramdac"
[ 26.168] (II) LoadModule: "ramdac"
[ 26.168] (II) Module "ramdac" already built-in
[ 26.168] (II) NVIDIA(0): Creating default Display subsection in Screen section
 "Default Screen" for depth/fbbpp 24/32
[ 26.168] (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
[ 26.168] (==) NVIDIA(0): RGB weight 888
[ 26.168] (==) NVIDIA(0): Default visual is TrueColor
[ 26.168] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[ 26.168] (**) NVIDIA(0): Option "NoLogo" "True"
[ 26.168] (**) NVIDIA(0): Enabling RENDER acceleration
[ 26.168] (II) NVIDIA(0): Support for GLX with the Damage and Composite X extensions is
[ 26.168] (II) NVIDIA(0): enabled.
[ 27.353] (II) NVIDIA(0): NVIDIA GPU Quadro NVS 140M (G86) at PCI:1:0:0 (GPU-0)
[ 27.353] (--) NVIDIA(0): Memory: 524288 kBytes
[ 27.353] (--) NVIDIA(0): VideoBIOS: 60.86.3e.00.00
[ 27.353] (II) NVIDIA(0): Detected PCI Express Link width: 16X
[ 27.353] (--) NVIDIA(0): Interlaced video modes are supported on this GPU
[ 27.353] (--) NVIDIA(0): Connected display device(s) on Quadro NVS 140M at PCI:1:0:0
[ 27.353] (--) NVIDIA(0): IBM (DFP-0)
[ 27.353] (--) NVIDIA(0): IBM (DFP-0): 330.0 MHz maximum pixel clock
[ 27.353] (--) NVIDIA(0): IBM (DFP-0): Internal Dual Link LVDS
[ 27.361] (WW) NVIDIA(0): The EDID for IBM (DFP-0) contradicts itself: mode "1680x1050"
[ 27.361] (WW) NVIDIA(0): is specified in the EDID; however, the EDID's valid
[ 27.361] (WW) NVIDIA(0): HorizSync range (53.246-63.877 kHz) would exclude this
[ 27.361] (WW) NVIDIA(0): mode's HorizSync (42.6 kHz); ignoring HorizSync check for
[ 27.361] (WW) NVIDIA(0): mode "1680x1050".
[ 27.361] (WW) NVIDIA(0): The EDID for IBM (DFP-0) contradicts itself: mode "1680x1050"
[ 27.361] (WW) NVIDIA(0): is specified in the EDID; however, the EDID's valid
[ 27.361] (WW) NVIDIA(0): HorizSync range (53.246-63.877 kHz) would exclude this
[ 27.361] (WW) NVIDIA(0): mode's HorizSync (42.6 kHz); ignoring HorizSync check for
[ 27.361] (WW) NVIDIA(0): mode "1680x1050".
[ 27.422] (II) NVIDIA(0): Assigned Display Device: DFP-0
[ 27.422] (==) NVIDIA(0):
[ 27.422] (==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
[ 27.422] (==) NVIDIA(0): will be used as the requested mode.
[ 27.422] (==) NVIDIA(0):
[ 27.422] (II) NVIDIA(0): Validated modes:
[ 27.422] (II) NVIDIA(0): "nvidia-auto-select"
[ 27.423] (II) NVIDIA(0): Virtual screen size determined to be 1680 x 1050
[ 28.710] (--) NVIDIA(0): DPI set to (129, 127); computed from "UseEdidDpi" X config
[ 28.710] (--) NVIDIA(0): option
[ 28.710] (==) NVIDIA(0): Enabling 32-bit ARGB GLX visuals.
[ 28.710] (--) Depth 24 pixmap format is 32 bpp
[ 28.711] (II) NVIDIA: Using 768.00 MB of virtual memory for indirect memory access.
[ 28.713] (II) NVIDIA(0): Initialized GPU GART.
[ 28.720] (II) NVIDIA(0): ACPI display change hotkey events enabled: the X server is new
[ 28.720] (II) NVIDIA(0): enough to receive ACPI hotkey events.
[ 28.720] (II) NVIDIA(0): ACPI brightness change hotkey events enabled.
[ 28.727] (II) NVIDIA(0): Setting mode "nvidia-auto-select"
[ 29.537] (II) Loading extension NV-GLX
[ 29.571] (II) NVIDIA(0): Initialized OpenGL Acceleration
[ 29.608] (==) NVIDIA(0): Disabling shared memory pixmaps
[ 29.623] (II) NVIDIA(0): Initialized X Rendering Acceleration
[ 29.623] (==) NVIDIA(0): Backing store disabled
[ 29.623] (==) NVIDIA(0): Silken mouse enabled
[ 29.632] (==) NVIDIA(0): DPMS enabled
[ 29.632] (II) Loading extension NV-CONTROL
[ 29.632] (II) Loading extension XINERAMA
[ 29.632] (II) Loading sub module "dri2"
[ 29.632] (II) LoadModule: "dri2"
[ 29.632] (II) Reloading /usr/lib/xorg/modules/extensions/libdri2.so
[ 29.632] (II) NVIDIA(0): [DRI2] Setup complete
[ 29.632] (==) RandR enabled
[ 29.632] (II) Initializing built-in extension Generic Event Extension
[ 29.632] (II) Initializing built-in extension SHAPE
[ 29.632] (II) Initializing built-in extension MIT-SHM
[ 29.632] (II) Initializing built-in extension XInputExtension
[ 29.632] (II) Initializing built-in extension XTEST
[ 29.632] (II) Initializing built-in extension BIG-REQUESTS
[ 29.632] (II) Initializing built-in extension SYNC
[ 29.632] (II) Initializing built-in extension XKEYBOARD
[ 29.632] (II) Initializing built-in extension XC-MISC
[ 29.632] (II) Initializing built-in extension SECURITY
[ 29.632] (II) Initializing built-in extension XINERAMA
[ 29.632] (II) Initializing built-in extension XFIXES
[ 29.633] (II) Initializing built-in extension RENDER
[ 29.633] (II) Initializing built-in extension RANDR
[ 29.633] (II) Initializing built-in extension COMPOSITE
[ 29.633] (II) Initializing built-in extension DAMAGE
[ 29.633] (II) Initializing built-in extension GESTURE
[ 29.633] (II) Initializing extension GLX
[ 29.658] (II) XKB: reuse xkmfile /var/lib/xkb/server-B20D7FC79C7F597315E3E501AEF10E0D866E8E92.xkm
[ 29.666] (II) config/udev: Adding input device Power Button (/dev/input/event2)
[ 29.666] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 29.666] (II) LoadModule: "evdev"
[ 29.666] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 29.666] (II) Module evdev: vendor="X.Org Foundation"
[ 29.666] compiled for 1.9.0, module version = 2.3.2
[ 29.666] Module class: X.Org XInput Driver
[ 29.666] ABI class: X.Org XInput driver, version 11.0
[ 29.666] (**) Power Button: always reports core events
[ 29.666] (**) Power Button: Device: "/dev/input/event2"
[ 29.682] (II) Power Button: Found keys
[ 29.682] (II) Power Button: Configuring as keyboard
[ 29.682] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD)
[ 29.682] (**) Option "xkb_rules" "evdev"
[ 29.682] (**) Option "xkb_model" "pc105"
[ 29.682] (**) Option "xkb_layout" "us"
[ 29.683] (II) config/udev: Adding input device Video Bus (/dev/input/event4)
[ 29.683] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
[ 29.683] (**) Video Bus: always reports core events
[ 29.683] (**) Video Bus: Device: "/dev/input/event4"
[ 29.710] (II) Video Bus: Found keys
[ 29.710] (II) Video Bus: Configuring as keyboard
[ 29.710] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD)
[ 29.710] (**) Option "xkb_rules" "evdev"
[ 29.710] (**) Option "xkb_model" "pc105"
[ 29.710] (**) Option "xkb_layout" "us"
[ 29.710] (II) config/udev: Adding input device Lid Switch (/dev/input/event0)
[ 29.710] (II) No input driver/identifier specified (ignoring)
[ 29.711] (II) config/udev: Adding input device Sleep Button (/dev/input/event1)
[ 29.711] (**) Sleep Button: Applying InputClass "evdev keyboard catchall"
[ 29.711] (**) Sleep Button: always reports core events
[ 29.711] (**) Sleep Button: Device: "/dev/input/event1"
[ 29.740] (II) Sleep Button: Found keys
[ 29.740] (II) Sleep Button: Configuring as keyboard
[ 29.740] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD)
[ 29.740] (**) Option "xkb_rules" "evdev"
[ 29.740] (**) Option "xkb_model" "pc105"
[ 29.740] (**) Option "xkb_layout" "us"
[ 29.744] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event3)
[ 29.744] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
[ 29.744] (**) AT Translated Set 2 keyboard: always reports core events
[ 29.744] (**) AT Translated Set 2 keyboard: Device: "/dev/input/event3"
[ 29.770] (II) AT Translated Set 2 keyboard: Found keys
[ 29.770] (II) AT Translated Set 2 keyboard: Configuring as keyboard
[ 29.770] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD)
[ 29.770] (**) Option "xkb_rules" "evdev"
[ 29.770] (**) Option "xkb_model" "pc105"
[ 29.770] (**) Option "xkb_layout" "us"
[ 29.770] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/event6)
[ 29.770] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "evdev touchpad catchall"
[ 29.770] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "touchpad catchall"
[ 29.770] (II) LoadModule: "synaptics"
[ 29.770] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
[ 29.770] (II) Module synaptics: vendor="X.Org Foundation"
[ 29.770] compiled for 1.9.0, module version = 1.2.2
[ 29.770] Module class: X.Org XInput Driver
[ 29.770] ABI class: X.Org XInput driver, version 11.0
[ 29.770] (II) Synaptics touchpad driver version 1.2.2
[ 29.770] (**) Option "Device" "/dev/input/event6"
[ 29.842] (II) SynPS/2 Synaptics TouchPad: x-axis range 1472 - 5472
[ 29.842] (II) SynPS/2 Synaptics TouchPad: y-axis range 1408 - 4448
[ 29.842] (II) SynPS/2 Synaptics TouchPad: pressure range 0 - 255
[ 29.842] (II) SynPS/2 Synaptics TouchPad: finger width range 0 - 0
[ 29.842] (II) SynPS/2 Synaptics TouchPad: buttons: left right double triple
[ 29.902] (--) SynPS/2 Synaptics TouchPad: touchpad found
[ 29.902] (**) SynPS/2 Synaptics TouchPad: always reports core events
[ 29.902] (II) XINPUT: Adding extended input device "SynPS/2 Synaptics TouchPad" (type: TOUCHPAD)
[ 29.902] (**) SynPS/2 Synaptics TouchPad: (accel) keeping acceleration scheme 1
[ 29.902] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration profile 0
[ 29.902] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration factor: 2.000
[ 29.902] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration threshold: 4
[ 29.962] (--) SynPS/2 Synaptics TouchPad: touchpad found
[ 29.962] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse0)
[ 29.962] (II) No input driver/identifier specified (ignoring)
[ 29.963] (II) config/udev: Adding input device ThinkPad Extra Buttons (/dev/input/event5)
[ 29.963] (**) ThinkPad Extra Buttons: Applying InputClass "evdev keyboard catchall"
[ 29.963] (**) ThinkPad Extra Buttons: always reports core events
[ 29.963] (**) ThinkPad Extra Buttons: Device: "/dev/input/event5"
[ 30.002] (II) ThinkPad Extra Buttons: Found keys
[ 30.002] (II) ThinkPad Extra Buttons: Configuring as keyboard
[ 30.002] (II) XINPUT: Adding extended input device "ThinkPad Extra Buttons" (type: KEYBOARD)
[ 30.002] (**) Option "xkb_rules" "evdev"
[ 30.002] (**) Option "xkb_model" "pc105"
[ 30.002] (**) Option "xkb_layout" "us"
[ 31.690] (II) config/udev: Adding input device TPPS/2 IBM TrackPoint (/dev/input/mouse1)
[ 31.690] (II) No input driver/identifier specified (ignoring)
[ 31.692] (II) config/udev: Adding input device TPPS/2 IBM TrackPoint (/dev/input/event7)
[ 31.692] (**) TPPS/2 IBM TrackPoint: Applying InputClass "evdev pointer catchall"
[ 31.692] (**) TPPS/2 IBM TrackPoint: always reports core events
[ 31.692] (**) TPPS/2 IBM TrackPoint: Device: "/dev/input/event7"
[ 31.712] (II) TPPS/2 IBM TrackPoint: Found 3 mouse buttons
[ 31.712] (II) TPPS/2 IBM TrackPoint: Found relative axes
[ 31.712] (II) TPPS/2 IBM TrackPoint: Found x and y relative axes
[ 31.712] (II) TPPS/2 IBM TrackPoint: Configuring as mouse
[ 31.712] (**) TPPS/2 IBM TrackPoint: YAxisMapping: buttons 4 and 5
[ 31.712] (**) TPPS/2 IBM TrackPoint: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 31.712] (II) XINPUT: Adding extended input device "TPPS/2 IBM TrackPoint" (type: MOUSE)
[ 31.712] (II) TPPS/2 IBM TrackPoint: initialized for relative axes.

$cat /var/log/Xorg.0.log.old
[ 32.448]
X.Org X Server 1.9.0
Release Date: 2010-08-20
[ 32.448] X Protocol Version 11, Revision 0
[ 32.448] Build Operating System: Linux 2.6.24-28-server x86_64 Ubuntu
[ 32.448] Current Operating System: Linux jlettvin-ThinkPad-T61-64bit 2.6.35-25-generic #44-Ubuntu SMP Fri Jan 21 17:40:44 UTC 2011 x86_64
[ 32.448] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.35-25-generic root=UUID=cd51a206-911b-475d-8ad7-f547b0a4a40b ro quiet splash nomodeset
[ 32.448] Build Date: 09 January 2011 12:14:27PM
[ 32.448] xorg-server 2:1.9.0-0ubuntu7.3 (For technical support please see http://www.ubuntu.com/support)
[ 32.448] Current version of pixman: 0.18.4
[ 32.448] Before reporting problems, check http://wiki.x.org
 to make sure that you have the latest version.
[ 32.448] Markers: (--) probed, (**) from config file, (==) default setting,
 (++) from command line, (!!) notice, (II) informational,
 (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 32.448] (==) Log file: "/var/log/Xorg.0.log", Time: Mon Jan 31 17:44:53 2011
[ 32.449] (==) Using config file: "/etc/X11/xorg.conf"
[ 32.449] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 32.449] (==) No Layout section. Using the first Screen section.
[ 32.449] (**) |-->Screen "Default Screen" (0)
[ 32.449] (**) | |-->Monitor "<default monitor>"
[ 32.449] (==) No device specified for screen "Default Screen".
 Using the first device section listed.
[ 32.449] (**) | |-->Device "Default Device"
[ 32.449] (==) No monitor specified for screen "Default Screen".
 Using a default monitor configuration.
[ 32.449] (==) Automatically adding devices
[ 32.449] (==) Automatically enabling devices
[ 32.449] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[ 32.449] Entry deleted from font path.
[ 32.449] (==) FontPath set to:
 /usr/share/fonts/X11/misc,
 /usr/share/fonts/X11/100dpi/:unscaled,
 /usr/share/fonts/X11/75dpi/:unscaled,
 /usr/share/fonts/X11/Type1,
 /usr/share/fonts/X11/100dpi,
 /usr/share/fonts/X11/75dpi,
 /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType,
 built-ins
[ 32.449] (==) ModulePath set to "/usr/lib/xorg/extra-modules,/usr/lib/xorg/modules"
[ 32.449] (II) The server relies on udev to provide the list of input devices.
 If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 32.449] (II) Loader magic: 0x7d17a0
[ 32.449] (II) Module ABI versions:
[ 32.449] X.Org ANSI C Emulation: 0.4
[ 32.449] X.Org Video Driver: 8.0
[ 32.449] X.Org XInput driver : 11.0
[ 32.449] X.Org Server Extension : 4.0
[ 32.450] (--) PCI:*(0:1:0:0) 10de:0429:17aa:20d8 rev 161, Mem @ 0xd6000000/16777216, 0xe0000000/268435456, 0xd4000000/33554432, I/O @ 0x00002000/128
[ 32.451] (II) Open ACPI successful (/var/run/acpid.socket)
[ 32.451] (II) "extmod" will be loaded by default.
[ 32.451] (II) "dbe" will be loaded by default.
[ 32.451] (II) "glx" will be loaded. This was enabled by default and also specified in the config file.
[ 32.451] (II) "record" will be loaded by default.
[ 32.451] (II) "dri" will be loaded by default.
[ 32.451] (II) "dri2" will be loaded by default.
[ 32.451] (II) LoadModule: "glx"
[ 32.451] (II) Loading /usr/lib/xorg/extra-modules/libglx.so
[ 32.463] (II) Module glx: vendor="NVIDIA Corporation"
[ 32.463] compiled for 4.0.2, module version = 1.0.0
[ 32.463] Module class: X.Org Server Extension
[ 32.463] (II) NVIDIA GLX Module 260.19.06 Mon Sep 13 04:54:41 PDT 2010
[ 32.463] (II) Loading extension GLX
[ 32.463] (II) LoadModule: "extmod"
[ 32.545] (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
[ 32.545] (II) Module extmod: vendor="X.Org Foundation"
[ 32.545] compiled for 1.9.0, module version = 1.0.0
[ 32.545] Module class: X.Org Server Extension
[ 32.545] ABI class: X.Org Server Extension, version 4.0
[ 32.545] (II) Loading extension MIT-SCREEN-SAVER
[ 32.545] (II) Loading extension XFree86-VidModeExtension
[ 32.545] (II) Loading extension XFree86-DGA
[ 32.545] (II) Loading extension DPMS
[ 32.545] (II) Loading extension XVideo
[ 32.545] (II) Loading extension XVideo-MotionCompensation
[ 32.545] (II) Loading extension X-Resource
[ 32.545] (II) LoadModule: "dbe"
[ 32.545] (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
[ 32.545] (II) Module dbe: vendor="X.Org Foundation"
[ 32.545] compiled for 1.9.0, module version = 1.0.0
[ 32.545] Module class: X.Org Server Extension
[ 32.545] ABI class: X.Org Server Extension, version 4.0
[ 32.545] (II) Loading extension DOUBLE-BUFFER
[ 32.545] (II) LoadModule: "record"
[ 32.545] (II) Loading /usr/lib/xorg/modules/extensions/librecord.so
[ 32.545] (II) Module record: vendor="X.Org Foundation"
[ 32.545] compiled for 1.9.0, module version = 1.13.0
[ 32.546] Module class: X.Org Server Extension
[ 32.546] ABI class: X.Org Server Extension, version 4.0
[ 32.546] (II) Loading extension RECORD
[ 32.546] (II) LoadModule: "dri"
[ 32.546] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so
[ 32.546] (II) Module dri: vendor="X.Org Foundation"
[ 32.546] compiled for 1.9.0, module version = 1.0.0
[ 32.546] ABI class: X.Org Server Extension, version 4.0
[ 32.546] (II) Loading extension XFree86-DRI
[ 32.546] (II) LoadModule: "dri2"
[ 32.546] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
[ 32.546] (II) Module dri2: vendor="X.Org Foundation"
[ 32.546] compiled for 1.9.0, module version = 1.2.0
[ 32.546] ABI class: X.Org Server Extension, version 4.0
[ 32.546] (II) Loading extension DRI2
[ 32.546] (II) LoadModule: "nvidia"
[ 32.546] (II) Loading /usr/lib/xorg/extra-modules/nvidia_drv.so
[ 32.547] (II) Module nvidia: vendor="NVIDIA Corporation"
[ 32.547] compiled for 4.0.2, module version = 1.0.0
[ 32.547] Module class: X.Org Video Driver
[ 32.547] (II) NVIDIA dlloader X Driver 260.19.06 Mon Sep 13 04:31:43 PDT 2010
[ 32.547] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[ 32.547] (++) using VT number 7

[ 32.548] (II) Loading sub module "fb"
[ 32.548] (II) LoadModule: "fb"
[ 32.548] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 32.548] (II) Module fb: vendor="X.Org Foundation"
[ 32.548] compiled for 1.9.0, module version = 1.0.0
[ 32.548] ABI class: X.Org ANSI C Emulation, version 0.4
[ 32.548] (II) Loading sub module "wfb"
[ 32.548] (II) LoadModule: "wfb"
[ 32.549] (II) Loading /usr/lib/xorg/modules/libwfb.so
[ 32.549] (II) Module wfb: vendor="X.Org Foundation"
[ 32.549] compiled for 1.9.0, module version = 1.0.0
[ 32.549] ABI class: X.Org ANSI C Emulation, version 0.4
[ 32.549] (II) Loading sub module "ramdac"
[ 32.549] (II) LoadModule: "ramdac"
[ 32.549] (II) Module "ramdac" already built-in
[ 32.549] (II) NVIDIA(0): Creating default Display subsection in Screen section
 "Default Screen" for depth/fbbpp 24/32
[ 32.549] (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
[ 32.549] (==) NVIDIA(0): RGB weight 888
[ 32.549] (==) NVIDIA(0): Default visual is TrueColor
[ 32.549] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[ 32.549] (**) NVIDIA(0): Option "NoLogo" "True"
[ 32.549] (**) NVIDIA(0): Enabling RENDER acceleration
[ 32.549] (II) NVIDIA(0): Support for GLX with the Damage and Composite X extensions is
[ 32.549] (II) NVIDIA(0): enabled.
[ 33.727] (II) NVIDIA(0): NVIDIA GPU Quadro NVS 140M (G86) at PCI:1:0:0 (GPU-0)
[ 33.727] (--) NVIDIA(0): Memory: 524288 kBytes
[ 33.727] (--) NVIDIA(0): VideoBIOS: 60.86.3e.00.00
[ 33.727] (II) NVIDIA(0): Detected PCI Express Link width: 16X
[ 33.727] (--) NVIDIA(0): Interlaced video modes are supported on this GPU
[ 33.727] (--) NVIDIA(0): Connected display device(s) on Quadro NVS 140M at PCI:1:0:0
[ 33.727] (--) NVIDIA(0): IBM (DFP-0)
[ 33.727] (--) NVIDIA(0): IBM (DFP-0): 330.0 MHz maximum pixel clock
[ 33.727] (--) NVIDIA(0): IBM (DFP-0): Internal Dual Link LVDS
[ 33.734] (WW) NVIDIA(0): The EDID for IBM (DFP-0) contradicts itself: mode "1680x1050"
[ 33.734] (WW) NVIDIA(0): is specified in the EDID; however, the EDID's valid
[ 33.734] (WW) NVIDIA(0): HorizSync range (53.246-63.877 kHz) would exclude this
[ 33.734] (WW) NVIDIA(0): mode's HorizSync (42.6 kHz); ignoring HorizSync check for
[ 33.734] (WW) NVIDIA(0): mode "1680x1050".
[ 33.735] (WW) NVIDIA(0): The EDID for IBM (DFP-0) contradicts itself: mode "1680x1050"
[ 33.735] (WW) NVIDIA(0): is specified in the EDID; however, the EDID's valid
[ 33.735] (WW) NVIDIA(0): HorizSync range (53.246-63.877 kHz) would exclude this
[ 33.735] (WW) NVIDIA(0): mode's HorizSync (42.6 kHz); ignoring HorizSync check for
[ 33.735] (WW) NVIDIA(0): mode "1680x1050".
[ 33.798] (II) NVIDIA(0): Assigned Display Device: DFP-0
[ 33.798] (==) NVIDIA(0):
[ 33.798] (==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
[ 33.798] (==) NVIDIA(0): will be used as the requested mode.
[ 33.798] (==) NVIDIA(0):
[ 33.798] (II) NVIDIA(0): Validated modes:
[ 33.798] (II) NVIDIA(0): "nvidia-auto-select"
[ 33.798] (II) NVIDIA(0): Virtual screen size determined to be 1680 x 1050
[ 35.091] (--) NVIDIA(0): DPI set to (129, 127); computed from "UseEdidDpi" X config
[ 35.091] (--) NVIDIA(0): option
[ 35.091] (==) NVIDIA(0): Enabling 32-bit ARGB GLX visuals.
[ 35.091] (--) Depth 24 pixmap format is 32 bpp
[ 35.091] (II) NVIDIA: Using 768.00 MB of virtual memory for indirect memory access.
[ 35.093] (II) NVIDIA(0): Initialized GPU GART.
[ 35.100] (II) NVIDIA(0): ACPI display change hotkey events enabled: the X server is new
[ 35.100] (II) NVIDIA(0): enough to receive ACPI hotkey events.
[ 35.100] (II) NVIDIA(0): ACPI brightness change hotkey events enabled.
[ 35.107] (II) NVIDIA(0): Setting mode "nvidia-auto-select"
[ 35.919] (II) Loading extension NV-GLX
[ 35.951] (II) NVIDIA(0): Initialized OpenGL Acceleration
[ 35.988] (==) NVIDIA(0): Disabling shared memory pixmaps
[ 35.988] (II) NVIDIA(0): Initialized X Rendering Acceleration
[ 35.988] (==) NVIDIA(0): Backing store disabled
[ 35.988] (==) NVIDIA(0): Silken mouse enabled
[ 35.995] (==) NVIDIA(0): DPMS enabled
[ 35.995] (II) Loading extension NV-CONTROL
[ 35.996] (II) Loading extension XINERAMA
[ 35.996] (II) Loading sub module "dri2"
[ 35.996] (II) LoadModule: "dri2"
[ 35.996] (II) Reloading /usr/lib/xorg/modules/extensions/libdri2.so
[ 35.996] (II) NVIDIA(0): [DRI2] Setup complete
[ 35.996] (==) RandR enabled
[ 35.996] (II) Initializing built-in extension Generic Event Extension
[ 35.996] (II) Initializing built-in extension SHAPE
[ 35.996] (II) Initializing built-in extension MIT-SHM
[ 35.996] (II) Initializing built-in extension XInputExtension
[ 35.996] (II) Initializing built-in extension XTEST
[ 35.996] (II) Initializing built-in extension BIG-REQUESTS
[ 35.996] (II) Initializing built-in extension SYNC
[ 35.996] (II) Initializing built-in extension XKEYBOARD
[ 35.996] (II) Initializing built-in extension XC-MISC
[ 35.996] (II) Initializing built-in extension SECURITY
[ 35.996] (II) Initializing built-in extension XINERAMA
[ 35.996] (II) Initializing built-in extension XFIXES
[ 35.996] (II) Initializing built-in extension RENDER
[ 35.996] (II) Initializing built-in extension RANDR
[ 35.996] (II) Initializing built-in extension COMPOSITE
[ 35.996] (II) Initializing built-in extension DAMAGE
[ 35.996] (II) Initializing built-in extension GESTURE
[ 35.996] (II) Initializing extension GLX
[ 36.022] (II) XKB: reuse xkmfile /var/lib/xkb/server-B20D7FC79C7F597315E3E501AEF10E0D866E8E92.xkm
[ 36.029] (II) config/udev: Adding input device Power Button (/dev/input/event2)
[ 36.029] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 36.029] (II) LoadModule: "evdev"
[ 36.029] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 36.029] (II) Module evdev: vendor="X.Org Foundation"
[ 36.029] compiled for 1.9.0, module version = 2.3.2
[ 36.029] Module class: X.Org XInput Driver
[ 36.029] ABI class: X.Org XInput driver, version 11.0
[ 36.029] (**) Power Button: always reports core events
[ 36.029] (**) Power Button: Device: "/dev/input/event2"
[ 36.050] (II) Power Button: Found keys
[ 36.050] (II) Power Button: Configuring as keyboard
[ 36.050] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD)
[ 36.050] (**) Option "xkb_rules" "evdev"
[ 36.050] (**) Option "xkb_model" "pc105"
[ 36.050] (**) Option "xkb_layout" "us"
[ 36.051] (II) config/udev: Adding input device Video Bus (/dev/input/event4)
[ 36.051] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
[ 36.051] (**) Video Bus: always reports core events
[ 36.051] (**) Video Bus: Device: "/dev/input/event4"
[ 36.072] (II) Video Bus: Found keys
[ 36.072] (II) Video Bus: Configuring as keyboard
[ 36.072] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD)
[ 36.072] (**) Option "xkb_rules" "evdev"
[ 36.072] (**) Option "xkb_model" "pc105"
[ 36.072] (**) Option "xkb_layout" "us"
[ 36.073] (II) config/udev: Adding input device Lid Switch (/dev/input/event0)
[ 36.073] (II) No input driver/identifier specified (ignoring)
[ 36.073] (II) config/udev: Adding input device Sleep Button (/dev/input/event1)
[ 36.073] (**) Sleep Button: Applying InputClass "evdev keyboard catchall"
[ 36.073] (**) Sleep Button: always reports core events
[ 36.073] (**) Sleep Button: Device: "/dev/input/event1"
[ 36.112] (II) Sleep Button: Found keys
[ 36.112] (II) Sleep Button: Configuring as keyboard
[ 36.112] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD)
[ 36.112] (**) Option "xkb_rules" "evdev"
[ 36.112] (**) Option "xkb_model" "pc105"
[ 36.112] (**) Option "xkb_layout" "us"
[ 36.117] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event3)
[ 36.117] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
[ 36.117] (**) AT Translated Set 2 keyboard: always reports core events
[ 36.117] (**) AT Translated Set 2 keyboard: Device: "/dev/input/event3"
[ 36.152] (II) AT Translated Set 2 keyboard: Found keys
[ 36.152] (II) AT Translated Set 2 keyboard: Configuring as keyboard
[ 36.152] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD)
[ 36.152] (**) Option "xkb_rules" "evdev"
[ 36.152] (**) Option "xkb_model" "pc105"
[ 36.152] (**) Option "xkb_layout" "us"
[ 36.153] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/event6)
[ 36.153] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "evdev touchpad catchall"
[ 36.153] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "touchpad catchall"
[ 36.153] (II) LoadModule: "synaptics"
[ 36.153] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
[ 36.153] (II) Module synaptics: vendor="X.Org Foundation"
[ 36.153] compiled for 1.9.0, module version = 1.2.2
[ 36.153] Module class: X.Org XInput Driver
[ 36.153] ABI class: X.Org XInput driver, version 11.0
[ 36.153] (II) Synaptics touchpad driver version 1.2.2
[ 36.153] (**) Option "Device" "/dev/input/event6"
[ 36.230] (II) SynPS/2 Synaptics TouchPad: x-axis range 1472 - 5472
[ 36.230] (II) SynPS/2 Synaptics TouchPad: y-axis range 1408 - 4448
[ 36.230] (II) SynPS/2 Synaptics TouchPad: pressure range 0 - 255
[ 36.230] (II) SynPS/2 Synaptics TouchPad: finger width range 0 - 0
[ 36.230] (II) SynPS/2 Synaptics TouchPad: buttons: left right double triple
[ 36.310] (--) SynPS/2 Synaptics TouchPad: touchpad found
[ 36.310] (**) SynPS/2 Synaptics TouchPad: always reports core events
[ 36.350] (II) XINPUT: Adding extended input device "SynPS/2 Synaptics TouchPad" (type: TOUCHPAD)
[ 36.350] (**) SynPS/2 Synaptics TouchPad: (accel) keeping acceleration scheme 1
[ 36.350] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration profile 0
[ 36.350] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration factor: 2.000
[ 36.350] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration threshold: 4
[ 36.430] (--) SynPS/2 Synaptics TouchPad: touchpad found
[ 36.430] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse0)
[ 36.430] (II) No input driver/identifier specified (ignoring)
[ 36.430] (II) config/udev: Adding input device ThinkPad Extra Buttons (/dev/input/event5)
[ 36.430] (**) ThinkPad Extra Buttons: Applying InputClass "evdev keyboard catchall"
[ 36.430] (**) ThinkPad Extra Buttons: always reports core events
[ 36.430] (**) ThinkPad Extra Buttons: Device: "/dev/input/event5"
[ 36.470] (II) ThinkPad Extra Buttons: Found keys
[ 36.470] (II) ThinkPad Extra Buttons: Configuring as keyboard
[ 36.470] (II) XINPUT: Adding extended input device "ThinkPad Extra Buttons" (type: KEYBOARD)
[ 36.470] (**) Option "xkb_rules" "evdev"
[ 36.470] (**) Option "xkb_model" "pc105"
[ 36.470] (**) Option "xkb_layout" "us"
[ 39.089] (II) config/udev: Adding input device TPPS/2 IBM TrackPoint (/dev/input/mouse1)
[ 39.089] (II) No input driver/identifier specified (ignoring)
[ 39.090] (II) config/udev: Adding input device TPPS/2 IBM TrackPoint (/dev/input/event7)
[ 39.090] (**) TPPS/2 IBM TrackPoint: Applying InputClass "evdev pointer catchall"
[ 39.090] (**) TPPS/2 IBM TrackPoint: always reports core events
[ 39.090] (**) TPPS/2 IBM TrackPoint: Device: "/dev/input/event7"
[ 39.112] (II) TPPS/2 IBM TrackPoint: Found 3 mouse buttons
[ 39.112] (II) TPPS/2 IBM TrackPoint: Found relative axes
[ 39.112] (II) TPPS/2 IBM TrackPoint: Found x and y relative axes
[ 39.112] (II) TPPS/2 IBM TrackPoint: Configuring as mouse
[ 39.112] (**) TPPS/2 IBM TrackPoint: YAxisMapping: buttons 4 and 5
[ 39.112] (**) TPPS/2 IBM TrackPoint: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 39.112] (II) XINPUT: Adding extended input device "TPPS/2 IBM TrackPoint" (type: MOUSE)
[ 39.112] (II) TPPS/2 IBM TrackPoint: initialized for relative axes.

Revision history for this message
iapx86 (jlettvin) said :
#17

NEWS!
An improvement on previous conditions!

Reiterating: ubuntu 10.00; two problems:
1) disappearing icons/panel
2) can't escape from black screen yet mouse moves

Problem 1 is unpredictable, so I have no report yet.
Problem 2, I used the following:
Ctrl-Alt-F1 (as suggested earlier in this thread)
login:password succeeded
$ ps -leaf|less (looked through list and noticed "/usr/bin/gnome-screensaver")
Recorded pid (process ID) of gnome-screensaver.
$ kill -9 ${pid}
Ctrl-Alt-F7 (figured this out for myself)
The black screen was gone and my session was where I left it.

This is a huge improvement over being forced into Alt-SysRq+R+E+I+S+U+B.
I have some restoration of confidence.

I did all the things suggested.
Apport was already installed.
I used synaptics to remove gnome-screensaver.

Now the final thing to report:
$ ls -al /usr/bin/gnome-screensaver
There is no such file.
So why was it listed in ps -leaf?

I may be close to success here.

Revision history for this message
iapx86 (jlettvin) said :
#18

Additional information:

After using synaptic to remove gnome-screensaver
there seem to be a lot of references to it remaining in various places.
gnome-screensaver is called by something, even though it doesn't exist.
How it becomes a process with a pid for /usr/bin/gnome-screensaver
when there is no such file is a mystery to me.

To repeat the major questions from this thread:
1) How do I stop getting black screen and mobile mouse from which there is no escape?
2) How do I stop losing icons and panels, forcing me to Magic-SysRq?

I now have a workaround escape from question 1 (although I ought to have a proper fix).
The second problem has not recurred today yet (I hope the recommended fixes helped).

I'd like to add two minor questions to this thread:
3) Why are there literally thousands of 'No such file or directory reports?
4) Why are there recursive directory loops, and why aren't they fatal?

While doing a gross search for gnome-screensaver,
I noticed recursive directory loops and numerous 'No such file or directory' reports.
In /etc, the list of grep matches is very short.
In /usr, the list is very long, mostly 'No such file'.
I eliminated all of the No such file messages in the listing below.

/etc$ sudo grep -i -r gnome-screensaver *
[sudo] password for jlettvin:
Binary file alternatives/x-session-manager matches
grep: blkid.tab: No such file or directory
hibernate/common.conf:## For gnome you need gnome-screensaver-command available.
xdg/menus/gnome-screensavers.menu: <Directory>gnome-screensaver.directory</Directory>

$grep -i -r gnome-screensaver /usr>&Desktop/gnome-screensaver.grp
$grep -v 'No such' Desktop/gnome-screensaver.grp
Binary file /usr/bin/gdmflexiserver matches
Binary file /usr/bin/gnome-power-manager matches
Binary file /usr/bin/gnome-control-center matches
/usr/bin/xdg-screensaver:# There seems to be a DBUS interface for gnome-screensaver
/usr/bin/xdg-screensaver:# http://cvs.gnome.org/viewcvs/gnome-screensaver/src/gs-listener-dbus.c?rev=1.36&view=log
/usr/bin/xdg-screensaver: screensaver_suspend_loop gnome-screensaver-command --poke
/usr/bin/xdg-screensaver: gnome-screensaver-command --activate > /dev/null 2> /dev/null
/usr/bin/xdg-screensaver: gnome-screensaver-command --lock > /dev/null 2> /dev/null
/usr/bin/xdg-screensaver: gnome-screensaver-command --deactivate > /dev/null 2> /dev/null
/usr/bin/xdg-screensaver: elif gnome-screensaver-command --query > /dev/null 2> /dev/null; then
Binary file /usr/bin/compiz matches
Binary file /usr/bin/x-session-manager matches
Binary file /usr/bin/gnome-panel matches
Binary file /usr/bin/gnome-session matches
grep: warning: /usr/bin/X11: recursive directory loop

Binary file /usr/bin/gnome-desktop-item-edit matches
Binary file /usr/lib64/indicator-session/indicator-session-service matches
/usr/lib64/pymodules/python2.6/orca/focus_tracking_presenter.py: # that are now showing (such as gnome-screensaver-dialog).
/usr/lib64/pymodules/python2.6/orca/scripts/apps/gnome-screensaver-dialog/script.py:"""Custom script for gnome-screensaver-dialog."""
Binary file /usr/lib64/pymodules/python2.6/orca/scripts/apps/gnome-screensaver-dialog/__init__.pyc matches
Binary file /usr/lib64/pymodules/python2.6/orca/scripts/apps/gnome-screensaver-dialog/script.pyc matches
/usr/lib64/pymodules/python2.6/orca/scripts/apps/gnome-screensaver-dialog/__init__.py:"""Custom script for gnome-screensaver-dialog."""
grep: warning: /usr/lib64/firefox-addons/searchplugins/common: recursive directory loop

/usr/lib64/python2.6/dist-packages/Onboard/OnboardGtk.py: if config.xid_mode: # XEmbed mode for gnome-screensaver?
Binary file /usr/lib64/python2.6/dist-packages/Onboard/Config.pyc matches
/usr/lib64/python2.6/dist-packages/Onboard/Config.py:GSS_XEMBED_ENABLE_GCONF_KEY = "/apps/gnome-screensaver/embedded_keyboard_enabled"
/usr/lib64/python2.6/dist-packages/Onboard/Config.py:GSS_XEMBED_COMMAND_GCONF_KEY = "/apps/gnome-screensaver/embedded_keyboard_command"
/usr/lib64/python2.6/dist-packages/Onboard/Config.py: help="XEmbed mode for gnome-screensaver")
/usr/lib64/python2.6/dist-packages/Onboard/Config.py: self._gconf_client.add_dir("/apps/gnome-screensaver", \
/usr/lib64/python2.6/dist-packages/Onboard/Config.py: ####### XEmbedding onboard into gnome-screensaver to unlock screen ########
/usr/lib64/python2.6/dist-packages/Onboard/Config.py: # methods concerning the xembed enabled gconf key of the gnome-screensaver
/usr/lib64/python2.6/dist-packages/Onboard/Config.py: Get status of xembed enabled gconf key of the gnome-screensaver.
/usr/lib64/python2.6/dist-packages/Onboard/Config.py: Set status of xembed enabled gconf key of the gnome-screensaver.
/usr/lib64/python2.6/dist-packages/Onboard/Config.py: # methods concerning the xembed command gconf key of the gnome-screensaver
/usr/lib64/python2.6/dist-packages/DistUpgrade/DistUpgradeQuirks.py: """killall gnome-screensaver """
/usr/lib64/python2.6/dist-packages/DistUpgrade/DistUpgradeQuirks.py: logging.debug("killing gnome-screensaver")
/usr/lib64/python2.6/dist-packages/DistUpgrade/DistUpgradeQuirks.py: subprocess.call(["killall", "-q", "gnome-screensaver"])
Binary file /usr/lib64/python2.6/dist-packages/DistUpgrade/DistUpgradeQuirks.pyc matches
Binary file /usr/lib64/gdm/gdm-user-switch-applet matches
grep: warning: /usr/lib64/firefox-3.6.13/searchplugins/common: recursive directory loop

grep: warning: /usr/lib64/firefox-3.6.13/distribution/searchplugins/common: recursive directory loop

Binary file /usr/lib64/gnome-settings-daemon-2.0/libmedia-keys.so matches
/usr/share/gnome/help/gnome-power-manager/C/gnome-power-manager.xml: <command>gnome-screensaver</command> is a session daemon that monitors user
/usr/share/gnome/help/gnome-power-manager/C/gnome-power-manager.xml: <command>gnome-screensaver-preferences</command>, then the login is marked
/usr/share/gnome/help/gnome-power-manager/C/gnome-power-manager.xml: Changing the session idle timeout in <command>gnome-screensaver-preferences</command>
/usr/share/gnome/help/gnome-power-manager/C/gnome-power-manager.xml: <command>gnome-screensaver-preferences</command> then the start of the sliders
/usr/share/gnome/help/gnome-power-manager/C/gnome-power-manager.xml: gnome-screensaver when the lid is closed, or the system performs a suspend or
/usr/share/gnome/help/gnome-power-manager/C/gnome-power-manager.xml: Then the policy keys can be set to force a gnome-screensaver lock and unlock
/usr/share/gnome/help/gnome-power-manager/C/gnome-power-manager.xml: The lock policy for gnome-screensaver is ignored until the simple mode
/usr/share/gnome/help/gnome-power-manager/en_GB/gnome-power-manager.xml: <para><command>gnome-screensaver</command> is a session daemon that monitors user input, and if the mouse has not been moved, or the keyboard been pressed then it starts a timeout. When the value of this timeout reaches the value set in <command>gnome-screensaver-preferences</command>, then the login is marked as 'session idle'. This is when <application>GNOME Power Manager</application> performs all the session idle actions such as enabling low-power mode and lowering the laptop panel brightness.</para>
/usr/share/gnome/help/gnome-power-manager/en_GB/gnome-power-manager.xml: <title>Changing the session idle timeout in <command>gnome-screensaver-preferences</command></title>
/usr/share/gnome/help/gnome-power-manager/en_GB/gnome-power-manager.xml: <para>To make this clearer, the sliders in <command>gnome-power-preferences</command> are set to start at the value of the session-timeout plus one minute, as we cannot logically trigger before the session is marked as idle. If you adjust the value of the 'session idle' timeout in <command>gnome-screensaver-preferences</command> then the start of the sliders in <command>gnome-power-preferences</command> will change accordingly.</para>
/usr/share/gnome/help/gnome-power-manager/en_GB/gnome-power-manager.xml: <para>By default, <application>GNOME Power Manager</application> supports a simple locking scheme. This means that the screen will lock if set to <guilabel>Lock screen</guilabel> in gnome-screensaver when the lid is closed, or the system performs a suspend or hibernate action.</para>
/usr/share/gnome/help/gnome-power-manager/en_GB/gnome-power-manager.xml: <para>Then the policy keys can be set to force a <application>gnome-screensaver</application> lock and unlock when the action is performed:</para>
/usr/share/gnome/help/gnome-power-manager/en_GB/gnome-power-manager.xml: <para>The lock policy for gnome-screensaver is ignored until the simple mode is re-enabled.</para>
/usr/share/gnome/help/system-admin-guide/C/screensavers.xml: <primary>gnome-screensaver</primary>
/usr/share/gnome/help/system-admin-guide/C/screensavers.xml:application for the GNOME Desktop is <application>gnome-screensaver</application>.
/usr/share/gnome/help/system-admin-guide/C/screensavers.xml:The following sections describe how to set preferences for the <application>gnome-screensaver</application> application, and how to change the themes that
/usr/share/gnome/help/system-admin-guide/C/screensavers.xml: <para>Users can also run the command <command>/usr/bin/gnome-screensaver-preferences</command> to open
/usr/share/gnome/help/system-admin-guide/C/screensavers.xml:<screen><userinput>pkg-config --variable=privlibexecdir gnome-screensaver</userinput></screen>
/usr/share/gnome/help/system-admin-guide/C/screensavers.xml:<screen><userinput>pkg-config --variable=themesdir gnome-screensaver</userinput></screen>
/usr/share/gnome/help/gdm/C/gdm.xml: such as the Fast User Switch Applet (FUSA) and gnome-screensaver
/usr/share/gnome/help/gdm/en_GB/gdm.xml: <para>GDM provides the ability to manage the main console display, and displays launched via VT. It is integrated with other programs, such as the Fast User Switch Applet (FUSA) and gnome-screensaver to manage multiple displays on the console via the Xserver Virtual Terminal (VT) interface. It also can manage XDMCP displays.</para>
/usr/share/gnome/help/control-center/C/config-screensaver.xml: <application>xscreensaver</application> or the <application>gnome-screensaver</application>
/usr/share/gnome/help-langpack/gnome-power-manager/en_GB/gnome-power-manager.xml: <para><command>gnome-screensaver</command> is a session daemon that monitors user input, and if the mouse has not been moved, or the keyboard been pressed then it starts a timeout. When the value of this timeout reaches the value set in <command>gnome-screensaver-preferences</command>, then the login is marked as 'session idle'. This is when <application>GNOME Power Manager</application> performs all the session idle actions such as enabling low-power mode and lowering the laptop panel brightness.</para>
/usr/share/gnome/help-langpack/gnome-power-manager/en_GB/gnome-power-manager.xml: <title>Changing the session idle timeout in <command>gnome-screensaver-preferences</command></title>
/usr/share/gnome/help-langpack/gnome-power-manager/en_GB/gnome-power-manager.xml: <para>To make this clearer, the sliders in <command>gnome-power-preferences</command> are set to start at the value of the session-timeout plus one minute, as we cannot logically trigger before the session is marked as idle. If you adjust the value of the 'session idle' timeout in <command>gnome-screensaver-preferences</command> then the start of the sliders in <command>gnome-power-preferences</command> will change accordingly.</para>
/usr/share/gnome/help-langpack/gnome-power-manager/en_GB/gnome-power-manager.xml: <para>By default, <application>GNOME Power Manager</application> supports a simple locking scheme. This means that the screen will lock if set to <guilabel>Lock screen</guilabel> in gnome-screensaver when the lid is closed, or the system performs a suspend or hibernate action.</para>
/usr/share/gnome/help-langpack/gnome-power-manager/en_GB/gnome-power-manager.xml: <para>Then the policy keys can be set to force a <application>gnome-screensaver</application> lock and unlock when the action is performed:</para>
/usr/share/gnome/help-langpack/gnome-power-manager/en_GB/gnome-power-manager.xml: <para>The lock policy for gnome-screensaver is ignored until the simple mode is re-enabled.</para>
/usr/share/gnome/help-langpack/gdm/en_GB/gdm.xml: <para>GDM provides the ability to manage the main console display, and displays launched via VT. It is integrated with other programs, such as the Fast User Switch Applet (FUSA) and gnome-screensaver to manage multiple displays on the console via the Xserver Virtual Terminal (VT) interface. It also can manage XDMCP displays.</para>
/usr/share/apport/symptoms/security.py: return 'gnome-screensaver'
/usr/share/apport/symptoms/security.py: return 'gnome-screensaver'
/usr/share/apport/symptoms/security.py: return 'gnome-screensaver'
/usr/share/compizconfig/normal.profile:s0_close_matches = ((type=Normal | Utility | Unknown) | name=sun-awt-X11-XFramePeer | name=sun-awt-X11-XDialogPeer) & !(role=toolTipTip | role=qtooltip_label) & !(type=Normal & override_redirect=1) & !(name=gnome-screensaver);(type=Menu | PopupMenu | DropdownMenu | Dialog | ModalDialog | Normal);(type=Tooltip | Notification)
/usr/share/compizconfig/normal.profile:s0_open_matches = ((type=Normal | Utility | Unknown) | name=sun-awt-X11-XFramePeer | name=sun-awt-X11-XDialogPeer) & !(role=toolTipTip | role=qtooltip_label) & !(type=Normal & override_redirect=1) & !(name=gnome-screensaver);(type=Menu | PopupMenu | DropdownMenu | Dialog | ModalDialog | Normal);(type=Tooltip | Notification)
/usr/share/compizconfig/extra.profile:s0_close_matches = ((type=Normal | Utility | Unknown) | name=sun-awt-X11-XFramePeer | name=sun-awt-X11-XDialogPeer) & !(role=toolTipTip | role=qtooltip_label) & !(type=Normal & override_redirect=1) & !(name=gnome-screensaver);(type=Menu | PopupMenu | DropdownMenu | Dialog | ModalDialog | Normal);(type=Tooltip | Notification)
/usr/share/compizconfig/extra.profile:s0_open_matches = ((type=Normal | Utility | Unknown) | name=sun-awt-X11-XFramePeer | name=sun-awt-X11-XDialogPeer) & !(role=toolTipTip | role=qtooltip_label) & !(type=Normal & override_redirect=1) & !(name=gnome-screensaver);(type=Menu | PopupMenu | DropdownMenu | Dialog | ModalDialog | Normal);(type=Tooltip | Notification)
/usr/share/gconf/defaults/16_ubuntu-artwork:/apps/gnome-screensaver/theme screensavers-ubuntu_theme
/usr/share/gconf/schemas/gnome-power-manager.schemas: <short>Use gnome-screensaver lock setting</short>
/usr/share/gconf/schemas/gnome-power-manager.schemas: <long>Whether to use the screen lock setting of gnome-screensaver to decide if the screen is locked after a hibernate, suspend or blank screen.</long>
/usr/share/pyshared/Onboard/OnboardGtk.py: if config.xid_mode: # XEmbed mode for gnome-screensaver?
/usr/share/pyshared/Onboard/Config.py:GSS_XEMBED_ENABLE_GCONF_KEY = "/apps/gnome-screensaver/embedded_keyboard_enabled"
/usr/share/pyshared/Onboard/Config.py:GSS_XEMBED_COMMAND_GCONF_KEY = "/apps/gnome-screensaver/embedded_keyboard_command"
/usr/share/pyshared/Onboard/Config.py: help="XEmbed mode for gnome-screensaver")
/usr/share/pyshared/Onboard/Config.py: self._gconf_client.add_dir("/apps/gnome-screensaver", \
/usr/share/pyshared/Onboard/Config.py: ####### XEmbedding onboard into gnome-screensaver to unlock screen ########
/usr/share/pyshared/Onboard/Config.py: # methods concerning the xembed enabled gconf key of the gnome-screensaver
/usr/share/pyshared/Onboard/Config.py: Get status of xembed enabled gconf key of the gnome-screensaver.
/usr/share/pyshared/Onboard/Config.py: Set status of xembed enabled gconf key of the gnome-screensaver.
/usr/share/pyshared/Onboard/Config.py: # methods concerning the xembed command gconf key of the gnome-screensaver
/usr/share/pyshared/orca/focus_tracking_presenter.py: # that are now showing (such as gnome-screensaver-dialog).
/usr/share/pyshared/orca/scripts/apps/gnome-screensaver-dialog/script.py:"""Custom script for gnome-screensaver-dialog."""
/usr/share/pyshared/orca/scripts/apps/gnome-screensaver-dialog/__init__.py:"""Custom script for gnome-screensaver-dialog."""
/usr/share/pyshared/DistUpgrade/DistUpgradeQuirks.py: """killall gnome-screensaver """
/usr/share/pyshared/DistUpgrade/DistUpgradeQuirks.py: logging.debug("killing gnome-screensaver")
/usr/share/pyshared/DistUpgrade/DistUpgradeQuirks.py: subprocess.call(["killall", "-q", "gnome-screensaver"])
/usr/share/python-support/gnome-orca.public:/usr/share/pyshared/orca/scripts/apps/gnome-screensaver-dialog/__init__.py
/usr/share/python-support/gnome-orca.public:/usr/share/pyshared/orca/scripts/apps/gnome-screensaver-dialog/script.py
/usr/share/gdm/guest-session/guest-session-launch:gnome-screensaver-command --lock || xscreensaver-command -lock || true
/usr/share/doc/libpam-gnome-keyring/README.Debian:The default PAM configuration for GDM and gnome-screensaver already
/usr/share/compiz/animation.xml: <value>((type=Normal | Unknown) | name=sun-awt-X11-XFramePeer | name=sun-awt-X11-XDialogPeer) &amp; !(role=toolTipTip | role=qtooltip_label) &amp; !(type=Normal &amp; override_redirect=1) &amp; !(name=gnome-screensaver)</value>
/usr/share/compiz/animation.xml: <value>((type=Normal | Unknown) | name=sun-awt-X11-XFramePeer | name=sun-awt-X11-XDialogPeer) &amp; !(role=toolTipTip | role=qtooltip_label) &amp; !(type=Normal &amp; override_redirect=1) &amp; !(name=gnome-screensaver)</value>
Binary file /usr/share/command-not-found/programs.d/amd64-main.db matches
Binary file /usr/share/locale-langpack/en_GB/LC_MESSAGES/gnome-screensaver.mo matches
Binary file /usr/share/locale-langpack/en@shaw/LC_MESSAGES/gnome-power-manager.mo matches
Binary file /usr/share/locale-langpack/en_AU/LC_MESSAGES/gnome-screensaver.mo matches
Binary file /usr/share/locale-langpack/en_CA/LC_MESSAGES/gnome-screensaver.mo matches
/usr/share/hibernate/scriptlets.d/lock:AddConfigHelp "LockGnomeScreenSaver <boolean>" "Lock all local X11 sessions with gnome-screensaver running before suspending."
/usr/share/hibernate/scriptlets.d/lock: if ! command -v gnome-screensaver-command > /dev/null 2>&1 ; then
/usr/share/hibernate/scriptlets.d/lock: vecho 0 'Cannot lock with gnome-screensaver. `gnome-screensaver-command` not found.'
/usr/share/hibernate/scriptlets.d/lock: for xpid in `pidof gnome-screensaver` ; do
/usr/share/hibernate/scriptlets.d/lock: vecho 2 "Locking $xuser's gnome-screensaver on display $xdisp using authority file $xauth"
/usr/share/hibernate/scriptlets.d/lock: DISPLAY=$xdisp XAUTHORITY=$xauth DBUS_SESSION_BUS_ADDRESS=$xdbus su $xuser -c "$(command -v gnome-screensaver-command) --lock"
/usr/share/hibernate/scriptlets.d/lock: vecho 0 "Failed to activate gnome-screensaver on $xdisp using authority file $xauth."
/usr/share/hibernate/scriptlets.d/lock: # anything. It just calls gnome-screensaver-command --poke, which makes
/usr/share/hibernate/scriptlets.d/lock: command -v gnome-screensaver-command > /dev/null 2>&1 || return
/usr/share/hibernate/scriptlets.d/lock: for xpid in `pidof gnome-screensaver` ; do
/usr/share/hibernate/scriptlets.d/lock: vecho 2 "Unlocking $xuser's gnome-screensaver on display $xdisp using authority file $xauth"
/usr/share/hibernate/scriptlets.d/lock: DISPLAY=$xdisp XAUTHORITY=$xauth DBUS_SESSION_BUS_ADDRESS=$xdbus su $xuser -c "$(command -v gnome-screensaver-command) --poke"
Binary file /usr/lib/indicator-session/indicator-session-service matches
/usr/lib/pymodules/python2.6/orca/focus_tracking_presenter.py: # that are now showing (such as gnome-screensaver-dialog).
/usr/lib/pymodules/python2.6/orca/scripts/apps/gnome-screensaver-dialog/script.py:"""Custom script for gnome-screensaver-dialog."""
Binary file /usr/lib/pymodules/python2.6/orca/scripts/apps/gnome-screensaver-dialog/__init__.pyc matches
Binary file /usr/lib/pymodules/python2.6/orca/scripts/apps/gnome-screensaver-dialog/script.pyc matches
/usr/lib/pymodules/python2.6/orca/scripts/apps/gnome-screensaver-dialog/__init__.py:"""Custom script for gnome-screensaver-dialog."""
grep: warning: /usr/lib/firefox-addons/searchplugins/common: recursive directory loop

/usr/lib/python2.6/dist-packages/Onboard/OnboardGtk.py: if config.xid_mode: # XEmbed mode for gnome-screensaver?
Binary file /usr/lib/python2.6/dist-packages/Onboard/Config.pyc matches
/usr/lib/python2.6/dist-packages/Onboard/Config.py:GSS_XEMBED_ENABLE_GCONF_KEY = "/apps/gnome-screensaver/embedded_keyboard_enabled"
/usr/lib/python2.6/dist-packages/Onboard/Config.py:GSS_XEMBED_COMMAND_GCONF_KEY = "/apps/gnome-screensaver/embedded_keyboard_command"
/usr/lib/python2.6/dist-packages/Onboard/Config.py: help="XEmbed mode for gnome-screensaver")
/usr/lib/python2.6/dist-packages/Onboard/Config.py: self._gconf_client.add_dir("/apps/gnome-screensaver", \
/usr/lib/python2.6/dist-packages/Onboard/Config.py: ####### XEmbedding onboard into gnome-screensaver to unlock screen ########
/usr/lib/python2.6/dist-packages/Onboard/Config.py: # methods concerning the xembed enabled gconf key of the gnome-screensaver
/usr/lib/python2.6/dist-packages/Onboard/Config.py: Get status of xembed enabled gconf key of the gnome-screensaver.
/usr/lib/python2.6/dist-packages/Onboard/Config.py: Set status of xembed enabled gconf key of the gnome-screensaver.
/usr/lib/python2.6/dist-packages/Onboard/Config.py: # methods concerning the xembed command gconf key of the gnome-screensaver
/usr/lib/python2.6/dist-packages/DistUpgrade/DistUpgradeQuirks.py: """killall gnome-screensaver """
/usr/lib/python2.6/dist-packages/DistUpgrade/DistUpgradeQuirks.py: logging.debug("killing gnome-screensaver")
/usr/lib/python2.6/dist-packages/DistUpgrade/DistUpgradeQuirks.py: subprocess.call(["killall", "-q", "gnome-screensaver"])
Binary file /usr/lib/python2.6/dist-packages/DistUpgrade/DistUpgradeQuirks.pyc matches
Binary file /usr/lib/gdm/gdm-user-switch-applet matches
grep: warning: /usr/lib/firefox-3.6.13/searchplugins/common: recursive directory loop

grep: warning: /usr/lib/firefox-3.6.13/distribution/searchplugins/common: recursive directory loop

Binary file /usr/lib/gnome-settings-daemon-2.0/libmedia-keys.so matches

Revision history for this message
iapx86 (jlettvin) said :
#19

Hopes dashed by new problem, maybe related.

While running a python program, the system froze solid.
Blinking Caps-Lock light.
Ctrl-Alt-F1 gave nothing.
Alt-SysRq+R+E+I+S+U+B gave nothing.
I had no choice but to power off and reboot.
I rebooted to Ubuntu 9.10 and rand fsck on the unmounted Ubuntu 10.10 disk.

# fsck /dev/sdb1
fsck from util-linux-ng 2.16
e2fsck 1.41.9 (22-Aug-2009)
/dev/sdb1: clean, 307860/60317696 files, 14280484/241266432 blocks (check after next mount)

Now I shall try to reboot to 10.10 and see if damage was done.

Can you help with this problem?

Provide an answer of your own, or ask iapx86 for more information if necessary.

To post a message you must log in.