[plasmashell] [Bug 411729] Greek accents and dead keys do not work in Debian Stable
https://bugs.kde.org/show_bug.cgi?id=411729 --- Comment #7 from Johann Höchtl --- As I see it right now, for those where installing ibus and adding the env variables to /etc/environment (PAM) works, it is a packing / distribution issue. Whether this IS the actual solution OR has to been tackled otherwise has to be decided from a Plasma architectural perspective. Gnome is not affected as the ibus setting is assumed, even in absence of the set environment variables, KDE doesn't implement the fallback. BTW. currently emerges another (more modern?) approach to let system.d set these variables on a per-user session, but this is a different topic. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 411729] Greek accents and dead keys do not work in Debian Stable
https://bugs.kde.org/show_bug.cgi?id=411729 --- Comment #4 from Johann Höchtl --- try to add this to /etc/environment INPUT_METHOD=ibus GTK_IM_MODULE=ibus QT_IM_MODULE=ibus XMODIFIERS=@im=ibus Do accents work afterwards? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417115] Apps launched with "Run in terminal" not working under wayland
https://bugs.kde.org/show_bug.cgi?id=417115 Johann Höchtl changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #6 from Johann Höchtl --- So this is very likely a duplicate of #408497 I cannot add more specifics. My suspicion for the bug I described is that the command shell used to display console programs when running under X is set in places which are not read when running under Wayland. This is just an assumption. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417115] Apps launched with "Run in terminal" not working under wayland
https://bugs.kde.org/show_bug.cgi?id=417115 --- Comment #3 from Johann Höchtl --- The problem I have originally reported is that when I am running plasma under wayland, a menu entry for neovim is set to [x] Run in terminal. This does not work, as no terminal is opened. This works when running under X My suspicion is, that for this to work, environment variables are required to be set? I only noticed that none of the environment variables set eg. in .profiles or .bashrc are available to programs started from the KDE start menu because the way the kwin_wayland user session is spawned, does not require a login shell. And maybe this is the reason too that the [ ] Run in terminal option does not work? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwayland] [Bug 417345] New: Wayland Plasma keyboard layout locked to English
https://bugs.kde.org/show_bug.cgi?id=417345 Bug ID: 417345 Summary: Wayland Plasma keyboard layout locked to English Product: frameworks-kwayland Version: 5.66.0 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mgraess...@kde.org Reporter: johann.hoec...@gmail.com CC: kwin-bugs-n...@kde.org Target Milestone: --- SUMMARY Using Wayland plasma, the keyboard layout is locked to English STEPS TO REPRODUCE 1. Open System settings, Keyboard settings 2. The layout is set to English (US) 3. Change layout to eg. German (prompted for root credentials) 4. Save 5. Logout 6. Login again OBSERVED RESULT 1. See keyboard layout set again to English (US) EXPECTED RESULT Keyboard layout set to German SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.66.0 Qt Version: 5.14.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwayland] [Bug 417115] Kicker Run in terminal not working under wayland
https://bugs.kde.org/show_bug.cgi?id=417115 --- Comment #1 from Johann Höchtl --- I think the titel should be changed as the problem is actually a more fundamental one (I think) Wayland plasma seems to be spawned without using a shell at at all. As such some important environment variables get not set. The way to go seems to be to define user environment variables in ~/.config/environment.d/.conf systemctl --user show-environment will output environment variables configured there, cf. https://github.com/systemd/systemd/pull/5131 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwayland] [Bug 417161] New: compose keys do not work under wayland QT
https://bugs.kde.org/show_bug.cgi?id=417161 Bug ID: 417161 Summary: compose keys do not work under wayland QT Product: frameworks-kwayland Version: 5.66.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mgraess...@kde.org Reporter: johann.hoec...@gmail.com Target Milestone: --- SUMMARY compose keys do not work STEPS TO REPRODUCE 1. German keyboard, open any QT application enter ´e OBSERVED RESULT 1. only e is displayed EXPECTED RESULT é is printed SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.66.0 Qt Version: 5.14.0 ADDITIONAL INFORMATION Does work in GTK-applications, eg. firefox Does work if the following is entererd into /etc/environment INPUT_METHOD=ibus GTK_IM_MODULE=ibus QT_IM_MODULE=ibus XMODIFIERS=@im=ibus (none of the lines above are required for Wayland GTK-Apps to work) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwayland] [Bug 417115] New: Kicker Run in terminal not working under wayland
https://bugs.kde.org/show_bug.cgi?id=417115 Bug ID: 417115 Summary: Kicker Run in terminal not working under wayland Product: frameworks-kwayland Version: 5.66.0 Platform: unspecified OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: mgraess...@kde.org Reporter: johann.hoec...@gmail.com Target Milestone: --- SUMMARY When starting vim from Kicker under wayland, nothing happens. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT vim (and likely any other application with "Run in terminal" option set) opens within terminal application Linux/KDE Plasma: KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.66.0 Qt Version: 5.14.0 ADDITIONAL INFORMATION Works in Plasma on X -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 413524] Files appear multiple times in Baloo search output
https://bugs.kde.org/show_bug.cgi?id=413524 --- Comment #5 from Johann Höchtl --- It may be relevant that my files system is BTRFS and home is on a sub-volumen. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 413524] Files appear multiple times in dolphin search output
https://bugs.kde.org/show_bug.cgi?id=413524 --- Comment #3 from Johann Höchtl --- @Nate Yes -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 413524] Files appear multiple times in dolphin search output
https://bugs.kde.org/show_bug.cgi?id=413524 --- Comment #1 from Johann Höchtl --- Likely related / the same as 401863 ? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 413524] New: Files appear multiple times in dolphin search output
https://bugs.kde.org/show_bug.cgi?id=413524 Bug ID: 413524 Summary: Files appear multiple times in dolphin search output Product: frameworks-baloo Version: 5.62.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: stefan.bru...@rwth-aachen.de Reporter: johann.hoec...@gmail.com Target Milestone: --- Created attachment 123522 --> https://bugs.kde.org/attachment.cgi?id=123522=edit screenshot of duplicate files SUMMARY: Files appear multiple times in dolphin search output STEPS TO REPRODUCE 1. Open search in Dolphin CTRL-F 2. Enter a search termin which is found at least once within your files OBSERVED RESULT Files appear multiple times EXPECTED RESULT Matching files appear just once SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.13.1 Kernel Version: 5.3.6-1-MANJARO OS Type: 64-bit Additional Info: When I toggle using the Buttons From Here (username) | Your files duplicate files disapear -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwayland] [Bug 411729] Greek accents and dead keys do not work in Debian Stable
https://bugs.kde.org/show_bug.cgi?id=411729 Johann Höchtl changed: What|Removed |Added Platform|Debian stable |unspecified Assignee|dolphin-bugs-n...@kde.org |mgraess...@kde.org Version|18.08.0 |5.62.0 Keywords||regression, wayland Product|dolphin |frameworks-kwayland CC||johann.hoec...@gmail.com Component|general |general --- Comment #1 from Johann Höchtl --- I am adding to this bug as I am relatively certain, that I am affected by the same bug. Using Manjaro Operating System: Manjaro Linux KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.13.1 Kernel Version: 5.3.6-1-MANJARO under Wayland. My locale says: localectl System Locale: LANG=en_US.UTF-8 LC_NUMERIC=de_AT.UTF-8 LC_TIME=de_AT.UTF-8 LC_MONETARY=de_AT.UTF-8 LC_PAPER=de_AT.UTF-8 LC_NAME=de_AT.UTF-8 LC_ADDRESS=de_AT.UTF-8 LC_TELEPHONE=de_AT.UTF-8 LC_MEASUREMENT=de_AT.UTF-8 LC_IDENTIFICATION=de_AT.UTF-8 VC Keymap: de-latin1 X11 Layout: de X11 Model: pc105 X11 Options: terminate:ctrl_alt_bksp When I try to enter dead keys under that layout like é (´ followeg by the letter e) or ê (^ followed by the letter e) in native KDE applications, these letters get ignored. Strangely, they are also ignored in OpenOffice. Dead letter entry works in GTK-Applications like firefox or thunderbird. They also work at the console. May be related to #411729 ? This is NOT exclusive to Dolphin, therefore re-assigning to frameworks-wayland -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384762] New: Modifier keyboard sequences are not entirely consumed by application and propagated to other application
https://bugs.kde.org/show_bug.cgi?id=384762 Bug ID: 384762 Summary: Modifier keyboard sequences are not entirely consumed by application and propagated to other application Product: plasmashell Version: 5.10.5 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: johann.hoec...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 This is very easy to reproduce: Start Wayland session Start firefox Sart Konsole Close Konsole with keyboard sequence CTRL-D Firefox will ask you to bookmark the currently active webpage because the keyboard sequence to close Konsole gets not consumed but propagated to Firefox. This is true for other keyboard sequences as well, eg. Open Firefox Open Emacs Close Emacs with ALT-F4 Firefox will show the menu bar which is shown when pressing the ALT modifier -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 370429] New: Baloo should forget about files not to index
https://bugs.kde.org/show_bug.cgi?id=370429 Bug ID: 370429 Summary: Baloo should forget about files not to index Product: frameworks-baloo Version: 5.23.0 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: pinak.ah...@gmail.com Reporter: johann.hoec...@gmail.com When I add a directory to baloo which should not be indexed but was indexed before, the files remain in the index. Instead there should be a logic that these files get removed, preferably with some logic not to peg the CPU. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
