Bug 373810 - Can't choose a brush preset, the first time, at start (Krita 3.1.1 - Ubuntu 14.04)
Summary: Can't choose a brush preset, the first time, at start (Krita 3.1.1 - Ubuntu 1...
Status: RESOLVED UPSTREAM
Alias: None
Product: krita
Classification: Applications
Component: Usability (other bugs)
Version First Reported In: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-12-18 11:24 UTC by mvowada
Modified: 2016-12-23 10:35 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
(Video Example) (971.73 KB, video/mp4)
2016-12-18 11:24 UTC, mvowada
Details

Note You need to log in before you can comment on or make changes to this bug.
Description mvowada 2016-12-18 11:24:29 UTC
Created attachment 102851 [details]
(Video Example)

(Krita 3.1.1 - Ubuntu 14.04)

A minor glitch. Here're the steps I follow to reproduce it:

1) Restart Krita (important).
2) Go to: toolbar > "Choose brush preset" (the brush preset window will open).
3) Choose a brush preset.

Actual Results: I can't choose any of the brush presets from the list.
Expected Results: Choose the clicked brush preset.
Comment 1 wolthera 2016-12-18 13:49:37 UTC
This is a bug specific with Unity. I've had it a small forever, I am not sure what can be done about it at all.
Comment 2 Halla Rempt 2016-12-22 12:08:41 UTC
Yes, wolthera is right. It's a problem with Ubuntu's default window manager -- if we don't get a click, we can't do anything. You might consider reporting the issue in Ubuntu's bug tracker.
Comment 3 mvowada 2016-12-22 15:39:54 UTC
Thanks for the hint on Unity!
Comment 4 Dmitry Kazakov 2016-12-23 10:26:55 UTC
Also reproducible here with AppImage + Ubuntu Unity 16.04-pre + NVidia GPU
Comment 5 Dmitry Kazakov 2016-12-23 10:35:51 UTC
It looks like the popup window is somehow not fully initialized. Mouse press events come to it (e.g. for the tags combo box) but the popup appears at the top-left corner of the screen.

So I guess the problem is that the tablet coordinates are not translated correctly on the first run.