Bug#467076: ratpoison: still keyboard problems
* Sebastian Bremicker [EMAIL PROTECTED] [080225 07:46]: Up to now, since last reboot, that situation did not appear again. But I have another idea, maybe the cause is, that at the time the shortcut did not work I had a second X with ratpoison and mythtv at vt8 (which runs at 1024x768 for the tv-out) running. Sometimes when I open multiple gnome-terminals there, they are opened on vt7, maybe the keyboard focus went to vt8 and I did not recognize this. I will try to reproduce the situation with the two X. Any news about this? Hochachtungsvoll, Bernhard R. Link -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#467076: ratpoison: still keyboard problems
package ratpoison tags 467076 + unreproducible moreinfo severity 467076 serious thanks * Sebastian Bremicker [EMAIL PROTECTED] [080223 14:01]: All c-t keybindings stop working when I am in a Gnome or KDE program like gnome-terminal or sylpheed, when I quit this program, they work again. Do I understand you correctly that this happens both with 1.4.2 and the new 1.4.3 you reported against? (1.4.3 has the keyboard grabbing radically changed so when it happens with both this is quite an important piece of information). No, this phenomen seems to have occured only in 1.4.3. I will try to run some of the suggested tests tomorrow. I'm changing the severity of this bug to serious, so that 1.4.3 will not reach testing, thus. I've tried on an unstable machine and installed some kde and gnome programs (kpdf and sylpeed specifically), and C-t still works when those programs are started. (In other words: I'm unable to reproduce this). Could you try in an clean environment? For example a new user (gnome uses glib which disregards $HOME, so either the home dir needs cleaning or easier a new user), starting as that user only ratpoison (without gnome-session or whatever else might be running) and some program in question and look if that still happens. If yes, the same with all possible things switched off (some gnome stuff pulls in all nasty kind of stuff in, temporarily moving dbus and gnome session stuff out of /etc/X11/Xsession.d might help). Hochachtungsvoll, Bernhard R. Link -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#467076: ratpoison: still keyboard problems
Hi, Could you try in an clean environment? For example a new user (gnome uses glib which disregards $HOME, so either the home dir needs cleaning or easier a new user), starting as that user only ratpoison (without gnome-session or whatever else might be running) and some program in question and look if that still happens. You are right, the problems do not occur with a new user, even when I execute the same scripts like as my normal user. I am sorry, this may be just a local problem here. Kind regards, Sebastian Bremicker .ratpoisonrc Description: Binary data .sebremx Description: Binary data
Bug#467076: ratpoison: still keyboard problems
* Sebastian Bremicker [EMAIL PROTECTED] [080224 13:47]: Could you try in an clean environment? For example a new user (gnome uses glib which disregards $HOME, so either the home dir needs cleaning or easier a new user), starting as that user only ratpoison (without gnome-session or whatever else might be running) and some program in question and look if that still happens. You are right, the problems do not occur with a new user, even when I execute the same scripts like as my normal user. I am sorry, this may be just a local problem here. It's still nothing that should happen, so it would be nice if you could investigate what triggers this. (Perhaps some gconf setting, some theming set, or or or ...). Hochachtungsvoll, Bernhard R. Link -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#467076: ratpoison: still keyboard problems
Hi, It's still nothing that should happen, so it would be nice if you could investigate what triggers this. (Perhaps some gconf setting, some theming set, or or or ...). Up to now, since last reboot, that situation did not appear again. But I have another idea, maybe the cause is, that at the time the shortcut did not work I had a second X with ratpoison and mythtv at vt8 (which runs at 1024x768 for the tv-out) running. Sometimes when I open multiple gnome-terminals there, they are opened on vt7, maybe the keyboard focus went to vt8 and I did not recognize this. I will try to reproduce the situation with the two X. Kind regards, Sebastian Bremicker -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#467076: ratpoison: still keyboard problems
* Sebastian Bremicker [EMAIL PROTECTED] [080222 21:36]: I don't know whether it is an X.org or ratpoison problem, but for some months now I have serious usability problems with ratpoison keybindings. First there was this deadlock, which was an X error, after this still my key-combinations with ctrl-alt ceased working after using c-t : or !, now there is still one problem left, which seems to be reproducible: All c-t keybindings stop working when I am in a Gnome or KDE program like gnome-terminal or sylpheed, when I quit this program, they work again. Are there any tests I could run? Do I understand you correctly that this happens both with 1.4.2 and the new 1.4.3 you reported against? (1.4.3 has the keyboard grabbing radically changed so when it happens with both this is quite an important piece of information). Besides other newly introduces X errors an other cause for such behaviour I can imagine is that those programs change the keyboard mapping somehow (though I guessed this would be done by gnomish and kdeish window managers instead of the libraries, but I simply not know). Though even if that is the case, I can hardly imagine C-t being hit by that. (On second thought, perhaps when very strange things with the modifiers are done). Debugging something like that is quite hard. Some ideas: try to bind another top-level dir, like definekey top F8 echo catched (in your .ratpoisonrc or after C-t :) This should cause it to print a message catched in the message window each time you press F8. It would be intresting if that behviour survives starting a Gnome or KDE window. If that works, one could try to change the prefix key from C-t to some key without modifiers (for example using escape F9) and testing if that works (to find out if it are really modifiers, or grabbing the key while waiting for subsequent keys fails) Also intresting would be xtrace's output on ratpoison while that happens and on those programs. Though that would most likely be veeery long, a bit tricky to start, and questionable if it gives that much information. (Especially as the more sophisticated xkb extension is not yet implemented in xtrace, though one should still see what ends up in ratpoison) Hochachtungsvoll, Bernhard R. Link -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#467076: ratpoison: still keyboard problems
Hi, All c-t keybindings stop working when I am in a Gnome or KDE program like gnome-terminal or sylpheed, when I quit this program, they work again. Do I understand you correctly that this happens both with 1.4.2 and the new 1.4.3 you reported against? (1.4.3 has the keyboard grabbing radically changed so when it happens with both this is quite an important piece of information). No, this phenomen seems to have occured only in 1.4.3. I will try to run some of the suggested tests tomorrow. Kind regards, Sebastian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#467076: ratpoison: still keyboard problems
Package: ratpoison Version: 1.4.3-1 Severity: normal Hi, I don't know whether it is an X.org or ratpoison problem, but for some months now I have serious usability problems with ratpoison keybindings. First there was this deadlock, which was an X error, after this still my key-combinations with ctrl-alt ceased working after using c-t : or !, now there is still one problem left, which seems to be reproducible: All c-t keybindings stop working when I am in a Gnome or KDE program like gnome-terminal or sylpheed, when I quit this program, they work again. Are there any tests I could run? Regards Sebastian -- System Information: Debian Release: lenny/sid APT prefers proposed-updates APT policy: (500, 'proposed-updates'), (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.24-1-686 (SMP w/1 CPU core) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages ratpoison depends on: ii libc6 2.7-8 GNU C Library: Shared libraries ii libreadline5 5.2-3 GNU readline and history libraries ii libx11-6 2:1.0.3-7 X11 client-side library ii libxinerama1 1:1.0.2-1 X11 Xinerama extension library ii libxtst6 2:1.0.3-1 X11 Testing -- Resource extension Versions of packages ratpoison recommends: ii 9menu 1.8-1.1 Creates X menus from the shell ii gnome-terminal [x-termi 2.18.4-1 The GNOME 2 terminal emulator appl ii konsole [x-terminal-emu 4:3.5.8.dfsg.1-7 X terminal emulator for KDE ii menu2.1.37 generates programs menu for all me ii xterm [x-terminal-emula 232-1X terminal emulator -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
