Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#2053 - The most recent Arch modification to the dbus package erases the keyboard buffer on shell logins
Attached to Project:
Arch Linux
Opened by Raven Morris (Samus_Aran) - Saturday, 22 January 2005, 05:42 GMT
Last edited by Jan de Groot (JGC) - Saturday, 22 January 2005, 12:57 GMT
Opened by Raven Morris (Samus_Aran) - Saturday, 22 January 2005, 05:42 GMT
Last edited by Jan de Groot (JGC) - Saturday, 22 January 2005, 12:57 GMT
|
DetailsThis bug is related to
The "dbus 0.23-2" upgrade from "dbus 0.23-1" has caused many undesired keyboard buffer issues. The issues are immediately gone if the dbus package is downgraded. During a full shell login in Xorg (in my case aterm, I don't think it matters, though), the keyboard buffer is erased when the initial command prompt appears. This means any typing performed during the login phase is lost. To clearly reproduce this bug: * Upgrade to "dbus 0.23-2" * Append a 2 second delay to your Bash login script e.g. # printf "\nsleep 2s\n">>~/.bash_login * Set your GNU Screen to do a full Bash login as its default function e.g. # printf "\nshell -/bin/bash\n">>~/.screenrc * Load GNU Screen e.g. # screen * Start a new console with Ctrl+A then C * Type text during the two second pause * Watch as it disappears * Downgrade to the previous release of dbus * Start a new console with Ctrl+A then C * Type text during the two second pause * Watch as it appears at the prompt I'm sure it can be reproduced with any old X terminal app that is set to do a "bash --login" or similar, I just happen to use GNU Screen and do the ^Ac method of getting a new console and then type my command while it is logging in 100+ times per day. |
This task depends upon
"xterm -fg grey -bg black -cr red -e bash --login"
And it is still 100% reproduceable. No need for GNU Screen, any Bash login will do it. I don't know if it affects other shells like tcsh, as I don't use any others. Okay, I just tried with the xterm and "tcsh -l" and the bug does not appear to be present like it is with "bash --login".
Anyhow, the cause of the bug is present in the "-1" to "-2" release. Whatever was changed should be put back.
The things that were changed are documented here:
http://www.beaglewiki.org/index.php/Starting%20a%20D-BUS%20Session%20Bus
I have 28 instances of "dbus-daemon-1 --fork --print-pid 8 --print-address 6 --session". Clearly it is starting this every single login shell session.
Also, I just realised that I was on the previous dbus release, so that would be why the file wasn't available. If dbus.sh was launching this background server every single login shell, then that surely is what was causing the keyboard buffer to be erased. I will upgrade my dbus and try deleting it.
The reason why I didn't notice this problem is because gnome-terminal doesn't use a login shell by default.