[kwin] [Bug 484439] Regression with Alt+Shift layout switching
https://bugs.kde.org/show_bug.cgi?id=484439 --- Comment #13 from Wismill --- (In reply to Kirill Zhumarin from comment #8) > Any reasons why broken XCB is still used for layout switching? This can be > implemented on the KDE side. Going against the protocol is opening a can of worms I am not ready to open. Finding a proper ad-hoc fix in libxkbcommon must ensure to not break anything else. So, the main reason is lack of resource. And forget to have this ever fixed in upstream XOrg, no one cares. So it is great it is fixed in Plasma 6.1! đ -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 475085] Meta should always be mod1
https://bugs.kde.org/show_bug.cgi?id=475085 Wismill changed: What|Removed |Added CC||d...@wismill.eu --- Comment #2 from Wismill --- Please consider opening a ticket at https://gitlab.freedesktop.org/xkeyboard-config, where the keyboard configurations are defined. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478208] Caps Lock assigned to Last used shortcut still acts as a Caps Lock
https://bugs.kde.org/show_bug.cgi?id=478208 Wismill changed: What|Removed |Added CC||d...@wismill.eu --- Comment #8 from Wismill --- This cannot be implemented in XKB, because there is no support for âlast *used* layoutâ. The issue seems to be that Plasma intercepts the keysym Caps_Lock but not its *action*. Plasma should probably handle this at a lower level, before the modifiers state is propagated. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 427589] Wrong keyboard layout
https://bugs.kde.org/show_bug.cgi?id=427589 Wismill changed: What|Removed |Added CC||d...@wismill.eu --- Comment #2 from Wismill --- setxkbmap is a X11 tool and as such will not give you a meaningful result. On recent versions there is indeed a warning: `WARNING: Running setxkbmap against an Xwayland server`. Is you issue incorrect layout for X11 apps or merely incorrect result with `setxkbmap -query`? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 470470] Usage of setxkbmap on Wayland resets Keyboard-Layout to US (even if it is not configured)
https://bugs.kde.org/show_bug.cgi?id=470470 Wismill changed: What|Removed |Added CC||d...@wismill.eu --- Comment #1 from Wismill --- setxkbmap and xmodmap are X11-only tools and will not work with Wayland. So e.g. `setxkbmap -query` will most probably not gives you any meaningful information. In a Wayland session, the only way to check reliably your keymap in X11 is to use `xkbcomp $DISPLAY -` . -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 470470] Usage of setxkbmap on Wayland resets Keyboard-Layout to US (even if it is not configured)
https://bugs.kde.org/show_bug.cgi?id=470470 --- Comment #3 from Wismill --- Note that setxkbmap should display the following warning: âWARNING: Running setxkbmap against an Xwayland serverâ. It may require a recent version. There is no tool to replace setxkbmap for Wayland; or rather: there is no *generic* (as in âfor all DEâ) tool to replace it. See the discussion at https://github.com/xkbcommon/libxkbcommon/issues/470#issuecomment-1998697198. It would be very useful to have a Plasma-specific tool to configure the keyboard config as setxkbmap. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485635] New: Keyboard layout is not restored in Wayland
https://bugs.kde.org/show_bug.cgi?id=485635 Bug ID: 485635 Summary: Keyboard layout is not restored in Wayland Classification: Plasma Product: plasmashell Version: master Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Keyboard Layout Assignee: plasma-b...@kde.org Reporter: d...@wismill.eu CC: butir...@gmail.com Target Milestone: 1.0 SUMMARY Last used keyboard layout is not restored when using a Wayland session. STEPS TO REPRODUCE 1. Configure at least 2 keyboard layouts with Global policy in a Wayland session. E.g.: us,de. 2. Switch to the second layout (de). 3. Logout 4. Login OBSERVED RESULT Current layout is the first layout (us). EXPECTED RESULT Current layout should be the last used layout, i.e. the second one (de). SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed KDE Plasma Version: master (6.0.80) KDE Frameworks Version: 6.2.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION - -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485635] Keyboard layout is not restored in Wayland
https://bugs.kde.org/show_bug.cgi?id=485635 Wismill changed: What|Removed |Added CC||d...@wismill.eu -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485635] Keyboard layout is not restored in Wayland
https://bugs.kde.org/show_bug.cgi?id=485635 --- Comment #1 from Wismill --- Note that it works in X11 session. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485635] Keyboard layout is not restored in Wayland
https://bugs.kde.org/show_bug.cgi?id=485635 --- Comment #3 from Wismill --- (In reply to Andrey from comment #2) > Please make sure you have following option enabled: > system settings -> startup and shutdown -> desktop session -> "restore > previous session" I do have this option activated, but it does not work. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485635] Keyboard layout is not restored in Wayland
https://bugs.kde.org/show_bug.cgi?id=485635 --- Comment #4 from Wismill --- Actually it does *not* work in 6.0.3 either. I just tried with a fresh new user. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485635] Keyboard layout is not restored in Wayland
https://bugs.kde.org/show_bug.cgi?id=485635 Wismill changed: What|Removed |Added Ever confirmed|0 |1 Status|RESOLVED|REOPENED Resolution|DUPLICATE |--- -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485635] Keyboard layout is not restored in Wayland
https://bugs.kde.org/show_bug.cgi?id=485635 --- Comment #6 from Wismill --- (In reply to Andrey from comment #5) > What's your layout switching policy? > Please note it doesn't work for App (or Window?) Switching policy. > As written in the description, itâs the Global policy. > Either way it's a duplicate, if it regressed let's continue in the original > report. > I don't think we need a new one. > Your call. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 412101] Wayland session does not remember the last used keyboard layout. The first keyboard layout listed in "layouts" tab of the "Keyboard" kcm is always used after login instead.
https://bugs.kde.org/show_bug.cgi?id=412101 Wismill changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #36 from Wismill --- It seems to have regressed. Tested on 6.0.3 and master (see Bug 485635). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 412101] Wayland session does not remember the last used keyboard layout. The first keyboard layout listed in "layouts" tab of the "Keyboard" kcm is always used after login instead.
https://bugs.kde.org/show_bug.cgi?id=412101 --- Comment #38 from Wismill --- I have a "LayoutDefaultGlobal" entry, but it is not overwritten at logout. It does work if I set it manually though. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 412101] Wayland session does not remember the last used keyboard layout. The first keyboard layout listed in "layouts" tab of the "Keyboard" kcm is always used after login instead.
https://bugs.kde.org/show_bug.cgi?id=412101 --- Comment #40 from Wismill --- (In reply to Andrey from comment #39) > Maybe we have stale KWin process? > Can you make sure there is no kwin and other Plasma processes in the system > immediately after logout? I tried to check this with htop in TTY and could not detect Plasma processes. But this method does not seem reliable if I am not fast enough. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 384702] KWin doesn't expose a way to use one keymap per keyboard
https://bugs.kde.org/show_bug.cgi?id=384702 Wismill changed: What|Removed |Added CC||d...@wismill.eu -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 422401] Can't assign shortcut to F24 key
https://bugs.kde.org/show_bug.cgi?id=422401 Wismill changed: What|Removed |Added CC||d...@wismill.eu --- Comment #24 from Wismill --- FYI, in xkeyboard-config 2.43+ there will be an option to map F13-F24 to their corresponding function keysyms. On Wayland you can define custom XKB options, see: https://xkbcommon.github.io/libxkbcommon/doc/current/user-configuration.html. You need Plasma 6.1+ though, to be able to configure this in the keyboard settings GUI. Corresponding MR: https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/-/merge_requests/726 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478152] Level3 symbols override layout third level bindings, so Estonian (US) layout does not work
https://bugs.kde.org/show_bug.cgi?id=478152 Wismill changed: What|Removed |Added CC||d...@wismill.eu --- Comment #2 from Wismill --- The misc:typo XKB option does override the third and fourth levels and I am afraid this makes it incompatible with you layout. Please open an issue at https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/ so we can modify the layout to add the symbols you need from the typo layout. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 177889] add ability to configure multiple keyboards
https://bugs.kde.org/show_bug.cgi?id=177889 Wismill changed: What|Removed |Added CC||d...@wismill.eu -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 491982] Caps Lock (while pressed) shortcut to change keyboard layout does not work in Electron apps
https://bugs.kde.org/show_bug.cgi?id=491982 Wismill changed: What|Removed |Added CC||d...@wismill.eu --- Comment #12 from Wismill --- I cannot reproduce this issue. I tried VS Code (Electron), installed natively. I do not have issue with Caps characters either. Distro: OpenSUSE Tumbleweed xkeyboard-config: 2.42 Plasma 6.1.4 Could share your xkeyboard-config package version and your ~/.config/kxkbrc file, or at least its `Options` field? There are many XKB options which may have their labels changed in different XKB versions. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 492933] Level 5 symbol on key having ISO_Level5_Latch on level 1 is ignored
https://bugs.kde.org/show_bug.cgi?id=492933 Wismill changed: What|Removed |Added CC||d...@wismill.eu -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 492933] Level 5 symbol on key having ISO_Level5_Latch on level 1 is ignored
https://bugs.kde.org/show_bug.cgi?id=492933 --- Comment #1 from Wismill --- I confirm this bug is still present in 6.1.5. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 494579] 6.2.0 causes Shift+Alt (but not Alt+Shift) to trigger Meta modifier-only shortcut
https://bugs.kde.org/show_bug.cgi?id=494579 Wismill changed: What|Removed |Added CC||d...@wismill.eu -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 492933] Level 5 symbol on key having ISO_Level5_Latch on level 1 is ignored
https://bugs.kde.org/show_bug.cgi?id=492933 --- Comment #2 from Wismill --- I just tried KDE Neon testing with Plasma 6.2, updated xkb-data to 2.42 and it seems to be fixed there. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 458442] Arabic keyboard layout sends ligatures as one character (Laa Problem)
https://bugs.kde.org/show_bug.cgi?id=458442 Wismill changed: What|Removed |Added CC||d...@wismill.eu --- Comment #3 from Wismill --- I cannot reproduce this Plasma 6.1.5. @AvidSeeker The sequence you expect is defined at: https://gitlab.freedesktop.org/xorg/lib/libx11/-/blob/f2ebbce6d0978d2d84f840196b03ee35a3ca1736/nls/en_US.UTF-8/Compose.pre#L4523, while the relevant key in this Arabic layout is: https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/-/blob/0f42a9a5b06262e35392680a3ad3d9cad3175086/symbols/ara#L53. So you may have an issue with the Compose file parsing, which would lead to not replacing UFEFB for "Ůا". Do other Compose sequence work? Is there other that do not work? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478208] Caps Lock assigned to Last used shortcut still acts as a Caps Lock
https://bugs.kde.org/show_bug.cgi?id=478208
--- Comment #11 from Wismill ---
As written above, this is Plasma bug, not an XKB one: the XKB action (locking
Caps) is resolved while it should not, when Caps key is bound to a shortcut.
In order to mitigate this, you may:
1. Use one of the XKB options to switch layouts. There are located in âKey
bindingsâ (top right button from keyboard config), then look for the group
âSwitching to another layoutâ. The âCaps Lockâ option in this group allow you
to switch to cycle the layouts. But they are many other options which may fit
better to your needs.
2. For power users: Tweak the XKB keymap by creating your own option. Follow
the guide at:
https://xkbcommon.org/doc/current/user-configuration.html#autotoc_md16:
cat $XDG_CONFIG_HOME/xkb/rules/evdev
! option = symbols
custom:caps= +my-caps
! include %S/evdev
$ cat $XDG_CONFIG_HOME/xkb/symbols/my-caps
partial alphanumeric_keys
xkb_symbols "deactivate caps" {
key {[ F35] };
};
and adapt the âDiscoverable layoutsâ section of the linked example with the
files above. Now re-open the keyboard settings and activate your brand new
option: you should be able to bind the CapsLock *key* as described in this
issue, *without* locking the Caps. It does not mess with systems files and it
will survive an update of those.
Note that I will not assist you further with tweaking XKB, so if you do not
feel comfortable please stick with temp solution 1) and wait for the KDE devs
to fix the issue.
--
You are receiving this mail because:
You are watching all bug changes.
[systemsettings] [Bug 491982] Caps Lock (while pressed) shortcut to change keyboard layout does not work in Electron apps
https://bugs.kde.org/show_bug.cgi?id=491982 --- Comment #16 from Wismill --- Are your problematic applications running with native Wayland support or X11? I set *3* layouts us,fr,de I tried using Chromium (*not* flatpack) in both case and I observe the following: - chromium --ozone-platform=wayland: no issue - chromium --ozone-platform=x11: pressing Caps, - Having first layout US active: Q gives Q (expected A), Y gives Z (expected Y); - Having second layout FR active: Q gives Q (ok) but Y gives Y (expected Z) So it seems that the group modifier is applied twice. In the case without only two layouts, it actually wraps to the first layout, so you observe no effect. But wait, I can observe this behavior in Gtk apps using e.g. `GDK_BACKEND=x11 gnome-text-editor` and Qt app e.g. QT_QPA_PLATFORM=xcb kate`. This seems to be an X11 bug only. Keep in mind this is for a Wayland session only, I have not tried a proper X11 session. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 491982] Caps Lock (while pressed) shortcut to change keyboard layout does not work in Electron apps
https://bugs.kde.org/show_bug.cgi?id=491982 --- Comment #18 from Wismill --- This should definitively be fixed, as it is still common to use X11 apps on Wayland (and will be for long, maybe forever). This could also a symptom of a deeper issue a with the keyboard state. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 434988] keyboard shortcuts use shifted symbols (e.g., Meta+!) instead of the unshifted ones (e.g., Meta+Shift+1)
https://bugs.kde.org/show_bug.cgi?id=434988 Wismill changed: What|Removed |Added CC||d...@wismill.eu -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 479442] Apple Aluminium keyboard (ISO) cannot be properly used
https://bugs.kde.org/show_bug.cgi?id=479442
--- Comment #2 from Wismill ---
@nathan67003: could you provide the keycode of each modifier? You may use
`evtest` for this. It would help to have the following mapping:
physical modifier (in maCOS idiom) + {left,right} side -> Linux keycode
(e.g. `code 46 (KEY_C)` part of evtest output)
so I can identify what are exactly the mismatches.
--
You are receiving this mail because:
You are watching all bug changes.
[systemsettings] [Bug 479442] Apple Aluminium keyboard (ISO) cannot be properly used
https://bugs.kde.org/show_bug.cgi?id=479442 --- Comment #3 from Wismill --- (In reply to John Veitch from comment #1) > I have an Apple Aluminium Keyboard with British keycaps and have a problem > on Plasma 6.1.5 on Wayland. The ` and \ keys are swapped in KDE > applications, although strangely they are not swapped in Chrome! > To make matters worse, the preview function in the Keyboard setting page > doesn't work. The error is [âŚ] I believe this is this upstream bug: https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/-/issues/334 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 496462] selected key for 3rd level becomes
https://bugs.kde.org/show_bug.cgi?id=496462 --- Comment #1 from Wismill --- I cannot reproduce. Could you provide: - The version of the xkeyboard-config package (or xkb-data). - The content of your ~/.config/kxkbrc, *once* you set the option. - What keyboard testing programs you are using. You may want to use xkbcli from the libxkbcommon-tool package. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 422401] Can't assign shortcut to F24 key
https://bugs.kde.org/show_bug.cgi?id=422401 Wismill changed: What|Removed |Added Resolution|--- |UPSTREAM Status|CONFIRMED |RESOLVED --- Comment #25 from Wismill --- (In reply to fanzhuyifan from comment #21) > Unfortunately, given the current codebase, we also rely on that on wayland. > Currently all shortcuts are stored using QKeySequence. We use the keymap to > convert keycodes to keysyms, and then convert the keysyms into Qt keys. If > we want to support platform native keycodes, that would need a pretty > significant change throughout the code base. So we can consider this fixed upstream in xkeyboard-config 2.43, see: https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/-/blob/master/ChangeLog.md. The only enhancement I see possible atm is to *inform the user* that a key cannot be used in a shortcut because it has no binding in the keyboard layout, instead of just ignoring the input. You may install manually corresponding MR https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/-/merge_requests/726 in you user config, using the following tutorial: https://xkbcommon.org/doc/current/user-configuration.html. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 493525] German NEO2 Layout - Layer 4 Key "Zero" isn't working after update
https://bugs.kde.org/show_bug.cgi?id=493525 Wismill changed: What|Removed |Added CC||d...@wismill.eu Status|REPORTED|RESOLVED Resolution|--- |UPSTREAM --- Comment #6 from Wismill --- (In reply to Ismael Asensio from comment #4) > According to the xkb layout description > (https://github.com/xkbcommon/libxkbcommon/blob/ > a600c36d1bc21aa33e68c391a637cc396a4ecaeb/test/data/symbols/de#L416) and the > info in the Neo Layout page (https://www.neo-layout.org/Layouts/neo/), to > get a "0" with the Space key you need Mod4/Ebene4 (ISO Level5), not Mod3 > (ISO Level3), which it is working. Note that the actual layout file is in another project, xkeyboard-config: https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/-/blob/63d45b4a84330eca6903963d37a6e50bc947c13d/symbols/de#L480. Files in xkbcommon repo are for testing purpose only. I cannot reproduce the issue either, so letâs close it. If you face another issue about keyboard layouts, please open a ticket upstream directly at: https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/-/issues. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 470470] No alternative to setxkbmap on Wayland
https://bugs.kde.org/show_bug.cgi?id=470470 Wismill changed: What|Removed |Added Summary|Usage of setxkbmap on |No alternative to setxkbmap |Wayland resets |on Wayland |Keyboard-Layout to US (even | |if it is not configured)| -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478152] Level3 symbols override layout third level bindings, so Estonian (US) layout does not work
https://bugs.kde.org/show_bug.cgi?id=478152 Wismill changed: What|Removed |Added Resolution|--- |UPSTREAM Status|REPORTED|RESOLVED --- Comment #3 from Wismill --- This is an upstream issue (option incompatible with a layout) and could be resolve by adding yet another layer. You would need to open a ticket in the upstream repository https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/ to discuss that. Another solution is to adapt the layout to your needs following this guide: https://xkbcommon.org/doc/current/user-configuration.html. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 496195] Capslock key does not switch behavior when using colemak layout
https://bugs.kde.org/show_bug.cgi?id=496195 --- Comment #1 from Wismill --- This is an upstream issue, similar to: https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/-/issues/490. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 453661] Global shortcuts are not working across multiple keyboard layouts (US and CZ for me)
https://bugs.kde.org/show_bug.cgi?id=453661 Wismill changed: What|Removed |Added CC||d...@wismill.eu -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 494848] shift+alt does not trigger alt+shift modifier only shortcut
https://bugs.kde.org/show_bug.cgi?id=494848 --- Comment #9 from Wismill --- (In reply to Vladislav Grechannik from comment #1) > Shift+Alt works if I set it in the old/deprecated X11 keymaps By the way what do you mean by deprecated? XKB keymaps (as in xkeyboard-config and /usr/share/X11/xkb) are not deprecated at all and are the standard keymaps in Wayland too. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 494848] shift+alt does not trigger alt+shift modifier only shortcut
https://bugs.kde.org/show_bug.cgi?id=494848 --- Comment #8 from Wismill --- (In reply to fanzhuyifan from comment #6) > Note that this has been removed from the default setting upstream in > https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/-/ > merge_requests/762. There hasn't been a release containing that commit > though. This will be the default in the upcoming xkeyboard-config 2.44, which will be released very soon. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 478620] Mouse navigation with numpad doesn't work under Wayland
https://bugs.kde.org/show_bug.cgi?id=478620 Wismill changed: What|Removed |Added CC||d...@wismill.eu -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 478219] Global shortcuts that send keystrokes/characters to the focused window
https://bugs.kde.org/show_bug.cgi?id=478219 Wismill changed: What|Removed |Added CC||d...@wismill.eu -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 497316] New: Diagram areas glitch in system monitor
https://bugs.kde.org/show_bug.cgi?id=497316 Bug ID: 497316 Summary: Diagram areas glitch in system monitor Classification: Applications Product: plasma-systemmonitor Version: 6.2.4 Platform: openSUSE OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: d...@wismill.eu CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Created attachment 176518 --> https://bugs.kde.org/attachment.cgi?id=176518&action=edit Widget with diagram glitch at the cursor SUMMARY Circular Diagram areas glitch when using system monitor as a widget. STEPS TO REPRODUCE 1. Create a System Monitor widget in the taskbar, with a circular diagram showing used and free RAM memory. 2. Click on the widget to show the detailed diagram. OBSERVED RESULT Diagram areas (free and used memory) have rounded edges and create a visual glitch. EXPECTED RESULT Diagram areas should not have rounded edge when next to each other. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed KDE Plasma Version: 6.2.4 KDE Frameworks Version: 6.8.0 Qt Version: 6.8.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 497316] Diagram areas glitch in system monitor
https://bugs.kde.org/show_bug.cgi?id=497316 Wismill changed: What|Removed |Added Status|RESOLVED|REPORTED Resolution|INTENTIONAL |--- --- Comment #2 from Wismill --- (In reply to Nate Graham from comment #1) > I believe this is in fact the intended appearance. It might be a cool effect at a greater scale, but at this *small scale* it does not look right: instead of 2 colors next to each other, there is a *third* one: the background. One wonder if this is a tiny percentage or whatever It is not immediate that this is a style effect and it looks like a glitch. Let me take an example in another field: good fonts and icons do not display the same level of details depending on their size, because it would look blurry at samall size, defeating readability. The rounded edges should be only at ends that are *not* located next to another meaningful data. Note that I am not against rounded effects, but they should be used with parsimony. So in name of *readability* against overstyling, I am reopening this. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 494610] Capslock is detected as Ctrl and also Capslock when it it assigned to be mapped to Ctrl
https://bugs.kde.org/show_bug.cgi?id=494610 --- Comment #1 from Wismill --- I cannot reproduce this. Could you: - Provide the version of the package xkeyboard-config (or xkb-data)? - Provide the content of your ~/.config/kxkbrc? So we get the exact config you are using. -- You are receiving this mail because: You are watching all bug changes.
[kcharselect] [Bug 98259] display keystrokes to enter the char if available
https://bugs.kde.org/show_bug.cgi?id=98259 Wismill changed: What|Removed |Added CC||d...@wismill.eu -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 498700] Keyboard Layout Switching Exhibits Odd Behavior
https://bugs.kde.org/show_bug.cgi?id=498700 Wismill changed: What|Removed |Added CC||d...@wismill.eu -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 474981] Searching for "shutdown", "restart" or "sleep" brings up the "Desktop Session" KCM instead of performing the actions themselves
https://bugs.kde.org/show_bug.cgi?id=474981 Wismill changed: What|Removed |Added CC||d...@wismill.eu -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 489866] Krunner doesn't order search results based on my preferred order
https://bugs.kde.org/show_bug.cgi?id=489866 Wismill changed: What|Removed |Added CC||d...@wismill.eu -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 482187] Missing Esperanto flag on keyboard layout
https://bugs.kde.org/show_bug.cgi?id=482187 Wismill changed: What|Removed |Added CC||d...@wismill.eu -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 402019] Accents not send to device
https://bugs.kde.org/show_bug.cgi?id=402019 Wismill changed: What|Removed |Added CC||d...@wismill.eu -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 500164] Layout swiched Back to "English" -> The set Layout won't save after reboot/boot
https://bugs.kde.org/show_bug.cgi?id=500164 Wismill changed: What|Removed |Added CC||d...@wismill.eu -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 496814] Changing decimal separator has no effect
https://bugs.kde.org/show_bug.cgi?id=496814 Wismill changed: What|Removed |Added CC||d...@wismill.eu -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 501917] Keyboard layout switching breaks if the first layout matches the system layout
https://bugs.kde.org/show_bug.cgi?id=501917 Wismill changed: What|Removed |Added CC||d...@wismill.eu -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 336750] wrong character for keyboard shortcut with (US-intl) dead keys keyboard layout
https://bugs.kde.org/show_bug.cgi?id=336750 Wismill changed: What|Removed |Added CC||d...@wismill.eu -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 485419] The tilde (~) and caret (^) keys are not working anymore in KDE apps (e.g. Konsole)
https://bugs.kde.org/show_bug.cgi?id=485419 Wismill changed: What|Removed |Added CC||d...@wismill.eu -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 502639] Ability to rep-map Copilot key to something useful
https://bugs.kde.org/show_bug.cgi?id=502639 --- Comment #3 from Wismill --- I think it is better tackled in xkeyboard-config. Please open a ticket at https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/issues with some laptop pictures as evidence. Once we have a fix, anybody should be able to use it without waiting for the xkeyboard-config release, using a user configuration. Further info at: https://xkbcommon.org/doc/current/user-configuration.html. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 502639] Ability to rep-map Copilot key to something useful
https://bugs.kde.org/show_bug.cgi?id=502639 --- Comment #4 from Wismill --- Oh my, I now remember that the Copilot key sends in fact `Win + Shift + F23`, so it may not be that easy to remap using only XKB, because not all applications handle *consumed* modifiers correctly (e.g. they will still see Win+Shift in addition to the expected Control). So either Plasma handles it, or you may be better served with remapping tools, e.g. keyd, KMonad or Kanata. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461207] Assigning Window shortcut key cannot include "meta" key (the "Windows" key) or it will be modified to some weird key and fail
https://bugs.kde.org/show_bug.cgi?id=461207 --- Comment #6 from Wismill --- I can reproduce the issue with left Meta/Win as Compose key on Plasma 6.3.4 (Wayland), although I get multiple square characters instead of just one. Note that it is not specific to left Meta: I get the same issue if using Menu as a Compose key. Note that the shortcut itself works, itâs just the display. While it makes sense that a combo is not possible (Compose if not a modifier), I suspect that there is an issue with the conversion of the keysym Multi_key to UTF-8. If the conversion is done using the libxkbcommon API somewhere in the stack (e.g. xkb_keysym_to_utf8), then in the case of Multi_key nothing is written in the string buffer, so if it was not 0-ed then it would explain why we see garbage. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 493025] Unable to associate CTRL+ALT+BACKSPACE sequence as a shortcut; BACKSPACE detected as "Unidentified"
https://bugs.kde.org/show_bug.cgi?id=493025 --- Comment #31 from Wismill --- (In reply to antonio from comment #30) > > @antonio: when XkbOptions is set/unset, does it change your > > ~/.config/kxkbrc? > File contents: > > [$Version] > update_info=kxkb.upd:remove-empty-lists,kxkb.upd:add-back-resetoptions, > kxkb_variants.upd:split-variants So it seems that you never change any keyboard setting in KDE and that you keyboard config is entirely set from the environment variables. I try on my own setup (Plasma 6.3.4, Wayland), and I think that the root issue is that QXkbCommon::keysymToQtKey or similar does not handle the keysym XKB_KEY_Terminate_Server that is generated by CTRL+ALT+BACKSPACE when the option "terminate:ctrl_alt_bksp" is set. Thus when setting a global shortcut KDE registers Ctrl+Alt, instead of Ctrl+Alt+Terminate_Server. I see 2 issues: - KDE should not register a shortcut when one of the keysym is not translated correctly (i.e. returns NoSymbol or Qt equivalent) - KDE should support all XKB keysyms. If the limit is what Qt supports, either fix Qt or have a hack to support more keysyms, if possible. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 493025] Unable to associate CTRL+ALT+BACKSPACE sequence as a shortcut; BACKSPACE detected as "Unidentified"
https://bugs.kde.org/show_bug.cgi?id=493025 --- Comment #29 from Wismill --- Coming late to the battle, but I have some comments: - XkbOptions="terminate:ctrl_alt_bksp" seems an ubiquitous default setting, but I might be wrong. I do remember seeing the CTRL+ALT+BACKSPACE shortcut in tutorials, a⌠long time ago đ . Since it is set in system files, KDE just pick up the option. However, in Wayland the env variable is `XKB_DEFAULT_OPTIONS`, see: https://invent.kde.org/plasma/kwin/-/blob/5f4ff1d49d1818521915543c942ddf6dda60ebc3/src/xkb.cpp#L573. So there should be a translation somewhere. - setxkbmap does not work in Wayland sessions. Use: - cat ~/.config/kxkbrc in KDE to show you keyboard config. There may be a better way with dbus specific to KDE, I do not remember how to query it. - xkbcli dump-keymap-wayland to get the actual keymap. You need libxkbcommon-tools 1.8+. - xkbcli interactive-wayland to replace xev - There is no libxkb, but libxkbfile (X11) and libxkbcommon (Wayland). @antonio: when XkbOptions is set/unset, does it change your ~/.config/kxkbrc? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 503230] Can't bind KEY_PROG2 as shortcut
https://bugs.kde.org/show_bug.cgi?id=503230 --- Comment #1 from Wismill --- Are you using a Wayland or a X11 session? Could you try your shortcut in the corresponding `xkbcli interactive-wayland` or `xkbcli interactive-x11` (keep the blank window focus while typing, press ESC to quit) and post the result here? You may need to install the libxkbcommon-tools package (or other similar name). Please also report the version of the libxkbcommon package. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 503632] Wayland : settings app keyboard layouts don't apply to X11 applications
https://bugs.kde.org/show_bug.cgi?id=503632 --- Comment #2 from Wismill --- 1. Do you observe the same issue with other X11 applications in a Wayland session? 2. Do you observe the same issue using gpu-screen-recorder in a X11 session? 3. Is the issue specific to the * numpad key? Note that setxkbmap should not be used in a Wayland session. Indeed it should display the warning âWARNING: Running setxkbmap against an Xwayland serverâ. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 419314] Dead key are not transmitted to Android device by KDE connect remote input
https://bugs.kde.org/show_bug.cgi?id=419314 Wismill changed: What|Removed |Added CC||d...@wismill.eu -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 500750] Zoom in / out (Enlarge / Shrink Font) doesn't work at least for two keyboard layouts (German, Italian)
https://bugs.kde.org/show_bug.cgi?id=500750 Wismill changed: What|Removed |Added CC||d...@wismill.eu -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 357194] Chosen keyboard layout doesn't work when plasma-desktop reboots with fcitx5
https://bugs.kde.org/show_bug.cgi?id=357194 Wismill changed: What|Removed |Added CC||d...@wismill.eu -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 499909] Alt and Win Behaviors and Key to Choose 3rd Level incompatible on GNOME applications
https://bugs.kde.org/show_bug.cgi?id=499909 Wismill changed: What|Removed |Added CC||d...@wismill.eu -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 476831] Per application Keyboard Layout not remembered under Wayland
https://bugs.kde.org/show_bug.cgi?id=476831 Wismill changed: What|Removed |Added CC||d...@wismill.eu -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 384702] KWin doesn't expose a way to use one keymap per keyboard
https://bugs.kde.org/show_bug.cgi?id=384702 Wismill changed: What|Removed |Added Resolution|--- |DUPLICATE Status|CONFIRMED |RESOLVED --- Comment #4 from Wismill --- *** This bug has been marked as a duplicate of bug 177889 *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 467992] Wrong keyboard layout switch hotkey behavior for more than two layouts and per window layout policy
https://bugs.kde.org/show_bug.cgi?id=467992 Wismill changed: What|Removed |Added CC||d...@wismill.eu -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 499097] Keyboard layout differs between X11 and Wayland sessions
https://bugs.kde.org/show_bug.cgi?id=499097 Wismill changed: What|Removed |Added CC||d...@wismill.eu --- Comment #6 from Wismill --- It seems a migration issue of the config, fixed by editing the config in Wayland. I would expect it to be fixed also by editing the keyboard config in the X11 session. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 499909] Alt and Win Behaviors and Key to Choose 3rd Level incompatible on GNOME applications
https://bugs.kde.org/show_bug.cgi?id=499909 --- Comment #1 from Wismill --- We need your precise keyboard config. Could you provide the content of `~/.config/kxkbrc`? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 499527] Spare keyboard layouts doesn't work on KDE Plasma 6 with Wayland
https://bugs.kde.org/show_bug.cgi?id=499527 Wismill changed: What|Removed |Added Resolution|--- |DUPLICATE CC||d...@wismill.eu Status|REPORTED|RESOLVED --- Comment #1 from Wismill --- *** This bug has been marked as a duplicate of bug 455431 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 498339] Media Keys Not Working
https://bugs.kde.org/show_bug.cgi?id=498339 Wismill changed: What|Removed |Added CC||d...@wismill.eu -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 498562] Remote control "<" transmits as ">"
https://bugs.kde.org/show_bug.cgi?id=498562 Wismill changed: What|Removed |Added CC||d...@wismill.eu -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 468181] X11: some french accentuated characters are not possible
https://bugs.kde.org/show_bug.cgi?id=468181 Wismill changed: What|Removed |Added CC||d...@wismill.eu -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482181] If keyboards were changed while laptop was sleeping, can't enter password on waking to unlock session
https://bugs.kde.org/show_bug.cgi?id=482181 Wismill changed: What|Removed |Added CC||d...@wismill.eu -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358775] When using "Switching to another layout" > "Both keys together" keyboard layout setting, the shift key inserts characters on the lock screen greeter
https://bugs.kde.org/show_bug.cgi?id=358775 Wismill changed: What|Removed |Added CC||d...@wismill.eu -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 449706] Keypad decimal separator should respect regional formatting
https://bugs.kde.org/show_bug.cgi?id=449706 Wismill changed: What|Removed |Added CC||d...@wismill.eu -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 177889] add ability to configure multiple keyboards
https://bugs.kde.org/show_bug.cgi?id=177889 Wismill changed: What|Removed |Added CC||pina...@pinaraf.info --- Comment #13 from Wismill --- *** Bug 384702 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 494121] Many keyboard layouts seem to be wrongly put under "bqn" label
https://bugs.kde.org/show_bug.cgi?id=494121 Wismill changed: What|Removed |Added CC||d...@wismill.eu --- Comment #3 from Wismill --- Cannot reproduce on Plasma 6.3. I think this was an issue with the layouts variants in the extra XKB registry file. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 500032] The "Legacy X11 App Support" setting does not work correctly with a different keyboard layout!
https://bugs.kde.org/show_bug.cgi?id=500032 Wismill changed: What|Removed |Added CC||d...@wismill.eu -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 500050] Regression: Disabling the layouts deletes them
https://bugs.kde.org/show_bug.cgi?id=500050 Wismill changed: What|Removed |Added CC||d...@wismill.eu -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 500050] Regression: Disabling the layouts deletes them
https://bugs.kde.org/show_bug.cgi?id=500050 --- Comment #1 from Wismill --- I confirm the issue on 6.3.0. -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 428389] Cannot use AltGr to input Romanian characters
https://bugs.kde.org/show_bug.cgi?id=428389 Wismill changed: What|Removed |Added CC||d...@wismill.eu -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 498700] Keyboard Layout Switching Exhibits Odd Behavior
https://bugs.kde.org/show_bug.cgi?id=498700 --- Comment #1 from Wismill --- Hi fellow Tumbleweed user, could you show the content of `~/.config/kxkbrc`? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 455431] "Spare Layouts" feature on Wayland
https://bugs.kde.org/show_bug.cgi?id=455431 Wismill changed: What|Removed |Added CC||droidkt...@gmail.com --- Comment #25 from Wismill --- *** Bug 499527 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 421062] Keyboard Layout settings are always disabled
https://bugs.kde.org/show_bug.cgi?id=421062 Wismill changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #2 from Wismill --- There is not enough info to debug: what is you distribution, do you use an input method, etc. Try delete ~/.config/kxkbrc and relaunch the settings. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 421062] Keyboard Layout settings are always disabled
https://bugs.kde.org/show_bug.cgi?id=421062 Wismill changed: What|Removed |Added CC||d...@wismill.eu -- You are receiving this mail because: You are watching all bug changes.
[ktouch] [Bug 434632] layouts error in wayland session but without error in X11 session
https://bugs.kde.org/show_bug.cgi?id=434632 Wismill changed: What|Removed |Added CC||d...@wismill.eu -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 478936] Unable to bind / use the calculator key in plasma 6 on Wayland
https://bugs.kde.org/show_bug.cgi?id=478936 Wismill changed: What|Removed |Added CC||d...@wismill.eu -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 480355] Add Telex as an additional Vietnamese keyboard layout variant
https://bugs.kde.org/show_bug.cgi?id=480355 Wismill changed: What|Removed |Added CC||d...@wismill.eu -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 503891] Layouts from ~/.config/xkb are not listed in settings
https://bugs.kde.org/show_bug.cgi?id=503891 --- Comment #12 from Wismill --- (In reply to Damglador from comment #11) > Is it possible to avoid the need of an xml file for keyboards to be > discoverable? No, it is mandatory to make it appear in the GUI for keyboard config. But it is not necessary if you use the same id of an exisiting variant. I do not advise it though, as this issue shows it is then confusing. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 503891] Layouts from ~/.config/xkb are not listed in settings
https://bugs.kde.org/show_bug.cgi?id=503891
--- Comment #8 from Wismill ---
- ~/.config/xkb/symbols/us replaces the *default* US layout, because 1) it has
the same file name 2) of the âdefaultâ in âdefault partial alphanumeric_keys
xkb_symbols "custom"â
- ~/.config/xkb/symbols/ua: same, but for the default Ukrainian layout
You do not see âEnglish (Custom)â in the Plasma config because it loads the
info from /usr/share/X11/xkb/rules/evdev.xml, unless you provided a custom
~/.config/xkb/rules/evdev.xml. The entry in the system XML file has label
âEnglish (US)â.
However, your config loads correctly: check that the layout switcher widget
displays e.g. âEnglish (Custom)â, because the switcher uses the data from the
symbols files.
The âCustomâ layout labelled as âA user-defined custom Layoutâ is yet another
feature and uses /usr/share/X11/xkb/symbols/custom, that *is not shipped* by
xkeyboard-config. So if you did not created this file, it does not exist, and
selecting this entry will break your config! Note that this feature is a hack
aimed at X11 users. Under Wayland you should use the ~/.config/xkb files.
So in order to config your custom files and have them correctly labelled, you
need:
1. Replace your ~/.config/xkb/symbols/us file (same for the ua) with:
// Required to fix https://github.com/xkbcommon/libxkbcommon/issues/726, unless
using libxkbcommon 1.9+
default partial alphanumeric_keys xkb_symbols { include "us(basic)" };
partial alphanumeric_keys
xkb_symbols "custom" {
include "us(basic)"
name[Group1]= "English (Custom)";
key {[ 1, exclam,onesuperior
]};
key {[ 2, at,twosuperior,
U2019 ]};
include "level3(ralt_switch)"
};
2. Add a ~/.config/xkb/rules/evdev.xml file following these instructions:
https://xkbcommon.org/doc/current/user-configuration.html#discoverable-layouts
for both your layouts:
us
custom
us
English (custom)
ua
custom
ua
Ukrainian (custom)
I added a link to the reference documentation of libxkbcommon in the KDE wiki.
--
You are receiving this mail because:
You are watching all bug changes.
[systemsettings] [Bug 503891] Layouts from ~/.config/xkb are not listed in settings
https://bugs.kde.org/show_bug.cgi?id=503891 --- Comment #10 from Wismill --- (In reply to Nate Graham from comment #9) > Thanks so much for your exhaustive answer! I had a feeling it was a setup > issue. The wiki ought to be updated to include the step with the XML file (+ the issue I mentioned), so that the user can use the GUI to configure their keyboard config. I.e. providing a *complete* example of a small variant of a standard layout (e.g. US for illustration), which is probably the most common scenario, like the current issue. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 501917] Keyboard layout switching breaks if the first layout matches the system layout
https://bugs.kde.org/show_bug.cgi?id=501917 --- Comment #4 from Wismill --- (In reply to Janne Grunau from comment #2) > The issue does *not* reproduce on my desktop with identical software. > Settings there: > $localectl > System Locale: LANG=en_US.UTF-8 > VC Keymap: us >X11 Layout: (unset) > $ cat ~/.config/kxkbrc > [$Version] > update_info=kxkb.upd:remove-empty-lists,kxkb.upd:add-back-resetoptions, > kxkb_variants.upd:split-variants > > [Layout] > DisplayNames=,, > LayoutList=us,eu,de > Options=caps:ctrl_modifier > ResetOldOptions=true > Use=true > VariantList=euro,,nodeadkeys The original bug is likely due to https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/-/issues/112, which is fixed in xkeyboard-config-2.44. You cannot reproduce because you do not have the same config: your `model` is not set, so it will default to `pc104`. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 502639] Ability to rep-map Copilot key to something useful
https://bugs.kde.org/show_bug.cgi?id=502639 --- Comment #6 from Wismill --- (In reply to Ali from comment #5) > +1, Might not be the most useful but I think the F23 bit of what the copilot > key sends is what blocks it from being easily remappable, the keyboard > preview in settings correctly sees the copilot key as being Meta+Shift, but > it seemingly isn't aware of F23, and nor is Kwin when mapping to the key, as > it sees it as meta+shift, but then pressing the copilot key doesn't active > the shortcut, while manually pressing meta+shift does. It sounds like this issue: https://bugs.kde.org/show_bug.cgi?id=461207#c6. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 504761] New: External USB DVD writer is not detected
https://bugs.kde.org/show_bug.cgi?id=504761 Bug ID: 504761 Summary: External USB DVD writer is not detected Classification: Applications Product: dolphin Version First 25.04.1 Reported In: Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: d...@wismill.eu CC: kfm-de...@kde.org Target Milestone: --- SUMMARY External USB DVD writer is not detected by Plasma: no pop-up to ask to mount the device and it does not show in Dolphin. However it work, as it is detected properly by the venerable K3b. STEPS TO REPRODUCE 1. Plug the DVD writer in 2. Insert a CD/DVD OBSERVED RESULT No pop-up to mount, not showing in Dolphin EXPECTED RESULT Pop-up to mount and shows in Dolphin SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed KDE Plasma Version: 6.3.5 KDE Frameworks Version: 6.14.0 Qt Version: 6.9.0 ADDITIONAL INFORMATION I do not think it is proper to Dolphin, but I do not know which component of KDE it corresponds to. Maybe frameworks? Do I miss a package? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 504761] External USB DVD writer is not detected
https://bugs.kde.org/show_bug.cgi?id=504761 --- Comment #1 from Wismill --- Note that it does show up *after* mounting it in K3b. -- You are receiving this mail because: You are watching all bug changes.
