Black screen using recent version Ubuntu with nvidia.

[Rob Koll]

As far as I can judge, i am experiencing the same issues as reported int bug 1068501. Up to Ubuntu 12.04 my machine was running OK, using the nvidia proprietary driver. Took some fiddling with X configuration file to get it on 1920*1200 corresponding to the screen I am using. Starting from 12.10 the desktop doesn't show. All I see is a one large area of one color. The color may change at some points in time, not clear when and why. Interval between changing is like half a minute or longer. In the one color screen only the mouse pointer is visible. When the pointer is moved over the screen I can guess where underlying windows are by the changes in the mouse pointer. Note that after the upgrade still startup programs where active, proven by the music player starting and evolution sounding new messages. As nvidia is used, opening a terminal by ctrl-alt-F1 doesn work (screen indicates that the video signal stops). But an invisible terminal can be opened by ctrl-alt-t. The terminal is not visible, but commands typed are executed. When the X session is stopped by sudo killall Xorg the login screen will become visible and works correct. In the transition even the background and closing windows may be shortly viewed. It looks like that the X session just has one large window on top of everything. Maybe it is a kind of background shown on top and not as background. Note that due to nvidia not working and even nouveau showing problems, those are disabled now. Now I have visible and working system, at low resolution (1024*768) and slow. Probably this is what you will see in the information gathered by ubuntu-bug. I am using 3 disks and multiple partitions, so I can use the system and experiment in another boot. So be aware of the fact that the issue is on another partition. Please instruct how to obtain relevant information from that. Note also that ubuntu-bug reported:

robbie@RobbiesP4Ubuntu:~$ [6254:6281:0530/185859:ERROR:object_proxy.cc(624)] Failed to get name owner. Got org.freedesktop.DBus.Error.NameHasNoOwner: Could not get owner of name 'org.chromium.Mtpd': no such name
[6254:6281:0530/185859:ERROR:object_proxy.cc(624)] Failed to get name owner. Got org.freedesktop.DBus.Error.NameHasNoOwner: Could not get owner of name 'org.chromium.Mtpd': no such name
[6254:6254:0530/185859:ERROR:object_proxy.cc(529)] Failed to call method: org.chromium.Mtpd.EnumerateStorages: object_path= /org/chromium/Mtpd: org.freedesktop.DBus.Error.ServiceUnknown: The name org.chromium.Mtpd was not provided by any .service files

As suggested in 1068601 I tried the daily build 13.10. That runs OK from live CD. Installs OK on hard disk (other partition, multi boot). After the install, I left the system. Upon returning, after wake up of screen saver, the desktop seemed ok. But any windows that open contain no readable data, just some kind of noise more or less regular pattern. So not really useful. As suggested in 1068601, I tried to gather info with apport-collect. Just put some scripts on the disk and started the scripts (with a short name) by typing the command in an invisible window. The first time I got a message indicating to install python-apport. So I did, after login into advanced options. Then it prompted to install python-launchpadlib. So again reboot, install, reboot. Now a strange thing happened. The desktop became visible, and contained one windows, with an internet explorer, probably firefox, no menus or program start icons. It was not possible to move the firefox window. Firefox allows to browse by typing URL and clicking on links. So I tried to look into help about, but no menu item could be opened. Also the quit button failed. But I could browse and find keys combination ctrl w (I believe). That closes the window. Then no more windows can be opened. Also ctrl-alt-t and typing commands seem not to execute commands (in an invisible underlying window).

Note that I did not change the package in which the bug is located. In my humble opinion it is a kind of combination flaw where properties of the kernel, X and the nvidia driver come together and manifest only on certain hardware. There are similar bug reports that indicate a timing issue. The changed behavior after installing python-launchpadlib may support that. But having seen that the bug can manifest from live CD, from classic hard drive and from SSD doesn't support the timing thing in my view.

One more note (just trying to give information): I can boot into advanced options, enable network, drop to root, and install or remove software. By that I can add or remove the nvidia driver. By that, I can switch on the bug or switch off - work around (price payed: low resolution). Note also that I need to use nvidia-173. At least that is the only one I found working on my hardware. The times I tried nouveau there have been other issues, like not reaching the resolution of my screen or just plain not working at all. Only starting from 13.10 daily build nouveau seems to reach a more or less working state.

Please instruct how to collect useful data.

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: linux-image-3.8.0-22-generic 3.8.0-22.33
ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11
Uname: Linux 3.8.0-22-generic i686
ApportVersion: 2.9.2-0ubuntu8
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: robbie 2326 F.... pulseaudio
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
CurrentDmesg: [ 14.636547] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Date: Thu May 30 18:57:45 2013
HibernationDevice: RESUME=UUID=3e4325d2-8263-498f-8778-88377df64575
InstallationDate: Installed on 2013-03-02 (89 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-22-generic root=UUID=10ff3bd0-3467-4035-a33e-2e3119c073c0 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.8.0-22-generic N/A
 linux-backports-modules-3.8.0-22-generic N/A
 linux-firmware 1.106
RfKill:

SourcePackage: linux
UpgradeStatus: Upgraded to raring on 2013-05-03 (26 days ago)
dmi.bios.date: 01/23/2006
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 080009
dmi.board.name: P4P800SE
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: Rev 2.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080009:bd01/23/2006:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASUSTeKComputerInc.:rnP4P800SE:rvrRev2.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.10 kernel[0].

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.10-rc3-saucy/

[Rob Koll (0x2jjt9d-agq-0tlbog0j)]

I attempted to test v3.10.0 kernel. But after the install, the machine did not boot into the nvidia driver. I un installed the nvidia driver. Then the machine seems to boot and use a low resolution driver. I tried to install the nvidia driver. That failed. The build of the kernel (I guess a new link) failed, indicating that an error is in the make.log file. In that process, the machine issued a new bug, 1185786. Up to my knowledge, issues with the daily build kernels and nvidia are known, so I guess the new bug is no new news. I hope you manage to handle the bugs together. I will attempt to upload the log file, but I guess that is done better at bug 118676.

Do you see a solution to get the V3.10.0 kernel running with the nvidia-173?

Are you interested in video captures of the machine during boot and shortly after to see how the bug manifests? I made such videos based on the old status (kernel 3.9.0). I am not sure whether or not I can upload the videos, files in the order of one G, .mov format taken with Canon D60.

At this point I do not place any tags, hoping that there are still tricks to do the check somehow.

[Rob Koll (0x2jjt9d-agq-0tlbog0j)]

Now I see that I refer to an incorrect bug. The reference in #4 should be to Bug #1186786.

[Launchpad Janitor (janitor)]

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