Bug 330040 - Canvas Only mode doesn't work on Intel HD Graphics on Windows
Summary: Canvas Only mode doesn't work on Intel HD Graphics on Windows
Status: RESOLVED UPSTREAM
Alias: None
Product: krita
Classification: Applications
Component: General (show other bugs)
Version: 2.8 Beta
Platform: Microsoft Windows Microsoft Windows
: NOR minor
Target Milestone: ---
Assignee: Krita Bugs
URL: http://i.imgur.com/DVHFrQI.png
Keywords:
Depends on:
Blocks:
 
Reported: 2014-01-16 16:55 UTC by Eiko Yumi
Modified: 2015-01-15 11:56 UTC (History)
2 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 Eiko Yumi 2014-01-16 16:55:23 UTC
Under Windows 8.1 64bit, with the latest downloadable build of Krita from the Krita.org website, an Intel HD2500 integrated GPU (with the latest drivers installed), enabling the OpenGL canvas causes the canvas-only mode (default key: tab) to show in full screen with garbage, and not getting updated in real time when painting/drawing.

Upon exiting the canvas mode, any change performed will show.

The canvas-only mode used to work in windowed mode in past builds, so perhaps that's where the problem lies.

Reproducible: Always

Steps to Reproduce:
0. Have an Intel integrated GPU
1. Create a new image
2. Enable the OpenGL mode (Settings>Configure Krita>Display>Enable OpenGL)
3. Enter the canvas-only mode (tab key)
4. Try drawing/painting
Actual Results:  
The image shows garbage and doesn't get updated.
The canvas only mode only seems to be working in full screen.

Expected Results:  
Besides working correctly, the canvas only mode (hide toolbars/UI) should work within the Krita window area. A different option/shortcut should be provided to make it work in full-screen, bypassing the windows manager's user interface.
Comment 1 Halla Rempt 2014-01-16 16:59:37 UTC
I can confirm with the HD4000 in my laptop. I'll check the nvidia card when I get home.
Comment 2 Eiko Yumi 2014-01-16 17:17:30 UTC
It appears that disabling the "Titlebar" option under:

Settings>Configure Krita>Canvas only settings

is a workaround to this problem, in addition to the usability issue I pointed.

However, I don't personally believe it's clear enough from a UI standpoint that disabling the "Titlebar" option from Canvas-only settings list makes the canvas-only mode not go full screen anymore.
Comment 3 Halla Rempt 2014-01-28 20:42:09 UTC
The option name has been changed. On NVidia the problem does not occur.
Comment 4 Dmitry Kazakov 2014-01-31 11:16:26 UTC
I have a hybrid graphics adapter Intel HDXXXX + ATI. When switching to Intel it shows garbage, when ATI --- everything is ok :)
Comment 5 Dmitry Kazakov 2014-01-31 11:28:44 UTC
The bug disappears if at least one Qt widget is shown on screen, e.g. Scroll Bars.
Comment 6 Dmitry Kazakov 2014-01-31 14:54:48 UTC
The bug was present from the very beginning of the implementation of openGL on Windows.
Tested on e02e34d22bae1d8beee80cd and the bug was already present.
Comment 7 Dmitry Kazakov 2014-02-01 06:42:39 UTC
Git commit 77fb87c6dc97d4db88c31a831decc8c6536181ad by Dmitry Kazakov.
Committed on 01/02/2014 at 06:41.
Pushed by dkazakov into branch 'master'.

Add a workaround for Intel video driver on Windows

This workaround just warns the user and shows the scrollbars on screen.

M  +44   -0    krita/ui/kis_view2.cpp

http://commits.kde.org/calligra/77fb87c6dc97d4db88c31a831decc8c6536181ad
Comment 8 Dmitry Kazakov 2014-02-01 06:45:27 UTC
Ok, the bug seems to be in a driver or Qt. Since we have a workaround now (and a message box for a user) I'm lowering the priority of the bug and renaming it.
Comment 9 Dmitry Kazakov 2014-02-04 08:27:12 UTC
Git commit 028cb602acd65c47729b4bd709fda49850dcd00e by Dmitry Kazakov.
Committed on 01/02/2014 at 06:41.
Pushed by dkazakov into branch 'calligra/2.8'.

Add a workaround for Intel video driver on Windows

This workaround just warns the user and shows the scrollbars on screen.

M  +44   -0    krita/ui/kis_view2.cpp

http://commits.kde.org/calligra/028cb602acd65c47729b4bd709fda49850dcd00e
Comment 10 Halla Rempt 2015-01-15 11:56:50 UTC
After some testing, it seems the workaround isn't necessary anymore -- intel apparently fixed their drivers.