[kde] [Bug 479891] Some text glyphs in QML software are mis-aligned or squished when using a fractional scale factor

2024-03-26 Thread akb825
https://bugs.kde.org/show_bug.cgi?id=479891 akb825 changed: What|Removed |Added CC||akb...@gmail.com -- You are receiving this mail

[systemsettings] [Bug 415179] Touchpad disabled when detected as both mouse and touchpad

2024-03-24 Thread akb825
https://bugs.kde.org/show_bug.cgi?id=415179 --- Comment #13 from akb825 --- After updating to Plasma 6 and switching to a Wayland session and libinput, everything seems to be working as expected. IIRC I earlier opted to use Synaptics because the libinput driver didn't support drag-lock

[okular] [Bug 475198] Links in markdown show raw markdown rather than a clickable link.

2023-10-04 Thread akb825
https://bugs.kde.org/show_bug.cgi?id=475198 --- Comment #4 from akb825 --- After further investigation, Arch does appear to have a proper dependency on the discount package, and the installed okularGenerator_md.so library is properly linking to libmarkdown.so. However, it looks like on August 27

[okular] [Bug 475198] Links in markdown show raw markdown rather than a clickable link.

2023-10-04 Thread akb825
https://bugs.kde.org/show_bug.cgi?id=475198 --- Comment #3 from akb825 --- > Can you test it with "discount-mkd2html test.md" in your system? After installing the discount package and running mkd2html, it displays the link correctly. Double checking the code for Okular, it ap

[okular] [Bug 475198] Links in markdown show raw markdown rather than a clickable link.

2023-10-04 Thread akb825
https://bugs.kde.org/show_bug.cgi?id=475198 --- Comment #2 from akb825 --- Created attachment 162092 --> https://bugs.kde.org/attachment.cgi?id=162092=edit Screenshot of the test file The attached file does not appear correctly. I have attached a screenshot of how it looks for me in Oku

[okular] [Bug 473940] Markdown code block is rendered interpreted as Markdown

2023-10-03 Thread akb825
https://bugs.kde.org/show_bug.cgi?id=473940 akb825 changed: What|Removed |Added CC||akb...@gmail.com --- Comment #2 from akb825

[okular] [Bug 475198] New: Links in markdown show raw markdown rather than a clickable link.

2023-10-03 Thread akb825
https://bugs.kde.org/show_bug.cgi?id=475198 Bug ID: 475198 Summary: Links in markdown show raw markdown rather than a clickable link. Classification: Applications Product: okular Version: 23.08.1 Platform: Archlinux

[Spectacle] [Bug 473879] Preview when using the rectangular region tool is offset to the right.

2023-09-28 Thread akb825
https://bugs.kde.org/show_bug.cgi?id=473879 akb825 changed: What|Removed |Added CC||akb...@gmail.com -- You are receiving this mail

[dolphin] [Bug 465489] Can no longer unassign "space" from activating selection mode

2023-02-08 Thread akb825
https://bugs.kde.org/show_bug.cgi?id=465489 --- Comment #2 from akb825 --- > Space would select the first file, not toggle the selection. One couldn't > de-select a file with > Space, but only with Ctrl+Space. My mistake, other threads mentioned toggling, though I prim

[dolphin] [Bug 465489] New: Can no longer unassign "space" from activating selection mode

2023-02-08 Thread akb825
https://bugs.kde.org/show_bug.cgi?id=465489 Bug ID: 465489 Summary: Can no longer unassign "space" from activating selection mode Classification: Applications Product: dolphin Version: 22.12.2 Platform: Other

[dolphin] [Bug 463095] Copying a file from one Dolphin window to another doesn't update clipboard.

2022-12-15 Thread akb825
https://bugs.kde.org/show_bug.cgi?id=463095 --- Comment #1 from akb825 --- In case it makes a difference, I am running through an X11 session. -- You are receiving this mail because: You are watching all bug changes.

[dolphin] [Bug 463095] New: Copying a file from one Dolphin window to another doesn't update clipboard.

