[plasmashell] [Bug 449531] Keyboard Layout applet does not appear immediately after adding a second keyboard layout; have to restart plasmashell first
https://bugs.kde.org/show_bug.cgi?id=449531 Andrey changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|CONFIRMED |NEEDSINFO --- Comment #4 from Andrey --- Can someone else confirm? Can't reproduce it. Any chance to try on VM? What second layout are you adding? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434713] Nothing happens when I press the keyboard shortcut of Keyboard Layout applet by the first time
https://bugs.kde.org/show_bug.cgi?id=434713 Andrey changed: What|Removed |Added Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/plas ||ma/plasma-desktop/commit/09 ||8a965b5df31a7b6a212b5269eec ||b36b9dadc6c Resolution|--- |FIXED --- Comment #17 from Andrey --- Git commit 098a965b5df31a7b6a212b5269eecb36b9dadc6c by Andrey Butirsky. Committed on 29/07/2022 at 10:51. Pushed by butirsky into branch 'master'. applets/keyboardlayout: fix unexpected expansion to full representation As a workaround, remove Keyboard Shortcuts configuration tab and already assigned shortcuts for the applet M +11 -0applets/keyboardlayout/contents/ui/configGeneral.qml A +25 -0 desktoppackage/contents/updates/keyboardlayout_remove_shortcut.js https://invent.kde.org/plasma/plasma-desktop/commit/098a965b5df31a7b6a212b5269eecb36b9dadc6c -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434713] Nothing happens when I press the keyboard shortcut of Keyboard Layout applet by the first time
https://bugs.kde.org/show_bug.cgi?id=434713 --- Comment #15 from Andrey --- (In reply to Chris Holland from comment #13) > * > https://github.com/Zren/plasma-applet-tiledmenu/blame/master/package/ > contents/ui/config/ConfigGeneral.qml#L21 > * > https://github.com/Zren/plasma-applet-tiledmenu/commit/ > ea15d8a2f141f0676b9608815a20707f0070b503 We still need to remove existing shortcut from the config, any ideas? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456391] broken/nonexistent keyboard layout
https://bugs.kde.org/show_bug.cgi?id=456391 Andrey changed: What|Removed |Added Flags||Wayland-, X11+ --- Comment #11 from Andrey --- I wonder if https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/951 might be related, can you test? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456391] broken/nonexistent keyboard layout
https://bugs.kde.org/show_bug.cgi?id=456391 --- Comment #9 from Andrey --- > (In reply to Andrey from comment #7) > > Wayland? > > No. Can you reproduce on wayland? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456391] broken/nonexistent keyboard layout
https://bugs.kde.org/show_bug.cgi?id=456391 --- Comment #7 from Andrey --- Wayland? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456391] broken/nonexistent keyboard layout
https://bugs.kde.org/show_bug.cgi?id=456391 Andrey changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #6 from Andrey --- (In reply to David Chmelik from comment #0) > STEPS TO REPRODUCE > 1. Edit 'system tray: keyboard layout:' add layouts including > alternative/international option such as 'with dead keys' for a > country/language/locale (UK, USA, maybe Germany, etc.) Try to customize text > & flag labels to distinguish alternative/international layout (maybe usi, > uki, whatever de/Deutsch/Austrian variant label: ) can't. > 2. Set keyboard layout 'always show' (or 'show when relevant' or 'always > hidden' but for either of latter two cases, subsequently make/test your own > steps.) > 3. See nothing work nor even keyboard layout icon display in system-tray! - Is 1. essential for 3? - "Edit 'system tray: keyboard layout:' add layouts" What do you mean exactly? - "Set keyboard layout 'always show'" - what if it's already set? - Can you reproduce on KDE Plasma Version: 5.24.80? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 456533] Not visible OSD on layout change
https://bugs.kde.org/show_bug.cgi?id=456533 Andrey changed: What|Removed |Added Status|NEEDSINFO |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408928] Keyboard layout OSD doesn't work on X
https://bugs.kde.org/show_bug.cgi?id=408928 Andrey changed: What|Removed |Added CC||speedy...@posteo.net --- Comment #19 from Andrey --- *** Bug 456533 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 456533] Not visible OSD on layout change
https://bugs.kde.org/show_bug.cgi?id=456533 Andrey changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |DUPLICATE --- Comment #1 from Andrey --- If it's on X11 then it's known issue and already reported: bug 408928 *** This bug has been marked as a duplicate of bug 408928 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455462] Wayland: Wrong keyboard layout for XWayland programs at login
https://bugs.kde.org/show_bug.cgi?id=455462 Andrey changed: What|Removed |Added Summary|Wayland: Wrong keyboard |Wayland: Wrong keyboard |layout for non-KDE programs |layout for XWayland |at login|programs at login -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 456162] Capslock doesn't trigger when key is held
https://bugs.kde.org/show_bug.cgi?id=456162 --- Comment #4 from Andrey --- (In reply to Andrey from comment #3) > You can report it here: > https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/-/issues (please provide the link if you do) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 456162] Capslock doesn't trigger when key is held
https://bugs.kde.org/show_bug.cgi?id=456162 Andrey changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |UPSTREAM --- Comment #3 from Andrey --- You can report it here: https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/-/issues -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 456162] Capslock doesn't trigger when key is held
https://bugs.kde.org/show_bug.cgi?id=456162 Andrey changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Andrey --- Doesn't seem like a KDE fault, can you check on other Desktop Environment? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 455888] The default shortcut (Ctrl+w) for the overview effect does not close the overview when the keyboard layout is non-Latin
https://bugs.kde.org/show_bug.cgi?id=455888 --- Comment #3 from Andrey --- Do you have a Latin layout configured first in the list? -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 444664] Implement KHamburgerMenu
https://bugs.kde.org/show_bug.cgi?id=444664 Andrey changed: What|Removed |Added Assignee|elvis.angelac...@kde.org|butir...@gmail.com CC||butir...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 455827] advanced keyboard settings are ignored in applications running under XWayland
https://bugs.kde.org/show_bug.cgi?id=455827 --- Comment #6 from Andrey --- Should the workaround with reset you've found be applied in X11, Wayland session or it's indifferent? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 455827] advanced keyboard settings are ignored in applications running under XWayland
https://bugs.kde.org/show_bug.cgi?id=455827 --- Comment #4 from Andrey --- Can you try to reproduce it again? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 445527] Dolphin crashes when closed while Ark compresses a file
https://bugs.kde.org/show_bug.cgi?id=445527 Andrey changed: What|Removed |Added CC||butir...@gmail.com Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #2 from Andrey --- Could you please check on master as a potential fix was just landed. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 445527] Dolphin crashes when closed while Ark compresses a file
https://bugs.kde.org/show_bug.cgi?id=445527 Andrey changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=440663 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 440663] New Dolphin window or tab opened after compression/extraction when certain default options are disabled, or when the job is canceled, or when the Dolphin window that initiated i
https://bugs.kde.org/show_bug.cgi?id=440663 Andrey changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=445527 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 440663] New Dolphin window or tab opened after compression/extraction when certain default options are disabled, or when the job is canceled, or when the Dolphin window that initiated i
https://bugs.kde.org/show_bug.cgi?id=440663 --- Comment #76 from Andrey --- (In reply to Alexander Lohnau from comment #71) > Git commit 75c6927883342ec533aea4663b7b5dfcf8d699a6 by Alexander Lohnau. > Committed on 27/12/2021 at 15:55. > Pushed by alex into branch 'release/21.12'. > > Do not highlight file after compression > > Dolphin opens a new tab whenever the file is compressed and > is not smart enough to highlight it in the currently open view. > Because people are annoyed by it and the alternatives are complex to > implement, > removing it is the best solution. > > > (cherry picked from commit 28f2ef4b22f53200cb8789dbc8fe8ecdba3a377f) > > M +2-5app/compressfileitemaction.cpp > > https://invent.kde.org/utilities/ark/commit/75c6927883342ec533aea4663b7b5dfcf8d699a6 Please note this workaround has been reverted in favor of the real fix above. Please test the fix on master, and if we still need to make the highlighting optional - please open a dedicated issue for that, I have some ideas in mind. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 440663] New Dolphin window or tab opened after compression/extraction when certain default options are disabled, or when the job is canceled, or when the Dolphin window that initiated i
https://bugs.kde.org/show_bug.cgi?id=440663 Andrey changed: What|Removed |Added Latest Commit|https://invent.kde.org/util |https://invent.kde.org/syst |ities/ark/commit/75c6927883 |em/dolphin/commit/73ff57bef |342ec533aea4663b7b5dfcf8d69 |44984643bf1ffdb9a478095cfb7 |9a6 |8dfb --- Comment #75 from Andrey --- Git commit 73ff57bef44984643bf1ffdb9a478095cfb78dfb by Andrey Butirsky. Committed on 22/06/2022 at 18:49. Pushed by butirsky into branch 'master'. do not open excessive tab even if directory of the file to be created is not the top-most opened in TreeView M +9-0src/dolphinmainwindow.cpp M +11 -0src/dolphinmainwindow.h M +26 -9src/dolphintabwidget.cpp M +25 -12 src/dolphintabwidget.h M +29 -7src/global.cpp https://invent.kde.org/system/dolphin/commit/73ff57bef44984643bf1ffdb9a478095cfb78dfb -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425315] Auto-started apps with system tray icons don't always show their tray icons after reboot when they launch before plasmashell is finished launching
https://bugs.kde.org/show_bug.cgi?id=425315 Andrey changed: What|Removed |Added Status|REOPENED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425315] Auto-started apps with system tray icons don't always show their tray icons after reboot when they launch before plasmashell is finished launching
https://bugs.kde.org/show_bug.cgi?id=425315 Andrey changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|WORKSFORME |--- -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455744] New: Sometimes search doesn't work
https://bugs.kde.org/show_bug.cgi?id=455744 Bug ID: 455744 Summary: Sometimes search doesn't work Product: kwin Version: 5.25.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-overview Assignee: kwin-bugs-n...@kde.org Reporter: led...@vivaldi.net Target Milestone: --- SUMMARY The search sometimes stops to work until reload. STEPS TO REPRODUCE 1. Activate overview effect. 2. Try to use built-in krunner OBSERVED RESULT Built-in krunner doeesn't work EXPECTED RESULT It should SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux with Linux Zen 5.18.5 (fully updated on 21.06.2022) (available in About System) KDE Plasma Version: 5.25.1 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.5 ADDITIONAL INFORMATION This bug exists ever since Niccolò Ve announced this effect on his YT channel. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455462] Wayland: Wrong keyboard layout for non-KDE programs at login
https://bugs.kde.org/show_bug.cgi?id=455462 Andrey changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #3 from Andrey --- The clue is if xwininfo doesn't show you any information when you click on a window, this is a Wayland window then. You can test on other clients. Considering your output, you dealt with XWayland apps instead. So you could try to run FF natively on Wayland and you shouldn't get the issue there. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455462] Wayland: Wrong keyboard layout for non-KDE programs at login
https://bugs.kde.org/show_bug.cgi?id=455462 --- Comment #1 from Andrey --- Are these apps Wayland or XWayland clients? You can check with "xwininfo" and point to the window -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 453875] kdeconnect crashes on startup
https://bugs.kde.org/show_bug.cgi?id=453875 --- Comment #2 from Andrey Rahmatullin --- Using lsof I found that for some reason libssl1.0.2 is loaded into the process, in addition to (and later than) the correct libssl3. Removing it helped (though I don't know who loaded it, considering that the second machine has it installed but not loaded into kdeconnectd). -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 453875] kdeconnect crashes on startup
https://bugs.kde.org/show_bug.cgi?id=453875
Andrey Rahmatullin changed:
What|Removed |Added
CC||w...@wrar.name
--- Comment #1 from Andrey Rahmatullin ---
I have the same problem on Debian Testing (kdeconnect 21.12.3, Qt 5.15.2). The
affected line is
"d->m_certificate.subjectInfo(QSslCertificate::CommonName).constFirst()" and
the drkonqi stack with debug symbols is
[KCrash Handler]
#4 std::__atomic_base::load (__m=std::memory_order_relaxed, this=0x0) at
/usr/include/c++/11/bits/atomic_base.h:479
#5 QAtomicOps::loadRelaxed (_q_value=...) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qatomic_cxx11.h:239
#6 QBasicAtomicInteger::loadRelaxed (this=0x0) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qbasicatomic.h:107
#7 QtPrivate::RefCount::ref (this=0x0) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qrefcount.h:55
#8 QString::QString (other=..., this=0x7fff8183ca78) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:1094
#9 KdeConnectConfig::deviceId (this=) at
./core/kdeconnectconfig.cpp:133
I've tried running it under gdb, so far I got to
(gdb) p
KdeConnectConfig::instance().d->m_certificate.subjectInfo(QSslCertificate::CommonName)
$3 = {> = {> = {},
{p = {d = 0x76b0a5f0 }, d = 0x76b0a5f0
}}, }
(not sure if it's possible to learn something useful about this QList instance
from this, as all methods return "Cannot evaluate function -- may be inlined")
But then I've read the output before the crash and there is "qt.network.ssl:
QSslSocket: cannot resolve " and "qt.network.ssl:
Incompatible version of OpenSSL" so it looks like it's something related to the
OpenSSL 3 migration. OTOH kdeconnect works without this problem on my other
machine running Debian sid...
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 455509] New: Some features disappeared, such as choosing desktops with numbers on keyboard and moving windows to desktops
https://bugs.kde.org/show_bug.cgi?id=455509 Bug ID: 455509 Summary: Some features disappeared, such as choosing desktops with numbers on keyboard and moving windows to desktops Product: kwin Version: 5.25.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: effects-desktop-grid Assignee: kwin-bugs-n...@kde.org Reporter: led...@vivaldi.net Target Milestone: --- Some features disappeared, such as choosing desktops with numbers on keyboard and moving windows to desktops *** STEPS TO REPRODUCE 1. Activate desktop grid 2. Press a number (for example, 2) OBSERVED RESULT Nothing happens EXPECTED RESULT Desktop is switched to the needed one (for example, 2) ADDITIONAL INFORMATION Seem's like this feature wasn't implemented back yet since rewriting the effect in QML -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 444569] Keyboard layout shortcuts activate wrong language [regression]
https://bugs.kde.org/show_bug.cgi?id=444569 Andrey changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=455431 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 455431] Spare layout not working after update
https://bugs.kde.org/show_bug.cgi?id=455431 Andrey changed: What|Removed |Added Resolution|WAITINGFORINFO |--- See Also||https://bugs.kde.org/show_b ||ug.cgi?id=444569 Status|NEEDSINFO |CONFIRMED Ever confirmed|0 |1 --- Comment #3 from Andrey --- Note it's not even planned though. Hope I'll have time some day to put my hands on it. Probably was reported already but couldn't find it. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 455431] Spare layout not working after update
https://bugs.kde.org/show_bug.cgi?id=455431 Andrey changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO CC||meve...@gmail.com --- Comment #1 from Andrey --- Please note spare layouts feature is not implemented for Wayland (yet). As it becomes recurring, we should probably add the platform to SOFTWARE/OS VERSIONS generation. Any ideas what's the best way to achieve that? (file an issue to some component etc.) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 434949] Custom shortcuts containing accented keys ("é" "è" "ç" "à") aren't working on X11
https://bugs.kde.org/show_bug.cgi?id=434949 Andrey changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=375518 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 375518] global shortcuts do not work for non-Latin symbols of foreign keyboard layouts
https://bugs.kde.org/show_bug.cgi?id=375518 Andrey changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=434949 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 375518] global shortcuts do not work for non-Latin symbols of foreign keyboard layouts
https://bugs.kde.org/show_bug.cgi?id=375518 --- Comment #36 from Andrey --- Johannes, please note the bug was filed for Wayland, please see if you still can reproduce the issue there. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 309193] Keyboard shortcuts doesn't work if non-english keyboard layout is set before english one
https://bugs.kde.org/show_bug.cgi?id=309193 Andrey changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=454511 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 454511] Alt+a does not work when "Czech" is one of the layouts, even if it's not currently selected
https://bugs.kde.org/show_bug.cgi?id=454511 Andrey changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=309193 URL||https://bugs.kde.org/show_b ||ug.cgi?id=309193#c74 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 453461] X11: Changing keyboard layout order stops most shortcuts from working
https://bugs.kde.org/show_bug.cgi?id=453461 Andrey changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=454511 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 454511] Alt+a does not work when "Czech" is one of the layouts, even if it's not currently selected
https://bugs.kde.org/show_bug.cgi?id=454511 Andrey changed: What|Removed |Added Ever confirmed|0 |1 Status|RESOLVED|REOPENED See Also||https://bugs.kde.org/show_b ||ug.cgi?id=453461 Resolution|WAITINGFORINFO |--- --- Comment #8 from Andrey --- Great, at least it works for Wayland. For X11 we don't use the same mechanism for searching Glabal shortcut suitable (as we don't use libxkbcommon there), thus is the problem. Hypothetically, fixable but I'm not sure if someone will bother.. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 454511] Alt+a does not work when "Czech" is one of the layouts, even if it's not currently selected
https://bugs.kde.org/show_bug.cgi?id=454511 --- Comment #5 from Andrey --- As a workaround, you could try to place non-Czech Latin layout first. Should work at least on X11, maybe Wayland, too. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 454511] Alt+a does not work when "Czech" is one of the layouts, even if it's not currently selected
https://bugs.kde.org/show_bug.cgi?id=454511 Andrey changed: What|Removed |Added Resolution|UPSTREAM|WAITINGFORINFO --- Comment #4 from Andrey --- (In reply to sedmicha from comment #2) > The problem was the default shortcut Alt+~ and that there is a ~ character > on the A key on the third level of the Czech keyboard (AltGr+a outputs ~). > It seems like when KDE handles shortcuts, it checks on all key levels of all > added layouts looking for a match. > > This seemed very weird to me at first, but thinking about it a bit more I > could see why KDE would want to handle shortcuts like that. So I'm not sure > if this is the intended behavior or not, but I assume it is. intended behavior is not quite the same but similar. Added recently for Wayland session. For X11, it always worked that way if one of Latin layouts is added first in Settings. This functionality is actually implemented in Qt and we just call it from our compositor. The logic behind it is to make Global shortcuts work uniformly on any layout. So if physical key has some Global shortcut defined for Latin layout - it always takes place whatever actual layout you have active. Just for the case, please confirm it works on Wayland the same way. PS: it still doesn't clear to me why you don't get standard action defined for Alt+`, it should switch windows of one group. > For example in the Opensuse bug report I linked, there's a comment from > someone with a Polish/Colemak layout that has issues with a bunch of key > combinations that don't work. He says: > ``` > I am experiencing the same issue, but also with Polish and Colemak layouts. > Currently I am unable to use Emacs keybindings such as Alt+w, Alt+h, > Control+Alt+a etc. Weirdly enough Alt+a works for me. > ``` That might be a different problem, Alt+w, Alt+h etc. are probably not global shortcuts. But then it should be reproducible on any desktop environment. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 452759] OSD of keyboard layout unnecessarily appears when I start to type on Wayland
https://bugs.kde.org/show_bug.cgi?id=452759 --- Comment #9 from Andrey --- (In reply to cantabile from comment #8) > This only happens in the Wayland session. The X11 session doesn't do this. Right, that OSD for X11 is not implemented for X11 at all AFAIK. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 454223] Keyboard Layout keeps resetting to US when I click anywhere on screen
https://bugs.kde.org/show_bug.cgi?id=454223 --- Comment #27 from Andrey --- I'm not suggesting to reinstall your system but rather try in on VM, so we would know what upgrade path producing it, if any. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 454223] Keyboard Layout keeps resetting to US when I click anywhere on screen
https://bugs.kde.org/show_bug.cgi?id=454223 --- Comment #25 from Andrey --- As I only have one IM applet, I wonder if the other one was left after upgrade. Can you check on new install? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 453506] Need to kick hotkeys on release, not press
https://bugs.kde.org/show_bug.cgi?id=453506 Andrey changed: What|Removed |Added Resolution|FIXED |UPSTREAM Status|NEEDSINFO |RESOLVED --- Comment #5 from Andrey --- For Modifier only shortcuts do not supporting multiple modifiers, please open another issue. Closing as XKB upstream. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 454223] Keyboard Layout keeps resetting to US when I click anywhere on screen
https://bugs.kde.org/show_bug.cgi?id=454223 --- Comment #23 from Andrey --- (In reply to stalkermar from comment #22) > Created attachment 149213 [details] > screenshot 3 > > And a screenshot #3. Man, this GUI is so outdated. I wish it would allow to > drag and drop multiple files in 1 go. It feels like I'm back in the 90s We see two IM applets, maybe that is the problem? Can you disable at least one? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 454223] Keyboard Layout keeps resetting to US when I click anywhere on screen
https://bugs.kde.org/show_bug.cgi?id=454223 --- Comment #18 from Andrey --- (In reply to stalkermar from comment #17) > > You can try forcibly disable the applet in Systray settings. > > There's no way to do that, though. There's no delete button, only "Show when > relevant" or "Always hidden". It's strange as I have one: "Disabled" for the IM applet. BTW, are you able to attach the files here? Wanted to attach the screenshot but couldn't. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 454223] Keyboard Layout keeps resetting to US when I click anywhere on screen
https://bugs.kde.org/show_bug.cgi?id=454223 Andrey changed: What|Removed |Added CC||aleix...@kde.org --- Comment #16 from Andrey --- (In reply to stalkermar from comment #15) > There was a widget called Input Method. And as soon as I removed it from the > panel, everything just started working again. I'm sure I didn't add it, the > thing have just appeared on me after the update. No matter how many times I > close it, the thing just re-appears after a reboot. Input Method is the usual source of such problems. But I completely unaware how it was introduced and why it re-appears. You can try forcibly disable the applet in Systray settings. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 454223] Keyboard Layout keeps resetting to US when I click anywhere on screen
https://bugs.kde.org/show_bug.cgi?id=454223 --- Comment #14 from Andrey --- (In reply to stalkermar from comment #3) > Graphics Platform: X11 What's on Wayland? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 454223] Keyboard Layout keeps resetting to US when I click anywhere on screen
https://bugs.kde.org/show_bug.cgi?id=454223 --- Comment #13 from Andrey --- (In reply to stalkermar from comment #4) > It actually worked fine on 20.04, so your best bet would be to reproduce it > like this: > > 1. Install Kubuntu 20.04 > 2. Add 1 more input language > 3. Update the distro to 21.10. I guess I've used this manual: > https://help.ubuntu.com/community/JammyUpgrades/Kubuntu > 4. Reboot. > 5. Update to the "latest and greatest" distro- 22.10 > 6. Reboot > 7. Observe the issue. So it might be upgrade issue, can you reproduce yourself in VM? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 454223] Keyboard Layout keeps resetting to US when I click anywhere on screen
https://bugs.kde.org/show_bug.cgi?id=454223 --- Comment #12 from Andrey --- (In reply to stalkermar from comment #0): > https://askubuntu.com/questions/1330324/kde-plasma-5-undesireable-keyboard- > layout-switching-behavior Did you try to follow the tips suggested? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 454223] Keyboard Layout keeps resetting to US when I click anywhere on screen
https://bugs.kde.org/show_bug.cgi?id=454223 --- Comment #10 from Andrey --- Do you have some ibus stuff installed maybe? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 440663] New Dolphin window or tab opened after compression/extraction when certain default options are disabled, or when the job is canceled, or when the Dolphin window that initiated i
https://bugs.kde.org/show_bug.cgi?id=440663 --- Comment #74 from Andrey --- (In reply to Nate Graham from comment #35) > When the "Open new folders > in tabs" and "Show on Startup: Folder, tabs, and window state from last > time" options are in use, everything is fine. When one or both are > unchecked, the issue re-appears. Actually it's the option name just misleading. When "Open new folders in tabs" is unchecked, it doesn't even try to attach to existing Dolphin instances and opens a new window(s) unconditionally. So the option should be inverted and named something like: "Open new folders in windows" instead. Whether or not to open a new tabs is actually depends on if the containing dir is opened anywhere in one of existing Dolphin instances. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 440663] New Dolphin window or tab opened after compression/extraction when certain default options are disabled, or when the job is canceled, or when the Dolphin window that initiated i
https://bugs.kde.org/show_bug.cgi?id=440663 Andrey changed: What|Removed |Added URL||https://invent.kde.org/syst ||em/dolphin/-/merge_requests ||/400 --- Comment #73 from Andrey --- The real fix is here: https://invent.kde.org/system/dolphin/-/merge_requests/400 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450996] Windows needing attention do not get the "needs attention" status in the Task Manager on wayland
https://bugs.kde.org/show_bug.cgi?id=450996 --- Comment #11 from Andrey --- (In reply to Nate Graham from comment #10) > Hmm, sounds kind of like their implementation might be buggy. This doesn't happen in Gnome Wayland session, with the very same apps. Maybe different mechanism is used there, I don't know. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450996] Windows needing attention do not get the "needs attention" status in the Task Manager on wayland
https://bugs.kde.org/show_bug.cgi?id=450996 --- Comment #9 from Andrey --- For me it doesn't even always open link from Thunderbird, but sometimes it does. Works very unstable. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450996] Windows needing attention do not get the "needs attention" status in the Task Manager on wayland
https://bugs.kde.org/show_bug.cgi?id=450996 Andrey changed: What|Removed |Added CC||butir...@gmail.com --- Comment #7 from Andrey --- (In reply to Nate Graham from comment #5) > It requires that the app in question actually request activation, though. > All KDE apps do at this point, but some 3rd-party apps do not, notable > Firefox and Thunderbird, in my testing. So it's up to them to implement the > Wayland activation protocol. Isn't it the implementation for FF? https://bugzilla.mozilla.org/show_bug.cgi?id=1692119 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 440663] New Dolphin window or tab opened after compression/extraction when certain default options are disabled, or when the job is canceled, or when the Dolphin window that initiated i
https://bugs.kde.org/show_bug.cgi?id=440663 --- Comment #72 from Andrey --- Patch here (unmerged) might be related as it fixed extra tab opening for me, even with the "Do not highlight file after compression" patch above reverted: https://invent.kde.org/system/dolphin/-/merge_requests/270 -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 426499] Draggable area not clearly signposted/misleading highlighting
https://bugs.kde.org/show_bug.cgi?id=426499 --- Comment #13 from Andrey --- (In reply to Joe Dight from comment #10) > I can't see if the lighter/darker split also exists on hover, when > no selection has been made. > If it does (or is made obvious somehow else) the bug is definitely fixed. The latest MR addresses this, could you have a look Joe? https://invent.kde.org/utilities/ark/-/merge_requests/118 -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 426499] Draggable area not clearly signposted/misleading highlighting
https://bugs.kde.org/show_bug.cgi?id=426499 Andrey changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #12 from Andrey --- Please consider this: https://invent.kde.org/utilities/ark/-/merge_requests/118 Hovered (with cursor) and selected rows are still in style but now both have clear color separation of draggable area. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 453892] kde system settings crash 20.04
https://bugs.kde.org/show_bug.cgi?id=453892 --- Comment #4 from Andrey --- 2 weeks ago. I was running out of space in the /user directory. Found the directory in which there was a database. It kept growing and occupied the entire disk. I had to remove it. After that everything works well. Problems with the settings menu just now noticed. ~/.local/share/kactivitymanagerd/resources/ Perhaps this is related... пн, 16 мая 2022 г. в 22:15, Nate Graham : > https://bugs.kde.org/show_bug.cgi?id=453892 > > Nate Graham changed: > >What|Removed |Added > > > Resolution|WAITINGFORINFO |--- > Status|NEEDSINFO |REPORTED > > --- Comment #3 from Nate Graham --- > Darn, that seems bad. > > Unfortunately I am unsure how to proceed because the backtrace doesn't > suggest > that any KDE code is at fault. I suspect a local installation issue, or > else an > upstream Qt issue. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 453892] kde system settings crash 20.04
https://bugs.kde.org/show_bug.cgi?id=453892 --- Comment #2 from Andrey --- I just run system settings. Video: https://youtu.be/BtJ_Z2Lw4ug пн, 16 мая 2022 г. в 21:20, Nate Graham : > https://bugs.kde.org/show_bug.cgi?id=453892 > > Nate Graham changed: > >What|Removed |Added > > > Status|REPORTED|NEEDSINFO > CC||n...@kde.org > Component|general |generic-crash > Resolution|--- |WAITINGFORINFO > > --- Comment #1 from Nate Graham --- > No KDE code is implicated in the backtrace. > > What were you doing when it crashed? > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 453892] New: kde system settings crash 20.04
https://bugs.kde.org/show_bug.cgi?id=453892 Bug ID: 453892 Summary: kde system settings crash 20.04 Product: systemsettings Version: 5.24.5 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: autoxar...@gmail.com Target Milestone: --- Application: systemsettings (5.24.5) (Compiled from sources) Qt Version: 5.15.3 Frameworks Version: 5.93.0 Operating System: Linux 5.13.0-41-generic x86_64 Windowing System: X11 Distribution: KDE neon User - 5.24 DrKonqi: 5.24.5 [KCrashBackend] -- Information about the crash: kde system settings crash 20.04 The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings), signal: Segmentation fault [New LWP 14342] [New LWP 14343] [New LWP 14344] [New LWP 14350] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". futex_wait_cancelable (private=, expected=0, futex_word=0x557c9a317134) at ../sysdeps/nptl/futex-internal.h:183 __preamble__ [Current thread is 1 (Thread 0x7f662e0ef9c0 (LWP 14340))] Thread 5 (Thread 0x7f6603fff700 (LWP 14350)): [KCrash Handler] #4 QV4::CompiledData::TypeReferenceMap::collectFromObject (obj=0x7f660a0f6018, this=0x7f65f821e0d8) at ../../include/QtQml/5.15.3/QtQml/private/../../../../../src/qml/common/qv4compileddata_p.h:845 #5 QQmlTypeData::tryLoadFromDiskCache (this=this@entry=0x7f65f821e030) at qml/qqmltypedata.cpp:162 #6 0x7f6631909a53 in QQmlTypeData::dataReceived (this=0x7f65f821e030, data=...) at qml/qqmltypedata.cpp:580 #7 0x7f66319623f6 in QQmlTypeLoader::setData (this=this@entry=0x557c9a4ebc28, blob=blob@entry=0x7f65f821e030, d=...) at qml/qqmltypeloader.cpp:447 #8 0x7f66319627a8 in QQmlTypeLoader::setData (this=this@entry=0x557c9a4ebc28, blob=blob@entry=0x7f65f821e030, fileName=...) at qml/qqmltypeloader.cpp:437 #9 0x7f6631962db4 in QQmlTypeLoader::loadThread (this=this@entry=0x557c9a4ebc28, blob=blob@entry=0x7f65f821e030) at qml/qqmltypeloader.cpp:299 #10 0x7f663196931c in PlainLoader::loadThread (this=0x7f6603ffdf17, blob=0x7f65f821e030, loader=0x557c9a4ebc28) at qml/qqmltypeloader.cpp:146 #11 QQmlTypeLoader::doLoad (this=this@entry=0x557c9a4ebc28, loader=..., blob=blob@entry=0x7f65f821e030, mode=mode@entry=QQmlTypeLoader::PreferSynchronous) at qml/qqmltypeloader.cpp:205 #12 0x7f663196311a in QQmlTypeLoader::load (this=this@entry=0x557c9a4ebc28, blob=blob@entry=0x7f65f821e030, mode=mode@entry=QQmlTypeLoader::PreferSynchronous) at qml/qqmltypeloader.cpp:237 #13 0x7f6631964cc8 in QQmlTypeLoader::getType (this=this@entry=0x557c9a4ebc28, unNormalizedUrl=..., mode=mode@entry=QQmlTypeLoader::PreferSynchronous) at qml/qqmltypeloader.cpp:825 #14 0x7f663190b566 in QQmlTypeData::resolveTypes (this=this@entry=0x7f65f8005a50) at ../../include/QtQml/5.15.3/QtQml/private/../../../../../src/qml/qml/qqmldatablob_p.h:95 #15 0x7f663190d85d in QQmlTypeData::allDependenciesDone (this=0x7f65f8005a50) at qml/qqmltypedata.cpp:743 #16 0x7f66319624c2 in QQmlTypeLoader::setData (this=this@entry=0x557c9a4ebc28, blob=blob@entry=0x7f65f8005a50, d=...) at qml/qqmltypeloader.cpp:450 #17 0x7f66319627a8 in QQmlTypeLoader::setData (this=this@entry=0x557c9a4ebc28, blob=blob@entry=0x7f65f8005a50, fileName=...) at qml/qqmltypeloader.cpp:437 #18 0x7f6631962db4 in QQmlTypeLoader::loadThread (this=this@entry=0x557c9a4ebc28, blob=blob@entry=0x7f65f8005a50) at qml/qqmltypeloader.cpp:299 #19 0x7f663196931c in PlainLoader::loadThread (this=0x7f6603ffe2d7, blob=0x7f65f8005a50, loader=0x557c9a4ebc28) at qml/qqmltypeloader.cpp:146 #20 QQmlTypeLoader::doLoad (this=this@entry=0x557c9a4ebc28, loader=..., blob=blob@entry=0x7f65f8005a50, mode=mode@entry=QQmlTypeLoader::PreferSynchronous) at qml/qqmltypeloader.cpp:205 #21 0x7f663196311a in QQmlTypeLoader::load (this=this@entry=0x557c9a4ebc28, blob=blob@entry=0x7f65f8005a50, mode=mode@entry=QQmlTypeLoader::PreferSynchronous) at qml/qqmltypeloader.cpp:237 #22 0x7f6631964cc8 in QQmlTypeLoader::getType (this=this@entry=0x557c9a4ebc28, unNormalizedUrl=..., mode=mode@entry=QQmlTypeLoader::PreferSynchronous) at qml/qqmltypeloader.cpp:825 #23 0x7f663190b566 in QQmlTypeData::resolveTypes (this=this@entry=0x557c9ad1f030) at ../../include/QtQml/5.15.3/QtQml/private/../../../../../src/qml/qml/qqmldatablob_p.h:95 #24 0x7f663190d85d in QQmlTypeData::allDependenciesDone (this=0x557c9ad1f030) at qml/qqmltypedata.cpp:743 #25 0x7f66319624c2 in QQmlTypeLoader::setData (this=this@entry=0x557c9a4ebc28, blob=blob@entry=0x557c9ad1f030, d=...) at qml/qqmltypeloader.cpp:450 #26 0x7f66319627a8 in QQmlTypeLoader::setData (this=this@entry=0x557c9a4ebc28, blob=blob@entry=0x557c9ad1f030, fileName=...) at qml/qqmltypeloader.cpp:437
[ark] [Bug 426499] Draggable area not clearly signposted/misleading highlighting
https://bugs.kde.org/show_bug.cgi?id=426499 --- Comment #11 from Andrey --- Thanks for replies. (In reply to Joe Dight from comment #10) > I can't see if the lighter/darker split also exists on hover, when > no selection has been made. > If it does (or is made obvious somehow else) the bug is definitely fixed. No, it doesn't. It wasn't clear from the report so I didn't pay much attention to hover. However, in previous version I cut off the hover highlight: https://invent.kde.org/utilities/ark/-/merge_requests/115#note_447960 It doesn't look in-style with recent selection highlights though as I tend to keep full-row selection. I'll see if similar color split can be implemented for hover highlight too. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 426499] Draggable area not clearly signposted/misleading highlighting
https://bugs.kde.org/show_bug.cgi?id=426499 --- Comment #8 from Andrey --- An attempt was made to fix it non-destructively using different colors for draggable and non-draggable areas. Here is how it looks like: https://invent.kde.org/utilities/ark/-/merge_requests/115#note_447931 There are different opinions if it actually fixes the bug. I would love to know what OP thinks about it. Joe, please reply if you read this. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 453661] Shortcuts are not working across multiple keyboard layouts (US and CZ for me)
https://bugs.kde.org/show_bug.cgi?id=453661 --- Comment #3 from Andrey --- "This is also inconsistent as ``SUPER + 9` (`SUPER + Í`) was not problematic before but after 2 days of this happening it started to be. Also `SUPER + 2` (`SUPER + Ě`) was problematic in the beginning but is not anymore." I would try to investigate that consistent in time. Reproducing in VM/new user would also help. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 426499] Draggable area not clearly signposted/misleading highlighting
https://bugs.kde.org/show_bug.cgi?id=426499 --- Comment #7 from Andrey --- Hmm, I tried to attach the screenshot but seem can't do that any more. Any help? -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 426499] Draggable area not clearly signposted/misleading highlighting
https://bugs.kde.org/show_bug.cgi?id=426499 Andrey changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/util ||ities/ark/commit/15bccd6a1d ||0514089729ff1422e9b83cde19d ||5bd Status|ASSIGNED|RESOLVED --- Comment #5 from Andrey --- Git commit 15bccd6a1d0514089729ff1422e9b83cde19d5bd by Andrey Butirsky. Committed on 12/05/2022 at 17:56. Pushed by butirsky into branch 'master'. fix draggable area not clearly signposted/misleading highlighting M +2-3part/archivemodel.cpp M +13 -0part/archiveview.cpp M +11 -0part/archiveview.h M +3-0part/part.cpp https://invent.kde.org/utilities/ark/commit/15bccd6a1d0514089729ff1422e9b83cde19d5bd -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 453506] Need to kick hotkeys on release, not press
https://bugs.kde.org/show_bug.cgi?id=453506 --- Comment #3 from Andrey --- (In reply to George from comment #2) > But if I: > 1) Open the KDE System Settings GUI -> Input Devices -> Keyboard -> Advanced > 2) Check the "Configure keyboard options" > 3) Expand "Switching to another layout" > 4) Pick any one of this bunch, for example: left alt, left ctrl, left win, > left shift (and uncheck the rest) > 5) And click Apply > > Then it would work on press anyway, I'm sorry to say. This is normal. Both Xorg and libxkbcommon implement triggering on press due historical reasons. With modifiers only shortcuts we have KWin-specific workaround. We could bind "change to the next layout" dbus function to some modifier key instead of XKB way you described, but that would work for single modifier only I guess.. (need to confirm) Theoretically we could implement combinations, too. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 375518] global shortcuts do not work for non-Latin symbols of foreign keyboard layouts
https://bugs.kde.org/show_bug.cgi?id=375518 Andrey changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=453461 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 453461] X11: Changing keyboard layout order stops most shortcuts from working
https://bugs.kde.org/show_bug.cgi?id=453461 Andrey changed: What|Removed |Added Summary|Changing keyboard layout|X11: Changing keyboard |order stops most shortcuts |layout order stops most |from working|shortcuts from working Resolution|UPSTREAM|--- Ever confirmed|0 |1 Status|RESOLVED|REOPENED See Also||https://bugs.kde.org/show_b ||ug.cgi?id=375518 --- Comment #8 from Andrey --- Potentially still can be fixed on Plasma side, see comment: https://bugs.kde.org/show_bug.cgi?id=309193#c74 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 453461] Changing keyboard layout order stops most shortcuts from working
https://bugs.kde.org/show_bug.cgi?id=453461 Andrey changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=309193 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 309193] Keyboard shortcuts doesn't work if non-english keyboard layout is set before english one
https://bugs.kde.org/show_bug.cgi?id=309193 Andrey changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED See Also||https://bugs.kde.org/show_b ||ug.cgi?id=453461 --- Comment #76 from Andrey --- Assuming this bug is opened for local shortcuts, closing as fixed in Qt. For global shortcuts, it was fixed in KWin for Wayland, for X11 see my notes above. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 453506] Need to kick hotkeys on release, not press
https://bugs.kde.org/show_bug.cgi?id=453506 Andrey changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from Andrey --- IIRC Kwin's Modifier only shortcuts are trigger on release, could you check that? I don't know if we have them documented, here are the links: https://blog.martin-graesslin.com/blog/2016/08/modifier-only-shortcuts-available-in-plasma-5-8/ https://bucharjan.cz/blog/plasma-custom-modifier-only-shortcuts.html -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 444228] Dolphin can't delete files - "an older item named 'trash:/' already exists"
https://bugs.kde.org/show_bug.cgi?id=444228 Andrey Fedoseev changed: What|Removed |Added CC||and...@andreyfedoseev.com --- Comment #3 from Andrey Fedoseev --- I had the same issue, but in my case it was a user error. While migrating my home folder to another OS installation, I accidentally break the `~/.local/share/Trash` folder: its contents became incomplete, and some files there ended up being owned by the `root` user. Simply removing `~/.local/share/Trash` and restarting Dolphin fixed the issue for me. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 453461] Changing keyboard layout order stops most shortcuts from working
https://bugs.kde.org/show_bug.cgi?id=453461 Andrey changed: What|Removed |Added Resolution|--- |UPSTREAM Status|REPORTED|RESOLVED --- Comment #7 from Andrey --- If you place redundant US layout on the first place, the order of others shouldn't matter on X11. Sorry but I don't think this bug will ever be fixed in X11. Closing as upstream. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 453461] Changing keyboard layout order stops most shortcuts from working
https://bugs.kde.org/show_bug.cgi?id=453461 --- Comment #5 from Andrey --- That is the problem I referred to. Please try Wayland. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 453461] Changing keyboard layout order stops most shortcuts from working
https://bugs.kde.org/show_bug.cgi?id=453461 --- Comment #3 from Andrey --- On X11, layout containing latin symbols should go fist due X11 implementation. We can nothing to do with it. Is it your problem? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 453461] Changing keyboard layout order stops most shortcuts from working
https://bugs.kde.org/show_bug.cgi?id=453461 --- Comment #1 from Andrey --- Does it persist after reboot? -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 426499] Draggable area not clearly signposted/misleading highlighting
https://bugs.kde.org/show_bug.cgi?id=426499 Andrey changed: What|Removed |Added URL||https://invent.kde.org/util ||ities/ark/-/merge_requests/ ||115 --- Comment #4 from Andrey --- https://invent.kde.org/utilities/ark/-/merge_requests/115 -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 426499] Draggable area not clearly signposted/misleading highlighting
https://bugs.kde.org/show_bug.cgi?id=426499 Andrey changed: What|Removed |Added Assignee|elvis.angelac...@kde.org|butir...@gmail.com CC||butir...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 452445] per-application keyboard layout not persisting
https://bugs.kde.org/show_bug.cgi?id=452445 --- Comment #13 from Andrey --- I didn't try how it works on X11 but it also makes sense to check it for Wayland, maybe in separate report. IIRC the layout is only saved there for apps instantiating itself (e.g opening a new window in Konsole). So if Telegram is closed to tray, no layout restoration takes place on reopening. That might be more attractive point to apply the efforts. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 452352] Calculate total directory size
https://bugs.kde.org/show_bug.cgi?id=452352 --- Comment #4 from Andrey --- Please note the sizes calculation in the patch is synchronous. If anyone had opportunity to test it on really big archives to estimate performance penalty, that would be helpful. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 452352] Calculate total directory size
https://bugs.kde.org/show_bug.cgi?id=452352 --- Comment #3 from Andrey --- Ragnar, could you follow up on your comment here? https://invent.kde.org/utilities/ark/-/blob/master/part/archivemodel.cpp#L822: > When ArchiveModel has been properly fixed, this code can likely be removed. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 452352] Calculate total directory size
https://bugs.kde.org/show_bug.cgi?id=452352 Andrey changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/util ||ities/ark/commit/3981425a61 ||c544a99ad7ab0c7228464e6430e ||b08 --- Comment #2 from Andrey --- Git commit 3981425a61c544a99ad7ab0c7228464e6430eb08 by Andrey Butirsky. Committed on 22/04/2022 at 09:45. Pushed by butirsky into branch 'master'. Calculate total directory size M +9-12 part/archivemodel.cpp M +1-2part/archivemodel.h M +1-1part/infopanel.cpp M +13 -7part/part.cpp https://invent.kde.org/utilities/ark/commit/3981425a61c544a99ad7ab0c7228464e6430eb08 -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 452352] Calculate total directory size
https://bugs.kde.org/show_bug.cgi?id=452352 Andrey changed: What|Removed |Added Status|CONFIRMED |ASSIGNED -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 452352] Calculate total directory size
https://bugs.kde.org/show_bug.cgi?id=452352 Andrey changed: What|Removed |Added URL||https://invent.kde.org/util ||ities/ark/-/merge_requests/ ||114 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 437374] System logs out instead of going to sleep
https://bugs.kde.org/show_bug.cgi?id=437374 --- Comment #7 from Andrey Fedoseev --- Ok, the issue is resolved, this time for real. It is actually related to the Nvidia drivers. Removing the Nvidia drivers leaves the following broken symlinks: /etc/systemd/system/systemd-hibernate.service.requires/nvidia-hibernate.service /etc/systemd/system/systemd-hibernate.service.requires/nvidia-resume.service /etc/systemd/system/systemd-suspend.service.requires/nvidia-resume.service /etc/systemd/system/systemd-suspend.service.requires/nvidia-suspend.service Removing those symlinks fixes the issue with `systemctl suspend` -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 437374] System logs out instead of going to sleep
https://bugs.kde.org/show_bug.cgi?id=437374 --- Comment #5 from Andrey Fedoseev --- @Nate Thank you for the reply. I agree that the issue may be at a deeper level. However, it manifests itself at the desktop environment level, at least I don't have another means to reproduce it. It doesn't crash the system, the X server keeps running, the login manager keeps running. It's the plasma session that gets terminated somehow. Do you have any suggestions about how I can better track the source of the problem? -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 437374] System logs out instead of going to sleep
https://bugs.kde.org/show_bug.cgi?id=437374 --- Comment #3 from Andrey Fedoseev --- The issue was resolved for me after I switched to another processor and GPU (Ryzen 5800X + GeForce 1080ti) a while ago, but now it's back after I switched GPU to Radeon 6700XT. In my case, it seems to correlate with the GPU being used: I had the issue with AMD graphics, but it was working with nvidia, so it may be related to the graphical stack. The current workaround for me is to use `sudo pm-suspend` instead of the built-in Sleep functions in Plasma. As stated in the original description, `sudo pm-suspend` works fine but `systemctl suspend` or any "sleep" function in Plasma causes immediate log out instead of going to sleep. My updated system information is: Operating System: KDE neon 5.24 KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 Kernel Version: 5.14.0-1032-oem (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 5800X 8-Core Processor Memory: 62,7 GiB of RAM Graphics Processor: AMD Radeon RX 6700 XT -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434713] Nothing happens when I press the keyboard shortcut of Keyboard Layout applet by the first time
https://bugs.kde.org/show_bug.cgi?id=434713 --- Comment #14 from Andrey --- Thanks you for let us know, Chris -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 452759] OSD of keyboard layout unnecessarily appears when I start to type on Wayland
https://bugs.kde.org/show_bug.cgi?id=452759 --- Comment #7 from Andrey --- That suppression might be a hacky as we don't have an easy way to handle this situation, AFAIK. But yes I remember I faced something like this when I implemented all this stuff, so thank you for the catch anyway. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 452759] OSD of keyboard layout unnecessarily appears when I start to type on Wayland
https://bugs.kde.org/show_bug.cgi?id=452759 Andrey changed: What|Removed |Added Status|NEEDSINFO |CONFIRMED Resolution|WAITINGFORINFO |--- --- Comment #5 from Andrey --- There is still point - it reminds you the layout has changed implicitly -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 452759] OSD of keyboard layout unnecessarily appears when I start to type on Wayland
https://bugs.kde.org/show_bug.cgi?id=452759 --- Comment #3 from Andrey --- Ok. Then it's side-effect of the implementation. Do you think it can't be considered as a "feature", still? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 452759] OSD of keyboard layout unnecessarily appears when I start to type on Wayland
https://bugs.kde.org/show_bug.cgi?id=452759 Andrey changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|CONFIRMED |NEEDSINFO --- Comment #1 from Andrey --- What is your Layout switching policy - is it Global or per App/Window? IIRC, the logic behind that behavior with App/Window policy is following: - on login, last used layout is restored, but for the window currently active only (which might be Desktop itself or so), as if you had changed it yourself - when you open a new app (Kate), it has internally saved "last used" layout initialized to a first layout which is US in your list - when the app got activated, the current layout is compared to a saved one for this app/window. If they differ, OSD happens which you got here The same logic will probably take place with App/Window policy even without logout/login. Can we perceive it as a feature as a logic behind is pretty solid? I'm afraid we would need hacks to suppress it. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 452352] Calculate total directory size
https://bugs.kde.org/show_bug.cgi?id=452352 Andrey changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 452352] Calculate total directory size
https://bugs.kde.org/show_bug.cgi?id=452352 Andrey changed: What|Removed |Added Assignee|elvis.angelac...@kde.org|butir...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 452352] Calculate total directory size
https://bugs.kde.org/show_bug.cgi?id=452352 Andrey changed: What|Removed |Added CC||butir...@gmail.com --- Comment #1 from Andrey --- I'm going to look at this -- You are receiving this mail because: You are watching all bug changes.
