jockey-backend crashed with IOError: [Errno 19] No such device

[internautas]

Sorry about the error can not say anything more

ProblemType: Crash
Architecture: i386
DistroRelease: /usr/bin/lsb_release:81: DeprecationWarning: the sets module is deprecated import sets Ubuntu 9.04
ExecutablePath: /usr/share/jockey/jockey-backend
InterpreterPath: /usr/bin/python2.6
MachineType: K7VT4APro
NonfreeKernelModules: nvidia
Package: jockey-common 0.5-0ubuntu2
PackageArchitecture: all
ProcAttrCurrent: unconfined
ProcCmdLine: User Name=UUID=6e18820d-5fda-4873-a22e-91ef73549636 ro quiet splash
ProcCmdline: /usr/bin/python /usr/share/jockey/jockey-backend --debug -l /var/log/jockey.log
ProcEnviron:

ProcVersionSignature: Ubuntu 2.6.28-8.26-generic
PythonArgs: ['/usr/share/jockey/jockey-backend', '--debug', '-l', '/var/log/jockey.log']
SourcePackage: jockey
Title: jockey-backend crashed with IOError: [Errno 19] No such device
Traceback: IOError: [Errno 19] No such device
UserGroups:

[Shawn vega (svega85-gmail)]

Happened to me after installing nvidia restricted drivers

[Dave Jeffery (kecske-bak)]

As with Shawn, it happened to me after installing nvidia restricted drivers.

[Ken Weeks (1044ken)]

Happened to me after installing nvidia restricted drivers.
I am running 64 bit.

[ynamestnikov (ynamestnikov)]

The same bug on 64 bit platform

[Gabriel Thörnblad (gabriel-thornblad)]

Confirming. I'm also running 64-bit.

[Michel FRANKE (michel-franke)]

as Shawn vega
I am running 32bits

[scotty2 (granny6989)]

same- running 32 bit on AMD64, eVga nVidia video card, just added drivers and was about to restart.

[cacula (cacula)]

Confirming. I'm also running 64-bit.

[famous3warriors (famous3warriors)]

Same as Shawn happened after installing nvidia drivers. Nvidia drivers did not take after error. showed that they were installed but are not.

[Pete Stucke (pstucke)]

I'm running Ubuntu 9.04 (64-bit), and I received the error after upgrading the following packages today:

