Bug 409104 - Can't open "Export" context menu
Summary: Can't open "Export" context menu
Status: RESOLVED UPSTREAM
Alias: None
Product: Spectacle
Classification: Applications
Component: General (show other bugs)
Version: 19.04.2
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Boudhayan Gupta
URL:
Keywords: wayland
Depends on:
Blocks:
 
Reported: 2019-06-24 04:52 UTC by Marvin Hagemeister
Modified: 2019-06-24 15:29 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 Marvin Hagemeister 2019-06-24 04:52:44 UTC
SUMMARY

Under wayland I can't open the export context menu. When this happens and spectacle is started from the terminal it prints this error message:

```
qt.qpa.wayland: Non-toplevel surfaces can't request window states
```

STEPS TO REPRODUCE
1. execute `spectacle` and take a screenshot
2. Export menu works
3. focus any other window
4. Now the Export menu won't shop up anymore

OBSERVED RESULT

Clicking the Export button does nothing

EXPECTED RESULT

Export context menu should open


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 Nicolas Fella 2019-06-24 08:45:22 UTC
I cannot reproduce it with Spectacle master and 19.04.

However, this sounds more like a KWin bug to me, so it might already be fixed in my KWin master session
Comment 2 David Redondo 2019-06-24 08:54:53 UTC
What version of Qt do you have?
Comment 3 Nate Graham 2019-06-24 11:24:24 UTC
Also cannot reproduce with Wayland and KWin from git master, and Qt 5.12.3.

As requested, please provide your Qt version.
Comment 4 Marvin Hagemeister 2019-06-24 15:27:45 UTC
Sorry, I forgot to fill out the OS section:

Linux/KDE Plasma: Arch Linux
(available in About System)
KDE Plasma Version: 5.16.1
KDE Frameworks Version: 5.59.0
Qt Version: 5.12.4

I'll try to check with kwin-git later.
Comment 5 David Redondo 2019-06-24 15:29:27 UTC
If it's Qt 5.12.4 it's propaply a Qt bug. Which is fixed by
https://codereview.qt-project.org/c/qt/qtwayland/+/265999