Bug 344579

Summary: remember resolution setting for current krdc size
Product: [Applications] krdc Reporter: Silver Salonen <silver.salonen>
Component: generalAssignee: Urs Wolfer <uwolfer>
Status: RESOLVED UPSTREAM    
Severity: minor CC: cpburnz
Priority: NOR    
Version First Reported In: 4.13.2   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Silver Salonen 2015-02-26 07:08:55 UTC
When selecting "Current KRDC Size" as resolution and when KRDC is resized, the setting is set to "Custom Resolution" instead.

Reproducible: Always

Steps to Reproduce:
1. Start a session with resolution set to "Current KRDC Size", set also "Show this dialog again for this host".
2. Disconnect
3. Resize KRDC window
4. Start the session again

Actual Results:  
Desktop resolution selection is now on "Custom Resolution".

Expected Results:  
Desktop resolution selection is still "Current KRDC Size" and the new (changed) window size is followed.
Comment 1 C. P. Burns 2015-10-29 16:31:37 UTC
I can confirm that I'm encountering the same issue with KRDC 4.14.12. Also, when "Desktop resolution" defaults to "Custom Resolution" from this, "Width" and "Height" are both set to "0".
Comment 2 Justin Zobel 2022-10-15 10:59:47 UTC
Thank you for reporting this bug in KDE software. As it has been a while since this issue was reported and confirmed, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "CONFIRMED" when replying. Thank you!
Comment 3 Bug Janitor Service 2022-10-30 05:03:45 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Silver Salonen 2022-11-03 14:07:33 UTC
I just tried it again and I see it's actually fixed now. I'll set the Status to Resolved + Upstream. I hope it's correct?