Bug 504645 - KMag amplification not working on Debian 12
Summary: KMag amplification not working on Debian 12
Status: REPORTED
Alias: None
Product: kmag
Classification: Applications
Component: general (other bugs)
Version First Reported In: 22.12.3
Platform: Debian stable Linux
: NOR major
Target Milestone: ---
Assignee: sarang
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-05-22 02:24 UTC by Roger Júnio
Modified: 2025-11-17 23:32 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
Print from Kmag without screen amplification (25.16 KB, image/png)
2025-05-22 02:24 UTC, Roger Júnio
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Roger Júnio 2025-05-22 02:24:17 UTC
Created attachment 181633 [details]
Print from Kmag without screen amplification

SUMMARY
KMag application is not working on Debian 12.
The application window opens but does not display any magnification.

STEPS TO REPRODUCE
1. Open Kmag (specifically, I use it with KDE Plasma Wayland or Gnome)
2. The error is here, there is no amplification even if you change the focus to something other than the mouse cursor.

OBSERVED RESULT
There is only the dark background of the Kmag window, there is no amplification.

EXPECTED RESULT
Screen amplification following the mouse cursor.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Debian GNU/Linux 12
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8
Kernel Version: 6.1.0-35-amd64 (64-bit)
Graphics Platform: offscreen
Processors: 16 × AMD Ryzen 7 5700U with Radeon Graphics
Memory: 15.0 GiB of RAM
Graphics Processor: AMD Radeon Graphics

ADDITIONAL INFORMATION
When running kmag via terminal, the following output continually occurs:

QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::end: Painter not active, aborted
Got Accessibility DBus address: "unix:path=/run/user/1000/at-spi/bus_0,guid=63ade28e1b0f317cb972deda682e7235"
Connected to Accessibility DBus at address= "unix:path=/run/user/1000/at-spi/bus_0,guid=63ade28e1b0f317cb972deda682e7235"
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::end: Painter not active, aborted
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::end: Painter not active, aborted
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::end: Painter not active, aborted
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::end: Painter not active, aborted
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::end: Painter not active, aborted
Comment 1 Shai 2025-11-17 21:49:11 UTC
I have two computers running Debian Testing. On one of them, I use plasma/X11, and kmag works. On the other, I use plasma/wayland, and it is exactly as the OP reported -- the kmag app opens, but shows nothing, no matter what the selection mode is.

KMagnifier
Version 25.04.0

KDE Frameworks 6.13.0
Qt 6.8.2
Comment 2 Antonio Rojas 2025-11-17 22:00:16 UTC
(In reply to Shai from comment #1)
> I have two computers running Debian Testing. On one of them, I use
> plasma/X11, and kmag works. On the other, I use plasma/wayland, and it is
> exactly as the OP reported -- the kmag app opens, but shows nothing, no
> matter what the selection mode is.

That is expected. kmag doesn't work on Wayland.
Comment 3 Shai 2025-11-17 23:32:10 UTC
(In reply to Antonio Rojas from comment #2)
> 
> That is expected. kmag doesn't work on Wayland.

In that case, kmag should detect that it's running under Wayland and give a proper error message, rather than display a blank window.