Bug 507553 - Virtual Monitor does not work, even krfb and krdc are installed
Summary: Virtual Monitor does not work, even krfb and krdc are installed
Status: RESOLVED DUPLICATE of bug 493626
Alias: None
Product: kdeconnect
Classification: Applications
Component: plasmoid (other bugs)
Version First Reported In: 25.04.3
Platform: Manjaro Linux
: NOR normal
Target Milestone: ---
Assignee: Albert Vaca Cintora
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-07-27 19:53 UTC by Quadrant1737
Modified: 2026-01-05 11:58 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Quadrant1737 2025-07-27 19:53:27 UTC
SUMMARY
Virtual Monitor does not work, even krfb and krdc are installed

STEPS TO REPRODUCE
1. Install krfb and krdc on both devices (both with Manjaro Plasma)
2. Pair and connect with kdeconnect
3. Try to activate Virtual Monitor

OBSERVED RESULT
Virtual Monitor doesn't work
Message "Virtual Monitor does not work"

EXPECTED RESULT
Virtual Monitor should work

SOFTWARE/OS VERSIONS
1. device:
Operating System: Manjaro Linux 
KDE Plasma Version: 6.3.6
KDE Frameworks Version: 6.16.0
Qt Version: 6.9.1
Kernel Version: 6.12.39-1-MANJARO (64-bit)
Graphics Platform: X11
Processors: 16 × AMD Ryzen 7 7735HS with Radeon Graphics
Memory: 30.1 GiB of RAM
Graphics Processor: AMD Radeon 680M
Manufacturer: LENOVO
Product Name: 21M5CTO1WW
System Version: ThinkPad E16 Gen 2
2. device
Operating System: Manjaro Linux 
KDE Plasma Version: 6.3.6
KDE Frameworks Version: 6.16.0
Qt Version: 6.9.1
Kernel Version: 6.15.3-1-MANJARO (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i5-5300U CPU @ 2.30GHz
Memory: 23.3 GiB of RAM
Graphics Processor: Intel® HD Graphics 5500
Manufacturer: Dell Inc.
Product Name: Latitude E5550

ADDITIONAL INFORMATION
https://bugs.kde.org/show_bug.cgi?id=485829#c2
Seems to be longer.
Comment 1 aristsakas 2026-01-05 11:58:35 UTC

*** This bug has been marked as a duplicate of bug 493626 ***