2022-12-15 Thread akb825
https://bugs.kde.org/show_bug.cgi?id=463095 Bug ID: 463095 Summary: Copying a file from one Dolphin window to another doesn't update clipboard. Classification: Applications Product: dolphin Version: 22.12.0 Platform:

[plasma-nm] [Bug 435561] Cannot specify usergroup for OpenConnect VPNs

2021-04-14 Thread akb825
https://bugs.kde.org/show_bug.cgi?id=435561 --- Comment #7 from akb825 --- I have submitted an MR here: https://invent.kde.org/plasma/plasma-nm/-/merge_requests/57 -- You are receiving this mail because: You are watching all bug changes.

[plasma-nm] [Bug 435561] Cannot specify usergroup for OpenConnect VPNs

2021-04-13 Thread akb825
https://bugs.kde.org/show_bug.cgi?id=435561 --- Comment #4 from akb825 --- Further investigation confirms that the patch I posted should fix the issue on the plasma-nm side of not forwarding the usergroup, while separate issues in NetworkManager-openconnect (related to the split routing

[plasma-nm] [Bug 435561] Cannot specify usergroup for OpenConnect VPNs

2021-04-13 Thread akb825
https://bugs.kde.org/show_bug.cgi?id=435561 --- Comment #3 from akb825 --- Created attachment 137574 --> https://bugs.kde.org/attachment.cgi?id=137574=edit usergroup.patch I went through the code and I believe the main problem is that only the host + port is passed to the NetworkMana

[plasma-nm] [Bug 435561] Cannot specify usergroup for OpenConnect VPNs

2021-04-09 Thread akb825
https://bugs.kde.org/show_bug.cgi?id=435561 akb825 changed: What|Removed |Added CC||akb...@gmail.com -- You are receiving this mail

[plasma-nm] [Bug 435561] Cannot specify usergroup for OpenConnect VPNs

2021-04-09 Thread akb825
https://bugs.kde.org/show_bug.cgi?id=435561 --- Comment #2 from akb825 --- After some more experimentation, the behavior of whether the dialog disappears and openconnect writes the cookie error to the journal, or whether it has the "unknown code" error in the dialog, appears to be in

[plasma-nm] [Bug 435561] Cannot specify usergroup for OpenConnect VPNs

2021-04-09 Thread akb825
https://bugs.kde.org/show_bug.cgi?id=435561 --- Comment #1 from akb825 --- After looking through the code, it looks like it *is* trying to parse the group from the gateway. However, attempting to do this fails to connect. No error is reported in the UI, it simply closes the dialog and isn't

[systemsettings] [Bug 421743] Realm option missing when connecting to Jumper/Pulse VPN via OpenConnect and NetworkManager.

2021-04-09 Thread akb825
https://bugs.kde.org/show_bug.cgi?id=421743 akb825 changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED

[plasma-nm] [Bug 435561] New: Cannot specify usergroup for OpenConnect VPNs

2021-04-09 Thread akb825
https://bugs.kde.org/show_bug.cgi?id=435561 Bug ID: 435561 Summary: Cannot specify usergroup for OpenConnect VPNs Product: plasma-nm Version: 5.21.4 Platform: Other OS: Linux Status: REPORTED Severity:

[systemsettings] [Bug 415179] Touchpad disabled when detected as both mouse and touchpad

2020-12-19 Thread akb825
https://bugs.kde.org/show_bug.cgi?id=415179 --- Comment #9 from akb825 --- Nevermind, it isn't consistent even with that change: XOrg will still sometimes keep the device enabled, even when verifying that the device name listed in xinput matches one of the ones I've disabled through an XOrg

[systemsettings] [Bug 415179] Touchpad disabled when detected as both mouse and touchpad

2020-12-19 Thread akb825
https://bugs.kde.org/show_bug.cgi?id=415179 --- Comment #8 from akb825 --- This seems to be a constantly moving target. I additionally need to disable PS/2 Generic Mouse to have the touchpad reliably work: Section "InputClass" Identifier "Ignore synaptics mouse"

