Bug 361733 - Opening File With Autosaved Version Externally Locks Splash Screen; Program
Summary: Opening File With Autosaved Version Externally Locks Splash Screen; Program
Status: RESOLVED FIXED
Alias: None
Product: krita
Classification: Applications
Component: General (show other bugs)
Version: 3.0 Alpha
Platform: Microsoft Windows Microsoft Windows
: NOR minor
Target Milestone: ---
Assignee: Krita Bugs
URL: http://stormingtheivory.tumblr.com/po...
Keywords: release_blocker
: 362932 (view as bug list)
Depends on:
Blocks:
 
Reported: 2016-04-13 17:41 UTC by Sam Keeper
Modified: 2019-09-05 08:15 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sam Keeper 2016-04-13 17:41:20 UTC
Opening a file that has an autosaved version externally--i.e navigating to the file in a folder and opening it, causing Krita to launch--causes a weird interaction between the splash screen and the "use autosaved version" dialogue. As seen in the attached post, the splash screen's "close" and "hide on opening" options disappear. It isn't possible to show in a static image, but since the "use autosaved version" dialogue box prevents you from selecting any other options, everything on the splash screen is locked. The splash screen, however, because it sits above EVERYTHING ELSE, blocks you from accessing the "autosaved..." dialogue.

As a result, the whole program is effectively locked down. If you attempt to close the dialogue window manually the whole program crashes.

System is Windows 8.1 using an Intel gpu

Reproducible: Always

Steps to Reproduce:
1. Locate a file with an autosaved version that will trigger the opening autosave dialogue
2. Open the file externally (i.e. by double clicking the file, right clicking krita and selecting it from the "recent files" list, &c)
3. Get stuck as described above



Categorized as minor because it's easy to work around this issue: simply open Krita, close the splash screen, then open the file. Should be fixed, but it's not actually system-breaking if you jump through the hoops in the right order.
Comment 1 wolthera 2016-04-14 13:27:08 UTC
Experienced this too on Ubuntu 15.10 with unity desktop
Comment 2 Halla Rempt 2016-04-14 18:46:13 UTC
Hi Sam,

Thanks for your report. I am now wondering whether this was because I had code at some point that forced the splash window on top at all times -- that got changed recently, but I'm not sure anymore when...
Comment 3 Halla Rempt 2016-04-16 13:32:54 UTC
https://phabricator.kde.org/T2296
Comment 4 Sam Keeper 2016-04-18 02:45:17 UTC
(In reply to Boudewijn Rempt from comment #2)
> Hi Sam,
> 
> Thanks for your report. I am now wondering whether this was because I had
> code at some point that forced the splash window on top at all times -- that
> got changed recently, but I'm not sure anymore when...

Yeah if I was to hazard a guess that's what I'd suspect the issue is. The splash screen does currently sit over top of all other programs on Windows, including even the Task Manager, which seems like it could cause a whole bunch of problems!
Comment 5 wolthera 2016-05-11 11:18:53 UTC
*** Bug 362932 has been marked as a duplicate of this bug. ***
Comment 6 wolthera 2016-05-11 11:31:00 UTC
https://phabricator.kde.org/T2480
Comment 7 Halla Rempt 2016-05-23 15:44:25 UTC
Git commit 11b54d3f7480e94ec2d8f5675815323d8c866ce0 by Boudewijn Rempt.
Committed on 23/05/2016 at 15:44.
Pushed by rempt into branch 'master'.

After it's turned into the recent documents windows.

Fixes Phabricator Task: T2480

M  +3    -2    libs/ui/KisApplication.cpp

http://commits.kde.org/krita/11b54d3f7480e94ec2d8f5675815323d8c866ce0