Gee! These Aren't Roasted!
I'm already running 13.10 though.
Code:~$ ls -la /var/cache/apt/archives/ total 88 drwxr-xr-x 3 root root 77824 Dec 20 04:49 . drwxr-xr-x 3 root root 4096 Dec 23 15:52 .. -rw-r----- 1 root root 0 Oct 16 20:05 lock drwxr-xr-x 2 root root 4096 Dec 20 03:41 partial
Ubuntu Member
slgtheindividual; OK !
My bad not remembering we are coping with 13.10.
Continuing plan A, let's try this !
I do have some heavy concern that the system may be borked (!); But, this is the last thing I can think of to try.
That syntax now I am uncertain about, if the "dpkg -i" fails try it as:Code:cd /var/cache/apt/archives wget http://gb.archive.ubuntu.com/ubuntu/pool/main/s/systemd/libudev1_204-0ubuntu19.1_amd64.deb wget http://gb.archive.ubuntu.com/ubuntu/pool/main/s/systemd/udev_204-0ubuntu19.1_amd64.deb sudo dpkg -i --force-remove-reinstreq libudev1_204-0ubuntu19.1 sudo dpkg -i --force-remove-reinstreq udev_204-0ubuntu19.1 sudo update-initramfs -u
something has got to give.Code:sudo dpkg -i --force-remove-reinstreq libudev1=204-0ubuntu19.1 sudo dpkg -i --force-remove-reinstreq udev=204-0ubuntu19.1
cheers
Gee! These Aren't Roasted!
ok well it basically worked until the dpkg commands (I tried both to be sure)
Code:~$ cd /var/cache/apt/archives /var/cache/apt/archives$ wget http://gb.archive.ubuntu.com/ubuntu/pool/main/s/systemd/libudev1_204-0ubuntu19.1_amd64.deb --2013-12-24 05:03:46-- http://gb.archive.ubuntu.com/ubuntu/pool/main/s/systemd/libudev1_204-0ubuntu19.1_amd64.deb Resolving gb.archive.ubuntu.com (gb.archive.ubuntu.com)... 91.189.92.201, 194.169.254.10, 91.189.92.156, ... Connecting to gb.archive.ubuntu.com (gb.archive.ubuntu.com)|91.189.92.201|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 35896 (35K) [application/x-debian-package] libudev1_204-0ubuntu19.1_amd64.deb: Permission denied Cannot write to ‘libudev1_204-0ubuntu19.1_amd64.deb’ (Permission denied). /var/cache/apt/archives$ sudo !! sudo wget http://gb.archive.ubuntu.com/ubuntu/pool/main/s/systemd/libudev1_204-0ubuntu19.1_amd64.deb --2013-12-24 05:03:57-- http://gb.archive.ubuntu.com/ubuntu/pool/main/s/systemd/libudev1_204-0ubuntu19.1_amd64.deb Resolving gb.archive.ubuntu.com (gb.archive.ubuntu.com)... 91.189.92.201, 194.169.254.10, 91.189.92.156, ... Connecting to gb.archive.ubuntu.com (gb.archive.ubuntu.com)|91.189.92.201|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 35896 (35K) [application/x-debian-package] Saving to: ‘libudev1_204-0ubuntu19.1_amd64.deb’ 100%[======================================>] 35,896 --.-K/s in 0.05s 2013-12-24 05:03:57 (726 KB/s) - ‘libudev1_204-0ubuntu19.1_amd64.deb’ saved [35896/35896] /var/cache/apt/archives$ sudo wget http://gb.archive.ubuntu.com/ubuntu/pool/main/s/systemd/udev_204-0ubuntu19.1_amd64.deb --2013-12-24 05:04:12-- http://gb.archive.ubuntu.com/ubuntu/pool/main/s/systemd/udev_204-0ubuntu19.1_amd64.deb Resolving gb.archive.ubuntu.com (gb.archive.ubuntu.com)... 194.169.254.10, 91.189.92.156, 91.189.92.200, ... Connecting to gb.archive.ubuntu.com (gb.archive.ubuntu.com)|194.169.254.10|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 1039732 (1015K) [application/x-debian-package] Saving to: ‘udev_204-0ubuntu19.1_amd64.deb’ 100%[======================================>] 1,039,732 2.16MB/s in 0.5s 2013-12-24 05:04:12 (2.16 MB/s) - ‘udev_204-0ubuntu19.1_amd64.deb’ saved [1039732/1039732] /var/cache/apt/archives$ sudo dpkg -i --force-remove-reinstreq libudev1_204-0ubuntu19.1 dpkg: error processing libudev1_204-0ubuntu19.1 (--install): cannot access archive: No such file or directory Errors were encountered while processing: libudev1_204-0ubuntu19.1 /var/cache/apt/archives$ sudo dpkg -i --force-remove-reinstreq libudev1=204-0ubuntu19.1 dpkg: error processing libudev1=204-0ubuntu19.1 (--install): cannot access archive: No such file or directory Errors were encountered while processing: libudev1=204-0ubuntu19.1 /var/cache/apt/archives$ sudo dpkg -i --force-remove-reinstreq udev_204-0ubuntu19.1 dpkg: error processing udev_204-0ubuntu19.1 (--install): cannot access archive: No such file or directory Errors were encountered while processing: udev_204-0ubuntu19.1 /var/cache/apt/archives$ sudo dpkg -i --force-remove-reinstreq udev=204-0ubuntu19.1 dpkg: error processing udev=204-0ubuntu19.1 (--install): cannot access archive: No such file or directory Errors were encountered while processing: udev=204-0ubuntu19.1 /var/cache/apt/archives$ sudo update-initramfs -u update-initramfs: Generating /boot/initrd.img-3.11.0-14-generic
Ubuntu Member
slgtheindividual; Oh !
My bad again ! I see the error of my ways !
try it as:
edit: from the PWD "/var/cache/apt/archives"
Give it the correct file name ! - may bad bad bad -Code:sudo dpkg -i --force-remove-reinstreq libudev1_204-0ubuntu19.1_amd64.deb sudo dpkg -i --force-remove-reinstreq udev_204-0ubuntu19.1_amd64.deb
As I fumble my way through my darkness.
Crossed fingers on many ways, let's see what breaks.
high regards
Last edited by Bashing-om; December 24th, 2013 at 06:41 PM. Reason: Present Working Directory
Staff Emeritus
I have been following this thread - I tried to reproduce your situation by installing the 2 ppas that we discovered into a saucy vm, bu the nearest I could find is that it is wine that installs the libudev1:i386, however even if I install wine1.7 the version never goes above 204-0ubuntu19.1
Nevertheless I wonder if it is worth trying to apt-get remove wine? Although I suspect the package system breakage won't let you do that, *maybe* if wine is the *only* thing requiring that package it will...Code:$ sudo apt-get install --dry-run wine1.7 | grep udev libtiff5:i386 libtinfo5:i386 libtxc-dxtn-s2tc0:i386 libudev1:i386 libtiff5:i386 libtinfo5:i386 libtxc-dxtn-s2tc0:i386 libudev1:i386 Inst libudev1:i386 (204-0ubuntu19.1 Ubuntu:13.10/saucy-updates [i386]) Conf libudev1:i386 (204-0ubuntu19.1 Ubuntu:13.10/saucy-updates [i386])
BTW Bashing-om's dpkg commands likely failed to execute because AFAIK dpkg -i needs the whole filename (including the .deb suffix)
Ubuntu Member
@ steeldriver; Glad you are keeping up with this one !
I am embarrassed at all the mistakes I am making, as well as the time factor and still no closure !
If that last "force" is ineffective -
Recon we will have to edit the control files to make it possible to remove the offending packages ???
Or as you say, find the package that is driving the libraries to the trusty version .. That too was my next thought ,, to selectively remove the PPAs and see what results.
Hey, we can do this
where there is a will there is a way
Gee! These Aren't Roasted!
Ok well I tried it and still got errors:
Code:~$ cd /var/cache/apt/archives /var/cache/apt/archives$ sudo wget http://gb.archive.ubuntu.com/ubuntu/pool/main/s/systemd/libudev1_204-0ubuntu19.1_amd64.deb --2013-12-24 19:50:38-- http://gb.archive.ubuntu.com/ubuntu/pool/main/s/systemd/libudev1_204-0ubuntu19.1_amd64.deb Resolving gb.archive.ubuntu.com (gb.archive.ubuntu.com)... 91.189.92.201, 194.169.254.10, 91.189.92.156, ... Connecting to gb.archive.ubuntu.com (gb.archive.ubuntu.com)|91.189.92.201|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 35896 (35K) [application/x-debian-package] Saving to: ‘libudev1_204-0ubuntu19.1_amd64.deb’ 100%[======================================>] 35,896 --.-K/s in 0.1s 2013-12-24 19:50:38 (368 KB/s) - ‘libudev1_204-0ubuntu19.1_amd64.deb’ saved [35896/35896] /var/cache/apt/archives$ sudo wget http://gb.archive.ubuntu.com/ubuntu/pool/main/s/systemd/udev_204-0ubuntu19.1_amd64.deb --2013-12-24 19:50:50-- http://gb.archive.ubuntu.com/ubuntu/pool/main/s/systemd/udev_204-0ubuntu19.1_amd64.deb Resolving gb.archive.ubuntu.com (gb.archive.ubuntu.com)... 194.169.254.10, 91.189.92.156, 91.189.92.200, ... Connecting to gb.archive.ubuntu.com (gb.archive.ubuntu.com)|194.169.254.10|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 1039732 (1015K) [application/x-debian-package] Saving to: ‘udev_204-0ubuntu19.1_amd64.deb’ 100%[======================================>] 1,039,732 1.29MB/s in 0.8s 2013-12-24 19:50:51 (1.29 MB/s) - ‘udev_204-0ubuntu19.1_amd64.deb’ saved [1039732/1039732] /var/cache/apt/archives$ sudo dpkg -i --force-remove-reinstreq libudev1_204-0ubuntu19.1_amd64.deb (Reading database ... 394713 files and directories currently installed.) Preparing to replace libudev1:amd64 204-0ubuntu19.1 (using libudev1_204-0ubuntu19.1_amd64.deb) ... Unpacking replacement libudev1:amd64 ... dpkg: error processing libudev1:amd64 (--install): package libudev1:amd64 204-0ubuntu19.1 cannot be configured because libudev1:i386 is at a different version (204-5) Errors were encountered while processing: libudev1:amd64 /var/cache/apt/archives$ sudo dpkg -i --force-remove-reinstreq udev_204-0ubuntu19.1_amd64.deb dpkg: warning: downgrading udev from 204-5 to 204-0ubuntu19.1 (Reading database ... 394713 files and directories currently installed.) Preparing to replace udev 204-5 (using udev_204-0ubuntu19.1_amd64.deb) ... Adding 'diversion of /bin/udevadm to /bin/udevadm.upgrade by fake-udev' Unpacking replacement udev ... dpkg: dependency problems prevent configuration of udev: udev depends on libudev1 (= 204-0ubuntu19.1); however: Package libudev1:amd64 is not configured yet. consolekit (0.4.6-3+b1) breaks udev (<< 204-1) and is installed. Version of udev to be configured is 204-0ubuntu19.1. dpkg: error processing udev (--install): dependency problems - leaving unconfigured Processing triggers for ureadahead ... ureadahead will be reprofiled on next reboot Processing triggers for man-db ... Errors were encountered while processing: udev
Ubuntu Member
slgtheindividual; This is for a fact getting real old.
Going round and around with the 32 bit libraries (i386).
I do not know -in these later versions of the operating system - where/if they are installed; or how the integration is done into the 64 bit OS.cannot be configured because libudev1:i386
Let's see what we can do do find those relationships:
what returns:
Has to exist somewhere, this should be the place in which to look !Code:ls -la /var/lib/dpkg/info/libudev* grep -B3 -A10 libudev1:i386 /var/lib/dpkg/status
sometimes I wonder, other times
I do not know
Gee! These Aren't Roasted!
ok no problem, that gives me:
Code:$ ls -la /var/lib/dpkg/info/libudev* -rw-r--r-- 1 root root 237 Dec 24 19:51 /var/lib/dpkg/info/libudev1:amd64.list -rw-r--r-- 1 root root 216 Dec 10 17:09 /var/lib/dpkg/info/libudev1:amd64.md5sums -rwxr-xr-x 1 root root 135 Dec 10 17:09 /var/lib/dpkg/info/libudev1:amd64.postinst -rwxr-xr-x 1 root root 132 Dec 10 17:09 /var/lib/dpkg/info/libudev1:amd64.postrm -rw-r--r-- 1 root root 49 Dec 10 17:09 /var/lib/dpkg/info/libudev1:amd64.shlibs -rw-r--r-- 1 root root 3982 Dec 10 17:09 /var/lib/dpkg/info/libudev1:amd64.symbols -rw-r--r-- 1 root root 231 Nov 11 20:14 /var/lib/dpkg/info/libudev1:i386.list -rw-r--r-- 1 root root 214 Sep 23 13:25 /var/lib/dpkg/info/libudev1:i386.md5sums -rwxr-xr-x 1 root root 135 Sep 23 13:25 /var/lib/dpkg/info/libudev1:i386.postinst -rwxr-xr-x 1 root root 132 Sep 23 13:25 /var/lib/dpkg/info/libudev1:i386.postrm -rw-r--r-- 1 root root 49 Sep 23 13:24 /var/lib/dpkg/info/libudev1:i386.shlibs -rw-r--r-- 1 root root 3982 Sep 23 13:24 /var/lib/dpkg/info/libudev1:i386.symbols $ grep -B3 -A10 libudev1:i386 /var/lib/dpkg/status $
Ubuntu Member
slgtheindividual; That at least is something:
Let's see where this leads:
While I am scratching my head why "/var/lib/dpkg/status" has a non-positive result/ not at all what I had expected//Code:cat /var/lib/dpkg/info/libudev1:i386.list
This may be a VERY long output, but anything meaningful in respect to "i386" from (??):
Code:grep -B3 -A10 "libudev1*" /var/lib/dpkg/statusshooting blanks
and still in the dark
Adv Reply
Bookmarks