jockey backend crashed when trying to install nvidia driver

Bug #350776 reported by Renjoy
82
This bug affects 11 people
Affects Status Importance Assigned to Milestone
jockey (Ubuntu)
Invalid
Undecided
Paulo da Rocha
Nominated for Jaunty by Robben
Nominated for Karmic by Robben

Bug Description

Binary package hint: jockey-common

While installing nvidia propritery drivers (180) in Jaunty Kubuntu Beta, jockey backend crashed with following error : Sorry, the Jockey backend crashed. Please file a bug at: ubuntu-bug jockey-common Trying to recover by restarting backend. Unable to perform update after this.

Revision history for this message
M.Letcher (m-letcher) wrote :

I also am seeing this crash and it left a lock on a cache dir that disabled updates until restarted.
This may or may not be related to a an issue I've reported with the the glx-180 trying to install for an 8800 GT at the following link.

https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-180/+bug/352485Tht

The attachment is an additional error display in addition to the one reported above which I also got.

Revision history for this message
M.Letcher (m-letcher) wrote :

Correction to link above which fails. The bug # is OK, so should be searchable if this link has problems.

https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-180/+bug/352485

Revision history for this message
Scott Miller (logopedist) wrote :

I've had the same problem using Jaunty Ubuntu Beta (not Kubuntu):

When it asks me to report the error automatically and I comply, it then generates the following error message:

"The problem cannot be reported:

You have some obsolete package versions installed. Please upgrade the following packages and check if the problem still occurs:

jockey-gtk, whiptail, consolekit, libssl0.9.8, python, jockey-common, libidl0, synaptic, python-apt, debconf, adduser, python2.6, python-minimal, python2.6-minimal, libck-connector0, libcups2, libpango1.0-common, debconf-i18n, libnewt0.52, x11-common, libvte9, libvte-common, python-central, cpp, libpango1.0-0"

I'm not a hacker, so upgrading all those packages manually is more than I can handle, and I don't know if it would solve the problem. It may be worth noting that after the correct driver has been identified for download, and I ask it to proceed, it never gets past 0% downloaded. It seems to hang up at that point.

Revision history for this message
Jan Prikryl (jan-prikryl) wrote :

The same problem here with Jaunty Ubuntu Beta. The first attempt to activate the proprietary driver resulted in a crash, the second try insalled the driver without any problems.

Revision history for this message
Alex (alexanderlane) wrote :

Empty "download" progress bar hangs for awhile when enabling proprietary nvidia driver (180) via menus System -> Administration -> Hardware Drivers. Eventually, it crashes, and a small window appears with the following message:

     Please file a bug at:
     ubuntu-bug jockey-common.

Revision history for this message
RnSC (webclark) wrote :

Same problem, but I can provide more detail.
New (Clean) install, first boot, first logon, first action on desktop.
Appearance Preferences was installed as "None".
System / Preferences / Appearance / Visual Effects
Select "Extra".
Searches and says that it must download a proprietary driver.
NVidia GeForce FX 5200
This same *identical* hardware setup is running 0810, and the same Visual effect setting, driver download, etc. took place flawlessly.

The driver download progress "Thermometer" sat at 0% for a long time, perhaps 10 minutes or more.

A dialog stating "Sorry, the jockey backend crashed. Please file a bug at ubuntu-bug jockey-common. Trying to recover by restarting backend." appears.

After another perhaps 10 minutes, I rebooted. There was never any apparent progress, and the "Appearance Preferences" box remained unresponsive until boot (It was blank, needed to be repainted since I had moved it).

After reboot, the desktop was in "Visual Effects" = "Normal" mode. I clicked on "Extra", and it searched for the driver, found it, and changed modes. The windows wiggled quite nicely when you move them, and it was selected in the Appearance Preferences dialog. I can set it back to "None", and back to "Extra" etc, and it works fine.

Attached is a file containing (1) The /var/log/messages for the first boot and the failure. Nothing interesting, and (2) The /var/log/jockey.log covering the first boot through failure and restart. Lots of problems are reported.

