[kwin] [Bug 365799] Graphical corruption and display stops updating when connecting external monitor through HDMI

[Artur O . via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365799

--- Comment #16 from Artur O.  ---
(In reply to Thomas Lübking from comment #15)
> I wanted to see KWin's opinion on the screen config ;-)
> 
> ==> Did you try OpenGL 2.0?
> 
> Ftr, GLX_EXT_buffer_age is *not* supported (the listing in client extensions
> is insufficient, one would expect it in server and general extensions as
> well)

Well after playing around and searching i found some help in #archlinux
channel. Uninstalling xf86-video-intel drivers solved my issues. No more
corruption and no more freezing when connecting/disconnecting monitor.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 365799] Graphical corruption and display stops updating when connecting external monitor through HDMI

[Artur O . via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365799

--- Comment #14 from Artur O.  ---
Created attachment 100183
  --> https://bugs.kde.org/attachment.cgi?id=100183=edit
kwin system log

The systemlog as requested (after the freezing occurs), but not sure if needed
now that this seems to be a compositing issue?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 365799] Graphical corruption and display stops updating when connecting external monitor through HDMI

[Artur O . via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365799

--- Comment #13 from Artur O.  ---
Created attachment 100182
  --> https://bugs.kde.org/attachment.cgi?id=100182=edit
glxinfo for ref

It supports bugger age it seems, but wanted to just include whole glxinfo just
for ref.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 365799] Graphical corruption and display stops updating when connecting external monitor through HDMI

[Artur O . via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365799

--- Comment #12 from Artur O.  ---
(In reply to Thomas Lübking from comment #10)
> The corruption looks very much like a driver bug, you see the buffer tiles
> which partially contain junk.
> Could be a buffer_age issue - check glxinfo for general support and in case
> KWIN_USE_BUFFER_AGE=0 kwin_x11 --replace &
> 
> https://community.kde.org/KWin/Environment_Variables#KWIN_USE_BUFFER_AGE
> 
> On
> > laptop screen stops updating while the second monitor works fine
> 
> Can you please dump the supportInformation again, but this time after
> attaching the screen and when one screen is dead (given that kwin actually
> responds in this state)
> Also, does restarting the compositor (SHIFT+Alt+F12, twice) resolve the
> state as well?
> 
> ---
> nb: this is on Qt 5.7.0 ...

Well I  played with this at work today. 

* You can drag/move windows when its "frozen", mouse updates as usual when
draging occurs just it won't update the screen/window position other than the
mouse.

* When toggling compositing with with the combination the moment you turn
compositing off the screen updates quickly as nothing has happend. The freeze
will also only occur when compositing is enabled. Turning compositing off with
the combination and then plugging in the external monitor just works.

* I tried the 'KWIN_USE_BUFFER_AGE=0 kwin_x11 --replace &' but the corruption
still occurs.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 365799] Graphical corruption and display stops updating when connecting external monitor through HDMI

[Artur O . via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365799

--- Comment #9 from Artur O.  ---
Here is a link to the video corruption I'm talking about
https://www.youtube.com/watch?v=x8fBxuncT9k

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 365799] Graphical corruption and display stops updating when connecting external monitor through HDMI

[Artur O . via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365799

--- Comment #8 from Artur O.  ---
(In reply to Artur O. from comment #7)
> Created attachment 100157 [details]
> kwin when screen corruption occur after unplugging external screen

most of these errors show up even after --replace and no visual errors occur.
Only new in this one is;
QXcbConnection: XCB error: 3 (BadWindow), sequence: 10168, resource id:
35651862, major code: 15 (QueryTree), minor code: 0

But not sure if this is even related or just coincidence.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 365799] Graphical corruption and display stops updating when connecting external monitor through HDMI

[Artur O . via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365799

--- Comment #7 from Artur O.  ---
Created attachment 100157
  --> https://bugs.kde.org/attachment.cgi?id=100157=edit
kwin when screen corruption occur after unplugging external screen

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 365799] Graphical corruption and display stops updating when connecting external monitor through HDMI

[Artur O . via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365799

--- Comment #6 from Artur O.  ---
Created attachment 100156
  --> https://bugs.kde.org/attachment.cgi?id=100156=edit
xrandr with external screen

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 365799] Graphical corruption and display stops updating when connecting external monitor through HDMI

[Artur O . via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365799

--- Comment #5 from Artur O.  ---
Created attachment 100155
  --> https://bugs.kde.org/attachment.cgi?id=100155=edit
Xrandr when running only laptop

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 365799] Graphical corruption and display stops updating when connecting external monitor through HDMI

[Artur O . via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365799

--- Comment #4 from Artur O.  ---
(In reply to Martin Gräßlin from comment #3)
> Does the problem also happen if you use OpenGL 2 in Compositing settings?

Yes, tried it now once more since i could not remember, it even kept the laptop
screen frozen after unplugging once.

1: Plug in screen -> laptop screen freezes, while the plugged in screen works 
2: (kwin_x11 --replace)
3: now works
4: unplugg new screen
5: screen repaints, however visual flickering/corruption occurs
6: (kwin_x11 --replace
7: now works

Same for opengl 2.0, however in kwin console i see:
OpenGL version: 3.0 instead of 3.3 when running replace when using 2.0
compositor settings instead of 3.1.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 365799] Graphical corruption and display stops updating when connecting external monitor through HDMI

[Artur O . via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365799

--- Comment #2 from Artur O.  ---
Created attachment 100146
  --> https://bugs.kde.org/attachment.cgi?id=100146=edit
kwin system log

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 365799] New: Graphical corruption and display stops updating when connecting external monitor through HDMI

[Artur O . via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365799

Bug ID: 365799
   Summary: Graphical corruption and display stops updating when
connecting external monitor through HDMI
   Product: kwin
   Version: 5.7.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: glx
  Assignee: kwin-bugs-n...@kde.org
  Reporter: commander.alch...@gmail.com

Laptop: Asus Zenbok UX32VD

I cannot remember when it started but it was sometimes after the Plasma 2 (I
think). When connecting an external display through HDMI the laptop screen
stops updating while the second monitor works fine. 

Using Kwin_X11 --replace after connecting the second screen mostly fixes this
however sometimes after a while i get weird graphical corruption, like an old
TV monitor (CRT) from the 90's in horror movies that it flashes and weird
visual screen noise occurring. Drop-down terminal that just flashes and shows
partially. 

Doing an kwin replace fixes this, switching to another backend from GLX to EGL
mitigates things ie, wont trigger the screen freeze on HDMI connection and also
does not have those graphical corruptions but it dooes not update/repaint
windows correctly all the time.

Reproducible: Always

Steps to Reproduce:
1. UX32VD ready
2. Connect something to HDMI
3. Laptop Screen freezes

Actual Results:  
Screen stops updating on laptop, and or graphical corruption...

Expected Results:  
working environment.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasma-nm] [Bug 362912] New: Add support for NM_DEVICE_TYPE_TUN

[Artur O . via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=362912

Bug ID: 362912
   Summary: Add support for NM_DEVICE_TYPE_TUN
   Product: plasma-nm
   Version: 5.6.4
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: editor
  Assignee: lu...@kde.org
  Reporter: commander.alch...@gmail.com
CC: jgrul...@redhat.com

NM seems to have updated how they list tun0. At this moment it shows up as 
"tun0 Unknown connection type"

Not sure if it should be listed there or be hidden or maybe shown that its
virtual somehow.
Probably related to: https://bugs.kde.org/show_bug.cgi?id=362911

Reproducible: Always

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasma-nm] [Bug 362911] Supress NM_DEVICE_TYPE_TUN from active connections

[Artur O . via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=362911

--- Comment #1 from Artur O.  ---
Created attachment 98885
  --> https://bugs.kde.org/attachment.cgi?id=98885=edit
Screenshot how it looks today.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasma-nm] [Bug 362911] New: Supress NM_DEVICE_TYPE_TUN from active connections

[Artur O . via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=362911

Bug ID: 362911
   Summary: Supress NM_DEVICE_TYPE_TUN from active connections
   Product: plasma-nm
   Version: 5.6.4
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: applet
  Assignee: jgrul...@redhat.com
  Reporter: commander.alch...@gmail.com
CC: lu...@kde.org

When connecting to a vpn connection plasma-nm will create and show tun0 entry
in both the plasma widget and in connections editor in addition to the VPN
connection.

Seems there is a change in NM:
https://bugzilla.gnome.org/show_bug.cgi?id=749369
git commit: 9110ad39c55bee0b338350d645374fb99fb6e47d

Feels like this should not be displayed during active connections.

Reproducible: Always

Steps to Reproduce:
1. Connect to vpn
2. Open applet
3. Now it will show tun0 besides the vpn connection in active connections.

Actual Results:  
Shows tun0 in active connections

Expected Results:  
should hide it since its virtual for the vpn connection.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 361987] Morphing popups: When morphing to a bigger tooltip the old content is streched.

[Artur O . via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=361987

--- Comment #6 from Artur O.  ---
(In reply to Thomas Lübking from comment #5)
> > Well i would say morph only the tooltip window and keep the size or 
> > constrain the resize to some % of the contents
> 
> That does obviously not work - I guess what you mean is to not transform the
> size (and not crossfade the content) but switch to new tooltip size &
> content directly and transform only the position.
> 
> There're already some filters to prevent "small™" and "large™" translations
> - matter of taste and values I guess.
> 
> I can't try your demo because I don't use KWin anymore.

Transform/Morph the container but not the contents. The demo would be jquery /
webb since i dont have any knoledge in qml/qt/kde dev. Or since you don't use
kwin anymore maybe try to record the situation when it happens.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 361987] Morphing popups: When morphing to a bigger tooltip the old content is streched.

[Artur O . via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=361987

--- Comment #4 from Artur O.  ---
(In reply to Thomas Lübking from comment #3)
> > Hide the old contents before starting the morph?
> And show what instead? The downsqueezed new content would be better?
> 
> There should be a crossfade from one to the other - does this not take place
> on your side?

Well i would say morph only the tooltip window and keep the size or constrain
the resize to some % of the contents final/original size so you don't stretch
for example one line elements across multiple lines, making it look like you
stretched something in ms paint.

I can see if i can get some js/jquery demo to demostrate my point. But you can
see on that website i linked how it currently looks when it strectches one line
element to 5+ rows during the morph. Just feels like the texture resize effect
when you resize a window. Looks good for minor adjustments but when you start
moving double size or more makes it just odd and lack for better word; ugly.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 361154] Running native OpenGL games - with compositing enabled - breaks X11 Plasma 5.6.0 Window Decorations

[Artur O . via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=361154

--- Comment #54 from Artur O.  ---
Created attachment 98474
  --> https://bugs.kde.org/attachment.cgi?id=98474=edit
Rendering issue Plasma Panel

I'm not 100% sure if this is related but also happens after fullscreen games
for me it seems and also noticed it after 5.6 update.

Toggling composting with ctrl+shift+F12 the panel switches betwen these two
states. One when effects are on (updated) and effects off (frozen).

Hovering over the frozen panel shows tooltips of the (updated) panel. Ie you
can hover over something and get a tooltip from a different application.

Also if you see the screenshot you see a standard X window icon, thats the Dota
2 icon.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 361154] Running native OpenGL games - with compositing enabled - breaks X11 Plasma 5.6.0 Window Decorations

[Artur O . via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=361154

--- Comment #53 from Artur O.  ---
Created attachment 98473
  --> https://bugs.kde.org/attachment.cgi?id=98473=edit
Decoration titlebar corruption

Here is a screenshot of decoration titlebar corruption.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 361987] Morphing popups: When morphing to a bigger tooltip the old content is streched.

[Artur O . via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=361987

--- Comment #2 from Artur O.  ---
If you need something easy case to test with;
https://www.epicgames.com/unrealtournament/forums/forumdisplay.php?57-Linux
atleast with chromium you can hover on _thread name_ and _thread op_ in the
forum to quickly see the morph doing its work.

Systemload (if you have many cores) and some smaller tooltop morphing from (big
-> small) shows that it morphs to the smaller one but content for the new
tooltip shows up during that time stretching it.

Again its polish thing and thanks for this effect, really gave KDE/Plasma a
more smooth feeling.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 361987] Morphing popups: When morphing to a bigger tooltip the old content is streched.

[Artur O . via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=361987

Artur O.  changed:

   What|Removed |Added

Summary|Morphing popups: When   |Morphing popups: When
   |morphing to a bigger one|morphing to a bigger
   |the old content is  |tooltip the old content is
   |streched.   |streched.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 361987] Morphing popups: When morphing to a bigger one the old content is streched.

[Artur O . via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=361987

Artur O.  changed:

   What|Removed |Added

Summary|Morphing popups: After  |Morphing popups: When
   |morphing to a bigger one|morphing to a bigger one
   |the old content is  |the old content is
   |streched.   |streched.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 361986] New: Toggling compositing when fullscreen breaks decoration

[Artur O . via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=361986

Bug ID: 361986
   Summary: Toggling compositing when fullscreen breaks decoration
   Product: kwin
   Version: 5.6.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: commander.alch...@gmail.com

Im not sure exactly if this is the right component but;
When a game launches fullscreen sometimes the decoration just breaks around
windows. Switching with ctrl + shift + F12 toggles between; 
"effects on + corruption" and "effects off + normal"

This shows how it can look with weird colours around windows;
https://i.imgur.com/GoL1vAf.jpg
I also noticed that decorations will flash from time to time, disappear also
with a black bar or just creating a odd shadow; https://i.imgur.com/uQlCMeb.png

Switching to oxygen when it happens seems to remove the corruption however
switching back to breeze introduces this again.



Reproducible: Always

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 352019] Qt5 drag pixmaps lag behind mouse cursor

[Artur O . via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=352019

--- Comment #46 from Artur O.  ---
(In reply to Thomas Lübking from comment #44)
> it's important to check the behavior over animated content (drag it across
> an unsynced glxgears) - the everyday nastiness could be mitigated by a less
> updating desktop window (removed animations in indicators etc)
> 
> didn't try, though

(In reply to alfaflo from comment #45)
> (In reply to Thomas Lübking from comment #44)
> > it's important to check the behavior over animated content (drag it across
> > an unsynced glxgears) - the everyday nastiness could be mitigated by a less
> > updating desktop window (removed animations in indicators etc)
> > 
> > didn't try, though
> 
> hm... "lag" gets bigger if I drag an icon over glxgears but still much
> better than in plasma <5.6.
> So it's not fixed but at least it doesn't prevent useful drag'n drop.
Well this is weird.
For me, lag gets quite bigger just by having glxgears open on the desktop (not
as much as before 5.6 but noticeable. 
No actual change if I drag over the glx window or if I minimize the glxgears
window. 

Still having the same mouse, and reducing the polling rate to 250MHz from
1000MHz and no lag is noticeable again no matter if I got glxgears open or not.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 352019] Qt5 drag pixmaps lag behind mouse cursor

[Artur O . via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=352019

--- Comment #42 from Artur O.  ---
(In reply to alfaflo from comment #41)
> (In reply to alfaflo from comment #38)
> > latest update (plasma 5.6 & qt 5.6) fixed it for me
> > by the way: plasma is now smooth like never before - thanks guys!
> > 
> > florian
> 
> An additional note: it seems that it's not fully gone. Compared to using
> noveau there's still a (very) little  "lag" but I think for daily use it's
> not a problem.

Do you mean the slight lag of like couple pixels? About the same as Window
drag?

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 361073] New: Session Logout and Session Switch User (from application launcher) get wrong position on the dialog.

[Artur O . via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=361073

Bug ID: 361073
   Summary: Session Logout and Session Switch User (from
application launcher) get wrong position on the
dialog.
   Product: plasmashell
   Version: 5.6.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Multi-screen support
  Assignee: aleix...@kde.org
  Reporter: commander.alch...@gmail.com
CC: plasma-b...@kde.org

Since the 5.6 update; 
session Logout dialog appears lower left of my primary monitor.
session switch user appears on the lower right of my primary monitor.

I have 3 monitors, (Portrait 1080x1920, Landscape 1920x1080, Landscape
1920x1080)
It seems that Logout appears trying to center between screen 0 and 1, while
switch user trying to center between them all and failing since the portrait
monitor is taller.

Reproducible: Always

Steps to Reproduce:
1. Have asymmetric screen setup, ie portrait and landscape screen setup. 
2. Click Leave - > Session Logout or Leave -> Session Switch User.
3. Dialog does not appear centered on primary monitor like it would before.

Actual Results:  
Wrong position.

Expected Results:  
Centered on primary monitor.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 356617] Primary display is not displayed in notification settings.

[Artur O . via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356617

--- Comment #6 from Artur O.  ---
(In reply to Artur O. from comment #5)
> (In reply to Martin Klapetek from comment #3)
> > Ok, the cause of the bug is the same as of bug 356461 (so fixing that one
> > will fix this one).
> 
> Arch just released plasma 5.5.1-1 and this issue seems to still be there.
> 
> If you open notification settings it will first show up as portrait for me
> but when i click over to "keyboard shortcuts" and then back it will be
> landscape. There is also some strange behaviour when moving the settings
> window.
> 
> Here is a video since I think it will better display the issue at hand.
> https://www.youtube.com/watch?v=9epQpiTBPrU

Still applies for Plasma 5.6 and QT 5.6

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 356653] When notification appears for first time, it appears twice

[Artur O . via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356653

--- Comment #32 from Artur O.  ---
(In reply to Artur O. from comment #31)
> (In reply to Martin Klapetek from comment #29)
> > Sorry, add plasma-workspace 5.6 to the mix.
> 
> Um has this gotten into main? Im still getting duplacate notifications about
> unlocked widgets on Arch with (kf5 5.19) and (plasma 5.5.5).

After Arch updated to Plasma 5.6 and QT 5.6 the issue is resolved for me.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 352019] Qt5 drag pixmaps lag behind mouse cursor

[Artur O . via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=352019

--- Comment #39 from Artur O.  ---
(In reply to alfaflo from comment #38)
> latest update (plasma 5.6 & qt 5.6) fixed it for me
> by the way: plasma is now smooth like never before - thanks guys!
> 
> florian

(In reply to Thomas Lübking from comment #36)
> Please see the referenced https://bugreports.qt.io/browse/QTBUG-48122

I can confirm this also. After Arch updated to QT 5.6 and Plasma 5.6 with the
rest the issue is now fixed for me too.

Looking at https://bugreports.qt.io/browse/QTBUG-48122 it seems it's not
related to this issue or that it was somehow fixed by another issue in QT and
that 48122 was not the "leading" cause of the lag.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 356653] When notification appears for first time, it appears twice

[Artur O . via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356653

--- Comment #31 from Artur O.  ---
(In reply to Martin Klapetek from comment #29)
> Sorry, add plasma-workspace 5.6 to the mix.

Um has this gotten into main? Im still getting duplacate notifications about
unlocked widgets on Arch with (kf5 5.19) and (plasma 5.5.5).

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 352050] Moving windows between monitors is stuttering badly when side screen tiling is enabled.

[Artur O . via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=352050

--- Comment #18 from Artur O.  ---
(In reply to Thomas Lübking from comment #16)
> the video is marked private.
> you can also attach it here or send it by mail

Oh sorry confused it with unlisted, its fixed now.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 352050] Moving windows between monitors is stuttering badly when side screen tiling is enabled.

[Artur O . via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=352050

--- Comment #17 from Artur O.  ---
(In reply to Thomas Lübking from comment #16)
> the video is marked private.
> you can also attach it here or send it by mail

Oh sorry confused it with unlisted, its fixed now.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 352050] Moving windows between monitors is stuttering badly when side screen tiling is enabled.

[Artur O . via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=352050

--- Comment #15 from Artur O.  ---
(In reply to Thomas Lübking from comment #14)
> How fast do you move windows?
> You'll have 250ms to get it across the active area (20px on either side of
> the edge) - otherwise the indicator is still created.

Not so slow, just a regular drag; here is a video I tried to do:
https://www.youtube.com/watch?v=Exa8UwPiP1U=youtu.be 

There is no indicator shown etc but it still feels and shows the stutter when
dragging.

Best Regards

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 352050] Moving windows between monitors is stuttering badly when side screen tiling is enabled.

[Artur O . via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=352050

--- Comment #13 from Artur O.  ---
(In reply to Thomas Lübking from comment #11)
> Git commit 3a1f11d21347032f7d1b8fd43d30ee7d3ce5ede0 by Thomas Lübking.
> Committed on 14/09/2015 at 19:02.
> Pushed by luebking into branch 'master'.
> 
> delay QuickTiling indication on inner screenborder
> 
> The user might just want to move the window from
> one screen to another, no point in wasting time to
> show the indicator
> REVIEW: 125024
> FIXED-IN: 5.5
> 
> M  +1-0client.cpp
> M  +1-0client.h
> M  +29   -8events.cpp
> 
> http://commits.kde.org/kwin/3a1f11d21347032f7d1b8fd43d30ee7d3ce5ede0

Hm im running on Arch and it seems that Windows still stutter when its enabled.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 356653] When notification appears for first time, it appears twice

[Artur O . via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356653

--- Comment #23 from Artur O.  ---
(In reply to Martin Klapetek from comment #22)
> Multifix at
> 
> https://git.reviewboard.kde.org/r/126459/
> https://git.reviewboard.kde.org/r/126460/
> https://git.reviewboard.kde.org/r/126461/

Read the reviewboard, 
> "The lock-widgets one is I think because of multiscreen, cause
> then you have two containments emitting two same notifications."
Then as I understand its not a duplicate and these won't fix that particular
issue?

Best Regards

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 356895] New: Unlock widgets triggers two of the same notification.

[Artur O . via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356895

Bug ID: 356895
   Summary: Unlock widgets triggers two of the same notification.
   Product: plasmashell
   Version: 5.5.1
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Notifications
  Assignee: mklape...@kde.org
  Reporter: commander.alch...@gmail.com
CC: plasma-b...@kde.org

When right-clicking on desktop and clicking unlock widgets, it triggers two
notifications about "widgets unlocked"

Reproducible: Always

Steps to Reproduce:
1. Lock widgets
2. Right-click on desktop and unlock widgets

Actual Results:  
Two notifications are shown, sometimes on different screens. (probably the
position bug getting triggered here).

Expected Results:  
One notification about unlocked widgets.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 356461] Notification Settings wrong default display for notifications and notifaction position.

[Artur O . via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356461

--- Comment #30 from Artur O.  ---
(In reply to Martin Klapetek from comment #29)
> Patch up at https://git.reviewboard.kde.org/r/126408/ if anybody
> wants to give it a try. That would help a lot if someone else could
> test it.

I tried your patch on workspace-git. Default position now seems to be top-right
of where the notification widget is located (primary desktop for me, middle). 

Spammed also the notifications with a simple for loop and notify send and they
seem stable.

Downgraded back to 1.5.1 and did the same, had to redo "unchecked custom
position" that for some reason was checked, but doing the for loop the
notifications came at different positions and even size. 

Summa summarum: I think the patch works (fixes default to top-right, and stable
notifications) at least for me and my "odd" setup. 

Thanks for your work Martin, and happy holidays!

For anyone else wanting to try this patch and is running arch, try this
pkgbuild https://gist.github.com/CommanderAlchemy/69eb96b5624a889bdea0 (drop in
replacement for current plasma-workspace).

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 356461] Notification Settings wrong default display for notifications and notifaction position.

[Artur O . via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356461

--- Comment #24 from Artur O.  ---
(In reply to Raghavendra kamath from comment #23)
> For me setting the custom location in notification solves thew problem and
> this setting now persists after reboot unlike earlier. I am on arch and can
> say this now works as intended

This bug report is about the default position not custom position.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 356461] Notification Settings wrong default display for notifications and notifaction position.

[Artur O . via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356461

--- Comment #17 from Artur O.  ---
(In reply to Martin Klapetek from comment #16)
> > for some reason plasma-desktop-git does not contain the notification applet
> 
> It's part of plasma-workspace.

Um for some reason the arch pkg is named plasma-desktop but it's
plasma-workspace.
https://aur.archlinux.org/packages/plasma-desktop-git/

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 356461] Notification Settings wrong default display for notifications and notifaction position.

[Artur O . via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356461

--- Comment #14 from Artur O.  ---
(In reply to Martin Klapetek from comment #13)
> Perhaps, although the notifications applet has in addition its
> own code to select the screen where to put the popups.
> 
> What it does is that it takes the screen information from Plasma,
> looks for a system screen that matches the one received from
> Plasma and then it intersects that screen with your "work area",
> that is the screen available space without panels.
> 
> But this is good for a single setup only, because as soon as you
> add a screen that has a different resolution, the work area will
> be the "bounding box", ie. the outer rectangle containing all
> of your screens, so the screen with the smaller resolution will
> have an empty space appended at its bottom part.
> 
> This becomes rather bad with setups like Artur's (if you look at
> his screenshots), because with the screen being in vertical mode,
> there's a lots of empty spaced attached to the other screens. So
> ideally I'd like to switch away from work area altogether, but it's
> hard to do so because I have just a single (laptop) screen, so I need
> someone to test patches.

Tried to find a git package in aur but for some reason plasma-desktop-git does
not contain the notification applet. However the 5.5.1 just went live on arch. 

Atm default position seems to be a bit random. Mostly it displays on the bottom
lower right corner of the working display (middle/primary). Spamming notify
send it sometimes just shows up on my left monitor in the middle.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 356617] Primary display is not displayed in notification settings.

[Artur O . via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356617

--- Comment #4 from Artur O.  ---
(In reply to Martin Klapetek from comment #3)
> Ok, the cause of the bug is the same as of bug 356461 (so fixing that one
> will fix this one).

Oh sweet, and thanks for fixing it =)

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 352194] Icon Only taskmanager in plasma sometimes triggers a preview even when no mouseover is in effect

[Artur O . via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=352194

--- Comment #1 from Artur O.  ---
I wonder if this could be related to:
https://bugs.kde.org/show_bug.cgi?id=352019

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 356608] New: Plasma panel does not launch on primary display

[Artur O . via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356608

Bug ID: 356608
   Summary: Plasma panel does not launch on primary display
   Product: plasmashell
   Version: 5.5.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Panel
  Assignee: plasma-b...@kde.org
  Reporter: commander.alch...@gmail.com

Plasma panel seem to launch on 0x0 instead of primary.

Reproducible: Always

Steps to Reproduce:
1. Have multimonitor
2. Add primary that is not 0x0
3. Reboot

Actual Results:  
Launches on 0x0

Expected Results:  
Launches on primary monitor.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 356610] New: Some applications does not seem to group automatically.

[Artur O . via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356610

Bug ID: 356610
   Summary: Some applications does not seem to group
automatically.
   Product: plasmashell
   Version: 5.5.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Icons-only Task Manager
  Assignee: h...@kde.org
  Reporter: commander.alch...@gmail.com
CC: plasma-b...@kde.org

I have noticed that Steam and Chromium maybe more does not seem to group
correctly. I have right-click on the icon -> "More Actions" ->  "Do not allow
this program to be grouped" and toggle it, then it seems to "update" and group
the application otherwise it won't.

Reproducible: Always

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 352194] Icon Only taskmanager in plasma sometimes triggers a preview even when no mouseover is in effect

[Artur O . via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=352194

Artur O.  changed:

   What|Removed |Added

Version|5.4.0   |5.5.0

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 356461] Notification Settings wrong default display for notifications and notifaction position.

[Artur O . via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356461

--- Comment #8 from Artur O.  ---
(In reply to Thaodan from comment #7)
> Is this patch inclued in 5.5? Cause the notification is still on the wrong
> screen.

This happend after 5.5 release so don't think so.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 356613] Notification Settings does not save custom position

[Artur O . via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356613

--- Comment #2 from Artur O.  ---
(In reply to Artur O. from comment #1)
> Here is a video of the issue. Notice how it won't jump to primary display.
> https://www.youtube.com/watch?v=D87oDLxNHd4

Sorry wrong bugreport :P

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 356613] Notification Settings does not save custom position

[Artur O . via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356613

--- Comment #1 from Artur O.  ---
Here is a video of the issue. Notice how it won't jump to primary display.
https://www.youtube.com/watch?v=D87oDLxNHd4

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 356613] New: Notification Settings does not save custom position

[Artur O . via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356613

Bug ID: 356613
   Summary: Notification Settings does not save custom position
   Product: plasmashell
   Version: 5.5.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Notifications
  Assignee: mklape...@kde.org
  Reporter: commander.alch...@gmail.com
CC: plasma-b...@kde.org

When setting custom position for the notifications they are reset at reboot.

Reproducible: Always

Steps to Reproduce:
1. Use custom notification setting.
2. Reboot
3. Profit

Actual Results:  
The "use custom position for the notification popup" is not selected anymore.

Expected Results:  
remember setting.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kopete] [Bug 305103] Kopete crashing during WLM account creation

[Artur O . via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=305103

Artur O.  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Artur O.  ---
Old issue that was fixed in some version.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kopete] [Bug 305103] Kopete crashing during WLM account creation

[Artur O . via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=305103

--- Comment #2 from Artur O.  ---
Old issue that was fixed in some version.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 356617] New: Wrong display is shown in notification settings.

[Artur O . via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356617

Bug ID: 356617
   Summary: Wrong display is shown in notification settings.
   Product: plasmashell
   Version: 5.5.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Notifications
  Assignee: mklape...@kde.org
  Reporter: commander.alch...@gmail.com
CC: plasma-b...@kde.org

Notification Settings show where to put the notifications but it seems that it
shows the 0x0 display. Mentioned it in this bug report but probably good to
create a new one for this issue.

Notice the screen orientation in screenshot:
https://bugsfiles.kde.org/attachment.cgi?id=95968 from bug:
https://bugs.kde.org/show_bug.cgi?id=356461

Reproducible: Always

Steps to Reproduce:
1. Have multiple monitors
2. Have different orientation for 0x0 display
3. Have not 0x0 as primary.
4. Open notification settings and notice the orientation shown.

Actual Results:  
Shown as portrait.

Expected Results:  
Shown as landscape.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 346437] Graphical corruption (Blue and black squares) in top left of windows

[Artur O . via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=346437

Artur O.  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #9 from Artur O.  ---
This was fixed in some update may it be kwin or nvidia.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-knotifications] [Bug 356461] Notification Settings wrong default display for notifications and notifaction position.

[Artur O . via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356461

--- Comment #3 from Artur O.  ---
Created attachment 95970
  --> https://bugs.kde.org/attachment.cgi?id=95970=edit
picture of notification when topright position is used.

Correct position of what I want but seems wrong that it shows portrait monitor
when its my primary landscape.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-knotifications] [Bug 356461] Notification Settings wrong default display for notifications and notifaction position.

[Artur O . via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356461

--- Comment #1 from Artur O.  ---
Created attachment 95968
  --> https://bugs.kde.org/attachment.cgi?id=95968=edit
picture of notification settings and display settings.

This shows the Notification Settings having the portrait monitor (0x0) as
template for settings instead of my primary monitor.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-knotifications] [Bug 356461] Notification Settings wrong default display for notifications and notifaction position.

[Artur O . via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356461

--- Comment #5 from Artur O.  ---
Created attachment 95972
  --> https://bugs.kde.org/attachment.cgi?id=95972=edit
picture of notification when middlebottom position is used.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-knotifications] [Bug 356461] Notification Settings wrong default display for notifications and notifaction position.

[Artur O . via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356461

--- Comment #4 from Artur O.  ---
Created attachment 95971
  --> https://bugs.kde.org/attachment.cgi?id=95971=edit
picture of notification when middletop position is used.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-knotifications] [Bug 356461] Notification Settings wrong default display for notifications and notifaction position.

[Artur O . via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356461

--- Comment #2 from Artur O.  ---
Created attachment 95969
  --> https://bugs.kde.org/attachment.cgi?id=95969=edit
picture of notification when default position is used.

Um about the position of the notification and relative to mouse. It now seems
that it's random. Sometimes it fires up on left sometimes on middle no matter
where the mouse is!

-- 
You are receiving this mail because:
You are watching all bug changes.