Summary: | Kmail configure window's height is more than the screen | ||
---|---|---|---|
Product: | [Applications] kmail2 | Reporter: | Sudhir Khanger <sudhir> |
Component: | config dialog | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | normal | CC: | montel |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
configure window too big with huge empty space
Kontact configure window |
Description
Sudhir Khanger
2015-10-11 21:02:55 UTC
Created attachment 94956 [details]
configure window too big with huge empty space
kmail version ? Laurent 4.14.9 like I mentioned in the report. Are you asking anything different? [sudhir@fedora ~]$ rpm -qa | grep kmail kmail-libs-4.14.9-1.fc22.x86_64 kmail-4.14.9-1.fc22.x86_64 [sudhir@fedora ~]$ rpm -qa | grep kontact kontact-libs-4.14.9-1.fc22.x86_64 kontact-4.14.9-1.fc22.x86_64 Ah ok I didn't see your last line (by default we add it in "Version:" field" in bug report) Ok I will investigate it. Version field doesn't have 4.14.9. Created attachment 94963 [details]
Kontact configure window
Kontact's configure window is also too big.
Please verify which page has a lot of widget Laurent I am not sure what you are asking. In configue dialog box we have several page. I need to know which page is too big. All of them are too big. The configure dialog in kmail opens big and stays big irrespective of where you are in the dialog. This bug has never been confirmed for a Kontact version that is based on KDE Frameworks, except possibly a Technology Preview version 5.0.x. Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the opportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it. Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life. Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12, preferably more recent), please open a new one unless it already exists. Thank you for all your input. |