Bug 18234

Summary:	aegisub-3.2.2: incorrect rendering of widgets
Product:	Mageia	Reporter:	Christian Apeltauer <c.apeltauer>
Component:	RPM Packages	Assignee:	David GEIGER <geiger.david68210>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal	CC:	marja11
Version:	Cauldron
Target Milestone:	---
Hardware:	i586
OS:	Linux
Whiteboard:
Source RPM:	aegisub-3.2.2-11.mga6	CVE:
Status comment:

Description Christian Apeltauer 2016-04-21 18:59:37 CEST

Description of problem:
1. If a new widget is added to the workspace (e. g. opening a video whereas no video was formerly opened), the new widget is not added until the window is resized. Likewise if a widget is removed (e. g. closing video) the occupied area is greyed but the other widgets are not resized until the whole window is resized.
2. If maximizing the window all widgets (except the icon bar) keep their current size and the new area is just a grey canvas

On console I get error outputs like the following:
(aegisub-3.2:5443): Gtk-WARNING **: Allocating size to GtkEntry 0xa2f1ea8 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?

Version-Release number of selected component (if applicable): aegisub-3.2.2-11.mga6

Version of wxGtk (against which aegisub is linked): wxgtk-3.0.2-7.mga6




How reproducible:


Steps to Reproduce:
1.
2.
3.

Marja Van Waes 2016-04-24 15:47:29 CEST

CC: (none) => marja11
Assignee: bugsquad => geiger.david68210

Comment 1 David GEIGER 2016-05-19 20:46:05 CEST

Hi,

Can you please report this issue upstream?

aegisub 3.2.2 is a quite old now and upstream has not published a new release yet.

http://devel.aegisub.org/wiki/Bugs

Comment 2 David GEIGER 2016-05-20 15:47:07 CEST

I have pushed a new release using latest source snapshot from upstream, could you test with this one if it works properly now, please?

- aegisub-3.2.2-14.git20160518.1.mga6

Comment 3 David GEIGER 2016-06-25 13:32:28 CEST

Closing of this bug as there is no response since 1 month and I think it should be fixed with the rebuild against wgtk3 compiled with GTK2.

Feel free to reopen if needed!

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