Bug 489116 - Search Results Display Error
Summary: Search Results Display Error
Status: REPORTED
Alias: None
Product: kleopatra
Classification: Applications
Component: general (show other bugs)
Version: 3.2.0.240501
Platform: Debian stable Linux
: NOR normal
Target Milestone: ---
Assignee: Andre Heinecke
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-06-24 16:46 UTC by KitchM
Modified: 2024-11-21 10:31 UTC (History)
5 users (show)

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


Attachments
Search Results Display (38.74 KB, image/png)
2024-06-24 16:46 UTC, KitchM
Details

Note You need to log in before you can comment on or make changes to this bug.
Description KitchM 2024-06-24 16:46:37 UTC
Created attachment 170916 [details]
Search Results Display

***
If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

SUMMARY
There is a display issue on receiving results from server search.

STEPS TO REPRODUCE
1. Select "Lookup on Server".
2. Type in something like gnupg.org.
3. See screenshot

OBSERVED RESULT
Defective display layout

EXPECTED RESULT
Should show progress and results.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 
Debian 11 Bullseye
Xfce 4.16

ADDITIONAL INFORMATION
Comment 1 Ingo Klöcker 2024-10-17 20:46:19 UTC
Your screenshot shows a progress window in front of the search window. Have you resized the progress window (for example with the mouse) while the search was running? And what application style are you using? This doesn't look like KDE's Breeze style. It could be the Fusion style.

I tried to reproduce this issue, but I don't get any display errors when I resize the progress window with the mouse while the search is running. Neither with the Breeze style nor with the Fusion style.

I suspect either a bug in the application style or in the graphics driver. In any case, it's highly unlikely that this problem only happens in Kleopatra. It's very likely that you can see the same problem in any other Qt application using a progress window.
Comment 2 KitchM 2024-10-18 14:09:08 UTC
No, I didn't.
Comment 3 KitchM 2024-10-18 14:11:39 UTC
I don't know what an application style is.
Comment 4 Bug Janitor Service 2024-11-02 03:46:31 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 KitchM 2024-11-03 13:24:30 UTC
Since I do not know what the respondent was talking about, I cannot reply further.  However, the basic issue is that other programs do not have such behavior so it is abnormal.  My solution was to not use Kleopatra.  I just thought the programmer(s) should know about the issue.
Comment 6 Bug Janitor Service 2024-11-18 03:46:26 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 7 KitchM 2024-11-18 17:48:42 UTC
Since the problem is not fixed, it would be stupid to mark it as RESOLVED WORKSFORME regardless of how much time has passed.
Comment 8 Ingo Klöcker 2024-11-21 10:31:46 UTC
We don't do anything special in Kleopatra when showing this progress window. Moreover, the problem doesn't happen on my system (or any other system the Kleopatra developers use). Hence, unfortunately there's nothing we can do about it. (And I don't think we could do anything about it because I doubt it's caused by something we do.)

Thanks for taking the time to report this issue. Sorry, that we won't be able to resolve your problem.