Bug 487795

Summary:	Plasma Workspace: startplasma on Wayland Display limited to 1024x768
Product:	[Plasma] plasmashell	Reporter:	tobias
Component:	Startup process	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	minor	CC:	kde, nate
Priority:	LO	Keywords:	wayland-only
Version First Reported In:	6.0.5
Target Milestone:	1.0
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

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.

Comment 3 Nate Graham 2025-04-05 22:24:28 UTC

What compositor are you using? KWin or something else?

Is this still happening in Plasma 6.3?

Comment 4 Bug Janitor Service 2025-04-20 03:47:17 UTC

🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!

Comment 5 tobias 2025-04-20 18:56:48 UTC

(In reply to Nate Graham from comment #3)
> What compositor are you using? KWin or something else?
> 
> Is this still happening in Plasma 6.3?

Weston is the compositor.
Now nothing works actually.
When I run the above command, a plasma loading screen is shown in fullscreen, and then it just disappears without error.
Happens in both situations: 1. inside a container (incus) and 2. on the host.

I assume that starting and using a KDE desktop inside a session is more complicated.

Comment 6 Nate Graham 2025-04-21 04:36:21 UTC

So it works as expected with KWin but not Weston?

Comment 7 Bug Janitor Service 2025-05-06 03:47:09 UTC

🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!

Comment 8 Bug Janitor Service 2025-05-21 03:47:04 UTC

🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.