[kwin] [Bug 368814] Compositor fails to load desktop effects with OpenGL

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #10 from Martin Gräßlin  ---
and how do you know that Alex is using an NVIDIA driver? We don't have that
information and thus we must assume that it's not the same issue and that you
are hijacking this bug report. Sorry, but that's experience here: just because
it might be related doesn't mean it's related. Especially not if drivers are
involved.

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

[kwin] [Bug 368814] Compositor fails to load desktop effects with OpenGL

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #8 from Martin Gräßlin  ---
@Stuart: you are hijacking a bug report. Alex's issue has nothing to do with
your issue. I'm not going to respond except this pointing of bug report
hijacking.

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

[kwin] [Bug 371573] Move resize window on empty area only works every second time

[Martin Gräßlin via KDE Bugzilla]

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

Martin Gräßlin  changed:

   What|Removed |Added

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

--- Comment #3 from Martin Gräßlin  ---
Possible patch at https://phabricator.kde.org/D3154

>From my testing it works fine except for the following situation:
1. trigger move
2. don't move mouse
3. try to trigger again

weston-terminal has no problem with this situation so that might be a problem
on the client side of the stack.

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

[kwin] [Bug 368814] Compositor fails to load desktop effects with OpenGL

[Martin Gräßlin via KDE Bugzilla]

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

Martin Gräßlin  changed:

   What|Removed |Added

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

--- Comment #5 from Martin Gräßlin  ---
@Stuart: you have a broken driver installation.  The popup comes from Plasma
and not KWin. Overall that looks like a broken driver. Please contact a support
forum on how to fix the driver.

@Alex: still waiting for your glxinfo.

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

[kwin] [Bug 371537] Temporary freeze when showing multiple tray notifications

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #12 from Martin Gräßlin  ---
Yeah it's using the modesettings driver. Good.

If you have the possibility, please ssh into your system and attach gdb to kwin
and try to get a backtrace from when the system freezes.

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

[klipper] [Bug 371504] Flexible Clipboard Item Selection

[Martin Gräßlin via KDE Bugzilla]

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

Martin Gräßlin  changed:

   What|Removed |Added

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

--- Comment #5 from Martin Gräßlin  ---
Sorry, but that doesn't provide any advantage over the features klipper already
has and sounds extremely complicated to me.

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

[krita] [Bug 371568] Krita opens main window and then maximizes it, instead of showing maximized in one go

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #5 from Martin Gräßlin  ---
Ok, found the problematic code:
void KisMainWindow::showEvent(QShowEvent *e)
{
KXmlGuiWindow::showEvent(e);

if (!d->geometryInitialized) {
/**
 * We should move the window only *after* it has been shown on
 * screen, otherwise it will become owned by a wrong screen, which
 * will make positioning of all the child widgets wrong.
 * (see bug https://bugs.kde.org/show_bug.cgi?id=362025)
 *
 * This is actually a bug/feature of Qt 5.5.x and it has been
 * fixed in Qt 5.6.0. So we can avoid this delay on newer versions
 * of Qt.
 */
QTimer::singleShot(1, this, SLOT(initializeGeometry()));
d->geometryInitialized = true;
}
}

Thus we have a show (normal geometry) with the initializeGeometry later. Which
is exactly what I observe in KWin.

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

[kwin] [Bug 340225] registerShortcut is undefined in declarativescript

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #25 from Martin Gräßlin  ---
> if that would be okay?

yes of course. I also want to have the script API fixed. It was just an idea I
got for in addition.

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

[kwin] [Bug 371573] Move resize window on empty area only works every second time

[Martin Gräßlin via KDE Bugzilla]

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

Martin Gräßlin  changed:

   What|Removed |Added

  Component|wayland-generic |input

--- Comment #2 from Martin Gräßlin  ---
I'm able to reproduce also with weston-terminal. The input offset position does
not get updated correctly when the window gets moved. Moving the pointer out of
the window and back in again makes every move trigger the window.

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

[kwin] [Bug 371573] Move resize window on empty area only works every second time

[Martin Gräßlin via KDE Bugzilla]

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

Martin Gräßlin  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

--- Comment #1 from Martin Gräßlin  ---
I guess the release of the button is never sent to the application as KWin
grabs it.

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

[krita] [Bug 371568] Krita opens main window and then maximizes it, instead of showing maximized in one go

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #3 from Martin Gräßlin  ---
> Um, actually, isn't this a Qt bug then?

I'm not excluding the possibility that it's a Qt bug.

> I know of no KDE or Qt application that uses showMaximized() directly

It's a hardly used feature that applications request to open maximized
directly.

> void KisMainWindow::initializeGeometry()

Can you point me to the code for that, then I can go through what it does.

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

[kwin] [Bug 371284] Kwin hinders brush cursor in krita making the window move while painting

[Martin Gräßlin via KDE Bugzilla]

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

Martin Gräßlin  changed:

   What|Removed |Added

  Component|general |core
  Flags||ReviewRequest+
URL||https://phabricator.kde.org
   ||/D3151

--- Comment #25 from Martin Gräßlin  ---
Possible fix at https://phabricator.kde.org/D3151

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

[krita] [Bug 371568] New: Krita opens main window and then maximizes it, instead of showing maximized in one go

[Martin Gräßlin via KDE Bugzilla]

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

Bug ID: 371568
   Summary: Krita opens main window and then maximizes it, instead
of showing maximized in one go
   Product: krita
   Version: 3.0.1.1
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: mgraess...@kde.org

When starting Krita on KWin one can observe that the maximize animation is run.
This means that Krita opens a window and afterwards changes it to maximized. I
confirmed this by adding debug statements into KWin. This is part of the reason
why bug #371284 happens - it hits a condition which normally cannot happen.

Reproducible: Always

Steps to Reproduce:
1. Start Krita on KWin/X11

Actual Results:  
Maximize animation is run

Expected Results:  
Maximize animation is not run, the window opens as maximized directly.

Qt provides API to show a window maximized. E.g. QWindow::showMaximized or
QWidget::showMaximized

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

[kwin] [Bug 371284] Kwin hinders brush cursor in krita making the window move while painting

[Martin Gräßlin via KDE Bugzilla]

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

Martin Gräßlin  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #23 from Martin Gräßlin  ---
I triggered the bug!

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

[krita] [Bug 371561] Appimage aborts when started on Wayland

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #3 from Martin Gräßlin  ---
are you sure the commit is correct. I just checked it in context and the other
usages of HAVE_X11 is a #if defined HAVE_X11. I might have got that wrong,
because in frameworks/Plasma we define HAVE_X11 to 0 or 1.

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

