By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.

Bug 1519

Summary:	[Regression] Building tqt3 with -glibmainloop causes window settings to be ignored
Product:	TDE	Reporter:	Darrell <darrella>
Component:	non-core programs	Assignee:	Timothy Pearson <kb9vqf>
Status:	RESOLVED FIXED
Severity:	critical	CC:	bugwatch, darrella, kb9vqf
Priority:	P5
Version:	R14.0.0 [Trinity]
Hardware:	Other
OS:	Linux
Compiler Version:		TDE Version String:
Application Version:		Application Name:
Attachments:	kpdf valgrind output with tqt3/internalmainloop kpdf valgrind output with tqt3/gliblmainloop

Description Darrell 2013-05-20 19:40:49 CDT

I rebuilt a full GIT package set on Sunday. Today (Monday), when opening a pdf through konqueror, kpdf opens in a tiny 470x285 window. Maximzing kpdf, then closing, then reopening results in the same tiny window. Forced settings (title bar->Advanced) fail to override. kpdf now ignores the kpdfrc [MainWindow] settings, which I verified have not changed. My settings have kpdf always opening maximized.

Investigating reveals the problem is caused by building tqt3 with the -glibmainloop configure option. Building without that option results in kpdf opening correctly (maximized).

I'm adding this report to the R14.0.0 road map.

Comment 1 Darrell 2013-05-21 13:30:29 CDT

As far as I can tell, the only affected app I have found thus far is kpdf. Other Trinity apps and GTK apps open according to how I configured them or how I configured the Advanced window settings.

Definitely related to -glibmainloop, however.

Comment 2 Timothy Pearson 2013-05-22 00:26:49 CDT

Could easily be undefined behaviour in kpdf that usually* worked without the glib main loop (but was always technically broken).  When I get a chance I'll run kpdf through Valgrind and see if anything pops out.

* I have noticed this same problem with all KDE 3 and TDE versions, but it was sporadic and only seemed to affect certain machines.

Comment 3 Darrell 2013-05-22 15:40:27 CDT

I have copies of tqt3 built both ways. I can help test both versions. Right now I have the internal main loop copy running. I'm far from an expert with valgrind, yet when I run valgrind against kpdf I see memory leak error reports.

I build tdegraphics using the libpaper option. I don't know whether that plays a role.

Comment 4 Darrell 2013-05-22 16:04:11 CDT

A note for testing when tqt3 is built with -glibmainloop:

I can't always get kpdf to behave as described when I run kpdf from the mini cli, menu, or command line. Sometimes then kpdf opens maximized (as configured) and sometimes in a tiny window. When I open kpdf using a pdf through konqueror (double-click) then I always see kpdf open in a tiny window.

I don't know about the alleged memory leaks reported by valgrind (probably needs attention), but I suspect the base problem is not reading or not honoring the kpdfrc [MainWindow] settings.

I'll attach two valgrind outputs, one with tqt3 built using the internal main loop and the other with glibmainloop.

Comment 5 Darrell 2013-05-22 16:05:08 CDT

Created attachment 1285 [details]
kpdf valgrind output with tqt3/internalmainloop

Comment 6 Darrell 2013-05-22 16:05:35 CDT

Created attachment 1286 [details]
kpdf valgrind output with tqt3/gliblmainloop

Comment 7 Timothy Pearson 2013-05-23 11:34:51 CDT

Fixed in GIT hash 2d2661a (tdelibs).

Thanks for reporting!

Comment 8 Darrell 2013-05-23 14:33:49 CDT

kpdf is again behaving normally here. Thanks! :-)