Bug 200629 - Printer driver selection menu requires scrolling when started
Summary: Printer driver selection menu requires scrolling when started
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: gtk2
Version: 5
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-07-29 09:35 UTC by Gilboa Davara
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-08-18 04:08:42 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Driver selection (112.59 KB, image/png)
2006-07-29 09:35 UTC, Gilboa Davara
no flags Details

Description Gilboa Davara 2006-07-29 09:35:55 UTC
Description of problem:
See attached picture. (Native display: 1600x1280)

Version-Release number of selected component (if applicable):
system-config-printer-0.6.151.7-1.x86_64

How reproducible:
Always.

Steps to Reproduce:
1. Create a new printer.
2. Open the driver/printer selection.
3.
  
Actual results:
Menu is not fully populated; needs scrolling to view all the printers.

Expected results:
Menu should be fully populated.

Additional info:
gtk problem?

Comment 1 Gilboa Davara 2006-07-29 09:35:55 UTC
Created attachment 133281 [details]
Driver selection

Comment 2 Tim Waugh 2006-08-01 11:54:24 UTC
That's just what the widget looks like when there are more entries than will fit
on the screen.  Move down to the bottom of it to scroll downwards.


Comment 3 Gilboa Davara 2006-08-01 12:10:41 UTC
... Then this bug should be opened against GTK?

Comment 4 Tim Waugh 2006-08-01 12:36:04 UTC
If you like (but it's intentional).

Comment 5 Tim Waugh 2006-08-01 12:37:03 UTC
FWIW the system-config-printer in FC6 avoids using that widget with large
numbers of entries.

Comment 6 Gilboa Davara 2006-08-01 12:48:27 UTC
OK. Thanks.
Should I report it upstream?

Comment 7 Matthias Clasen 2006-08-18 04:08:42 UTC
No need, there is an upstream bug about this behaviour


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