[krita] [Bug 371561] New: Appimage aborts when started on Wayland

[Martin Gräßlin via KDE Bugzilla]

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

Bug ID: 371561
   Summary: Appimage aborts when started on Wayland
   Product: krita
   Version: 3.0.1.1
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: mgraess...@kde.org

When trying to start Krita (appimage) on Plasma Wayland the application aborts
and doesn't start:

./krita-3.0.1.1-x86_64.appimage 
QCoreApplication::arguments: Please instantiate the QApplication object first
krita.lib.pigment: Compiled for arch: 7
krita.lib.pigment: Features supported:
krita.lib.pigment:   "SSE2" ---  yes
krita.lib.pigment:   "SSSE3"---  yes
krita.lib.pigment:   "SSE4.1"   ---  yes
krita.lib.pigment:   "AVX " ---  yes
krita.lib.pigment:   "AVX2 "---  yes
This application failed to start because it could not find or load the Qt
platform plugin "wayland"
in "".

Available platform plugins are: minimal, offscreen, xcb.

Reinstalling the application may fix this problem.
Aborted (core dumped)



Reproducible: Always

Steps to Reproduce:
1. Start a Plasma/Wayland session
2. Download Krita appimage
3. Try to run the appimage

Actual Results:  
Abort

Expected Results:  
Starts

It looks to me like the appimage has Qt bundled but does not include QtWayland.
That's fine, at the moment Krita wouldn't run on Wayland anyway due to missing
tablet support in Qt. Given that I suggest to add the following to Krita prior
to instancing the QApplication:

#if HAVE_X11
qputenv("QT_QPA_PLATFORM", "xcb");
#endif

This will ensure that the appimage doesn't crash on Wayland.

Please note that the next Fedora Workstation release will default to Wayland. I
highly recommend to fix this issue prior to Fedora release.

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

[kwin] [Bug 371537] Temporary freeze when showing multiple tray notifications

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #9 from Martin Gräßlin  ---
xorg.0.log should tell you which driver you are using. If it says something
like "LoadModule: intel" then you are on intel.

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

[kwin] [Bug 371537] Temporary freeze when showing multiple tray notifications

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #7 from Martin Gräßlin  ---
are you using the intel xorg driver or the modesettings xorg driver? Can you
check in dmesg whether you see anything related to the freeze (e.g. hung gpu)?
Can you check in /var/log/Xorg.0.log for any errors which might be related.

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

[Plasma SDK] [Bug 371554] uninstall/upgrade options of plasmapkg2 don't work for kwinscripts

[Martin Gräßlin via KDE Bugzilla]

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

Martin Gräßlin  changed:

   What|Removed |Added

Product|kwin|Plasma SDK
   Assignee|kwin-bugs-n...@kde.org  |plasma-b...@kde.org
Version|git master  |5.8.2
  Component|scripting   |General
 CC||antonis.tsiapalio...@kde.or
   ||g

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

[kwin] [Bug 371537] Temporary freeze when showing multiple tray notifications

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #4 from Martin Gräßlin  ---
What I don't really understand from your bug report: is plasma freezing or
KWin? Is it a problem of just the rendering of the notifications or is e.g.
glxgears no longer updated as well? Can you still move the mouse cursor while
the freeze happens?

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

[kwin] [Bug 340225] registerShortcut is undefined in declarativescript

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #23 from Martin Gräßlin  ---
An idea what could be done in addition. We could provide a declarative way to
export the shortcuts:
GlobalShortcut {
shortcut: "Ctrl+Alt+1"
onTriggered: console.log("triggered")
}

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

[klipper] [Bug 371504] Flexible Clipboard Item Selection

[Martin Gräßlin via KDE Bugzilla]

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

Martin Gräßlin  changed:

   What|Removed |Added

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

--- Comment #3 from Martin Gräßlin  ---
Sorry, but the clipboard doesn't work the way you think it works. In general
one doesn't know when something gets pasted. On X11 an application sets the
clipboard content and another application reads it - the setting application
doesn't know that it got read. This makes your use case impossible.

On Wayland clipboard works different by being a direct communication between
the pasting and providing application. There one could say the copying client
is informed, but in fact it isn't. Because the pasting client takes a copy of
the data and on next paste it uses the already retrieved data. Overall your
idea is just impossible to implement with the two platforms we have.

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

[kwin] [Bug 351116] Titlebar font should be editable from WM settings

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #13 from Martin Gräßlin  ---
Am 23. Oktober 2016 21:00:20 MESZ, schrieb Tsu Jan via KDE Bugzilla
:
>https://bugs.kde.org/show_bug.cgi?id=351116
>
>Tsu Jan  changed:
>
>   What|Removed |Added
>
> CC||tsujan2...@gmail.com
>
>--- Comment #12 from Tsu Jan  ---
>Technical problems aside, since kwin works well outside KDE too, it's
>logical
>to expect a separate titlebar font setting for it.

Please note that the setting modules KWin provides are technically Plasma
specific. In fact other desktops would need to provide a different way to
configure KWin without requiring kcmshell5.

So overall that's really outside the scope of KWin

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

[kwin] [Bug 340225] registerShortcut is undefined in declarativescript

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #18 from Martin Gräßlin  ---
Am 23. Oktober 2016 18:14:34 MESZ, schrieb via KDE Bugzilla
:
>https://bugs.kde.org/show_bug.cgi?id=340225
>
>--- Comment #17 from kdeb...@chilon.net ---
>I've written the code for it but the code necessary to handle calling a
>declarative js function from C++ seems a bit complicated. I'm trying to
>find
>another example in the KDE code so I can simplify this.

Have a look at JSEngineGlobalMethodsWrapper. Any slot in this class is exported
in the object KWin in declarative scripts. That's different to the normal
scripts, but iirc I introduced this class as a solution to the problem that we
cannot export method globally

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

[kwin] [Bug 371537] Temporary freeze when showing multiple tray notifications

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #2 from Martin Gräßlin  ---
Please provide output of:
 qdbus org.kde.KWin /KWin supportInformation

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

[frameworks-kwayland] [Bug 371527] Ctrl + [key] standard shortcuts don't work in plasma wayland session (kwrite, dolphin, systemsettings etc.)

[Martin Gräßlin via KDE Bugzilla]

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

Martin Gräßlin  changed:

   What|Removed |Added

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

--- Comment #2 from Martin Gräßlin  ---
This is a bug in QtWayland 5.7.0 which breaks all shortcuts with the Control
modifier: https://bugreports.qt.io/browse/QTBUG-54367

