X not working when 855resolution installed and upgrading from Breezy to Dapper

Bug #41977 reported by Gaele Strootman
6
Affects Status Importance Assigned to Milestone
915resolution (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

855resolution is only available in Breezy. It is replaced by 915resolution in Dapper. However, if 855resolution is installed on Breezy, then it is not automatically upgraded to 915resolution during the upgrade to Dapper (beta).
After the Dapper upgrade X will try to start with a resolution it can not support anymore.

Steps to reproduce:
1. install Breezy
2. install 855resolution
3. choose a resolution of e.g. 1400x1050
4. upgrade to Dapper beta
5. reboot
6. X won't start

Note: 855resolution and 915resolution both need a (different) manually edited config file to work.

A work-around would be to remove the conflicting resolution(s) from xorg.conf before upgrading to Dapper.

Revision history for this message
Michel D'HOOGE (michel-dhooge) wrote :

It is a bit long to reproduce!
Can you check the state of your 855resolution package with the following command?
dpkg -s 855resolution

And since 'dpkg -s 915resolution' gives the following output...
Package: 915resolution
Status: install ok installed
Priority: extra
Section: x11
Installed-Size: 124
Maintainer: Steffen Joeris <email address hidden>
Architecture: i386
Version: 0.5-1ubuntu5
Replaces: 855resolution
Provides: 855resolution
Depends: libc6 (>= 2.3.4-1)
Recommends: vbetool (>= 0.6-1)
Conflicts: 855resolution

I think the problem may be more in the upgrade process which should have warned about the conflict.

Changed in 915resolution:
status: Unconfirmed → Needs Info
Revision history for this message
Gaele Strootman (gaele) wrote :

As I upgraded to Dapper I no longer have 855resolution available, so I cannot check its state for you.

> I think the problem may be more in the upgrade process which
> should have warned about the conflict.

Exactly.

I noticed the latest version of 915resolution will automatically detect the maximum available resolution. Which means that it might not need a manually edited config file anymore.

Which leaves us with one question: can 855resolution be automatically replaced with 915resolution during the upgrade process? I guess that will solve the problem.

Revision history for this message
Paul Sladen (sladen) wrote :

Excellent!

Changed in 915resolution:
status: Needs Info → Fix Released
Revision history for this message
Paul Sladen (sladen) wrote :

It is automatically replaced.

$ apt-cache show 915resolution | grep 855
Replaces: 855resolution
Provides: 855resolution
Conflicts: 855resolution
 855G, and 865G chipsets, as well as 915G, 915GM, and 945G chipsets.

As of the latest version, it now makes some attempt to auto-detect your panel-size (note, this will probably screw-over external VGA or dual-head).

You're right that it does a replace but doesn't make an effort to parse the configuration files. Since it would be preferable to use the 'auto' configuration I'm not sure whether to add it.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.