After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 784048 - Consider using traditional UI under i3
Consider using traditional UI under i3
Status: RESOLVED FIXED
Product: simple-scan
Classification: Other
Component: general
3.20.x
Other Linux
: Normal normal
: ---
Assigned To: Simple Scan maintainer(s)
Simple Scan maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2017-06-21 16:51 UTC by Yuri Khan
Modified: 2017-06-22 08:42 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Yuri Khan 2017-06-21 16:51:16 UTC 
Simple Scan checks the XDG_CURRENT_DESKTOP environment variable against a whitelist of “traditional desktops”. If it finds a match, it hides the title bar and displays the traditional menu bar and toolbar.

IMO this approach is wrong and the traditional UI should be enabled in all cases except maybe GNOME; but if you want to whitelist, then please whitelist i3 also.
Comment 1 Robert Ancell 2017-06-21 21:27:17 UTC 
This problem has been fixed in the unstable development version. The fix will be available in the next major software release. You may need to upgrade your Linux distribution to obtain that newer version.

The reason we use a whitelist is Simple Scan is designed as a GNOME application, so this is the designed way it should be used. To support other desktops we have a list to opt-out of this.
Comment 2 Yuri Khan 2017-06-22 04:58:53 UTC 
Thanks.

For me, the critical difference in Simple Scan is that keyboard shortcuts work in classic UI but not in the new one. Especially important is Ctrl+1 to scan a page; the shortest equivalent in the header bar UI I could find is F10 Space. The Preferences dialog is not keyboard-accessible at all.

Should I file a separate bug report about that?
Comment 3 Robert Ancell 2017-06-22 08:42:02 UTC 
Yes, please file a new bug for that. Thanks!