| Summary: | Impossible to enter “/” (a slash) into the message field (and likely others too). | ||
|---|---|---|---|
| Product: | [Unmaintained] kopete | Reporter: | Navid Zamani <navid.zamani> |
| Component: | Chat Window | Assignee: | Kopete Developers <kopete-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | robert |
| Priority: | NOR | ||
| Version First Reported In: | 1.0.80 | ||
| Target Milestone: | --- | ||
| Platform: | Gentoo Packages | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Navid Zamani
2011-03-03 17:27:00 UTC
There is a possibility that KDE does this with certain keyboard layouts only, because it doesn’t track all modifier keys. (I only heard this, but it’s obviously a useful pointer.) Here, I have to type “Mod3-I” to enter “/”. “Mod3” is mapped to the physical key usually used for “Caps Lock”, and “I” is mapped to the physical key that is “S” in QWERT* layouts. It’s the popular German NEO 2.0 layout, you can see here: http://www.neo-layout.org/ I'm using opensuse 12.1 with: Qt: 4.7.4 KDE: 4.7.2 (4.7.2) "release 5" Kopete: 1.1.2 This bug can be marked as fixed. It work's as expected (also with german NEO layout). A friend with the same setup has confirmed this, too. The browser rekonq intodruced the same problem for its url lineedit. It would be cool to know which patch resolved this bug. I already did a close look on the source history starting November 2010, but didn't found anything obvious. :( (In reply to comment #2) > This bug can be marked as fixed. It work's as expected (also with german NEO > layout). A friend with the same setup has confirmed this, too. Interesting. It is indeed fixed and works here (4.7.3 / 1.1.3) too. I’m just as curious about when it got fixed. I had avoided using Kopete, as it got very annoying. I may go back… > It would be cool to know which patch resolved this bug. I already did a close > look on the source history starting November 2010, but didn't found anything > obvious. :( That’s because it happened somewhere between 4.7.0 and 4.7.2, as far as I can tell. I’m marking this as fixed, and will update the related Gentoo bug too. Thanks for the info, Robert. |