critical battery state action destroys netbook remix on lucid

[Seva Gluschenko]

I've just ran out of my notebook's battery hanging out a bit too long. Instead of shutting down, Lucid Lynx (10.04) forced my user session to close and showed me gdm greeting. At this time I've connected my notebook to the power supply. After logging in I've found a classic session w/o panels. This Ubuntu 10.04 NBR had been upgraded from 9.10, I don't know if it affects anything.
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: gvs 1433 F.... pulseaudio
 /dev/snd/pcmC0D0p: gvs 1433 F...m pulseaudio
CRDA: Error: [Errno 2] Нет такого файла или каталога
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf4800000 irq 22'
   Mixer name : 'Intel G45 DEVCTG'
   Components : 'HDA:14f15051,1179ff52,00100000 HDA:80862802,80860101,00100000'
   Controls : 18
   Simple ctrls : 8
CheckboxSubmission: f11adeb5d021530d2507d98f9109337f
CheckboxSystem: b1865df84255b8716d3bcc269ff410d1
DistroRelease: Ubuntu 10.04
Frequency: This has only happened once.
GnomeSessionIdleInhibited: No
GnomeSessionInhibitors: None
GnomeSessionSuspendInhibited: No
HibernationDevice: RESUME=UUID=06618ac6-7594-4c17-ba10-e2d953250d19
InstallationMedia: Ubuntu-Netbook-Remix 9.10 "Karmic Koala" - Release i386 (20091028.4)
MachineType: TOSHIBA Satellite U400
Package: linux (not installed)
PackageArchitecture: i386
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic root=UUID=63e1b95c-d691-43c1-b4ad-00e764e73296 ro quiet splash
ProcEnviron:
 LANG=ru_RU.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
Regression: No
RelatedPackageVersions: linux-firmware 1.34
Reproducible: No
Tags: lucid lucid needs-upstream-testing
Uname: Linux 2.6.32-22-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 05/19/2009
dmi.bios.vendor: TOSHIBA
dmi.bios.version: V3.80
dmi.board.name: Satellite U400
dmi.board.vendor: TOSHIBA
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnTOSHIBA:bvrV3.80:bd05/19/2009:svnTOSHIBA:pnSatelliteU400:pvrPSU44E-0GC048NW:rvnTOSHIBA:rnSatelliteU400:rvrNotApplicable:cvnTOSHIBA:ct10:cvrN/A:
dmi.product.name: Satellite U400
dmi.product.version: PSU44E-0GC048NW
dmi.sys.vendor: TOSHIBA

[Leo (leorolla)]

Could you describe your power settings?

Did you use the computer many times since this happened? Did you have the same problem?

Maybe you can find the pertinent lines in one of the /var/log/sys* files to see if there was some powerdown signal sent etc?

Could you open a terminal and run
apport-collect 581245
?

Thank you.

[Seva Gluschenko (gvs-ya)]

apport information

[Seva Gluschenko (gvs-ya)]

apport information

[Seva Gluschenko (gvs-ya)]

apport information

[Seva Gluschenko (gvs-ya)]

apport information

[Seva Gluschenko (gvs-ya)]

apport information

[Seva Gluschenko (gvs-ya)]

apport information

[Seva Gluschenko (gvs-ya)]

apport information

[Seva Gluschenko (gvs-ya)]

apport information

[Seva Gluschenko (gvs-ya)]

apport information

[Seva Gluschenko (gvs-ya)]

apport information

[Seva Gluschenko (gvs-ya)]

apport information

[Seva Gluschenko (gvs-ya)]

apport information

[Seva Gluschenko (gvs-ya)]

apport information

[Seva Gluschenko (gvs-ya)]

apport information

[Seva Gluschenko (gvs-ya)]

Well, it happened just once because I never ran out of battery before and don't plan to do that in the future.

I'd changed my power settings from default "suspend" to "shut down".

My syslog rotation is default one, so the oldest log available is dated 2010-05-26. It's kinda too late to be sorry.

I've run apport-collect despite I doubt it would help much. Most probably, the problem is somewhere in GNOME settings

[Seva Gluschenko (gvs-ya)]

apport information

[Seva Gluschenko (gvs-ya)]

apport information

[Seva Gluschenko (gvs-ya)]

apport information

[Seva Gluschenko (gvs-ya)]

apport information

[Seva Gluschenko (gvs-ya)]

apport information

[Seva Gluschenko (gvs-ya)]

apport information

[Seva Gluschenko (gvs-ya)]

apport information

[Seva Gluschenko (gvs-ya)]

apport information

[Leo (leorolla)]

When you logged in after this logout, what session did you choose?

Does you computer suspend and wake up wihout problems?

Don't you have .gz files with older syslogs?

[Seva Gluschenko (gvs-ya)]

I didn't choose a session, so it was default choice if any available.

My computer suspends and wakes up without any problems, I virtually never reboot (only after some updates).

Unfortunately, I don't have older syslogs.

[Leo (leorolla)]

And now, what happens when you choose UNE at the login screen?
Is the result the same for every user?

[Seva Gluschenko (gvs-ya)]

Well, I don't wish to terminate my session now. I'll tell you when I have a chance to login next time

[Leo (leorolla)]

Of course. When and if you want.
For information: you can switch user without terminating you session. And unlike MS-Windows, it really works.

I will mark this report "Invalid" as it seems that the logs have been lost and it will be a pain to try and understand exactly what happened (and probably we won't succeed anyway).

If you can reproduce the same error again, please mark this report as "New" for each package, and after that please run "apport-collect 581245" in the terminal, and also attach the syslog.

[Jeremy Foshee (jeremyfoshee)]

Seva,
   I look forward to your update when you have a chance to log in again.

Thanks!

~JFo

[penalvch (penalvch)]

Seva Gluschenko, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily kernel folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.12-rc2

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]