white screen after login

Bug #1121113 reported by Andrey Kolchenko
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Incomplete
Medium
Unassigned

Bug Description

After login to my profile, I get a white screen and I cannot do anything (only move a mouse).
I tryed to switch to Ubuntu, Gnome Classic and Pantheon. It does not work.
Then I in other tty kill lightdm, and log in again. This manipulations helped me, but it's a bug.
I got this trouble after update a system yesterday.

ProblemType: Bug
DistroRelease: elementary OS 0.2
Package: elementary-desktop 1.295-0~369~precise1 [origin: LP-PPA-elementary-os-daily]
ProcVersionSignature: Ubuntu 3.2.0-38.59-generic 3.2.37
Uname: Linux 3.2.0-38-generic x86_64
ApportVersion: 2.0.1-0ubuntu17.1+elementary3~precise1
Architecture: amd64
CrashDB: elementary_meta
Date: Sun Feb 10 16:14:35 2013
InstallationMedia: elementary OS 0.2 "Luna" - Beta 1 amd64 (20121114)
MarkForUpload: True
SourcePackage: elementary-meta
SuspiciousXErrors:

ThirdParty: True
UpgradeStatus: No upgrade log present (probably fresh install)
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: PCH [HDA Intel PCH], device 0: ALC887-VD Analog [ALC887-VD Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
ApportVersion: 2.0.1-0ubuntu17.1+elementary3~precise1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: komex 5125 F.... pulseaudio
 /dev/snd/controlC1: komex 5125 F.... pulseaudio
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
Card0.Amixer.info:
 Card hw:0 'PCH'/'HDA Intel PCH at 0xf7c10000 irq 45'
   Mixer name : 'Realtek ALC887-VD'
   Components : 'HDA:10ec0887,1462d798,00100302'
   Controls : 35
   Simple ctrls : 19
Card1.Amixer.info:
 Card hw:1 'C110'/'Webcam C110 at usb-0000:00:1a.0-1.6, high speed'
   Mixer name : 'USB Mixer'
   Components : 'USB046d:0829'
   Controls : 0
   Simple ctrls : 0
Card1.Amixer.values:

CurrentDmesg:
 [ 6.179806] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
 [ 16.689455] eth0: no IPv6 routers present
DistroRelease: elementary OS 0.2
HibernationDevice: RESUME=UUID=b1eca610-3820-4da1-8a1b-78fdc15a3c58
InstallationMedia: elementary OS 0.2 "Luna" - Beta 1 amd64 (20121114)
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
MachineType: MSI MS-7798
MarkForUpload: True
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-38-generic root=UUID=8279c01f-53ea-49ea-8c65-1133498cdb7e ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.2.0-38.59-generic 3.2.37
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-38-generic N/A
 linux-backports-modules-3.2.0-38-generic N/A
 linux-firmware 1.79.2
RfKill:

StagingDrivers: mei
Tags: luna staging
Uname: Linux 3.2.0-38-generic x86_64
UnreportableReason: Этот пакет «elementary» не является официальным. Пожалуйста, удалите все дополнительные пакеты и повторите снова.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 04/20/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V1.1
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: B75MA-P45 (MS-7798)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.1:bd04/20/2012:svnMSI:pnMS-7798:pvr1.0:rvnMSI:rnB75MA-P45(MS-7798):rvr1.0:cvnMSI:ct3:cvr1.0:
dmi.product.name: MS-7798
dmi.product.version: 1.0
dmi.sys.vendor: MSI

Revision history for this message
Andrey Kolchenko (komex) wrote :
Revision history for this message
Chris Johns (ter0) wrote :

I got this after upgrading to 3.2.37 on two machines.

Revision history for this message
Sergey "Shnatsel" Davidoff (shnatsel) wrote :

Must be a kernel bug then.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in linux (Ubuntu):
status: New → Confirmed
affects: elementaryos → linux (Ubuntu)
tags: added: regression-update
Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1121113

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
tags: added: precise
Revision history for this message
Andrey Kolchenko (komex) wrote : AcpiTables.txt

apport information

tags: added: apport-collected staging
description: updated
Revision history for this message
Andrey Kolchenko (komex) wrote : AlsaDevices.txt

apport information

Revision history for this message
Andrey Kolchenko (komex) wrote : ArecordDevices.txt

apport information

Revision history for this message
Andrey Kolchenko (komex) wrote : BootDmesg.txt

apport information

Revision history for this message
Andrey Kolchenko (komex) wrote : Card0.Amixer.values.txt

apport information

Revision history for this message
Andrey Kolchenko (komex) wrote : Card0.Codecs.codec.0.txt

apport information

Revision history for this message
Andrey Kolchenko (komex) wrote : Lspci.txt

apport information

Revision history for this message
Andrey Kolchenko (komex) wrote : Lsusb.txt

apport information

Revision history for this message
Andrey Kolchenko (komex) wrote : PciMultimedia.txt

apport information

Revision history for this message
Andrey Kolchenko (komex) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Andrey Kolchenko (komex) wrote : ProcEnviron.txt

apport information

Revision history for this message
Andrey Kolchenko (komex) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Andrey Kolchenko (komex) wrote : ProcModules.txt

apport information

Revision history for this message
Andrey Kolchenko (komex) wrote : PulseList.txt

apport information

Revision history for this message
Andrey Kolchenko (komex) wrote : UdevDb.txt

apport information

Revision history for this message
Andrey Kolchenko (komex) wrote : UdevLog.txt

apport information

Revision history for this message
Andrey Kolchenko (komex) wrote : WifiSyslog.txt

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Andrey Kolchenko (komex) wrote :

Yes, It's a kernel bug (3.2.0-38-generic). When I switch kernel to 3.2.0-37-generic, the problem was disappeared.

Revision history for this message
Chris Johns (ter0) wrote :

Yeah, sorry, in my previous comment I put the wrong Kernel version, it's in 3.2.0-38.

Revision history for this message
linrunner (linrunner) wrote :
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.8 kernel[0] (Not a kernel in the daily directory) and install both the linux-image and linux-image-extra .deb packages.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8-rc7-raring/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.