Hope this helps!

Revision history for this message
RnSC (webclark) wrote :

RnSC Post a minute ago...
I neglected to say that this occurred on the just-released 0904 desktop, Thursday, April 23.

Revision history for this message
Blake W (blake-weyman) wrote :

This also affects me, on a fresh install of Ubuntu 9.04 i386. The nvidia download progress bar in "Hardware Drivers" has always been very sluggish, in every ubuntu version i've tried.

Revision history for this message
pranith (bobby-prani) wrote :

I confirm this bug affects me. I am using Kubuntu 9.04 x86_64 installed today. Can provide more info if needed

pranith (bobby-prani)
Changed in jockey (Ubuntu):
status: New → Confirmed
Revision history for this message
Scott Miller (logopedist) wrote :

I meant to specify that I was using 64 bit version of Ubuntu. Obviously, I'm not sure if it matters, but I meant to report the version I was using in case it turns out to be specific to the 64 bit version.

Revision history for this message
MockY (mocky) wrote :

Like Alex mentioned before:
"
Empty "download" progress bar hangs for awhile when enabling proprietary nvidia driver (180) via menus System -> Administration -> Hardware Drivers. Eventually, it crashes, and a small window appears with the following message:

     Please file a bug at:
     ubuntu-bug jockey-common.
"

I am experiencing exactly the same behaviour. And that not just on only one machine. I have installed Jaunty final on 4 machines now, all with Nvidia graphic cards, and the exact same behaviour occurs. In all cases, when I restart the computer, the driver is indeed enabled. I just wonder what may happen down the road in terms of stability....

Revision history for this message
crashcookie (crashcookie) wrote :

had exactly the same issue Alex and MockY have

Revision history for this message
Tom Wolf (tjwolf) wrote :

I have the same issue on a fresh install of the official 9.04 release. It came about when I tried to activate he NVidia driver via System->Administration->Device Drivers.

And, as with another poster, before installing 9.04, I had Ubuntu 8.10 installed and the nvidia drives were working fine on that release.

In general, this release seems to have a lot of trouble with the restricted device drivers: initially after installing 9.04, the Device Drivers screen didn't even show ANY restricted device drivers. Only after a couple hours of trying and then changing Software Sources from "Main Server" to a specific mirror and then doing an update check did the drivers show up :-(

Revision history for this message
Blake W (blake-weyman) wrote :

mine never enabled the drivers after it crashed. but i did figure out a workaround for those who can't stand errors:

* Install "nvidia-glx-180" (or your preferred driver version, replacing "180" with the version number), using your preferred package manager.