It will be resolved with QtWayland 5.7.1. Please ask your distribution to
backport the patch to 5.7.0 - they know which commit it is.

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

[kwin] [Bug 371502] Task switcher (task manager) only allows to switch between two windows of application

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #4 from Martin Gräßlin  ---
which Keyboard layout are you using?

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 371494] Support color temperature adjustments in Wayland (like Redshift in X11 or f.lux)

[Martin Gräßlin via KDE Bugzilla]

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

Martin Gräßlin  changed:

   What|Removed |Added

   Assignee|cas...@candrei.ro   |kwin-bugs-n...@kde.org
  Component|colorcorrection |platform-drm

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

[kwin] [Bug 371048] kwin_wayland crash at session login

[Martin Gräßlin via KDE Bugzilla]

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

Martin Gräßlin  changed:

   What|Removed |Added

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

--- Comment #7 from Martin Gräßlin  ---
Thanks for the update

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

[kwin] [Bug 371508] Desktop Cube Animation doesn't work

[Martin Gräßlin via KDE Bugzilla]

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

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

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

[klipper] [Bug 371504] Flexible Clipboard Item Selection

[Martin Gräßlin via KDE Bugzilla]

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

Martin Gräßlin  changed:

   What|Removed |Added

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

--- Comment #1 from Martin Gräßlin  ---
I'm sorry, but this feature request doesn't make sense. One can only have one
entry in the clipboard which makes selecting multiple entries rather pointless.
That's a technical limitation of the concept of the clipboard: there can only
be one entry in the clipboard.

Now having multiple entries to select from (a history) is exactly what Klipper
provides.  You click an entry in the history and that's the one which is going
to be pasted. This sounds from the functionality exactly as what you requested.
I also encourage you to explore the options and the global shortcuts for the
clipboard. There are global shortcuts to pop up the history and to navigate
through the history.

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

[kwin] [Bug 371480] SDL2 Apps causing desktop effects to disappear, task-manager function weirdly, all desktop widgets to disappear and sometimes kwin to crash

[Martin Gräßlin via KDE Bugzilla]

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

Martin Gräßlin  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |WORKSFORME

--- Comment #1 from Martin Gräßlin  ---
This is expected behavior. SDL sets a hint to disable the compositor for better
performance and KWin honors this. With Plasma 5.8 we introduced a GUI config
option where you can disable this behavior in general.

With Plasma 5.7 you can already create a window specific rule to disallow
"Block Compositing". Create a rule for the window and select "Force" "No". That
will ensure that the compositing does not get disabled.

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

