[kwin] [Bug 461657] Night color does not deactivate when waking the computer up from sleep
https://bugs.kde.org/show_bug.cgi?id=461657 jade changed: What|Removed |Added Version|5.26.3 |5.27.5 Keywords||wayland CC||k...@lfcode.ca --- Comment #5 from jade --- I don't think it's the same bug as https://bugs.kde.org/show_bug.cgi?id=428357, since the bug here is that the state of night color is mismatched with the state of the actual colour of the monitors, and stays that way. An example of something that will fix this condition for one monitor is to unplug it and plug it back in, or change the resolution. Also, making it preview a different colour temperature then disable the preview will rectify it across all screens. Reproduced on KWin Wayland 5.27.5 on Arch Linux, with AMD Mesa drivers. I believe that this is a wayland only bug since it did not appear to happen on X11 when I was still on X11, but occurs on the same system with the same software version on wayland. Poking the preview can be achieved with a script like so: #!/bin/sh busctl call --user org.kde.KWin /ColorCorrect org.kde.kwin.ColorCorrect preview u 5000 sleep 1 busctl call --user org.kde.KWin /ColorCorrect org.kde.kwin.ColorCorrect stopPreview -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 478595] New: Share via iOS share menu to KDE Connect?
https://bugs.kde.org/show_bug.cgi?id=478595 Bug ID: 478595 Summary: Share via iOS share menu to KDE Connect? Classification: Applications Product: kdeconnect Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: ios-application Assignee: lucas.w...@tuta.io Reporter: k...@lfcode.ca Target Milestone: --- SUMMARY I want to share from an iOS app directly to my computer without having to save a file or photo in the middle. The Android app has a share item that does exactly this, but the iOS one doesn't appear in the share menu on my iPad on version 0.3.0 (9). STEPS TO REPRODUCE 1. Open share menu in e.g. Photos 2. Observe lack of KDE Connect 3. Experience sadness OBSERVED RESULT No KDE Connect in share menu :( EXPECTED RESULT KDE Connect appears in share menu and I can yeet a file to my computer with it. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.11 iOS app version: 0.3.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 482019] When in rectangular capture mode, UI disappears after starting to annotate image
https://bugs.kde.org/show_bug.cgi?id=482019 jade changed: What|Removed |Added CC||k...@lfcode.ca -- You are receiving this mail because: You are watching all bug changes.
[wacomtablet] [Bug 457574] New: kcm-wacomtablet sets express buttons on the wrong device for Huion H640P
https://bugs.kde.org/show_bug.cgi?id=457574 Bug ID: 457574 Summary: kcm-wacomtablet sets express buttons on the wrong device for Huion H640P Product: wacomtablet Version: 3.2.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jazzv...@gmail.com Reporter: k...@lfcode.ca Target Milestone: --- SUMMARY I am using the digimend drivers with the Huion H640P tablet (https://github.com/DIGImend/digimend-kernel-drivers, which I built the latest version of just now). There are four devices exposed by the drivers for this device: ~ » xsetwacom --list devices Tablet Monitor stylus id: 11 type: STYLUS Tablet Monitor Pad pad id: 12 type: PAD Tablet Monitor Touch Strip pad id: 13 type: PAD Tablet Monitor Dial pad id: 14 type: PAD By inspection, I found that kcm-wacomtablet set the buttons on device 14, which makes them not do anything. I then tried setting it on the other devices exposed by the tablet, and found that setting it on device 12 is correct: ~ » xsetwacom --get 14 'Button' 1 key +Control_L +Shift_L +p -p this is what I have in the kcm settings ~ » xsetwacom --set 14 'Button' 1 'key z' *press it* (nothing) ~ » xsetwacom --set 13 'Button' 1 'key z' *press it* (nothing) ~ » xsetwacom --set 12 'Button' 1 'key z' *press it* (z) STEPS TO REPRODUCE 1. Set an Express Button in "Graphic Tablet - System Settings" on a Huion H640P 2. Press the button OBSERVED RESULT Nothing happens, because the settings panel set it on the wrong device. EXPECTED RESULT I would like it to set on the correct device. I know that this device is sorta a weird thing and might need some workaround code :/ SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.25.3 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 Kernel Version: 5.15.55-2-lts (64-bit) Graphics Platform: X11 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[wacomtablet] [Bug 457574] kcm-wacomtablet sets express buttons on the wrong device for Huion H640P
https://bugs.kde.org/show_bug.cgi?id=457574 --- Comment #1 from jade --- Oh, bonus madness: the buttons are in discontinuous order!! The buttons that exist are 1, 2, 3, 8, 9, 10, which are just the six buttons on the left in order top to bottom. There is no obvious reason that they are in a weird order. But this might be something this implementation might run into as well. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 429476] New: App crashes when using any selection tool
https://bugs.kde.org/show_bug.cgi?id=429476 Bug ID: 429476 Summary: App crashes when using any selection tool Product: krita Version: 4.4.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Tools/Selection Assignee: krita-bugs-n...@kde.org Reporter: jdy...@protonmail.com Target Milestone: --- Created attachment 133544 --> https://bugs.kde.org/attachment.cgi?id=133544&action=edit Crash Backtrace File SUMMARY STEPS TO REPRODUCE 1. Using any selection tool (outline, rectangular etc.) 2. Selecting a part of the image 3. Attempt to move the selection OBSERVED RESULT Krita crashed as soon as trying to move the selection EXPECTED RESULT moving the selected part without crashing SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.20.3 KDE Frameworks Version: 5.76.0 Qt Version: 5.15.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 479779] New: textDocument/formatting LSP message causes duplication of buffer text
https://bugs.kde.org/show_bug.cgi?id=479779
Bug ID: 479779
Summary: textDocument/formatting LSP message causes duplication
of buffer text
Classification: Applications
Product: kate
Version: 23.08.4
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: application
Assignee: kwrite-bugs-n...@kde.org
Reporter: k...@lfcode.ca
Target Milestone: ---
Created attachment 164889
--> https://bugs.kde.org/attachment.cgi?id=164889&action=edit
debug log from kate, with lsp logs
SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
Given the following document of Nix code:
let x = 5;
in 1
When the formatting button is pressed using the nixd language server, the
following becomes the buffer content:
in 1
let x = 5;
in 1
This is essentially pasting the content of the file a second time, which is a
bug. This does not happen in neovim with coc, and I strongly suspect this is a
bug in kate's LSP client.
This is what the language server responds to the format request with:
"{\"id\":4,\"jsonrpc\":\"2.0\",\"result\":[{\"newText\":\"let x = 5;\\nin
1\\n\",\"range\":{\"end\":{\"character\":2147483647,\"line\":2147483647},\"start\":{\"character\":0,\"line\":0}}}]}"
This message is intending to overwrite the entire contents of the file with the
provided text. However, kate seems to do something different with it.
I have attached a full debug log of the LSP interaction.
I ran kate with the following:
LSPCLIENT_DEBUG=1 QT_FORCE_STDERR_LOGGING=1
QT_LOGGING_RULES='katelspclientplugin=true;default.debug=true' kate --startanon
-b bad.nix
STEPS TO REPRODUCE
0. Acquire nixd and nixpkgs-fmt from nixpkgs. If you have nix, this can be done
with `nix-shell -p nixd nixpkgs-fmt`, then running kate from the resulting
shell.
1. Configure kate with nixd like so:
{
"servers": {
"nix": {
"command": ["nixd"],
"highlightingModeRegex": "^Nix$"
}
}
}
2. Write this into bad.nix:
let x = 5;
in 1
3. Press the LSP format button
4. Get mangled text
OBSERVED RESULT
Text is mangled.
EXPECTED RESULT
Text should be replaced with the new text from the language server.
SOFTWARE/OS VERSIONS
Operating System: NixOS 24.05
KDE Plasma Version: 5.27.10
KDE Frameworks Version: 5.112.0
Qt Version: 5.15.11
Kernel Version: 6.1.69 (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-7700HQ CPU @ 2.80GHz
Memory: 31.2 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 630
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 475619] Straight lines at the beginnings of strokes with a Wacom Intuos on Plasma Wayland
https://bugs.kde.org/show_bug.cgi?id=475619 Jade changed: What|Removed |Added CC||mashmer...@gmail.com --- Comment #4 from Jade --- Created attachment 162403 --> https://bugs.kde.org/attachment.cgi?id=162403&action=edit Example of the strange behaviour of tablet brush strokes (In reply to Nate Graham from comment #1) > Before you used your pen, was the mouse cursor located in the exact location > on screen that the straight line originated from? It doesn't seem to be related to where the mouse pointer was originally. In this attachment I mark the place where the mouse pointer was left at. However when the tablet brush strokes start, and the straight lines appear and they seem to point to a completely unrelated location to where the mouse cursor was. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475619] Straight lines at the beginnings of strokes with a Wacom Intuos on Plasma Wayland
https://bugs.kde.org/show_bug.cgi?id=475619 Jade changed: What|Removed |Added CC|mashmer...@gmail.com| -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475847] New: KWin scripts should be able to subscribe to DBus signals
https://bugs.kde.org/show_bug.cgi?id=475847 Bug ID: 475847 Summary: KWin scripts should be able to subscribe to DBus signals Classification: Plasma Product: kwin Version: 5.27.8 Platform: Archlinux OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: scripting Assignee: kwin-bugs-n...@kde.org Reporter: k...@lfcode.ca Target Milestone: --- SUMMARY I would like to be able to subscribe to DBus signals from a KWin script, which seems to not be something that is possible (last time I looked at least). Alternatively, it could equally be accomplished by being able to create DBus services from a script, either way would work. As far as I can tell the current state is that it is hard to send any sort of programmatic message to an installed KWin script. The essential use case here is being able to invoke KWin actions from another application. For example, a use for this would be to raise a window by PID using a command line tool: you create a script which stays resident in KWin and then you invoke a DBus service to send a message to the script when you want to raise the window. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 384695] Configurable horizontal scrolling key (ALT or SHIFT) + WHEEL
https://bugs.kde.org/show_bug.cgi?id=384695 jade changed: What|Removed |Added CC||k...@lfcode.ca --- Comment #11 from jade --- Andrew: I have filed a bug on qt about the not-very-related Wayland issue, as it appears that the problem is that qt simply did not implement horizontal scrolling on Wayland at all. You can confirm with launching Okular with `XDG_SESSION_TYPE=x11 okular` https://bugreports.qt.io/browse/QTBUG-118618 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461657] Night color does not deactivate when waking the computer up from sleep
https://bugs.kde.org/show_bug.cgi?id=461657 --- Comment #8 from jade --- Another thought I have is there's another bug that I sometimes experience in which the monitor brightness gets desynchronized after monitors dim for sleep warning: is this a general DDC/DPMS handling bug where the monitor's state gets out of sync? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468295] 5.27.4 Night color remains on at sunrise, can't disable
https://bugs.kde.org/show_bug.cgi?id=468295 jade changed: What|Removed |Added CC||k...@lfcode.ca --- Comment #7 from jade --- See also (possible duplicate): https://bugs.kde.org/show_bug.cgi?id=461657 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468295] 5.27.4 Night color remains on at sunrise, can't disable
https://bugs.kde.org/show_bug.cgi?id=468295 jade changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=461657 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461657] Night color does not deactivate when waking the computer up from sleep
https://bugs.kde.org/show_bug.cgi?id=461657 jade changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=468295 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433170] Option to change update interval
https://bugs.kde.org/show_bug.cgi?id=433170 jade changed: What|Removed |Added Version|unspecified |5.21.0 Component|general |System Monitor Assignee|ksysguard-b...@kde.org |plasma-b...@kde.org Product|plasma-systemmonitor|plasmashell Target Milestone|--- |1.0 CC||k...@lfcode.ca, ||notm...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433170] Option to change update interval
https://bugs.kde.org/show_bug.cgi?id=433170 --- Comment #13 from jade --- Created attachment 136189 --> https://bugs.kde.org/attachment.cgi?id=136189&action=edit flamegraph of plasmashell while running the misbehaving widget -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433170] Option to change update interval
https://bugs.kde.org/show_bug.cgi?id=433170 --- Comment #14 from jade --- I believe I moved the bug successfully. I agree with the usability issues discussed, it basically shows half a second of history, with maybe 2 samples at a time, which is a lot less useful than it used to be prior to plasma 1.21. I dug through the source and it appears to be a regression introduced in https://invent.kde.org/plasma/libksysguard/-/merge_requests/98, but I don't know enough about compiling and running KDE to try bisecting it to make sure. For me, a bug in this widget, likely this one, has caused plasmashell to take 100% CPU on one core of a beefy processor and make the rest of plasmashell to be laggy. I've attached a flamegraph of where the CPU went. I had the CPU widget in the bottom bar of my desktop, with 24 CPU sensors, one per hardware thread. This was not happening continuously and I don't know if I can cause it to reproduce again. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 373869] New: Unable to move docker
https://bugs.kde.org/show_bug.cgi?id=373869 Bug ID: 373869 Summary: Unable to move docker Product: krita Version: 3.1.1 Platform: Other OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: Dockers Assignee: krita-bugs-n...@kde.org Reporter: jadegod...@gmail.com Target Milestone: --- Windows 10 running 3.1.1. When I click and drag a docked window, I'm unable to move it to any location. I'm not seeing any errors or signs I shouldn't be able to move it, the screen adjusts and the area on the side bars highlight as I would expect. But when I hover over the new location, it will snap back to its original position. I'm unable to move from left, right, top, bottom, or even re-order windows. I've attached a video that shows my actions. Out of every attempt I made, it only worked once, and then I couldn't move that successful dock back to its original location. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 373869] Unable to move docker
https://bugs.kde.org/show_bug.cgi?id=373869 --- Comment #1 from Jade --- Unable to upload the video due to size. https://www.dropbox.com/s/9a4an119k2o29vv/2016-12-18-1658-38.flv -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 450815] New: Krita Causes Computer to Freeze
https://bugs.kde.org/show_bug.cgi?id=450815 Bug ID: 450815 Summary: Krita Causes Computer to Freeze Product: krita Version: 5.0.2 Platform: PCLinuxOS OS: Microsoft Windows Status: REPORTED Severity: critical Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: jab2...@nau.edu Target Milestone: --- SUMMARY *** Whenever I try to hover over, or try to do an action like open it. Then at least the mouse and touch systems stop working. But it seems like the whole system freezes if it were my inclination. NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Use a Wacom pro drawing tablet. 2. Install kita 3. Use for a month. Have it suddenly not work. OBSERVED RESULT The entire system starts to freeze. EXPECTED RESULT You are able to hover, open, and uninstall without system freezing SOFTWARE/OS VERSIONS Windows: 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 450815] Krita Causes Computer to Freeze
https://bugs.kde.org/show_bug.cgi?id=450815 --- Comment #2 from Jade Brimhall --- This was all on the wacom mobile studio pro drawing tablet. It uses the Windows 10 OS. Because of the application freezing whenever I tired to do anything with it. I had to fill in the computer info instead of what I assume it does when you report a bug which is fill in all this oppertating and computer info automatically. The installation process was default. Since it takes a while for it to load I didn't want to change anything starting location since it takes about 20 minutes to load anyways. I did make it system administrator or have administrator privileges which may be the culprit since that gives it more access to do what it wants. I tracked down the files and deleted them. Then I had to wait a long while (around 20 min) in order for it to unfreeze and declare it uninstalled from my system. Side note since then. I have reinstalled krita default location(s). It has always done this but I didn't make the connection at the time. When restarting the mobile studio pro. If opening krita is one of the first things I do then it opens (albeit taking 20 min.). From there if closed. I am unable to open the application again. On Fri, Feb 25, 2022 at 1:58 AM Ahab Greybeard wrote: > https://bugs.kde.org/show_bug.cgi?id=450815 > > Ahab Greybeard changed: > >What|Removed |Added > > > CC| > |ahab.greybe...@hotmail.co.u >||k > Resolution|--- |WAITINGFORINFO > Status|REPORTED|NEEDSINFO > > --- Comment #1 from Ahab Greybeard --- > Please clarify which OS you are using. This report has a mixture of > 'PCLinuxOS' > and 'Microsoft Windows' and 'Windows: 10'. > Also, how was version 5.0.2 installed on your computer? > > The Steps To Reproduce are not easy to reproduce so this report will be > difficult to investigate. > > I suggest that you go to https://krita-artists.org/ (sign up and log in > are > needed) then create a New Topic there in the General Questions category. > There > you can explain your problem in more detail and with more information and > get > advice on things to try doing. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 448151] New: Drawing Cancels "Right Click" to show brush pallets.
https://bugs.kde.org/show_bug.cgi?id=448151 Bug ID: 448151 Summary: Drawing Cancels "Right Click" to show brush pallets. Product: krita Version: 5.0.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Brush engines Assignee: krita-bugs-n...@kde.org Reporter: jab2...@nau.edu Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** When you draw and then try to single right click, the brush palette does not show up. You can only draw again. You need to switch to another tool, then back to the brush tool, and then right click once to get the brush palette to re-appear. If you draw again after tool swapping, you will run into the same problem of not being able to bring up the brush palette when you right click. It would be nice that when you right click once without or barely moving that it consistently brings up the brush palette. Even when you had drawn before. STEPS TO REPRODUCE 1. Pick brush tool 2. Draw something 3. Right click 4. You should see the problem OBSERVED RESULT You will not be able to bring up brush palette after drawing something. EXPECTED RESULT You will be able to bring up the brush palette after drawing by simply right clicking in place. SOFTWARE/OS VERSIONS Windows: 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
