[systemsettings] [Bug 486199] Not possible to add bluetooth devices using only keyboard

2024-04-27 Thread Mads
https://bugs.kde.org/show_bug.cgi?id=486199 Mads changed: What|Removed |Added CC||m...@ab3.no --- Comment #1 from Mads --- Qt 6.7.0

[systemsettings] [Bug 486199] New: Not possible to add bluetooth devices using only keyboard

2024-04-27 Thread Mads
https://bugs.kde.org/show_bug.cgi?id=486199 Bug ID: 486199 Summary: Not possible to add bluetooth devices using only keyboard Classification: Applications Product: systemsettings Version: 6.0.4 Platform: Other

[kwin] [Bug 452119] With an Intel iGPU, animations aren't as smooth on Wayland versus Xorg

2023-06-30 Thread Mads
https://bugs.kde.org/show_bug.cgi?id=452119 Mads changed: What|Removed |Added CC||m...@ab3.no -- You are receiving this mail because

[kwalletmanager] [Bug 263174] Fingerprint support for kwallet

2022-11-15 Thread Mads
https://bugs.kde.org/show_bug.cgi?id=263174 Mads changed: What|Removed |Added CC||m...@ab3.no -- You are receiving this mail because

[kde] [Bug 458865] After an update to qt5-base the dolphin file picker dialog used in GTK applications via GTK_USE_PORTAL=1 ignores theming

2022-10-13 Thread Mads
https://bugs.kde.org/show_bug.cgi?id=458865 Mads changed: What|Removed |Added CC||m...@ab3.no -- You are receiving this mail because

[kscreenlocker] [Bug 455712] Non-functional "Unlock" button sometimes shown after entering correct password

2022-10-13 Thread Mads
https://bugs.kde.org/show_bug.cgi?id=455712 Mads changed: What|Removed |Added CC||m...@ab3.no -- You are receiving this mail because

[okular] [Bug 391625] Okular displays blurry images when opening epub files

2022-07-25 Thread Mads
https://bugs.kde.org/show_bug.cgi?id=391625 --- Comment #10 from Mads --- This doesn't have an easy fix, unfortunately, because more often than not a page is css data, not a raw png, even if it's a comic. So I haven't found a simple method for scaling the page when it needs to expand to fill

[okular] [Bug 391625] Okular displays blurry images when opening epub files

2022-07-25 Thread Mads
https://bugs.kde.org/show_bug.cgi?id=391625 --- Comment #9 from Mads --- When I checked now with an epub of a comic I just got from Kobo, and there the png was 1400x2000. So I don't think we should just double it, we should triple the size to 1800, 2400 to be sure. Or make it configurable

[okular] [Bug 391625] Okular displays blurry images when opening epub files

2022-07-25 Thread Mads
https://bugs.kde.org/show_bug.cgi?id=391625 Mads changed: What|Removed |Added CC||m...@ab3.no --- Comment #8 from Mads --- This is still

[systemsettings] [Bug 450090] X11 kwin does not scale cursor size when setting Global scale over 100 %

2022-02-12 Thread Mads
https://bugs.kde.org/show_bug.cgi?id=450090 Mads changed: What|Removed |Added CC||m...@ab3.no -- You are receiving this mail because

[systemsettings] [Bug 450090] New: X11 kwin does not scale cursor size when setting Global scale over 100 %

2022-02-12 Thread Mads
https://bugs.kde.org/show_bug.cgi?id=450090 Bug ID: 450090 Summary: X11 kwin does not scale cursor size when setting Global scale over 100 % Product: systemsettings Version: 5.24.0 Platform: Gentoo Packages

[kruler] [Bug 432521] Cannot move on wayland

2021-03-08 Thread Mads
https://bugs.kde.org/show_bug.cgi?id=432521 Mads changed: What|Removed |Added CC||m...@ab3.no --- Comment #2 from Mads --- Any news

[kwin] [Bug 430850] KWin - Add a way to force disable virtual keyboard

2020-12-27 Thread Mads
https://bugs.kde.org/show_bug.cgi?id=430850 Mads changed: What|Removed |Added CC||m...@ab3.no --- Comment #1 from Mads --- Here's

[kwin] [Bug 430850] New: KWin - Add a way to force disable virtual keyboard

2020-12-27 Thread Mads
https://bugs.kde.org/show_bug.cgi?id=430850 Bug ID: 430850 Summary: KWin - Add a way to force disable virtual keyboard Product: kwin Version: 5.20.4 Platform: Gentoo Packages OS: Linux Status: REPORTED

[elisa] [Bug 409587] Many inotify_add_watch errors starting Elisa

