Bug 487795 - Plasma Workspace: startplasma on Wayland Display limited to 1024x768
Summary: Plasma Workspace: startplasma on Wayland Display limited to 1024x768
Status: REPORTED
Alias: None
Product: plasmashell
Classification: Plasma
Component: Startup process (show other bugs)
Version: 6.0.5
Platform: Arch Linux Linux
: LO minor
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: wayland
Depends on:
Blocks:
 
Reported: 2024-05-30 14:26 UTC by tobias
Modified: 2024-06-12 19:56 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description tobias 2024-05-30 14:26:28 UTC
SUMMARY
Followup to https://discuss.kde.org/t/startplasma-wayland-options/15366

I could not find the Workspace category here, thats why I filed it in this category.

When I try to start startplasma on an existing Wayland Display, the Wayland window is limited to 1024x768.

Command tried (as user):
WAYLAND_DISPLAY=wayland-1 /usr/lib/plasma-dbus-run-session-if-needed /usr/bin/startplasma-wayland

When I try the same on an X-Display, I can adjust the size, though the original size is still 1024x768.

Now I would like to have two things:
1. The window size should be equal the Wayland Display size.
2. I would like to have or if existing know some options that I can give to "startplasma" to configure things and know how to do so.

OBSERVED RESULT
Window size limited.

EXPECTED RESULT
Window size should not be limited.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 6.0.5
KDE Frameworks Version: 6.2.0
Qt Version: 6.7.1
Kernel Version: 6.6.32-1-lts (64-bit)
Graphics Platform: Wayland
Graphics Processor: Mesa Intel® Graphics

ADDITIONAL INFORMATION
Might be similar to: https://bugs.kde.org/show_bug.cgi?id=436497
Comment 1 Nate Graham 2024-06-12 19:05:11 UTC
What's your use case for this?
Comment 2 tobias 2024-06-12 19:56:37 UTC
(In reply to Nate Graham from comment #1)
> What's your use case for this?

My usecase is quite complicated, I tried to use containers (LXC, Incus etc.), but the problem seems to exist when starting on the Host as well.