[Ubuntu-x-swat] [Bug 544817] Re: Nvidia 6150 fails to start Xorg with nvidia-current

This is caused by Nvidia driver and Hauppauge 1600 being in the same system. Updating /etc/default/grub's GRUB_CMDLINE_LINUX_DEFAULT to include "vmalloc=256MB" solves issue ** Changed in: nvidia-graphics-drivers (Ubuntu) Status: New => Invalid -- Nvidia 6150 fails to start Xorg with nvid

[Ubuntu-x-swat] [Bug 544817] Re: Nvidia 6150 fails to start Xorg with nvidia-current

** Attachment added: "BootDmesg.txt" http://launchpadlibrarian.net/41684555/BootDmesg.txt ** Attachment added: "CurrentDmesg.txt" http://launchpadlibrarian.net/41684556/CurrentDmesg.txt ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/41684557/Dependencies.txt ** A

[Ubuntu-x-swat] [Bug 544817] [NEW] Nvidia 6150 fails to start Xorg with nvidia-current

Public bug reported: (EE) NVIDIA(0): Failed to initialize NVIDIA graphics device PCI:0:5:0 If Proprietary driver is selected during Mythbuntu installation, Xorg/GDM fails to start on reboot. Selecting the Open Source driver during install works correctly. But if nvidia- current is activated fro

[Ubuntu-x-swat] [Bug 544793] Re: With nvidia-173 Xorg fails to start

As I had tried removing nvidia-current as a troubleshooting step, I will resubmit with nvidia-current driver installed ** Changed in: nvidia-graphics-drivers (Ubuntu) Status: New => Invalid -- With nvidia-173 Xorg fails to start https://bugs.launchpad.net/bugs/544793 You received this bug

[Ubuntu-x-swat] [Bug 544793] Re: With nvidia-current Xorg fails to start

** Attachment added: "BootDmesg.txt" http://launchpadlibrarian.net/41682541/BootDmesg.txt ** Attachment added: "CurrentDmesg.txt" http://launchpadlibrarian.net/41682542/CurrentDmesg.txt ** Attachment added: "GdmLog.txt" http://launchpadlibrarian.net/41682543/GdmLog.txt ** Attachment ad

[Ubuntu-x-swat] [Bug 544793] [NEW] With nvidia-173 Xorg fails to start

Public bug reported: During Mythbuntu (Lucid beta1) install, if the proprietary nvidia driver is selected, after reboot system boots to a text login screen (X fails to start). If instead OpenSource driver is selected during install, system reboots to a working Xorg. If nvidia-current (recomm

[Ubuntu-x-swat] [Bug 526175] Re: Nvidia-Setting of "Separate X Screen" causes Nautilus to continually respawn itself 100% CPU usage

*** This bug is a duplicate of bug 508890 *** https://bugs.launchpad.net/bugs/508890 This appears to be a duplicate of: bug 508890 https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/508890 ** This bug has been marked a duplicate of bug 508890 Nautilus crashes when there are multiple

[Ubuntu-x-swat] [Bug 526175] Re: Nvidia-Setting of "Separate X Screen" causes Nautilus to continually respawn itself 100% CPU usage

** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/39582796/Dependencies.txt -- Nvidia-Setting of "Separate X Screen" causes Nautilus to continually respawn itself 100% CPU usage https://bugs.launchpad.net/bugs/526175 You received this bug notification because you are a me

[Ubuntu-x-swat] [Bug 526175] [NEW] Nvidia-Setting of "Separate X Screen" causes Nautilus to continually respawn itself 100% CPU usage

Public bug reported: If I enable "Separate X Screen" with nvidia-settings, Xorg.conf is saved and GDM restarted - after logging back-in mouse pointer constantly alternates between pointer and spinning wheel. CPU jumping to 100%. Nautilus is constantly respawning itself trying to open a file manag