Bug 185181 - Pup error dialog box cannot be resized
Pup error dialog box cannot be resized
Product: Fedora
Classification: Fedora
Component: pirut (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jeremy Katz
Depends On:
Blocks: FC6Target
  Show dependency treegraph
Reported: 2006-03-11 05:21 EST by Gilboa Davara
Modified: 2007-11-30 17:11 EST (History)
1 user (show)

See Also:
Fixed In Version: 1.0.1
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-04-12 13:07:35 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
"Error download packages" screenshot (73.33 KB, image/png)
2006-03-11 05:21 EST, Gilboa Davara
no flags Details

  None (edit)
Description Gilboa Davara 2006-03-11 05:21:07 EST
Pup error dialog box cannot be resized

Description of problem:
If pup yum-backend fails due to any reason (download failure / etc), an "Error
downloading packages" dialog box is displayed, with a small "Details" expander.
Once the detail expander is selected, a rather small text control is opened,
showing a detailed error description.
If I resize/maximize the "Error downloading packages" dialog box, the dialog box
itself is resized, but the "Details" control isn't resized with it.

Version-Release number of selected component (if applicable):
Pirut 0.9.10-1

How reproducible:

Steps to Reproduce:
1. Disconnect the network.
2. Start package updater.
3. Wait for network error.
4. Resize the "Error downloading packages" dialog box.
Actual results:
Details text control does not get resized with the parent dialog box.

Expected results:
... Details text control should get resized with parent dialog box.

Additional info:
Comment 1 Gilboa Davara 2006-03-11 05:21:07 EST
Created attachment 125987 [details]
"Error download packages" screenshot
Comment 2 Jeremy Katz 2006-04-12 13:07:35 EDT
This should be fixed in FC5 final

Note You need to log in before you can comment on or make changes to this bug.