Bug 15830

Summary:	column size and position issues in rpmdrake
Product:	Mageia	Reporter:	Samuel Verschelde <stormi-mageia>
Component:	RPM Packages	Assignee:	Thierry Vignaud <thierry.vignaud>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	CC:	mageia, marja11, mg, olav, richard.j.walker
Version:	4
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	rpmdrake, gtk+3.0	CVE:
Status comment:
Attachments:	default sized window with really small summary column result after going fullscreen, columns are not aligned with headers anymore back to initial size, columns are not aligned with headers anymore

Description Samuel Verschelde 2015-05-03 12:14:52 CEST

As first reported in bug 12366, in somes cases (easily reproduced with "all packages, alphabetical order" and "all" instead of "GUI packages only"), the summary column is really small and not resizable.

Actually, it's probably resizable, but you can't because other unresizable columns such as release are too large.

Additionnaly, after switching to fullscreen columns are not aligned with headers anymore.

This is more easily understandable with screenshots, so screenshots follow.

Reproducible: 

Steps to Reproduce:

Samuel Verschelde 2015-05-03 12:15:27 CEST

CC: (none) => mageia, mg, richard.j.walker

Comment 1 Samuel Verschelde 2015-05-03 12:16:41 CEST

Created attachment 6433 [details]
default sized window with really small summary column

Comment 2 Samuel Verschelde 2015-05-03 12:17:14 CEST

Created attachment 6434 [details]
result after going fullscreen, columns are not aligned with headers anymore

Comment 3 Samuel Verschelde 2015-05-03 12:20:11 CEST

Created attachment 6435 [details]
back to initial size, columns are not aligned with headers anymore

Comment 4 Thierry Vignaud 2015-06-01 12:32:22 CEST

Probably be a gtk+3 bug...

CC: (none) => olav
Source RPM: rpmdrake => rpmdrake, gtk+3.0

Comment 5 Samuel Verschelde 2015-09-21 13:19:04 CEST

Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer 
maintained, which means that it will not receive any further security or bug 
fix updates.

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version.

Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't 
able to fix it before Mageia 4's end of life. If you are able to reproduce it 
against a later version of Mageia, you are encouraged to click on "Version" and 
change it against that version of Mageia. If it's valid in several versions, 
select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

Comment 6 Marja Van Waes 2015-09-28 16:45:00 CEST

This is fixed in cauldron, I don't know about Mga5

CC: (none) => marja11

Comment 7 Marja Van Waes 2015-10-27 06:56:31 CET

As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates.

This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version)

If you are able to reproduce it against a maintained version of Mageia, you are encouraged to
1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED"
2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.
3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page:
https://wiki.mageia.org/en/How_to_report_a_bug_properly

If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too).

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you
most [2].
[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

Status: NEW => RESOLVED
Resolution: (none) => OLD