Re: debian testing amd64: X windows trouble after todays updates. (input events problem?)
Well, I am using debian testing on laptops since around 1999.
Stable always seems to be missing the one or other driver or
configuration for that, sometimes I have to fall back to unstable.
Anyway, what I do now - in fact, have already
done - is sending in a bug report. I still have my doubts that
desktop-base is the cause, since it really does not do very much. Only
the other packages are more unlikely to cause the effect.
Most of the time, such annoyances vanish after a few days, weeks or
months, until now I never had one like this that completely broke
usability. So maybe I'll try to get
desktop-base 5.0.6 somewhere, take a look at the differences and try
to figure out if something there might be the cause. Only I had to
switch back to a working machine now to do something productive.
For your problem: Normally I use dselect and there '=' to fix a package
whenever I get this dependency upgrade problem where someone put a
minor version/release number in a dependency that really does not work with
the continouus upgrades in testing or unstable. I must admit that
I never bothered to find out what underlying dpkg
functionality that one uses to do its work.
On Fri, 10 Dec 2010, Hugo Vanwoerkom wrote:
Peter Koellner wrote:
Well, I found the dpkg log with all the packages updated in that batch. one
of them or a combination has to be responsible. I guess it might be
desktop-base 6.0.2
Indeed, but what are you going to do? I do a backup before a dist-upgrade, so
I can fall back to something that works. But never doing an upgrade again is
not an option. Pinning never seems to work for me: right now I want to pin
mc, mondo and mindi, but it does not work, they get updated anyway:
Package: mc
Pin: version 4.6*
Pin-Priority: 1001
Package: wmtemp
Pin: version 0.0.6-3
Pin-Priority: 1001
Hugo
--
peter koellner <peter@asgalon.net>
Reply to: