[kwin] [Bug 351055] Icons are upscaled in "Large Icons" Task Switcher

[Martin Gräßlin]

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

--- Comment #28 from Martin Gräßlin <mgraess...@kde.org> ---
> Where do I have to search for those icons to confirm?

KWin takes the icon you can see in xprop. If there is only one in 32x32 that
one will be used. KWin does not use any installed icon as that is not how it's
supposed to be done for X11 window managers.

For Qt/KDE applications we are able to use the installed icons thanks to an
extension. Maybe it could be possible to define a window rule for the .desktop
file of a window.

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

[kscreenlocker] [Bug 379521] Kscreenlocker takes a full minute until it is responsive

[Martin Gräßlin]

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

Martin Gräßlin <mgraess...@kde.org> changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDSINFO
 Resolution|--- |BACKTRACE

--- Comment #1 from Martin Gräßlin <mgraess...@kde.org> ---
Unfortunately the backtrace is lacking debug symbols. If you are able to
reproduce please install the debug packages and attach a new backtrace. Without
the debug symbols we do not see where it crashes.

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

[kwin] [Bug 371862] xclipboard_syncer goes crazy when kwin_wayland goes down

[Martin Gräßlin]

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

Martin Gräßlin <mgraess...@kde.org> changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/kwi
   ||n/572f730e8ecd39767390d9a15
   ||68a8cb50625965b
 Status|REOPENED|RESOLVED
 Resolution|--- |FIXED

--- Comment #6 from Martin Gräßlin <mgraess...@kde.org> ---
Git commit 572f730e8ecd39767390d9a1568a8cb50625965b by Martin Gräßlin.
Committed on 05/05/2017 at 17:17.
Pushed by graesslin into branch 'master'.

[helper] Terminate xclipboardsyncer if kwin_wayland goes down

Summary:
Normally the xclipboardsyncer should terminate because the socket
becomes unusable. But we have reports of it not really going down and
running amok.

In order to prevent such situations this change registers SIGTERM to be
sent to xclipboardsyncer when the parent process (that is kwin_wayland)
dies in whatever way. This ensures that xclipboardsyncer cannot become
an orphan.

Test Plan: Only compile tested, no way to get into the problematic situation

Reviewers: #kwin, #plasma

Subscribers: plasma-devel, kwin

Tags: #kwin

Differential Revision: https://phabricator.kde.org/D5589

M  +1-0CMakeLists.txt
M  +1-0config-kwin.h.cmake
M  +9-0helpers/xclipboardsync/main.cpp

https://commits.kde.org/kwin/572f730e8ecd39767390d9a1568a8cb50625965b

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

[kwin] [Bug 377901] Window movement breaks after 49 days

[Martin Gräßlin]

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

Martin Gräßlin <mgraess...@kde.org> changed:

   What|Removed |Added

   Version Fixed In||5.8.7
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/kwi
   ||n/0bec9ad7337536e319c17c568
   ||4d97e1156399fdb

--- Comment #16 from Martin Gräßlin <mgraess...@kde.org> ---
Git commit 0bec9ad7337536e319c17c5684d97e1156399fdb by Martin Gräßlin.
Committed on 03/05/2017 at 19:36.
Pushed by graesslin into branch 'Plasma/5.8'.

Improve the x11 timestamp handling

Summary:
So far KWin only updated the x11 timestamp if the new timestamp is larger
than the existing one. While this is a useful thing it creates problems
when the 32 bit msec based time stamp wraps around which happens after
running an X server for 49 days. After the timestamp wrapped around KWin
would not update the timestamp any more and thus some calls might fail.
Most prominent victims are keyboard and pointer grab which fails as the
timestamp is either larger than the server timestamp or smaller than the
last grab timestamp.

Another problem related to timestamp handling is KWin getting broken by
wrong timestamps sent by applications. A prominent example is clusterssh
which used to send a timestamp as unix time which is larger than the
x timestamp and thus our timestamp gets too large.

This change addresses these problems by allowing to reset the timestamp.
This is only used from updateXTime (which is normally invoked before we
do things like grabKeyboard). Thus we make QX11Info::getTimestamp the
ultimate trusted source for timestamps.
Related: bug 348569
FIXED-IN: 5.8.7

Test Plan: As I cannot wait 50 days: unit tests for the two conditions added.

Reviewers: #kwin, #plasma

Subscribers: plasma-devel, kwin

Tags: #kwin

Differential Revision: https://phabricator.kde.org/D5704

M  +11   -0autotests/CMakeLists.txt
A  +123  -0autotests/test_x11_timestamp_update.cpp [License: GPL (v2)]
M  +6-2main.h
M  +1-1utils.cpp
M  +3-3utils.h

https://commits.kde.org/kwin/0bec9ad7337536e319c17c5684d97e1156399fdb

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

[kwin] [Bug 348569] KWin's timestamp mechanism isn't robust against bogus event times

[Martin Gräßlin]

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

Martin Gräßlin <mgraess...@kde.org> changed:

   What|Removed |Added

   Version Fixed In||5.8.7
 Resolution|--- |FIXED
 Status|REOPENED|RESOLVED
  Latest Commit||https://commits.kde.org/kwi
   ||n/0bec9ad7337536e319c17c568
   ||4d97e1156399fdb

--- Comment #38 from Martin Gräßlin <mgraess...@kde.org> ---
Git commit 0bec9ad7337536e319c17c5684d97e1156399fdb by Martin Gräßlin.
Committed on 03/05/2017 at 19:36.
Pushed by graesslin into branch 'Plasma/5.8'.

Improve the x11 timestamp handling

Summary:
So far KWin only updated the x11 timestamp if the new timestamp is larger
than the existing one. While this is a useful thing it creates problems
when the 32 bit msec based time stamp wraps around which happens after
running an X server for 49 days. After the timestamp wrapped around KWin
would not update the timestamp any more and thus some calls might fail.
Most prominent victims are keyboard and pointer grab which fails as the
timestamp is either larger than the server timestamp or smaller than the
last grab timestamp.

Another problem related to timestamp handling is KWin getting broken by
wrong timestamps sent by applications. A prominent example is clusterssh
which used to send a timestamp as unix time which is larger than the
x timestamp and thus our timestamp gets too large.

This change addresses these problems by allowing to reset the timestamp.
This is only used from updateXTime (which is normally invoked before we
do things like grabKeyboard). Thus we make QX11Info::getTimestamp the
ultimate trusted source for timestamps.
Related: bug 377901
FIXED-IN: 5.8.7

Test Plan: As I cannot wait 50 days: unit tests for the two conditions added.

Reviewers: #kwin, #plasma

Subscribers: plasma-devel, kwin

Tags: #kwin

Differential Revision: https://phabricator.kde.org/D5704

M  +11   -0autotests/CMakeLists.txt
A  +123  -0autotests/test_x11_timestamp_update.cpp [License: GPL (v2)]
M  +6-2main.h
M  +1-1utils.cpp
M  +3-3utils.h

https://commits.kde.org/kwin/0bec9ad7337536e319c17c5684d97e1156399fdb

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

[kwin] [Bug 379558] kwin_x11 PID: 2196 Signal: Segmentation fault (11) Time: 05/05/17 12:56:26

[Martin Gräßlin]

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

Martin Gräßlin <mgraess...@kde.org> changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #1 from Martin Gräßlin <mgraess...@kde.org> ---
as a workaround use the breeze window decoration.

*** This bug has been marked as a duplicate of bug 361236 ***

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

[kwin] [Bug 361236] Aurorae crashes in QQmlBinding::write on creation - Qt 5.6

[Martin Gräßlin]

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

Martin Gräßlin <mgraess...@kde.org> changed:

   What|Removed |Added

 CC||felipesabra...@gmail.com

--- Comment #119 from Martin Gräßlin <mgraess...@kde.org> ---
*** Bug 379558 has been marked as a duplicate of this bug. ***

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

[kwin] [Bug 379552] Alt Tabbing causes KWin to crash

[Martin Gräßlin]

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

Martin Gräßlin <mgraess...@kde.org> changed:

   What|Removed |Added

 Resolution|--- |BACKTRACE
 Status|UNCONFIRMED |NEEDSINFO

--- Comment #1 from Martin Gräßlin <mgraess...@kde.org> ---
Unfortunately the backtrace is lacking debug symbols. If you are able to
reproduce please install the debug packages and attach a new backtrace. Without
the debug symbols we do not see where it crashes.

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

[kwin] [Bug 379549] kwin crash after klockscreen+monitor off

[Martin Gräßlin]

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

Martin Gräßlin <mgraess...@kde.org> changed:

   What|Removed |Added

 Resolution|--- |BACKTRACE
 Status|UNCONFIRMED |NEEDSINFO

--- Comment #1 from Martin Gräßlin <mgraess...@kde.org> ---
Unfortunately the backtrace is lacking debug symbols. If you are able to
reproduce please install the debug packages and attach a new backtrace. Without
the debug symbols we do not see where it crashes.

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

[kwin] [Bug 379547] KWin creshed when I touch of left top screen corner with mouse (desktop grid action)

[Martin Gräßlin]

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

Martin Gräßlin <mgraess...@kde.org> changed:

   What|Removed |Added

 Resolution|--- |BACKTRACE
 Status|UNCONFIRMED |NEEDSINFO

--- Comment #1 from Martin Gräßlin <mgraess...@kde.org> ---
Unfortunately the backtrace is lacking debug symbols. If you are able to
reproduce please install the debug packages and attach a new backtrace. Without
the debug symbols we do not see where it crashes.

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

[kwin] [Bug 363224] Kwin crashes from time to time (this time using Virtual Machine Manager)

[Martin Gräßlin]

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

Martin Gräßlin <mgraess...@kde.org> changed:

   What|Removed |Added

 CC||heinrich.kieneke@t-online.d
   ||e

--- Comment #69 from Martin Gräßlin <mgraess...@kde.org> ---
*** Bug 379544 has been marked as a duplicate of this bug. ***

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

[kwin] [Bug 379544] Win-Crash after starting the finance software "moneyplex"

[Martin Gräßlin]

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

Martin Gräßlin <mgraess...@kde.org> changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Martin Gräßlin <mgraess...@kde.org> ---


*** This bug has been marked as a duplicate of bug 363224 ***

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

[kwin] [Bug 379528] KWin crash

[Martin Gräßlin]

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

Martin Gräßlin <mgraess...@kde.org> changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |UPSTREAM

--- Comment #1 from Martin Gräßlin <mgraess...@kde.org> ---
Crashes in the proprietary NVIDIA driver. Nothing we can do.

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

[kwin] [Bug 379472] Kwin crashes when attempting to start session.

[Martin Gräßlin]

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

Martin Gräßlin <mgraess...@kde.org> changed:

   What|Removed |Added

 Resolution|BACKTRACE   |INVALID
 Status|NEEDSINFO   |RESOLVED

--- Comment #5 from Martin Gräßlin <mgraess...@kde.org> ---
Changing to invalid as KWin must be run against the Qt version it was compiled
with.

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

[kwin] [Bug 363224] Kwin crashes from time to time (this time using Virtual Machine Manager)

[Martin Gräßlin]

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

Martin Gräßlin <mgraess...@kde.org> changed:

   What|Removed |Added

 CC||jv...@altsci.com

--- Comment #68 from Martin Gräßlin <mgraess...@kde.org> ---
*** Bug 379493 has been marked as a duplicate of this bug. ***

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

[kwin] [Bug 379493] Kwin Crashes rarely on pinentry dialog

[Martin Gräßlin]

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

Martin Gräßlin <mgraess...@kde.org> changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Martin Gräßlin <mgraess...@kde.org> ---


*** This bug has been marked as a duplicate of bug 363224 ***

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

[kwin] [Bug 348569] KWin's timestamp mechanism isn't robust against bogus event times

[Martin Gräßlin]

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

Martin Gräßlin <mgraess...@kde.org> changed:

   What|Removed |Added

  Flags||ReviewRequest+
URL||https://phabricator.kde.org
   ||/D5704

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

[kwin] [Bug 377901] Window movement breaks after 49 days

[Martin Gräßlin]

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

Martin Gräßlin <mgraess...@kde.org> changed:

   What|Removed |Added

URL||https://phabricator.kde.org
   ||/D5704
  Flags||ReviewRequest+

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

[plasma-integration] [Bug 376395] libreoffice and the xorg-xserver-video-intel-native-modesetting

[Martin Gräßlin]

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

--- Comment #5 from Martin Gräßlin <mgraess...@kde.org> ---
You reported this bug against Plasma-integration. Neither Neon, nor
libreoffice, nor the libreoffice-kde integration are developed by Plasma
developers. I'm sorry, you are wrong here.

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

[kwin] [Bug 379472] Kwin crashes when attempting to start session.

[Martin Gräßlin]

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

Martin Gräßlin <mgraess...@kde.org> changed:

   What|Removed |Added

 Resolution|--- |BACKTRACE
 Status|UNCONFIRMED |NEEDSINFO

--- Comment #1 from Martin Gräßlin <mgraess...@kde.org> ---
Unfortuntely the debug symbols for Qt are missing and it crashes directly when
creating the QApplication. Given the information we have from it: do you have
the KWin QPA plugin installed to the correct location so that Qt finds it?

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

[kwin] [Bug 363224] Kwin crashes from time to time (this time using Virtual Machine Manager)

[Martin Gräßlin]

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

Martin Gräßlin <mgraess...@kde.org> changed:

   What|Removed |Added

 CC||aaroncdcalc...@gmail.com

--- Comment #67 from Martin Gräßlin <mgraess...@kde.org> ---
*** Bug 379480 has been marked as a duplicate of this bug. ***

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

[kwin] [Bug 379480] Random kWin crashes

[Martin Gräßlin]

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

Martin Gräßlin <mgraess...@kde.org> changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #1 from Martin Gräßlin <mgraess...@kde.org> ---


*** This bug has been marked as a duplicate of bug 363224 ***

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

[kwin] [Bug 379465] kwin_x11 crashes after mpv is set to fullscreen

[Martin Gräßlin]

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

Martin Gräßlin <mgraess...@kde.org> changed:

   What|Removed |Added

 Resolution|--- |BACKTRACE
 Status|UNCONFIRMED |NEEDSINFO

--- Comment #1 from Martin Gräßlin <mgraess...@kde.org> ---
As always for arch users the backtrace is completely useless as it's missing
debug symbols. Nothing we can do.

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

[kwin] [Bug 363224] Kwin crashes from time to time (this time using Virtual Machine Manager)

[Martin Gräßlin]

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

Martin Gräßlin <mgraess...@kde.org> changed:

   What|Removed |Added

 CC||mrnam...@gmx.co.uk

--- Comment #66 from Martin Gräßlin <mgraess...@kde.org> ---
*** Bug 379446 has been marked as a duplicate of this bug. ***

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

[kwin] [Bug 379446] KWin crash when attempting to install vcrun2008 on wine

[Martin Gräßlin]

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

Martin Gräßlin <mgraess...@kde.org> changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Martin Gräßlin <mgraess...@kde.org> ---


*** This bug has been marked as a duplicate of bug 363224 ***

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

[kwin] [Bug 379410] Window tab dragging has no effect

[Martin Gräßlin]

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

--- Comment #3 from Martin Gräßlin <mgraess...@kde.org> ---
> Ah, I see that now, thank you.  Is there an issue that I may track to be
> informed about when this regression is fixed?  I've been running KDE 4 for
> the past year because of this missing feature.

