-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Ron,
Ron wrote: >> I can confirm the original report, and have been watching this bug >> number. I have had to pin version 0.7.4.1-4 to get correct support for > Actually I'm more inclined to simply close this bug as a problem on > the user site, since it doesn't actually appear to be a bug in the > package if we take the error message at face value. > > This is a pretty popular package, so I find it unlikely that this > report would lie dormant since october if there was a real problem > in it. I would appear to be a counterexample to the idea that no-one else had the problem, but I take the point. > However it would be nice to get an explanation from you or > the OP as to how you got your system into an inconsistent state if > it is more than an isolated event for a single user. My X setup is pretty plain vanilla. In the light of your comments I tried to install the new version of the package again, and now it is working as advertised, so yes, from my perspective the bug is now resolved, thanks. > My guess would be that you've previously pinned something else (or > not restarted X since updating it?) which is keeping your server at > an older version. The old package works with the old version, and > if you want to keep your system that way, that's what you'll have > to use. The current package works with the xserver that was in > unstable at the time it was uploaded (and indeed still works for > me with the xserver currently there too). Well I haven't pinned anything X related, or anything else I can think of for a while, so I don't think that's it. I restarted the Xserver about a dozen times, because I hadn't initially realised that the package was upgraded, so I tried altering the xorg.conf in many ways and restarting to fix the problem initially. It was after all that I checked the bugs database and found this, and just regressed the package and all was well. > If you can confirm that we can consider this done and leave an > explanation for anyone else that may stumble into the same issue. So, fixed for me, but if someone else (OP?) still has the problem I'm not sure how it resolved - presumably more recent dist-upgrades did it. Perhaps the whole thing was a result of some fluff left over from xfree86 in the big changeover. Thanks for your time and efforts! CT. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFF0fnu0SwfPjLnaZYRAlQ+AKD+LhGa0+qSeqXAvabTedvi2mvaygCgudpx K76Gc5AlkGyQlQCs47wyzs8= =jsGh -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
