[markdownpart] [Bug 441541] Comments break preview
https://bugs.kde.org/show_bug.cgi?id=441541 Andrew changed: What|Removed |Added CC||travn...@gmail.com --- Comment #13 from Andrew --- (In reply to Friedrich W. H. Kossebau from comment #9) > there are bigger blockers > to make this perfect (starting with embedded images which need proper > internal redirection to load) Is it also related to external images? Pictures described like these are not shown for me: [](#readme) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 353960] automatic new wallet wizard stops with "no suitable key" without hint
https://bugs.kde.org/show_bug.cgi?id=353960 Andrew changed: What|Removed |Added CC||andrew.loe...@gmail.com --- Comment #28 from Andrew --- Plasma 6, 2024, and this is still a thing. Sure, I've been using Linux since 1998 and I know how to generate GPG keys. But here's the thing... a KDE Wallet dialog that pops up every time you connect to wifi or enter any system password only to insist that you don't have any keys, and then doesn't actually tell you how to create them, in an endless loop, is GARBAGE. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 307505] Double click free space to folder up
https://bugs.kde.org/show_bug.cgi?id=307505 Andrew Shark changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #18 from Andrew Shark --- Implemented with https://invent.kde.org/system/dolphin/-/merge_requests/764 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 392798] Power button actions should be handled from lock screen
https://bugs.kde.org/show_bug.cgi?id=392798 --- Comment #27 from Andrew McNabb --- The workaround from comment #23 didn't work for me. I went to Energy Saving and turned off suspending when the power button is pressed (to avoid suspending while trying to create the shortcut), and then I tried to create the shortcut. Unfortunately, when I tried to enter the shortcut key by pressing the power button, nothing happened at all; it just didn't register as a key press. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 392798] Power button actions should be handled from lock screen
https://bugs.kde.org/show_bug.cgi?id=392798 Andrew McNabb changed: What|Removed |Added CC||amcn...@mcnabbs.org -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 472917] Add ability to ignore individual module outside of module-set in config
https://bugs.kde.org/show_bug.cgi?id=472917 Andrew Shark changed: What|Removed |Added Latest Commit|https://invent.kde.org/sdk/ |https://invent.kde.org/sdk/ |kdesrc-build/-/commit/66bff |kdesrc-build/-/commit/24f6b |6dc56039cc75bcc64bc5a7c6fb3 |604e110113070dfef7e3d3951fb |8f9b1e82|e55a1a2f --- Comment #7 from Andrew Shark --- Git commit 24f6b604e110113070dfef7e3d3951fbe55a1a2f by Andrew Shark. Committed on 28/01/2024 at 07:28. Pushed by ashark into branch 'docbook_historied_per_file'. Allow ignoring modules from global config This will let users to constantly ignore specified modules in global section, so they do not need to pass it in command line each time. Also, it will allow to ignore some defined modules that are not in any module set (for example, gpgme). Original commit: 66bff6dc https://invent.kde.org/sdk/kdesrc-build/-/commit/66bff6dc56039cc75bcc64bc5a7c6fb38f9b1e82 M +3-1doc/cmdline/supported-cmdline-params.docbook M +2-2doc/kdesrc-buildrc/conf-options-table.docbook https://invent.kde.org/sdk/kdesrc-build/-/commit/24f6b604e110113070dfef7e3d3951fbe55a1a2f -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 354796] Add no-src configuration option, similar to the command line option
https://bugs.kde.org/show_bug.cgi?id=354796 Andrew Shark changed: What|Removed |Added Latest Commit|https://invent.kde.org/sdk/ |https://invent.kde.org/sdk/ |kdesrc-build/-/commit/d8104 |kdesrc-build/-/commit/68dbc |fa8e9defa5b25f7eab538a7b0f2 |8f847165e08fcd7559df8eefd79 |fc652e1d|71d8a68b --- Comment #10 from Andrew Shark --- Git commit 68dbc8f847165e08fcd7559df8eefd7971d8a68b by Andrew Shark. Committed on 28/01/2024 at 21:24. Pushed by ashark into branch 'docbook_historied_per_file'. Support phase selection individually for modules and module-sets Previously we could only select phases globally from command line. They were applied to all modules. Sometimes user want to control phase selection for individual module. The clone is happening from the remote/origin by default. This becomes a problem when user is working with a local branch that is not presented in remote. For example, user may not have a developer account, or just does not want to upload his work even in work/user branch yet. He just wants kdesrc-build to not touch the sources of that module (while the other modules still be updated), and does not want to exclude module from build phase. Let's say user wants to work with `kio`, and testing it with `ark`. Previously, user could achieve this task by running `kdesrc-build` several times. Different quirks were needed. Example: - `kdesrc-build ark --include-dependencies` - build ark with dependencies (including kio) as normal - `...` - make changes to the kio project - `kdesrc-build kio --no-src --no-include-dependencies` - `kdesrc-build ark --include-dependencies --ignore-modules kio` After this commit user can specify the `no-src` option for the `kio` module, and then just run `kdesrc-build ark --include-dependencies`. The `kio` will not be updated in this process, but will not be excluded from build phase. Original commit: d8104fa8 https://invent.kde.org/sdk/kdesrc-build/-/commit/d8104fa8e9defa5b25f7eab538a7b0f2fc652e1d M +88 -14 doc/kdesrc-buildrc/conf-options-table.docbook https://invent.kde.org/sdk/kdesrc-build/-/commit/68dbc8f847165e08fcd7559df8eefd7971d8a68b -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 308689] Feature Request: Have a flag to display which modules failed to build/install on last run
https://bugs.kde.org/show_bug.cgi?id=308689 Andrew Shark changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |MOVED -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 394195] Warn if current environment variables do not match with the build of other modules
https://bugs.kde.org/show_bug.cgi?id=394195 Andrew Shark changed: What|Removed |Added Resolution|--- |INTENTIONAL Status|REPORTED|RESOLVED CC||ash...@linuxcomp.ru --- Comment #2 from Andrew Shark --- Yes, this can be controlled by set-env for those variables you need. But it already set the needed one. Those the extra - that is your responsibility, not tool's. -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 479938] There's something wrong related to `kaccounts-integration` when being built using Qt5/KF5
https://bugs.kde.org/show_bug.cgi?id=479938 Andrew Shark changed: What|Removed |Added CC||ash...@linuxcomp.ru --- Comment #4 from Andrew Shark --- https://invent.kde.org/sysadmin/repo-metadata/-/issues/17 - currently, there is a problem building this module directly. -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 410805] Use cmake --build and cmake --install instead of calling make directly
https://bugs.kde.org/show_bug.cgi?id=410805 Andrew Shark changed: What|Removed |Added CC||ash...@linuxcomp.ru Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #1 from Andrew Shark --- Currently, Ninja generator is already supported. Use cmake-generator Ninja config option. In the output you can see: Running cmake targeting Ninja... run_logged_command(): Module extra-cmake-modules, Command: cmake -B . -S /home/andrew/kde6/src/extra-cmake-modules -G Ninja -D... Compiling... run_logged_command(): Module extra-cmake-modules, Command: ninja -j 10 Installing extra-cmake-modules run_logged_command(): Module extra-cmake-modules, Command: ninja install -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 484854] Initial setup dependency installation should not fail if one of the dependency is unavailable
https://bugs.kde.org/show_bug.cgi?id=484854 Andrew Shark changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED CC||ash...@linuxcomp.ru --- Comment #1 from Andrew Shark --- Fixed with https://invent.kde.org/sdk/kde-builder/-/commit/49c7a0d105f7fed2ecb12f21bf2a9b7149a3c26c -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478556] Sometimes the stacking order is out of sync with Xorg
https://bugs.kde.org/show_bug.cgi?id=478556
--- Comment #74 from Andrew Shark ---
@vm Thanks for sharing!
And wow, I did not know that you can click on radio button to disable that.
Very counter-intuitive... It should be a radio-button with the check mark ("V")
inside, instead of circle, to indicate that you can disable it as a checkbox.
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 478556] Sometimes the stacking order is out of sync with Xorg
https://bugs.kde.org/show_bug.cgi?id=478556 --- Comment #70 from Andrew Shark --- As a crutch idea, I think one could make a kwin script that switches the virtual desktop forward and backward at any time the jetbrains window (or any x11 window? but experienced most with jetbrains) is moved, resised, activated. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 412257] kiod5 doesn't release usb device when it is not in use
https://bugs.kde.org/show_bug.cgi?id=412257 Andrew changed: What|Removed |Added CC||travn...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478556] Sometimes the stacking order is out of sync with Xorg
https://bugs.kde.org/show_bug.cgi?id=478556 --- Comment #66 from Andrew Shark --- Unfortunately, I did not found that bug report before reporting mine. But for that developer who will go fixing this, I want to make a note, that it is worth checking Comment #64 link, because I have extensively described there two other reproduce methods and attached a video. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478556] Sometimes the stacking order is out of sync with Xorg
https://bugs.kde.org/show_bug.cgi?id=478556 Andrew Shark changed: What|Removed |Added CC||ash...@linuxcomp.ru --- Comment #64 from Andrew Shark --- The bug in the JetBrains youtrack: https://youtrack.jetbrains.com/issue/PY-72228/Input-events-are-passed-to-underlying-X11-window -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 486089] Microphone UI shows opposite option when clicked
https://bugs.kde.org/show_bug.cgi?id=486089 --- Comment #2 from Andrew Baker --- Created attachment 168882 --> https://bugs.kde.org/attachment.cgi?id=168882=edit Behaviour shown when unmuting mic -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 486089] Microphone UI shows opposite option when clicked
https://bugs.kde.org/show_bug.cgi?id=486089 --- Comment #1 from Andrew Baker --- Created attachment 168881 --> https://bugs.kde.org/attachment.cgi?id=168881=edit Behaviour shown when muting mic -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 486089] New: Microphone UI shows opposite option when clicked
https://bugs.kde.org/show_bug.cgi?id=486089 Bug ID: 486089 Summary: Microphone UI shows opposite option when clicked Classification: Plasma Product: plasma-pa Version: 6.0.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: plasma-b...@kde.org Reporter: andrew.ba...@andrewbaker.uk CC: isma...@gmail.com, m...@ratijas.tk Target Milestone: --- SUMMARY Clicking the microphone icon in the panel when using microphone, mutes the mic as expected but then shows the microphone volume level. When the microphone is unmuted it shows Microphone Muted on screen STEPS TO REPRODUCE 1. Open application that uses microphone 2. Click microphone icon to mute 3. Click microphone icon to unmute OBSERVED RESULT Mic volume level shown when muting microphone from panel Microphone muted shown when unmuting microphone from panel EXPECTED RESULT Mic volume level shown when unmuting microphone from panel Microphone muted shown when muting microphone from panel SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora Linux 40 (available in About System) KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[KPipeWire] [Bug 482594] Screen sharing/recording fails with error message "Failed to connect PipeWire context"
https://bugs.kde.org/show_bug.cgi?id=482594 Andrew Simmons changed: What|Removed |Added CC||agsimmo...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 485851] if a window is under another window but part of the window of the window below is visible clicking on it does not return to the front
https://bugs.kde.org/show_bug.cgi?id=485851 --- Comment #5 from andrew --- (In reply to andrew from comment #3) > (In reply to fanzhuyifan from comment #2) > > What are your settings in window management - window behavior - focus - > > raising windows? > > > > Does this happen with windows from any app? > > What are your settings in window management - window behavior - focus > - window activation policy: click to focus > - delay focus by: 300ms > - focus stealing prevention: none > - click raises active window: no > - raise on hover: no > > Does this happen with windows from any app? > - Seems to happen more often with desktop telegram in the front and firefox > below with youtube playing a video. > - is not deterministic, it happens occasionally during long uses > - anyway I use all the default kde options except change the theme to the > dark one, I recently deleted all the configurations folders from my home > - happens on two of my computers both running archlinux and all updated to > date I saw that the current options were not the ones that are set by pressing the "dafault" button, these days I must have tried to change to try to get around the bug, I was able to reproduce it as well after using the options that are set with the "dafault" button - window activation policy: click to focus - delay focus by: 300ms - focus stealing prevention: low - click raises active window: yes - raise on hover: no -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 485851] if a window is under another window but part of the window of the window below is visible clicking on it does not return to the front
https://bugs.kde.org/show_bug.cgi?id=485851 --- Comment #4 from andrew --- (In reply to andrew from comment #3) > (In reply to fanzhuyifan from comment #2) > > What are your settings in window management - window behavior - focus - > > raising windows? > > > > Does this happen with windows from any app? > > What are your settings in window management - window behavior - focus > - window activation policy: click to focus > - delay focus by: 300ms > - focus stealing prevention: none > - click raises active window: no > - raise on hover: no > > Does this happen with windows from any app? > - Seems to happen more often with desktop telegram in the front and firefox > below with youtube playing a video. > - is not deterministic, it happens occasionally during long uses > - anyway I use all the default kde options except change the theme to the > dark one, I recently deleted all the configurations folders from my home > - happens on two of my computers both running archlinux and all updated to > date -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 485851] if a window is under another window but part of the window of the window below is visible clicking on it does not return to the front
https://bugs.kde.org/show_bug.cgi?id=485851 --- Comment #3 from andrew --- (In reply to fanzhuyifan from comment #2) > What are your settings in window management - window behavior - focus - > raising windows? > > Does this happen with windows from any app? What are your settings in window management - window behavior - focus - window activation policy: click to focus - delay focus by: 300ms - focus stealing prevention: none - click raises active window: no - raise on hover: no Does this happen with windows from any app? - Seems to happen more often with desktop telegram in the front and firefox below with youtube playing a video. - is not deterministic, it happens occasionally during long uses - anyway I use all the default kde options except change the theme to the dark one, I recently deleted all the configurations folders from my home - happens on two of my computers both running archlinux and all updated to date -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 406342] kdewebkit fails to build because Qt5WebKitWidgetsConfig.cmake not found
https://bugs.kde.org/show_bug.cgi?id=406342 Andrew Shark changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |UNMAINTAINED --- Comment #5 from Andrew Shark --- kdewebkit is only existing for compatibility currently. It is not used in kf6, and not any module depends on it. See https://mail.kde.org/pipermail/kde-frameworks-devel/2024-April/123493.html So, just do not build this module. -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 406342] kdewebkit fails to build because Qt5WebKitWidgetsConfig.cmake not found
https://bugs.kde.org/show_bug.cgi?id=406342 Andrew Shark changed: What|Removed |Added CC||ash...@linuxcomp.ru Summary|compilation:|kdewebkit fails to build |Qt5WebKitWidgetsConfig.cmak |because |e not found |Qt5WebKitWidgetsConfig.cmak ||e not found -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 484287] kdescr-build missing some dependencies
https://bugs.kde.org/show_bug.cgi?id=484287 Andrew Shark changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED CC||ash...@linuxcomp.ru --- Comment #5 from Andrew Shark --- Not a kde-builder/kdesrc-build bug. Please make an mr here: https://invent.kde.org/sysadmin/repo-metadata/-/tree/master/distro-dependencies?ref_type=heads -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 404487] When building Qt 5, global make options are ignored
https://bugs.kde.org/show_bug.cgi?id=404487
Andrew Shark changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution|--- |FIXED
CC||ash...@linuxcomp.ru
--- Comment #7 from Andrew Shark ---
The qt5-set module-set is handled very differently, it creates a Qt5
supermodule, which then handle building of its submodules itself.
The mentioned mr was merged. The module definitions now contain:
```
module-set qt5-set
set-env MAKEFLAGS -j${num-cores}
end module-set
options qtwebengine
set-env NINJAFLAGS -j${num-cores-low-mem}
end options
```
So the several cores building is no longer a problem.
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 485851] if a window is under another window but part of the window of the window below is visible clicking on it does not return to the front
https://bugs.kde.org/show_bug.cgi?id=485851 --- Comment #1 from andrew --- I tried to create a new account on the computer and it happens as well without changing any configuration, it happens on my work computer as well. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 485851] if a window is under another window but part of the window of the window below is visible clicking on it does not return to the front
https://bugs.kde.org/show_bug.cgi?id=485851 andrew changed: What|Removed |Added Summary|sometimes having a window |if a window is under |partially above another |another window but part of |window clicking in the |the window of the window |window below brings it to |below is visible clicking |the front |on it does not return to ||the front -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 485851] New: sometimes having a window partially above another window clicking in the window below brings it to the front
https://bugs.kde.org/show_bug.cgi?id=485851 Bug ID: 485851 Summary: sometimes having a window partially above another window clicking in the window below brings it to the front Classification: Plasma Product: kwin Version: 6.0.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: core Assignee: kwin-bugs-n...@kde.org Reporter: fand...@protonmail.com Target Milestone: --- SUMMARY for example if i have telegram desktop in the front and firefox under telegram-desktop but a part of firefox is visible, clicking on the visible part of firefox does not return to the front STEPS TO REPRODUCE 1. open a window A 2. open a window B 3. window A is more large than window B 4. window B is in the front 5. click in a visible part of window A OBSERVED RESULT the window A don't brings to the front EXPECTED RESULT brings to the front SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.8.7-zen1-1-zen (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 7800X3D 8-Core Processor Memory: 30.6 GiB of RAM Graphics Processor: AMD Radeon RX 7900 XTX -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 463966] kdesrc-build failed building Qt5 claiming init_repository doesn't exist
https://bugs.kde.org/show_bug.cgi?id=463966 Andrew Shark changed: What|Removed |Added Resolution|--- |UNMAINTAINED CC||ash...@linuxcomp.ru Status|REPORTED|RESOLVED --- Comment #2 from Andrew Shark --- Thanks for the report. I can reproduce the issue in kdesrc-build. This happens because the `_updateRepository()`, and therefore the check for the init-repository file existence and its executable permission `(! -e "$srcdir/init-repository" || ! -x _)` is done before the function to clone/update existing clone was finished. In python (kde-builder) the promise is starting to execute right when it is created (unlike in perl), so it was working correctly in kde-builder already. But just to make the logic proper and to be on a safe side, I have added the promise awaits in the commit linked above). The similar change was needed for kdesrc-build, but it is now feature freeze, please switch to kde-builder. -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 463966] kdesrc-build failed building Qt5 claiming init_repository doesn't exist
https://bugs.kde.org/show_bug.cgi?id=463966 --- Comment #1 from Andrew Shark --- Git commit 8826ab116f33e3ca6fd7907c42e176c148e0350c by Andrew Shark. Committed on 20/04/2024 at 00:35. Pushed by ashark into branch 'master'. Wait until finished cloning of qt5 repo before checking init-repository script M +3-1ksblib/Updater/Qt5.py https://invent.kde.org/sdk/kde-builder/-/commit/8826ab116f33e3ca6fd7907c42e176c148e0350c -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 485738] New: Kate crashes when deleting the file that is the only one opened in split view
https://bugs.kde.org/show_bug.cgi?id=485738 Bug ID: 485738 Summary: Kate crashes when deleting the file that is the only one opened in split view Classification: Applications Product: kate Version: 24.02.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: ash...@linuxcomp.ru Target Milestone: --- STEPS TO REPRODUCE 1. Create two files in home directory: 1.txt and 2.txt 2. Open 1.txt in Kate, Open 2.txt in Kate. 3. Click View | Split View | Split Vertical 4. Close 2.txt in the left view. So now you have the only tab in left view which is 1.txt, and the only tab in right view with 2.txt. 5. In the right view, right click on the 2.txt tab, and choose "Delete". 6. It asks "Do you really want to delete...?", answer Yes. OBSERVED RESULT Kate crashes EXPECTED RESULT Kate should not crash. As there are no more tabs opened in right split view, it should be either closed, or a placeholder should be shown there. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 456593] plasma-wayland-protocol builds, but doesn't install properly
https://bugs.kde.org/show_bug.cgi?id=456593 Andrew Shark changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED CC||ash...@linuxcomp.ru --- Comment #8 from Andrew Shark --- This is fixed. -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 458045] skanpage: Could NOT find KF5Purpose
https://bugs.kde.org/show_bug.cgi?id=458045 Andrew Shark changed: What|Removed |Added Status|REPORTED|RESOLVED CC||ash...@linuxcomp.ru Resolution|--- |WORKSFORME --- Comment #4 from Andrew Shark --- Cannot reproduce. `kde-builder skanpage` on opensuse Tumbleweed works as expected. Created mr for missing dependencies: https://invent.kde.org/sysadmin/repo-metadata/-/merge_requests/361 -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 325574] Unable to modify file on Android device using kio-mtp
https://bugs.kde.org/show_bug.cgi?id=325574 Andrew Simmons changed: What|Removed |Added CC||agsimmo...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485530] sticky note with dark theme buttons low contrast
https://bugs.kde.org/show_bug.cgi?id=485530 --- Comment #1 from andrew --- typo "buttons at bottom have low contrast with the background" is the "OBSERVED RESULT" -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485530] New: sticky note with dark theme buttons low contrast
https://bugs.kde.org/show_bug.cgi?id=485530 Bug ID: 485530 Summary: sticky note with dark theme buttons low contrast Classification: Plasma Product: plasmashell Version: 6.0.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: fand...@protonmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Created attachment 168505 --> https://bugs.kde.org/attachment.cgi?id=168505=edit screenshot SUMMARY STEPS TO REPRODUCE 1. set dark theme 2. create note OBSERVED RESULT EXPECTED RESULT buttons at bottom have low contrast with the background Operating System: Arch Linux KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.8.5-zen1-1-zen (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 7800X3D 8-Core Processor Memory: 30.6 GiB of RAM Graphics Processor: AMD Radeon RX 7900 XTX -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 485404] New: Terminal captures Tab key, but not Shift+Tab
https://bugs.kde.org/show_bug.cgi?id=485404 Bug ID: 485404 Summary: Terminal captures Tab key, but not Shift+Tab Classification: Applications Product: dolphin Version: 24.02.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: panels: terminal Assignee: dolphin-bugs-n...@kde.org Reporter: accounts+...@chiller3.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY When the terminal inside Dolphin is focused, it successfully captures the Tab key, but Shift+Tab is not captured. Pressing Shift+Tab causes the focus to move away from the terminal component and into the free disk space widget in the bottom right corner. This prevents certain functionality in CLI applications from working. For example, zsh allows using Shift+Tab to move backwards in a tab completion list. STEPS TO REPRODUCE 1. Open Dolphin 2. Open the terminal with F4 3. Press Tab (it is sent to the shell) 4. Press Shift+Tab OBSERVED RESULT The focus shifts away from the terminal component. EXPECTED RESULT Shift+Tab is sent to the command running in the terminal. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 40 KDE Plasma Version: 6.0.3-2.fc40.x86_64 KDE Frameworks Version: 6.0.0-1.fc40.x86_64 Qt Version: 6.6.2-1.fc40.x86_64 Dolphin Version: 24.02.1-1.fc40.x86_64 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 480866] kate segfault while long pressing ctrl+z
https://bugs.kde.org/show_bug.cgi?id=480866 --- Comment #4 from Andrew --- Maybe I got same. Currently not reproducible. Kate 23.08.5 from Fedora 39 repos. [KCrash Handler] #4 0x7fb00b531e1b in KateModifiedInsertText::undo() () at /lib64/libKF5TextEditor.so.5 #5 0x7fb00b534145 in KateUndoManager::undo() () at /lib64/libKF5TextEditor.so.5 #6 0x7fb00c0e92d8 in void doActivate(QObject*, int, void**) () at /lib64/libQt5Core.so.5 #7 0x7fb00cda7d44 in QAction::triggered(bool) () at /lib64/libQt5Widgets.so.5 #8 0x7fb00cdaab9b in QAction::activate(QAction::ActionEvent) () at /lib64/libQt5Widgets.so.5 #9 0x7fb00cdab7bd in QAction::event(QEvent*) () at /lib64/libQt5Widgets.so.5 #10 0x7fb00cdaeb95 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #11 0x7fb00c0b4e78 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #12 0x7fb00c59a4ee in QShortcutMap::dispatchEvent(QKeyEvent*) () at /lib64/libQt5Gui.so.5 #13 0x7fb00c59ab83 in QShortcutMap::tryShortcut(QKeyEvent*) () at /lib64/libQt5Gui.so.5 #14 0x7fb00c54e2b2 in QWindowSystemInterface::handleShortcutEvent(QWindow*, unsigned long, int, QFlags, unsigned int, unsigned int, unsigned int, QString const&, bool, unsigned short) () at /lib64/libQt5Gui.so.5 #15 0x7fb00c568ff5 in QGuiApplicationPrivate::processKeyEvent(QWindowSystemInterfacePrivate::KeyEvent*) () at /lib64/libQt5Gui.so.5 #16 0x7fb00c54ad4c in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () at /lib64/libQt5Gui.so.5 #17 0x7fb005e954e6 in xcbSourceDispatch(_GSource*, int (*)(void*), void*) () at /lib64/libQt5XcbQpa.so.5 #18 0x7fb009911e5c in g_main_context_dispatch_unlocked.lto_priv () at /lib64/libglib-2.0.so.0 #19 0x7fb00996cf18 in g_main_context_iterate_unlocked.isra () at /lib64/libglib-2.0.so.0 #20 0x7fb00990fad3 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #21 0x7fb00c1073b9 in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #22 0x7fb00c0b383b in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #23 0x7fb00c0bbacb in QCoreApplication::exec() () at /lib64/libQt5Core.so.5 #24 0x556b4775c3e7 in main () [Inferior 1 (process 3745) detached] -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 485028] Breeze Dark is broken in Flatpak applications
https://bugs.kde.org/show_bug.cgi?id=485028 --- Comment #2 from Andrew --- Update to the above comment: unfortunately, the workaround doesn't affect Slack (which is an Electron application). -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 485028] Breeze Dark is broken in Flatpak applications
https://bugs.kde.org/show_bug.cgi?id=485028 --- Comment #1 from Andrew --- A workaround is to run the following command: sudo flatpak override --env=GTK_THEME=Breeze Which actually gives weird results because, for example, in Inkscape's Preferences the system default theme is displayed as Breeze-Dark both before the override and after. But before the override, the UI is rendered in light colours, while after it, it is rendered in dark colours. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 485069] Yakuake Wayland Plasma 6: window size wrong when closed on a smaller screen
https://bugs.kde.org/show_bug.cgi?id=485069 Andrew Ammerlaan changed: What|Removed |Added Platform|Other |Gentoo Packages -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 485069] Yakuake Wayland Plasma 6: window size wrong when closed on a smaller screen
https://bugs.kde.org/show_bug.cgi?id=485069 --- Comment #1 from Andrew Ammerlaan --- Screen recording exceeds file size limit, so please download it from here instead: https://drive.google.com/file/d/13GDeljPf1S0Nkb-bh8-Dfc_EEIhluVPD/view?usp=sharing -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 485069] New: Yakuake Wayland Plasma 6: window size wrong when closed on a smaller screen
https://bugs.kde.org/show_bug.cgi?id=485069 Bug ID: 485069 Summary: Yakuake Wayland Plasma 6: window size wrong when closed on a smaller screen Classification: Applications Product: yakuake Version: 24.02.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: h...@kde.org Reporter: andrewammerl...@gentoo.org Target Milestone: --- SUMMARY In a multi screen setup the yakuake window will have half the size it should on the bigger screen if it was closed on the smaller screen. If the yakuake window is closed on the bigger screen there is no problem, if the yakuake window is *not* closed on the smaller screen there is also no problem. Wayland is affected, X11 was not tested. STEPS TO REPRODUCE 1. Have a multi-screen setup with different resolutions 2. Open yakuake on the smaller monitor, and close it with F12 3. Now open yakuake on the bigger monitor with F12 OBSERVED RESULT Half the window is shown, the rest of the window is gone/invisible/missing. EXPECTED RESULT We see the whole window. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Gentoo Linux 2.15 KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION See attached screen recording -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 485028] New: Breeze Dark is broken in Flatpak applications
https://bugs.kde.org/show_bug.cgi?id=485028 Bug ID: 485028 Summary: Breeze Dark is broken in Flatpak applications Classification: KDE Neon Product: neon Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: neon-b...@kde.org Reporter: as.a...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- I am running the latest KDE neon User Edition with all the latest updates: DISTRIB_ID=neon DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="KDE neon 6.0" The system is configured to use Breeze Dark. After the update to Plasma 6.0.0, Gtk, and Electron applications installed from Flatpak, like Inkscape, Slack, and Audacity have been rendered in the light Breeze theme with icons from Breeze Dark. I can manually switch the theme in Inkscape to Dark, and it will render correctly, but if I leave the system default theme, it will be rendered as Breeze light with Breeze Dark icons, as described above. I also have Google Chrome installed from a .deb package and configured to use the GTK theme - it is rendered correctly in Breeze Dark. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 252420] ark --forcesubfolder parameter and "Extract into a subfolder" service menu item
https://bugs.kde.org/show_bug.cgi?id=252420 Andrew Shark changed: What|Removed |Added Status|CONFIRMED |RESOLVED CC||ash...@linuxcomp.ru Resolution|--- |INTENTIONAL --- Comment #14 from Andrew Shark --- In this MR we decided to not add such an extra menu item: https://invent.kde.org/utilities/ark/-/issues/17 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482339] Tasks Show on incorrect screen after monitor reconnected
https://bugs.kde.org/show_bug.cgi?id=482339 Andrew Shark changed: What|Removed |Added CC||ash...@linuxcomp.ru --- Comment #38 from Andrew Shark --- I had this bug, prepared a bug report, only found this one when was filing my. Thanks for the fix! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 341378] When disabling touchpad, add ability to not disabling clickpad buttons (for clickpads on Lenovo laptops)
https://bugs.kde.org/show_bug.cgi?id=341378 --- Comment #7 from Andrew Shark --- I have Lenovo T14 now, which has combined touchpad: it has physical buttons (for left, middle and right mouse buttons), and also it can be clicked itself (i.e. be used as clickpad). On Plasma 6, I disabled the touchpad in System Settings, and can confirm that it disables the clickpad functionality. At the same time, the physical buttons (left, middle, right) and the trackpoint remains working, so this "bug" is not such an issue on this laptop. My guess is that the physical buttons on top of the T14's touchpad are actually belonging to another "mouse/pointing device" (the one that corresponds to the trackpoint), so that is why they remain working when disabling touchpad. I currently could not test on another laptop with clickpad only (i.e. without the trackpoint and without physical buttons). I do not remember now, but most likely that was an issue for me, that is why I subscribed to this bug. But, iirc, in some of the weekly Nate's articles, there was a mentioning that disabling touchpad on laptops without connected mouse now shows the warning to user? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 341378] When disabling touchpad, add ability to not disabling clickpad buttons (for clickpads on Lenovo laptops)
https://bugs.kde.org/show_bug.cgi?id=341378 Andrew Shark changed: What|Removed |Added Summary|Lenovo's clickpad's are |When disabling touchpad, |completely switched off,|add ability to not |which makes it impossible |disabling clickpad buttons |to click on anything|(for clickpads on Lenovo ||laptops) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 484238] New: kcm_sddm: sets empty CursorSize= resulting in invisible cursor at login
https://bugs.kde.org/show_bug.cgi?id=484238 Bug ID: 484238 Summary: kcm_sddm: sets empty CursorSize= resulting in invisible cursor at login Classification: Applications Product: systemsettings Version: 6.0.2 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_sddm Assignee: plasma-b...@kde.org Reporter: andrewammerl...@gentoo.org CC: k...@david-redondo.de, k...@davidedmundson.co.uk Target Milestone: --- SUMMARY Synchronizing Plasma settings to SDDM results in an invisible cursor in SDDM (wayland mode): STEPS TO REPRODUCE 1. Set some cursor size in plasma settings 2. Synchronize to SDDM 3. Restart OBSERVED RESULT We get: CursorSize= in /etc/sddm.conf.d/kde_settings.conf EXPECTED RESULT We should get: CursorSize=24 in /etc/sddm.conf.d/kde_settings.conf SOFTWARE/OS VERSIONS Linux/KDE Plasma: Gentoo linux (available in About System) KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.2 Qt Version: 6.6.2 ADDITIONAL INFORMATION Manually specifying the correct cursor size resolves the invisible cursor problem. A second related bug is probably that an empty setting should be considered invalid. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449163] Plasma panel visually freezes after some time under Wayland
https://bugs.kde.org/show_bug.cgi?id=449163 Andrew Simmons changed: What|Removed |Added CC|agsimmo...@gmail.com| -- You are receiving this mail because: You are watching all bug changes.
[kcolorchooser] [Bug 479406] The "Pick Screen Color" button is missing on Wayland session
https://bugs.kde.org/show_bug.cgi?id=479406 Andrew changed: What|Removed |Added CC||andrewnguyen...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kasts] [Bug 469259] strange voices when increasing the play speed
https://bugs.kde.org/show_bug.cgi?id=469259 Andrew Smith changed: What|Removed |Added CC||k...@espadav8.co.uk --- Comment #5 from Andrew Smith --- I've noticed this issue on the Android version. Is there the option to install other sound backends there too? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483738] Task Manager's 'Show only tasks' setting has no effect
https://bugs.kde.org/show_bug.cgi?id=483738 Andrew Smith changed: What|Removed |Added CC||k...@espadav8.co.uk -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483886] Plasma crashed when i clicked on X button of notification pop-up
https://bugs.kde.org/show_bug.cgi?id=483886 --- Comment #1 from Andrew --- Created attachment 167402 --> https://bugs.kde.org/attachment.cgi?id=167402=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483886] New: Plasma crashed when i clicked on X button of notification pop-up
https://bugs.kde.org/show_bug.cgi?id=483886 Bug ID: 483886 Summary: Plasma crashed when i clicked on X button of notification pop-up Classification: Plasma Product: plasmashell Version: 5.27.5 Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: sterea...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.27.5) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.1.0-18-amd64 x86_64 Windowing System: X11 Distribution: Debian GNU/Linux 12 (bookworm) DrKonqi: 5.27.5 [CoredumpBackend] -- Information about the crash: The crash has happened when I tried to close the notifications. Konsole is also frozen. The crash can be reproduced sometimes. -- Backtrace (Reduced): #3 0x7f844e277c86 in QtQml::qmlExecuteDeferred(QObject*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #4 0x7f844e749059 in QQuickTransition::prepare(QList&, QList&, QQuickTransitionManager*, QObject*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7f844e73e997 in QQuickTransitionManager::transition(QList const&, QQuickTransition*, QObject*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7f844ccdd50d in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f844d962fae in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 The reporter indicates this bug may be a duplicate of or related to bug 479971, bug 480164, bug 480882, bug 481323, bug 481894, bug 482503. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 482977] after upgrading to kde 6 everything is smaller on full hd 16:10 monitors
https://bugs.kde.org/show_bug.cgi?id=482977 --- Comment #6 from andrew --- (In reply to Nate Graham from comment #5) > Thanks. Can you create a new clean user account and see if the issue is > still happening there? can reproduce even with a new clean user account -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 429818] Autoscroll file a bit to show line context when searching
https://bugs.kde.org/show_bug.cgi?id=429818 --- Comment #6 from Andrew Shark --- > We will not keep feature requests open for ever, if x years nobody shows up > to do it, we close them. Wow. Super strange policy. Did not see such thing for any other projects. Some bugs are opened for decades! -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 482977] after upgrading to kde 6 everything is smaller on full hd 16:10 monitors
https://bugs.kde.org/show_bug.cgi?id=482977 --- Comment #4 from andrew --- (In reply to Nate Graham from comment #3) > Andrew, is this on X11 or Wayland, or both? Do you have an NVIDIA GPU? i can reproduce on x11 and wayland Operating System: Arch Linux KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.0.6.realtime1-1-rt (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-4570S CPU @ 2.90GHz Memory: 23.4 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 4600 -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 483290] New: Application list is interactable through kill confirmation dialog
https://bugs.kde.org/show_bug.cgi?id=483290 Bug ID: 483290 Summary: Application list is interactable through kill confirmation dialog Classification: Applications Product: plasma-systemmonitor Version: 6.0.1 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: amey...@protonmail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Created attachment 166985 --> https://bugs.kde.org/attachment.cgi?id=166985=edit Screen recording of the bug SUMMARY When the "Kill Application" dialog is open, clicking and dragging over the dialog selects items in the applications list below, apparently changing what is set to be killed. Interacting with the dialog's scroll bar will either cause the applications list to scroll, do nothing, or cause the program to become unresponsive. STEPS TO REPRODUCE 1. Select one or more items in the application list and select the option to terminate or kill them. 2. Click and drag on the body or scroll bar of the confirmation dialog. OBSERVED RESULT Interacting with the dialog body selects items on the applications list. Interacting with the dialog scroll bar causes the applications list to scroll or makes the program stop responding. EXPECTED RESULT Interacting with the confirmation dialog should not affect the applications list. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423390] Bottom Plasma panel and desktop are not fully adjacent to screen border (1 pixel on the right and bottom) when PLASMA_USE_QT_SCALING=1 is set on X11
https://bugs.kde.org/show_bug.cgi?id=423390 Andrew Brouwers changed: What|Removed |Added CC||abrouw...@gmail.com --- Comment #17 from Andrew Brouwers --- I see a similar issue, occasionally, on wayland + plasma 6. I'm at 150% scaling, and this will happen sporadically. Restarting the desktop fixes it, but it'll eventually come back (after some yet-to-be-determined action occurs). -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 482977] after upgrading to kde 6 everything is smaller on full hd 16:10 monitors
https://bugs.kde.org/show_bug.cgi?id=482977 --- Comment #2 from andrew --- (In reply to cdanek from comment #1) > Same here (except that I don't exactly know what kind of monitor I have; it > says "Built-in Screen 2560x1440"). > Want to add one piece of detail regarding the scaling. The Firefox browser > does not seem to understand that. No matter what value I set for Settings -> > Display -> Scale, e.g. 80% or 120%, in Firefox all sizes (font, tabs, bars, > etc.) get _smaller_ in both cases. All other tested software behave as > expected (e.g. Dolphin, LibreOffice). Is that a bug in KDE or Firefox? I think we have two different bugs, in my case any app both qt and gtk have abnormal sizes, some things are really too small, I think your problem is due to scaling with wayland -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 482996] New: CTRL+ESC should by default start system monitor from kde 6+
https://bugs.kde.org/show_bug.cgi?id=482996 Bug ID: 482996 Summary: CTRL+ESC should by default start system monitor from kde 6+ Classification: Applications Product: plasma-systemmonitor Version: 6.0.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: fand...@protonmail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- SUMMARY up to kde 5 there was ksysguard which by default automatically started with ctrl+esc, on kde 6 ksysguard has been removed, so the shortcut should now default to system monitor SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.8-zen1-1-zen (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 7800X3D 8-Core Processor Memory: 30.6 GiB of RAM Graphics Processor: AMD Radeon RX 7900 XTX -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482990] the panel in "dodge windows" mode prevents focusing the close button of a maximized window when the cursor is in the edge of the screen
https://bugs.kde.org/show_bug.cgi?id=482990 andrew changed: What|Removed |Added Summary|the panel in "dodge |the panel in "dodge |windows" mode prevents |windows" mode prevents |focusing the close button |focusing the close button |of a window when the cursor |of a maximized window when |is in the edge |the cursor is in the edge ||of the screen -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482990] New: the panel in "dodge windows" mode prevents focusing the close button of a window when the cursor is in the edge
https://bugs.kde.org/show_bug.cgi?id=482990 Bug ID: 482990 Summary: the panel in "dodge windows" mode prevents focusing the close button of a window when the cursor is in the edge Classification: Plasma Product: kwin Version: 6.0.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: decorations Assignee: kwin-bugs-n...@kde.org Reporter: fand...@protonmail.com Target Milestone: --- SUMMARY with the panel in "dodge windows" mode, if a window is maximized if I go with the cursor in the top right edge I can't focus the close button, I have to move the cursor a little to the left to be able to press the window close button. STEPS TO REPRODUCE 1. enable dodge windows on the bottom panel 2. open a maximized window 3. move the cursor to the top right edge 4. left click OBSERVED RESULT the close button is not focussed EXPECTED RESULT should be focussed SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.8-zen1-1-zen (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 7800X3D 8-Core Processor Memory: 30.6 GiB of RAM Graphics Processor: AMD Radeon RX 7900 XTX -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482986] compositor does come back after closing a game
https://bugs.kde.org/show_bug.cgi?id=482986 andrew changed: What|Removed |Added Summary|compositor does not then|compositor does come back |come back after closing a |after closing a game |game| -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482986] New: compositor does not then come back after closing a game
https://bugs.kde.org/show_bug.cgi?id=482986 Bug ID: 482986 Summary: compositor does not then come back after closing a game Classification: Plasma Product: kwin Version: 6.0.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: fand...@protonmail.com Target Milestone: --- STEPS TO REPRODUCE 1. open a game (ie "like a dragon infinite wealth" from steam (valve proton)) 2. close the game, (all processes killed) OBSERVED RESULT compositor is disabled when open the game but is not restored when close the game EXPECTED RESULT compositor must be restored SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.8-zen1-1-zen (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 7800X3D 8-Core Processor Memory: 30.6 GiB of RAM Graphics Processor: AMD Radeon RX 7900 XTX -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 482977] New: after upgrading to kde 6 everything is smaller on full hd 16:10 monitors
https://bugs.kde.org/show_bug.cgi?id=482977 Bug ID: 482977 Summary: after upgrading to kde 6 everything is smaller on full hd 16:10 monitors Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: fand...@protonmail.com Target Milestone: --- SUMMARY after upgrading to kde 6 from kde 5 all apps including kde apps have both text and layouts in general too small both on xorg and wayland, I tried deleting everything ~/.config and ~/.local and reconfiguring scaling and font size, but even restoring the configurations I had previously everything is smaller, it only happens on full hd 16:10 monitors, on my setup with 4k 16:9 monitor I couldn't reproduce. If I increase the font size even more it's even worse because all the layouts get weird. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482976] New: activating/deactivating the floating panel sometimes a padding remains between the panel and the bottom edge
https://bugs.kde.org/show_bug.cgi?id=482976 Bug ID: 482976 Summary: activating/deactivating the floating panel sometimes a padding remains between the panel and the bottom edge Classification: Plasma Product: plasmashell Version: 6.0.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Edit Mode toolbar Assignee: plasma-b...@kde.org Reporter: fand...@protonmail.com Target Milestone: 1.0 STEPS TO REPRODUCE 1. enable/disable multiple times floating + change size of the panel 2. close the editor OBSERVED RESULT Activating/deactivating the floating panel sometimes leaves a padding that is as much high as the height of the panel itself, it is solved by relogging to kde EXPECTED RESULT no padding without floating panel SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.8-zen1-1-zen (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 7800X3D 8-Core Processor Memory: 30.6 GiB of RAM Graphics Processor: AMD Radeon RX 7900 XTX -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482975] by left-clicking sometimes the click comes in the wrong position in firefox
https://bugs.kde.org/show_bug.cgi?id=482975 andrew changed: What|Removed |Added Summary|when I do a left click on |by left-clicking sometimes |firefox wraps firefox click |the click comes in the |in the wrong place |wrong position in firefox -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482975] New: when I do a left click on firefox wraps firefox click in the wrong place
https://bugs.kde.org/show_bug.cgi?id=482975 Bug ID: 482975 Summary: when I do a left click on firefox wraps firefox click in the wrong place Classification: Plasma Product: kwin Version: 6.0.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: core Assignee: kwin-bugs-n...@kde.org Reporter: fand...@protonmail.com Target Milestone: --- STEPS TO REPRODUCE 1. open firefox (kwin x11) 2. open a website 3. maximize, minimize, resize ecc the window multiple times 4. now if you perform a left click on a windowed (not maximized window) the clicked elements is wrong OBSERVED RESULT it only happens after continuous use of firefox and only after resizing the window multiple times, the clicks are usually wrong by so many pixels, for example clicking pause on youtube might click the channel name instead of the pause button SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.8-zen1-1-zen (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 7800X3D 8-Core Processor Memory: 30.6 GiB of RAM Graphics Processor: AMD Radeon RX 7900 XTX -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 308689] Feature Request: Have a flag to display which modules failed to build/install on last run
https://bugs.kde.org/show_bug.cgi?id=308689 Andrew Shark changed: What|Removed |Added Status|CONFIRMED |RESOLVED CC||ash...@linuxcomp.ru Resolution|--- |MOVED --- Comment #1 from Andrew Shark --- Move to https://invent.kde.org/sdk/kde-builder/-/issues/73 -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 457124] Untracked files prevents switching branches
https://bugs.kde.org/show_bug.cgi?id=457124 Andrew Shark changed: What|Removed |Added Resolution|--- |MOVED CC||ash...@linuxcomp.ru Status|CONFIRMED |RESOLVED --- Comment #1 from Andrew Shark --- Move to https://invent.kde.org/sdk/kde-builder/-/issues/72 -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 445435] kdesrc-build doesn't respect HTTPS_PROXY
https://bugs.kde.org/show_bug.cgi?id=445435 Andrew Shark changed: What|Removed |Added CC||ash...@linuxcomp.ru Status|REPORTED|RESOLVED Resolution|--- |MOVED --- Comment #1 from Andrew Shark --- Move to https://invent.kde.org/sdk/kde-builder/-/issues/71 -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 482196] Disabling history doesn't disable memory of last-typed search
https://bugs.kde.org/show_bug.cgi?id=482196 --- Comment #5 from Andrew Brouwers --- (In reply to Nate Graham from comment #4) > Currently this behavior is intentional, but I can see how it's somewhat > confusing: disabling history doesn't disable *recent* history, only long > term history. Maybe we need another setting for this: > > > History: ( ) Disable > > ( ) Only last-typed search > > ( ) Suggestions from all past searches > > (o) Auto-complete from all past searches Yeah, I would expect disable history to start with a blank input, every time. -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 474018] When using --resume-after, specify current module number and total modules number as in full set
https://bugs.kde.org/show_bug.cgi?id=474018 Andrew Shark changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |MOVED --- Comment #1 from Andrew Shark --- Move to https://invent.kde.org/sdk/kde-builder/-/issues/70 -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 397458] Wish list: Improve support for showing code warnings / errors
https://bugs.kde.org/show_bug.cgi?id=397458 Andrew Shark changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |MOVED CC||ash...@linuxcomp.ru --- Comment #2 from Andrew Shark --- Move to https://invent.kde.org/sdk/kde-builder/-/issues/69 -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 481272] Perl 5.28 being required prevents use in openSUSE LEAP 15.5 and potentially other non-rolling-release distros
https://bugs.kde.org/show_bug.cgi?id=481272 --- Comment #12 from Andrew Shark --- About self-update I have some thoughts, but that may be discussed in another issue. For the note, in case you really would need to use kdesrc-build in suse leap (for testing for example), you can manually remove that "|!" from specifier. I am not doing that for kdesrc-build, because to remove it properly, it needs to be replaced by something, and documentation needs to be changed, and I switched development to kde-builder. -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 481272] Perl 5.28 being required prevents use in openSUSE LEAP 15.5 and potentially other non-rolling-release distros
https://bugs.kde.org/show_bug.cgi?id=481272 --- Comment #10 from Andrew Shark --- I know Marco is a KDE developer. But note, that people were expected to update kdesrc-build, because it had module-definitions included in its repo. If you were keeping the kdesrc-build outdated, that was incorrect usage. Note that now distro-dependencies and module-definitions moved to repo-metadata. So they will be up to date automatically at each kde-builder run. But still, it is assumed you are a recent version of kde-builder and update regularly. -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 419688] name inconsistency discover / plasma-discover
https://bugs.kde.org/show_bug.cgi?id=419688 Andrew Shark changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |NOT A BUG --- Comment #1 from Andrew Shark --- When the binary name is not the same as module name, use --exec option: kde-builder discover --exec plasma-discover -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 284228] kdesrc-build should list updated packages that had been skipped
https://bugs.kde.org/show_bug.cgi?id=284228 Andrew Shark changed: What|Removed |Added Resolution|--- |MOVED Status|CONFIRMED |RESOLVED CC||ash...@linuxcomp.ru --- Comment #2 from Andrew Shark --- Move to https://invent.kde.org/sdk/kde-builder/-/issues/66 -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 474074] When failed to build module, add the link to the project pipeline in gitlab
https://bugs.kde.org/show_bug.cgi?id=474074 Andrew Shark changed: What|Removed |Added Resolution|--- |MOVED Status|REPORTED|RESOLVED --- Comment #1 from Andrew Shark --- Moved to https://invent.kde.org/sdk/kde-builder/-/issues/65 -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 478706] kuserfeedback fails to build the source cannot be found, so the metadata is incorrect.
https://bugs.kde.org/show_bug.cgi?id=478706 Andrew Shark changed: What|Removed |Added CC||ash...@linuxcomp.ru Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #2 from Andrew Shark --- Working ok for me for branch-group kf6-qt6. kde-builder kuserfeedback --src-only. Build is also ok. Also, metadata issues should go to the repo-metadata repo, not related to kdesrc-build/kde-builder. -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 315105] kdesrc-build should treat "obvious" dependencies as implicit
https://bugs.kde.org/show_bug.cgi?id=315105 Andrew Shark changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED CC||ash...@linuxcomp.ru --- Comment #3 from Andrew Shark --- Each project has now .kde-ci.yml, in each kde game the dependency is listed. For example: kde/kdegames/kgoldrunner: kde/kdegames/libkdegames See https://invent.kde.org/sysadmin/repo-metadata/-/blob/master/dependencies/dependency-data-kf6-qt6?ref_type=heads -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 362687] Enable kdesrc-build to handle Git Submodules
https://bugs.kde.org/show_bug.cgi?id=362687 Andrew Shark changed: What|Removed |Added Resolution|--- |MOVED CC||ash...@linuxcomp.ru Status|REPORTED|RESOLVED --- Comment #4 from Andrew Shark --- Duplicates https://invent.kde.org/sdk/kde-builder/-/issues/40 -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 480029] ./kdesrc-build --initial-setup cannot find linux.ini
https://bugs.kde.org/show_bug.cgi?id=480029 Andrew Shark changed: What|Removed |Added Resolution|--- |INTENTIONAL CC||ash...@linuxcomp.ru Status|REPORTED|RESOLVED --- Comment #1 from Andrew Shark --- As you distro is not in the list of supported distros, skip the --install-distro-packages step, and only use --generate-config. If you want to add support for your distro, prepare a package list and file mr here: https://invent.kde.org/sysadmin/repo-metadata/-/tree/master/distro-dependencies?ref_type=heads -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 456205] Add build / initial-setup support for Linux Mint: "kdesrc-build does not know your distribution (linuxmint)"
https://bugs.kde.org/show_bug.cgi?id=456205 Andrew Shark changed: What|Removed |Added CC||ash...@linuxcomp.ru Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #4 from Andrew Shark --- I have checked now with linuxmintd/mint21.3-amd64 docker image, the /etc/os-release contains the debian: ID_LIKE="ubuntu debian" So initial setup works. -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 420630] Unable to pass initial setup on OpenSUSE Leap 15.5
https://bugs.kde.org/show_bug.cgi?id=420630 Andrew Shark changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=481272 -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 481272] Perl 5.28 being required prevents use in openSUSE LEAP 15.5 and potentially other non-rolling-release distros
https://bugs.kde.org/show_bug.cgi?id=481272 Andrew Shark changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=420630 -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 420630] Unable to pass initial setup on OpenSUSE Leap 15.5
https://bugs.kde.org/show_bug.cgi?id=420630 Andrew Shark changed: What|Removed |Added Resolution|--- |UNMAINTAINED Status|REOPENED|RESOLVED --- Comment #10 from Andrew Shark --- OpenSUSE Leap is currently not supported. The package list opensuse.ini in repo-metadata is assumed for open suse TumbleWeed, not for OpenSuse Leap. If you want to add support for the OpenSuse Leap, please provide a list of packages and make MR here: https://invent.kde.org/sysadmin/repo-metadata/-/blob/master/distro-dependencies/opensuse.ini?ref_type=heads Also, because of the bug 481272 you would need to use kde-builder. -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 481272] Perl 5.28 being required prevents use in openSUSE LEAP 15.5 and potentially other non-rolling-release distros
https://bugs.kde.org/show_bug.cgi?id=481272
--- Comment #8 from Andrew Shark ---
I have explored what happened.
The OpenSuse Leap 15.5 uses perl 5.26.1.
That perl version uses GetOpt::Long 2.49 specification:
perl -MGetopt::Long -e 'print $Getopt::Long::VERSION, "\n";'
2.49
Here is the doc for this specification:
https://perldoc.perl.org/5.26.1/Getopt::Long
It can be seen that this spec already supports such specification of number of
args:
> It is also possible to specify the minimal and maximal number of arguments an
> option takes. foo=s{2,4} indicates an option that takes at least two and at
> most 4 arguments. foo=s{1,} indicates one or more values; foo:s{,} indicates
> zero or more option values.
The issue appeared after introducing the short version of option as exclamation
mark in this commit:
https://invent.kde.org/sdk/kdesrc-build/-/commit/5b155c5e29dd2d377fd1f84fb42d0e629a9f368b#9cca8ad07f12b7b754bac5e08c4e360e4c8ab1a3_448_460
This was half of year ago, and nobody complained. Because newer versions of
perl allow exclamation mark. This proves nobody uses outdated distros like
OpenSuse Leap for development.
--
You are receiving this mail because:
You are watching all bug changes.
[kdesrc-build] [Bug 447601] ./kdesrc-build --initial-setup does not install Perl YAML on openSUSE TW
https://bugs.kde.org/show_bug.cgi?id=447601 Andrew Shark changed: What|Removed |Added CC||ash...@linuxcomp.ru Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #5 from Andrew Shark --- Cannot reproduce under openSUSE Tumbleweed image. I see in [this](https://invent.kde.org/sdk/kdesrc-build/-/commit/1b34b936490b652bf99e03197f18c53abf4eb3fd#19fffd4e5cecfecc6dd5b053a9570c740101166f_296_292) commit the `perl-YAML-LibYAML` was replaced by `perl(YAML::LibYAML)`. But that is dated 2019-12-17, while original poster date is 2021-12-28. Also, consider switching to kde-builder if still using kdesrc-build. -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 481098] For some distributions --initial-setup will not properly set the amount of usable cores
https://bugs.kde.org/show_bug.cgi?id=481098 Andrew Shark changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/sdk/ ||kde-builder/-/commit/f2392f ||e48d3113fd004704827e68af93d ||c491715 Status|REPORTED|RESOLVED --- Comment #2 from Andrew Shark --- Git commit f2392fe48d3113fd004704827e68af93dc491715 by Andrew Shark. Committed on 02/03/2024 at 17:42. Pushed by ashark into branch 'master'. FirstRun: Actually use nproc for supported distros M +4-4ksblib/FirstRun.py M +1-1ksblib/OSSupport.py https://invent.kde.org/sdk/kde-builder/-/commit/f2392fe48d3113fd004704827e68af93dc491715 -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 482196] History setting not effective
https://bugs.kde.org/show_bug.cgi?id=482196 --- Comment #3 from Andrew Brouwers --- Created attachment 166311 --> https://bugs.kde.org/attachment.cgi?id=166311=edit konsole launched, while "kons" retained in a future krunner instance -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 482196] History setting not effective
https://bugs.kde.org/show_bug.cgi?id=482196 --- Comment #2 from Andrew Brouwers --- (In reply to Alexander Lohnau from comment #1) > Hmm, I am not sure how to handle this. It is not any persistent history, but > just your last typed query. In case a window opens and KRunner closes, you > might otherwise miss your previously typed text. Though you should be able > to override the text with just one keystroke. > > A sensible differentiation might be the cause for closing KRunner. Like the > escape key could be handled separately and clear the text when a match is > run. Though I am not sure if this behavior seems consistent to the average > user. I should clarify, even if I type "kons," hit "enter" once konsole is highlighted (ie, it didn't get interrupted, but rather successfully launched my searched-for app), it *still* shows in my history. The history setting just seems broken in plasma 6. -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 481272] Perl 5.28 being required prevents use in openSUSE LEAP 15.5 and potentially other non-rolling-release distros
https://bugs.kde.org/show_bug.cgi?id=481272 Andrew Shark changed: What|Removed |Added Status|CONFIRMED |NEEDSINFO Resolution|--- |FIXED --- Comment #7 from Andrew Shark --- I also would like to know if that was working ever, marking as NEEDSINFO. Other than that, I recommend using kde-builder anyway (it supports not so fresh python versions also). -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 439982] kdesrc-build --run does not set icon for application window on wayland
https://bugs.kde.org/show_bug.cgi?id=439982 Andrew Shark changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |INTENTIONAL --- Comment #3 from Andrew Shark --- It seems it is impossible to do after kwin has started. Also, even if modify system's XDG_DATA_DIR to contain dev path first, then normal app also will have that modified icon. In other words, in a single kwin session it is impossible to have different icons for the apps (dev and normal). I only can think now of some hacky ways, such as making a window rule triggered by window title to apply custom desktop file. -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 311830] Absolute path to the log file should be shown as soon as an error is encountered.
https://bugs.kde.org/show_bug.cgi?id=311830 Andrew Shark changed: What|Removed |Added CC||ash...@linuxcomp.ru Resolution|--- |MOVED Status|REOPENED|RESOLVED --- Comment #7 from Andrew Shark --- Duplicate of https://invent.kde.org/sdk/kde-builder/-/issues/39 -- You are receiving this mail because: You are watching all bug changes.
