https://bugs.kde.org/show_bug.cgi?id=342735
--- Comment #9 from Andrey Grozin ---
Created attachment 157720
--> https://bugs.kde.org/attachment.cgi?id=157720=edit
bug.dvi in okular
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=432818
Andrey changed:
What|Removed |Added
CC||vkra...@kde.org
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=467884
Andrey Reeshkov changed:
What|Removed |Added
CC||reesh...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=467884
Bug ID: 467884
Summary: Unable manage added bluetooth device in mobile
controls of settings
Classification: I don't know
Product: kde
Version: unspecified
Platform: Other
https://bugs.kde.org/show_bug.cgi?id=432818
--- Comment #15 from Andrey ---
XKB_* vars are parsed by libxkbcommon itself and have nothing to do with
Plasma.
KWIN_XKB_DEFAULT_KEYMAP is from KWin but I'm not sure if it's necessary.
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=447206
Andrey changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=432818
Andrey changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=447206
Andrey changed:
What|Removed |Added
CC||butir...@gmail.com
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=432818
--- Comment #12 from Andrey ---
As said above, XKB custom configuration should get applied having you put it in
proper place in HOME, and other mentioned conditions met. Even on Wayland.
That might need recent KWin enough (I'm not sure) - can you test
https://bugs.kde.org/show_bug.cgi?id=432818
--- Comment #9 from Andrey ---
Does your custom config get applied at least?
There is a note in the docs:
"Note: Where libxkbcommon runs in a privileged context, only the system
(datadir) path is available."
I remember there was a patch merg
https://bugs.kde.org/show_bug.cgi?id=432818
--- Comment #8 from Andrey ---
AFAIK, there was no progress and no is planned.
libxkbregistry doesn't give you any extra functionality, it's just for
developer convenience.
Do you know you can place your stuff in ~/.xkb, $XDG_CONFIG_HOME/xkb
https://bugs.kde.org/show_bug.cgi?id=467519
--- Comment #5 from Andrey Fedoseev ---
(In reply to David from comment #4)
> You can find out if you are using an input method like Fcitx by typing "echo
> $XMODIFIERS" in Konsole. If you have an input method installed it would look
https://bugs.kde.org/show_bug.cgi?id=467519
--- Comment #3 from Andrey Fedoseev ---
(In reply to David from comment #1)
> Could you mention some details about your input settings?
>
> Keyboard layout?
I use English and Russian keyboard layouts.
> Input method used (Ibus, FCITX)
https://bugs.kde.org/show_bug.cgi?id=467519
--- Comment #2 from Andrey Fedoseev ---
Created attachment 157487
--> https://bugs.kde.org/attachment.cgi?id=157487=edit
KDE Locale Settings
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=467519
Bug ID: 467519
Summary: Keyboard input doesn't work in plasmoids / plasma
widgets
Classification: Plasma
Product: plasmashell
Version: 5.27.2
Platform: Neon
https://bugs.kde.org/show_bug.cgi?id=466073
Andrey changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=444569
Andrey changed:
What|Removed |Added
Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas
|ma
https://bugs.kde.org/show_bug.cgi?id=466053
Andrey changed:
What|Removed |Added
Assignee|plasma-b...@kde.org |butir...@gmail.com
--- Comment #5 from Andrey
https://bugs.kde.org/show_bug.cgi?id=466053
--- Comment #3 from Andrey ---
(In reply to Michael Lashkevich from comment #2)
> (In reply to Andrey from comment #1)
> >
> > *** This bug has been marked as a duplicate of bug 444569 ***
>
> But that bug was marked as fixed for
https://bugs.kde.org/show_bug.cgi?id=466073
--- Comment #1 from Andrey ---
Maybe it's just standard messages when there is no settings defined in config
so default values are used?
Does it specific to Keyboard KCM, if so - any ideas what's wrong?
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=444569
Andrey changed:
What|Removed |Added
CC||lashk...@landau.ac.ru
--- Comment #12 from Andrey
https://bugs.kde.org/show_bug.cgi?id=466053
Andrey changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=420866
Andrey changed:
What|Removed |Added
Status|REPORTED|NEEDSINFO
Resolution
https://bugs.kde.org/show_bug.cgi?id=420866
Andrey changed:
What|Removed |Added
Status|RESOLVED|REPORTED
CC
https://bugs.kde.org/show_bug.cgi?id=415995
Andrey changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=415995
Andrey changed:
What|Removed |Added
URL||https://codereview.qt-proje
https://bugs.kde.org/show_bug.cgi?id=415995
Andrey changed:
What|Removed |Added
Summary|Cannot assign accented keys |Cannot assign dead keys
https://bugs.kde.org/show_bug.cgi?id=465536
Andrey changed:
What|Removed |Added
CC||butir...@gmail.com
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=463563
--- Comment #13 from Andrey ---
It might be this patch will fix it, still I need more info requested above.
https://codereview.qt-project.org/c/qt/qtbase/+/458395
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=463563
Andrey changed:
What|Removed |Added
Status|REOPENED|NEEDSINFO
Resolution
https://bugs.kde.org/show_bug.cgi?id=463563
Andrey changed:
What|Removed |Added
Resolution|WORKSFORME |---
Ever confirmed|0 |1
https://bugs.kde.org/show_bug.cgi?id=415995
Andrey changed:
What|Removed |Added
Version Fixed In||Qt 6.6.0
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=415995
Andrey changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Ever confirmed|0 |1
https://bugs.kde.org/show_bug.cgi?id=415995
Andrey changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=415995
Andrey changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Ever confirmed|1 |0
https://bugs.kde.org/show_bug.cgi?id=415995
Andrey changed:
What|Removed |Added
Resolution|WORKSFORME |WAITINGFORINFO
--- Comment #15 from Andrey
https://bugs.kde.org/show_bug.cgi?id=418288
--- Comment #13 from Andrey Babkin ---
UPD: For my situation I think I've found the root cause of the issue - most
likely this was happening due to plasma integration plugin installed in chrome
(https://chrome.google.com/webstore/detail/plasma
https://bugs.kde.org/show_bug.cgi?id=453661
Andrey changed:
What|Removed |Added
Version Fixed In||Qt 6.6.0
Resolution|UPSTREAM
https://bugs.kde.org/show_bug.cgi?id=464829
Andrey changed:
What|Removed |Added
CC||butir...@gmail.com
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=464706
Andrey changed:
What|Removed |Added
CC||butir...@gmail.com
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=464183
--- Comment #2 from Andrey ---
IIUC it's actually the same problem as BUG 453661, if so - let's track it there
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=453661
Andrey changed:
What|Removed |Added
CC||kasper.haep...@outlook.be
--- Comment #24 from Andrey
https://bugs.kde.org/show_bug.cgi?id=464183
Andrey changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=464509
Andrey changed:
What|Removed |Added
CC||butir...@gmail.com
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=418288
Andrey Babkin changed:
What|Removed |Added
CC||babkin.and...@gmail.com
--- Comment #10 from
https://bugs.kde.org/show_bug.cgi?id=455431
--- Comment #8 from Andrey ---
It's all possible, but first we should replicate X11 behavior I think. For that
we need to create the structures in KWin required.
Then we could imitate the MacOS behaviour or whatever.
I'm sorry but I still not on it yet
https://bugs.kde.org/show_bug.cgi?id=463563
--- Comment #8 from Andrey ---
Also your problem might be related to this patch, I don't see it adds
Syper/Hyper, though:
https://codereview.qt-project.org/c/qt/qtbase/+/411073
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=463563
Andrey changed:
What|Removed |Added
Resolution|FIXED |WAITINGFORINFO
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=463563
--- Comment #7 from Andrey ---
As you can see there, the patch is about Hyper, too:
"qxkbcommon: Map Super/Hyper to Meta early enough to have an effect"
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=463563
--- Comment #5 from Andrey ---
Also note, according to the comment there:
https://bugreports.qt.io/browse/QTBUG-62102?focusedCommentId=568808=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-568808
, you should still be able
https://bugs.kde.org/show_bug.cgi?id=463563
Andrey changed:
What|Removed |Added
URL||https://bugreports.qt.io/br
https://bugs.kde.org/show_bug.cgi?id=463563
--- Comment #1 from Andrey ---
Please try Wayland also
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=436318
Andrey changed:
What|Removed |Added
CC||butir...@gmail.com
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=461176
Andrey changed:
What|Removed |Added
CC||butir...@gmail.com
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=452119
Andrey changed:
What|Removed |Added
CC||butir...@gmail.com
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=444335
Andrey changed:
What|Removed |Added
CC||butir...@gmail.com
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=448867
Andrey changed:
What|Removed |Added
CC||butir...@gmail.com
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=462824
Andrey changed:
What|Removed |Added
CC||butir...@gmail.com
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=402913
--- Comment #26 from Andrey ---
(In reply to Henning from comment #23)
> And do you have a clue on where and how the FocusOut events are generated?
That happens when shortcut get intercepted by system as Global shortcut, so the
app has no chance to
https://bugs.kde.org/show_bug.cgi?id=402913
--- Comment #25 from Andrey ---
AFAIK Wayland has no kglobalaccel5 to kill, does the workaround with
bind/unbind work there?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=402913
--- Comment #22 from Andrey ---
If it's known to be X11 only issue let's mark it as such, or provide more info
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=453661
--- Comment #23 from Andrey ---
I have a question to all the reporters.
The Qt patch I suggested upstream implies all the shortcuts on QWERTZ keyboard
will behave as if they were on QWERTY, assuming US is the first layout:
pressing Ctrl+z as it printed
https://bugs.kde.org/show_bug.cgi?id=375518
--- Comment #46 from Andrey ---
(In reply to George Melikov from comment #38)
> Global hotkey Shift+Win+2 is still broken for me on layout switch to
> non-English with other Shift+2 symbol (english has @ there, my layout has ")
> in Wayla
https://bugs.kde.org/show_bug.cgi?id=453661
Andrey changed:
What|Removed |Added
URL|https://bugreports.qt.io/br |https://bugreports.qt.io/br
|owse
https://bugs.kde.org/show_bug.cgi?id=453661
Andrey changed:
What|Removed |Added
Assignee|kdelibs-b...@kde.org|butir...@gmail.com
URL|https
https://bugs.kde.org/show_bug.cgi?id=454223
Andrey changed:
What|Removed |Added
URL||https://unix.stackexchange
https://bugs.kde.org/show_bug.cgi?id=453661
--- Comment #21 from Andrey ---
That wasn't exactly the same patch, so it's OK )
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=375518
Andrey changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=415995
Andrey changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=415995
Andrey changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=453661
Andrey changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=453661
--- Comment #19 from Andrey ---
Got it working with the patch I suggested upstream. Stay tuned.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=415995
--- Comment #11 from Andrey ---
(In reply to Andrey from comment #9)
> Does it work for wayland with KDE Qt patch collection?
Please note some distros apply the KDE Qt patches just partially. You have to
make sure you have the patch needed in the fi
https://bugs.kde.org/show_bug.cgi?id=375518
Andrey changed:
What|Removed |Added
URL||https://bugreports.qt.io/br
https://bugs.kde.org/show_bug.cgi?id=375518
Andrey changed:
What|Removed |Added
Resolution|WORKSFORME |WAITINGFORINFO
--- Comment #45 from Andrey
https://bugs.kde.org/show_bug.cgi?id=462677
Andrey changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=462677
--- Comment #8 from Andrey ---
(In reply to jakubby from comment #0)
> 4. Switching layout now enables the caps lock functionality, but it didn't
> in the past or at least on arch linux.
I doubt it worked the other way, can you test on VM a
https://bugs.kde.org/show_bug.cgi?id=462677
--- Comment #6 from Andrey ---
(In reply to jakubby from comment #3)
> Now it does both, switching caps-lock and acting as a switch layout switch.
That's really odd, don't you have some IBus packages installed, just for the
case?
I need some
https://bugs.kde.org/show_bug.cgi?id=462677
--- Comment #5 from Andrey ---
(In reply to jakubby from comment #0)
> 3. Set caps-lock as the switch key for keyboard layouts.
Where do you set it?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=462677
Andrey changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=462433
Andrey changed:
What|Removed |Added
CC||butir...@gmail.com
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=462278
Andrey changed:
What|Removed |Added
CC||butir...@gmail.com
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=439895
Andrey changed:
What|Removed |Added
Latest Commit||https://invent.kde.org/util
https://bugs.kde.org/show_bug.cgi?id=462299
Andrey changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=462285
--- Comment #2 from Andrey ---
Do you see a layout applet in systray, what happens if you click on it?
What happens if you press the switching shortcut?
Do you have IBus packages installed? (you shouldn't)
Did you try to ask about your problem on some
https://bugs.kde.org/show_bug.cgi?id=453661
Andrey changed:
What|Removed |Added
URL||https://bugreports.qt.io/br
https://bugs.kde.org/show_bug.cgi?id=355046
Andrey changed:
What|Removed |Added
CC||butir...@gmail.com
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=453661
--- Comment #14 from Andrey ---
For X11 it always fall-backs to the first layout defined because of internal
Xorg peculiarity (bug), that is why it works there if the first is US or
similar.
For "Latin", Qt tests each of the configured layo
https://bugs.kde.org/show_bug.cgi?id=453661
--- Comment #12 from Andrey ---
(In reply to Andrey from comment #11)
> Both ` and ; are legitimate (Latin or even ASCII) symbols for shortcuts, so
> if one key generates them it seems impossible to solve without knowing what
> physical key wa
https://bugs.kde.org/show_bug.cgi?id=453661
--- Comment #11 from Andrey ---
Both ` and ; are legitimate (Latin or even ASCII) symbols for shortcuts, so if
one key generates them it seems impossible to solve without knowing what
physical key was pressed? Do you have some solution in mind, other
https://bugs.kde.org/show_bug.cgi?id=453661
Andrey changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=375518
Andrey changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=453661
--- Comment #7 from Andrey ---
Does it work for you with other layouts, for example with EN, RU?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=415995
Andrey changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=434949
Andrey changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=415995
Andrey changed:
What|Removed |Added
CC||butir...@gmail.com
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=452445
--- Comment #16 from Andrey ---
Andreas, that's because if an application closed it won't be treated as the
same application when it run again.
I don't know how to solve this.
If you open a new window from existing application, the layout
https://bugs.kde.org/show_bug.cgi?id=461833
Andrey changed:
What|Removed |Added
Resolution|--- |WORKSFORME
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=439895
Andrey changed:
What|Removed |Added
CC||butir...@gmail.com
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=445527
Andrey changed:
What|Removed |Added
Resolution|FIXED |DUPLICATE
--- Comment #11 from Andrey ---
I'll mark
201 - 300 of 1949 matches
Mail list logo