Installing nvidia-glx-new restricted drivers increase gnome login time

Bug #160535 reported by Mike Mackintosh
6
Affects Status Importance Assigned to Milestone
linux-restricted-modules-2.6.22 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: nvidia-glx-new

Originally thought to be suffering from bug, https://bugs.launchpad.net/ubuntu/+s...e2/+bug/151544, i was doing some research for members of the forum and noticed that bug 151544 was actually more than on problem. In going about to help troubleshoot the problem, i ran into a new bug.

When installing the nvidia-glx-new drivers from the repository either using synaptic, apt-get, the restricted drivers applet, or installing the proprietary drivers form nvidia's website, gnome begins to hang after login. I installed the AMD64-Alternative image. I can reproduce this bug over and over, by installing and uninstalling the nvidia drivers.

Affects of the bug: When the drivers are installed, the GDM login manager will appear. After credentials are entered, it will start to load the desktop. Nothing will appear for between 20-40 seconds. Even after installing gnome-splashscreen-manager, and enabling it, nothing will view in this time frame. The desktop will turn to the background color, as defined in, /etc/gdm/PreSession/Default

There is no gnome-panel, no wallpaper, no splashscreen for gnome. dmesg and xsession-errors don't report any problems with the extended login times.

Revision history for this message
Mike Mackintosh (mike-mackintosh) wrote :

Creating a new user, logging out, logging back in, the problem still exists. Although using failsafe gnome, the problem is cured, so it seems as if the nvidia-glx-new package causes a problem with the session.

Revision history for this message
Gurubie (gurubie) wrote :

Could this need the dpi set in the xorg.conf?

Revision history for this message
Mike Mackintosh (mike-mackintosh) wrote :

I tried setting the dpi in xorg.conf, and the problem is still existent.

Revision history for this message
linux23d (linux23d) wrote :

I can confirm that the problem is possibly in relation to the Nvidia restricted drivers (nvidia-glx-new).

I had just finished installing Gutsy on the 7th Dec 2007 (yesterday), without using the Ubuntu restricted Nvidia driver. I used Envy to install the new Nvidia drivers, and the system was running fine (no slow login issues). Envy also creates its own packages called nvidia-glx-new and nviia-glx-new-dev.

Today (9th Dec 2007) linux-ubuntu-modules was updated. But before reboot, I had used envy to uninstall the Nvidia Driver. Envy removed nvidia-glx-new, nvidia-glx-dev, then (I Think) downloaded and installed libgl1-mesa-glx libgl1-mesa-dri and libgl1-mesa-dev. The only thing that remained was the kernel driver : - nvidia-kernel-common (20051028+1ubuntu7)

I used Envy to reinstall the Nvdia driver. Envy did not remove the libgl1-mesa-glx libgl1-mesa-dri and libgl1-mesa-dev packages.

I then rebooted and found myself with the slow gnome login problem.

I Must see what happens after I disable the restricted driver using the Restricted Driver Manager. Or just reboot after I uninstall the Nvidia driver (using Envy).

I'll report back.

Revision history for this message
linux23d (linux23d) wrote :

Tested both ideas, but still have the same problem.

Revision history for this message
Bryce Harrington (bryce) wrote :

Hi thedaywassaved,

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with the latest development release of Ubuntu? (ISOs are available from cdimage.ubuntu.com)

If it remains an issue, could you also attach a new /var/log/Xorg.0.log?
Thanks in advance.

The output of lspci -vvnn would also be worth having.

Changed in linux-restricted-modules-2.6.22:
status: New → Incomplete
Revision history for this message
Bryce Harrington (bryce) wrote :

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.

Changed in linux-restricted-modules-2.6.22:
status: Incomplete → Invalid
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.