2020-12-13 Thread Mads Peter Rommedahl
https://bugs.kde.org/show_bug.cgi?id=409587 Mads Peter Rommedahl changed: What|Removed |Added CC||madspe...@rommedahl.info --- Comment #3

[digikam] [Bug 412578] Manual geotagging is difficult and time-consuming

2020-07-16 Thread Mads J
https://bugs.kde.org/show_bug.cgi?id=412578 Mads J changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED

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

2020-01-27 Thread Mads
https://bugs.kde.org/show_bug.cgi?id=415179 --- Comment #3 from Mads --- Same issue, on an XPS 15 9570 myself. Here's the workaround I'm using: $ cat /etc/X11/xorg.conf.d/99-custom.conf Section "InputClass" Identifier "Ignore synaptics mouse" MatchProduct &q

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

2020-01-27 Thread Mads
https://bugs.kde.org/show_bug.cgi?id=415179 Mads changed: What|Removed |Added CC||m...@ab3.no -- You are receiving this mail because

[digikam] [Bug 412578] Manual geotagging is difficult and time-consuming

2019-10-04 Thread Mads J
https://bugs.kde.org/show_bug.cgi?id=412578 --- Comment #5 from Mads J --- Point 3: It happens at all zoom levels. But I found a pattern: Every time the cursor come 50-80 pix near the edge of the map, it jumps back. Very annoying. See recording at https://www.fedefotos.dk/downloads

[digikam] [Bug 412578] Manual geotagging is difficult and time-consuming

2019-10-03 Thread Mads J
https://bugs.kde.org/show_bug.cgi?id=412578 Mads J changed: What|Removed |Added Resolution|DUPLICATE |--- Ever confirmed|0 |1

[digikam] [Bug 412578] New: Manual geotagging is difficult and time-consuming

2019-10-03 Thread Mads J
https://bugs.kde.org/show_bug.cgi?id=412578 Bug ID: 412578 Summary: Manual geotagging is difficult and time-consuming Product: digikam Version: 6.3.0 Platform: Windows CE OS: MS Windows Status: REPORTED

[Touchpad-KCM] [Bug 387153] libinput-backend touchpad KCM only used on Wayland

2018-01-18 Thread Mads
https://bugs.kde.org/show_bug.cgi?id=387153 Mads <m...@ab3.no> changed: What|Removed |Added CC||m...@ab3.no -- You are rec

[dolphin] [Bug 363548] file area becomes inaccessible for the mouse after opening a file on hidpi screen when using a multi monitor setting

2017-09-07 Thread Mads
https://bugs.kde.org/show_bug.cgi?id=363548 --- Comment #36 from Mads <m...@ab3.no> --- Oh, I managed to not be clear on that, sorry! No, I can't reproduce the no-clickable issue at all anymore. So for me, this bug is resolved. -- You are receiving this mail because: You are watching a

[dolphin] [Bug 363548] file area becomes inaccessible for the mouse after opening a file on hidpi screen when using a multi monitor setting

2017-09-07 Thread Mads
https://bugs.kde.org/show_bug.cgi?id=363548 --- Comment #33 from Mads <m...@ab3.no> --- To clarify: dolphin does not appear to have this unclickable file area issue anymore if using: - kde-frameworks 5.37 - dolphin 17.08.0 - plasma 5.10.0 - Qt 5.9.1 - modesetting ddx - QT_SCREEN_SCALE_F

[dolphin] [Bug 363548] file area becomes inaccessible for the mouse after opening a file on hidpi screen when using a multi monitor setting

2017-09-04 Thread Mads
https://bugs.kde.org/show_bug.cgi?id=363548 --- Comment #32 from Mads <m...@ab3.no> --- kscreen sets the QT_SCREEN_SCALE_FACTORS to "QT_SCREEN_SCALE_FACTORS=eDP-1-1=2;DP-1-1=2;HDMI-1-1=2;DP-1-2=2;HDMI-1-2=2;" on my computer when I have chosen 2 as scaling value. eDP-1 is conne

[dolphin] [Bug 363548] file area becomes inaccessible for the mouse after opening a file on hidpi screen when using a multi monitor setting

2017-07-06 Thread Mads
https://bugs.kde.org/show_bug.cgi?id=363548 --- Comment #29 from Mads <m...@ab3.no> --- Sorry for spamming the bug report, but I did some more testing - there was a difference between the computers, because one screen ran with QT_SCREEN_SCALE_FACTORS 1 on the non-primary monitor

[dolphin] [Bug 363548] file area becomes inaccessible for the mouse after opening a file on hidpi screen when using a multi monitor setting

