Control: tags -1 + moreinfo

Hi Ciril and Jan-Hendrik,

2010-11-07 18:50 Cyril Brulebois:
Package: aptitude
Version: 0.6.3-3.2
Severity: important

Hi,

context: I've got the whole X Server 1.9 stack installed from experimental,
except a few video drivers. After having uploaded -ati/-radeon to
experimental, I tried to install them through the GUI, with '+' on them,
but that doesn't work because the unstable version is preferred, so they
appear as 'broken' (as expected). Then, in turn, I pick the experimental
version, and everything goes green again.

Unfortunately, hitting 'g' to perform the installation leads to this
assertion:
| Exception : ../../src/ui.cc:1389: void auto_fix_broken(): Assertion 
"resman->resolver_exists()" failed.

That's reproducible.

(Full package name: xserver-xorg-video-ati and xserver-xorg-video-radeon.)


Trying the CLI, same kind of issues. Here's a transcript:
[...]
| The following actions will resolve these dependencies:
|
|      Install the following packages:
| 1)     xserver-xorg-video-ati [1:6.13.2-1 (experimental)]
| 2)     xserver-xorg-video-radeon [1:6.13.2-1 (experimental)]
|
|
|
| Accept this solution? [Y/n/q/?] y
| The following packages have unmet dependencies:
|   xserver-xorg-core: Breaks: xserver-xorg-video-6 which is a virtual package.
| *** ERROR: search aborted by fatal exception.  You may continue
|            searching, but some solutions will be unreachable.
|
| I want to resolve dependencies, but no dependency resolver was created.The 
following NEW packages will be installed:
|   xserver-xorg-video-ati xserver-xorg-video-radeon
| 0 packages upgraded, 2 newly installed, 0 to remove and 2 not upgraded.
| Need to get 0 B/910 kB of archives. After unpacking 1847 kB will be used.
| aptitude failed to find a solution to these dependencies.  You can solve them 
yourself by hand or type 'n' to quit.
| The following packages have unmet dependencies:
|   xserver-xorg-core: Breaks: xserver-xorg-video-6 which is a virtual package.
| Resolve these dependencies by hand? [N/+/-/_/:/?] ^C

That's reproducible as well.

As you can see below, I have Debian's testing, unstable, and
experimental repositories enabled, and only that.


2010-12-03 17:39 Jan-Hendrik (HennR) Peters:
Same problem here.

I'm trying to replace xserver-xorg-video-radeonhd with
xserver-xorg-video-radeon:

# aptitude install xserver-xorg-video-radeon

[...]

Accept this solution? [Y/n/q/?] y
The following packages have unmet dependencies:
 xserver-xorg-core: Breaks: xserver-xorg-video-6 which is a virtual
package.
*** ERROR: search aborted by fatal exception.  You may continue
          searching, but some solutions will be unreachable.

I want to resolve dependencies, but no dependency resolver was
created.The following NEW packages will be installed:
 xserver-xorg-video-radeon
0 packages upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/665 kB of archives. After unpacking 1,520 kB will be used.
aptitude failed to find a solution to these dependencies.  You can solve
them yourself by hand or type 'n' to quit.
The following packages have unmet dependencies:
 xserver-xorg-core: Breaks: xserver-xorg-video-6 which is a virtual
package.
Resolve these dependencies by hand? [N/+/-/_/:/?]
Abort.


So far so good.

But if I start aptitude with ncurses and do the following:

mark xserver-xorg-video-radeonhd to get removed
mark xserver-xorg-video-radeon to get installed
switch to dependency resolve mode (pressing e)
choose alternative number 2 (install xserver-xorg-video-radeon)
submitting my choice by pressing "!" aptitude crashes with this error:

Uncaught exception: ../../src/ui.cc:1389: void auto_fix_broken():
Assertion "resman->resolver_exists()" failed.

sometimes I have to press "g" to make it crash tough.

Well, I just figured out that this happens as well if I don't mark
xserver-xorg-video-radeonhd to get removed before.


Have you both experienced this issue in that last few years, after this
report that you have sent?

I have not seen any other bug reports related with this problem in the
hundreds that I have triaged in the last few years, and the problems in
this report seem to have happened at a very specific point in time,
within one month, and never reported since.

This can have been caused by a bad compilation, or bad interaction/ABI
incompatibility of some of the libraries.

If it wasn't experienced after that point in time, I don't think that it
makes a lot of sense to chase it after 5 years.


Cheers.
--
Manuel A. Fernandez Montecelo <manuel.montez...@gmail.com>

Reply via email to