* Reboot and it'll be activated. However, "Hardware Drivers" doesn't think it's the same thing as the one it mentions, so for the sake of completeness, open Hardware Drivers, and select the driver you just installed, and click "Activate". It'll want you to reboot, do so, and all will be well (assuming that your card works with that driver, I've heard a few stories about new-ish nvidia cards not working at all with the newest nvidia driver).

Revision history for this message
Tom Wolf (tjwolf) wrote :

I just perused through the installation forums for possible help and noticed that one guy didn't get the above error when he inserted the installation CD prior to trying to activate the driver. I tried that and it worked! The Driver screen let me activate the NVidia driver.

Hope this helps others as a workaround. Definitely a bug though - in 8.10 I never had to insert a disk! (Actually, in 8.10 I don't recall it going out on the internet to retrieve the list of restricted drivers either - I guess it was all done as part of the initial installation then?)

tom

Revision history for this message
Blake W (blake-weyman) wrote :

I think that what's happened there is that the cd contains the drivers, and ubuntu saw no reason to grab it from the internet... and presumably asked to insert the cd, and then jockey timed out because it was waiting for user intervention that was impossible to give?

Revision history for this message
Neverbots (neverboterere) wrote :

I am still stuck with the same problem after a new install of the official 9.04 release. Have tried all the suggestions above and nothing seems to work for me. I had it working though in with the better version but then I had just upgraded from 8.10 so assume it just picked the settings from the previous installation. What annoys me though is the fact that this problem has been reported way back but there is still no fix in the final release

Revision history for this message
Vinod (vinodkutty) wrote :

I encountered the same problem in 9.04 after trying to change Appearance settings. Hardware is nVidia 160m in Dell E6500. I've always hated nVidia's stance on open source; this just brings back bad memories.

I noticed this in my pstree:

     ├─jockey-backend─┬─cdrom───mount
     │ └─{jockey-backend}

and top showed:

  PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
 3885 root 20 0 16664 1740 1452 R 24 0.0 8:55.71 cdrom
 3790 root 20 0 180m 70m 16m S 14 0.9 4:43.00 jockey-backend
 2529 messageb 20 0 22064 1792 808 S 6 0.0 2:42.00 dbus-daemon

So I disabled 'local cdrom' in my Synaptic settings and retried. At first it didn't work, but then I realized the above 'cdrom' process was still running. So I killed it, and this time it seems to work (at least it downloads and installed). I'm about to reboot and confirm.

Revision history for this message
Vinod (vinodkutty) wrote :

Follow up to my above comment: Disabling the local cdrom repository in my Synaptic settings seems to have worked around this problem.

To summarize:
-- go to System->Administration->Synaptic Package Manager->Settings->Repositories and uncheck the "cdrom with Ubuntu 9.04 'Jaunty Jackalope' checkbox.
-- killed 'cdrom' process that was hung above
-- Run System->Preferences->Appearance->Visual Effects to use "Extra" and trigger the driver search. Waited for a few minutes; saw some activity in 'top'
-- rebooted after it was done

After reboot, nVidia driver works, and I can change my Appearance -> Visual Effects settings.

I did notice my wireless connection (wlan0; Intel PRO/Wireless 5300 AGN [Shiloh] using 'iwlagn' driver ) had trouble right after I did this, and I had to disable and re-enable it in Network Manager before it finally reconnected. Not sure if this is related, but that's what I observed.

Revision history for this message
Casper Bang (casper-bang) wrote :

I have exactly the same problem with installing Propriatary drivers + a nasty side effect. My screen goes into power save after about 10 min. of running Ubuntu 9.04. I assume this is a ACPI issue of some kind, was hoping to fix it with Nvidia's binary driver... but ran into the problem mentioned in this thread. :(

Revision history for this message
AJenbo (ajenbo) wrote :

Same problem here, changing the software source to http://ftp.klid.dk/ftp/ubuntu instead of "Server for denmark" fixed the issue. (i have a danish install of ubuntu 9.04)

Revision history for this message
beetlejuicer (crand275) wrote :

Same problem over here.

Running nVidia GeForce 9300 on an ASUS X83Vb.

Ubuntu 9.04 x64

I upgraded from 8.10 -> 9.04 and the driver installed but my X server kept crashing over & over.

I installed 9.04 fresh and got the jockey backend crash described here.

I'm going back to 8.10.

Revision history for this message
Ashley (revdice) wrote :

Workaround?
Ok I had the same exact problem here on a fresh 9.04 64bit install running on a p4 quad with a geforce 8800 GT. I went to the Synaptic Package Manager, found the nVidia 180 driver package, marked it for install, applied.... No errors at all in the console. Restarted and X loaded fine, Gnome has all of its shiney effects enabled, the graphics are great. So far so good. No errors, no corruption, no weird behavior at all. :)

Paulo da Rocha (pcdopc)
Changed in jockey (Ubuntu):
assignee: nobody → Paulo da Rocha (pcdopc)
Revision history for this message
Jay Herrick (jay-herrickweb) wrote :

I can confirm that un-checking the CD-ROM in Software Sources allowed the drivers to install through the Hardware Drivers interface.

Revision history for this message
Paulo da Rocha (pcdopc) wrote : Re: [Bug 350776] Re: jockey backend crashed when trying to install nvidia driver

I tried one more time after send this bug report and apparently the jockey
crash again
but when i would try again the driver status has changed to active! o/

Now, my pc, is soooo much better than before but I still can't change to
extra effects. =/

[]'s

2009/5/9 Jay Herrick <email address hidden>

> I can confirm that un-checking the CD-ROM in Software Sources allowed
> the drivers to install through the Hardware Drivers interface.
>
> --
> jockey backend crashed when trying to install nvidia driver
> https://bugs.launchpad.net/bugs/350776
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “jockey” source package in Ubuntu: Confirmed
>
> Bug description:
> Binary package hint: jockey-common
>
> While installing nvidia propritery drivers (180) in Jaunty Kubuntu Beta,
> jockey backend crashed with following error : Sorry, the Jockey backend
> crashed. Please file a bug at: ubuntu-bug jockey-common Trying to recover by
> restarting backend. Unable to perform update after this.
>

--
E é como sempre dizem:
Ogden Nash <http://www.brainyquote.com/quotes/authors/o/ogden_nash.html> -
"The trouble with a kitten is that when it grows up, it's always a cat."

Revision history for this message
M.Letcher (m-letcher) wrote :

Ok, another weekend, another try, and still no joy. I disabled the CD option in the update manager. At least Jockey didn't crash this time. However, the only option in hardware drivers this time was for nv - which appeared to default to nv-173. Jockey looked for drivers but didn't even offer options for 173 much less 180. Attempting to enable effects failed after a search for drivers. So, once again I manually removed nv-180-glx, re-installed it and experienced the failure of X to start. Again, /dev/nvidia0 isn't recognized and so the 8800-GT card at PCI-1:0.0 fails to get initialized and X fails. Back to Vista, again. I'm sooo disappointed that this is taking more than 4 months to resolve as its just getting a graphics driver installed.
Any suggestions or help is greatly appreaciated.
I've been trying to get my nieces interested in Ubuntu but this is giving me caution in suggesting it to them. They're busy enough already and lack my patience.

Revision history for this message
Paulo da Rocha (pcdopc) wrote :

Update: Only 180 is working. 173 FAIL!

2009/5/9 M.Letcher <m.letcher@q.com>

> Ok, another weekend, another try, and still no joy. I disabled the CD
> option in the update manager. At least Jockey didn't crash this time.
> However, the only option in hardware drivers this time was for nv - which
> appeared to default to nv-173. Jockey looked for drivers but didn't even
> offer options for 173 much less 180. Attempting to enable effects failed
> after a search for drivers. So, once again I manually removed nv-180-glx,
> re-installed it and experienced the failure of X to start. Again,
> /dev/nvidia0 isn't recognized and so the 8800-GT card at PCI-1:0.0 fails to
> get initialized and X fails. Back to Vista, again. I'm sooo disappointed
> that this is taking more than 4 months to resolve as its just getting a
> graphics driver installed.
> Any suggestions or help is greatly appreaciated.
> I've been trying to get my nieces interested in Ubuntu but this is giving
> me caution in suggesting it to them. They're busy enough already and lack my
> patience.
>
> --
> jockey backend crashed when trying to install nvidia driver
> https://bugs.launchpad.net/bugs/350776
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “jockey” source package in Ubuntu: Confirmed
>
> Bug description:
> Binary package hint: jockey-common
>
> While installing nvidia propritery drivers (180) in Jaunty Kubuntu Beta,
> jockey backend crashed with following error : Sorry, the Jockey backend
> crashed. Please file a bug at: ubuntu-bug jockey-common Trying to recover by
> restarting backend. Unable to perform update after this.
>

--
E é como sempre dizem:
Charles Kuralt<http://www.brainyquote.com/quotes/authors/c/charles_kuralt.html>
- "You can find your way across this country using burger joints the
way a
navigator uses stars."

Revision history for this message
Paulo da Rocha (pcdopc) wrote :

Update 2: I tried one more time AND 173 works AND extra effects too!

Obs. : I didn't try anything new I just do the same thing I tried before. o/

2009/5/9 Paulo César <email address hidden>

> Update: Only 180 is working. 173 FAIL!
>
> 2009/5/9 M.Letcher <m.letcher@q.com>
>
> Ok, another weekend, another try, and still no joy. I disabled the CD
>> option in the update manager. At least Jockey didn't crash this time.
>> However, the only option in hardware drivers this time was for nv - which
>> appeared to default to nv-173. Jockey looked for drivers but didn't even
>> offer options for 173 much less 180. Attempting to enable effects failed
>> after a search for drivers. So, once again I manually removed nv-180-glx,
>> re-installed it and experienced the failure of X to start. Again,
>> /dev/nvidia0 isn't recognized and so the 8800-GT card at PCI-1:0.0 fails to
>> get initialized and X fails. Back to Vista, again. I'm sooo disappointed
>> that this is taking more than 4 months to resolve as its just getting a
>> graphics driver installed.
>> Any suggestions or help is greatly appreaciated.
>> I've been trying to get my nieces interested in Ubuntu but this is giving
>> me caution in suggesting it to them. They're busy enough already and lack my
>> patience.
>>
>> --
>> jockey backend crashed when trying to install nvidia driver
>> https://bugs.launchpad.net/bugs/350776
>> You received this bug notification because you are a direct subscriber
>> of the bug.
>>
>> Status in “jockey” source package in Ubuntu: Confirmed
>>
>> Bug description:
>> Binary package hint: jockey-common
>>
>> While installing nvidia propritery drivers (180) in Jaunty Kubuntu Beta,
>> jockey backend crashed with following error : Sorry, the Jockey backend
>> crashed. Please file a bug at: ubuntu-bug jockey-common Trying to recover by
>> restarting backend. Unable to perform update after this.
>>
>
>
>
> --
> E é como sempre dizem:
> Charles Kuralt<http://www.brainyquote.com/quotes/authors/c/charles_kuralt.html> - "You can find your way across this country using burger joints the way a
> navigator uses stars."

--
E é como sempre dizem:
Vince Lombardi<http://www.brainyquote.com/quotes/authors/v/vince_lombardi.html>
- "We didn't lose the game; we just ran out of time."

Revision history for this message
Ahmad deaN (ruffey1910) wrote :

Guys, I've got the same problem with you, jockey backend crashed...my solution is, i update as much as i could with update manager, and finally all got fixed. oh, by the way, i've used the 180 driver...

hope this helps...

Revision history for this message
fig_wright (fig-wright) wrote :

I also had this problem and fixed it by unchecking the install cd in sources.

Revision history for this message
beach_defender (barry-hpfm) wrote :

Hi,
I have the same issue with the on-board nvidia graphics on my PC. I have not been able to resolve it so I bought a Radeon HD4350 pci express card. With this one I can at leaqst boot up and I get high quality graphics (with no extra drivers installed) BUT the screen goes black every few minutes or when you change window/applications.

I tried to install the ATI drivers, but I get the same jockey-common background process error.

Has this been resolved yet?

Revision history for this message
Matt Goodfellow (thatdamncanadian) wrote :

Same issue with Hardware Drivers app on 9.04. Doesn't seem to be related to the driver as same problem occured for the Broadcom B43 driver as well. Above work-around (disable CD as source) fixed problem.

Revision history for this message
Renjoy (renjoy) wrote :

Thank you.

On Thu, Oct 29, 2009 at 2:34 AM, Matt Goodfellow <
<email address hidden>> wrote:

> Same issue with Hardware Drivers app on 9.04. Doesn't seem to be
> related to the driver as same problem occured for the Broadcom B43
> driver as well. Above work-around (disable CD as source) fixed problem.
>
> --
> jockey backend crashed when trying to install nvidia driver
> https://bugs.launchpad.net/bugs/350776
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Regards

Renjoy Henry

Revision history for this message
Neverbots (neverboterere) wrote : Re: New Address

Thank you for emailing <email address hidden>
Please note that this email address has changed to <email address hidden>
Your email has been forwarded, but please take note for future reference and update your contacts list.
Kind regards
bsat.co.za Admin

Revision history for this message
dino99 (9d9) wrote :
Changed in jockey (Ubuntu):
status: Confirmed → 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.