We currently don't have any time line on it. With all of GTK going to CSD I'm
not even sure it makes sense to add it as it means a weird user experience (why
can't I add Libreoffice?)

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

[kwin] [Bug 379338] huge memory usage. from 0 to 16Gb in less than 30 seconds

[Martin Gräßlin]

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

Martin Gräßlin <mgraess...@kde.org> changed:

   What|Removed |Added

  Component|wayland-generic |aurorae

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

[kwayland-integration] [Bug 379434] Wayland: Open File dialog unable to handle "Enter" button

[Martin Gräßlin]

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

Martin Gräßlin <mgraess...@kde.org> changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |INVALID

--- Comment #1 from Martin Gräßlin <mgraess...@kde.org> ---
Chromium is an X11 application. Xwayland on Neon still has problems with such
kinds of setups, it requires Xwayland 1.19.

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

[kwin] [Bug 379410] Window tab dragging has no effect

[Martin Gräßlin]

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

Martin Gräßlin <mgraess...@kde.org> changed:

   What|Removed |Added

 Resolution|--- |LATER
Version|unspecified |5.9.5
   Assignee|mgraess...@kde.org  |kwin-bugs-n...@kde.org
  Component|general |decorations
Product|frameworks-kwindowsystem|kwin
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Martin Gräßlin <mgraess...@kde.org> ---
Window tab support is currently not implemented as listed in
https://community.kde.org/Plasma/5.9_Errata#Missing_features

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

[kwin] [Bug 379338] huge memory usage. from 0 to 16Gb in less than 30 seconds

[Martin Gräßlin]

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

--- Comment #7 from Martin Gräßlin <mgraess...@kde.org> ---
Just had a look into massif and it seems to confirm that it is related to
aurorae. There is one element of 677 MiB and it is from inside Aurorae. It
might be possible that ac08c5ac9d4532b2506c76e8b69249b32d365aa3 fixed this
issue, too. But that's only in master

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

[kwin] [Bug 379381] New and reappearing windows appear on all desktops

[Martin Gräßlin]

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

--- Comment #1 from Martin Gräßlin <mgraess...@kde.org> ---
please provide the output of:
qdbus org.kde.KWin /KWin supportInformation

Also please use xprop and xwininfo on a broken window.

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

[kwin] [Bug 379379] Crash upon opening IntelliJ Toolbox

[Martin Gräßlin]

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

Martin Gräßlin <mgraess...@kde.org> changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |UPSTREAM

--- Comment #1 from Martin Gräßlin <mgraess...@kde.org> ---
The crash happened in the proprietary NVIDIA driver. There is nothing we can do
about it.

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

[kwin] [Bug 379376] media player related crash

[Martin Gräßlin]

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

Martin Gräßlin <mgraess...@kde.org> changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #1 from Martin Gräßlin <mgraess...@kde.org> ---
As a workaround use the breeze window decoration

*** This bug has been marked as a duplicate of bug 361236 ***

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

[kwin] [Bug 361236] Aurorae crashes in QQmlBinding::write on creation - Qt 5.6

[Martin Gräßlin]

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

Martin Gräßlin <mgraess...@kde.org> changed:

   What|Removed |Added

 CC||pmanou...@gmail.com

--- Comment #118 from Martin Gräßlin <mgraess...@kde.org> ---
*** Bug 379376 has been marked as a duplicate of this bug. ***

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

[kwin] [Bug 379369] kwin_wayland crash when closing down

[Martin Gräßlin]

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

Martin Gräßlin <mgraess...@kde.org> changed:

   What|Removed |Added

  Flags||Wayland+, X11-

--- Comment #1 from Martin Gräßlin <mgraess...@kde.org> ---
compare adcd98aa1f2ac2f3d0da46dcc41eb23944acbafe in breeze

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

[kwin] [Bug 379338] huge memory usage. from 0 to 16Gb in less than 30 seconds

[Martin Gräßlin]

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

--- Comment #6 from Martin Gräßlin <mgraess...@kde.org> ---
Given the debug output it could be related to the window decoration you are
using. I haven't tested aurorae much on Wayland, consider giving a try to the
default breeze.

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

[kwin] [Bug 379424] KWin Crash After Waking From Suspend

[Martin Gräßlin]

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

--- Comment #1 from Martin Gräßlin <mgraess...@kde.org> ---
please provide the output of:
qdbus org.kde.KWin /KWin supportInformation

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

[kwin] [Bug 377756] Restore windows to correct position and activity

[Martin Gräßlin]

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

Martin Gräßlin <mgraess...@kde.org> changed:

   What|Removed |Added

 CC||loic.yh...@gmail.com

--- Comment #3 from Martin Gräßlin <mgraess...@kde.org> ---
*** Bug 379421 has been marked as a duplicate of this bug. ***

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

[kwin] [Bug 379421] kwin crashes after "unable to claim manager selection, another wm running"

[Martin Gräßlin]

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

Martin Gräßlin <mgraess...@kde.org> changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Martin Gräßlin <mgraess...@kde.org> ---


*** This bug has been marked as a duplicate of bug 377756 ***

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

[kwin] [Bug 379397] Startup crash

[Martin Gräßlin]

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

Martin Gräßlin <mgraess...@kde.org> changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #1 from Martin Gräßlin <mgraess...@kde.org> ---


*** This bug has been marked as a duplicate of bug 363224 ***

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

[kwin] [Bug 363224] Kwin crashes from time to time (this time using Virtual Machine Manager)

[Martin Gräßlin]

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

Martin Gräßlin <mgraess...@kde.org> changed:

   What|Removed |Added

 CC||arsenarsen...@outlook.com

--- Comment #65 from Martin Gräßlin <mgraess...@kde.org> ---
*** Bug 379397 has been marked as a duplicate of this bug. ***

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

[kwin] [Bug 379398] KWin Crash after installation of VirtualBox extensions

[Martin Gräßlin]

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

Martin Gräßlin <mgraess...@kde.org> changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #1 from Martin Gräßlin <mgraess...@kde.org> ---


*** This bug has been marked as a duplicate of bug 363224 ***

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

[kwin] [Bug 363224] Kwin crashes from time to time (this time using Virtual Machine Manager)

[Martin Gräßlin]

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

Martin Gräßlin <mgraess...@kde.org> changed:

   What|Removed |Added

 CC||wolfgang@aon.at

--- Comment #64 from Martin Gräßlin <mgraess...@kde.org> ---
*** Bug 379398 has been marked as a duplicate of this bug. ***

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

[kwin] [Bug 377901] Window movement breaks after 49 days

[Martin Gräßlin]

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

--- Comment #13 from Martin Gräßlin <mgraess...@kde.org> ---
> I would _expect_ that XCB wouldn't do something that runs contrary to the
> xlib documentation's definition of basic datatypes, such as timestamps.
> Maybe you've gotten bitten by just such an incompatibility, though?

Unfortunately yes. Recent case: https://phabricator.kde.org/D5549

Also there are differences in the library. E.g. Xlib is older than 64 bit, so
some parts which are in the protocol defined as int32 are set to long in Xlib,
which results in nice incompatible code on 64 bit. So yeah it doesn't match 1:1
and in these aspects doesn't match the X protocol. That's why I don't trust the
XLib library any more for interaction with X.

Anyway I checked the x protocol and timestamp is a card32 which would support
the description of XLib. Unfortunately the x protocol doesn't talk about how
timestamps are intended to be.

> 
> > Also a spec is one thing, the other is how the one and only
> > X-Server behaves.
> 
> True, but I expect a few things to be true
> * xlib's description of how timestamp rollover is handled in the X server is
> how it's intended to be handled.
> * The x.org developers working on the parts of the server that handle
> timestamps aren't careless noobs, so xorg's handling of timestamp rollover
> is going to match the described behavior.
> 
> > Long story short: I don't trust any x documentation.
> 
> That's not an entirely unreasonable stance to have. But, if you can't easily
> test to check whether the documented behavior matches the implemented
> behavior, isn't it more pragmatic to code as if the documented behavior is
> true, and rely on user bug reports (supported by "The implemented behavior
> didn't match the docs!" prints in the code, where practical) to let you know
> when the implementation doesn't match the docs? :)

well I would like to fix it for good and not have to wait for the next bug fix
release + 50 days to figure out whether it worked ;-)

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

[kwin] [Bug 379338] huge memory usage. from 0 to 16Gb in less than 30 seconds

[Martin Gräßlin]

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

Martin Gräßlin <mgraess...@kde.org> changed:

   What|Removed |Added

   Severity|critical|major
  Flags||Wayland+, X11-
  Component|platform-wayland|wayland-generic

--- Comment #1 from Martin Gräßlin <mgraess...@kde.org> ---
Can you try to only run a nested kwin_wayland in an X11 session and check
whether the problem happens there as well. If yes, that would allow to run
valgrind on it. If not we need to look for another solution. Investigating the
startup of the Plasma Wayland session is unfortunately not trivial.

I reduced the importance to major as currently we don't have critical bugs on
Wayland yet.

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

[kwin] [Bug 377901] Window movement breaks after 49 days

[Martin Gräßlin]

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

--- Comment #11 from Martin Gräßlin <mgraess...@kde.org> ---
That is the documentation of Xlib, but KWin uses xcb. Mostly the two libraries
match, but sometimes there are differences. Also a spec is one thing, the other
is how the one and only X-Server behaves. Long story short: I don't trust any x
documentation.

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

[neon] [Bug 379321] New: Downloading Sources is broken

[Martin Gräßlin]

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

Bug ID: 379321
   Summary: Downloading Sources is broken
   Product: neon
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Packages Dev Edition [unstable]
  Assignee: neon-b...@kde.org
  Reporter: mgraess...@kde.org
CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org
  Target Milestone: ---

Get:7 http://archive.neon.kde.org/dev/unstable xenial/main Sources [1.549 kB]   
Err:7 http://archive.neon.kde.org/dev/unstable xenial/main Sources
  Writing more data than expected (1551971 > 1548600)
Fetched 102 kB in 0s (112 kB/s)
Reading package lists... Done
E: Failed to fetch
http://archive.neon.kde.org/dev/unstable/dists/xenial/main/source/Sources 
Writing more data than expected (1551971 > 1548600)

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

[kwin] [Bug 379310] Special application settings not applied for Spotify on startup

[Martin Gräßlin]

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

Martin Gräßlin <mgraess...@kde.org> changed:

   What|Removed |Added

 Resolution|--- |INVALID
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Martin Gräßlin <mgraess...@kde.org> ---
I'm sorry. Spotify is based on the weird chromium embedding thingy.
Unfortunately that one is not ICCCM compliant. Our window rules can only
operate with ICCCM compliant windows due to that they are not working for
Spotify (and similar applications). We cannot change our code here, because we
are also expected to be ICCCM compliant and changing this would result in bugs
in other areas.

You are not the first to report this issue.

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

[kwin] [Bug 377901] Window movement breaks after 49 days

[Martin Gräßlin]

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

--- Comment #9 from Martin Gräßlin <mgraess...@kde.org> ---
Some additional investigation results: both moving windows and Alt+Tab require
a keyboard/pointer grab. The xTime() is going into those requests and the
documentation says:

"The request fails with status InvalidTime if the specified time is earlier
than the last-pointer-grab time or later than the current server time.
Otherwise, the last-pointer-grab time is set to the specified time, with
CurrentTime replaced by the current server time."

If we don't update the xTime any more due to overflow we are in the situation
that our specified time is "later than current server time". On the other hand
if we pass the new wrapped around number we fall into the condition that
"specified time is earlier than the last-pointer-grab time".

To illustrate: let's assume the last-pointer-grab time is 2^32, Now we
increment by 1 and will have a server time of 0. If we send in 0 it is earlier
than the last-pointer-grab time. On the other hand if we send in our last state
from updating X time we are later than the server time.

To a certain degree this is broken in the X11 specification and if the X-Server
behaves exactly like described in the spec we won't be able to fix it. KWin
cannot use the CurrentTime check as we need to be explicit in the time we
request, or we would run into other bugs. So currently what I see is that we
need to relax our conditions in order to get the grab still working, but window
management will probably still be broken, till some other application requests
a pointer grab with 0.

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

[kwin] [Bug 377901] Window movement breaks after 49 days

[Martin Gräßlin]

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

Martin Gräßlin <mgraess...@kde.org> changed:

   What|Removed |Added

   Severity|normal  |critical
   Priority|NOR |HI
  Component|platform-x11-standalone |core

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

[kwin] [Bug 377901] Window movement breaks after 49 days

[Martin Gräßlin]

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

--- Comment #8 from Martin Gräßlin <mgraess...@kde.org> ---
Relevant commit in KWin is:
commit d95ab94f0a664c09223cf1b6d273da41b1cb625e
Author: Martin Gräßlin <mgraess...@kde.org>
Date:   Thu Feb 19 09:59:21 2015 +0100

Migrate away from QX11Info::appTime

The porting to Qt5 broke the timestamp handling in many areas. A deeper
look into Qt's xcb plugin shows that the appTime handling is not
sufficient for KWin's need. E.g. the time is only updated in response to
a property notify event if it's for a Qt created window, which is hardly
ever the case in KWin. Another example is that key press/release events
never updated the appTime.

As the functionality in Qt is rather trivial we can do the timestamp
handling ourselves. We filter all events anyway and it is slightly faster
as we don't have to go through the QPA interface any more.



This means I need to compare how it was done in Qt 4.

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

[kwin] [Bug 377901] Window movement breaks after 49 days

[Martin Gräßlin]

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

--- Comment #7 from Martin Gräßlin <mgraess...@kde.org> ---
We do have the following code:

void setX11Time(xcb_timestamp_t timestamp) {
if (timestamp > m_x11Time) {
m_x11Time = timestamp;
}
}

this means if the timestamp wraps around we will never update again. And the
x11Time is used for various checks. So this is clearly fishy. I need to check
in our git log why we did the sanity checking here, but I'm sure there is a
good reason for it.

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

[plasma-nm] [Bug 379279] NetworkManager "Ask For Password" Popup Focus

[Martin Gräßlin]

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

Martin Gräßlin <mgraess...@kde.org> changed:

   What|Removed |Added

 CC||mgraess...@kde.org
  Component|core|general
   Assignee|kwin-bugs-n...@kde.org  |jgrul...@redhat.com
Product|kwin|plasma-nm

--- Comment #1 from Martin Gräßlin <mgraess...@kde.org> ---
The dialog which opens need to have proper hints and timestamps to ensure that
KWin grants focus.

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

[kwin] [Bug 377901] Window movement breaks after 49 days

[Martin Gräßlin]

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

--- Comment #5 from Martin Gräßlin <mgraess...@kde.org> ---
Waiting for 49 from a dev running the system in a VM won't really help you. All
we could know then is that we can reproduce it, that info is not worth to wait
two days.

The good information is the 32 bit msec timestamp. Those are used a lot on X11
so it's quite likely that they overflow. I try to investigate where they are
used and what a smaller timestamp might mean. We do have sanity checks there,
maybe they need to be weakened.

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

[kwin] [Bug 378704] [Wayland] {min,max}ize, close buttons do not work on next window

[Martin Gräßlin]

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

Martin Gräßlin <mgraess...@kde.org> changed:

   What|Removed |Added

  Flags||Wayland+
  Component|wayland-generic |input

--- Comment #2 from Martin Gräßlin <mgraess...@kde.org> ---
Sounds like no enter event is sent to the decoration.

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

[kwin] [Bug 378709] [Wayland] keyboard numlock status not always being recognized

[Martin Gräßlin]

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

Martin Gräßlin <mgraess...@kde.org> changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Martin Gräßlin <mgraess...@kde.org> ---
Fixed in master

*** This bug has been marked as a duplicate of bug 377155 ***

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

[kwin] [Bug 377155] [Wayland] Caps Lock does not run on XWayland applications

[Martin Gräßlin]

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

Martin Gräßlin <mgraess...@kde.org> changed:

   What|Removed |Added

 CC||germano.massu...@gmail.com

--- Comment #15 from Martin Gräßlin <mgraess...@kde.org> ---
*** Bug 378709 has been marked as a duplicate of this bug. ***

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

[kwin] [Bug 376155] "Quick tile window to the left/right" de-maximizes the window without tiling as a first action since plasma 5.9.0

[Martin Gräßlin]

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

--- Comment #12 from Martin Gräßlin <mgraess...@kde.org> ---
(In reply to sedrubal from comment #11)
> This bug is still present in fedora and arch.

Of course it is, if it were fixed it would be marked as fixed.

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

[kwin] [Bug 371862] xclipboard_syncer goes crazy when kwin_wayland goes down

[Martin Gräßlin]

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

Martin Gräßlin <mgraess...@kde.org> changed:

   What|Removed |Added

  Flags||Wayland+, X11-,
   ||ReviewRequest+
URL||https://phabricator.kde.org
   ||/D5589

--- Comment #4 from Martin Gräßlin <mgraess...@kde.org> ---
Possible patch at: https://phabricator.kde.org/D5589

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

[kwin] [Bug 373669] Crash on kwin

[Martin Gräßlin]

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

--- Comment #9 from Martin Gräßlin <mgraess...@kde.org> ---
(In reply to Orgad Shaneh from comment #8)
> (In reply to Martin Gräßlin from comment #7)
> > Ok, so there is one script which gets loaded.
> 
> And... is kwin expected to crash when loading scripts?

Obviously not.

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

[kwin] [Bug 377155] [Wayland] Caps Lock does not run on XWayland applications

[Martin Gräßlin]

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

Martin Gräßlin <mgraess...@kde.org> changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/kwi
   ||n/a039c2760f6458059dfc91b03
   ||5a5e03022a31d12

--- Comment #14 from Martin Gräßlin <mgraess...@kde.org> ---
Git commit a039c2760f6458059dfc91b035a5e03022a31d12 by Martin Gräßlin.
Committed on 24/04/2017 at 19:00.
Pushed by graesslin into branch 'master'.

Handle modifier updates in the same sequence as Wayland does

Summary:
Consider the case that capslock gets pressed and released.
In the case of Weston we have a sequence of:
 1. Key press event
 2. Modifier changed event
 3. Key release event
 4. Modifier changed event

KWin however used to send the events in the following sequence:
 1. Modifier changed event (on key press)
 2. Key press event
 3. Modifier changed event (on key release)
 4. Key release event

It looks like Xwayland is not able to properly process the sequence
sent by KWin. And in fact KWin's sequence is wrong as it sends a state
which does not match. We report that the caps lock is pressed in the
modifiers prior to the application getting informed about the key press
of caps lock.

This change aligns KWin's implementation to the behavior of Weston. The
main difference is that when modifiers change Xkb internally caches the
serialized modifier states. And KeyboardInputRedirection just forwards
the modifiers to KWayland::Server::SeatInterface once the processing has
finished. SeatInterface ignores the forwarding if no states changes, so
it is fine to do it that way.

Test Plan:
Not yet tested with an affected Xwayland as I only have 1.18 and the
problem started with 1.19. But verified the sequence of events with
WAYLAND_DEBUG
and caps lock stil working in QtWayland clients and Xwayland 1.18

Reviewers: #kwin, #plasma

Subscribers: plasma-devel, kwin

Tags: #kwin

Differential Revision: https://phabricator.kde.org/D5452

M  +2-0keyboard_input.cpp
M  +21   -9xkb.cpp
M  +11   -0xkb.h

https://commits.kde.org/kwin/a039c2760f6458059dfc91b035a5e03022a31d12

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

[kwin] [Bug 379111] Vertical sync causes flickering on screen capturing

[Martin Gräßlin]

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

--- Comment #3 from Martin Gräßlin <mgraess...@kde.org> ---
Try using OpenGL 2. Also ich you are not using xorg modesettings ddx give it a
try.

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

[kwin] [Bug 379144] [Feature request] Bring back window event sounds

[Martin Gräßlin]

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

Martin Gräßlin <mgraess...@kde.org> changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |WONTFIX

--- Comment #1 from Martin Gräßlin <mgraess...@kde.org> ---
No the ipc is still required. But one can use KWin scripts to emulate the
behavior.

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

[kwin] [Bug 361598] Alt+Tab does not always work when pressing it quickly

[Martin Gräßlin]

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

--- Comment #5 from Martin Gräßlin <mgraess...@kde.org> ---
You could run kwin from a konsole and watch the debug output.

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

[kwin] [Bug 376320] Task switcher themes not working under wayland

[Martin Gräßlin]

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

Martin Gräßlin <mgraess...@kde.org> changed:

   What|Removed |Added

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

--- Comment #5 from Martin Gräßlin <mgraess...@kde.org> ---
This should be fixed in latest KWin master. Relevant commit:
https://cgit.kde.org/kwin.git/commit/?id=ac08c5ac9d4532b2506c76e8b69249b32d365aa3

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

[kwin] [Bug 373514] kwin_wayland crashes after Alt+Tab

[Martin Gräßlin]

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

Martin Gräßlin <mgraess...@kde.org> changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 Status|UNCONFIRMED |NEEDSINFO

--- Comment #5 from Martin Gräßlin <mgraess...@kde.org> ---
Waiting for response for further investigation.

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

[neon] [Bug 379116] New: Failure when updating kate

[Martin Gräßlin]

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

Bug ID: 379116
   Summary: Failure when updating kate
   Product: neon
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Packages Dev Edition [unstable]
  Assignee: neon-b...@kde.org
  Reporter: mgraess...@kde.org
CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org
  Target Milestone: ---

sudo apt full-upgrade
Reading package lists... Done
Building dependency tree   
Reading state information... Done
You might want to run 'apt-get -f install' to correct these.
The following packages have unmet dependencies:
 kate : Depends: kate5-data (>= 4:17.04.0+p16.04+git20170423.0131-0) but
4:17.04.0+p16.04+git20170421.0347-0 is installed
E: Unmet dependencies. Try using -f.


sudo apt-get -f install
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Correcting dependencies...Starting pkgProblemResolver with broken count: 0
Starting 2 pkgProblemResolver with broken count: 0
Done
 Done
Starting pkgProblemResolver with broken count: 0
Starting 2 pkgProblemResolver with broken count: 0
Done
The following additional packages will be installed:
  kate5-data
The following packages will be upgraded:
  kate5-data
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
43 not fully installed or removed.
Need to get 0 B/1.210 kB of archives.
After this operation, 12,3 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
(Reading database ... 323185 files and directories currently installed.)
Preparing to unpack
.../kate5-data_4%3a17.04.0+p16.04+git20170423.0131-0_all.deb ...
Unpacking kate5-data (4:17.04.0+p16.04+git20170423.0131-0) over
(4:17.04.0+p16.04+git20170421.0347-0) ...
dpkg: error processing archive
/var/cache/apt/archives/kate5-data_4%3a17.04.0+p16.04+git20170423.0131-0_all.deb
(--unpack):
 trying to overwrite '/usr/share/locale/nb/LC_MESSAGES/plasma_applet_org.mo',
which is also in package kdeplasma-addons-data
4:5.9.4+p16.04+git20170422.0314-0
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Errors were encountered while processing:

/var/cache/apt/archives/kate5-data_4%3a17.04.0+p16.04+git20170423.0131-0_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

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

[kwin] [Bug 379111] Vertical sync causes flickering on screen capturing

[Martin Gräßlin]

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

--- Comment #1 from Martin Gräßlin <mgraess...@kde.org> ---
Please provide output of
qdbus org.kde.KWin /KWin supportInformation

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

[kwin] [Bug 344326] Buffer objects (VBO, FBO) need remapping after suspend/vt switch with NVIDIA

[Martin Gräßlin]

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

Martin Gräßlin <mgraess...@kde.org> changed:

   What|Removed |Added

   Severity|normal  |crash

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

[kwin] [Bug 344326] Buffer objects (VBO, FBO) need remapping after suspend/vt switch with NVIDIA

[Martin Gräßlin]

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

Martin Gräßlin <mgraess...@kde.org> changed:

   What|Removed |Added

  Component|compositing |scene-opengl

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

[kwin] [Bug 379070] KWin Crash after interacting with tray icon of "Jetbrains Toolbox"

[Martin Gräßlin]

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

Martin Gräßlin <mgraess...@kde.org> changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDSINFO
 Resolution|--- |BACKTRACE

--- Comment #1 from Martin Gräßlin <mgraess...@kde.org> ---
The backtrace is lacking debug symbols. If you are able to reproduce please
install debug packages and attach a new backtrace.

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

[kwin] [Bug 344326] Buffer objects (VBO, FBO) need remapping after suspend/vt switch with NVIDIA

[Martin Gräßlin]

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

Martin Gräßlin <mgraess...@kde.org> changed:

   What|Removed |Added

 CC||jdr...@mailbox.org

--- Comment #158 from Martin Gräßlin <mgraess...@kde.org> ---
*** Bug 379067 has been marked as a duplicate of this bug. ***

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

[kwin] [Bug 379067] Kwin crashes after reawakening from suspend-to-ram

[Martin Gräßlin]

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

Martin Gräßlin <mgraess...@kde.org> changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #1 from Martin Gräßlin <mgraess...@kde.org> ---


*** This bug has been marked as a duplicate of bug 344326 ***

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

[kwin] [Bug 379065] crash crash crash crash

[Martin Gräßlin]

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

Martin Gräßlin <mgraess...@kde.org> changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Martin Gräßlin <mgraess...@kde.org> ---
Please stop reporting this issue. It is a bug in the proprietary Nvidia driver.
We cannot do anything. As a workaround switching to the breeze decoration will
not trigger this problem.

*** This bug has been marked as a duplicate of bug 379048 ***

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

[kwin] [Bug 379048] Duplicate bug report not found

[Martin Gräßlin]

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

--- Comment #5 from Martin Gräßlin <mgraess...@kde.org> ---
*** Bug 379065 has been marked as a duplicate of this bug. ***

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

[kwin] [Bug 378951] regression: can no longer use touchscreen with kwin_x11

[Martin Gräßlin]

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

Martin Gräßlin <mgraess...@kde.org> changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|REOPENED|RESOLVED
  Latest Commit|https://commits.kde.org/kwi |https://commits.kde.org/kwi
   |n/a5735e19b99d21d843252dcb1 |n/eec6afe6f5fef80f519c7afb3
   |2a147d122760371 |3e4fd568d74aab0

--- Comment #8 from Martin Gräßlin <mgraess...@kde.org> ---
Git commit eec6afe6f5fef80f519c7afb33e4fd568d74aab0 by Martin Gräßlin.
Committed on 22/04/2017 at 06:17.
Pushed by graesslin into branch 'master'.

Don't map screenedge approach window if edge is only used for touch

Summary:
Another regression from enabling touch support on X11.
The approach window for pointer input gets unmapped as soon as the mouse
enters the window. This ensures that mouse motion events are not stolen
from other applications. But with the touch events we did not even react
on the enter event if it's not activated for pointer. The result was an
area around the screenedge being blocked for pointer input.

This change only creates and maps the approach window if the edge is
activated for pointer input.

Test Plan:
Activated edges through pointer and touch, reconfigured and tested
motion events

Reviewers: #kwin, #plasma

Subscribers: plasma-devel, kwin

Tags: #kwin

Differential Revision: https://phabricator.kde.org/D5528

M  +15   -1plugins/platforms/x11/standalone/edge.cpp

https://commits.kde.org/kwin/eec6afe6f5fef80f519c7afb33e4fd568d74aab0

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

[Powerdevil] [Bug 378445] kscreenlocker_greet occasionally freezes in malloc in signal handler

[Martin Gräßlin]

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

--- Comment #12 from Martin Gräßlin <mgraess...@kde.org> ---
Assuming the signal handler is the reason the steps to reproduce are:
Let screen lock through idle timeout and during grace period lock the screen
through shortcut

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

[kwin] [Bug 379062] Same bug report as before

[Martin Gräßlin]

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

Martin Gräßlin <mgraess...@kde.org> changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Martin Gräßlin <mgraess...@kde.org> ---


*** This bug has been marked as a duplicate of bug 379048 ***

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

[kwin] [Bug 379048] Duplicate bug report not found

[Martin Gräßlin]

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

--- Comment #4 from Martin Gräßlin <mgraess...@kde.org> ---
*** Bug 379062 has been marked as a duplicate of this bug. ***

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

[Powerdevil] [Bug 378445] kscreenlocker_greet occasionally freezes in malloc in signal handler

[Martin Gräßlin]

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

--- Comment #11 from Martin Gräßlin <mgraess...@kde.org> ---
In the case of sigusr1 it could happen that memory gets allocated from the
signal handler.

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

[kwin] [Bug 379046] It never finds my other reports.

[Martin Gräßlin]

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

Martin Gräßlin <mgraess...@kde.org> changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Martin Gräßlin <mgraess...@kde.org> ---
same

*** This bug has been marked as a duplicate of bug 379048 ***

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

[kwin] [Bug 379048] Duplicate bug report not found

[Martin Gräßlin]

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

--- Comment #3 from Martin Gräßlin <mgraess...@kde.org> ---
*** Bug 379046 has been marked as a duplicate of this bug. ***

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

[kwin] [Bug 379048] Duplicate bug report not found

[Martin Gräßlin]

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

--- Comment #2 from Martin Gräßlin <mgraess...@kde.org> ---
*** Bug 379047 has been marked as a duplicate of this bug. ***

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

[kwin] [Bug 379047] Keeps crashing never finds old reports

[Martin Gräßlin]

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

Martin Gräßlin <mgraess...@kde.org> changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Martin Gräßlin <mgraess...@kde.org> ---
Please do not report the same issue multiple times. That just creates work for
us.

*** This bug has been marked as a duplicate of bug 379048 ***

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

[kwin] [Bug 379048] Duplicate bug report not found

[Martin Gräßlin]

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

Martin Gräßlin <mgraess...@kde.org> changed:

   What|Removed |Added

 Resolution|--- |UPSTREAM
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Martin Gräßlin <mgraess...@kde.org> ---
NVIDIA driver. Nothing we can do.

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

[Powerdevil] [Bug 378445] kscreenlocker_greet occasionally freezes in malloc in signal handler

[Martin Gräßlin]

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

--- Comment #9 from Martin Gräßlin <mgraess...@kde.org> ---
or another explanation could be memory corruption or even defect RAM.

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

[kwin] [Bug 379027] can’t resize or move windows, copy does not work

[Martin Gräßlin]

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

Martin Gräßlin <mgraess...@kde.org> changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |UNMAINTAINED

--- Comment #1 from Martin Gräßlin <mgraess...@kde.org> ---
I'm sorry but version 5.5 is no longer supported and we don't investigate bugs
in it. If you need user support please ask at forum.kde.org

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

[kwin] [Bug 379041] KWin crashes shortly after resume

[Martin Gräßlin]

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

Martin Gräßlin <mgraess...@kde.org> changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |UPSTREAM

--- Comment #1 from Martin Gräßlin <mgraess...@kde.org> ---
Crash is in the proprietary NVIDIA driver. Nothing we can do about that, I'm
sorry.

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

[ktorrent] [Bug 378906] Ktorrent disables automatic screen lock

[Martin Gräßlin]

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

Martin Gräßlin <mgraess...@kde.org> changed:

   What|Removed |Added

 CC|mgraess...@kde.org  |

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

[kwin] [Bug 373669] Crash on kwin

[Martin Gräßlin]

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

--- Comment #7 from Martin Gräßlin <mgraess...@kde.org> ---
Ok, so there is one script which gets loaded.

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

[neon] [Bug 379012] New: kscreenlocker built without seccomp support

[Martin Gräßlin]

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

Bug ID: 379012
   Summary: kscreenlocker built without seccomp support
   Product: neon
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Packages Dev Edition [unstable]
  Assignee: neon-b...@kde.org
  Reporter: mgraess...@kde.org
CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org
  Target Milestone: ---

From
http://build.neon.kde.org/job/xenial_unstable_plasma_kscreenlocker_bin_amd64/70/consoleFull:

04:31:35 -- The following OPTIONAL packages have not been found:
04:31:35 
04:31:35  * Seccomp , The enhanced seccomp library. ,

04:31:35Used for putting the look'n'feel package in the greeter into a
sandbox.
04:31:35 

This is an important security feature which got pre-announced on distributions
mailing list.

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

[kwin] [Bug 378951] regression: can no longer use touchscreen with kwin_x11

[Martin Gräßlin]

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

--- Comment #7 from Martin Gräßlin <mgraess...@kde.org> ---
Next try: https://phabricator.kde.org/D5528

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

[kwin] [Bug 378951] regression: can no longer use touchscreen with kwin_x11

[Martin Gräßlin]

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

Martin Gräßlin <mgraess...@kde.org> changed:

   What|Removed |Added

 Resolution|FIXED   |---
 Ever confirmed|0   |1
 Status|RESOLVED|REOPENED

--- Comment #6 from Martin Gräßlin <mgraess...@kde.org> ---
nope, it's not yet sufficient. The screenedges still block events.

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

[kwin] [Bug 378951] regression: can no longer use touchscreen with kwin_x11

[Martin Gräßlin]

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

Martin Gräßlin <mgraess...@kde.org> changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/kwi
   ||n/a5735e19b99d21d843252dcb1
   ||2a147d122760371
 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #5 from Martin Gräßlin <mgraess...@kde.org> ---
Git commit a5735e19b99d21d843252dcb12a147d122760371 by Martin Gräßlin.
Committed on 20/04/2017 at 15:03.
Pushed by graesslin into branch 'master'.

[platforms/x11] Do not grab touch events

Summary:
Grabbing the touch events seems to cause issues. It seems to also grab
pointer events from touchpad and breaks touch input on other events.

Also testing shows that we don't need it and get touch ownership events
for our screenedge windows reported.

Test Plan: Triggered touch screen edge, normal system usage on X11

Reviewers: #plasma, #kwin

Subscribers: plasma-devel, kwin

Tags: #kwin

Differential Revision: https://phabricator.kde.org/D5520

M  +0-18   plugins/platforms/x11/standalone/xinputintegration.cpp

https://commits.kde.org/kwin/a5735e19b99d21d843252dcb12a147d122760371

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

[kwin] [Bug 372876] Dock widgets cannot be moved

[Martin Gräßlin]

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

Martin Gräßlin <mgraess...@kde.org> changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/kwi
   ||n/9a13743c4988fbf653e20df43
   ||e919e836766d3c8

--- Comment #1 from Martin Gräßlin <mgraess...@kde.org> ---
Git commit 9a13743c4988fbf653e20df43e919e836766d3c8 by Martin Gräßlin.
Committed on 20/04/2017 at 15:02.
Pushed by graesslin into branch 'master'.

Don't update the focused pointer Surface if a button is pressed

Summary:
During pointer motion we already had the condition that an update of
focused pointer surface can only happen when no button is pressed. But
there are more conditions where we try to update the focused pointer even
if a button is pressed. E.g. if the stacking order changes.

This happens when trying to move one of Qt's dock widgets:
 1. Press inside a dock widget
 2. Qt opens another window, which is underneath the cursor
 3. KWin sends pointer leave to parent window
 4. dock widget movement breaks

This change ensures that also this sequence works as expected and the
pointer gets only updated when there are no buttons pressed, no matter
from where we go into the update code path.

Test Plan: Dock widgets in Dolphin can be moved now.

Reviewers: #kwin, #plasma

Subscribers: plasma-devel, kwin

Tags: #kwin

Differential Revision: https://phabricator.kde.org/D5461

M  +58   -0autotests/integration/pointer_input.cpp
M  +1-4input.cpp
M  +11   -0pointer_input.cpp

https://commits.kde.org/kwin/9a13743c4988fbf653e20df43e919e836766d3c8

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

[kwin] [Bug 364483] Wayland : Kwin's "Slide Back" effect does not work.

[Martin Gräßlin]

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

Martin Gräßlin <mgraess...@kde.org> changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution|--- |FIXED
  Latest Commit|http://commits.kde.org/kwin |https://commits.kde.org/kwi
   |/8d4204ac0d1354818987c4b0fa |n/919b497f9020a4be49c66d7e0
   |fcf7abde442626  |7f8a15aced317f0

--- Comment #24 from Martin Gräßlin <mgraess...@kde.org> ---
Git commit 919b497f9020a4be49c66d7e07f8a15aced317f0 by Martin Gräßlin.
Committed on 20/04/2017 at 15:03.
Pushed by graesslin into branch 'master'.

[effects/slideback] Consider windows which do have painting disabled as not
usable

Summary:
On Wayland it can happen that a window is still in the stacking order
although it is not visible. This is mostly the case for Plasma windows.
So far the slideback effect did not ignore those windows and as they are
higher in the stacking order than most other windows it blocked the
effect from working once a Plasma panel element got closed.

This change considers a window which has painting disabled in the
stacking order as not usable and thus filters out all those windows.

Reviewers: #kwin, #plasma

Subscribers: plasma-devel, kwin

Tags: #kwin

Differential Revision: https://phabricator.kde.org/D5462

M  +1-1effects/slideback/slideback.cpp

https://commits.kde.org/kwin/919b497f9020a4be49c66d7e07f8a15aced317f0

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

[kwin] [Bug 378982] Plasma crached after switching theme of window manager

[Martin Gräßlin]

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

Martin Gräßlin <mgraess...@kde.org> changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDSINFO
 Resolution|--- |BACKTRACE

--- Comment #1 from Martin Gräßlin <mgraess...@kde.org> ---
As with every bug report by Arch users the backtrace is completely useless as
it's missing debug symbols.

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

[kwin] [Bug 378951] regression: can no longer use touchscreen with kwin_x11

[Martin Gräßlin]

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

Martin Gräßlin <mgraess...@kde.org> changed:

   What|Removed |Added

URL||https://phabricator.kde.org
   ||/D5520

--- Comment #3 from Martin Gräßlin <mgraess...@kde.org> ---
Possible fix at https://phabricator.kde.org/D5520

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

[kwin] [Bug 373669] Crash on kwin

[Martin Gräßlin]

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

--- Comment #5 from Martin Gräßlin <mgraess...@kde.org> ---
Desktop change OSD activated? It is internally implemented as a script.

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

[kwin] [Bug 373669] Crash on kwin

[Martin Gräßlin]

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

Martin Gräßlin <mgraess...@kde.org> changed:

   What|Removed |Added

  Component|general |scripting

--- Comment #3 from Martin Gräßlin <mgraess...@kde.org> ---
Do you have any scripts installed?

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