Bug 190393

Summary:	digikam always starts in fullscreen after a crash
Product:	[Applications] digikam	Reporter:	Russell Harrison <rharrison>
Component:	Usability-FullScreen	Assignee:	Digikam Developers <digikam-bugs-null>
Status:	RESOLVED FIXED
Severity:	crash	CC:	caulier.gilles
Priority:	NOR
Version:	0.10.0
Target Milestone:	---
Platform:	Fedora RPMs
OS:	Linux
Latest Commit:		Version Fixed In:	2.5.0
Sentry Crash Report:

Description Russell Harrison 2009-04-23 01:12:31 UTC

I'm also seeing this problem and I really can't delete the config file every time it happens.  Redoing all my settings every time is getting frustrating. :-(

+++ This bug was initially created as a clone of Bug #175598 +++

Version:           0.10.0-beta6 (using 4.1.80 (KDE 4.1.80 (KDE 4.2 Beta1)), Gentoo)
Compiler:          x86_64-pc-linux-gnu-gcc
OS:                Linux (x86_64) release 2.6.26-tuxonice

after the crash described in #175597 digikam always starts in fullscreen mode, even if i quit it in normal mode

Comment 1 caulier.gilles 2009-04-23 08:56:46 UTC

Are you a backtrace of the crash.

Which is the context to reproduce the crash ?

Gilles Caulier

Comment 2 Russell Harrison 2009-04-30 18:52:22 UTC

It seems to happen every time digiKam crashes no matter what the cause.  I have found that it only happens if I have digiKam maximized.  Looking at the config file the last time it happened I noticed that it was setting the width and height to one pixel greater than the resolution in this case.  Changing these values to something smaller than the maximum causes the application to open normally just not maximized.

I've been running without maximizing digiKam since I discovered this and have not seen the problem since.

Comment 3 caulier.gilles 2011-12-13 13:32:08 UTC

Russell,

This entry still valid with 2.x serie ?

Gilles Caulier

Comment 4 Russell Harrison 2011-12-14 21:30:04 UTC

(In reply to comment #3)
> Russell,
> 
> This entry still valid with 2.x serie ?
> 
> Gilles Caulier

I haven't seen the issue in quite some time.  Pleasantly I don't think I've even had a crash (face detection aside) using the 2.x series.  I think we can mark this as fixed!