[frameworks-knotifications] [Bug 481069] Consider re-adding the feature to execute commands in notifications
https://bugs.kde.org/show_bug.cgi?id=481069 Zach Robichaud changed: What|Removed |Added CC||zach2...@gmail.com --- Comment #34 from Zach Robichaud --- I use this feature extensively and its removal impacts my workflow significantly. One of my primary use cases involves home automation. For example, when my computer locks, it automatically turns off my office fan and lights. Additionally, I utilize Konsole's silence notifications for long-running commands to trigger a script that sends me a Slack message when the task is completed. While I understand there are alternative hooks and methods to achieve these actions, leveraging the notification system has been the most straightforward and effective approach for me. It also enables my computer to alert me about low disk space and other easy-to-configure notifications. Removing this feature would disrupt these automations, and I'd like to advocate for its retention or for a similar functionality to be made available. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 476953] Meta/Super/Win/Cmd key does not respect keyboard layout in X11
https://bugs.kde.org/show_bug.cgi?id=476953 Zach White changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 476953] Meta/Super/Win/Cmd key does not respect keyboard layout in X11
https://bugs.kde.org/show_bug.cgi?id=476953 --- Comment #2 from Zach White --- I'm in Wayland right now and this does work properly, holding Meta and pressing W closes the window, no matter which keyboard layout I've selected. Unfortunately there's a lot that doesn't work properly in Wayland for me (such as latte-dock and the fact that UltrawideWindows no longer recognizes any of my panels and places windows behind them) so this isn't a viable option for me at this time. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 476953] New: Meta/Super/Win/Cmd key does not respect keyboard layout in X11
https://bugs.kde.org/show_bug.cgi?id=476953 Bug ID: 476953 Summary: Meta/Super/Win/Cmd key does not respect keyboard layout in X11 Classification: I don't know Product: kde Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: k...@drpepper.org Target Milestone: --- SUMMARY When using multiple keyboard layouts the "Meta" key (aka Super or Win or Command) will only use the default layout rather than using the currently chosen layout, breaking keyboard shortcuts. On my setup I have "Dvorak" as my primary keyboard layout and "Qwerty" as an option for people who use my computer. However, when they press Super the keys revert to dvorak, so they have to press the dvorak location to use a key. For example, I have meta+w assigned to close the current window, and while Qwerty is selected they have to press meta+comma to close a window, instead of meta+w. If I switch the order of the two keyboards the problem reverses, now when dvorak is selected I have to use qwerty keys while holding down meta. STEPS TO REPRODUCE 0. These steps assume you have "English (US)" with no Variant as your default keyboard layout 1. Open System Settings -> Workspace -> Shortcuts -> KWin -> Close Window 2. Set Custom Shortcuts to Meta+W, click Apply 3. Press Meta+W, observe that the window closes 4. Open System Settings -> Hardware -> Input Devices -> Keyboard -> Layouts 5. Click "Add" to add a new layout 6. Select "English (Dvorak)" 7. Click "Apply" 8. Switch to the Dvorak layout (I use the icon on the right side of the start bar) 9. Hold down Meta and press the key to the right of "M" (this is W on Dvorak) 10. Observe that the window does not close, even though you just pressed Meta+W 11. Verify that the keyboard layout is still set to Dvorak, but press Meta+Qwerty W 12. Observe that the window closes, even though you just typed Meta+Comma 13. Swap the order of the keyboard layouts and try steps 8-12 again, observe that now when holding down Meta all the keys correspond to Dvorak. OBSERVED RESULT While holding down Meta the pressed keys correspond to the First keyboard layout. EXPECTED RESULT While holding down Meta the pressed keys correspond to the Selected keyboard layout. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.27 (available in About System) KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.11 ADDITIONAL INFORMATION Only tested in X11, not tested in Wayland -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 475486] New: Multi-track audio-only export not behaving as expected, and output is broken
https://bugs.kde.org/show_bug.cgi?id=475486 Bug ID: 475486 Summary: Multi-track audio-only export not behaving as expected, and output is broken Classification: Applications Product: kdenlive Version: 23.08.1 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: zoonyga...@gmail.com Target Milestone: --- Created attachment 162233 --> https://bugs.kde.org/attachment.cgi?id=162233=edit A basic scaffold. You'll have to provide your own music files, but the basic project structure is there. SUMMARY *** Exporting separate audio tracks generates files that have no audio, and the tracks that are exported do not match what is expected from similar software. *** STEPS TO REPRODUCE 1. Create 2 timelines 2. Add audio files to both audio tracks in the first one (adding video is optional) 3. Create second sequence and populate audio tracks 4. Add second sequence to first 5. Open first sequence 6. Render audio only as multiple files (settings don't matter, everything I've tried produces same result). OBSERVED RESULT 5 files: - One master channel for the selected sequence - 3 completely silent files (from playing around, these appear to represent one track from the first sequence, and both audio tracks from the second sequence) - One track that contains either the first or second audio track from the visible sequence, seemingly at random. EXPECTED RESULT 3 files: - Master channel for selected sequence - Audio track 1 from selected sequence, including audio from nested sequence - Audio track 2 from selected sequence SOFTWARE/OS VERSIONS Windows 10, Ubuntu, Manjaro ADDITIONAL INFORMATION I have also tried this on multiple machines with different hardware and experience the same issue. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 457646] Ctrl key not respected in shortcuts that include it when using XKB option to swap Caps Lock and Ctrl key
https://bugs.kde.org/show_bug.cgi?id=457646 --- Comment #10 from Zach --- I booted up a live Gnome version of my distro (Garuda) and was able to replicate the bug. I would be able to create and run the shortcut using the original Ctrl key position. But when I swapped CapsLock and Ctrl, I wasn't able to create the shortcut but other shorter character length key combinations would work. So I guess not a KDE specific bug after all? On Wednesday, August 10, 2022 at 02:51:58 PM EDT, Andrey wrote: https://bugs.kde.org/show_bug.cgi?id=457646 --- Comment #9 from Andrey --- Can you also try on Gnome maybe? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 457646] Ctrl key not respected in shortcuts that include it when using XKB option to swap Caps Lock and Ctrl key
https://bugs.kde.org/show_bug.cgi?id=457646 --- Comment #7 from Zach --- Trying the different combinations for the Ctrl location, it fails on all where the Capslock acts as the Ctrl and works everywhere else. The bug only seems to occur when the CapsLock key is involved. I don't know if this'll be beneficial, but the hardware I'm using is a ThinkPad T14 Gen 1 with Ryen 5. I haven't changed any keyboard settings in the bios. On Wednesday, August 10, 2022 at 10:18:35 AM EDT, Nate Graham wrote: https://bugs.kde.org/show_bug.cgi?id=457646 --- Comment #6 from Nate Graham --- Thanks for the info. Do any of the other ctrl-swapping/re-mapping options also fail? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 457646] Ctrl key not respected in shortcuts that include it when using XKB option to swap Caps Lock and Ctrl key
https://bugs.kde.org/show_bug.cgi?id=457646 --- Comment #5 from Zach --- When I swapped the keys to the default configuration, the shortcut works. It didn't work if I had the Ctrl and Capslock keys swapped and tried the shortcut using the physical location of the Ctrl key (as it now acts as a Capslock). And didn't work if I had the keys swapped and used the physical Capslock key location (now acting as Ctrl). It still works if I use the Ctrl key on the right side of the keyboard. On Tuesday, August 9, 2022 at 03:24:41 PM EDT, Nate Graham wrote: https://bugs.kde.org/show_bug.cgi?id=457646 Nate Graham changed: What |Removed |Added Status|REPORTED |NEEDSINFO Product|kwin |frameworks-kglobalaccel CC| |n...@kde.org Assignee|kwin-bugs-n...@kde.org |kdelibs-b...@kde.org Resolution|--- |WAITINGFORINFO Version|5.25.4 |5.96.0 Summary|switch desktop shortcut not |Ctrl key not respected in |working for "Switch One |shortcuts that include it |Desktop to the Right" |when using XKB option to | |swap Caps Lock and Ctrl key Component|input |general --- Comment #4 from Nate Graham --- > On my system, I've swapped the Capslock and Ctrl keys using the Advanced > options in the keyboard input section of the KDE settings And does it work if you press the Capslock+Meta+right? What about actual Ctrl key+Meta+Right? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457646] switch desktop shortcut not working for "Switch One Desktop to the Right"
https://bugs.kde.org/show_bug.cgi?id=457646 --- Comment #2 from Zach --- Good morning, Attached is the requested file after attempting to change the shortcut. Playing around with it, I think this is a bug hiding in another place. When I tried using the other Ctrl key, the shortcut worked. On my system, I've swapped the Capslock and Ctrl keys using the Advanced options in the keyboard input section of the KDE settings. I've attached a screenshot of that section as well. Thank you for the help. Very Respectfully, Zach On Tuesday, August 9, 2022 at 06:31:56 AM EDT, Vlad Zahorodnii wrote: https://bugs.kde.org/show_bug.cgi?id=457646 --- Comment #1 from Vlad Zahorodnii --- Can't reproduce it, the shortcut works fine on my machine. Can you attach your ~/.config/kglobalaccelrc file after changing the shortcut to Meta+Ctrl+Right? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457646] New: switch desktop shortcut not working for "Switch One Desktop to the Right"
https://bugs.kde.org/show_bug.cgi?id=457646 Bug ID: 457646 Summary: switch desktop shortcut not working for "Switch One Desktop to the Right" Product: kwin Version: 5.25.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: input Assignee: kwin-bugs-n...@kde.org Reporter: prometheus7...@yahoo.com 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 *** Switch desktop shortcut not working for "Switch One Desktop to the Right" STEPS TO REPRODUCE 1. Have the default keyboard shortcut for "Switch One Desktop to the Right" set 2. Call the shortcut by typing "Meta+Ctrl+Right" OBSERVED RESULT The shortcut keys are pressed but no action occurs. It does not seem to perform any action. EXPECTED RESULT Shift the virtual desktop one to the right. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Garuda Linux / KDE Plasma 5.25.4 KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 ADDITIONAL INFORMATION Trying to set "Meta+Ctrl+Right" as a custom shortcut fails. My guess is there's a character limit that prevents it from seeing it as valid. Setting shorter character length shortcuts will allow the shortcut to function as expected. Any equal or longer length custom shortcut will fail to save and the action won't be performed. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414559] Running "sudo udevadm trigger -s input" resets touchpad configuration; can happen after system upgrade
https://bugs.kde.org/show_bug.cgi?id=414559 --- Comment #27 from Zach White --- (In reply to sausagefactory0 from comment #25) > I need to change it two times > (to "Adaptive" and then to "Flat") to make it flat again. You can avoid changing it two times by changing another setting instead. I toggle "Press left and right buttons for middle-click" one time and it resets all my settings, so I only have to "Apply" once. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414559] Running "sudo udevadm trigger -s input" resets touchpad configuration; can happen after system upgrade
https://bugs.kde.org/show_bug.cgi?id=414559 --- Comment #23 from Zach White --- I tried to dig into this problem a little bit and here is what I was able to observe. I still have not figured out how I can either fix or workaround the issue. The first surprising observation is that `sudo udevadm monitor` does not register any output at all at times I would expect it to. For example, there is no output when I run `udevadm trigger -s input` but there is output when I run `sudo udevadm trigger -s input`. This is what I see running that: https://gist.github.com/skullydazed/6a0703258dc9f0a231cebc0395174228 When I unplug and plugin my mouse here is what udevadm shows: https://gist.github.com/skullydazed/855393941da35627e15870b313224b7d Now, here's where things get interesting. I grabbed a second mouse and plugged it in (a Logitech TrackMan Marble.) When I did this my first mouse (Logitech MX Ergo) kept the correct settings but the new mouse had incorrect settings. More interestingly, when I went into System Settings -> Input Devices -> Mouse and changed a setting both mice adopted the correct settings. Steps to reproduce with any 2 mice: 1. Have first mouse plugged in, second mouse unplugged. 2. Go to System Settings -> Input Devices -> Mouse, check "Invert scroll direction", click "Apply". 3. Verify that moving the scroll wheel away from you scrolls a window down. 4. Plug in second mouse 5. Observe that first mouse scrolls down when the wheel is scrolled away from you while second mouse scrolls down when the wheel is scrolled towards you. 6. In the mouse settings window check (or uncheck) "Press left and right buttons together", then click Apply. 7. Observe that both mice scroll identically I believe this bug is classified incorrectly. Based on my observations it seems that the problem is that USB plug events are configuring devices with the default settings rather than the user's settings. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420054] Keyboard kded module causes hang after switching back from virtual console
https://bugs.kde.org/show_bug.cgi?id=420054 Zach changed: What|Removed |Added CC||zach.les...@grafana.com --- Comment #33 from Zach --- I believe I'm experiencing something similar with a USB keyboard. This appears to happen after a suspend/resume because all the USB devices are re-detected, but also happens whenever I plugin in a keyboard. The laptop keyboard also stops working when a USB keyboard is plugged in. Switching to virtual console and back works with both keyboards while plasma is hung. Keyboard events seem to buffer, because after some period of time (1m?), the keyboard starts working again and all of the keypresses that were pressed while frozen all replay at once, followed by a brief pause and an error `kded5[1067]: org.kde.kcm_keyboard: Failed with return code: 1`. As mentioned in this post, disabling the keyboard background service and re-plugging the USB keyboard works as expected. Intel graphics, i915 chipset. If this is unrelated, let me know and I can file a new issue. This has been quite a chore to track down, but worth creating a bugs account for. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414559] Running "sudo udevadm trigger -s input" resets touchpad configuration; can happen after system upgrade
https://bugs.kde.org/show_bug.cgi?id=414559 Zach White changed: What|Removed |Added CC||k...@drpepper.org --- Comment #19 from Zach White --- I upgraded my KDE Neon (5.24) system over the weekend and this started to occur for me. I do not have a touchpad at all, I'm using a Logitech MX Ergo with the wireless receiver, and the bug is triggered every time my trackball wakes up from sleep (being wireless the device itself goes into a sleep mode, this is not DPMS or the host sleeping.) The problem does not occur if I briefly (~30s) turn the trackball off and back on again. I can trigger the problem with `sudo udevadm trigger -s input`. Is there a workaround I can use here to make my preferred settings the default settings? I tried `sudo cp ~/.config/kcminputrc /root/.config` but that did not work. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 436235] Elisa crashes when scrolling down in Files mode
https://bugs.kde.org/show_bug.cgi?id=436235 Zach Rice changed: What|Removed |Added CC||zach.r...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 436235] Elisa crashes when scrolling down in Files mode
https://bugs.kde.org/show_bug.cgi?id=436235 --- Comment #4 from Zach Rice --- Created attachment 145476 --> https://bugs.kde.org/attachment.cgi?id=145476=edit New crash information added by DrKonqi elisa (21.08.1) using Qt 5.15.2 - What I was doing when the application crashed: I had just cleared the playlist and began scrolling through my local files. -- Backtrace (Reduced): #6 0x7f82b01798bd in QHash::isEmpty (this=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qhash.h:285 #7 QHash::empty (this=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qhash.h:544 #8 QQmlIncubatorPrivate::incubate (this=0x558be71a3550, i=...) at qml/qqmlincubator.cpp:333 #9 0x7f82b0179f22 in QQmlIncubationController::incubateFor (this=this@entry=0x558be5cd5ac0, msecs=) at qml/qqmlincubator.cpp:409 #10 0x7f82ae850ae4 in QQuickWindowIncubationController::incubate (this=0x558be5cd5ab0) at items/qquickwindow.cpp:171 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 445847] New: Crash opening "Appearance" in System Settings
https://bugs.kde.org/show_bug.cgi?id=445847
Bug ID: 445847
Summary: Crash opening "Appearance" in System Settings
Product: kde
Version: unspecified
Platform: unspecified
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: unassigned-b...@kde.org
Reporter: z...@xmyth.me
Target Milestone: ---
Application: systemsettings5 (5.23.3)
Qt Version: 5.15.2
Frameworks Version: 5.88.0
Operating System: Linux 5.15.2-1-default x86_64
Windowing System: X11
Distribution: "openSUSE Tumbleweed"
DrKonqi: 5.23.3 [KCrashBackend]
-- Information about the crash:
- What I was doing when the application crashed:
I clicked on "Appearance" in System Settings and it crashed. Repeatedly.
The crash can be reproduced every time.
-- Backtrace:
Application: System Settings (systemsettings5), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = {}}
[KCrash Handler]
#6 0x7f5e3d4ade20 in QOpenGLContext::isValid
(this=this@entry=0x55e26e291220) at kernel/qopenglcontext.cpp:723
#7 0x7f5e3d4aed02 in QOpenGLContext::doneCurrent (this=0x55e26e291220) at
kernel/qopenglcontext.cpp:1057
#8 0x7f5e3d4b24d6 in QGuiGLThreadContext::~QGuiGLThreadContext
(this=0x7f5e30006580, __in_chrg=) at
kernel/qopenglcontext.cpp:231
#9 qThreadStorage_deleteData (d=0x7f5e30006580) at
../../include/QtCore/../../src/corelib/thread/qthreadstorage.h:92
#10 QThreadStorage::deleteData (x=0x7f5e30006580) at
../../include/QtCore/../../src/corelib/thread/qthreadstorage.h:135
#11 0x7f5e3cd2e41f in QThreadStorageData::finish (p=p@entry=0x55e26dde84d0)
at thread/qthreadstorage.cpp:200
#12 0x7f5e3cf1062f in QCoreApplicationPrivate::cleanupThreadData
(this=this@entry=0x55e26de13e90) at kernel/qcoreapplication.cpp:501
#13 0x7f5e3d45eb54 in QGuiApplicationPrivate::~QGuiApplicationPrivate
(this=0x55e26de13e90, __in_chrg=) at
kernel/qguiapplication.cpp:1707
#14 0x7f5e3dbbd529 in QApplicationPrivate::~QApplicationPrivate
(this=0x55e26de13e90, __in_chrg=) at kernel/qapplication.cpp:163
#15 0x55e26cebc144 in main (argc=, argv=) at
/usr/src/debug/systemsettings5-5.23.3-1.1.x86_64/app/main.cpp:209
[Inferior 1 (process 2533) detached]
Possible duplicates by query: bug 415016.
Reported using DrKonqi
This report was filed against 'kde' because the product 'systemsettings' could
not be located in Bugzilla. Add it to drkonqi's mappings file!
--
You are receiving this mail because:
You are watching all bug changes.
[bugs.kde.org] [Bug 437173] smb://zach@tower.local/Scarlet/Media/Zerochan/somefile.etc smb://zach@tower.local/Scarlet/Media/Zerochan/somefile.etc
https://bugs.kde.org/show_bug.cgi?id=437173 zach changed: What|Removed |Added Summary|smb://zach@tower.local/Scar |smb://zach@tower.local/Scar |let/Media/Zerochan/milk/aiE |let/Media/Zerochan/somefile |nhance/Nana_May-173_1.mp4 |.etc |smb://zach@tower.local/Scar |smb://zach@tower.local/Scar |let/Media/Zerochan/milk/aiE |let/Media/Zerochan/somefile |nhance/Nana_May-173.mp4 |.etc -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 437173] New: smb://zach@tower.local/Scarlet/Media/Zerochan/milk/aiEnhance/Nana_May-173_1.mp4 smb://zach@tower.local/Scarlet/Media/Zerochan/milk/aiEnhance/Nana_May-173.mp4
https://bugs.kde.org/show_bug.cgi?id=437173 Bug ID: 437173 Summary: smb://zach@tower.local/Scarlet/Media/Zerochan/milk/aiE nhance/Nana_May-173_1.mp4 smb://zach@tower.local/Scarlet/Media/Zerochan/milk/aiE nhance/Nana_May-173.mp4 Product: bugs.kde.org Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: sysad...@kde.org Reporter: zachfbstud...@gmail.com CC: she...@kde.org Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Copying files to network SMB Share 2. Modifying SMB files 3. (Using dolphin file browser) 4. Deleting SMB: folder in home directory and still getting crashes OBSERVED RESULT Internal Error crash, files on Linux but not on network folder (IE browsing share from windows is empty after a successful transfer on Linux side.) EXPECTED RESULT File copies SOFTWARE/OS VERSIONS OS: Garuda Linux x86_64 ╗╠╠╠╝╝╢╠┐ Host: B550 AORUS PRO ╣╢╣╢╗╕ , `"╘╠╠╔╥_ Kernel: 5.12.3-zen1-1-zen ╒╠╠╠╕╙╥╥╜ `"╜╠╬╠╠╠╥, Uptime: 1 hour, 6 mins ╠╠╗╗╗╬╠╠╠╝╙╠╠╣╢┐ Packages: 1886 (pacman) ╣╠╥╬╣╗Shell: zsh 5.8 ╒╠╠╗ Resolution: 3840x2160 DE: Plasma 5.21.5 ╬ ```"╜╝╢╠╠╡ WM: KWin ╒╠╣, ╘╠╪WM Theme: Breeze ╞╠╠╠╢┐╜ Theme: Breeze Dark [Plasma], Breeze [GTK2/3] `╠╗ Icons: breeze-dark [Plasma], breeze-dark [GTK2/3] ,╬"╕Terminal: konsole ╠╗ Terminal Font: FantasqueSansMono Nerd Font Mono 12 ╝^╠╝╣╡ CPU: AMD Ryzen 7 3700X (16) @ 3.600GHz ╔╜`╞┘╢╛╜ ╡╢╠"╚╠╠╜╝┌╞╞"╢╠╠╣╩╢╪ GPU: NVIDIA GeForce RTX 2060 SUPER ╜╒" `╜` ╜╙╕ └╣╕ ╞╙╖ Memory: 4509MiB / 64315MiB ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 416943] New: Touchpad Settings Only Shows Built-in Touchpad
https://bugs.kde.org/show_bug.cgi?id=416943 Bug ID: 416943 Summary: Touchpad Settings Only Shows Built-in Touchpad Product: systemsettings Version: 5.17.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: kcm_touchpad Assignee: plasma-b...@kde.org Reporter: zach.richar...@gmail.com Target Milestone: --- Created attachment 125543 --> https://bugs.kde.org/attachment.cgi?id=125543=edit The issue and libinput devices list SUMMARY I'm using a laptop with a built-in touchpad (like most) and I also have an Apple Magic Trackpad 2. Wether the Apple Trackpad is plugged in over USB, or paired via Bluetooth, I cannot select it in Touchpad settings. The "Device" selection is disabled and the laptop's built-in touchpad is selected. The Apple Trackpad works and can be configured via libinput itself, but not the KDE settings. STEPS TO REPRODUCE 1. Plug an external touchpad into a laptop with a built-in touchpad 2. open the KDE Touchpad settings component 3. try to change the device OBSERVED RESULT Cannot change device, therefore cannot change settings via KDE. EXPECTED RESULT Can change device, can change settings, settings applied via libinput. SOFTWARE/OS VERSIONS Windows: - macOS: - Linux/KDE Plasma: Arch Linux (5.4.15-arch1-1) (available in About System) KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.66.0 Qt Version: 5.14.1 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373232] Horizontal lines with fractional HiDPI scaling
https://bugs.kde.org/show_bug.cgi?id=373232 Zach Hobbs changed: What|Removed |Added CC||zachho...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 389559] Info Center crashes on clicking Energy Information
https://bugs.kde.org/show_bug.cgi?id=389559 --- Comment #2 from Zach vd M. --- Created attachment 115492 --> https://bugs.kde.org/attachment.cgi?id=115492=edit New crash information added by DrKonqi kinfocenter (5.12.6) using Qt 5.9.5 - What I was doing when the application crashed: I tried to open the ' Energy Information' Item from the KInfoCentre Active tab 'About system' trying to swith over to 'Energy Information' then it crashes -- Backtrace (Reduced): #6 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 #7 0x7f6dc1f25801 in __GI_abort () at abort.c:79 #8 0x7f6dc26f5fa7 in QMessageLogger::fatal(char const*, ...) const () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 [...] #11 0x7f6dc1558f8e in QQuickWidget::resizeEvent(QResizeEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5QuickWidgets.so.5 #12 0x7f6dc36a6be2 in QWidget::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 389559] Info Center crashes on clicking Energy Information
https://bugs.kde.org/show_bug.cgi?id=389559 Zach vd M. changed: What|Removed |Added CC||zm20...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 396649] New: Dolphin crashes while using synergy to use mouse on remote computer
https://bugs.kde.org/show_bug.cgi?id=396649 Bug ID: 396649 Summary: Dolphin crashes while using synergy to use mouse on remote computer Product: dolphin Version: 17.04.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: zgknocc...@gmail.com CC: elvis.angelac...@kde.org Target Milestone: --- Application: dolphin (17.04.2) Qt Version: 5.6.2 Frameworks Version: 5.32.0 Operating System: Linux 4.4.104-18.44-default x86_64 Distribution: "openSUSE Leap 42.3" -- Information about the crash: - What I was doing when the application crashed: I had my mouse sitting on my windows laptop. This has been happening everytime i use synergy. I have to restart computer with the hardware switch, as i cannot enter keyboard commands outside of the windows key on my keyboard. Application: Dolphin (dolphin), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f620e41a900 (LWP 2556))] Thread 9 (Thread 0x7f61dc1f6700 (LWP 2699)): #0 0x7f620dcc020d in poll () at /lib64/libc.so.6 #1 0x7f6202783314 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f620278342c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f6207f611ab in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f6207f0ebfb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f6207d49f5a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f6207d4ea29 in () at /usr/lib64/libQt5Core.so.5 #7 0x7f6203317744 in start_thread () at /lib64/libpthread.so.0 #8 0x7f620dcc8aad in clone () at /lib64/libc.so.6 Thread 8 (Thread 0x7f61e173b700 (LWP 2655)): #0 0x7f620331c0bf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f61eec35b4b in () at /usr/lib64/dri/radeonsi_dri.so #2 0x7f61eec358c7 in () at /usr/lib64/dri/radeonsi_dri.so #3 0x7f6203317744 in start_thread () at /lib64/libpthread.so.0 #4 0x7f620dcc8aad in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7f61e1f3c700 (LWP 2654)): #0 0x7f620331c0bf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f61eec35b4b in () at /usr/lib64/dri/radeonsi_dri.so #2 0x7f61eec358c7 in () at /usr/lib64/dri/radeonsi_dri.so #3 0x7f6203317744 in start_thread () at /lib64/libpthread.so.0 #4 0x7f620dcc8aad in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7f61e273d700 (LWP 2653)): #0 0x7f620331c0bf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f61eec35b4b in () at /usr/lib64/dri/radeonsi_dri.so #2 0x7f61eec358c7 in () at /usr/lib64/dri/radeonsi_dri.so #3 0x7f6203317744 in start_thread () at /lib64/libpthread.so.0 #4 0x7f620dcc8aad in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f61e2f3e700 (LWP 2652)): #0 0x7f620331c0bf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f61eec35b4b in () at /usr/lib64/dri/radeonsi_dri.so #2 0x7f61eec358c7 in () at /usr/lib64/dri/radeonsi_dri.so #3 0x7f6203317744 in start_thread () at /lib64/libpthread.so.0 #4 0x7f620dcc8aad in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f61e3946700 (LWP 2651)): #0 0x7f620331c0bf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f61eec35b4b in () at /usr/lib64/dri/radeonsi_dri.so #2 0x7f61eec358c7 in () at /usr/lib64/dri/radeonsi_dri.so #3 0x7f6203317744 in start_thread () at /lib64/libpthread.so.0 #4 0x7f620dcc8aad in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f61f4a36700 (LWP 2574)): #0 0x7f62027c4899 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f6202782969 in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #2 0x7f6202783230 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f620278342c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f6207f611ab in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f6207f0ebfb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f6207d49f5a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7f6208376295 in () at /usr/lib64/libQt5DBus.so.5 #8 0x7f6207d4ea29 in () at /usr/lib64/libQt5Core.so.5 #9 0x7f6203317744 in start_thread () at /lib64/libpthread.so.0 #10 0x7f620dcc8aad in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f61f6626700 (LWP 2566)): #0 0x7f620dcc020d in poll () at /lib64/libc.so.6 #1 0x7f62002da3e2 in () at /usr/lib64/libxcb.so.1 #2 0x7f62002dbfcf in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7f61f8bb10d9 in () at /usr/lib64/libQt5XcbQpa.so.5 #4
[krita] [Bug 386008] Shortcuts not working with Wacom Feel drivers
https://bugs.kde.org/show_bug.cgi?id=386008 Zach <zhi...@gmail.com> changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #3 from Zach <zhi...@gmail.com> --- Hi, thank you so much! Just carrying out the first step did the trick. Does this mean wintab is obsolete? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 386008] Shortcuts not working with Wacom Feel drivers
https://bugs.kde.org/show_bug.cgi?id=386008 Zach <zhi...@gmail.com> changed: What|Removed |Added Summary|Shortcuts not working with |Shortcuts not working with |Wacom drivers |Wacom Feel drivers -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 386008] New: Shortcuts not working with Wacom drivers
https://bugs.kde.org/show_bug.cgi?id=386008 Bug ID: 386008 Summary: Shortcuts not working with Wacom drivers Product: krita Version: 3.3.1 Platform: Windows CE OS: MS Windows Status: UNCONFIRMED Severity: major Priority: NOR Component: shortcuts Assignee: krita-bugs-n...@kde.org Reporter: zhi...@gmail.com Target Milestone: --- It came up after I updated my computer (Lenovo Yoga 520) to Windows 10, version 1709. Whenever I use the pen, while simultaneously pressing the keys (ctrl+z, spacebar, etc), it would not respond or simply stays in that function until I use a mouse to switch out of/use it. I've tried downgrading Krita from ver 3.3.1 to 3.2 and even installing older Wacom Feel drivers from version ISD_7.3.4-47 to 7.3.4-36, but it still shows the same problem. When I completely remove all instances of Wacom Feel driver; with my pen functioning as a bare minimum of a mouse pointer, the keys seems to behave normally. I suspect it could be the Windows 10 update causing all these problems. I do hope you could look into it, before I consider the option of rolling back my windows update. Thank you in advance. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 385621] New: Settings blurry with HiDPI scaling
https://bugs.kde.org/show_bug.cgi?id=385621 Bug ID: 385621 Summary: Settings blurry with HiDPI scaling Product: systemsettings Version: 5.11.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: zachho...@gmail.com Target Milestone: --- When I add HiDPI scaling I see issues in a few apps, for example #373232 on Konsole. But the biggest issues are with the Settings app and Discover app. In the settings app, the left navigation panels are very blurry, and the content panels are blurry for some sections and not others. These sections are blurry: - Workspace Theme (all but "Curser Theme" sub section) - Desktop Behavior -> Desktop Effects Examples of sections that are not blurry: - Colors - Fonts - Icons - Desktop Behavior -> (all EXCEPT Desktop Effects) I'm on KDE Neon, Plasma 5.11. Nvidia drivers, 3840x2160 display, 1.3 scaling factor. When I take a screenshot with Spectacle all the windows are blurry, so decided not to include a screenshot example. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 384980] Intermittent "not responding" freezes
https://bugs.kde.org/show_bug.cgi?id=384980 --- Comment #2 from Zach <zhi...@gmail.com> --- Hi, Thank you for your response! I managed to find out about it too. Regards, Zach -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 384980] Intermittent "not responding" freezes
https://bugs.kde.org/show_bug.cgi?id=384980 Zach <zhi...@gmail.com> changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 384980] Intermittent "not responding" freezes
https://bugs.kde.org/show_bug.cgi?id=384980 Zach <zhi...@gmail.com> changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|FIXED |--- -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 384980] Intermittent "not responding" freezes
https://bugs.kde.org/show_bug.cgi?id=384980 Zach <zhi...@gmail.com> changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 384980] New: Intermittent "not responding" freezes
https://bugs.kde.org/show_bug.cgi?id=384980 Bug ID: 384980 Summary: Intermittent "not responding" freezes Product: krita Version: 3.3.0-rc.1 Platform: Windows CE OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: zhi...@gmail.com Target Milestone: --- Created attachment 107960 --> https://bugs.kde.org/attachment.cgi?id=107960=edit Freezes intermittently As with the title, it occurs within 10 mins throughout my animation process; while drawing or doing anything else like clicking a button. I'm not entirely sure if it's because Krita cannot handle too many frames (I have 200+ frames with 8 layers in it with sound, 1920 x 1080 px , 300ppi)? After a few seconds, it will return to normal. I hope to work it out because the animation features are really promising. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 359735] Intermittent, Unresponsive when running Krita
https://bugs.kde.org/show_bug.cgi?id=359735 Zach <zhi...@gmail.com> changed: What|Removed |Added CC||zhi...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 378577] New: Power Management doesn't reset battery power status after suspend
https://bugs.kde.org/show_bug.cgi?id=378577 Bug ID: 378577 Summary: Power Management doesn't reset battery power status after suspend Product: Powerdevil Version: 5.9.4 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-de...@kde.org Reporter: kuroro.zh...@gmail.com Target Milestone: --- When battery fell to below Low level, suspend system, connect AC Power, charge battery to above Low level, disconnect AC Power, found that Power Management still recognize battery power level is under Low level. coz when open Power Management settings, "Energy Saving" is in "On Low Battery" tab, and screen will dimmed as setting in "On Low Battery". -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 370011] url in Chrome doesn't make it to shared clipboard
https://bugs.kde.org/show_bug.cgi?id=370011 --- Comment #2 from Zach <zachle...@fastmail.jp> --- Yes, Chrome on Android. Its the only app that doesnt seem to work. Maybe it has to do with my slightly older Android version? -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 370011] New: url in Chrome doesn't make it to shared clipboard
https://bugs.kde.org/show_bug.cgi?id=370011 Bug ID: 370011 Summary: url in Chrome doesn't make it to shared clipboard Product: kdeconnect Version: unspecified Platform: Other OS: Android 4.x Status: UNCONFIRMED Severity: normal Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: zachle...@fastmail.jp When copying a url in the Chrome address bar, the copied address does not transfer to the KDE machine. All other text seems to copy fine. Reproducible: Always Steps to Reproduce: 1. Copy a url from the address bar in Chrome 2. Try to paste the url on your KDE machine 3. Actual Results: Previous item, not url, is pasted. Expected Results: The url should be pasted. -- You are receiving this mail because: You are watching all bug changes.
