Bug 397344 - Force solid background for maximized windows not working with qt apps and borderless maximized windows active
Summary: Force solid background for maximized windows not working with qt apps and bor...
Status: RESOLVED FIXED
Alias: None
Product: lattedock
Classification: Plasma
Component: application (show other bugs)
Version: 0.8.0
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: Michail Vourlakos
URL:
Keywords:
: 397454 (view as bug list)
Depends on:
Blocks:
 
Reported: 2018-08-10 13:41 UTC by Alvaro
Modified: 2018-08-21 12:16 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 0.8.1


Attachments
Transparent bar background with System Settings windows (419.63 KB, image/png)
2018-08-10 13:41 UTC, Alvaro
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alvaro 2018-08-10 13:41:33 UTC
Created attachment 114392 [details]
Transparent bar background with System Settings windows

Force solid background for maximized windows is not working when I use qt apps (dolphin, qtbittorrent...) and borderless maximezed windows. When I use firefox works normally. 

Notice that I have installed Active Windows Control and Global Menu plasmoids.
Comment 1 Michail Vourlakos 2018-08-20 13:36:03 UTC
I cant understand what you are describing.
I cant reproduce such behavior
Comment 2 Alvaro 2018-08-20 13:55:11 UTC
To reproduce the bug:

- Create a top bar
- Activate "Force solid background for maximized or snapped windows"
- Activate "Hide background for not maximized windows"
- Check "Support borderless maximized windows in different layouts" checkbox in Preferences tab of Settings windows and activate for the layout in "Layout" tab
- Open Dolphin and maximize it

In my case the bug happens with apps made in Qt:

Dolphin, qbittorrent, Settings, Discover, Vlc

With other apps such Firefox the tweak is working fine.
Comment 3 Michail Vourlakos 2018-08-20 14:02:30 UTC
I tried but I cant reproduce it...