[plasmashell] [Bug 356175] [wayland] plasmashell crashes at startup

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #22 from Martin Gräßlin  ---
(In reply to Lóránt Farkas from comment #21)
> Created attachment 101692 [details]
> kstart5 plasmashell backtrace

That's a crash of kstart5 - please report a new bug for that one.

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

[kwin] [Bug 371406] Modifier to constrain mouse pointer to the current desktop

[Martin Gräßlin via KDE Bugzilla]

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

Martin Gräßlin  changed:

   What|Removed |Added

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

--- Comment #1 from Martin Gräßlin  ---
Sorry KWin is the wrong layer for such a feature. That belongs into X server.
KWin cannot control the pointer motion.

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

[kwin] [Bug 371284] Kwin hinders brush cursor in krita making the window move while painting

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #22 from Martin Gräßlin  ---
Some investigation results: if one removes the window decoration the problem is
not triggered. Krita starts as a normal window and directly maximizes. This
might cause a problem with the decoration not having a correct geometry and
then accepting events.

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

[kwin] [Bug 371399] [Wayland] Firefox either hangs my desktop or crashes the session.

[Martin Gräßlin via KDE Bugzilla]

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

Martin Gräßlin  changed:

   What|Removed |Added

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

--- Comment #3 from Martin Gräßlin  ---
We need the backtrace, without we cannot do much :-(

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

[kwin] [Bug 371284] Kwin hinders brush cursor in krita making the window move while painting

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #21 from Martin Gräßlin  ---
I have now installed krtia on my system and are (of course) not able to
reproduce the problem. When using the wacom tablet the cursor never turns into
a mouse cursor. In fact I cannot leave the drawing area at all while drawing.
Which I think is what is expected.

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

[kwin] [Bug 371399] [Wayland] Firefox either hangs my desktop or crashes the session.

[Martin Gräßlin via KDE Bugzilla]

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

Martin Gräßlin  changed:

   What|Removed |Added

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

--- Comment #1 from Martin Gräßlin  ---
Firefox is working fine for me (just typing in it). This might be a nouveau
problem.

What we need is a way to gdb into kwin. In case you have a second system,
please try to ssh into the system, attach gdb and get a backtrace.

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

[kwin] [Bug 371048] kwin_wayland crash at session login

[Martin Gräßlin via KDE Bugzilla]

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

Martin Gräßlin  changed:

   What|Removed |Added

  Component|platform-wayland|wayland-generic
 Status|NEEDSINFO   |UNCONFIRMED
 Resolution|BACKTRACE   |---

--- Comment #5 from Martin Gräßlin  ---
reopening to investigate the XInternAtom usage

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

[kwin] [Bug 371397] kwin crashed after login

[Martin Gräßlin via KDE Bugzilla]

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

Martin Gräßlin  changed:

   What|Removed |Added

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

--- Comment #1 from Martin Gräßlin  ---
Unfortunately the backtrace lacks debug symbols. Due to that we only see that
it crashed (in Qt) but don't know which code caused it. Please install debug
symbols for KWin and Qt and attach a new backtrace.

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

[kwin] [Bug 371384] Mouse Cursor de-scales on window chrome (on window edges)

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #1 from Martin Gräßlin  ---
@David: is display scale in Qt playing into the cursor size? If yes we need to
make sure that KWin also uses that.

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

[kwin] [Bug 371048] kwin_wayland crash at session login

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #4 from Martin Gräßlin  ---
hmm the core doesn't give me anything useful.

What is interesting is the: XInternAtom

KWin code does not have any XInternAtom call anymore which means that was from
a library or plugin that kwin loads. Any third party widget style or window
decoration?

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

[kwin] [Bug 371284] Kwin hinders brush cursor in krita making the window move while painting

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #20 from Martin Gräßlin  ---
I don't see any key press/release or pointer events there. Shot in the blue.
Please restart KWin with the following command:

KWIN_NO_XI2=1 kwin_x11 --replace &

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

[kwin] [Bug 371284] Kwin hinders brush cursor in krita making the window move while painting

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #16 from Martin Gräßlin  ---
Thanks, I expected to see:
ClientMessage event, serial 21, synthetic YES, window 0x305,
message_type 0x132 (_NET_WM_MOVERESIZE), format 32

which is not there. That means KWin does trigger the move. But why? There are
three different ways how KWin could trigger the move itself:
1. Right click window decoration -> More Actions -> Move
2. Click window decoration
3. Modifier+click anywhere on the window

Given the videos we can clearly rule out option 1. So somehow we go into
possibility 2 or 3. First thing: could it be that your tool triggers the meta
key? I have heard that some tablets do that. To rule out please change the
setting back to Alt.

For the possibility 2: please use xev again but slightly different. Use
xwininfo, click on krita. That will give you a window id. Now pass that to xev
with:
xev -id 

This will record all motion events. Thus we should hopefully be able to
reconstruct where the actual mouse events are, whether they go into the window
decoration, but we just don't see it.

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

[kwin] [Bug 371284] Kwin hinders brush cursor in krita making the window move while painting

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #13 from Martin Gräßlin  ---
Thanks for the updated video, looks like it is KWin which is moving the window.
I have absolutely no idea how that can happen. KWin itself only triggers the
window moving when you interact with the decoration, but that's not what you
are doing. So something must be triggering the window move and normally that
would come from the application.

Could you please run:
xev -root > xev.out

Trigger the problem, terminate xev and attach the output. This records all X
events, so please don't type to not get any sensitive data in.

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

[kwin] [Bug 371323] Add GUI configuration option to disable/edit ModifierOnlyShortcuts

[Martin Gräßlin via KDE Bugzilla]

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

Martin Gräßlin  changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution|--- |WONTFIX

--- Comment #3 from Martin Gräßlin  ---
sorry gui is currently not planed. We cannot merge it together with "normal"
global shortcuts as they are implemented technically different. At the moment
we don't plan to add a gui for it. We think it's not needed.

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

[kwin] [Bug 371323] Add configuration option to disable/edit ModifierOnlyShortcuts

[Martin Gräßlin via KDE Bugzilla]

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

Martin Gräßlin  changed:

   What|Removed |Added

   Severity|normal  |wishlist
 Resolution|--- |WORKSFORME
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Martin Gräßlin  ---
This is configurable as shown in the link. To reiterate:

open ~/.config/kwinrc in a text editor, add the following:
[ModifierOnlyShortcuts]
Meta=

--
At the moment we do not have any plans to expose this through a GUI interface.

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

[kwin] [Bug 371284] Kwin hinders brush cursor in krita making the window move while painting

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #9 from Martin Gräßlin  ---
(In reply to Boudewijn Rempt from comment #5)
> The default style for Krita is Fusion, and it's in fact really hard to use
> Breeze or Oxygen because both of those styles are too broken to be used, at
> least in the versions currently shipped by distributions
@boud: can we please get this fixed? Having a consistent look and feel is very
important for us and Krita is a very important application for our ecosystem.
Let's try to work together and prioritize any issues in breeze and oxygen and
also get all distributions to ship the fixes. We can do that!

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

[kwin] [Bug 371284] Kwin hinders brush cursor in krita making the window move while painting

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #8 from Martin Gräßlin  ---
Also could you please switch to the default breeze cursor theme and rerecord
the video? The "drag" cursor icon is confusing to me as KWin doesn't use it. I
need to see the which cursor icon is used during the drag to evaluate whether
that's actually KWin moving the window.

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

[kwin] [Bug 371284] Kwin hinders brush cursor in krita making the window move while painting

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #7 from Martin Gräßlin  ---
Are you pressing the Alt key anywhen during interacting with the window?

Could you 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 371284] Kwin hinders brush cursor in krita making the window move while painting

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #3 from Martin Gräßlin  ---
It looks a lot like the widget style is triggering a window move. This is
something that breeze and oxygen do. The explanation for openbox not triggering
it would be that this window manager doesn't support the respective hint.

If that's the case we need to bounce the bug back to krita as they need to
properly mark the widget as interactive.

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

[kwin] [Bug 371284] Kwin hinders brush cursor in krita making the window move while painting

[Martin Gräßlin via KDE Bugzilla]

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

Martin Gräßlin  changed:

   What|Removed |Added

  Component|libinput|general

--- Comment #2 from Martin Gräßlin  ---
Which window/widget style are you using? I cannot properly recognize in the
video.

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

[kwin] [Bug 370917] KWin is putting newly opened windows on random screen

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #9 from Martin Gräßlin  ---
Interesting it does not provide a position hint - kwin should have positioned
it.

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

[kwin] [Bug 371229] Drag starts on window below if window dragged on closes while dragging

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #1 from Martin Gräßlin  ---
That's on X11 or Wayland?

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

[dolphin] [Bug 371223] New: Tooltips non functional on Wayland

[Martin Gräßlin via KDE Bugzilla]

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

Bug ID: 371223
   Summary: Tooltips non functional on Wayland
   Product: dolphin
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: view-engine: tooltip
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: mgraess...@kde.org

On Wayland the tooltips do not work. The tooltip window shows for a very short
moment and then gets dismissed again.

Reproducible: Always

Steps to Reproduce:
1. Use Wayland
2. Enable tooltips
3. Hover a folder

Actual Results:  
A window flashes up for a short moment somewhere on the screen

Expected Results:  
Tooltip

This might be related to a related issue in systemsettings which is addressed
by https://phabricator.kde.org/D3112

The tooltip window lacks the transientParent QWindow which is required on
Wayland (and actually also on X11) to have the correct relationship. On Wayland
tooltips are positioned in relation to their transient parent window.

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

[kwin] [Bug 368814] Compositor fails to load desktop effects with OpenGL

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #2 from Martin Gräßlin  ---
Please provide output of glxinfo

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

[frameworks-kwayland] [Bug 371213] Implement xdg_shell_v6 support

[Martin Gräßlin via KDE Bugzilla]

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

Martin Gräßlin  changed:

   What|Removed |Added

Version|5.8.2   |5.27.0
Product|kwin|frameworks-kwayland
   Severity|normal  |wishlist
   Assignee|kwin-bugs-n...@kde.org  |mgraess...@kde.org
  Component|wayland-generic |server

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

[plasmashell] [Bug 368885] The plasma panel has no shadow on Wayland

[Martin Gräßlin via KDE Bugzilla]

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

Martin Gräßlin  changed:

   What|Removed |Added

  Latest Commit||http://commits.kde.org/plas
   ||ma-workspace/59733c21a4bb0d
   ||04bb76367995aa611e66f5f3e5
 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

--- Comment #4 from Martin Gräßlin  ---
Git commit 59733c21a4bb0d04bb76367995aa611e66f5f3e5 by Martin Gräßlin.
Committed on 19/10/2016 at 11:04.
Pushed by graesslin into branch 'master'.

[shell] Create panelshadow in surfacecreated event instead of show event

Summary:
In the show event the Wayland implementation does not pick up the shadow
at all.

Test Plan: Shadow on Wayland, not tested on X11

Reviewers: #plasma, mart

Subscribers: plasma-devel

Tags: #plasma

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

M  +1-1shell/panelview.cpp

http://commits.kde.org/plasma-workspace/59733c21a4bb0d04bb76367995aa611e66f5f3e5

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

[kwin] [Bug 340225] registerShortcut is undefined in declarativescript

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #15 from Martin Gräßlin  ---
> we need this for kwin-tiling

why does kwin-tiling need the declarative script? Does it do any user
interface? If not it should use the qscript based scripting where this is still
available.

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

[kwin] [Bug 340225] registerShortcut is undefined in declarativescript

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #14 from Martin Gräßlin  ---
if you have any specific questions please ask. I thought that this would be
sufficient as a starter.

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

[plasmashell] [Bug 368885] The plasma panel has no shadow on Wayland

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #3 from Martin Gräßlin  ---
Possible patch at https://phabricator.kde.org/D3109

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

[kactivitymanagerd] [Bug 371204] Activity gets ignored after restart

[Martin Gräßlin via KDE Bugzilla]

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

Martin Gräßlin  changed:

   What|Removed |Added

 CC||plasma-b...@kde.org
Product|kwin|kactivitymanagerd
   Assignee|kwin-bugs-n...@kde.org  |ivan.cu...@kde.org
  Component|activities  |general

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

[kwin] [Bug 371199] Dragging windows on my left screen causes them to jump down to the bottom

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #4 from Martin Gräßlin  ---
Thanks for testing! Now we know where the problem is.

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

[kwin] [Bug 371199] Dragging windows on my left screen causes them to jump down to the bottom

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #2 from Martin Gräßlin  ---
can you try removing the panel between your screens?

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

[kwin] [Bug 371199] Dragging windows on my left screen causes them to jump down to the bottom

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #1 from Martin Gräßlin  ---
KWin Support Information:
The following information should be used when requesting support on e.g.
http://forum.kde.org.
It provides information about the currently running instance, which options are
used,
what OpenGL driver and which effects are running.
Please post the information provided underneath this introductory text to a
paste bin service
like http://paste.kde.org instead of pasting into support threads.

==

Version
===
KWin version: 5.8.1
Qt Version: 5.7.0
Qt compile version: 5.7.0
XCB compile version: 1.12

Operation Mode: X11 only

Build Options
=
KWIN_BUILD_DECORATIONS: yes
KWIN_BUILD_TABBOX: yes
KWIN_BUILD_ACTIVITIES: yes
HAVE_INPUT: yes
HAVE_DRM: yes
HAVE_GBM: yes
HAVE_X11_XCB: yes
HAVE_EPOXY_GLX: yes
HAVE_WAYLAND_EGL: yes

X11
===
Vendor: The X.Org Foundation
Vendor Release: 11804000
Protocol Version/Revision: 11/0
SHAPE: yes; Version: 0x11
RANDR: yes; Version: 0x14
DAMAGE: yes; Version: 0x11
Composite: yes; Version: 0x4
RENDER: yes; Version: 0xb
XFIXES: yes; Version: 0x50
SYNC: yes; Version: 0x31
GLX: yes; Version: 0x0

Decoration
==
Plugin: org.kde.breeze
Theme: 
Blur: 0
onAllDesktopsAvailable: false
alphaChannelSupported: true
closeOnDoubleClickOnMenu: false
decorationButtonsLeft: 0, 2
decorationButtonsRight: 6, 3, 4, 5
borderSize: 3
gridUnit: 10
font: Noto Sans,10,-1,5,50,0,0,0,0,0
smallSpacing: 2
largeSpacing: 10

Options
===
focusPolicy: 0
nextFocusPrefersMouse: false
clickRaise: true
autoRaise: false
autoRaiseInterval: 0
delayFocusInterval: 0
shadeHover: false
shadeHoverInterval: 250
separateScreenFocus: false
placement: 4
focusPolicyIsReasonable: true
borderSnapZone: 10
windowSnapZone: 10
centerSnapZone: 0
snapOnlyWhenOverlapping: false
rollOverDesktops: true
focusStealingPreventionLevel: 1
legacyFullscreenSupport: false
operationTitlebarDblClick: 5000
operationMaxButtonLeftClick: 5000
operationMaxButtonMiddleClick: 5015
operationMaxButtonRightClick: 5014
commandActiveTitlebar1: 0
commandActiveTitlebar2: 30
commandActiveTitlebar3: 2
commandInactiveTitlebar1: 4
commandInactiveTitlebar2: 30
commandInactiveTitlebar3: 2
commandWindow1: 7
commandWindow2: 8
commandWindow3: 8
commandWindowWheel: 31
commandAll1: 10
commandAll2: 3
commandAll3: 14
keyCmdAllModKey: 16777251
showGeometryTip: true
condensedTitle: false
electricBorderMaximize: true
electricBorderTiling: true
electricBorderCornerRatio: 0.25
borderlessMaximizedWindows: false
killPingTimeout: 5000
hideUtilityWindowsForInactive: true
inactiveTabsSkipTaskbar: false
autogroupSimilarWindows: false
autogroupInForeground: true
compositingMode: 1
useCompositing: true
compositingInitialized: true
hiddenPreviews: 2
glSmoothScale: 2
colorCorrected: false
xrenderSmoothScale: false
maxFpsInterval: 1666
refreshRate: 0
vBlankTime: 600
glStrictBinding: false
glStrictBindingFollowsDriver: true
glCoreProfile: true
glPreferBufferSwap: 0
glPlatformInterface: 1
windowsBlockCompositing: true

Screen Edges

desktopSwitching: false
desktopSwitchingMovingClients: false
cursorPushBackDistance: 1x1
timeThreshold: 150
reActivateThreshold: 350
actionTopLeft: 0
actionTop: 0
actionTopRight: 0
actionRight: 0
actionBottomRight: 0
actionBottom: 0
actionBottomLeft: 0
actionLeft: 0

Screens
===
Multi-Head: no
Active screen follows mouse:  no
Number of Screens: 2

Screen 0:
-
Name: DVI-I-0
Geometry: 0,0,1920x1080
Refresh Rate: 60

Screen 1:
-
Name: DVI-D-0
Geometry: 1920,0,1920x1080
Refresh Rate: 60


Compositing
===
Compositing is active
Compositing Type: OpenGL
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce GTX 970/PCIe/SSE2
OpenGL version string: 3.1.0 NVIDIA 370.28
OpenGL platform interface: GLX
OpenGL shading language version string: 1.40 NVIDIA via Cg compiler
Driver: NVIDIA
Driver version: 370.28
GPU class: Unknown
OpenGL version: 3.1
GLSL version: 1.40
X server version: 1.18.4
Linux kernel version: 4.7.7
Direct rendering: Requires strict binding: no
GLSL shaders:  yes
Texture NPOT support:  yes
Virtual Machine:  no
OpenGL 2 Shaders are used
Painting blocks for vertical retrace:  no

Loaded Effects:
---
zoom
slidingpopups
kwin4_effect_login
wobblywindows
slide
screenshot
kwin4_effect_windowaperture
kwin4_effect_translucency
minimizeanimation
cube
sheet
resize
kwin4_effect_morphingpopups
kwin4_effect_maximize
kwin4_effect_fade
presentwindows
highlightwindow
kwin4_effect_dialogparent
blur
contrast
windowgeometry
startupfeedback
screenedge
kscreen

Currently Active Effects:
-
blur
contrast

Effect Settings:

zoom:
zoomFactor: 1.2
mousePointer: 0
mouseTracking: 0
enableFocusTracking: false
followFocus: true
focusDelay: 350
moveFactor: 20
targetZoom: 1

slidingpopups:
fadeInTime: 30
fadeOutTime: 50

kwin4_effect_login:

wobblywindows:
stiffness: 0.06
drag: 0.9
moveFactor: 0.1

[kwin] [Bug 370917] KWin is putting newly opened windows on random screen

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #7 from Martin Gräßlin  ---
please also xprop

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

[kwin] [Bug 370985] Chrome doesn't show its own minimize/maximize/close buttons when maximized

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #6 from Martin Gräßlin  ---
> But I can have libunity installed and it still works with IceWM!

Start icewm in a Plasma session and chrome won't have it. It's a DBus protocol
Chrome interacts with through libunity.

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

[kscreenlocker] [Bug 369137] Screen will not lock when switching virtual terminal

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #2 from Martin Gräßlin  ---
Just tried how this behaves on Wayland: there we get the screen locked, but
rendering breaks completely. It means that KIdleTime doesn't fire if not on the
current vt on X11. Doesn't surprise me really.

I don't really know what we can do about it. If X does not notify us, it
doesn't notify us. Not much we can do about it.

What could be done is adding a new option whether to lock the screen when
switching vts.

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

[kwin] [Bug 366609] Context menu do not close when discarded on Wayland

[Martin Gräßlin via KDE Bugzilla]

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

Martin Gräßlin  changed:

   What|Removed |Added

 CC||itl964@gmail.com

--- Comment #3 from Martin Gräßlin  ---
*** Bug 370926 has been marked as a duplicate of this bug. ***

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

[plasmashell] [Bug 370926] Panel right click menus don't go away under wayland

[Martin Gräßlin via KDE Bugzilla]

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

Martin Gräßlin  changed:

   What|Removed |Added

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

--- Comment #1 from Martin Gräßlin  ---
Same as bug #366609 on kwin: reason is lack of popup window support in KWin

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

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

[plasmashell] [Bug 365109] Konversation doesn't raise on Wayland

[Martin Gräßlin via KDE Bugzilla]

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

Martin Gräßlin  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|CONFIRMED   |RESOLVED

--- Comment #3 from Martin Gräßlin  ---
Same as bug #370338 which is the generic one for KWin.

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

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

[kwin] [Bug 370338] Reopening System Settings doesn't raise it or give focus

[Martin Gräßlin via KDE Bugzilla]

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

Martin Gräßlin  changed:

   What|Removed |Added

 CC||aleix...@kde.org

--- Comment #2 from Martin Gräßlin  ---
*** Bug 365109 has been marked as a duplicate of this bug. ***

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

[plasmashell] [Bug 369386] [Wayland] Panel "Auto-hide" option does not work.

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #6 from Martin Gräßlin  ---
Step 2: https://phabricator.kde.org/D3080
Step 3: https://phabricator.kde.org/D3084

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

[plasmashell] [Bug 369867] Widget searching stopped working on Wayland session.

[Martin Gräßlin via KDE Bugzilla]

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

Martin Gräßlin  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED

--- Comment #5 from Martin Gräßlin  ---
All patches are pushed.

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

[kwin] [Bug 370158] Krunner on Wayland can only be opened on the first desktop

[Martin Gräßlin via KDE Bugzilla]

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

Martin Gräßlin  changed:

   What|Removed |Added

  Latest Commit||http://commits.kde.org/plas
   ||ma-workspace/9abb8102128893
   ||41ef1c8c00ab1c940d14846cd8
 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED

--- Comment #7 from Martin Gräßlin  ---
Git commit 9abb810212889341ef1c8c00ab1c940d14846cd8 by Martin Gräßlin.
Committed on 18/10/2016 at 06:16.
Pushed by graesslin into branch 'master'.

[krunner] Make KRunner on Wayland a Panel

Summary:
Panel is the best matching type which gives us the required behavior
like being on all desktops.

Reviewers: #plasma, broulik

Subscribers: plasma-devel

Tags: #plasma

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

M  +3-0krunner/view.cpp

http://commits.kde.org/plasma-workspace/9abb810212889341ef1c8c00ab1c940d14846cd8

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

[plasmashell] [Bug 364529] Wayland : No title in Task manager for Systemsettings

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #7 from Martin Gräßlin  ---
> Using yesterday's Neon wayland spin. Should I open a new bug?

Title is bug #370333 - it should be fixed, but I'm not sure whether the fix is
already in the iso.

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

[kwin] [Bug 371048] kwin_wayland crash at session login

[Martin Gräßlin via KDE Bugzilla]

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

Martin Gräßlin  changed:

   What|Removed |Added

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

--- Comment #1 from Martin Gräßlin  ---
Please provide a backtrace of the crash. Without we are not able to
investigate. All we have now is that it crashed somewhere in libX11 which is
not a very helpful information as we use that a few times in KWin and in
libraries.

Maybe check whether coredumpctl caught the crash.

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

[kwin] [Bug 370985] Chrome doesn't show its own minimize/maximize/close buttons when maximized

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #4 from Martin Gräßlin  ---
(In reply to Peter Eszlari from comment #3)

> If there is nothing you can do, how does it come, that other window managers
> (IceWM) and KWin 5.5 have no such problem?

It's not a problem of KWin, but of Plasma providing a dbus service previously
only used in Unity.  Apparently Chrome interprets the availability of that
service as "I'm in Unity" instead of using the XDG_CURRENT_DESKTOP. Thus it
removes the title bar as that's what's needed in Unity.

> 
> A workaround that I found, is to remove libunity:
> $ sudo apt remove libunity9

Which shows the problem is in Chrome: they misdetect the desktop.

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

[kwin] [Bug 359327] Exiting game a in Steam Big Picture Mode gets semi-windowed BPM

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #13 from Martin Gräßlin  ---
Unfortunately for further investigation I would have to run it myself. But I
don't have steam or any games and there is no easy way for me to get it as it's
non-free software. Are there any other applications you experience the problem
with?

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

[kwin] [Bug 359327] Exiting game a in Steam Big Picture Mode gets semi-windowed BPM

[Martin Gräßlin via KDE Bugzilla]

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

Martin Gräßlin  changed:

   What|Removed |Added

Version|unspecified |5.8.1

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

[kwin] [Bug 370917] KWin is putting newly opened windows on random screen

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #5 from Martin Gräßlin  ---
> Setting to 'Focus follows mouse' definitely made things better for every 
> application except GTK based. Not sure if it's KWin's issue or just GTK do 
> not follow rules. If latter then this bug report can be closed. Thank you.

Please provide output of xwininfo on such a window.

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

[kwin] [Bug 359327] Exiting game a in Steam Big Picture Mode gets semi-windowed BPM

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #11 from Martin Gräßlin  ---
As we don't have a version information: can anyone test with Plasma 5.8.1 - our
current release?

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

[kwin] [Bug 359327] Exiting game a in Steam Big Picture Mode gets semi-windowed BPM

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #9 from Martin Gräßlin  ---
(In reply to Shawn from comment #8)
> (In reply to Martin Gräßlin from comment #7)
> > Which window is having focus when the game exits?
> 
> The steam overlay still has focus.  It is still fullscreen, too.  But the
> panel is now visible on top.

are you sure it's having focus. That would not be like how KWin handles
fullscreen windows. An active fullscreen window is above the panel. Only
non-active fullscreen windows are below panel.

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

[neon] [Bug 371000] qtbase-abi conflicts with the current qtcreator package

[Martin Gräßlin via KDE Bugzilla]

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

Martin Gräßlin  changed:

   What|Removed |Added

Product|plasma-integration  |neon
Version|5.8.0   |unspecified
   Assignee|mgraess...@kde.org  |neon-b...@kde.org
  Component|general |general
 CC||j...@jriddell.org,
   ||neon-b...@kde.org,
   ||sit...@kde.org

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

[kwin] [Bug 370999] Kwin crashes sometimes when opening windows

[Martin Gräßlin via KDE Bugzilla]

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

Martin Gräßlin  changed:

   What|Removed |Added

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

--- Comment #1 from Martin Gräßlin  ---
As a workaround use 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 via KDE Bugzilla]

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

--- Comment #45 from Martin Gräßlin  ---
*** Bug 370999 has been marked as a duplicate of this bug. ***

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

[kwin] [Bug 369661] TabBox no longer allows mouse wheel

[Martin Gräßlin via KDE Bugzilla]

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

Martin Gräßlin  changed:

   What|Removed |Added

  Latest Commit||http://commits.kde.org/kwin
   ||/e9d20b80e9a79f514a219357d9
   ||91092d83665350
   Version Fixed In||5.8.2
 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED

--- Comment #6 from Martin Gräßlin  ---
Git commit e9d20b80e9a79f514a219357d991092d83665350 by Martin Gräßlin.
Committed on 17/10/2016 at 06:23.
Pushed by graesslin into branch 'Plasma/5.8'.

[tabbox] Intercept QWheelEvents on QQuickWindow for scrolling

Summary:
The TabBox performs the scrolling of the items by itself in order to
support wheel events even if the mouse is not on the TabBox. For that
KWin grabs pointer events on X11 (on Wayland an input filter is used)
and forwards them to the TabBox.

Qt uses Xinput2 for scrolling on the QQuickWindow. Due to that KWin
does not get any xcb core button press/release events when scrolling
inside the QQuickWindow and thus scrolling doesn't work.

There are three possible approaches to fix this:
1. Implement scrolling support in each of the QML switchers
2. Add an xinput2 filter to TabBox
3. Intercept the QWheelEvents on the QQuickWindow

The first approach has the disadvantage that all themes need
adjustment and that there might be behaviorial difference whether one
scrolls on the TabBox window or outside the window.

The second approach would be most in line with the other filters, but
is difficult due to the nature of xinput2 (no xcb bindings, etc).

Thus the third approach might be the best solution. Wheel events are
only delivered to the QQuickWindow if the native events were not already
intercepted, thus we know it won't have side effects for the case that
Wayland is used or xinput2 is not supported.

The implementation installs an event filter on the QQuickWindow which
gets created when showing the TabBox and inside the filter waits till
there is an angleDelta of +/-120 and scrolls by one per every 120 angle
delta as described in the QWheelEvent documentation.
FIXED-IN: 5.8.2

Test Plan: Scrolled with touchpad and mouse wheel.

Reviewers: #kwin, #plasma, broulik

Subscribers: plasma-devel, kwin

Tags: #kwin

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

M  +32   -0tabbox/tabboxhandler.cpp
M  +2-0tabbox/tabboxhandler.h

http://commits.kde.org/kwin/e9d20b80e9a79f514a219357d991092d83665350

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

[kwin] [Bug 370341] Meta+Shift+KEY shortcuts not working

[Martin Gräßlin via KDE Bugzilla]

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

Martin Gräßlin  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED
   Version Fixed In||5.8.2
  Latest Commit||http://commits.kde.org/kwin
   ||/78a2732a9a421b8554022ec5ed
   ||cca30d95b45d1a

--- Comment #5 from Martin Gräßlin  ---
Git commit 78a2732a9a421b8554022ec5edcca30d95b45d1a by Martin Gräßlin.
Committed on 17/10/2016 at 06:13.
Pushed by graesslin into branch 'Plasma/5.8'.

Fix shortcut triggering with shift+letter

Summary:
A shortcut with e.g. shift+w could not be triggered as shift is
considered as consumed. It transforms the keysym to an uppercase variant
thus it is consumed.

This change checks for the condition that shift is pressed and is the
only consumed modifier. If the current keysym is a letter the shift is
removed from the consumed modifier again to still support the shortcut.
FIXED-IN: 5.8.2

Reviewers: #kwin, #plasma_on_wayland

Subscribers: plasma-devel, kwin

Tags: #plasma_on_wayland, #kwin

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

M  +1-2autotests/integration/globalshortcuts_test.cpp
M  +13   -2keyboard_input.cpp
M  +1-1keyboard_input.h

http://commits.kde.org/kwin/78a2732a9a421b8554022ec5edcca30d95b45d1a

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

[kwin] [Bug 369214] Keyboard "Lock" keys (Caps/Num/Scroll) leds not turning on.

[Martin Gräßlin via KDE Bugzilla]

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

Martin Gräßlin  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|REOPENED|RESOLVED
  Latest Commit||http://commits.kde.org/kwin
   ||/4c7752c965ab9e10ddb18b1007
   ||7bdb4cdd52df6f
   Version Fixed In||5.8.2

--- Comment #3 from Martin Gräßlin  ---
Git commit 4c7752c965ab9e10ddb18b10077bdb4cdd52df6f by Martin Gräßlin.
Committed on 17/10/2016 at 06:01.
Pushed by graesslin into branch 'Plasma/5.8'.

Support LEDs in Xkb and libinput

Summary:
The Xkb implementation starts to track the state of the LEDs in the
keymap and emits a signal whenever the LEDs change. This signal is
connected to a method in LibInput::Connection which updates the led
state on all devices and uses it to init the state of the led when a new
device gets connected.
FIXED-IN: 5.8.2

Test Plan: Connected a keyboard with LEDs and enabled NumLock and ScrollLock.

Reviewers: #kwin, #plasma_on_wayland

Subscribers: plasma-devel, kwin

Tags: #plasma_on_wayland, #kwin

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

M  +2-0input.cpp
M  +27   -0keyboard_input.cpp
M  +21   -0keyboard_input.h
M  +33   -0libinput/connection.cpp
M  +4-0libinput/connection.h

http://commits.kde.org/kwin/4c7752c965ab9e10ddb18b10077bdb4cdd52df6f

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

[kwin] [Bug 370301] Auto grouping of any program windows does not work

[Martin Gräßlin via KDE Bugzilla]

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

Martin Gräßlin  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED
  Latest Commit||http://commits.kde.org/kwin
   ||/db95b96854e50b9182ea6e01a3
   ||806099ef378cb3
   Version Fixed In||5.8.2

--- Comment #6 from Martin Gräßlin  ---
Git commit db95b96854e50b9182ea6e01a3806099ef378cb3 by Martin Gräßlin.
Committed on 17/10/2016 at 06:02.
Pushed by graesslin into branch 'Plasma/5.8'.

[kwinrules] Hide all autogroup related widgets

Summary:
Window tabs which are required for autogroup are currently not supported
in KWin. Thus exposing autogroup related window rules does not make any
sense.

This change hides the options again in the hope that we can bring the
feature back in future.
FIXED-IN: 5.8.2

Reviewers: #kwin, #plasma

Subscribers: plasma-devel, kwin

Tags: #kwin

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

M  +13   -0kcmkwin/kwinrules/ruleswidget.cpp

http://commits.kde.org/kwin/db95b96854e50b9182ea6e01a3806099ef378cb3

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

[kwin] [Bug 370982] BorderlessMaximizedWindows settings only work on x11 or xwayland windows

[Martin Gräßlin via KDE Bugzilla]

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

Martin Gräßlin  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #1 from Martin Gräßlin  ---
Most likely related to the other maximize bugs like:
 * bug #366632
 * bug #368393
 * bug #368545

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

[kwin] [Bug 370985] Chrome doesn't show its own minimize/maximize/close buttons when maximized

[Martin Gräßlin via KDE Bugzilla]

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

Martin Gräßlin  changed:

   What|Removed |Added

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

--- Comment #1 from Martin Gräßlin  ---
We don't have any control over Chrome's client side decoration. AFAIK this
problem exists because of the progress indicator which Chrome interprets as
"I'm on Unity" and hides the buttons. This is a pure bug by Chrome, it should
use XDG_CURRENT_DESKTOP env variable instead. Please report to Chrome
developers - there is nothing we can do about this.

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

[kwin] [Bug 359327] Exiting game a in Steam Big Picture Mode gets semi-windowed BPM

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #7 from Martin Gräßlin  ---
Which window is having focus when the game exits?

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

[kwin] [Bug 370982] BorderlessMaximizedWindows settings only work on x11 or xwayland windows

[Martin Gräßlin via KDE Bugzilla]

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

Martin Gräßlin  changed:

   What|Removed |Added

  Component|decorations |wayland-generic

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

[kwin] [Bug 370917] KWin is putting newly opened windows on random screen

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #3 from Martin Gräßlin  ---
> Active screen follows mouse: no

Please try changing this option and check whether it works better for you. It's
Systemsettings -> Window Behavior -> Window Actions and Behavior, all way down
checkbox "active screen follows mouse".

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

[kwin] [Bug 370917] KWin is putting newly opened windows on random screen

[Martin Gräßlin via KDE Bugzilla]

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

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

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

[kwin] [Bug 370510] Can't move windows to 2nd monitor - stuck at panel border

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #7 from Martin Gräßlin  ---
> You'll find that the panel blocks any window being dragged by the titlebar, 
> regardless of where the panel is. The question is if this behaviour should be 
> removed or not.

This is the protection I talked about. It is the intended behavior and will not
be changed in general. The only question is whether we can make it work better
in the multi-screen case.

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

[plasmashell] [Bug 370953] plasma folder view: icon labels corrupted using nvidia binary driver

[Martin Gräßlin via KDE Bugzilla]

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

Martin Gräßlin  changed:

   What|Removed |Added

   Assignee|mgraess...@kde.org  |h...@kde.org

--- Comment #2 from Martin Gräßlin  ---
Please don't randomly assign bugs to me.

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

[kwin] [Bug 370939] Add "Keep Above" to WindowAction

[Martin Gräßlin via KDE Bugzilla]

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

Martin Gräßlin  changed:

   What|Removed |Added

  Component|decorations |core
Summary|[Feature Request] - Set |Add "Keep Above" to
   |"Keep Above" with Middle|WindowAction
   |Button in window title bar  |

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

[kwin] [Bug 370913] Logout from Wayland session locks up system

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #1 from Martin Gräßlin  ---
I have seen the problem as well, though when starting directly from vt doesn't
cause the issue.

Does a restart of sddm (through ssh) fix the issue?

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