[systemsettings] [Bug 415179] Touchpad disabled when detected as both mouse and touchpad

2020-11-25 Thread akb825
https://bugs.kde.org/show_bug.cgi?id=415179 --- Comment #7 from akb825 --- After some investigation, it looks like the current issue is caused because there's a second touchpad device (PS/2 Synaptics TouchPad) that shows up in the xinput device list. The ordering of the list is inconsistent

[systemsettings] [Bug 415179] Touchpad disabled when detected as both mouse and touchpad

2020-11-24 Thread akb825
https://bugs.kde.org/show_bug.cgi?id=415179 --- Comment #6 from akb825 --- >From what I can tell the workaround listed by Mads is no longer doing anything. Having the workaround or not has the same behavior: sometimes when I boot (maybe 25-50% of the time) it will disable the trackpad, ot

[systemsettings] [Bug 415179] Touchpad disabled when detected as both mouse and touchpad

2020-07-24 Thread akb825
https://bugs.kde.org/show_bug.cgi?id=415179 --- Comment #5 from akb825 --- To provide an update for this issue, the X11 workaround Mads posted is inconsistent. Sometimes it still disables the touchpad on boot and requires one or two reboots before it works. I've kept up to date based on Arch's

[plasmashell] [Bug 423600] Desktop inherits DPI setting from login manager after first login

2020-07-10 Thread akb825
https://bugs.kde.org/show_bug.cgi?id=423600 --- Comment #18 from akb825 --- I've attached three screenshots: 1. The correct results shown with the first login after booting and after synchronizing the SDDM settings with KDE. 2. The desktop elements too small after logging in a second time

[plasmashell] [Bug 423600] Desktop inherits DPI setting from login manager after first login

2020-07-10 Thread akb825
https://bugs.kde.org/show_bug.cgi?id=423600 --- Comment #17 from akb825 --- Created attachment 130024 --> https://bugs.kde.org/attachment.cgi?id=130024=edit The desktop elements being too large after setting a very high DPI for SDDM. -- You are receiving this mail because: You are watch

[plasmashell] [Bug 423600] Desktop inherits DPI setting from login manager after first login

2020-07-10 Thread akb825
https://bugs.kde.org/show_bug.cgi?id=423600 --- Comment #16 from akb825 --- Created attachment 130023 --> https://bugs.kde.org/attachment.cgi?id=130023=edit The desktop elements being too small on the second login with the default (non-synchronized) settings. -- You are receiving this m

[plasmashell] [Bug 423600] Desktop inherits DPI setting from login manager after first login

2020-07-10 Thread akb825
https://bugs.kde.org/show_bug.cgi?id=423600 --- Comment #15 from akb825 --- Created attachment 130022 --> https://bugs.kde.org/attachment.cgi?id=130022=edit The correct result on the first login and when the KDE and SDDM settings are synchronized. -- You are receiving this mail because:

[plasmashell] [Bug 423600] Desktop inherits DPI setting from login manager after first login

2020-07-09 Thread akb825
https://bugs.kde.org/show_bug.cgi?id=423600 --- Comment #13 from akb825 --- Yes, syncing the SDDM settings works around the problem. It basically hides the bug, but it took quite a bit of digging around to track down. Let's say I'm a normal user of KDE and just set up my machine. I have a high

[plasmashell] [Bug 423600] Desktop inherits DPI setting from login manager after first login

2020-07-09 Thread akb825
https://bugs.kde.org/show_bug.cgi?id=423600 --- Comment #11 from akb825 --- The problem is Plasma desktop has the following behavior: * The first time logging on after booting, it correctly takes KDE's DPI. * The second time logging on (and each time following) it takes SDDM's DPI. All other

[plasmashell] [Bug 423600] Desktop inherits DPI setting from login manager after first login

2020-07-08 Thread akb825
https://bugs.kde.org/show_bug.cgi?id=423600 --- Comment #9 from akb825 --- On my laptop I only adjusted the scaling by setting the global scale to 200% in the Display Configuration control panel. (which I'm assuming is the KScreen KCM you're referring to) However, this setting doesn't apply

