Re: debian testing amd64: X windows trouble after todays updates. (input events problem?)
On 2010.12.10. 14:41, 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 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d04ed3d.50...@informatik.hu
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 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/alpine.osx.2.00.1012101654220@local.meinefc.de
Re: debian testing amd64: X windows trouble after todays updates. (input events problem?)
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 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/idti4b$jf...@dough.gmane.org
Re: debian testing amd64: X windows trouble after todays updates. (input events problem?)
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 -- peter koellner 2010-12-09 16:33:55 upgrade php-net-smtp 1.4.2-1 1.4.2-3 2010-12-09 16:33:57 upgrade php-soap 0.12.0-1 0.12.0-2 2010-12-09 16:33:58 upgrade isc-dhcp-client 4.1.1-P1-12 4.1.1-P1-15 2010-12-09 16:33:59 upgrade isc-dhcp-common 4.1.1-P1-12 4.1.1-P1-15 2010-12-09 16:34:01 upgrade libkrb5-dev 1.8.3+dfsg-2 1.8.3+dfsg-3 2010-12-09 16:34:02 upgrade krb5-multidev 1.8.3+dfsg-2 1.8.3+dfsg-3 2010-12-09 16:34:03 upgrade libk5crypto3 1.8.3+dfsg-2 1.8.3+dfsg-3 2010-12-09 16:34:04 upgrade libgssapi-krb5-2 1.8.3+dfsg-2 1.8.3+dfsg-3 2010-12-09 16:34:05 upgrade libkrb5-3 1.8.3+dfsg-2 1.8.3+dfsg-3 2010-12-09 16:34:07 upgrade libkrb5support0 1.8.3+dfsg-2 1.8.3+dfsg-3 2010-12-09 16:34:08 upgrade libgssrpc4 1.8.3+dfsg-2 1.8.3+dfsg-3 2010-12-09 16:34:09 upgrade libkdb5-4 1.8.3+dfsg-2 1.8.3+dfsg-3 2010-12-09 16:34:10 upgrade libkadm5srv-mit7 1.8.3+dfsg-2 1.8.3+dfsg-3 2010-12-09 16:34:11 upgrade libkadm5clnt-mit7 1.8.3+dfsg-2 1.8.3+dfsg-3 2010-12-09 16:34:12 upgrade desktop-base 5.0.6 6.0.2 2010-12-09 16:34:15 upgrade gthumb 3:2.11.5-3 3:2.11.5-4 2010-12-09 16:34:17 upgrade gthumb-data 3:2.11.5-3 3:2.11.5-4 2010-12-09 16:34:20 upgrade php5-cli 5.3.3-4 5.3.3-5 2010-12-09 16:34:21 upgrade php5-mysql 5.3.3-4 5.3.3-5 2010-12-09 16:34:22 upgrade php5-mcrypt 5.3.3-4 5.3.3-5 2010-12-09 16:34:24 upgrade php5-gd 5.3.3-4 5.3.3-5 2010-12-09 16:34:25 upgrade libapache2-mod-php5 5.3.3-4 5.3.3-5 2010-12-09 16:34:26 upgrade php5-common 5.3.3-4 5.3.3-5 2010-12-09 16:34:27 upgrade libasyncns0 0.3-1 0.3-1.1 2010-12-09 16:34:28 upgrade libwebkit-1.0-common 1.2.5-2 1.2.5-2.1 2010-12-09 16:34:30 upgrade libwebkit-1.0-2 1.2.5-2 1.2.5-2.1 2010-12-09 16:34:31 upgrade php-pear 5.3.3-4 5.3.3-5 2010-12-09 16:34:33 upgrade php5 5.3.3-4 5.3.3-5 2010-12-09 16:34:35 upgrade python2.5 2.5.5-10 2.5.5-11 2010-12-09 16:34:37 upgrade python2.5-minimal 2.5.5-10 2.5.5-11 2010-12-09 16:34:38 upgrade wpasupplicant 0.6.10-2 0.6.10-2.1 2010-12-09 16:34:40 upgrade dhcp3-client 4.1.1-P1-12 4.1.1-P1-15 2010-12-09 16:34:41 upgrade dhcp3-common 4.1.1-P1-12 4.1.1-P1-15
Re: debian testing amd64: X windows trouble after todays updates. (input events problem?)
On Thu, 9 Dec 2010, Peter Koellner wrote: I switched between xdm and gdm, and the problem with unresponsive window manager and locked in focused window seems to go away with that, though I am not totally sure. Today I am having the same effect after starting the gnome session via xdm, so the display manager has nothing to do with it. The input events seem to reach the window manager and gnome panels occasionally, but I have to try for minutes until I am able to switch focus, close a window or start another application. I don't see any error messages. This is an effect so bad I have not experienced ever with debian during the last twelve years or so. The gnome panel gets redrawn on schedule and I can use my application in keyboard focus, but mouse events seem to have difficulties. xpdf left a dysfunctional menu on the display, when I try to click the Quit menu entry the mouseclick event reaches the gnome panel below instead and minimizes the xpdf window. So I guess some part of the X input event handling got clobbered. -- peter koellner -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/alpine.deb.2.02.1012101401330.2...@kropotkin