What is your 'env' output?
Comment 4 Alvaro 2018-08-20 14:07:24 UTC
Sorry, I don't know how to check that. Could you tell me please?
Comment 5 Michail Vourlakos 2018-08-20 14:08:26 UTC
(In reply to Alvaro from comment #4)
> Sorry, I don't know how to check that. Could you tell me please?

just run in your terminal the 'env' command and send the output
Comment 6 Alvaro 2018-08-20 14:09:27 UTC
XDG_VTNR=7
LC_PAPER=en_GB
XDG_SESSION_ID=4
SSH_AGENT_PID=2986
PAM_KWALLET5_LOGIN=/run/user/1000/kwallet5.socket
LC_ADDRESS=en_GB
LC_MONETARY=en_GB
GPG_AGENT_INFO=/home/panabuntu/.gnupg/S.gpg-agent:0:1
TERM=xterm-256color
SHELL=/bin/bash
KONSOLE_DBUS_SERVICE=:1.158
DERBY_HOME=/usr/lib/jvm/java-8-oracle/db
QT_LINUX_ACCESSIBILITY_ALWAYS_ON=1
KONSOLE_PROFILE_NAME=Profile 1
GS_LIB=/home/panabuntu/.fonts
WINDOWID=148897799
LC_NUMERIC=en_GB
SHELL_SESSION_ID=4446d38f1db240d79689d43055136e10
GTK_MODULES=appmenu-gtk-module
XDG_SESSION_CLASS=user
KDE_FULL_SESSION=true
USER=panabuntu
LS_COLORS=rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:mi=00:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arc=01;31:*.arj=01;31:*.taz=01;31:*.lha=01;31:*.lz4=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.tzo=01;31:*.t7z=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.dz=01;31:*.gz=01;31:*.lrz=01;31:*.lz=01;31:*.lzo=01;31:*.xz=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.alz=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.cab=01;31:*.jpg=01;35:*.jpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.ogv=01;35:*.ogx=01;35:*.aac=00;36:*.au=00;36:*.flac=00;36:*.m4a=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:*.oga=00;36:*.opus=00;36:*.spx=00;36:*.xspf=00;36:
XCURSOR_SIZE=0
QT_ACCESSIBILITY=1
LC_TELEPHONE=en_GB
XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session3
XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0
QT_AUTO_SCREEN_SCALE_FACTOR=0
SSH_AUTH_SOCK=/tmp/ssh-FDEUfz96U2x9/agent.2939
SESSION_MANAGER=local/panalaptop:@/tmp/.ICE-unix/3040,unix/panalaptop:/tmp/.ICE-unix/3040
QT_SCREEN_SCALE_FACTORS=eDP-1=2;DP-1=2;HDMI-1=2;DP-2=2;HDMI-2=2;
DEFAULTS_PATH=/usr/share/gconf//usr/share/xsessions/plasma.default.path
LIBVIRT_DEFAULT_URI=qemu:///system
XDG_CONFIG_DIRS=/etc/xdg/xdg-/usr/share/xsessions/plasma:/etc/xdg
PATH=/home/panabuntu/bin:/home/panabuntu/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/usr/lib/jvm/java-8-oracle/bin:/usr/lib/jvm/java-8-oracle/db/bin:/usr/lib/jvm/java-8-oracle/jre/bin
DESKTOP_SESSION=/usr/share/xsessions/plasma
LC_IDENTIFICATION=en_GB
XDG_SESSION_TYPE=x11
PWD=/home/panabuntu
JAVA_HOME=/usr/lib/jvm/java-8-oracle
KONSOLE_DBUS_WINDOW=/Windows/1
LANG=en_GB.UTF-8
KDE_SESSION_UID=1000
MANDATORY_PATH=/usr/share/gconf//usr/share/xsessions/plasma.mandatory.path
LC_MEASUREMENT=en_GB
UBUNTU_MENUPROXY=1
KONSOLE_DBUS_SESSION=/Sessions/1
XDG_SEAT=seat0
SHLVL=1
HOME=/home/panabuntu
COLORFGBG=15;0
LANGUAGE=en_GB:en_US
KDE_SESSION_VERSION=5
XCURSOR_THEME=breeze_cursors
XDG_SESSION_DESKTOP=KDE
LOGNAME=panabuntu
XDG_DATA_DIRS=/home/panabuntu/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share/:/usr/share//usr/share/xsessions/plasma:/home/panabuntu/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share:/usr/share:/var/lib/snapd/desktop
J2SDKDIR=/usr/lib/jvm/java-8-oracle
DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-WPoWgmiM9n,guid=f74dccd69a089617640d31d35b7a7661
LESSOPEN=| /usr/bin/lesspipe %s
XDG_RUNTIME_DIR=/run/user/1000
PROFILEHOME=
DISPLAY=:0
XDG_CURRENT_DESKTOP=KDE
J2REDIR=/usr/lib/jvm/java-8-oracle/jre
LESSCLOSE=/usr/bin/lesspipe %s %s
LC_TIME=en_GB
XAUTHORITY=/home/panabuntu/.Xauthority
LC_NAME=en_GB
COLORTERM=truecolor
_=/usr/bin/env
Comment 7 Michail Vourlakos 2018-08-20 22:09:14 UTC
nothing special at your config,

I was hoping  that you may have added scale specific parameters such as PLASMA_USE_QT_SCALING

can you send your layout file in order to test drive it?
Comment 8 Alvaro 2018-08-20 22:17:16 UTC
I've sent you the layout file. I'm using scaling in the main settings, 2x scaling
Comment 9 Michail Vourlakos 2018-08-20 22:19:49 UTC
(In reply to Alvaro from comment #8)
> I've sent you the layout file. I'm using scaling in the main settings, 2x
> scaling

it works just fine in my system.
If you change your scaling to 1x the issue is fixed?
Comment 10 Alvaro 2018-08-20 22:25:08 UTC
(In reply to Michail Vourlakos from comment #9)
> (In reply to Alvaro from comment #8)
> > I've sent you the layout file. I'm using scaling in the main settings, 2x
> > scaling
> 
> it works just fine in my system.
> If you change your scaling to 1x the issue is fixed?

Yhea...with scale = 1 the issue is fixed
Comment 11 Michail Vourlakos 2018-08-21 10:20:56 UTC
(In reply to Alvaro from comment #10)
> (In reply to Michail Vourlakos from comment #9)
> > (In reply to Alvaro from comment #8)
> 
> Yhea...with scale = 1 the issue is fixed

try to run latte from the terminal with command: latte-dock -d --with-window


it will show you a Latte debug window, when the issue appears what is the screen resolution used by Latte dock, do you notice anything strange?
Comment 12 Michail Vourlakos 2018-08-21 10:24:02 UTC
ok, I think I found it, in your parameters there is:

QT_SCREEN_SCALE_FACTORS=eDP-1=2;DP-1=2;HDMI-1=2;DP-2=2;HDMI-2=2;

in my system even when from plasma systemsettings I use Scale Factor=2 these variables dont change.

1. what is your plasma version?
2. Have you set that manually?
3. What is your Qt version?
Comment 13 Alvaro 2018-08-21 10:28:26 UTC
(In reply to Michail Vourlakos from comment #12)
> ok, I think I found it, in your parameters there is:
> 
> QT_SCREEN_SCALE_FACTORS=eDP-1=2;DP-1=2;HDMI-1=2;DP-2=2;HDMI-2=2;
> 
> in my system even when from plasma systemsettings I use Scale Factor=2 these
> variables dont change.
> 
> 1. what is your plasma version?
> 2. Have you set that manually?
> 3. What is your Qt version?

1. 5.13.4
2. No, I set the scale parameter from the monitor settings window
3. 5.11.1

> in my system even when from plasma systemsettings I use Scale Factor=2 these
> variables dont change.

Maybe you should logout or restart.
Comment 14 Alvaro 2018-08-21 10:47:11 UTC
(In reply to Michail Vourlakos from comment #11)
> (In reply to Alvaro from comment #10)
> > (In reply to Michail Vourlakos from comment #9)
> > > (In reply to Alvaro from comment #8)
> > 
> > Yhea...with scale = 1 the issue is fixed
> 
> try to run latte from the terminal with command: latte-dock -d --with-window
> 
> 
> it will show you a Latte debug window, when the issue appears what is the
> screen resolution used by Latte dock, do you notice anything strange?

I've noticed that when I change the active window between app with no issue and app with issue the parameter StartLayoutSize(no fill applets) change a lot:

  Not Issued apps
- Firefox: 1071 px
- Thunderbird: 985 px
- Android studio: 483 px

  Issued apps
- Konsole: 483 px
- Systemsettings: 490 px
- KsysGuard: 483 px

Also the value "Draw Shadows(external)" changes. When I maximize the windows with no issue the value change from "No" to "Yes" and when I do it with the apps with the issue it remains in "No"
Comment 15 Michail Vourlakos 2018-08-21 10:54:58 UTC
This is kwin upstream issue and you can follow the discussion there when I uploaded the infos.

Fast way to solve this:

1. The issue appears when double-clicking the window titlebar and only for qt-based apps. If you drag the window title bar to the top the issue doesnt appear

2. In order to workaround it another way is to change the panel heights and make it even e.g. 31px., 33px. etc...
it breaks only for odd values, 32px., 34px. etc..
Comment 16 Alvaro 2018-08-21 11:12:07 UTC
(In reply to Michail Vourlakos from comment #15)
> This is kwin upstream issue and you can follow the discussion there when I
> uploaded the infos.
> 
> Fast way to solve this:
> 
> 1. The issue appears when double-clicking the window titlebar and only for
> qt-based apps. If you drag the window title bar to the top the issue doesnt
> appear
> 
> 2. In order to workaround it another way is to change the panel heights and
> make it even e.g. 31px., 33px. etc...
> it breaks only for odd values, 32px., 34px. etc..

1. That's true

2. I've tried to change the panel height but the issue still there.

PS:Just saying thanks for the great work you are doing :)
Comment 17 Michail Vourlakos 2018-08-21 11:13:51 UTC

*** This bug has been marked as a duplicate of bug 397700 ***
Comment 18 Michail Vourlakos 2018-08-21 11:18:35 UTC
*** Bug 397454 has been marked as a duplicate of this bug. ***
Comment 19 Michail Vourlakos 2018-08-21 12:12:46 UTC
Git commit bb8835f156c6cf828d2d8f89d335f813c79dd6a1 by Michail Vourlakos.
Committed on 21/08/2018 at 12:09.
Pushed by mvourlakos into branch 'master'.

identify maximized window screen differently

--there are cases that the window geometry isnt consistent
for maximized windows. That was breaking the previous
implementation of dynamic background because of:
https://bugs.kde.org/show_bug.cgi?id=397700
the new implementation is using only the window center in
order to identify the screen in which a window is
present
FIXED-IN: 0.8.1

M  +3    -5    app/dock/visibilitymanager.cpp

https://commits.kde.org/latte-dock/bb8835f156c6cf828d2d8f89d335f813c79dd6a1
Comment 20 Michail Vourlakos 2018-08-21 12:13:36 UTC
Git commit f61f1a58fe8ed4e545e41fdabfb79e14f833a560 by Michail Vourlakos.
Committed on 21/08/2018 at 12:13.
Pushed by mvourlakos into branch 'v0.8'.

identify maximized window screen differently

--there are cases that the window geometry isnt consistent
for maximized windows. That was breaking the previous
implementation of dynamic background because of:
https://bugs.kde.org/show_bug.cgi?id=397700
the new implementation is using only the window center in
order to identify the screen in which a window is
present
FIXED-IN: 0.8.1
(cherry picked from commit bb8835f156c6cf828d2d8f89d335f813c79dd6a1)

M  +3    -5    app/dock/visibilitymanager.cpp

https://commits.kde.org/latte-dock/f61f1a58fe8ed4e545e41fdabfb79e14f833a560
Comment 21 Michail Vourlakos 2018-08-21 12:16:07 UTC
(In reply to Alvaro from comment #0)
> 

I changed a bit the implementation in order to not fall into the case of https://bugs.kde.org/show_bug.cgi?id=397700 it should work without issues