update 8.10 to 9.04 ==> Pb with udevinfo (not found)

[zarakoff]

Binary package hint: update-manager

In script update-initramfs, cpio command don't found ./udevinfo
dpkg --configure -a give the same error
Update cancelled, impossible to restart in previous configuration

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/update-manager
InterpreterPath: /usr/bin/python2.6
NonfreeKernelModules: nvidia
Package: update-manager 1:0.111.0
PackageArchitecture: all
ProcAttrCurrent: unconfined
ProcCmdline: /usr/bin/python2.6 /usr/bin/update-manager -dc
ProcEnviron:
 SHELL=/bin/bash
 LANG=fr_FR.UTF-8
 LANGUAGE=fr_FR:fr:en_GB:en
PythonArgs: ['/usr/bin/update-manager', '-dc']
SourcePackage: update-manager

Uname: Linux 2.6.27-14-generic i686
UserGroups: lpadmin

[Michael Vogt (mvo)]

Thanks for your bugreport.

Please attach the files in /var/log/dist-upgrade/* from the failed install

[seba (5-admin-starepro-info)]

I have this same issue.

I'm paste my logs.

[Patrik Nilsson (nipatriknilsson)]

I had no crash during the update of 8.10 to 9.04, but udevinfo is not found on the system after the update:

patrik@ubuntu:~$ udevinfo -a -p $(udevinfo -q path -n /dev/sdb1)
bash: udevinfo: command not found
bash: udevinfo: command not found
patrik@ubuntu:~$

The above command worked in 8.10.

patrik@ubuntu:~$ sudo find / -name *udevinfo*
[sudo] password for patrik:
patrik@ubuntu:~$

No hits.

[tuxedo0801 (alex-root1-deactivatedaccount)]

Same on my machine. Had no issues with updating 8.10 to 9.04. But an application which needs udevinfo to identify hard-disks and so on is no more running, because udevinfo is missing.

Is there a workaround known?!

[richie (kokauh)]

Same on my machine.
Trying to configure madfuload 1.2.
_______________

checking for udev version... configure: line 2811: udevinfo: command not found
none
configure: error: udev version 057 or later is required
_______________

Newly installed 9.04 amd64 release. No dist. upgrades.
Works in 8.10 i386.

[rc3 (midnightcodr)]

Try udevadm instead. For example:
  udevadm info -q path -n /dev/video0
will probe information about the USB webcam I just plug in. I haven't tested the new command options yet but basically you can substitute udeinfo with udevadm info.

[Patrik Nilsson (nipatriknilsson)]

I also did a fresh install on a new computer. udevinfo is not found on this new machine. It was the first thing I tested after install. No packages were installed or deinstallled before this.

Ubuntu 9.04 was installed with the alternate cd. My ubuntu 8.10 computer was also installed using the alternate cd, which after upgrade to 9.04 was missing the udevinfo command.

[rc3 (midnightcodr)]

Sorry about the example I listed earlier, that command will only show the full path for the video0 device, to get all information, use
    udevadm info -a -p $(udevadm info -q path -n/dev/video0)

To get information about /dev/sda1
    udevadm info -a -p $(udevadm info -q path -n/dev/sda1)

Another not-too-complicated example:
    udevadm info -a -p /sys/class/net/eth0

To see more examples, here's a good one:
    http://reactivated.net/writing_udev_rules.html
It also teaches you how to write udev rules.

[rc3 (midnightcodr)]

Run or add the follow line to your .bashrc might be a workaround for those who have written scripts using the old udevinfo command
    alias udevinfo='udevadm info'

[NKJensen (nkj)]

alias udevinfo='udevadm info' did not solve my problem.

I still get the cpio error:

nkj@nkj-laptop:~$ sudo dpkg --configure -a
Setting up initramfs-tools (0.92bubuntu29) ...
update-initramfs: deferring update (trigger activated)

Setting up linux-image-2.6.28-13-generic (2.6.28-13.44) ...
Running depmod.
update-initramfs: Generating /boot/initrd.img-2.6.28-13-generic
cpio: ./bin/udevinfo: Cannot stat: No such file or directory
update-initramfs: failed for /boot/initrd.img-2.6.28-13-generic
Failed to create initrd image.
dpkg: error processing linux-image-2.6.28-13-generic (--configure):
 subprocess post-installation script returned error exit status 2
dpkg: dependency problems prevent configuration of linux-image-generic:
 linux-image-generic depends on linux-image-2.6.28-13-generic; however:
  Package linux-image-2.6.28-13-generic is not configured yet.
dpkg: error processing linux-image-generic (--configure):
 dependency problems - leaving unconfigured
Processing triggers for initramfs-tools ...
update-initramfs: Generating /boot/initrd.img-2.6.27-14-generic
cpio: ./bin/udevinfo: Cannot stat: No such file or directory
update-initramfs: failed for /boot/initrd.img-2.6.27-14-generic
dpkg: subprocess post-installation script returned error exit status 1
nkj@nkj-laptop:~$

[rc3 (midnightcodr)]

How about creating this file
*/bin/udevinfo*
with the following lines in it:
#!/bin/bash
udevadm info $@

Make it executable:
*chmod +x /bin/udevinfo*

Then try your command again.

On Tue, Jun 9, 2009 at 3:46 PM, NKJensen <email address hidden> wrote:

> alias udevinfo='udevadm info' did not solve my problem.
>
> I still get the cpio error:
>
> nkj@nkj-laptop:~$ sudo dpkg --configure -a
> Setting up initramfs-tools (0.92bubuntu29) ...
> update-initramfs: deferring update (trigger activated)
>
> Setting up linux-image-2.6.28-13-generic (2.6.28-13.44) ...
> Running depmod.
> update-initramfs: Generating /boot/initrd.img-2.6.28-13-generic
> cpio: ./bin/udevinfo: Cannot stat: No such file or directory
> update-initramfs: failed for /boot/initrd.img-2.6.28-13-generic
> Failed to create initrd image.
> dpkg: error processing linux-image-2.6.28-13-generic (--configure):
> subprocess post-installation script returned error exit status 2
> dpkg: dependency problems prevent configuration of linux-image-generic:
> linux-image-generic depends on linux-image-2.6.28-13-generic; however:
> Package linux-image-2.6.28-13-generic is not configured yet.
> dpkg: error processing linux-image-generic (--configure):
> dependency problems - leaving unconfigured
> Processing triggers for initramfs-tools ...
> update-initramfs: Generating /boot/initrd.img-2.6.27-14-generic
> cpio: ./bin/udevinfo: Cannot stat: No such file or directory
> update-initramfs: failed for /boot/initrd.img-2.6.27-14-generic
> dpkg: subprocess post-installation script returned error exit status 1
> nkj@nkj-laptop:~$
>
> --
> update 8.10 to 9.04 ==> Pb with udevinfo (not found)
> https://bugs.launchpad.net/bugs/350988
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “update-manager” source package in Ubuntu: Incomplete
>
> Bug description:
> Binary package hint: update-manager
>
> In script update-initramfs, cpio command don't found ./udevinfo
> dpkg --configure -a give the same error
> Update cancelled, impossible to restart in previous configuration
>
> ProblemType: Crash
> Architecture: i386
> DistroRelease: Ubuntu 9.04
> ExecutablePath: /usr/bin/update-manager
> InterpreterPath: /usr/bin/python2.6
> NonfreeKernelModules: nvidia
> Package: update-manager 1:0.111.0
> PackageArchitecture: all
> ProcAttrCurrent: unconfined
> ProcCmdline: /usr/bin/python2.6 /usr/bin/update-manager -dc
> ProcEnviron:
> SHELL=/bin/bash
> LANG=fr_FR.UTF-8
> LANGUAGE=fr_FR:fr:en_GB:en
> PythonArgs: ['/usr/bin/update-manager', '-dc']
> SourcePackage: update-manager
> Title: update-manager crashed with RuntimeError in <module>()
> Traceback:
> Traceback (most recent call last):
> File "/usr/bin/update-manager", line 44, in <module>
> gtk.init_check()
> RuntimeError: could not open display
> Uname: Linux 2.6.27-14-generic i686
> UserGroups: lpadmin
>

[rc3 (midnightcodr)]

How about creating this file
/bin/udevinfo
with the following lines in it:
#!/bin/bash
udevadm info $@

Make it executable:
chmod +x /bin/udevinfo

Then try your command again.

[NKJensen (nkj)]

Thanks for you help - I see what you are trying to do to correct old versus new udev behaviour.

Unfortunatly, it did not fix the problem.

The script is in place, and I can run it with command line argument "-help" and udevadm answers.

But the error message:

update-initramfs: Generating /boot/initrd.img-2.6.28-13-generic
cpio: ./bin/udevinfo: Cannot stat: No such file or directory

still results if I run "sudo dpkg --configure -a", leaving me pretty much stuck.

What I don't get, though, is how cpio is involved in this part of the work....

[NKJensen (nkj)]

I found some more info here:

https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/323894/comments/4

but it seems to be slightly off. In my case "dpkg --configure -a" crashes. Any ideas?

[NKJensen (nkj)]

I tried this advice:

rename update-initramfs and place a shellscript

#! /bin/sh
exit 0

Then run "dpkg --configure -a"

It worked, so that "dpkg --audit" now returns with no errors. I can still only boot in "rescue mode", and fixing the packages, fixing the X system does still not work.

I tried to reinstall the original update-initramfs and the error is back.

[Kafi (kafiland)]

Hola,

For your information, passing to karmic solve this...

Good luck!

Kafi

Passer à Karmic résoud le problème chez moi

[GuyR (guy-rouger)]

Hello
Happend using this

guy@ubuntu-desktop:~$ crontab -l
no crontab for guy
guy@ubuntu-desktop:~$ crontab -e
no crontab for guy - using an empty one

Select an editor. To change later, run 'select-editor'.
  1. /bin/ed
  2. /bin/nano <---- easiest
  3. /usr/bin/vim.tiny

Choose 1-3 [2]: 2
crontab: installing new crontab
guy@ubuntu-desktop:~$ crontab -l
# m h dom mon dow command
0-15-30-45 * * * * /usr/bin/update-manager

[GuyR (guy-rouger)]

To: guy@guy-desktop
Subject: Cron <guy@ubuntu-desktop> /usr/bin/update-manager
Content-Type: text/plain; charset=ANSI_X3.4-1968
X-Cron-Env: <SHELL=/bin/sh>
X-Cron-Env: <HOME=/home/guy>
X-Cron-Env: <PATH=/usr/bin:/bin>
X-Cron-Env: <LOGNAME=guy>
Date: Fri, 9 Apr 2010 10:02:14 +0200 (CEST)

/usr/lib/pymodules/python2.6/gtk-2.0/gtk/__init__.py:57: GtkWarning: could not open display
  warnings.warn(str(e), _gtk.Warning)
Traceback (most recent call last):
  File "/usr/bin/update-manager", line 43, in <module>
    gtk.init_check()
RuntimeError: could not open display

[miked (miked11)]

This bug was long ago and probably took out the computer I was using at the time. Please close this bug for me, I have probably upgraded many times since then, or no longer have access to the machine. thanks.