kde 4.4.2: black screen after plymouth

Bug #613751 reported by paolinuz
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nvidia-graphics-drivers (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: kdebase-workspace

Often, after plymouth is loaded, X don't start with nvidia driver.
With kdm I get black screen (my monitors flashes various time) and I can only reboot my system pressing the reset button on my laptop.
Only after "n" reboot i can see kdm login screen.

I have installed gnome-desktop wiht gdm as default login manager.

Also with gdm i have the same problem but i can see diagnostic window that show me the following message:

Failed to allocate primary buffer. out of memory
EEE NVIDIA(0): *** Aborting ***

Than i can acces to X with vesa driver and than i can reboot safety my system.
After reboot X start with nvidia driver and I can login on my system...

My system laptop:
Acer TravelMate 5620
kubuntu lucid 10.04 32 bit
kde 4.4.2
nvidia driver 256.35
01:00.0 VGA compatible controller: nVidia Corporation G72M [Quadro NVS 110M/GeForce Go 7300] (rev a1)

Tags: kubuntu
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Driver issue.

affects: kdebase-workspace (Ubuntu) → nvidia-graphics-drivers (Ubuntu)
Bryce Harrington (bryce)
tags: added: kubuntu
Revision history for this message
Daniel Hahler (blueyed) wrote :

Just for info: instead of hard-resetting your machine, you can "soft-reboot" it using the "Alt-SysReq-REISUB" method, see http://mark.koli.ch/2009/02/linux-magic-sysrq-key-r-e-i-s-u-b-reboot-even-if-system-utterly-broken.html

Revision history for this message
Daniel Hahler (blueyed) wrote :

This just happened to me, too - using xorg-edgers PPA.

Revision history for this message
Daniel Hahler (blueyed) wrote :

My workaround (also before using xorg-edgers (which is required currently for nvidia)) is to boot the recovery kernel, wait until disk activity is silent, then manually do "init 2" and "start kdm".

Revision history for this message
Daniel Hahler (blueyed) wrote :

See also bug 607490, which indicates this might be a kernel issue.

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.