[arch-general] Error updating related to pygobject, pygobject-devel, Python, and Python2
It would seem I have something misconfigured on my machine. I haven't noticed anything on the mailing list or on the Arch news about this, checked the bug tracker and followed the links to the Python mailing list, and I'm still a little confused. Below is an example of what I get back from pacman -Sy and pacman -Su, the rest is in a pastebin at http://pastebin.com/3dBxsGvE. myra@gandalf ../repos/extra-x86_64]:pacsu (equivalent to pacman -Su) :: Starting full system upgrade... warning: pacman: local (4.0.0rc1-1) is newer than core (3.5.4-4) :: Replace pygobject with extra/python2-gobject2? [Y/n] y :: Replace pygobject with extra/python2-gtkhtml2? [Y/n] y :: Replace pygobject with extra/python2-gtkspell? [Y/n] y :: Replace pygobject with extra/python2-httplib2? [Y/n] y :: Replace pygobject with extra/python2-libgnome? [Y/n] y :: Replace pygobject with extra/python2-nose? [Y/n] y :: Replace pygobject with extra/python2-numpy? [Y/n] y :: Replace pygobject with extra/python2-pip? [Y/n] y :: Replace pygobject with extra/python2-pyopenssl? [Y/n] y :: Replace pygobject with extra/python2-pyqt? [Y/n] y --- adnauseum resolving dependencies... looking for inter-conflicts... error: unresolvable package conflicts detected error: failed to prepare transaction (conflicting dependencies) :: python2-nose and python-nose are in conflict The adnauseum got 1455 line of repetition through pygobject and pygobject-devel. Based on the Python mailing list referenced in FS25747 on the bug tracker, I'm not sure what to do next. You'll notice in the pastebin I stopped hitting the Y and just pressed enter (yes I really did that). No problems prior to today, but it seems as though I've borked something up. Any suggestions would be appreciated. Myra -- Life's fun when your sick and psychotic!
Re: [arch-general] Down doesn't stick
On Fri, Sep 2, 2011 at 10:13 PM, Manolo Martínez wrote: > I use arch + openbox and I don't. > Thanks. The xset woraround doesn't solve it all. evince refuses to comply, although gvim works fine Jorge
Re: [arch-general] Down doesn't stick
I use arch + openbox and I don't. M On 09/02/11 at 09:16pm, Jorge Almeida wrote: > On Fri, Sep 2, 2011 at 8:41 PM, Patrick Burroughs > wrote: > > On Fri, Sep 2, 2011 at 12:26, Jorge Almeida wrote: > >> Good point. In a TTY there is no problem. It's an X thing. Maybe I > >> should try the openbox list. Google shows nothing. > > > > You might try `xset r 116` — that will explicitly enable autorepeat > > for the Down key, if it was somehow disabled. > > > Right. It does the job. I guess I'll put it in the openbox startup > file. Somehow it seems strange that openbox is responsable for this, I > would first suspect some driver or something like that. It would be > interesting to know whether somebody else who uses arch+openbox has > this problem. > > Thanks > > Jorge --
Re: [arch-general] [signoff] linux-3.0.4-1
Excerpts from Fons Adriaensen's message of 2011-09-01 11:14:40 +0200: > On Wed, Aug 31, 2011 at 10:49:09AM -0500, David C. Rankin wrote: > > On 08/30/2011 04:38 AM, Tobias Powalowski wrote: > >> Latest kernel is in testing, > >> please signoff for both arches > >> > >> greetings > >> tpowa > > > > Signoff i686 :) > > Does this mean that the 'swappiness' problem has been solved, > or there is a workaround for it ? > > Caio, It seems like there's a fix available, but I'm not sure it's part of 3.0.4. See the last couple of comments there: https://bugzilla.kernel.org/show_bug.cgi?id=40262 Regards, Philipp
Re: [arch-general] Down doesn't stick
On Fri, Sep 2, 2011 at 8:41 PM, Patrick Burroughs wrote: > On Fri, Sep 2, 2011 at 12:26, Jorge Almeida wrote: >> Good point. In a TTY there is no problem. It's an X thing. Maybe I >> should try the openbox list. Google shows nothing. > > You might try `xset r 116` — that will explicitly enable autorepeat > for the Down key, if it was somehow disabled. > Right. It does the job. I guess I'll put it in the openbox startup file. Somehow it seems strange that openbox is responsable for this, I would first suspect some driver or something like that. It would be interesting to know whether somebody else who uses arch+openbox has this problem. Thanks Jorge
Re: [arch-general] Down doesn't stick
On Fri, Sep 2, 2011 at 12:26, Jorge Almeida wrote: > Good point. In a TTY there is no problem. It's an X thing. Maybe I > should try the openbox list. Google shows nothing. You might try `xset r 116` — that will explicitly enable autorepeat for the Down key, if it was somehow disabled. ~Celti
Re: [arch-general] Down doesn't stick
On Fri, Sep 2, 2011 at 2:23 PM, Jari Vetoniemi wrote: No GTK problem. It happens with gvim (gtk) but also with Chromium (don't know which tk it uses) and vim in an xterm > Also, going to add.. Does this happen in virtual terminals (TTYs), > switch to one and try doing `less textfile` and hold the down key. > Good point. In a TTY there is no problem. It's an X thing. Maybe I should try the openbox list. Google shows nothing. Thanks Jorge
Re: [arch-general] Down doesn't stick
Also, going to add.. Does this happen in virtual terminals (TTYs), switch to one and try doing `less textfile` and hold the down key. 2011/9/2 Jari Vetoniemi : > Nothing really stands out on your update, only openbox. Does this > happen in every applications? So it's not a GTK or Qt bug? > Do you get any useful output by testing holding down, down key in `xev`? > > 2011/9/2 Jorge Almeida : >> On Fri, Sep 2, 2011 at 1:09 PM, Jari Vetoniemi wrote: >>> Could you check that you have `xset r` enabled? Does any key repeat, >>> if you hold them? >> >> $ xset q >> Keyboard Control: >> auto repeat: on key click percent: 0 LED mask: >> XKB indicators: >> 00: Caps Lock: off 01: Num Lock: off 02: Scroll Lock: off >> 03: Compose: off 04: Kana: off 05: Sleep: off >> 06: Suspend: off 07: Mute: off 08: Misc: off >> 09: Mail: off 10: Charging: off 11: Shift Lock: off >> 12: Group 2: off 13: Mouse Keys: off >> auto repeat delay: 660 repeat rate: 25 >> auto repeating keys: 00ffdbff >> faefffefefff >> dfff >> fff7 >> bell percent: 50 bell pitch: 400 bell duration: 100 >> Pointer Control: >> acceleration: 2/1 threshold: 4 >> Screen Saver: >> prefer blanking: yes allow exposures: yes >> timeout: 0 cycle: 600 >> Colors: >> default colormap: 0x20 BlackPixel: 0x0 WhitePixel: 0xff >> Font Path: >> /usr/share/fonts/misc/,/usr/share/fonts/TTF/,/usr/share/fonts/Type1/,/usr/share/fonts/100dpi/,/usr/share/fonts/75dpi/,built-ins >> DPMS (Energy Star): >> Standby: 600 Suspend: 600 Off: 600 >> DPMS is Disabled >> >> >> Keeping 'a' pressed in a text editor or xterm produces lots of a's. >> And Up works, as said. >> >>> Maybe it's window manager behavior like mentioned above, (used for >>> hotkey or hotkey combination for perhaps and grabs the key which would >>> be IMO bad) >>> >> I have a few shortcuts set up, but I didn't change anything, and they >> still work, anyway. Other than that, I can't imagine what can affect >> Down and not Up. >> >>> Anyways sounds weird and can't really pinpoint unless more information >>> is given and what packages did you upgrade. >>> >> >> OK, here it goes. >> Thanks >> >> [2012-08-12 00:21] upgraded netcfg (2.6.6-1 -> 2.6.7-1) >> [2011-08-31 16:03] Running 'pacman -Syuw' >> [2011-08-31 16:03] synchronizing package lists >> [2011-08-31 16:03] starting full system upgrade >> [2011-08-31 16:58] Running 'pacman -Su' >> [2011-08-31 16:58] warning: /etc/makepkg.conf installed as >> /etc/makepkg.conf.pacnew >> [2011-08-31 16:58] upgraded pacman (3.5.4-2 -> 3.5.4-4) >> [2011-08-31 16:58] Running 'pacman -Su' >> [2011-08-31 16:58] starting full system upgrade >> [2011-08-31 16:59] upgraded linux-api-headers (2.6.39.1-1 -> 3.0.1-1) >> [2011-08-31 17:00] Generating locales... >> [2011-08-31 17:00] en_US.UTF-8... done >> [2011-08-31 17:00] en_US.ISO-8859-1... done >> [2011-08-31 17:00] pt_PT.UTF-8... done >> [2011-08-31 17:00] pt_PT.ISO-8859-1... done >> [2011-08-31 17:00] pt_PT.ISO-8859-15@euro... done >> [2011-08-31 17:00] Generation complete. >> [2011-08-31 17:00] upgraded glibc (2.14-4 -> 2.14-5) >> [2011-08-31 17:00] upgraded gcc-libs (4.6.1-2 -> 4.6.1-4) >> [2011-08-31 17:00] upgraded acpitool (0.5.1-2 -> 0.5.1-3) >> [2011-08-31 17:00] upgraded alsa-utils (1.0.24.2-2 -> 1.0.24.2-3) >> [2011-08-31 17:00] upgraded audacious-plugins (3.0-6 -> 3.0.2-1) >> [2011-08-31 17:00] upgraded audacious (3.0-5 -> 3.0.2-1) >> [2011-08-31 17:00] upgraded avahi (0.6.30-4 -> 0.6.30-5) >> [2011-08-31 17:00] upgraded zlib (1.2.5-3 -> 1.2.5-4) >> [2011-08-31 17:00] upgraded binutils (2.21.1-1 -> 2.21.1-2) >> [2011-08-31 17:00] upgraded run-parts (3.4.4-1 -> 4.0.2-1) >> [2011-08-31 17:00] upgraded ca-certificates (20110421-3 -> 20110502-1) >> [2011-08-31 17:00] upgraded ca-certificates-java (20110426-4 -> 20110816-1) >> [2011-08-31 17:00] upgraded gmp (5.0.2-2 -> 5.0.2-3) >> [2011-08-31 17:00] upgraded nettle (2.1-1 -> 2.2-1) >> [2011-08-31 17:00] upgraded gnutls (2.12.7-2 -> 3.0.1-1) >> [2011-08-31 17:00] upgraded libcups (1.4.8-1 -> 1.4.8-2) >> [2011-08-31 17:00] upgraded gdk-pixbuf2 (2.23.5-1 -> 2.24.0-1) >> [2011-08-31 17:00] upgraded gtk-update-icon-cache (2.24.5-3 -> 2.24.6-1) >> [2011-08-31 17:00] upgraded gtk2 (2.24.5-3 -> 2.24.6-1) >> [2011-08-31 17:00] upgraded nspr (4.8.8-1 -> 4.8.9-1) >> [2011-08-31 17:00] upgraded nss (3.12.10-1 -> 3.12.11-3) >> [2011-08-31 17:00] upgraded chromium (13.0.782.112-2 -> 13.0.782.218-1) >> [2011-08-31 17:00] upgraded isl (0.06-1 -> 0.07-1) >> [2011-08-31 17:00] upgraded cloog (0.16.2-1 -> 0.16.3-1) >> [2011-08-31 17:00] upgraded dash (0.5.7-1 -> 0.5.7-2) >> [2011-08-31 17:00] upgraded device-mapper (2.02.86-1 -> 2.02.88-1) >> [2011-08-31 17:00] upgraded devtools (0.9.23-1 -> 0.9.27-1) >> [2011-08-31 17:
Re: [arch-general] Down doesn't stick
Nothing really stands out on your update, only openbox. Does this happen in every applications? So it's not a GTK or Qt bug? Do you get any useful output by testing holding down, down key in `xev`? 2011/9/2 Jorge Almeida : > On Fri, Sep 2, 2011 at 1:09 PM, Jari Vetoniemi wrote: >> Could you check that you have `xset r` enabled? Does any key repeat, >> if you hold them? > > $ xset q > Keyboard Control: > auto repeat: on key click percent: 0 LED mask: > XKB indicators: > 00: Caps Lock: off 01: Num Lock: off 02: Scroll Lock: off > 03: Compose: off 04: Kana: off 05: Sleep: off > 06: Suspend: off 07: Mute: off 08: Misc: off > 09: Mail: off 10: Charging: off 11: Shift Lock: off > 12: Group 2: off 13: Mouse Keys: off > auto repeat delay: 660 repeat rate: 25 > auto repeating keys: 00ffdbff > faefffefefff > dfff > fff7 > bell percent: 50 bell pitch: 400 bell duration: 100 > Pointer Control: > acceleration: 2/1 threshold: 4 > Screen Saver: > prefer blanking: yes allow exposures: yes > timeout: 0 cycle: 600 > Colors: > default colormap: 0x20 BlackPixel: 0x0 WhitePixel: 0xff > Font Path: > /usr/share/fonts/misc/,/usr/share/fonts/TTF/,/usr/share/fonts/Type1/,/usr/share/fonts/100dpi/,/usr/share/fonts/75dpi/,built-ins > DPMS (Energy Star): > Standby: 600 Suspend: 600 Off: 600 > DPMS is Disabled > > > Keeping 'a' pressed in a text editor or xterm produces lots of a's. > And Up works, as said. > >> Maybe it's window manager behavior like mentioned above, (used for >> hotkey or hotkey combination for perhaps and grabs the key which would >> be IMO bad) >> > I have a few shortcuts set up, but I didn't change anything, and they > still work, anyway. Other than that, I can't imagine what can affect > Down and not Up. > >> Anyways sounds weird and can't really pinpoint unless more information >> is given and what packages did you upgrade. >> > > OK, here it goes. > Thanks > > [2012-08-12 00:21] upgraded netcfg (2.6.6-1 -> 2.6.7-1) > [2011-08-31 16:03] Running 'pacman -Syuw' > [2011-08-31 16:03] synchronizing package lists > [2011-08-31 16:03] starting full system upgrade > [2011-08-31 16:58] Running 'pacman -Su' > [2011-08-31 16:58] warning: /etc/makepkg.conf installed as > /etc/makepkg.conf.pacnew > [2011-08-31 16:58] upgraded pacman (3.5.4-2 -> 3.5.4-4) > [2011-08-31 16:58] Running 'pacman -Su' > [2011-08-31 16:58] starting full system upgrade > [2011-08-31 16:59] upgraded linux-api-headers (2.6.39.1-1 -> 3.0.1-1) > [2011-08-31 17:00] Generating locales... > [2011-08-31 17:00] en_US.UTF-8... done > [2011-08-31 17:00] en_US.ISO-8859-1... done > [2011-08-31 17:00] pt_PT.UTF-8... done > [2011-08-31 17:00] pt_PT.ISO-8859-1... done > [2011-08-31 17:00] pt_PT.ISO-8859-15@euro... done > [2011-08-31 17:00] Generation complete. > [2011-08-31 17:00] upgraded glibc (2.14-4 -> 2.14-5) > [2011-08-31 17:00] upgraded gcc-libs (4.6.1-2 -> 4.6.1-4) > [2011-08-31 17:00] upgraded acpitool (0.5.1-2 -> 0.5.1-3) > [2011-08-31 17:00] upgraded alsa-utils (1.0.24.2-2 -> 1.0.24.2-3) > [2011-08-31 17:00] upgraded audacious-plugins (3.0-6 -> 3.0.2-1) > [2011-08-31 17:00] upgraded audacious (3.0-5 -> 3.0.2-1) > [2011-08-31 17:00] upgraded avahi (0.6.30-4 -> 0.6.30-5) > [2011-08-31 17:00] upgraded zlib (1.2.5-3 -> 1.2.5-4) > [2011-08-31 17:00] upgraded binutils (2.21.1-1 -> 2.21.1-2) > [2011-08-31 17:00] upgraded run-parts (3.4.4-1 -> 4.0.2-1) > [2011-08-31 17:00] upgraded ca-certificates (20110421-3 -> 20110502-1) > [2011-08-31 17:00] upgraded ca-certificates-java (20110426-4 -> 20110816-1) > [2011-08-31 17:00] upgraded gmp (5.0.2-2 -> 5.0.2-3) > [2011-08-31 17:00] upgraded nettle (2.1-1 -> 2.2-1) > [2011-08-31 17:00] upgraded gnutls (2.12.7-2 -> 3.0.1-1) > [2011-08-31 17:00] upgraded libcups (1.4.8-1 -> 1.4.8-2) > [2011-08-31 17:00] upgraded gdk-pixbuf2 (2.23.5-1 -> 2.24.0-1) > [2011-08-31 17:00] upgraded gtk-update-icon-cache (2.24.5-3 -> 2.24.6-1) > [2011-08-31 17:00] upgraded gtk2 (2.24.5-3 -> 2.24.6-1) > [2011-08-31 17:00] upgraded nspr (4.8.8-1 -> 4.8.9-1) > [2011-08-31 17:00] upgraded nss (3.12.10-1 -> 3.12.11-3) > [2011-08-31 17:00] upgraded chromium (13.0.782.112-2 -> 13.0.782.218-1) > [2011-08-31 17:00] upgraded isl (0.06-1 -> 0.07-1) > [2011-08-31 17:00] upgraded cloog (0.16.2-1 -> 0.16.3-1) > [2011-08-31 17:00] upgraded dash (0.5.7-1 -> 0.5.7-2) > [2011-08-31 17:00] upgraded device-mapper (2.02.86-1 -> 2.02.88-1) > [2011-08-31 17:00] upgraded devtools (0.9.23-1 -> 0.9.27-1) > [2011-08-31 17:00] upgraded diffutils (3.0-2 -> 3.1-1) > [2011-08-31 17:00] upgraded djview4 (4.7-1 -> 4.8-1) > [2011-08-31 17:00] upgraded eject (2.1.5-5 -> 2.1.5-7) > [2011-08-31 17:00] warning: /etc/fstab installed as /etc/fstab.pacnew > [2011-08-31 17:00] groupadd: GID '19' alr
Re: [arch-general] emacs-color-theme: please use a snapshot
Am 29.08.2011 20:58, schrieb Eric Bélanger: On Sun, Aug 28, 2011 at 10:11 AM, XeCycle wrote: Hope I'm not disturbing~ But I don't know whether this worth a bug report. The package `emacs-color-theme' uses the stable release, released in 2006. In 2007, there's a commit fixing a bug (for me, the bug causes conflict with Gnus), but the upstream didn't release a new version since then. So I would suggest on using a snapshot version --- I fixed that bug myself. Following is more about that bug and how I fixed it: Function `replace-in-string' is provided in XEmacs but not GNU Emacs, so the author of color-theme defined his own. Yes, he checks whether the function exists. Gnus also defined one, but the name is `mm-replace-in-string'. Gnus checks whether `replace-in-string' is present, and if it does, the `mm-' is just an alias to that. All right, Eh? But the author of color-theme defined the function different from XEmacs did. So Gnus was confused, then it complained about something like "wrong number of arguments" when using it --- for example, when EasyPG is trying to verify a PGP/MIME signature. I fixed that by renaming the defun in color-theme.el to `color-theme-replace-in-string', by adding a sed line in the build() function before the compilation. You should submit a bug report to make sure the maintainer is aware of this. -- Carl Lei (XeCycle) Department of Physics, Shanghai Jiao Tong University OpenPGP public key: 7795E591 Fingerprint: 1FB6 7F1F D45D F681 C845 27F7 8D71 8EC4 7795 E591 Applied in -6. But Eric's hint was correct for future requests like this, I read this list very rarely. Regards Stefan
Re: [arch-general] Down doesn't stick
On Fri, Sep 2, 2011 at 1:09 PM, Jari Vetoniemi wrote: > Could you check that you have `xset r` enabled? Does any key repeat, > if you hold them? $ xset q Keyboard Control: auto repeat: onkey click percent: 0LED mask: XKB indicators: 00: Caps Lock: off01: Num Lock:off02: Scroll Lock: off 03: Compose: off04: Kana:off05: Sleep: off 06: Suspend: off07: Mute:off08: Misc:off 09: Mail:off10: Charging:off11: Shift Lock: off 12: Group 2: off13: Mouse Keys: off auto repeat delay: 660repeat rate: 25 auto repeating keys: 00ffdbff faefffefefff dfff fff7 bell percent: 50bell pitch: 400bell duration: 100 Pointer Control: acceleration: 2/1threshold: 4 Screen Saver: prefer blanking: yesallow exposures: yes timeout: 0cycle: 600 Colors: default colormap: 0x20BlackPixel: 0x0WhitePixel: 0xff Font Path: /usr/share/fonts/misc/,/usr/share/fonts/TTF/,/usr/share/fonts/Type1/,/usr/share/fonts/100dpi/,/usr/share/fonts/75dpi/,built-ins DPMS (Energy Star): Standby: 600Suspend: 600Off: 600 DPMS is Disabled Keeping 'a' pressed in a text editor or xterm produces lots of a's. And Up works, as said. > Maybe it's window manager behavior like mentioned above, (used for > hotkey or hotkey combination for perhaps and grabs the key which would > be IMO bad) > I have a few shortcuts set up, but I didn't change anything, and they still work, anyway. Other than that, I can't imagine what can affect Down and not Up. > Anyways sounds weird and can't really pinpoint unless more information > is given and what packages did you upgrade. > OK, here it goes. Thanks [2012-08-12 00:21] upgraded netcfg (2.6.6-1 -> 2.6.7-1) [2011-08-31 16:03] Running 'pacman -Syuw' [2011-08-31 16:03] synchronizing package lists [2011-08-31 16:03] starting full system upgrade [2011-08-31 16:58] Running 'pacman -Su' [2011-08-31 16:58] warning: /etc/makepkg.conf installed as /etc/makepkg.conf.pacnew [2011-08-31 16:58] upgraded pacman (3.5.4-2 -> 3.5.4-4) [2011-08-31 16:58] Running 'pacman -Su' [2011-08-31 16:58] starting full system upgrade [2011-08-31 16:59] upgraded linux-api-headers (2.6.39.1-1 -> 3.0.1-1) [2011-08-31 17:00] Generating locales... [2011-08-31 17:00] en_US.UTF-8... done [2011-08-31 17:00] en_US.ISO-8859-1... done [2011-08-31 17:00] pt_PT.UTF-8... done [2011-08-31 17:00] pt_PT.ISO-8859-1... done [2011-08-31 17:00] pt_PT.ISO-8859-15@euro... done [2011-08-31 17:00] Generation complete. [2011-08-31 17:00] upgraded glibc (2.14-4 -> 2.14-5) [2011-08-31 17:00] upgraded gcc-libs (4.6.1-2 -> 4.6.1-4) [2011-08-31 17:00] upgraded acpitool (0.5.1-2 -> 0.5.1-3) [2011-08-31 17:00] upgraded alsa-utils (1.0.24.2-2 -> 1.0.24.2-3) [2011-08-31 17:00] upgraded audacious-plugins (3.0-6 -> 3.0.2-1) [2011-08-31 17:00] upgraded audacious (3.0-5 -> 3.0.2-1) [2011-08-31 17:00] upgraded avahi (0.6.30-4 -> 0.6.30-5) [2011-08-31 17:00] upgraded zlib (1.2.5-3 -> 1.2.5-4) [2011-08-31 17:00] upgraded binutils (2.21.1-1 -> 2.21.1-2) [2011-08-31 17:00] upgraded run-parts (3.4.4-1 -> 4.0.2-1) [2011-08-31 17:00] upgraded ca-certificates (20110421-3 -> 20110502-1) [2011-08-31 17:00] upgraded ca-certificates-java (20110426-4 -> 20110816-1) [2011-08-31 17:00] upgraded gmp (5.0.2-2 -> 5.0.2-3) [2011-08-31 17:00] upgraded nettle (2.1-1 -> 2.2-1) [2011-08-31 17:00] upgraded gnutls (2.12.7-2 -> 3.0.1-1) [2011-08-31 17:00] upgraded libcups (1.4.8-1 -> 1.4.8-2) [2011-08-31 17:00] upgraded gdk-pixbuf2 (2.23.5-1 -> 2.24.0-1) [2011-08-31 17:00] upgraded gtk-update-icon-cache (2.24.5-3 -> 2.24.6-1) [2011-08-31 17:00] upgraded gtk2 (2.24.5-3 -> 2.24.6-1) [2011-08-31 17:00] upgraded nspr (4.8.8-1 -> 4.8.9-1) [2011-08-31 17:00] upgraded nss (3.12.10-1 -> 3.12.11-3) [2011-08-31 17:00] upgraded chromium (13.0.782.112-2 -> 13.0.782.218-1) [2011-08-31 17:00] upgraded isl (0.06-1 -> 0.07-1) [2011-08-31 17:00] upgraded cloog (0.16.2-1 -> 0.16.3-1) [2011-08-31 17:00] upgraded dash (0.5.7-1 -> 0.5.7-2) [2011-08-31 17:00] upgraded device-mapper (2.02.86-1 -> 2.02.88-1) [2011-08-31 17:00] upgraded devtools (0.9.23-1 -> 0.9.27-1) [2011-08-31 17:00] upgraded diffutils (3.0-2 -> 3.1-1) [2011-08-31 17:00] upgraded djview4 (4.7-1 -> 4.8-1) [2011-08-31 17:00] upgraded eject (2.1.5-5 -> 2.1.5-7) [2011-08-31 17:00] warning: /etc/fstab installed as /etc/fstab.pacnew [2011-08-31 17:00] groupadd: GID '19' already exists [2011-08-31 17:00] groupadd: GID '33' already exists [2011-08-31 17:00] useradd: group 'http' does not exist [2011-08-31 17:00] chage: user 'http' does not exist in /etc/passwd [2011-08-31 17:00] upgraded filesystem (2011.04-1 -> 2011.08-1) [2011-08-31 17:00] upgraded util-linux (2.19.1-2 -> 2.19.1-3) [2011-08-31 17:00] upgraded fakeroot (1.16-1 -> 1.17-1) [2011-08-31 17:01]
Re: [arch-general] Down doesn't stick
On Fri, Sep 2, 2011 at 12:48 PM, Jesse Jaara wrote: > Check the keyboard settings from KDE/Gnome/Xfce control panel, > if you us one of them. Don't know how the keyboard settings > are handled on window-managers and such. > > Nope, I'm a openbox user. Whatever settings are active must come from X. Anyway, they are the defaults, except for the kind of customization that is taken care by xmodmap Thanks J.
Re: [arch-general] Down doesn't stick
Could you check that you have `xset r` enabled? Does any key repeat, if you hold them? Maybe it's window manager behavior like mentioned above, (used for hotkey or hotkey combination for perhaps and grabs the key which would be IMO bad) Anyways sounds weird and can't really pinpoint unless more information is given and what packages did you upgrade. 2011/9/2 Jesse Jaara : > 02.09.2011 14:43, Jorge Almeida kirjoitti: >> Two days ago I did a one week -due general upgrading. After rebooting, >> the "Down" key changed its usual behavior: keeping the key pressed >> should keep producing Down events (I use it sometimes to scroll a >> google page without the mouse, or to move down across a text editing >> page). Now, it only sends one event. If I want to scroll down two >> lines I have to press twice. The Up key still has the usual behavior. >> I checked with xev that events are not being sent (i.e., they are not >> just being ignored). I suspected a keyboard hw probem, and so I used >> xmodmap to map another key (AltGr, right next to the space bar) to be >> another Down. It worked well yesterday, but today, after booting, new >> and old key have both the same strange behavior. >> >> I have no idea what package may be causing this... >> >> Jorge Almeida > Check the keyboard settings from KDE/Gnome/Xfce control panel, > if you us one of them. Don't know how the keyboard settings > are handled on window-managers and such. > >
Re: [arch-general] Down doesn't stick
02.09.2011 14:43, Jorge Almeida kirjoitti: > Two days ago I did a one week -due general upgrading. After rebooting, > the "Down" key changed its usual behavior: keeping the key pressed > should keep producing Down events (I use it sometimes to scroll a > google page without the mouse, or to move down across a text editing > page). Now, it only sends one event. If I want to scroll down two > lines I have to press twice. The Up key still has the usual behavior. > I checked with xev that events are not being sent (i.e., they are not > just being ignored). I suspected a keyboard hw probem, and so I used > xmodmap to map another key (AltGr, right next to the space bar) to be > another Down. It worked well yesterday, but today, after booting, new > and old key have both the same strange behavior. > > I have no idea what package may be causing this... > > Jorge Almeida Check the keyboard settings from KDE/Gnome/Xfce control panel, if you us one of them. Don't know how the keyboard settings are handled on window-managers and such. signature.asc Description: OpenPGP digital signature
[arch-general] Down doesn't stick
Two days ago I did a one week -due general upgrading. After rebooting, the "Down" key changed its usual behavior: keeping the key pressed should keep producing Down events (I use it sometimes to scroll a google page without the mouse, or to move down across a text editing page). Now, it only sends one event. If I want to scroll down two lines I have to press twice. The Up key still has the usual behavior. I checked with xev that events are not being sent (i.e., they are not just being ignored). I suspected a keyboard hw probem, and so I used xmodmap to map another key (AltGr, right next to the space bar) to be another Down. It worked well yesterday, but today, after booting, new and old key have both the same strange behavior. I have no idea what package may be causing this... Jorge Almeida