[plasmashell] [Bug 423600] Desktop inherits DPI setting from login manager after first login

2020-07-03 Thread akb825
https://bugs.kde.org/show_bug.cgi?id=423600 --- Comment #7 from akb825 --- To provide a bit more info, the example numbers I used were for my laptop. I also have a desktop with 4k monitors, but the specific DPI settings are a bit different: I have the KDE set to use 120 DPI, but the default

[plasmashell] [Bug 423600] Desktop inherits DPI setting from login manager after first login

2020-07-03 Thread akb825
https://bugs.kde.org/show_bug.cgi?id=423600 --- Comment #6 from akb825 --- > I'm not convinced that SDDM is involved at all, but your symptoms match a > description of not using Qt scaling. I believe that the SDDM settings are merely the trigger for the bug in Plasma. The DPI se

[plasmashell] [Bug 423600] Desktop inherits DPI setting from login manager after first login

2020-07-01 Thread akb825
https://bugs.kde.org/show_bug.cgi?id=423600 --- Comment #4 from akb825 --- In this case, the "-dpi 192" option was set after synchronizing with the KDE settings. However, if I remove this setting, based on the size of the UI elements I believe it was using a default of

[plasmashell] [Bug 423600] Desktop inherits DPI setting from login manager after first login

2020-07-01 Thread akb825
https://bugs.kde.org/show_bug.cgi?id=423600 --- Comment #2 from akb825 --- If the DPI scaling isn't 100%, it will be different for the login manager by default unless you manually synchronize the settings under the Advanced section of the "Login Screen (SDDM)" control panel. I

[plasmashell] [Bug 423600] New: Desktop inherits DPI setting from login manager after first login

2020-06-27 Thread akb825
https://bugs.kde.org/show_bug.cgi?id=423600 Bug ID: 423600 Summary: Desktop inherits DPI setting from login manager after first login Product: plasmashell Version: 5.19.2 Platform: Other OS: Linux

[systemsettings] [Bug 421743] New: Realm option missing when connecting to Jumper/Pulse VPN via OpenConnect and NetworkManager.

2020-05-18 Thread akb825
https://bugs.kde.org/show_bug.cgi?id=421743 Bug ID: 421743 Summary: Realm option missing when connecting to Jumper/Pulse VPN via OpenConnect and NetworkManager. Product: systemsettings Version: 5.18.5 Platform: Other

[systemsettings] [Bug 415179] Touchpad disabled when detected as both mouse and touchpad

2020-02-22 Thread akb825
https://bugs.kde.org/show_bug.cgi?id=415179 --- Comment #4 from akb825 --- After updating today having xf86-input-synaptics installed no longer works around the bug. Applying the X11 config by Mads was able to restore the touchpad. -- You are receiving this mail because: You are watching all

[Touchpad-KCM] [Bug 415179] Touchpad disabled when detected as both mouse and touchpad

2019-12-15 Thread akb825
https://bugs.kde.org/show_bug.cgi?id=415179 --- Comment #2 from akb825 --- > Can you see if installing the xf86-input-synaptics brings back the option to > disable touchpad while mouse is connected. Thank you, that did restore the ability to adjust when the touchpad is enabled. I wa

[Touchpad-KCM] [Bug 415179] New: Touchpad disabled when detected as both mouse and touchpad

2019-12-14 Thread akb825
https://bugs.kde.org/show_bug.cgi?id=415179 Bug ID: 415179 Summary: Touchpad disabled when detected as both mouse and touchpad Product: Touchpad-KCM Version: unspecified Platform: Archlinux Packages OS:

[valgrind] [Bug 383723] SIGILL failure with ud2 opcode _dispatch_kq_init (in /usr/lib/system/libdispatch.dylib) (macOS)

2017-10-23 Thread akb825
https://bugs.kde.org/show_bug.cgi?id=383723 akb825 <akb...@gmail.com> changed: What|Removed |Added CC||akb...@gmail.com -