2017-07-06 Thread Mads
https://bugs.kde.org/show_bug.cgi?id=363548 --- Comment #28 from Mads <m...@ab3.no> --- Hm I did some testing myself now, and I don't get this bug either. On one computer I have Qt 5.7.1 with KDE frameworks 5.35.0 and dolphin 17.04.2 (everything on Gentoo), and I don't see this bug (with

[dolphin] [Bug 363548] file area becomes inaccessible for the mouse after opening a file on hidpi screen when using a multi monitor setting

2017-07-05 Thread Mads
https://bugs.kde.org/show_bug.cgi?id=363548 --- Comment #27 from Mads <m...@ab3.no> --- If I understand this correctly, then the patch mentioned here is just a workaround for an underlying qt issue that has been fixed in qt 5.9.1... So you might want to wait until it rolls out or get it ins

[dolphin] [Bug 363548] file area becomes inaccessible for the mouse after opening a file on hidpi screen when using a multi monitor setting

2017-07-05 Thread Mads
https://bugs.kde.org/show_bug.cgi?id=363548 --- Comment #25 from Mads <m...@ab3.no> --- Is the system running with Qt 5.9.1? -- You are receiving this mail because: You are watching all bug changes.

[dolphin] [Bug 363548] file area becomes inaccessible for the mouse after opening a file on hidpi screen when using a multi monitor setting

2017-07-05 Thread Mads
https://bugs.kde.org/show_bug.cgi?id=363548 Mads <m...@ab3.no> changed: What|Removed |Added CC||m...@ab3.no --- Comment #23 from M

[konsole] [Bug 381978] konsole applies scaling twice when using two HiDPI monitors and moving the konsole window away from primary screen

2017-07-04 Thread Mads
https://bugs.kde.org/show_bug.cgi?id=381978 --- Comment #1 from Mads <m...@ab3.no> --- Hm, this isn't a konsole issue, I see now... the same happens in other Qt applications too. Can this bug be closed? -- You are receiving this mail because: You are watching all bug changes.

[konsole] [Bug 381978] konsole applies scaling twice when using two HiDPI monitors and moving the konsole window away from primary screen

2017-07-04 Thread Mads
https://bugs.kde.org/show_bug.cgi?id=381978 Mads <m...@ab3.no> changed: What|Removed |Added CC||m...@ab3.no -- You are rec

[konsole] [Bug 381978] New: konsole applies scaling twice when using two HiDPI monitors and moving the konsole window away from primary screen

2017-07-04 Thread Mads
https://bugs.kde.org/show_bug.cgi?id=381978 Bug ID: 381978 Summary: konsole applies scaling twice when using two HiDPI monitors and moving the konsole window away from primary screen Product: konsole Version:

[plasma-pa] [Bug 379245] plasma-pa does not honor switching pulseaudio server by using pax11publish

2017-05-02 Thread Mads
https://bugs.kde.org/show_bug.cgi?id=379245 --- Comment #4 from Mads <m...@ab3.no> --- In e.g. audacious, I have to press the stop button and then press play again for the audio to switch server, it won't switch the currently playing stream on the fly. But you don't have to r

[plasma-pa] [Bug 379245] plasma-pa does not honor switching pulseaudio server by using pax11publish

2017-05-02 Thread Mads
https://bugs.kde.org/show_bug.cgi?id=379245 --- Comment #2 from Mads <m...@ab3.no> --- $ qdbus org.pulseaudio.Server /org/pulseaudio/server_lookup1 org.PulseAudio.ServerLookup1.Address unix:path=/run/user/1000/pulse/dbus-socket $ pax11publish -e -S another_pulseserver $

[plasma-pa] [Bug 379245] plasma-pa does not honor switching pulseaudio server by using pax11publish

2017-04-26 Thread Mads
https://bugs.kde.org/show_bug.cgi?id=379245 Mads <m...@ab3.no> changed: What|Removed |Added CC||m...@ab3.no -- You are rec

[plasma-pa] [Bug 379245] New: plasma-pa does not honor switching pulseaudio server by using pax11publish

2017-04-26 Thread Mads
https://bugs.kde.org/show_bug.cgi?id=379245 Bug ID: 379245 Summary: plasma-pa does not honor switching pulseaudio server by using pax11publish Product: plasma-pa Version: unspecified Platform: Other OS:

[kwin] [Bug 356882] No compositing with Mesa 11.1.0 (EGL 1.5) and Plasma/KWin 5.5.1 when using EGL OpenGL interface

2016-01-18 Thread Mads via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356882 Mads <m...@ab3.no> changed: What|Removed |Added CC||m...@ab3.no --- Comment #12 from M