Normally your system would be able to have both and i386 and an amd64
version at the same time. But that's a library for the video driver, so
it doesn't really make sense to have 2 different versions of it at the
same time unless you are going to be driving 2 different video cards and
want/need to use a 64bit and a 32bit at the same time.
The way I would have done it is to do CTRL+ALT+F1, login as you and then do:
sudo stop lightdm
sudo dpkg -r libdrm-radeon1:i386
sudo apt-get install libdrm-radeon1
Hopefully that would take care of it.
Brian Cluff
On 07/05/2013 06:44 PM, Dazed_75 wrote:
> I thought the :i386 packages were part of the system for supporting 32
> bit programs to run in 64-bit (though I had always though there was no
> problem doing so except for packages that used the kernel directly (like
> drivers).
>
> Anyway, that did not help. when I went to a console (i.e. ctrl-F2) and
> killed X it just dropped me to the login screen (which makes some
> sense). So I restarted and used the recovery console. Using that
> command to me the filesystem was ro so I went back to the recovery
> screen and chose the dpkg fix entry from the menu. That looked like it
> fixed things and did install the other 9 updates, but still complained
> about the i386 thing. Dropping to a root shell again (the FS was now
> rw), I tried again to dpkg -r .. to no avail.
>
> rebooting put me back in normally and the Update Manager now shows only
> libdrm-radeon1 needing update but it fails the same way. I'm going to
> hope the update itself caused the problem and maybe they will put out a
> fix this weekend.
>
> Thanks for your help!
>
>
> On Fri, Jul 5, 2013 at 6:06 PM, Brian Cluff <brian@snaptek.com
> <mailto:brian@snaptek.com>> wrote:
>
> Looks like you managed to get both the i386 version and the amd64
> version of libdrm-radeon1 trying to install at the same time, and of
> course stepping on each others toes since they provide the same
> thing. I've run into similar problems in the past with other
> packages that atarted out with an i386 only version and then later
> added a 64bit version.
>
> You should be able to fix yourself right up by doing:
> dpkg -r libdrm-radeon1:i386
>
> You might want to do the above from a plain console without X
> running since you will be swapping part of it's brains out with a
> totally different version, just be be safe.
>
> Brian Cluff
>
>
> On 07/05/2013 05:55 PM, Dazed_75 wrote:
>
> Update. None of the known fixes and when the Update Manager
> complains
> and I click on Details, it says:
>
> The following packages have unmet dependencies:
>
> libdrm-radeon1:Depends:libc6(>__=2.14) but 2.15-0ubuntu10.4 is
> installed
> libdrm-radeon1:i386:
>
> The way I read that it looks like not a problem. BTW, this is
> Ubuntu
> 12.04.2 64bit which makes me wonder about that 10.4 in the message.
>
>
> On Fri, Jul 5, 2013 at 5:44 PM, Dazed_75 <lthielster@gmail.com
> <mailto:lthielster@gmail.com>
> <mailto:lthielster@gmail.com <mailto:lthielster@gmail.com>>> wrote:
>
> Thsi may only affect some people and maybe only those with
> Radeon
> graphics, but the error I got just said "Error: Broken
> Count >0". I
> tried fixing broken packages to no avail. In the end, I got
>
> dpkg: error processing libdrm-radeon1 (--configure):
> libdrm-radeon1:amd64 2.4.43-0ubuntu0.0.1 cannot be configured
> because libdrm-radeon1:i386 is in a different version
> (2.4.43-0ubuntu0.0.2)
> dpkg: error processing libdrm-radeon1:i386 (--configure):
> libdrm-radeon1:i386 2.4.43-0ubuntu0.0.2 cannot be configured
> because libdrm-radeon1:amd64 is in a different version
> (2.4.43-0ubuntu0.0.1)
> Errors were encountered while processing:
> libdrm-radeon1
> libdrm-radeon1:i386
> E: Sub-process /usr/bin/dpkg returned an error code (1)
>
>
> --
> Dazed_75 a.k.a. Larry
>
> Please protect my address like I protect yours. When sending
> messages to multiple recipients, use the BCC: (Blind carbon
> copy).
> Remove addresses from a forwarded message body before
> clicking Send.
>
>
>
>
> --
> Dazed_75 a.k.a. Larry
>
> Please protect my address like I protect yours. When sending
> messages to
> multiple recipients, use the BCC: (Blind carbon copy). Remove
> addresses
> from a forwarded message body before clicking Send.
>
>
> ------------------------------__---------------------
> PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.__org
> <mailto:PLUG-discuss@lists.phxlinux.org>
> To subscribe, unsubscribe, or to change your mail settings:
> http://lists.phxlinux.org/__mailman/listinfo/plug-discuss
> <http://lists.phxlinux.org/mailman/listinfo/plug-discuss>
>
> ------------------------------__---------------------
> PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.__org
> <mailto:PLUG-discuss@lists.phxlinux.org>
> To subscribe, unsubscribe, or to change your mail settings:
> http://lists.phxlinux.org/__mailman/listinfo/plug-discuss
> <http://lists.phxlinux.org/mailman/listinfo/plug-discuss>
>
>
>
>
> --
> Dazed_75 a.k.a. Larry
>
> Please protect my address like I protect yours. When sending messages to
> multiple recipients, use the BCC: (Blind carbon copy). Remove addresses
> from a forwarded message body before clicking Send.
>
>
> ---------------------------------------------------
> PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
> To subscribe, unsubscribe, or to change your mail settings:
> http://lists.phxlinux.org/mailman/listinfo/plug-discuss
>
---------------------------------------------------
PLUG-discuss mailing list -
PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
http://lists.phxlinux.org/mailman/listinfo/plug-discuss
(text/plain)