apport (0.143) to 0.144
apport-gtk (0.143) to 0.144
compiz-core (1:0.8.2-0ubuntu1) to 1:0.8.2-0ubuntu2
compiz-fusion-plugins-extra (0.7.9+git20090213-0ubuntu1) to 0.8.2-0ubuntu1
compiz-fusion-plugins-main (0.7.9+git20090213-0ubuntu2) to 0.8.2-0ubuntu1
compiz-plugins (1:0.8.2-0ubuntu1) to 1:0.8.2-0ubuntu2
compiz-wrapper (1:0.8.2-0ubuntu1) to 1:0.8.2-0ubuntu2
cups (1.3.9-14ubuntu2) to 1.3.9-15
cups-bsd (1.3.9-14ubuntu2) to 1.3.9-15
cups-client (1.3.9-14ubuntu2) to 1.3.9-15
cups-common (1.3.9-14ubuntu2) to 1.3.9-15
f-spot (0.5.0.3-1ubuntu2) to 0.5.0.3-1ubuntu4
gnome-applets (2.25.92-0ubuntu1) to 2.25.92-0ubuntu2
gnome-applets-data (2.25.92-0ubuntu1) to 2.25.92-0ubuntu2
gnome-applets-dbg (2.25.92-0ubuntu1) to 2.25.92-0ubuntu2
gnome-screensaver (2.24.0-0ubuntu4) to 2.24.0-0ubuntu5
gnome-settings-daemon (2.25.92-0ubuntu4) to 2.25.92-0ubuntu5
gvfs (1.1.7-0ubuntu1) to 1.1.8-0ubuntu1
gvfs-backends (1.1.7-0ubuntu1) to 1.1.8-0ubuntu1
gvfs-bin (1.1.7-0ubuntu1) to 1.1.8-0ubuntu1
gvfs-fuse (1.1.7-0ubuntu1) to 1.1.8-0ubuntu1
icedtea-6-jre-cacao (6b14-1.4.1-0ubuntu2) to 6b14-1.4.1-0ubuntu3
icedtea6-plugin (6b14-1.4.1-0ubuntu2) to 6b14-1.4.1-0ubuntu3
initramfs-tools (0.92bubuntu22) to 0.92bubuntu23
libavcodec-unstripped-52 (3:0.svn20090204-2ubuntu1+unstripped2) to 3:0.svn20090204-2ubuntu1+unstripped3
libavutil-unstripped-49 (3:0.svn20090204-2ubuntu1+unstripped2) to 3:0.svn20090204-2ubuntu1+unstripped3
libcups2 (1.3.9-14ubuntu2) to 1.3.9-15
libcupsimage2 (1.3.9-14ubuntu2) to 1.3.9-15
libdecoration0 (1:0.8.2-0ubuntu1) to 1:0.8.2-0ubuntu2
libdrm-intel1 (2.4.4-0ubuntu6) to 2.4.5-0ubuntu1
libdrm2 (2.4.4-0ubuntu6) to 2.4.5-0ubuntu1
libgalago1.0-cil (0.5.0-2.2) to 0.5.0-2.2ubuntu1
libgvfscommon0 (1.1.7-0ubuntu1) to 1.1.8-0ubuntu1
libpulse-browse0 (0.9.14-0ubuntu10) to 0.9.14-0ubuntu11
libpulse0 (0.9.14-0ubuntu10) to 0.9.14-0ubuntu11
libpulsecore9 (0.9.14-0ubuntu10) to 0.9.14-0ubuntu11
libpurple-bin (1:2.5.4-2ubuntu2) to 1:2.5.5-1ubuntu1
libpurple0 (1:2.5.4-2ubuntu2) to 1:2.5.5-1ubuntu1
libusplash0 (0.5.30) to 0.5.31
linux-firmware (1.9) to 1.10
module-init-tools (3.7~pre7-1) to 3.7~pre7-3
openjdk-6-jdk (6b14-1.4.1-0ubuntu2) to 6b14-1.4.1-0ubuntu3
openjdk-6-jre (6b14-1.4.1-0ubuntu2) to 6b14-1.4.1-0ubuntu3
openjdk-6-jre-headless (6b14-1.4.1-0ubuntu2) to 6b14-1.4.1-0ubuntu3
openjdk-6-jre-lib (6b14-1.4.1-0ubuntu2) to 6b14-1.4.1-0ubuntu3
pidgin (1:2.5.4-2ubuntu2) to 1:2.5.5-1ubuntu1
pidgin-data (1:2.5.4-2ubuntu2) to 1:2.5.5-1ubuntu1
pulseaudio (0.9.14-0ubuntu10) to 0.9.14-0ubuntu11
pulseaudio-esound-compat (0.9.14-0ubuntu10) to 0.9.14-0ubuntu11
pulseaudio-module-gconf (0.9.14-0ubuntu10) to 0.9.14-0ubuntu11
pulseaudio-module-hal (0.9.14-0ubuntu10) to 0.9.14-0ubuntu11
pulseaudio-module-x11 (0.9.14-0ubuntu10) to 0.9.14-0ubuntu11
pulseaudio-utils (0.9.14-0ubuntu10) to 0.9.14-0ubuntu11
python-apport (0.143) to 0.144
python-cupshelpers (1.1.3+git20090218-0ubuntu6) to 1.1.3+git20090218-0ubuntu7
python-problem-report (0.143) to 0.144
python3-minimal (3.0.1-0ubuntu2) to 3.0.1-0ubuntu3
sound-juicer (2.25.3-0ubuntu1) to 2.25.92-0ubuntu1
system-config-printer-common (1.1.3+git20...

[Steven Schnautz (sschnautz)]

Happened after installing NVIDIA 180 drivers on a 32 bit system.

[Robert D. Martin (ets3rodamar)]

I, too, had just activated the Nvidia 96.43.10 driver in anticipation of starting Baldur's Gate under PlayOnLinux. I think though that the error message first came after I mistakenly tried to start the game via clicking on the starter icon while yet having forgotten to first insert the Baldur's Gate DVD into the DVD drive.

I thus got the impression that the DVD not being in the drive had caused or provoked the error message.

Btw I had only just dist-upgraded beforehand. Thus this occurred under the ubuntu Linux on x86/x86_64,
linux-image-2.6.28-9.29-generic. Maybe I should have restarted ubuntu after activating the Nvidia driver before trying to start the game.

[cibbao (cibbao)]

Received installing 180 nvidia driver

Ho avuto questo problema installando i driver 180 nvidia

> Date: Wed, 11 Mar 2009 18:18:39 +0000
> From: <email address hidden>
> To: <email address hidden>
> Subject: [Bug 335567] Re: jockey-backend crashed with IOError: [Errno 19] No such device
>
> I, too, had just activated the Nvidia 96.43.10 driver in anticipation of
> starting Baldur's Gate under PlayOnLinux. I think though that the error
> message first came after I mistakenly tried to start the game via
> clicking on the starter icon while yet having forgotten to first insert
> the Baldur's Gate DVD into the DVD drive.
>
> I thus got the impression that the DVD not being in the drive had caused
> or provoked the error message.
>
> Btw I had only just dist-upgraded beforehand. Thus this occurred under the ubuntu Linux on x86/x86_64,
> linux-image-2.6.28-9.29-generic. Maybe I should have restarted ubuntu after activating the Nvidia driver before trying to start the game.
>
> --
> jockey-backend crashed with IOError: [Errno 19] No such device
> https://bugs.launchpad.net/bugs/335567
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “jockey” source package in Ubuntu: New
>
> Bug description:
> Sorry about the error can not say anything more
>
> ProblemType: Crash
> Architecture: i386
> DistroRelease: /usr/bin/lsb_release:81: DeprecationWarning: the sets module is deprecated import sets Ubuntu 9.04
> ExecutablePath: /usr/share/jockey/jockey-backend
> InterpreterPath: /usr/bin/python2.6
> MachineType: K7VT4APro
> NonfreeKernelModules: nvidia
> Package: jockey-common 0.5-0ubuntu2
> PackageArchitecture: all
> ProcAttrCurrent: unconfined
> ProcCmdLine: User Name=UUID=6e18820d-5fda-4873-a22e-91ef73549636 ro quiet splash
> ProcCmdline: /usr/bin/python /usr/share/jockey/jockey-backend --debug -l /var/log/jockey.log
> ProcEnviron:
>
> ProcVersionSignature: Ubuntu 2.6.28-8.26-generic
> PythonArgs: ['/usr/share/jockey/jockey-backend', '--debug', '-l', '/var/log/jockey.log']
> SourcePackage: jockey
> Title: jockey-backend crashed with IOError: [Errno 19] No such device
> Traceback: IOError: [Errno 19] No such device
> UserGroups:

_________________________________________________________________
Scopri le keyword più cercate della settimana!
http://clk.atdmt.com/GBL/go/136430524/direct/01/

[linuxuser600 (linuxuser600)]

Happened after installing 180 nvidia driver on 32bit

[Joe Archer (joe-archer-gmail)]

Same, happened after installing the Nvidia 180 driver on 32bit, now desktop effects will not enable, and window decoration fails on reboot.

[Martin Pitt (pitti)]

This started recently, need to try and reproduce.

[Åskar (olskar)]

Confirmed

[pothos (pothos)]

I got it away in 'repairing' packages by the easy grub-recoverymode-menu.
After a new kernel was installed (apt-get hadn't anything, just dpkg) and a new nvidia package configured,
nothing was selected in the hardware-driver menu. I manually activated nvidia 180 and after a reboot, this problem and glxinfo or compiz problems were gone.

[inbetween (inbetween)]

thanks

met vriendelijke groet

albert

http://www.inbetween-computers.nl
**********************************************************************************************
ATTENTIE

Dit emailbericht is vertrouwelijk en mogelijk ook persoonlijk. Mocht u dit bericht bij vergissing ontvangen hebben dan wordt u verzocht de afzender hierover te informeren en het bericht te verwijderen. Tevens wordt u bij deze in kennis gesteld dat iedere openbaarmaking, verveelvoudiging, verspreiding dan wel gebruik van het bericht ten strengste verboden is. Wij nemen aan, maar staan daarvoor niet in, dat dit bericht en eventuele bijlagen, vriusvrij zijn. U blijft zelf verantwoordelijk voor het controleren van het bericht/bijlagen op mogelijke virussen.
**********************************************************************************************
This e-mail is confidential and may also be privileged. It is intended for use by the addressee only. If you are not the intended addressee, we request that you notify us immediately and delete this e-mail, and any attachment(s), without copying, forwarding, disclosing or using it any other way. Inbetween computers will not be liable for damage relating to the communication by e-mail of data or documents. Inbetween computers has its seat at Meppen, The Netherlands and is registered in the Commercial Register in Meppel under number 04044737.
**********************************************************************************************
Vrijwaring/Disclaimer
De gegevens in dit elektronisch document en de eventuele bijlagen zijn uitsluitend bedoeld voor de geadresseerde(n). De informatie wordt zorgvuldig samengesteld. Inbetween kan echter niet garanderen dat de informatie absoluut juist, volledig en tijdig overkomt via het Internet. Voor belangrijke beslissingen aangaande de verstrekte informatie dient u een en ander persoonlijk bij betreffende te controleren.

pothos schreef:
> I got it away in 'repairing' packages by the easy grub-recoverymode-menu.
> After a new kernel was installed (apt-get hadn't anything, just dpkg) and a new nvidia package configured,
> nothing was selected in the hardware-driver menu. I manually activated nvidia 180 and after a reboot, this problem and glxinfo or compiz problems were gone.
>
>

[Martin Pitt (pitti)]

I tried to reproduce this, but it seems this only happens on a real nvidia card.

If this happens for you, can you please do the following:

 - ensure that the nvidia driver is not installed, and jockey is not opened; best is probably to do that from a fresh install, but if you can reproduce it again after uninstalling the driver, that's fine

  - sudo killall jockey-backend # if that fails with "no such process", that's okay

  - start jockey, confirm that nvidia is displayed as available, but don't do anything yet

  - determine the PID of jockey-backend:

    ps aux|grep jockey-backend|grep -v grep |awk '{print $2}'

  - sudo strace -f -v -s 1024 -o /tmp/jockey.trace -p 12345

     Replace 12345 with the pid you determined in the previous step

  - enable nvidia in jockey

  - confirm that it crashes

  - go back to the terminal with the strace, press Control-C, and attach /tmp/jockey.trace here.

Thank you!

[Ynot (tatkinson321)]

Jockey trace attached

Jaunty alpha 6 (amd64)
Nvidia 7600 GT

[Eylem (eylemkoca)]

This happened right after installing nvidia proprietary drivers. 64 bits jaunty alpha 6. Video card is GTX 260.

[Eylem (eylemkoca)]

Update: After restart, the drivers were installed and I was able to enable all desktop effects.

[JRLROCKS (email-jasonlambert)]

32bit just installed Nvidia driver on Go 7600 - laptop

[mvavrek (mattvavrek)]

Confirmed with Jaunty Alpha 6 on Dell XPS M1210 (Nvidia GeForce Go 7400) laptop

[Martin Pitt (pitti)]

Ynot, thanks. However, it seems you didn't actually get the "IOError 19" crash while you ran strace? So I'm afraid this won't help me to track down the problem.

[phook (phookyll)]

Confirmed with Jaunty Alpha 6, 64bit. Happened while or just after installing Nvidia 180 propriety drivers.

[Liam O'Reilly (aliam13-2)]

I can also confirm with Jaunty Alpha 6, 64bit. Happened while or just after installing Nvidia 180 propriety drivers. Also after these drivers are installed the "Display" application states "It apears that your graphic driver does not support the necessary extensions to use this tool. Do you want to use your graphics driver vendor's tool instead? [No][Yes]". If I choose no then the drop down box with the resolutions is missing many resolutions for my graphic card / monitor setup including the optimal 1280x1024 (I think this is the optimal - cant quite remember). The best in the list is 640x480.

This work perfectly for me in Intrepid. This is a very big problem for me and will prevent me from upgrading to Jaunty if it is not resolved.

[Eylem (eylemkoca)]

About the Display settings offering to use Nvidia's tool, I think it is how it's intended to be. Meaning, you're supposed to say "Yes". Just like in M$ Windows, Nvidia settings tool takes over the control. What needs to be done possibly though is to make this more clear and and smooth, without a warning that might scare many users away from saying "Yes". Not a show stopper but hey "Ubuntu just works", right?

[Liam O'Reilly (aliam13-2)]

Dear Eylem, if you are correct and I am now supposed to use the Nivida application to configure things then the dialog box definitely needs to communicate a message that does not suggest something is wrong. I have a few questions and points though. 1) Can the Nividia GUI configure rotation and duel head as easily as the normal GUI (I prefer using xrandr - but normal people will not). 2) I believe the normal GUI is much easier to use than the Nvidia one, and most people will not want that many options (don't take it away - I just think they would prefer the normal GUI as it is less complex)

Somehow jockey worked the last time I tried it and now my graphics are working ok. Although my sound is very buggy (filing bugs now). The previous alpha worked well, this one does not.

[Liam O'Reilly (aliam13-2)]

I think there is somehting broken. The Nvidia's settings application displays my monitor (SyncMaster 913N) correctly, while the normal gnome application does not. I am unstable in the gnome application to rotate my screen. Thus options are missing and the monitor was not detected correctly. I should still be able to use the gnome application even if the Nvidia application allows me to configure more.

[Richard Craig (rchrdcrg)]

Just commenting that this crash apparently occurred after a successful install of the proprietary Nvidia drivers through the restricted modules application. Everything went smoothly, and the crash came up after I hit the "close" button... had the crash report not popped up, I wouldn't have even known anything went wrong.

[sadicote (mzsade)]

Same here Richard. I also did gksudo nvidia-xconfig to check if the driver was actually installed, Nvidia was clearly listed under 'System Device', and though i am glad that nothing actually 'crashed'--isn't everything supposed to go blank when a system crashes? I think i can live with these pseudo crashes.

[Per-Inge (per-inge-hallin)]

Yes the Nvidia driver was installed OK and I, as written below,
shouldn't have noticed anything in case the crash message hadn't popped
up.

On lör, 2009-03-14 at 23:40 +0000, Richard Craig wrote:

> Just commenting that this crash apparently occurred after a successful
> install of the proprietary Nvidia drivers through the restricted modules
> application. Everything went smoothly, and the crash came up after I
> hit the "close" button... had the crash report not popped up, I wouldn't
> have even known anything went wrong.
>

[denzilla74 (denzilla74-deactivatedaccount)]

Happened too me after enabling nvidia drivers for Ti4600. Driver are functioning after reboot though.

[Sokolov Sergey (cleversokol-deactivatedaccount)]

Confirm, amd64.

Videocard: NVidia 8600GS
Videodriver, I was installing: 180 (180.35 as I understand)

[Martin Pitt (pitti)]

Ah, I got ssh access to an nvidia machine and debugged it there. Committed fix to trunk now.

[luk1don (luk1don)]

The fresh new system and this error...

[Launchpad Janitor (janitor)]

This bug was fixed in the package jockey - 0.5-0ubuntu4

---------------
jockey (0.5-0ubuntu4) jaunty; urgency=low

  * Merge bug fixes from trunk:
    - Fix KDE autostart file.
    - handlers.py: Fix crash if closing /sys file during rebind fails
      (LP: #335567)
    - nvidia.py: Do not attempt to rebind driver, it's doomed to fail anyway.
  * nvidia.py: Remove -libvdpau for driver >= 180, and nvidia-settings, when
    removing the driver.

 -- Martin Pitt <email address hidden> Mon, 16 Mar 2009 19:26:56 +0100

[Per-Inge (per-inge-hallin)]

In my case AMD Athlone 5000+
Videocard Geforce 8600GTS
Installing videodriver 180.37

However the driver was installed OK, so no other impact but the crash
message.

mån 2009-03-16 klockan 15:54 +0000 skrev sokolovss:

> Confirm, amd64.
>
> Videocard: NVidia 8600GS
> Videodriver, I was installing: 180 (180.35 as I understand)
>

[Brady Merriweather (brady-merriweather)]

Same here. After the install of the driver, it hasn't misbehaved since. I'm
not seeing any performance issues.

On Mar 16, 2009 3:19pm, Per-Inge <email address hidden> wrote:
> In my case AMD Athlone 5000+

> Videocard Geforce 8600GTS

> Installing videodriver 180.37

> However the driver was installed OK, so no other impact but the crash

> message.

> mån 2009-03-16 klockan 15:54 +0000 skrev sokolovss:

> > Confirm, amd64.

> >

> > Videocard: NVidia 8600GS

> > Videodriver, I was installing: 180 (180.35 as I understand)

> >

> --

> jockey-backend crashed with IOError: [Errno 19] No such device

> https://bugs.launchpad.net/bugs/335567

> You received this bug notification because you are a direct subscriber

> of the bug.