[kate] [Bug 466571] New: Kate crashes on MacOS when using the "Save Copy As..." menu option
https://bugs.kde.org/show_bug.cgi?id=466571 Bug ID: 466571 Summary: Kate crashes on MacOS when using the "Save Copy As..." menu option Classification: Applications Product: kate Version: 22.12.2 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: codest...@catsanddags.com Target Milestone: --- Created attachment 156813 --> https://bugs.kde.org/attachment.cgi?id=156813&action=edit Full-length crash report, generated by macOS SUMMARY *** When using "Save Copy As..." under the "File" menu, Kate first prompts for a location to save the copy, then crashes once a location to save to has been provided. (On MacOS) *** STEPS TO REPRODUCE 1. Create or open a file with some code in Kate 2. Click "Save Copy As..." under the "File" menu 3. Enter a location to save the file and click "Save" OBSERVED RESULT Kate crashes EXPECTED RESULT A copy of the file being created in the specified location. SOFTWARE/OS VERSIONS macOS: MacOS Monterey 12.2.1 The "Components" tab under "About Kate" says: * KDE Frameworks Version 5.103.0 * Qt Version 5.15.8 (built against 5.15.8) * The cocoa windowing system Kate installed from a .dmg file of the most recent stable build ADDITIONAL INFORMATION This crash appears to be specific to the "Save Copy As..." option - taking the same steps with the "Save As..." option does not cause a crash. The crash report generated by macOS included the following (full length crash report included as an attachment): Crashed Thread:8 KIO::WorkerThread Exception Type:EXC_BAD_ACCESS (SIGBUS) Exception Codes: KERN_PROTECTION_FAILURE at 0x00030a196ff8 Exception Codes: 0x0002, 0x00030a196ff8 Exception Note:EXC_CORPSE_NOTIFY Termination Reason:Namespace SIGNAL, Code 10 Bus error: 10 Terminating Process: exc handler [38847] VM Region Info: 0x30a196ff8 is in 0x30a196000-0x30a197000; bytes after start: 4088 bytes before end: 7 REGION TYPESTART - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL Stack 30a111000-30a196000[ 532K] rw-/rwx SM=PRV thread 5 ---> Stack Guard 30a196000-30a197000[4K] ---/rwx SM=NUL Stack 30a197000-30a219000[ 520K] rw-/rwx SM=PRV -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 466576] New: Terminal "Edit Color Scheme" window hidden after selecting a color (on macOS)
https://bugs.kde.org/show_bug.cgi?id=466576 Bug ID: 466576 Summary: Terminal "Edit Color Scheme" window hidden after selecting a color (on macOS) Classification: Applications Product: kate Version: 22.12.2 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: codest...@catsanddags.com Target Milestone: --- Created attachment 156815 --> https://bugs.kde.org/attachment.cgi?id=156815&action=edit Screenshot showing positions of the windows after selecting a color SUMMARY *** When attempting to edit a terminal color scheme in Kate, the "Edit Color Scheme" window is sent to the background and hidden behind the "Edit Profile" window after selecting a color with the color-picker tool. *** STEPS TO REPRODUCE 1. Ctrl+click on a terminal in Kate and choose "Edit current profile..." 2. Navigate to the "Appearance" section in the profile settings 3. Select a color profile to edit 4. Click on one of the colors displayed to bring up the color picker tool 5. Select a color OBSERVED RESULT The "Edit Color Scheme" window disappears behind the "Edit Profile" window EXPECTED RESULT The "Edit Color Scheme" window staying on top of the "Edit Profile" window, because the "Edit Color Scheme" window is the one the user was working in. SOFTWARE/OS VERSIONS macOS: MacOS Monterey 12.2.1 The "Components" tab under "About Kate" says: * KDE Frameworks Version 5.103.0 * Qt Version 5.15.8 (built against 5.15.8) * The cocoa windowing system Kate installed from a .dmg file of the most recent stable build ADDITIONAL INFORMATION Screenshot attached to show the positions of the windows after selecting a color The "Edit Color Scheme" window also shows other odd behaviors - when switching from Kate to another application, the "Edit Color Scheme" window stays on top in front of the other application. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 466577] New: Feature request: Ability to enter ssh key passphrase when doing a "git push" from Kate's Project plugin
https://bugs.kde.org/show_bug.cgi?id=466577 Bug ID: 466577 Summary: Feature request: Ability to enter ssh key passphrase when doing a "git push" from Kate's Project plugin Classification: Applications Product: kate Version: 22.12.2 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: codest...@catsanddags.com Target Milestone: --- SUMMARY *** When doing a "git push" from Kate's Project plugin, the push will fail if the ssh key associated with the remote repository requires an ssh key passphrase. Adding the ability to prompt for the key passphrase would improve the usability of the Project plugin for some users. *** STEPS TO REPRODUCE 1. Set up a local git repository, configured to push to a remote repository using an ssh key. When creating the ssh key, set a key passphrase. 2. Attempt to push committed changes to the remote repository using the "git push" icon in the Kate Project plugin OBSERVED RESULT Push fails due to inability to authenticate EXPECTED RESULT Prompt to enter the ssh key passphrase SOFTWARE/OS VERSIONS macOS: MacOS Monterey 12.2.1 The "Components" tab under "About Kate" says: * KDE Frameworks Version 5.103.0 * Qt Version 5.15.8 (built against 5.15.8) * The cocoa windowing system Kate installed from a .dmg file of the most recent stable build ADDITIONAL INFORMATION Unsure if software/OS versions are relevant or if this feature currently does not exist in Kate on any OS. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 466577] Feature request: Ability to enter ssh key passphrase when doing a "git push" from Kate's Git plugin
https://bugs.kde.org/show_bug.cgi?id=466577 Kristen changed: What|Removed |Added Summary|Feature request: Ability to |Feature request: Ability to |enter ssh key passphrase|enter ssh key passphrase |when doing a "git push" |when doing a "git push" |from Kate's Project plugin |from Kate's Git plugin -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 466577] Feature request: Ability to enter ssh key passphrase when doing a "git push" from the Git view in Kate's Projects plugin
https://bugs.kde.org/show_bug.cgi?id=466577 Kristen changed: What|Removed |Added Summary|Feature request: Ability to |Feature request: Ability to |enter ssh key passphrase|enter ssh key passphrase |when doing a "git push" |when doing a "git push" |from Kate's Git plugin |from the Git view in Kate's ||Projects plugin -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 466577] Feature request: Ability to enter ssh key passphrase when doing a "git push" from the Git view in Kate's Projects plugin
https://bugs.kde.org/show_bug.cgi?id=466577 --- Comment #1 from Kristen --- My earlier comment may be incorrect in referring to doing a git push from the Projects plugin. If my description is unclear, I am referring to the git toolview where it is possible to perform simple git operations such as commits/pushes/pulls (I think this comes from the Projects plugin, but I am not 100% sure). -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 466577] Feature request: Ability to enter ssh key passphrase when doing a "git push" from Kate's git toolview
https://bugs.kde.org/show_bug.cgi?id=466577 Kristen changed: What|Removed |Added Summary|Feature request: Ability to |Feature request: Ability to |enter ssh key passphrase|enter ssh key passphrase |when doing a "git push" |when doing a "git push" |from the Git view in Kate's |from Kate's git toolview |Projects plugin | -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 443727] Scroll mouse wheel -> Cycle through desktops not working for MX Master
https://bugs.kde.org/show_bug.cgi?id=443727 --- Comment #2 from Kristen McWilliam --- (In reply to Richard Llom from comment #1) > Can you still reproduce this issue? I just tried in KDE Neon, it seems to be working now! 👍 -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 435001] Ark does not preserve user generated xattrs (extended attributes) when editing/updating/saving a .zip file (and other types of archives)
https://bugs.kde.org/show_bug.cgi?id=435001 Kristen McWilliam changed: What|Removed |Added CC||kmcwilliampub...@gmail.com --- Comment #5 from Kristen McWilliam --- In the linked merge request I have fixed this issue for the following scenarios: - Adding files to the archive - Copying files within the archive - Deleting / removing files from the archive - Encrypting the archive - Moving files within the archive For all of these situations the metadata is now preserved. Are you aware of any other operations that cause the metadata to be lost? -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 435001] Ark does not preserve user generated xattrs (extended attributes) when editing/updating/saving a .zip file (and other types of archives)
https://bugs.kde.org/show_bug.cgi?id=435001 --- Comment #8 from Kristen McWilliam --- I am happy to report that all of these scenarios are also covered by the current changes. :) -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 435001] Ark does not preserve user generated xattrs (extended attributes) when editing/updating/saving a .zip file (and other types of archives)
https://bugs.kde.org/show_bug.cgi?id=435001 --- Comment #10 from Kristen McWilliam --- It hasn't been merged yet, it still needs a review first. I will let you know when it is so you can test it out. :) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483279] New: Pasting to search field doesn't work
https://bugs.kde.org/show_bug.cgi?id=483279 Bug ID: 483279 Summary: Pasting to search field doesn't work Classification: Plasma Product: kwin Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-overview Assignee: kwin-bugs-n...@kde.org Reporter: kmcwilliampub...@gmail.com Target Milestone: --- SUMMARY *** The overview's search field doesn't accept paste input via hotkey (Ctrl + V), right-click context menu (there is none), nor middle-click paste. *** STEPS TO REPRODUCE 1. Copy some text to clipboard 2. Open Overview effect 3. Press Ctrl + V to paste (optionally put focus on search box first), though it should work without that OBSERVED RESULT Text is not pasted into the search field EXPECTED RESULT Text should be pasted SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora 40 / Plasma 6.0.1 (also on master) (available in About System) KDE Plasma Version: Plasma 6.0.1 (also on master) 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.
[yakuake] [Bug 446920] [Feature Reequest] Open directory in yakuake from commandline
https://bugs.kde.org/show_bug.cgi?id=446920 Kristen McWilliam changed: What|Removed |Added CC||kmcwilliampub...@gmail.com --- Comment #1 from Kristen McWilliam --- Try the dbus interface. For example, using qdbus from another terminal... Open/close: qdbus org.kde.yakuake /yakuake/window toggleWindowState Change the directory of the active tab to /etc: qdbus org.kde.yakuake /yakuake/sessions runCommand "cd /etc" Open a new tab and change its location to /usr: qdbus org.kde.yakuake /yakuake/sessions addSession && qdbus org.kde.yakuake /yakuake/sessions runCommand "cd /usr" -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 481641] Gracelock broken after manually locking the screen
https://bugs.kde.org/show_bug.cgi?id=481641 --- Comment #3 from Kristen McWilliam --- Agreed, this is intentional design and not a regression; I don't see a reason for a grace period when invoked manually - though if you can think of a use case I am open to having my mind changed. :) -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 481450] The "Reset" and "Defaults" buttons does not work properly if either or both of the duration settings are set to custom
https://bugs.kde.org/show_bug.cgi?id=481450 Kristen McWilliam changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/plas ||ma/kscreenlocker/-/commit/f ||1c250ed61fccd31b544007b5a50 ||c96cb5bc1152 --- Comment #2 from Kristen McWilliam --- Git commit f1c250ed61fccd31b544007b5a50c96cb5bc1152 by Kristen McWilliam. Committed on 26/02/2024 at 18:45. Pushed by merritt into branch 'master'. fix(kcm): reset and default actions not reflected immediately Seems as if ComboBoxes have some difficulty with the reset and default actions in KCMs. This patch adds listeners to the reset and default actions and triggers an update of the ComboBoxes. Took inspirations from the Powerdevil KCM, which was having similar issues with ComboBoxes. See: https://invent.kde.org/plasma/powerdevil/-/blob/089a47aecc57c6e064e3bc459087ffd84495febc/kcmodule/profiles/ui/main.qml#L72 M +2-0kcm/kcm.cpp M +11 -0kcm/kcm.h M +30 -0kcm/ui/main.qml https://invent.kde.org/plasma/kscreenlocker/-/commit/f1c250ed61fccd31b544007b5a50c96cb5bc1152 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486024] New: callDBus fails for specific number types
https://bugs.kde.org/show_bug.cgi?id=486024
Bug ID: 486024
Summary: callDBus fails for specific number types
Classification: Plasma
Product: kwin
Version: master
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: scripting
Assignee: kwin-bugs-n...@kde.org
Reporter: kmcwilliampub...@gmail.com
Target Milestone: ---
SUMMARY
Calling a method on a D-Bus object can fail if the method has arguments of a
specific number signature, such as uint32.
STEPS TO REPRODUCE
1. Monitor kwin script output:
```
journalctl -b -f | grep -i "kwin"
```
2. Open the KWin Scripting Console
3. Call the `Inhibit` method on `org.freedesktop.Notifications`, which works as
expected:
```javascript
callDBus(
"org.freedesktop.Notifications",
"/org/freedesktop/Notifications",
"org.freedesktop.Notifications",
"Inhibit",
"",
"",
{},
function (reply) {
console.info("Callback. Reply: " + reply);
}
);
```
4. Check the output of the journal, which should show the
message "Callback. Reply: $number" - I'll assume it was 1 for the sake of
this example. Do Not Disturb should have been enabled.
5. Call the method `UnInhibit` on `org.freedesktop.Notifications`, which
expects
a uint32 as argument:
```javascript
callDBus(
"org.freedesktop.Notifications",
"/org/freedesktop/Notifications",
"org.freedesktop.Notifications",
"UnInhibit",
1,
function (reply) {
console.info("UnInhibit callback. Reply: " + reply);
}
);
```
OBSERVED RESULT
KWin journal output shows it failed due to no method with the signature:
```
kwin_wayland[4962]: warning:kwin_scripting:unknown:0 - Received D-Bus message
is error: "No such method 'UnInhibit' in interface
'org.freedesktop.Notifications' at object path '/org/freedesktop/Notifications'
(signature 'i')"
```
The method `UnInhibit` expects a uint32 as argument, but callDBus is trying
with
an int `(signature 'i')`.
EXPECTED RESULT
The method `UnInhibit` should be called successfully, and Do Not Disturb should
be disabled.
SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 40
KDE Plasma Version: 6.0.3
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.8.7-300.fc40.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 3700X 8-Core Processor
Memory: 31.3 GiB of RAM
Graphics Processor: AMD Radeon RX 580 Series
Manufacturer: Micro-Star International Co., Ltd.
Product Name: MS-7C56
System Version: 2.0
ADDITIONAL INFORMATION
This is probably because `QJSValue::toVariant()` only converts to int or double
for numbers, and special handling is needed to check for other types:
https://invent.kde.org/plasma/kwin/-/blob/7949032411153ebf9d87b0e936b1bc288df12b38/src/scripting/scripting.cpp#L344
Interestingly, if `UnInhibit` is called without a callback, it fails silently.
The error from kwin about the type mismatch is only output if a callback is
provided.
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 486024] callDBus fails for specific number types
https://bugs.kde.org/show_bug.cgi?id=486024 --- Comment #2 from Kristen McWilliam --- (In reply to fanzhuyifan from comment #1) > Would you be interested in submitting a merge request? More information can > be found at https://community.kde.org/Get_Involved/development > > Thanks! Yeah, though I wanted to check if anyone had a pertinent interjection about how to handle the change before I started it, since it seems like it could have some snowball effects. :) -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 484464] New: Move to Next / Previous Screen shortcut no longer works
https://bugs.kde.org/show_bug.cgi?id=484464 Bug ID: 484464 Summary: Move to Next / Previous Screen shortcut no longer works Classification: Applications Product: yakuake Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: h...@kde.org Reporter: kmcwilliampub...@gmail.com Target Milestone: --- SUMMARY Previous to Plasma 6 the display that Yakuake lived on could be changed with the keyboard shortcuts: - `Window to Next Screen` (default Meta+Shift+Right) - `Window to Previous Screen` (default Meta+Shift+Left) Since Plasma 6 this no longer works, instead the window flashes momentarily but stays on the same screen. STEPS TO REPRODUCE 1. Open Yakuake on a left-hand screen 2. Invoke `Window to Next Screen` keyboard shortcut (default Meta+Shift+Right) OBSERVED RESULT Window flashes very briefly EXPECTED RESULT Expected window to move to next screen SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.0.2 / master -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 484523] New: Special characters has no results
https://bugs.kde.org/show_bug.cgi?id=484523 Bug ID: 484523 Summary: Special characters has no results Classification: Plasma Product: krunner Version: 6.0.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: specialcharacters Assignee: plasma-b...@kde.org Reporter: kmcwilliampub...@gmail.com CC: alexander.loh...@gmx.de, natalie_clar...@yahoo.de Target Milestone: --- SUMMARY The Special Characters plugin is not returning results STEPS TO REPRODUCE 1. Ensure the `Special Characters` search plugin is enabled (default) 2. Search for a special character with krunner (with or without prefix), eg. `copyright` or `# copyright` OBSERVED RESULT No results for special characters, in this instance should have been the result for the copyright symbol: ©, but same with other characters (for example, `Yen` for the Japanese currency.) EXPECTED RESULT Expected list of special characters displayed for copying SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 40, Plasma 6.0.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 452636] Humble request to bring back the option to turn off "activate on hover" for sidebar categories
https://bugs.kde.org/show_bug.cgi?id=452636 Kristen McWilliam changed: What|Removed |Added CC||kmcwilliampub...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 418015] Add shortcut: move window to corner
https://bugs.kde.org/show_bug.cgi?id=418015 Kristen McWilliam changed: What|Removed |Added Resolution|--- |DOWNSTREAM Status|ASSIGNED|RESOLVED --- Comment #6 from Kristen McWilliam --- This was implemented by the requester as a KWin script: https://store.kde.org/p/1702170 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483348] Plasma desktop panel moving to wrong screen on next login
https://bugs.kde.org/show_bug.cgi?id=483348 Kristen McWilliam changed: What|Removed |Added CC||kmcwilliampub...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445058] kwin interactive console does not work
https://bugs.kde.org/show_bug.cgi?id=445058 Kristen McWilliam changed: What|Removed |Added CC|kmcwilliampub...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360478] Desktop widgets and Folder View icons do not remember their sizes and positions on a per-resolution basis
https://bugs.kde.org/show_bug.cgi?id=360478 Kristen McWilliam changed: What|Removed |Added CC|kmcwilliampub...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 443727] New: Scroll mouse wheel -> Cycle through desktops not working for MX Master
https://bugs.kde.org/show_bug.cgi?id=443727 Bug ID: 443727 Summary: Scroll mouse wheel -> Cycle through desktops not working for MX Master Product: lattedock Version: 0.10.2 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: kmcwilliampub...@gmail.com Target Milestone: --- SUMMARY One of my mice is a Logitech MX Master, and for some reason scrolling on the taskbar to cycle desktops doesn't work with this specific mouse. STEPS TO REPRODUCE 1. Scroll on empty part of task bar with MX Master OBSERVED RESULT None EXPECTED RESULT Change virtual desktop SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION `evtest` for the MX Master: ``` Event: time 1634226719.154269, -- SYN_REPORT Event: time 1634226719.190266, type 2 (EV_REL), code 11 (REL_WHEEL_HI_RES), value -15 Event: time 1634226719.190266, type 2 (EV_REL), code 8 (REL_WHEEL), value -1 Event: time 1634226719.190266, -- SYN_REPORT Event: time 1634226719.286266, type 2 (EV_REL), code 11 (REL_WHEEL_HI_RES), value -15 Event: time 1634226719.286266, -- SYN_REPORT Event: time 1634226719.330269, type 2 (EV_REL), code 11 (REL_WHEEL_HI_RES), value -15 Event: time 1634226719.330269, -- SYN_REPORT Event: time 1634226719.354264, type 2 (EV_REL), code 11 (REL_WHEEL_HI_RES), value -15 Event: time 1634226719.354264, -- SYN_REPORT Event: time 1634226719.378268, type 2 (EV_REL), code 11 (REL_WHEEL_HI_RES), value -15 Event: time 1634226719.378268, -- SYN_REPORT Event: time 1634226719.850253, type 2 (EV_REL), code 11 (REL_WHEEL_HI_RES), value -15 Event: time 1634226719.850253, -- SYN_REPORT Event: time 1634226719.874254, type 2 (EV_REL), code 11 (REL_WHEEL_HI_RES), value -15 Event: time 1634226719.874254, -- SYN_REPORT Event: time 1634226719.890252, type 2 (EV_REL), code 11 (REL_WHEEL_HI_RES), value -15 Event: time 1634226719.890252, -- SYN_REPORT Event: time 1634226719.898248, type 2 (EV_REL), code 11 (REL_WHEEL_HI_RES), value -15 Event: time 1634226719.898248, type 2 (EV_REL), code 8 (REL_WHEEL), value -1 Event: time 1634226719.898248, -- SYN_REPORT Event: time 1634226719.906250, type 2 (EV_REL), code 11 (REL_WHEEL_HI_RES), value -15 Event: time 1634226719.906250, -- SYN_REPORT Event: time 1634226719.922250, type 2 (EV_REL), code 11 (REL_WHEEL_HI_RES), value -15 Event: time 1634226719.922250, -- SYN_REPORT Event: time 1634226719.930251, type 2 (EV_REL), code 11 (REL_WHEEL_HI_RES), value -15 Event: time 1634226719.930251, -- SYN_REPORT Event: time 1634226719.946250, type 2 (EV_REL), code 11 (REL_WHEEL_HI_RES), value -15 Event: time 1634226719.946250, -- SYN_REPORT Event: time 1634226720.100250, type 2 (EV_REL), code 11 (REL_WHEEL_HI_RES), value -15 Event: time 1634226720.100250, -- SYN_REPORT Event: time 1634226720.172251, type 2 (EV_REL), code 11 (REL_WHEEL_HI_RES), value -15 Event: time 1634226720.172251, -- SYN_REPORT Event: time 1634226720.196248, type 2 (EV_REL), code 11 (REL_WHEEL_HI_RES), value -15 Event: time 1634226720.196248, -- SYN_REPORT Event: time 1634226720.220248, type 2 (EV_REL), code 11 (REL_WHEEL_HI_RES), value -15 Event: time 1634226720.220248, type 2 (EV_REL), code 8 (REL_WHEEL), value -1 Event: time 1634226720.220248, -- SYN_REPORT Event: time 1634226720.236247, type 2 (EV_REL), code 11 (REL_WHEEL_HI_RES), value -15 Event: time 1634226720.236247, -- SYN_REPORT Event: time 1634226720.262249, type 2 (EV_REL), code 11 (REL_WHEEL_HI_RES), value -15 Event: time 1634226720.262249, -- SYN_REPORT Event: time 1634226720.276269, type 2 (EV_REL), code 11 (REL_WHEEL_HI_RES), value -15 Event: time 1634226720.276269, -- SYN_REPORT Event: time 1634226720.302250, type 2 (EV_REL), code 11 (REL_WHEEL_HI_RES), value -15 Event: time 1634226720.302250, -- SYN_REPORT Event: time 1634226720.490245, type 2 (EV_REL), code 11 (REL_WHEEL_HI_RES), value -15 Event: time 1634226720.490245, -- SYN_REPORT Event: time 1634226720.568246, type 2 (EV_REL), code 11 (REL_WHEEL_HI_RES), value -15 Event: time 1634226720.568246, -- SYN_REPORT Event: time 1634226720.592247, type 2 (EV_REL), code 11 (REL_WHEEL_HI_RES), value -15 Event: time 163
[frameworks-plasma] [Bug 443903] New: "QML module not found" in IDE
https://bugs.kde.org/show_bug.cgi?id=443903 Bug ID: 443903 Summary: "QML module not found" in IDE Product: frameworks-plasma Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: components Assignee: notm...@gmail.com Reporter: kmcwilliampub...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- IDE is apparently unable to import plasmoid: `import org.kde.plasma.plasmoid 2.0` > QML module not found (org.kde.plasma.plasmoid). Same experience in QtCreator & KDevelop. This doesn't affect the build, only working on the source code. This makes development more difficult, and in particular poses a barrier to potential new contributors since things like IntelliSense, Go To Definition, quick docs, etc will not work. So far the only insight to the issue has been: > "That module is only present if you're running in a Plasmashell context" Is there any way to resolve this? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 443903] "QML module not found" in IDE
https://bugs.kde.org/show_bug.cgi?id=443903 --- Comment #2 from Kristen McWilliam --- A few examples: plasma-desktop: containments/desktop/package/contents/ui/main.qml applets/keyboardlayout/contents/ui/main.qml plasma-workspace: components/containmentlayoutmanager/qml/BasicAppletContainer.qml kweather: plasmoid/package/contents/ui/main.qml So far every instance I have checked has the same issue. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 443903] "QML module not found" in IDE
https://bugs.kde.org/show_bug.cgi?id=443903 --- Comment #3 from Kristen McWilliam --- Created attachment 142556 --> https://bugs.kde.org/attachment.cgi?id=142556&action=edit qtcreator error -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 443903] "QML module not found" in IDE
https://bugs.kde.org/show_bug.cgi?id=443903 --- Comment #4 from Kristen McWilliam --- Created attachment 142557 --> https://bugs.kde.org/attachment.cgi?id=142557&action=edit kdevelop error -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 443903] "QML module not found" in IDE
https://bugs.kde.org/show_bug.cgi?id=443903 --- Comment #6 from Kristen McWilliam --- Same, and I don't see them in VSCode either. Despite the missing error, do you get any sort of intelligent parsing of doc comments, autocomplete suggestions, go to definition for the things plasmoid imports? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443991] New: Continuous Integration (CI) tests are not running on merge requests
https://bugs.kde.org/show_bug.cgi?id=443991 Bug ID: 443991 Summary: Continuous Integration (CI) tests are not running on merge requests Product: kwin Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: kmcwilliampub...@gmail.com Target Milestone: --- CI of tests is not running. As a result there appear to be failing tests directly from master: ``` 97% tests passed, 4 tests failed out of 152 Total Test time (real) = 260.30 sec The following tests FAILED: 94 - kwin-testInputMethod (Failed) 95 - kwin-testInputMethod-waylandonly (Failed) 104 - kwin-testNightColor (Failed) 105 - kwin-testNightColor-waylandonly (Failed) ``` Unsure of where to file this, happy to move to a more appropriate place if needs be.. 🤷 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 479363] New: Allow resizing clipboard plasmoid to screen height
https://bugs.kde.org/show_bug.cgi?id=479363 Bug ID: 479363 Summary: Allow resizing clipboard plasmoid to screen height Classification: Plasma Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Clipboard Assignee: plasma-b...@kde.org Reporter: kmcwilliampub...@gmail.com Target Milestone: 1.0 SUMMARY Currently the plasmoid can only be resized to a maximum of ~half the screen height, though a user may wish to make it taller. STEPS TO REPRODUCE 1. Click the clipboard icon in the tray 2. Grab the top edge and pull it up as far as possible OBSERVED RESULT Stops expanding at ~half screen height. EXPECTED RESULT Continues expanding as far as space allows. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora (available in About System) KDE Plasma Version: 5.91.90 KDE Frameworks Version: 5.248.0 Qt Version: 6.6.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 479364] New: Add global shortcut to toggle showing clipboard plasmoid
https://bugs.kde.org/show_bug.cgi?id=479364 Bug ID: 479364 Summary: Add global shortcut to toggle showing clipboard plasmoid Classification: Plasma Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Clipboard Assignee: plasma-b...@kde.org Reporter: kmcwilliampub...@gmail.com Target Milestone: 1.0 SUMMARY Currently there is only a shortcut for "Show Clipboard Items at Mouse Position", there should also be a shortcut to toggle show/hide for the plasmoid that _doesn't_ follow the mouse cursor. STEPS TO REPRODUCE 1. Right click clipboard icon in tray, choose `Configure Clipboard...` 2. Select the `Shortcuts` tab on the left OBSERVED RESULT No shortcut available to toggle the plasmoid with a static position EXPECTED RESULT Should be a shortcut to toggle the plasmoid with a static position SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora (available in About System) KDE Plasma Version: 5.91.90 KDE Frameworks Version: 5.248.0 Qt Version: 6.6.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 479364] Add global shortcut to toggle showing clipboard plasmoid
https://bugs.kde.org/show_bug.cgi?id=479364 --- Comment #2 from Kristen McWilliam --- (In reply to Nicolas Fella from comment #1) > All system tray Plasmoids have the ability to set such a shortcut in the > system tray settings. > > What's missing here is the ability to set the same shortcut from the applets > own config I think that needs to have its discoverability improved - even after you said it was there, it took me a hot minute to find where to configure that shortcut. Maybe there should be a default button in the tray plasmoid configs that will bring the user to the system tray settings for its entry, where you can configure the "show" shortcut and when the icon should show in the tray. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 479364] Hard to find the feature to set per-applet keyboard shortcuts for applets that don't expose the functionality in their own config windows
https://bugs.kde.org/show_bug.cgi?id=479364 --- Comment #4 from Kristen McWilliam --- (In reply to Nate Graham from comment #3) > As for the original request, I think that has to be a no. There's not a > reason I can see to set a default keyboard shortcut for one random System > Tray applet but not all the others--especially for an applet that already > has a keyboard shortcut available to access its content in another way. Definitely doesn't need a _default_ shortcut, just a (discoverable) way to set one. > The issue here is that for applets whose "Configure..." button opens a KCM > or nonstandard dialog, you won't see the page that lets you set a keyboard > shortcut for it. For those, you have to do so via the System Tray's own > config dialog, on the "Entries" page. > > I'm not sure how we could improve this, but I'll change the title to reflect > the true issue. Aside from the idea of there being a button that takes the user to the appropriate entry in the System Tray Settings, it can be confusing that the System Tray Settings has both `Entries` (that can configure keyboard shortcuts for various items) and `Keyboard Shortcuts` (which configures only the System Tray Settings shortcut). -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 474866] New: Warning about kservices5 is not helpful
https://bugs.kde.org/show_bug.cgi?id=474866
Bug ID: 474866
Summary: Warning about kservices5 is not helpful
Classification: Plasma
Product: krunner
Version: 5.27.8
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: plasma-b...@kde.org
Reporter: kmcwilliampub...@gmail.com
CC: alexander.loh...@gmx.de, natalie_clar...@yahoo.de
Target Milestone: ---
SUMMARY
***
When starting krunner from the terminal to debug an issue, I noticed this
warning output:
kf.runner: KRunner D-Bus plugin "vscode_runner" installs the .desktop file
("krunner/dbusplugins/plasma-runner-vscode_runner.desktop") still in the
kservices5 folder. Please install it to
${KDE_INSTALL_DATAROOTDIR}/krunner/dbusplugins.
However there doesn't seem to be any info about this variable:
KDE_INSTALL_DATAROOTDIR. It isn't an env var, and Google / bugs.kde.org / KDE
Invent all turn up zilch about it.
***
STEPS TO REPRODUCE
1. Install a plugin that uses the (presumably) depreciated install location,
for example: https://github.com/Merrit/vscode-runner/releases/tag/v1.3.0
2. Run krunner from the terminal
OBSERVED RESULT
Supremely unhelpful message about it using an old install location.
EXPECTED RESULT
A helpful message, or at least documentation somewhere on this variable.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora 38 / Plasma 5.27.8
KDE Plasma Version: 5.27.8
KDE Frameworks Version: 5.109.0
Qt Version: 5.15.10
ADDITIONAL INFORMATION
Looking at the current template readme:
https://invent.kde.org/frameworks/krunner/-/blob/b98f238545dd4b488d6e7cbd96113f44844bb75d/templates/runner6python/README.md
It says to install to ~/.local/share/krunner/dbusplugins/ , so I presume it
means that KDE_INSTALL_DATAROOTDIR should likely be ~/.local/share/ , but again
this doesn't seem documented anywhere, nor did it seem to turn up in code
search.
¯\_(ツ)_/¯
--
You are receiving this mail because:
You are watching all bug changes.
[krunner] [Bug 474866] Warning about kservices5 is not helpful
https://bugs.kde.org/show_bug.cgi?id=474866 --- Comment #3 from Kristen McWilliam --- (In reply to Nate Graham from comment #2) > Yeah, it's a CMake variable, so this is a message mostly intended for > developers to fix. Aye, but the error is reported for a plugin using the dbus interface, which can be any programming language and has no need to rely on CMake. :) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445058] kwin interactive console does not work
https://bugs.kde.org/show_bug.cgi?id=445058 Kristen McWilliam changed: What|Removed |Added CC||kmcwilliampub...@gmail.com --- Comment #17 from Kristen McWilliam --- I can confirm what @hexchain says, `console.info` works - for me nothing else was producing output at all, but this finally did. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 449765] Context menu, no way to remove some elements or position them
https://bugs.kde.org/show_bug.cgi?id=449765 Kristen McWilliam changed: What|Removed |Added CC||kmcwilliampub...@gmail.com --- Comment #1 from Kristen McWilliam --- It would be nice if there was a way to edit the entire context menu, including reordering, changing toplevel or sublevel of items, hiding or showing default items, adding/moving separators, etc. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477061] New: [Feature Request] Provide Typescript definition files
https://bugs.kde.org/show_bug.cgi?id=477061 Bug ID: 477061 Summary: [Feature Request] Provide Typescript definition files Classification: Plasma Product: kwin Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: scripting Assignee: kwin-bugs-n...@kde.org Reporter: kmcwilliampub...@gmail.com Target Milestone: --- It would be very nice if KWin could provide [Typescript definition files](https://www.typescriptlang.org/docs/handbook/2/type-declarations.html) for the scripting API. This would provide type information to the IDE, making it easier to work with KWin scripts by providing autocompletion and documentation directly in the IDE. This would improve efficiency and reduce barriers to entry for people to use KWin scripting, and likely reduce the instances of help requests for people doing things like trying to create KWin scripts. ## Specific example Someone is trying to create their first KWin script and is unfamiliar with all the various types available, and they will have to look up every single property, function, etc in separate documentation. By contrast having the type information available allows one to see directly in the editor things like autocompletion so that something like `workspace.` gives an immediately relevant list of possibilities and how to call them: > Ah, `workspace.activeClient` sounds like exactly what I need! > > `workspace.activeClient.` now gives me a list of properties and functions I > can use on the active client. Nice! ## Benefits - **Reduced barrier to entry** for people to use KWin scripting - **Improved documentation** for the scripting API, since the type information and doc comments would be available directly in the IDE - **Improved efficiency** for people writing KWin scripts, since they don't have to look up the documentation for every single property, function, etc - **Improved code quality** for KWin scripts, since the IDE can provide warnings and errors for things like typos, incorrect types, etc I think this would be a huge improvement to the KWin scripting experience. I know I have struggled a lot with KWin scripting because of the lack of type information and thorough documentation, and I think this would help a lot of people. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 476084] New: Missing icons don't fallback gracefully
https://bugs.kde.org/show_bug.cgi?id=476084 Bug ID: 476084 Summary: Missing icons don't fallback gracefully Classification: Applications Product: Spectacle Version: git-master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: noaha...@gmail.com Reporter: kmcwilliampub...@gmail.com CC: k...@david-redondo.de Target Milestone: --- Created attachment 162563 --> https://bugs.kde.org/attachment.cgi?id=162563&action=edit Shows annotations toolbar with incorrect icons SUMMARY If the active icon theme is missing an icon used in the annotations toolbar, it fails to fallback to the icon from a different theme. STEPS TO REPRODUCE 1. Use an icon theme that is missing one of the used icons; Tela icon theme is known to be missing a couple, or delete for example `draw-arrow.svg` from any other theme, and (re)apply that icon theme. 2. Open Spectacle and take a screenshot 3. Show the annotation tools OBSERVED RESULT If the active icon theme is missing the named icon specified in https://invent.kde.org/graphics/spectacle/-/blob/c35da74aafbbfac9c7fa55259a1b9e1c8ee9915b/src/Gui/AnnotationsToolBarContents.qml#L101 it falls back to a pink brush like icon every time. EXPECTED RESULT If a named icon is missing from the active theme it should fall back to the appropriate icon from Breeze, hicolor, etc. SOFTWARE/OS VERSIONS Linux: Fedora 38 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 Also present in git master and dev session with kf6 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 476084] Missing icons don't fallback gracefully
https://bugs.kde.org/show_bug.cgi?id=476084 --- Comment #2 from Kristen McWilliam --- Agreed, the behaviour seems slightly problematic - as evidenced by every missing icon here falling back to "draw" instead of "draw-highlight", "draw-arrow", etc. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 476084] Missing icons don't fallback gracefully
https://bugs.kde.org/show_bug.cgi?id=476084 --- Comment #4 from Kristen McWilliam --- Do you have a reference for this behaviour? Accoring to the Freedesktop Icon Theme Spec (https://specifications.freedesktop.org/icon-theme-spec/icon-theme-spec-latest.html): "Inherits: The name of the theme that this theme inherits from. If an icon name is not found in the current theme, it is searched for in the inherited theme (and recursively in all the inherited themes)." I checked Tela, and it does specify Inherits: "Inherits=hicolor,Adwaita,breeze". I haven't seen anything about how it searches for the first part of the name instead so far. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 476084] Missing icons don't fallback gracefully
https://bugs.kde.org/show_bug.cgi?id=476084 --- Comment #6 from Kristen McWilliam --- Thank you~ I read through the spec.. "In some cases you don't always want to fall back to an icon in an inherited theme. For instance, sometimes you look for a set of icons, prefering any of them before using an icon from an inherited theme. To support such operations implementations can contain a function that finds the first of a list of icon names in the inheritance hierarchy . . . This can be very useful for example when handling mimetype icons, where there are more and less "specific" versions of icons." This sounds to me like it is intended to be optional, and only for specific circumstances. I'm not actually clear on why this behaviour would be desired instead of a fallback theme really. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kiconthemes] [Bug 476084] When an icon isn't found in the theme, look in its fallback theme before falling back to a more generic icon in the current theme
https://bugs.kde.org/show_bug.cgi?id=476084 --- Comment #9 from Kristen McWilliam --- I like the way you re-worded the title here, checking for the fallback theme _and then_ a generic icon in the current theme sounds quite reasonable (at least at first glance, I am not super familiar with the intricacies.) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kiconthemes] [Bug 476084] When an icon isn't found in the theme, look in its fallback theme before falling back to a more generic icon in the current theme
https://bugs.kde.org/show_bug.cgi?id=476084 --- Comment #11 from Kristen McWilliam --- Agreed, I can see value to both. I am not sure how to reconcile that. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 474973] baloosearch (as well as Dolphin and other apps using baloo) do not find anything when serching files inside the Downloads directory
https://bugs.kde.org/show_bug.cgi?id=474973
Kristen McWilliam changed:
What|Removed |Added
CC||kmcwilliampub...@gmail.com
--- Comment #26 from Kristen McWilliam ---
src/tools/baloosearch/main.cpp
Number of arguments: 2
arg[0] = /home/merritt/Development/kde/build/baloo/bin/baloosearch6
arg[1] = avatar.jpg
query.toJSON(): {"searchString":"avatar.jpg"}
query.toSearchUrl():
baloosearch:?json=%7B%22searchString%22:%22avatar.jpg%22%7D
/home/merritt/Downloads/balootest.txt
/home/merritt/Downloads/avatar.jpg
Elapsed: 1.93772 msecs
Number of arguments: 4
arg[0] = /home/merritt/Development/kde/build/baloo/bin/baloosearch6
arg[1] = -d
arg[2] = /home/merritt/Downloads
arg[3] = avatar.jpg
query.toJSON():
{"includeFolder":"/home/merritt/Downloads","searchString":"avatar.jpg"}
query.toSearchUrl():
baloosearch:?json=%7B%22includeFolder%22:%22/home/merritt/Downloads%22,%22searchString%22:%22avatar.jpg%22%7D
Elapsed: 19.443 msecs
*
I tried to debug the actual implementations, especially in
`SearchStore::constructQuery`, `SearchStore::exec`, and
`Transaction::postingIterator`; but the code there made my brain melt so all I
have is some values extracted from baloosearch.
This does show the error as I am experiencing it, as I have a `avatar.jpg` in
my ~/Downloads folder, and I created a text file `~Downloads/balootest.txt`
with the content of `avatar.jpg` for the purposes of the test. We can see a
plain search finds both, and a search restricted to the Downloads directory
finds nothing.
Popping the `query.toSearchUrl` into Dolphin reveals the same thing, as
expected.
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-baloo] [Bug 474973] baloosearch (as well as Dolphin and other apps using baloo) do not find anything when serching files inside the Downloads directory
https://bugs.kde.org/show_bug.cgi?id=474973 --- Comment #29 from Kristen McWilliam --- Interesting ❯ baloosearch -i avatar.jpg 1c73f77ac33fdc9 /home/merritt/Downloads/balootest.txt 1c44735ac33fdc9 /home/merritt/Downloads/avatar.jpg Elapsed: 1.09867 msecs ❯ baloosearch -i -d /home/merritt/Downloads avatar.jpg Elapsed: 51.9425 msecs ❯ ./baloo-checkdb.py Loading DB from /home/merritt/.local/share/baloo/index... Unique documents: 3 Unique terms: 296550 Checking connectivity of IdTreeDB... ERROR: 162704729950978818 (/???/pubspec.lock) has dangling parent 162704712771109634 (/???) ERROR: 162704734245946114 (/???/pubspec.yaml) has dangling parent 162704712771109634 (/???) ERROR: 162704760015749890 (/???/build) has dangling parent 162704712771109634 (/???) ERROR: 163843793932583682 (/???/linux) has dangling parent 162704712771109634 (/???) ERROR: 164981427690078978 (/???/macos) has dangling parent 162704712771109634 (/???) ERROR: 182410404977246978 (/???/gutter) has dangling parent 182410190228882178 (/???) ERROR: 182410417862148866 (/???/performance-white.png) has dangling parent 182410190228882178 (/???) ERROR: 182410422157116162 (/???/template_new_project.png) has dangling parent 182410190228882178 (/???) ERROR: 182410426452083458 (/???/memory_dashbo...@2x.png) has dangling parent 182410190228882178 (/???) ERROR: 182410430747050754 (/???/template_new_module.png) has dangling parent 182410190228882178 (/???) ERROR: 182410435042018050 (/???/general) has dangling parent 182410190228882178 (/???) ERROR: 182410563891036930 (/???/trackwidget-dgrey.png) has dangling parent 182410190228882178 (/???) ERROR: 182410568186004226 (/???/baselines-white.png) has dangling parent 182410190228882178 (/???) ERROR: 182410572480971522 (/???/custom) has dangling parent 182410190228882178 (/???) ERROR: 182410645495415554 (/???/can...@2x.png) has dangling parent 182410190228882178 (/???) ERROR: 182410649790382850 (/???/trackwidget-white.png) has dangling parent 182410190228882178 (/???) ERROR: 182410654085350146 (/???/reload_debug.png) has dangling parent 182410190228882178 (/???) ERROR: 182410658380317442 (/???/guidelines-dgrey.png) has dangling parent 182410190228882178 (/???) ERROR: 182410662675284738 (/???/images-dgrey.png) has dangling parent 182410190228882178 (/???) ERROR: 182410666970252034 (/???/template_new_plugin.png) has dangling parent 182410190228882178 (/???) ERROR: 182410671265219330 (/???/Icon-192.png) has dangling parent 182410190228882178 (/???) ERROR: 182410675560186626 (/???/flutter_13.png) has dangling parent 182410190228882178 (/???) ERROR: 182410679855153922 (/???/slow-white.png) has dangling parent 182410190228882178 (/???) ERROR: 182410684150121218 (/???/flutter_inspect.png) has dangling parent 182410190228882178 (/???) ERROR: 182410688445088514 (/???/flutter_64.png) has dangling parent 182410190228882178 (/???) ERROR: 182410692740055810 (/???/bazel_...@2x.png) has dangling parent 182410190228882178 (/???) ERROR: 182410697035023106 (/???/images-lgrey.png) has dangling parent 182410190228882178 (/???) ERROR: 182410701329990402 (/???/widget-select-white.png) has dangling parent 182410190228882178 (/???) ERROR: 182410705624957698 (/???/flut...@2x.png) has dangling parent 182410190228882178 (/???) ERROR: 182410709919924994 (/???/cancel.png) has dangling parent 182410190228882178 (/???) ERROR: 182410714214892290 (/???/flutter_t...@2x.png) has dangling parent 182410190228882178 (/???) ERROR: 182410718509859586 (/???/repaints-white.png) has dangling parent 182410190228882178 (/???) ERROR: 182410722804826882 (/???/template_new_package.png) has dangling parent 182410190228882178 (/???) ERROR: 182410727099794178 (/???/perf) has dangling parent 182410190228882178 (/???) ERROR: 182411010567635714 (/???/actions) has dangling parent 182410190228882178 (/???) ERROR: 182411027747504898 (/???/refresh-white.png) has dangling parent 182410190228882178 (/???) ERROR: 182411032042472194 (/???/guidelines-white.png) has dangling parent 182410190228882178 (/???) ERROR: 182411036337439490 (/???/hot-rest...@2x.png) has dangling parent 182410190228882178 (/???) ERROR: 182411040632406786 (/???/phone.png) has dangling parent 182410190228882178 (/???) ERROR: 182411044927374082 (/???/flutter.png) has dangling parent 182410190228882178 (/???) ERROR: 182411049222341378 (/???/flutter...@2x.png) has dangling parent 182410190228882178 (/???) ERROR: 182411053517308674 (/???/inspector) has dangling parent 182410190228882178 (/???) ERROR: 182411384229790466 (/???/feedback.png) has dangling parent 182410190228882178 (/???) ERROR: 182411388524757762 (/???/widget-select-dgrey.png) has dangling parent 182410190228882178 (/???) ERROR: 182411392819725058 (/???/observatory_overflow.png) has dangling parent 182410190228882178 (/???) ERROR: 182411397114692354 (/???/timeline.png) has dangling parent 182410190228882178 (/???) ERROR: 182411401409659650 (/???/observat...@2x.png) has dangling parent 182410190228882178 (/???) ERROR: 182411405704626946
[kwin] [Bug 445058] kwin interactive console does not work
https://bugs.kde.org/show_bug.cgi?id=445058 Kristen McWilliam changed: What|Removed |Added CC||kmcwilliampub...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kauth] [Bug 363678] kauth_install_actions does not honour CMAKE_INSTALL_PREFIX
https://bugs.kde.org/show_bug.cgi?id=363678 Kristen McWilliam changed: What|Removed |Added CC||kmcwilliampub...@gmail.com --- Comment #11 from Kristen McWilliam --- Ran into this while trying to extend a KAuth helper; really unfortunate developer experience. If we don't have a good way to resolve the root issues, perhaps someone familiar could at least update the KAuth guide with information about how to properly build and test: https://develop.kde.org/docs/features/kauth/using_kauth/ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 490314] New: Plasma crashes when display config switches
https://bugs.kde.org/show_bug.cgi?id=490314 Bug ID: 490314 Summary: Plasma crashes when display config switches Classification: Plasma Product: plasmashell Version: 6.1.1 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: kmcwilliampub...@gmail.com Target Milestone: 1.0 Application: plasmashell (6.1.1) Qt Version: 6.7.2 Frameworks Version: 6.3.0 Operating System: Linux 6.9.7-200.fc40.x86_64 x86_64 Windowing System: Wayland Distribution: "Fedora Linux 40 (KDE Plasma)" DrKonqi: 6.1.1 [CoredumpBackend] -- Information about the crash: The crash seems to happen in 2 scenarios: - One of the attached displays is turned off, and goes in to a sleep mode where it is momentarily seen as disconnected - I press a hotkey that runs a script, which changes the enabled displays using kscreen-doctor The crash can be reproduced sometimes. -- Backtrace (Reduced): #5 QtWaylandClient::QWaylandWindow::waylandScreen (this=this@entry=0x565051f99590) at /usr/src/debug/qt6-qtwayland-6.7.2-1.fc40.x86_64/src/client/qwaylandwindow.cpp:956 #6 0x7f7bc54dedab in QtWaylandClient::QWaylandWindow::devicePixelRatio (this=0x565051f99590) at /usr/src/debug/qt6-qtwayland-6.7.2-1.fc40.x86_64/src/client/qwaylandwindow.cpp:1517 #7 QtWaylandClient::QWaylandWindow::scale (this=this@entry=0x565051f99590) at /usr/src/debug/qt6-qtwayland-6.7.2-1.fc40.x86_64/src/client/qwaylandwindow.cpp:1514 #8 0x7f7bafa71fdb in QtWaylandClient::QWaylandEglWindow::updateSurface (this=0x565051f99590, create=true) at /usr/src/debug/qt6-qtwayland-6.7.2-1.fc40.x86_64/src/hardwareintegration/client/wayland-egl/qwaylandeglwindow.cpp:70 #9 0x7f7bafa72973 in QtWaylandClient::QWaylandGLContext::makeCurrent (this=this@entry=0x7f7abc593c20, surface=) at /usr/src/debug/qt6-qtwayland-6.7.2-1.fc40.x86_64/src/hardwareintegration/client/wayland-egl/qwaylandglcontext.cpp:318 Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 490314] Plasma crashes when display config switches
https://bugs.kde.org/show_bug.cgi?id=490314 --- Comment #1 from Kristen McWilliam --- Created attachment 171682 --> https://bugs.kde.org/attachment.cgi?id=171682&action=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 366032] plasma-pa should allow to select the sink for volume control
https://bugs.kde.org/show_bug.cgi?id=366032 --- Comment #4 from Kristen McWilliam --- Yeah, I agree. I ended up doing exactly that, just rebinding the volume keys on my keyboard to control it like you described. Much better than adding a ton of complexity for an edge case like this. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 495652] Unable to modify displays since 6.2
https://bugs.kde.org/show_bug.cgi?id=495652 Kristen McWilliam changed: What|Removed |Added Attachment #175418|0 |1 is obsolete|| --- Comment #3 from Kristen McWilliam --- Created attachment 175564 --> https://bugs.kde.org/attachment.cgi?id=175564&action=edit kscreen-doctor with WAYLAND_DEBUG=1 Attaching the kscreen-doctor output when run with WAYLAND_DEBUG=1. The wiki says the kwin logs should be at ~/.local/share/sddm/wayland-session.log but the sddm folder doesn't exist on my system, and I have QT_LOGGING_RULES="kwin_*.debug=true" in my /etc/environment (and rebooted). -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 495652] Unable to modify displays since 6.2
https://bugs.kde.org/show_bug.cgi?id=495652 --- Comment #1 from Kristen McWilliam --- Created attachment 175418 --> https://bugs.kde.org/attachment.cgi?id=175418&action=edit kscreen.log with debug enabled -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 495652] New: Unable to modify displays since 6.2
https://bugs.kde.org/show_bug.cgi?id=495652 Bug ID: 495652 Summary: Unable to modify displays since 6.2 Classification: Plasma Product: KScreen Version: 6.2.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: kscreen-bugs-n...@kde.org Reporter: kmcwilliampub...@gmail.com Target Milestone: --- SUMMARY In both the KCM & with kscreen-doctor I can no longer enable/disable monitors at will; I think it began with 6.2. kscreen-doctor fails silently. Trying to configure the displays in the KCM causes the changes to appear reverted immediately after clicking Apply, and it does not seem like the displays tried to change configuration. I have 3 displays connected; 2 monitors and 1 TV. One monitor uses DP, other other displays both use HDMI. It only happens sometimes, but I can't seem to find a pattern. When I am unable to switch to the TV the only thing that works is to unplug the power from one of the monitors, then it suddenly works. STEPS TO REPRODUCE 1. Have 2 monitors enabled, TV disabled. 2. Disable both monitors and enable the TV. OBSERVED RESULT Changes revert/fail silently. EXPECTED RESULT Monitors' output should be disabled, output to TV should be enabled. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 40 KDE Plasma Version: 6.2.2 KDE Frameworks Version: 6.7.0 Qt Version: 6.7.2 Kernel Version: 6.11.4-201.fc40.x86_64 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 3700X 8-Core Processor Memory: 47.0 GiB of RAM Graphics Processor: AMD Radeon RX 580 Series ADDITIONAL INFORMATION ``` ❯ kscreen-doctor --outputs [ 16:38:13.617 ] kscreen.kwayland: KScreen::WaylandConfig::addOutput 195: adding output 63 [ 16:38:13.617 ] kscreen.kwayland: KScreen::WaylandConfig::addOutput 195: adding output 64 [ 16:38:13.618 ] kscreen.kwayland: KScreen::WaylandConfig::addOutput 195: adding output 65 [ 16:38:13.618 ] kscreen.kwayland: KScreen::WaylandBackend::WaylandBackend 31: Loading Wayland backend. Output: 1 DP-1 enabled connected priority 1 DisplayPort Modes: 1:3840x2160@60*! 2:3840x2160@60 3:3840x2160@60 4:3840x2160@50 5:3840x2160@30 6:3840x2160@30 7:3840x2160@25 8:3840x2160@24 9:3840x2160@24 10:2560x1440@60 11:1920x1200@60 12:1920x1080@60 13:1920x1080@60 14:1920x1080@60 15:1920x1080@50 16:1920x1080@24 17:1920x1080@24 18:1920x1080@24 19:1920x1080@24 20:1600x1200@60 21:1680x1050@60 22:1280x1024@60 23:1440x900@60 24:1280x960@60 25:1280x800@60 26:1280x720@60 27:1280x720@60 28:1280x720@60 29:1280x720@50 30:1440x576@50 31:1440x576@50 32:1024x768@60 33:1440x480@60 34:1440x480@60 35:1440x480@60 36:1440x480@60 37:800x600@60 38:800x600@56 39:720x576@50 40:720x480@60 41:720x480@60 42:720x480@60 43:720x480@60 44:640x480@60 45:640x480@60 46:640x480@60 47:1600x1200@60 48:1280x1024@60 49:1024x768@60 50:2560x1600@60 51:1920x1200@60 52:3840x2160@60 53:3200x1800@60 54:2880x1620@60 55:2560x1440@60 56:1920x1080@60 57:1600x900@60 58:1368x768@60 59:1280x720@60 Geometry: 0,0 2560x1440 Scale: 1.5 Rotation: 1 Overscan: 0 Vrr: Automatic RgbRange: unknown HDR: disabled Wide Color Gamut: disabled ICC profile: none Color profile source: sRGB Brightness control: supported, set to 85% Output: 2 HDMI-A-1 disabled connected priority 0 HDMI Modes: 60:3840x2160@60*! 61:4096x2160@60 62:4096x2160@60 63:4096x2160@30 64:4096x2160@30 65:4096x2160@24 66:4096x2160@24 67:3840x2160@60 68:3840x2160@60 69:3840x2160@30 70:3840x2160@30 71:3840x2160@30 72:3840x2160@24 73:3840x2160@24 74:1920x1200@60 75:1920x1080@60 76:1920x1080@60 77:1920x1080@60 78:1920x1080@30 79:1920x1080@30 80:1920x1080@24 81:1920x1080@24 82:1600x1200@60 83:1680x1050@60 84:1280x1024@75 85:1280x1024@60 86:1440x900@60 87:1280x960@60 88:1280x800@60 89:1152x864@75 90:1280x720@60 91:1280x720@60 92:1280x720@60 93:1280x720@30 94:1280x720@30 95:1280x720@24 96:1280x720@24 97:1024x768@75 98:1024x768@70 99:1024x768@60 100:800x600@75 101:800x600@72 102:800x600@60 103:720x480@60 104:720x480@60 105:640x480@75 106:640x480@73 107:640x480@60 108:640x480@60 109:640x480@60 110:720x400@70 111:1600x1200@60 112:1280x1024@60 113:1024x768@60 114:2560x1600@60 115:1920x1200@60 116:1280x800@60 117:3840x2160@60 118:3200x1800@60 119:2880x1620@60 120:2560x1440@60 121:1920x1080@60 122:1600x900@60 123:1368x768@60 124:1280x720@60 Geometry: 0,0 2560x1440 Scale: 1.5 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown HDR: disabled Wide Color Gamut: disabled ICC profile: none Color profile source: sRGB Brightness control: supported, se
[krunner] [Bug 493859] Help needed: Flaktpak + krunner DBus plugin
https://bugs.kde.org/show_bug.cgi?id=493859 Kristen McWilliam changed: What|Removed |Added CC||kmcwilliampub...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 495652] Unable to modify displays since 6.2
https://bugs.kde.org/show_bug.cgi?id=495652 Kristen McWilliam changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 451539] Allow fast copy to clipboard on received SMS
https://bugs.kde.org/show_bug.cgi?id=451539 Kristen McWilliam changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/netw ||ork/kdeconnect-kde/-/commit ||/caaac80ca5cde5d94cdf3617a4 ||fba4b4a19f38b2 --- Comment #2 from Kristen McWilliam --- Git commit caaac80ca5cde5d94cdf3617a4fba4b4a19f38b2 by Kristen McWilliam. Committed on 17/10/2024 at 17:51. Pushed by merritt into branch 'fix_copy_auth_code'. fix: copy auth code to desktop clipboard SMS auth codes generate a notification that has a "Copy $code" button (eg. "Copy 123456"), but the button doesn't actually copy the code as expected. This patch fixes that. Related: bug 435614 M +2-1plugins/notifications/CMakeLists.txt M +30 -0plugins/notifications/notificationsplugin.cpp M +8-0plugins/notifications/notificationsplugin.h M +3-0tests/CMakeLists.txt A +93 -0tests/notificationstest.cpp [License: GPL(3+eV) GPL(v3.0) GPL(v2.0)] https://invent.kde.org/network/kdeconnect-kde/-/commit/caaac80ca5cde5d94cdf3617a4fba4b4a19f38b2 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 435614] Unable to copy text from popup for SMS
https://bugs.kde.org/show_bug.cgi?id=435614 Kristen McWilliam changed: What|Removed |Added Resolution|WORKSFORME |FIXED Latest Commit||https://invent.kde.org/netw ||ork/kdeconnect-kde/-/commit ||/caaac80ca5cde5d94cdf3617a4 ||fba4b4a19f38b2 --- Comment #5 from Kristen McWilliam --- Git commit caaac80ca5cde5d94cdf3617a4fba4b4a19f38b2 by Kristen McWilliam. Committed on 17/10/2024 at 17:51. Pushed by merritt into branch 'fix_copy_auth_code'. fix: copy auth code to desktop clipboard SMS auth codes generate a notification that has a "Copy $code" button (eg. "Copy 123456"), but the button doesn't actually copy the code as expected. This patch fixes that. Related: bug 451539 M +2-1plugins/notifications/CMakeLists.txt M +30 -0plugins/notifications/notificationsplugin.cpp M +8-0plugins/notifications/notificationsplugin.h M +3-0tests/CMakeLists.txt A +93 -0tests/notificationstest.cpp [License: GPL(3+eV) GPL(v3.0) GPL(v2.0)] https://invent.kde.org/network/kdeconnect-kde/-/commit/caaac80ca5cde5d94cdf3617a4fba4b4a19f38b2 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 495652] Unable to modify displays since 6.2
https://bugs.kde.org/show_bug.cgi?id=495652 --- Comment #8 from Kristen McWilliam --- Created attachment 178000 --> https://bugs.kde.org/attachment.cgi?id=178000&action=edit drm debug log -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 495652] Unable to modify displays since 6.2
https://bugs.kde.org/show_bug.cgi?id=495652 --- Comment #9 from Kristen McWilliam --- I got kwin logs by doing: > journalctl --since "2 minutes ago" -f --user-unit plasma-kwin_wayland .. and reproducing the issue. The only thing that outputs when I do so is: > Feb 05 12:37:14 SHODAN kwin_wayland[2151]: kwin_core: Applying config failed Which I believe is from https://invent.kde.org/plasma/libkscreen/-/blob/cbe11cd62064a2e9f85b3664f5cd97b10d553903/src/doctor/doctor.cpp#L491 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 495652] Unable to modify displays since 6.2
https://bugs.kde.org/show_bug.cgi?id=495652 --- Comment #5 from Kristen McWilliam --- (In reply to David Edmundson from comment #4) > Is this still an issue? It is. I've been very time constrained lately, so I have only looked into it a little bit so far and haven't tracked down the issue as yet. Also present on the master branches as of last week when I was looking at it. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 484523] Special characters has no results
https://bugs.kde.org/show_bug.cgi?id=484523 --- Comment #2 from Kristen McWilliam --- I think you are correct, the description says it is for entering the hex code. I presumed it was for finding the characters via keywords, which seems much more useful. There is a 3rd party runner that does this here: https://github.com/domschrei/krunner-symbols It doesn't seem fully updated for Plasma 6 though. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 495652] Unable to modify displays since 6.2
https://bugs.kde.org/show_bug.cgi?id=495652 --- Comment #10 from Kristen McWilliam --- Fixed my logging rules > QT_LOGGING_RULES="kwin_*.debug=true" It provides a few more lines of output now: Feb 05 19:30:59 SHODAN kwin_wayland[4109]: kwin_wayland_drm: Atomic modeset test failed! Cannot allocate memory Feb 05 19:30:59 SHODAN kwin_wayland[4109]: kwin_wayland_drm: Atomic modeset test failed! Cannot allocate memory Feb 05 19:30:59 SHODAN kwin_wayland[4109]: kwin_wayland_drm: Atomic modeset test failed! Cannot allocate memory Feb 05 19:30:59 SHODAN kwin_wayland[4109]: kwin_wayland_drm: Atomic modeset test failed! Cannot allocate memory Feb 05 19:30:59 SHODAN kwin_wayland[4109]: kwin_wayland_drm: Atomic modeset test failed! Cannot allocate memory Feb 05 19:30:59 SHODAN kwin_wayland[4109]: kwin_wayland_drm: Atomic modeset test failed! Cannot allocate memory Feb 05 19:30:59 SHODAN kwin_wayland[4109]: kwin_core: Applying config failed -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 499008] "clean metadata" does not work
https://bugs.kde.org/show_bug.cgi?id=499008 Kristen McWilliam changed: What|Removed |Added CC||kmcwilliampub...@gmail.com --- Comment #8 from Kristen McWilliam --- Perhaps we should consider a way in the settings to show info about a plugin such as if it was installed from the "Get New.." or other, as well as any metadata about author/links/etc if available. Would make it easier for users to determine where they come from, and who to contact about them. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 495652] Unable to modify displays since 6.2
https://bugs.kde.org/show_bug.cgi?id=495652 --- Comment #14 from Kristen McWilliam --- Thanks for looking at that, appreciate it! I made a bug report here: https://gitlab.freedesktop.org/drm/amd/-/issues/3967 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 495652] Unable to modify displays since 6.2
https://bugs.kde.org/show_bug.cgi?id=495652 --- Comment #12 from Kristen McWilliam --- (In reply to Zamundaaa from comment #11) > If you follow the steps at > https://invent.kde.org/plasma/kwin/-/wikis/Debugging/Debugging-DRM-issues, > you might be able to get more information about the underlying issue. I did follow the steps there, does the drm debug log I attached not contain the necessary info? I've looked through it a bit, but as you say it is quite verbose and I am not sure what to look for. -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 501991] Job progress notification from Flatpaked browser via plasma-browser-integration freezes and OOMs plasmashell
https://bugs.kde.org/show_bug.cgi?id=501991 Kristen McWilliam changed: What|Removed |Added CC||kmcwilliampub...@gmail.com --- Comment #1 from Kristen McWilliam --- For me this also happens with the non-flatpak system installation of Firefox. (Fedora 41) Just signed into a dev session and started a download with Firefox. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 451539] Allow fast copy to clipboard on received SMS
https://bugs.kde.org/show_bug.cgi?id=451539 Kristen McWilliam changed: What|Removed |Added Latest Commit|https://invent.kde.org/netw |https://invent.kde.org/netw |ork/kdeconnect-kde/-/commit |ork/kdeconnect-kde/-/commit |/caaac80ca5cde5d94cdf3617a4 |/92e61c07c639c3a2b7e6e87478 |fba4b4a19f38b2 |777142bd97dafb --- Comment #3 from Kristen McWilliam --- Git commit 92e61c07c639c3a2b7e6e87478777142bd97dafb by Kristen McWilliam. Committed on 26/03/2025 at 16:07. Pushed by merritt into branch 'master'. fix: copy auth code to desktop clipboard SMS auth codes generate a notification that has a "Copy $code" button (eg. "Copy 123456"), but the button doesn't actually copy the code as expected. This patch fixes that. Related: bug 435614 M +2-1plugins/notifications/CMakeLists.txt M +30 -0plugins/notifications/notificationsplugin.cpp M +8-0plugins/notifications/notificationsplugin.h M +3-0tests/CMakeLists.txt A +93 -0tests/notificationstest.cpp [License: GPL(3+eV) GPL(v3.0) GPL(v2.0)] https://invent.kde.org/network/kdeconnect-kde/-/commit/92e61c07c639c3a2b7e6e87478777142bd97dafb -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 435614] Unable to copy text from popup for SMS
https://bugs.kde.org/show_bug.cgi?id=435614 Kristen McWilliam changed: What|Removed |Added Latest Commit|https://invent.kde.org/netw |https://invent.kde.org/netw |ork/kdeconnect-kde/-/commit |ork/kdeconnect-kde/-/commit |/caaac80ca5cde5d94cdf3617a4 |/92e61c07c639c3a2b7e6e87478 |fba4b4a19f38b2 |777142bd97dafb --- Comment #6 from Kristen McWilliam --- Git commit 92e61c07c639c3a2b7e6e87478777142bd97dafb by Kristen McWilliam. Committed on 26/03/2025 at 16:07. Pushed by merritt into branch 'master'. fix: copy auth code to desktop clipboard SMS auth codes generate a notification that has a "Copy $code" button (eg. "Copy 123456"), but the button doesn't actually copy the code as expected. This patch fixes that. Related: bug 451539 M +2-1plugins/notifications/CMakeLists.txt M +30 -0plugins/notifications/notificationsplugin.cpp M +8-0plugins/notifications/notificationsplugin.h M +3-0tests/CMakeLists.txt A +93 -0tests/notificationstest.cpp [License: GPL(3+eV) GPL(v3.0) GPL(v2.0)] https://invent.kde.org/network/kdeconnect-kde/-/commit/92e61c07c639c3a2b7e6e87478777142bd97dafb -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 502585] Keyboard layout set during installation/setup (tested Arch's archinstall or Fedora's Anaconda) doesn't appear in Keyboard KCM
https://bugs.kde.org/show_bug.cgi?id=502585 Kristen McWilliam changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #7 from Kristen McWilliam --- Looks like layout chosen during install isn't listed in the KCM afterwards, regardless of installer/distro/language. Confirmed on my system (Fedora 41), Kinoite, and openSUSE Tumbleweed. > Assuming the devs are in the US; You reproduce the issue by trying to install > any of these distros with abnt2 keyboard layout, then post-installation you > should notice that your keyboard is working fine, which shouldn't be the case. I tried this by installing with language set to Japanese, and the keyboard layout does in fact seem to be Japanese afterwards, it just isn't listed. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 502585] Keyboard layout set during installation doesn't appear in Keyboard KCM
https://bugs.kde.org/show_bug.cgi?id=502585 Kristen McWilliam changed: What|Removed |Added Summary|Keyboard layout set during |Keyboard layout set during |installation/setup (tested |installation doesn't appear |Arch's archinstall or |in Keyboard KCM |Fedora's Anaconda) doesn't | |appear in Keyboard KCM | -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 476967] Plasma Integration Firefox extension does not work on LibreWolf
https://bugs.kde.org/show_bug.cgi?id=476967 Kristen McWilliam changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED CC||kmcwilliampub...@gmail.com --- Comment #3 from Kristen McWilliam --- Resolved with https://invent.kde.org/plasma/plasma-browser-integration/-/commit/5723f037b7761ff66f662098cdced6dbf4124704 -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 476967] Plasma Integration Firefox extension does not work on LibreWolf
https://bugs.kde.org/show_bug.cgi?id=476967 Kristen McWilliam changed: What|Removed |Added Status|RESOLVED|REOPENED Ever confirmed|0 |1 Resolution|FIXED |--- --- Comment #5 from Kristen McWilliam --- You're right, the bug being closed should've waited for the separate commit for the regular version. Thanks for pointing that out. The regular version will be submitted shortly. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 502585] Keyboard layout set during installation doesn't appear in Keyboard KCM
https://bugs.kde.org/show_bug.cgi?id=502585 --- Comment #8 from Kristen McWilliam --- Seems like it might be x11 only: https://invent.kde.org/plasma/plasma-desktop/-/blob/139cc1c06454e31cc87fb3c3fa799f5591d98ab9/kcms/keyboard/kcm_keyboard.cpp#L50 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 502585] Keyboard layout set during installation doesn't appear in Keyboard KCM
https://bugs.kde.org/show_bug.cgi?id=502585 --- Comment #9 from Kristen McWilliam --- .. which is backed up by the fact that the bug isn't present in an x11 session. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 495652] Unable to modify displays since 6.2
https://bugs.kde.org/show_bug.cgi?id=495652 --- Comment #15 from Kristen McWilliam --- (In reply to Zamundaaa from comment #13) > I don't think there's anything we can do about it certainly, the issue is > completely in the layer below us. Occurs to me we should still find a way to catch this sort of error, and present a message to the user about it rather than failing silently. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 495652] Unable to modify displays since 6.2
https://bugs.kde.org/show_bug.cgi?id=495652 --- Comment #17 from Kristen McWilliam --- Ah that's unfortunate. Guess that'll have to do for now. Thanks :) -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 476967] Plasma Integration Firefox extension does not work on LibreWolf
https://bugs.kde.org/show_bug.cgi?id=476967 Kristen McWilliam changed: What|Removed |Added Latest Commit||https://invent.kde.org/plas ||ma/plasma-browser-integrati ||on/-/commit/80ff71965fec75c ||51773b20f7c724976ccb728a3 Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #7 from Kristen McWilliam --- Git commit 80ff71965fec75c51773b20f7c724976ccb728a3 by Kristen McWilliam. Committed on 12/05/2025 at 20:43. Pushed by merritt into branch 'master'. feat: add librewolf support M +6-0CMakeLists.txt https://invent.kde.org/plasma/plasma-browser-integration/-/commit/80ff71965fec75c51773b20f7c724976ccb728a3 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 493975] Breeze Icons 6.6 makes `dialog-information` display at too large a size toolbar of Virtual Machine Manager app
https://bugs.kde.org/show_bug.cgi?id=493975 Kristen McWilliam changed: What|Removed |Added Status|ASSIGNED|RESOLVED CC||kris...@kde.org Resolution|--- |FIXED --- Comment #13 from Kristen McWilliam --- Fixed with https://invent.kde.org/frameworks/breeze-icons/-/commit/135e59fb4395c1779a52ab113cc70f7baa53fd5d -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 504350] Plasma notifies about unread notifications even when there is no unread notification
https://bugs.kde.org/show_bug.cgi?id=504350 --- Comment #5 from Kristen McWilliam --- (In reply to Nate Graham from comment #4) > Notably, with today's git master (and *not* Akseli's patch), I can't > reproduce this using the steps provided. Same here, I can't seem to reproduce on either stable or git master. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 504803] When in screensaver mode, don't show interactive UI elements, since they can't be interacted with
https://bugs.kde.org/show_bug.cgi?id=504803 --- Comment #9 from Kristen McWilliam --- I can also confirm, this bug has been annoying me. Thanks for opening the issue! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 503724] "Reviews and Comments" is styled as a web URL link, but navigates pages within the dialog
https://bugs.kde.org/show_bug.cgi?id=503724 Kristen McWilliam changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/fram ||eworks/knewstuff/-/commit/e ||833d3140aeaa40b19fd0043c93e ||f5a51959c5ed Status|ASSIGNED|RESOLVED --- Comment #4 from Kristen McWilliam --- Git commit e833d3140aeaa40b19fd0043c93ef5a51959c5ed by Kristen McWilliam, on behalf of John Veness. Committed on 29/05/2025 at 13:06. Pushed by merritt into branch 'master'. Change "Comments and Reviews" link into a button Right now this is a link but doesn't open a URL, violating the HIG guideline against this. Instead, make it a conventional button. With credit and many thanks to Nate Graham for his initial work on this (see !363 for more discussion). | Before | After | | -- | -- | |  |  | |  |  | M +8-7src/qtquick/qml/EntryDetails.qml https://invent.kde.org/frameworks/knewstuff/-/commit/e833d3140aeaa40b19fd0043c93ef5a51959c5ed -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 502423] "You missed some notifications" notification that appears after exiting DND mode isn't actionable
https://bugs.kde.org/show_bug.cgi?id=502423 Kristen McWilliam changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/plas ||ma/plasma-workspace/-/commi ||t/9fabf42c39a25308739dd3483 ||881cc889243bf58 Status|ASSIGNED|RESOLVED --- Comment #4 from Kristen McWilliam --- Git commit 9fabf42c39a25308739dd3483881cc889243bf58 by Kristen McWilliam. Committed on 24/06/2025 at 21:44. Pushed by merritt into branch 'master'. applets/notifications: Add actions to missed notifications notification When a notification is displayed informing the user that notifications were missed while in Do Not Disturb, now clicking the button or the notification itself will open the notifications applet to show the missed notifications. M +10 -0applets/notifications/package/contents/ui/main.qml M +25 -9libnotificationmanager/notifications.cpp M +7-0libnotificationmanager/notifications.h https://invent.kde.org/plasma/plasma-workspace/-/commit/9fabf42c39a25308739dd3483881cc889243bf58 -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 402634] Hotkey to open/retract yakuake doesn't work in Wayland if flag "Use Open/Retract action to focus window" is set
https://bugs.kde.org/show_bug.cgi?id=402634 Kristen McWilliam changed: What|Removed |Added CC||kris...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 505684] Windows pinned to appear on multiple virtual desktops don't sync position and size once they are either Quick or Custom Tiled
https://bugs.kde.org/show_bug.cgi?id=505684 Kristen McWilliam changed: What|Removed |Added CC||kris...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 505169] 'Do not disturb' notification briefly visible in panel when going into and out of fullscreen
https://bugs.kde.org/show_bug.cgi?id=505169 --- Comment #4 from Kristen McWilliam --- Its an interesting question; if you don't have the notifications applet pinned to the panel, it needs to show up to indicate something. I'm not sure off the top of my head what a good UX for this would be. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 502585] Keyboard layout set during installation doesn't appear in Keyboard KCM
https://bugs.kde.org/show_bug.cgi?id=502585 --- Comment #12 from Kristen McWilliam --- My previous comment was confusing; the bug is only present in Wayland sessions, so it affects anyone running Wayland. (which I presume is most people by now..) -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 506332] Post-Screenshot toolbar menu "save", "save as", and "copy" are icon only
https://bugs.kde.org/show_bug.cgi?id=506332 Kristen McWilliam changed: What|Removed |Added CC||kris...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[KDE Initial System Setup] [Bug 506153] Use more intuitive placement for arrow in Next button
https://bugs.kde.org/show_bug.cgi?id=506153 Kristen McWilliam changed: What|Removed |Added Latest Commit||https://invent.kde.org/syst ||em/kiss/-/commit/ced9c3798a ||8d6ddc695e45e5e6a8ec3fc2287 ||3d7 Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #3 from Kristen McWilliam --- Git commit ced9c3798a8d6ddc695e45e5e6a8ec3fc22873d7 by Kristen McWilliam. Committed on 25/06/2025 at 20:19. Pushed by merritt into branch 'master'. fix: next arrow position in wizard Defaults to the left of the label, which looks odd. M +2-0src/qml/Wizard.qml https://invent.kde.org/system/kiss/-/commit/ced9c3798a8d6ddc695e45e5e6a8ec3fc22873d7 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 505684] Windows pinned to appear on multiple virtual desktops don't sync position and size once they are either Quick or Custom Tiled
https://bugs.kde.org/show_bug.cgi?id=505684 --- Comment #5 from Kristen McWilliam --- I believe this regression was introduced with https://invent.kde.org/plasma/kwin/-/merge_requests/6893 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 507460] New: Unable to go fullscreen
https://bugs.kde.org/show_bug.cgi?id=507460 Bug ID: 507460 Summary: Unable to go fullscreen Classification: Plasma Product: plasmashell Version First master Reported In: Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Web Browser widget Assignee: plasma-b...@kde.org Reporter: kris...@kde.org Target Milestone: 1.0 SUMMARY When selecting a control that would normally go fullscreen in the widget, nothing happens. Example: I have a web browser widget for my Home Assistant on my bar, I pop it up to check my cameras.. I want to see a feed larger, but the fullscreen button for the feed does nothing. STEPS TO REPRODUCE 1. Navigate to a page that has a fullscreen toggle, like a YouTube video 2. Click to go fullscreen OBSERVED RESULT Nothing happens EXPECTED RESULT Content should go fullscreen SOFTWARE/OS VERSIONS Operating System: Fedora Linux 42 KDE Plasma Version: 6.4.80 KDE Frameworks Version: 6.17.0 Qt Version: 6.9.1 Kernel Version: 6.15.6-200.fc42.x86_64 (64-bit) Graphics Platform: Wayland Processors: 32 × AMD Ryzen 9 9950X 16-Core Processor Memory: 128 GiB of RAM (123.4 GiB usable) Graphics Processor 1: AMD Radeon RX 9070 XT Graphics Processor 2: AMD Radeon Graphics -- You are receiving this mail because: You are watching all bug changes.
