Bug 268405

Summary: Ark extraction dialog has improper dimensions (cannot see folders)
Product: [Applications] ark Reporter: Gabe A <gabextreme>
Component: generalAssignee: Raphael Kubo da Costa <rakuco>
Status: RESOLVED DUPLICATE    
Severity: normal    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: Improper default dimensions.

Description Gabe A 2011-03-13 21:11:52 UTC
Created attachment 57935 [details]
Improper default dimensions. 

Version:           unspecified (using KDE 4.6.1) 
OS:                Linux

When KDE is first installed, Ark's extraction dialog displays improper dimensions. This has been the case since KDE4.3. See screenshot. 

Reproducible: Always

Steps to Reproduce:
1. Install fresh KDE distribution, OR purge application settings cache, arkrc, window states, etc. 
2. Open an archive with Ark.
3. Click "Extract"
4. Observe improper dimensions of file extraction dialog. 

Actual Results:  
Dimensions are far too narrow for the window. New users are confused unless/until they realize that it's a default window size glitch and horizontally expand the window. 

Expected Results:  
Dimension of of 640,480 is a good minimum (and is still smaller than the default dimensions of Ark itself. 

Workaround 1: Resize window (end user)
Workaround 2: Add custom rule to ~/.kde/arkrc/share/config/kwinrulesrc as follows:

[2]
Description=Ark extract dialog dimension fix
size=640,480
sizerule=4
title=Extract – Ark
titlematch=1
types=32
wmclass=ark ark
wmclasscomplete=true
wmclassmatch=1

(Note that sizerule can be something else; if the dimensions are already cached, however, these newly specified dimensions will not apply). 

Setup: All default settings, fresh Ubuntu packages. It's been this way since KDE4.3, and only for Ark. KDE set to optimize for "Very high CPU, Very high resolution".
Comment 1 Raphael Kubo da Costa 2011-03-13 23:18:50 UTC
Thanks for the report, this bug is already being tracked.

*** This bug has been marked as a duplicate of bug 249476 ***