Weblog entry #6 for Utumno

Mess after dist-upgrading Sid to Xorg 7.0
Posted by Utumno on Mon 17 Apr 2006 at 08:22
Tags: none.
Saturday I foolishly dist-upgraded my Sid to Xorg 7.0... All hell broke loose. Several missing modules ( 1. xserver-xorg-input-all should Depend: on xserver-xorg-input-kbd and xserver-xorg-input-mouse, shouldn't it? 2. xfonts-base got deinstalled 3. nvidia proprietary drivers no longer work 4. mess, mess, mess. )

I recommend waiting a few weeks until things settle down.

 

Comments on this Entry

Posted by Utumno (60.248.xx.xx) on Mon 17 Apr 2006 at 08:29
[ Send Message | View Utumno's Scratchpad | View Weblogs ]
I should mention I finally got it working with a few 'apt-get --reinstall' s , 'vim xorg.conf' s and the like. However, that was not for the faint at heart.

[ Parent | Reply to this comment ]

Posted by rbochan (24.59.xx.xx) on Mon 17 Apr 2006 at 13:51
[ Send Message | View Weblogs ]
xserver-xorg-input-all should Depend: on xserver-xorg-input-kbd and xserver-xorg-input-mouse, shouldn't it?

You'd think that "xserver-xorg-input-all" would include "xserver-xorg-input-synaptics" as well, but it doesn't. That screwed me for a good 45 minutes until I realized it.
After a good 3 hours of mucking around with it, my secondary laptop still isn't right...
-KDE (using startx) is coming up at 75 dpi instead of 100
-no 3d accelleration
-can no longer use external PS/2 mouse
-fonts fonts and more fonts issues than I can count

I have no idea how this made it out of experimental.

...Rob

The American Dream isn't an SUV and a house in the suburbs; it's Don't Tread On Me.

[ Parent | Reply to this comment ]

Posted by simonw (84.45.xx.xx) on Mon 17 Apr 2006 at 21:59
[ Send Message | View Weblogs ]
I think the answer to why it got in unstable so quickly, is that it was always going to hurt. The nice folks in Ubuntu did a lot of the hard work here, so unstable is playing catch-up not only with Xorg, but also with other "based on" (in a very loose sense here) Debian distros.

Judging from various reports some people got through it unscathed, and perhaps not enough people were running X from Experimental (that figures).

I waited a while, till a few solutions appeared, and then upgraded myself, discovering a new bug, and backed out. The maintainer was in #debian trying to sort these when he was suppose to be organising a party for a friend, what more can one ask on an Easter Sunday?

When modularising packages, life in unstable is always going to be hairy, which is why everyone tells you not to run unstable on real boxes.

If in doubt install package "xorg" and hope, I expect the more serious problems to be sorted either by now, or in the next day or two. If you are running unstable, you should be trying this now, and reporting the bugs, not waiting till it is all smelling of roses.

http://wiki.debian.org/Xorg69To7

[ Parent | Reply to this comment ]

Posted by Utumno (60.248.xx.xx) on Tue 18 Apr 2006 at 02:53
[ Send Message | View Utumno's Scratchpad | View Weblogs ]
Oh! nice page. I had most of those problems. I wish Xorg7 postinst script would print something along the lines

In case of problems: lynx http://wiki.debian.org/Xorg69To7

just like udev warns you to purge the hotplug package...

[ Parent | Reply to this comment ]

Posted by tuani (202.159.xx.xx) on Mon 5 Feb 2007 at 03:31
[ Send Message ]
i have debian-sarge 14CD,
and I configuration server-miror like this.


1. copy 14 cd to direktory /debin/sarge

#cp -R /media/cdrom /debian/sarge
cd /debian/sarge

2. exstrack paket
# dpkg-scanpackages pool/contrib /dev/null | gzip -9c
> Packages.gz
# dpkg-scanpackages pool/main /dev/null | gzip -9c >
Packages.gz


cd /var/www
# ln -s /Debian/sarge

# vi /etc/apt/source.list
deb http://10.252.10.254 /sarge contrib main


testing
# apt-get update
not found paket

[ Parent | Reply to this comment ]

User Login

Username:

Password:

[ Advanced Login ]

Register Account

Quick Site Search