Bug 132126

Summary: Splash-image hides messages during startup
Product: [Applications] kphotoalbum Reporter: Marcus Gustafsson <gaspode>
Component: generalAssignee: KPhotoAlbum Bugs <kpabugs>
Status: RESOLVED WORKSFORME    
Severity: normal    
Priority: NOR    
Version: SVN (KDE3 branch)   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Marcus Gustafsson 2006-08-09 11:29:34 UTC
Version:           SVN (using KDE 3.5.2, Gentoo)
Compiler:          gcc version 3.3.5 (Gentoo Linux 3.3.5-r1, ssp-3.3.2-3, pie-8.7.7.1)
OS:                Linux (i686) release 2.6.16-gentoo-r13

If kphotoalbum tries to throw up a dialog box during the startup it is hidden below the splash-image making it impossible to click it (or for that matter see it).
My problem seems to be that whenever I start kphotoalbum after it has been forcibly killed by one reason or another it tries to ask me wether it should use the backup database, but I can't reach the dialog which is hidden below the splash-image. It is not possible to move the splash-image out of the way either.
Comment 1 Jan Kundrát 2007-05-10 14:49:27 UTC
This doesn't happen to me (+/- fresh KDE, Gentoo). Could you please try to reproduce either with recent release (3.0.2) or with recent SVN version?
Comment 2 Marcus Gustafsson 2007-06-03 19:24:54 UTC
I can confirm that it still happens with 3.0 (seems to be the newest stable one for x86_64 on Gentoo, yes, I changed computer since I filed the bug). The problem is less now as the splash screen is smaller than the dialog (so I can see it and move it out from behind the splash screen), but still exists. I think I solved it on my old computer with some bug-workaround setting in FVWM. I'll post it once I manage to get my .fvwm2rc from my old computer.
Comment 3 Jan Kundrát 2007-06-03 22:46:18 UTC
It seems that you've already brought that up to FVWM devs [1]. As it's something that is solved by reconfiguring the window manager and FVWM developers don't blame KPA here, I think we can close this one as "works for me".

Thanks for reporting anyway.

[1] http://www.fvwm.org/cgi-bin/fvwm-bug/fix in unstable?id=4089;user=guest