No prompt for restart after driver install

Bug #272238 reported by plun
24
Affects Status Importance Assigned to Milestone
jockey (Ubuntu)
Fix Released
Undecided
Martin Pitt

Bug Description

Intrepid clean install, Alpha 6

nVidia driver install without any trouble, 177.70

To avoid confused users it must be better to prompt for a restart.

Also, if possible, make the Window larger... rather messy now.

Thanks ! :)

Related branches

Revision history for this message
Alberto Milone (albertomilone) wrote :

1) Do you use Ubuntu or Kubuntu? (Jockey has a GTK and a KDE ui.)
2) I'll work on the notification
3) Can you explain (in detail, maybe with a screenshot) what you by "making the window larger"?

Revision history for this message
nullack (nullack) wrote :

Moving status to confirmed as the developer has kindly agreed to work on notifying the user in making the user experience more intuitive.

Changed in jockey:
status: New → Confirmed
Revision history for this message
plun (plun) wrote :

1. Ubuntu-GTK

2. Thanks Alberto !

3. http://ubuntu-pics.de/bild/3446/jockey_WlYyT4.png

This is a challenge out of MMI design (man-machine interface)

Double text boxes with scrollbars.

Maybe just to reduce the amount of text above the first text box ?

A lot of PCs can run without proprietary drivers, maybe the text is somehow misleading.

I also think that its room for some discussion about this ;)

Revision history for this message
Markus Korn (thekorn) wrote :

This is also an issue in a live session, installing a restricted driver via jockey works like a charm, but it requires restarting of X. So there should be a hint like "please log out and log in again" instead of rebooting which does not make any sense in a live session ;)

Markus

Revision history for this message
Mario Limonciello (superm1) wrote :

Confirmed that this is still present in 0.5~alpha1-0ubuntu2 .

Revision history for this message
Alberto Milone (albertomilone) wrote :

This is fixed in revision 420-421 of my branch:
https://code.launchpad.net/~albertomilone/jockey/jockey-generic

Revision history for this message
Martin Pitt (pitti) wrote :

Thanks Alberto, merged to trunk, will upload to Intrepid soon.

Changed in jockey:
assignee: nobody → pitti
status: Confirmed → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package jockey - 0.5~alpha1-0ubuntu5

---------------
jockey (0.5~alpha1-0ubuntu5) intrepid; urgency=low

  * Merge bug fixes from trunk:
    - Fix XorgDriverHandler to not be "used" right after enabling.
    - Make sure that dri2 is not disabled for fglrx, it crashes amdcccle. (LP:
      #273320) [Alberto]
    - Use a "refresh" icon for drivers where a reboot needs to happen.
      (LP: #272238) [Alberto]
    - Fix KDE notification and the related test. Work around segfault when
      exiting the KDE UI. (LP: #270522) [Alberto]
    - search_driver(): Return list of installed files in addition to status
      code. Document the return value in README.txt. (LP: #269311)
    - Converts search_driver() printer device ID to friendly string (only
      supports printers for now). (part of LP #269454)
    - Do not make a backup of xorg.conf if the proprietary driver is already
      set there, so that we don't automatically revert to a configuration with
      the proprietary driver after uninstalling exactly that. [Alberto]

 -- Martin Pitt <email address hidden> Wed, 24 Sep 2008 22:40:22 +0200

Changed in jockey:
status: Fix Committed → Fix Released
Revision history for this message
plun (plun) wrote :

Well, I change status for this one because I didn't get any prompt, just
a little notification within the GUI.

Preferred is the same as with kernel installs.

After a little adventure with Nouveau I also wonder how Jockey triggers DKMS reset ?

The only way I found out is a kernel reinstall

Changed in jockey:
status: Fix Released → Incomplete
status: Incomplete → New
Revision history for this message
plun (plun) wrote :

Also got this after my little adventure with Nouveau

[ 60.085644] NVRM: API mismatch: the client has the version 177.80, but
[ 60.085648] NVRM: this kernel module has the version 177.76. Please
[ 60.085650] NVRM: make sure that this kernel module and all NVIDIA driver
[ 60.085651] NVRM: components have the same version.
[ 63.205642] NVRM: API mismatch: the client has the version 177.80, but
[ 63.205646] NVRM: this kernel module has the version 177.76. Please

[ 278.936478] NVRM: loading NVIDIA UNIX x86 Kernel Module 177.80 Wed Oct 1 14:38:10 PDT 2008
[ 358.173432] NVRM: loading NVIDIA UNIX x86 Kernel Module 177.80 Wed Oct 1 14:38:10 PDT 2008

So something is probably broken somewhere....

Revision history for this message
plun (plun) wrote :

plun@plun:~$ locate nvidia.ko

/lib/modules/2.6.27-3-generic/updates/dkms/nvidia.ko
/lib/modules/2.6.27-4-generic/kernel/drivers/video/nvidia/nvidia.ko
/lib/modules/2.6.27-4-generic/updates/dkms/nvidia.ko
/lib/modules/2.6.27-6-generic/updates/dkms/nvidia.ko
/lib/modules/last-good-boot/updates/dkms/nvidia.ko
/var/lib/dkms/nvidia/177.80/2.6.27-6-generic/i686/module/nvidia.ko
/var/lib/dkms/nvidia/177.80/build/.nvidia.ko.cmd
/var/lib/dkms/nvidia/177.80/build/nvidia.ko
/var/lib/dkms/nvidia/original_module/2.6.27-6-generic/i686/nvidia.ko

I must install the driver from nVidia for solving this....

Revision history for this message
Alberto Milone (albertomilone) wrote :

Please post the output of the following commands:
apt-cache policy nvidia-glx-177 nvidia-177-kernel-source
dkms status

Revision history for this message
Martin Pitt (pitti) wrote :

Right, it's not supposed to do the tray icon any more, just display the need to reboot in the jockey UI.

Changed in jockey:
status: New → Fix Released
Revision history for this message
plun (plun) wrote :

It must be much better with a tray-icon reboot signal...

----------------------------------------------------------------------------------

plun@plun:~$ apt-cache policy nvidia-glx-177 nvidia-177-kernel-source
nvidia-glx-177:
  Installed: 177.80-0ubuntu1
  Candidate: 177.80-0ubuntu1
  Version table:
 *** 177.80-0ubuntu1 0
        500 http://archive.ubuntu.com intrepid/restricted Packages
        100 /var/lib/dpkg/status
nvidia-177-kernel-source:
  Installed: 177.80-0ubuntu1
  Candidate: 177.80-0ubuntu1
  Version table:
 *** 177.80-0ubuntu1 0
        500 http://archive.ubuntu.com intrepid/restricted Packages
        100 /var/lib/dpkg/status
----------------------------------------------------------------------------------

plun@plun:~$ dkms status
nvidia, 177.80, 2.6.27-5-generic, i686: installed
nvidia, 177.80, 2.6.27-6-generic, i686: installed (original_module exists) (WARNING! Diff between built and installed module!)

------------------------------------------------------------------------------

ABI bump for kernel ?

DKMS trigg for Jockey.... ?

sudo apt-get install --reinstall linux-image-2.6.27-5-generic

Trigg OK....

Revision history for this message
plun (plun) wrote :

For avoiding work maybe this is important.

I enabled Nouveau with this wiki

http://nouveau.freedesktop.org/wiki/UbuntuPackages

Going back was a adventure.... ;)

Nevertheless its several threads within the forum with the same challenge and I dont think
all of the enabled Nouveau...

Something breaks Jockey and Jockey should be "master" over this...

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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