X not working when 855resolution installed and upgrading from Breezy to Dapper
Bug #41977 reported by
Gaele Strootman
This bug report is a duplicate of:
Bug #46176: vbetool autoconfig fails to set 915resolution config.
Edit
Remove
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.
To post a comment you must log in.
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.