package fglrx (not installed) failed to install/upgrade: trying to overwrite '/etc/ati/signature', which is also in package xorg-driver-fglrx 2:8.721-0ubuntu8

Same error here:

....dpkg: errore nell'elaborare /var/cache/apt/archives/fglrx_2%3a8.721-0ubuntu10_i386.deb (--unpack):
 tentata sovrascrittura di "/etc/ati/signature" presente anche nel pacchetto xorg-driver-fglrx 2:8.721-0ubuntu10
......
Let me know if I can give more info.

(Sorry for the pollution; I've already posted info in another bug discussion).

fglrx on my system did not upgrade form 9.10 to 10.4 beta 2.

$ apt-get install fglrx
....
 Unpacking fglrx (from .../fglrx_2%3a8.721-0ubuntu10_i386.deb) ...
 dpkg: error processing /var/cache/apt/archives/fglrx_2%3a8.721-0ubuntu10_i386.deb (--unpack):
 trying to overwrite '/etc/ati/signature', which is also in package xorg-driver-fglrx 2:8.721-0ubuntu7

$ aptitude search fglrx
p fglrx - Video driver for the ATI graphics accelerators
BdA fglrx-amdcccle - Catalyst Control Center for the ATI graphics accelerat
p fglrx-dev - Video driver for the ATI graphics accelerators (devel
BdA fglrx-kernel-source - Transitional package for fglrx-kernel-source
i fglrx-modaliases - Identifiers supported by the ATI graphics driver

$ aptitude show fglrx-modaliases
Package: fglrx-modaliases
State: installed
Automatically installed: no
Version: 2:8.721-0ubuntu7
...

This bug was fixed in the package fglrx-installer - 2:8.723.1-0ubuntu2

---------------
fglrx-installer (2:8.723.1-0ubuntu2) lucid; urgency=low

  * debian/fglrx.dirs, fglrx.install.in, fglrx.postinst,
    fglrx.preinst:
    - Make /etc/ati a slave link which points to
      /usr/lib/fglrx/etc/ati. This will avoid issues when
      upgrading packages with user modified files in
      /etc/ati (LP: #559587, LP: #440233).
    - Make sure to remove /etc/ati if it's not a link.
 -- Alberto Milone <email address hidden> Wed, 14 Apr 2010 17:37:14 +0200

E: /var/cache/apt/archives/fglrx_2%3a8.723.1-0ubuntu1_i386.deb: trying to overwrite '/etc/ati/signature', which is also in package xorg-driver-fglrx 2

Sorry folks that I'm not technically proficient enough to specify where the new fglrx I installed and rebooted last night REALLY messes my system up. I do see that my ubuntu boot is of the lucid flavor, but after the splash screen starts (and gets as far as the word UBUNTU and five dots below), I get only vertical stripes. No way to see the login box. For what it's worth, last night's pattern had a lot of white stripes; tonight there's a lot of black between the colored stripes. I can't get into a recovery/safe mode, or even to the prior karmic kernel. I'm writing this now from another machine, though Vista boots fine on that first pc (EVGA 630i MB with onboard Nvidia for what it's worth--maybe check ubuntuforums for the specs). FYI, it's still working as expected in the Vista boot, likewise using the HDMI cable to the all-in-wonder video/tuner card -- so these stripes aren't a hardware failure. Unfortunately, with the deadlines coming this week, I won't be able to mess around with it for a few days. Should I just try to boot with a Karmic cd to be able to read files on the ubuntu portion of the hard disk, or wait to burn an iso of the release candidate?

Sorry to bother, but how can I install the fixed fglrx-installer??

@nikolausbooth:
Version 2:8.723.1-0ubuntu2 contains the fix while you're using 2:8.723.1-0ubuntu1

@jurrabi
You should wait until the server that you're using gets the new packages.

@jweaver28
You didn't provide a log or any kind of evidence that what you're experiencing is relevant to the problem discussed in this bug report

You could just boot in recovery mode, drop to the command line with networking support, type "jockey-text -d fglrx" and reboot. Things should be back to normal then.

Sorry, Alberto, I can't get into recovery mode. From what I remember, recovery mode is an option after the logon screen, and the video craziness starts just before the logon screen. I suppose I could boot from a karmic cd, but where would I look for the log? IMHO, a "can't start" bug is worse than the "can't update because of broken package" bug that this started as.

@jweaver28
You can access the grub menu by holding the "shift" key immediately after turning on your computer (after the bios). You'll be able to enter Recovery mode from there.