https://bugs.kde.org/show_bug.cgi?id=316734
--- Comment #48 from Martin Flöser ---
(In reply to Nate Graham from comment #47)
> Cannot reproduce in the Plasma Wayland session with current git master, FWIW.
Just experienced the issue on wakeup with relatively recent git master
(20211
https://bugs.kde.org/show_bug.cgi?id=453558
Martin Flöser changed:
What|Removed |Added
Component|client |wayland-generic
Product|frameworks
https://bugs.kde.org/show_bug.cgi?id=336369
--- Comment #47 from Martin Flöser ---
(In reply to Krystof Jelinek from comment #45)
> I am pretty confident that quite a lot of people still hold it, and again I
> ask: how does it improve security?
As a father of a 3 year old child I can te
https://bugs.kde.org/show_bug.cgi?id=316734
--- Comment #42 from Martin Flöser ---
Can those affected by the problem please check dmesg after a suspend cycle for
messages related to drm?
Personally I haven't experienced this problem for years (!) any more and given
the past I fear that th
https://bugs.kde.org/show_bug.cgi?id=316734
--- Comment #46 from Martin Flöser ---
Based on comment #43 I read through the relevant code pieces for Wayland. On
Wayland we ensure that when the screen is locked only the lock screen window or
input method window should be visible (see
https
https://bugs.kde.org/show_bug.cgi?id=439137
--- Comment #7 from Martin Flöser ---
>From the description it sounds that window gets mapped without the
WM_TRANSIENT_FOR property and KWin and likewise XFWM does not support changing
the state of that property.
I just checked ICCCM and could
https://bugs.kde.org/show_bug.cgi?id=439137
--- Comment #9 from Martin Flöser ---
(In reply to nyanpasu64 from comment #8)
> On the technical side of things, how would I "monitor the property states
> once the window gets mapped and then monitor for changes of the property"?
&
https://bugs.kde.org/show_bug.cgi?id=439137
--- Comment #11 from Martin Flöser ---
Good! That explains the behavior. The placement is done in the manage method,
thus once we know it's a transient, it's too late.
I think this should go back to GTK devs to look into ensuring that th
https://bugs.kde.org/show_bug.cgi?id=428195
Bug ID: 428195
Summary: Panel triggers constant repaints
Product: plasmashell
Version: master
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
https://bugs.kde.org/show_bug.cgi?id=428195
--- Comment #3 from Martin Flöser ---
(In reply to David Edmundson from comment #2)
> Does
>
> QSG_VISUALIZE=changes plasmashell --replace
>
> tell use anything?
Nothing repaints...
(In reply to Konrad Materka from comment #1)
&
https://bugs.kde.org/show_bug.cgi?id=428195
--- Comment #4 from Martin Flöser ---
Created attachment 132718
--> https://bugs.kde.org/attachment.cgi?id=132718&action=edit
Wayland debug output
Run with WAYLAND_DEBUG=1 - we can nicely see the constant repaints.
--
You are receiving th
https://bugs.kde.org/show_bug.cgi?id=428195
--- Comment #10 from Martin Flöser ---
(In reply to Konrad Materka from comment #9)
> (In reply to Martin Flöser from comment #3)
> > yep, none is causing it.
> Do I understand correctly, that even if you disable all applets and
https://bugs.kde.org/show_bug.cgi?id=435467
Bug ID: 435467
Summary: KWIN_DRM_DEVICE no longer supported
Product: kwin
Version: git master
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
https://bugs.kde.org/show_bug.cgi?id=435468
Bug ID: 435468
Summary: XDG_SESSION_ID no longer honored by KWin
Product: kwin
Version: git master
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
https://bugs.kde.org/show_bug.cgi?id=435467
--- Comment #2 from Martin Flöser ---
(In reply to Vlad Zahorodnii from comment #1)
> Would it be sufficient if we introduce an environment variable with a
> slightly different name, KWIN_DRM_DEVICES?
sure
--
You are receiving this mail becaus
https://bugs.kde.org/show_bug.cgi?id=421131
Martin Flöser changed:
What|Removed |Added
CC||mgraess...@kde.org
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=421131
--- Comment #2 from Martin Flöser ---
Can you please check whether KWin is running with real-time scheduling? The
whole idea of giving real-time scheduling was to prevent laggy situations on
heavy system load. But not all distributions were able to
https://bugs.kde.org/show_bug.cgi?id=421131
--- Comment #4 from Martin Flöser ---
You can use ksysguard. Enable the process priority column and check whether
kwin_wayland is marked as realtime or FIFO. I would like to give you a
screenshot how it should look like, but on KDE neon it's de
https://bugs.kde.org/show_bug.cgi?id=421131
--- Comment #5 from Martin Flöser ---
You could also check
getcap /usr/bin/kwin_wayland
it should print:
/usr/bin/kwin_wayland = cap_sys_nice+ep
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=421131
--- Comment #8 from Martin Flöser ---
cmake looks for optional build dependency Libcap. Verify that you have built
KWin with that dependency. In case your KWin is built with libcap support do:
sudo setcap CAP_SYS_NICE=+ep `which kwin_wayland
https://bugs.kde.org/show_bug.cgi?id=474938
Bug ID: 474938
Summary: Qt6: Calendar fails to start
Classification: Applications
Product: Merkuro
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=474938
--- Comment #2 from Martin Flöser ---
71 min from report to fix - I am deeply impressed!
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=423610
Bug ID: 423610
Summary: Krunner crashes once entering text
Product: krunner
Version: unspecified
Platform: Neon Packages
OS: Linux
Status: REPORTED
Keywords: drk
https://bugs.kde.org/show_bug.cgi?id=316734
--- Comment #61 from Martin Flöser ---
(In reply to Shmerl from comment #60)
> I haven't tested it with X11, but is the code shared for it too? It's in
> wayland_server.cpp, so I assumed it only fixes the Wayland use case.
The patch
https://bugs.kde.org/show_bug.cgi?id=437742
Bug ID: 437742
Summary: maliit-keyboard has broken dependencies
Product: neon
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
https://bugs.kde.org/show_bug.cgi?id=428195
Martin Flöser changed:
What|Removed |Added
Resolution|--- |WORKSFORME
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=434794
Bug ID: 434794
Summary: maliit-keyboard misses dependency to
qml-module-qtquick-localstorag
Product: neon
Version: unspecified
Platform: Other
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=274931
--- Comment #82 from Martin Flöser ---
No, we cannot detect that a window belongs to plasma. If all of that were that
simple we would have done it.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=400090
Martin Flöser changed:
What|Removed |Added
Component|platform-wayland|compositing
Flags
https://bugs.kde.org/show_bug.cgi?id=400096
--- Comment #1 from Martin Flöser ---
Please provide the output of qdbus org.kde.KWin /KWin supportInformation
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=274931
--- Comment #84 from Martin Flöser ---
I'm sorry, but also this idea would not work due to the fact how KWin
internally works. I'm sorry, that we cannot resolve the problem. As everyone
can see it is now seven years old and has many users fo
https://bugs.kde.org/show_bug.cgi?id=400098
Martin Flöser changed:
What|Removed |Added
Resolution|--- |BACKTRACE
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=399372
--- Comment #6 from Martin Flöser ---
Please provide the output of
qdbus org.kde.KWin /KWin supportInformation
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=400021
--- Comment #11 from Martin Flöser ---
300 ms could be worth a try.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=274931
--- Comment #87 from Martin Flöser ---
I'm sorry but your understanding of the KWin rules implementation is
unfortunately not how it works. Please trust a Dev knowing the code base that
there's no easy fix.
--
You are receiving this mail be
https://bugs.kde.org/show_bug.cgi?id=400135
--- Comment #2 from Martin Flöser ---
Ehm, That has always been a toggle.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=400135
Martin Flöser changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=400171
Martin Flöser changed:
What|Removed |Added
Resolution|--- |NOT A BUG
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=400135
--- Comment #6 from Martin Flöser ---
(In reply to Andres Betts from comment #5)
> Maybe that is something that can be addressed. What is the logic behind the
> delay in activation/deactivation?
Without, a fast movement wuld make it ac
https://bugs.kde.org/show_bug.cgi?id=400171
--- Comment #3 from Martin Flöser ---
(In reply to Christoph Feck from comment #2)
> Which information should the decoration use to decide that windows are tiled?
The corners edges information.
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=400202
Martin Flöser changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=399778
Martin Flöser changed:
What|Removed |Added
CC||dontdie...@gmail.com
--- Comment #14 from
https://bugs.kde.org/show_bug.cgi?id=400227
Martin Flöser changed:
What|Removed |Added
Severity|normal |wishlist
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=400240
--- Comment #2 from Martin Flöser ---
(In reply to Vlad Zagorodniy from comment #1)
> Hmm, looks like we're not connecting to existing wayland clients when
> creating EffectsHandler.
Quite likely as initially we didn't support a co
https://bugs.kde.org/show_bug.cgi?id=375708
Martin Flöser changed:
What|Removed |Added
Attachment #115644|0 |1
is obsolete
https://bugs.kde.org/show_bug.cgi?id=400336
--- Comment #1 from Martin Flöser ---
Please provide the output of qdbus org.kde.KWin /KWin supportInformation
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=400358
Martin Flöser changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=396830
Martin Flöser changed:
What|Removed |Added
CC||diehar...@hotmail.com
--- Comment #3 from
https://bugs.kde.org/show_bug.cgi?id=398668
--- Comment #7 from Martin Flöser ---
For me track mouse effect works just fine.
Please provide the output of:
qdbus org.kde.KWin /KWin supportInformation
For what is worth I wouldn't trust Devuan to be a distribution providing a
workable de
https://bugs.kde.org/show_bug.cgi?id=400394
Martin Flöser changed:
What|Removed |Added
Resolution|--- |BACKTRACE
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=398668
--- Comment #13 from Martin Flöser ---
According to the debug output the track mouse effect is *not* enabled.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=400461
--- Comment #2 from Martin Flöser ---
Please provide output of:
qdbus org.kde.KWin /KWin supportInformation
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=400451
Martin Flöser changed:
What|Removed |Added
Component|wayland-generic |general
Product|kwin
https://bugs.kde.org/show_bug.cgi?id=407288
Martin Flöser changed:
What|Removed |Added
CC|mgraess...@kde.org |
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=408390
Martin Flöser changed:
What|Removed |Added
Severity|normal |wishlist
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=408575
Martin Flöser changed:
What|Removed |Added
Severity|critical|normal
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=408475
Martin Flöser changed:
What|Removed |Added
Severity|critical|normal
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=408615
Martin Flöser changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=408575
--- Comment #2 from Martin Flöser ---
*** Bug 408615 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=404983
--- Comment #3 from Martin Flöser ---
ScreenshotEffect doesn't support QPainter:
bool ScreenShotEffect::supported()
{
return effects->compositingType() == XRenderCompositing ||
(effects->isOpenGLCompositing() &&
https://bugs.kde.org/show_bug.cgi?id=404983
Martin Flöser changed:
What|Removed |Added
Component|general |effects-various
Flags
https://bugs.kde.org/show_bug.cgi?id=386271
--- Comment #12 from Martin Flöser ---
>From a security perspective the best way would be KWin to handle the shortcut
and launch spectacle (or any other tool) and pipe it the screenshot. The
alternative would be spectacle asking and KWin showing
https://bugs.kde.org/show_bug.cgi?id=408610
Martin Flöser changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Flags
https://bugs.kde.org/show_bug.cgi?id=408677
Martin Flöser changed:
What|Removed |Added
Component|general |common
Product|kwin
https://bugs.kde.org/show_bug.cgi?id=408678
Martin Flöser changed:
What|Removed |Added
Resolution|--- |BACKTRACE
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=408639
Martin Flöser changed:
What|Removed |Added
Resolution|--- |UPSTREAM
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=408668
Martin Flöser changed:
What|Removed |Added
Status|REPORTED|NEEDSINFO
Resolution
https://bugs.kde.org/show_bug.cgi?id=408694
Martin Flöser changed:
What|Removed |Added
Status|REPORTED|NEEDSINFO
Resolution
https://bugs.kde.org/show_bug.cgi?id=344326
--- Comment #190 from Martin Flöser ---
This bug is only for KWin. Issues in other applications are handled in other
reports.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=408741
--- Comment #1 from Martin Flöser ---
X11 or Wayland?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=408746
--- Comment #1 from Martin Flöser ---
Please provide output of xprop and xwininfo of emacs. Emacs is known to be not
standard compliant, it's a tricky application.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=408746
--- Comment #6 from Martin Flöser ---
What's your screen resolution?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=408746
Martin Flöser changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=408741
Martin Flöser changed:
What|Removed |Added
Component|appmenu |core
Flags
https://bugs.kde.org/show_bug.cgi?id=408787
Martin Flöser changed:
What|Removed |Added
Target Milestone|--- |1.0
CC
https://bugs.kde.org/show_bug.cgi?id=408791
--- Comment #1 from Martin Flöser ---
Please provide output of qdbus org.kde.KWin /KWin supportInformation
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=408784
Martin Flöser changed:
What|Removed |Added
Resolution|--- |INTENTIONAL
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=408571
Martin Flöser changed:
What|Removed |Added
Assignee|kwin-bugs-n...@kde.org |dolphin-bugs-n...@kde.org
Product
https://bugs.kde.org/show_bug.cgi?id=408806
Martin Flöser changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=408812
Martin Flöser changed:
What|Removed |Added
Status|REPORTED|NEEDSINFO
Resolution
https://bugs.kde.org/show_bug.cgi?id=408817
--- Comment #1 from Martin Flöser ---
Does your notebook have multiple gpus?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=408846
Martin Flöser changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=408969
Martin Flöser changed:
What|Removed |Added
Target Milestone|--- |1.0
Product|kwin
https://bugs.kde.org/show_bug.cgi?id=409108
Martin Flöser changed:
What|Removed |Added
Resolution|--- |NOT A BUG
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=409042
--- Comment #3 from Martin Flöser ---
Please try the proprietary Nvidia driver.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=407612
--- Comment #23 from Martin Flöser ---
Oops, sorry. Though I don't understand why: Aurorae should not create any
internal windows at all...
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=409085
--- Comment #3 from Martin Flöser ---
The bouncy cursor is rather old and kind of a symbol for the kde desktop. I
don't know when it got introduced, but was definitely already present in 3.x.
That's kind of a reason to keep it as it is.
On
https://bugs.kde.org/show_bug.cgi?id=408748
--- Comment #14 from Martin Flöser ---
I don't understand why this was moved to KWin. It's clearly not a bug in the
window manager as it's not involved with input handling on X11.
--
You are receiving this mail because:
You are w
https://bugs.kde.org/show_bug.cgi?id=409042
--- Comment #5 from Martin Flöser ---
Please contact your distribution support forum on how to install the NVIDIA
drivers for your GPU. If I understand correctly your GPU was released in 2006.
It is very likely that you will have to install legacy
https://bugs.kde.org/show_bug.cgi?id=373907
--- Comment #25 from Martin Flöser ---
(In reply to Christoph Feck from comment #24)
> Did anyone have a chance to test Qt 5.14 (dev) builds? The question is, if
> besides support in Qt something else needs to be added/changed in KDE code.
We n
https://bugs.kde.org/show_bug.cgi?id=408668
Martin Flöser changed:
What|Removed |Added
Resolution|WAITINGFORINFO |DOWNSTREAM
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=409330
Martin Flöser changed:
What|Removed |Added
Assignee|kwin-bugs-n...@kde.org |se...@kde.org
Product|kwin
https://bugs.kde.org/show_bug.cgi?id=409349
--- Comment #2 from Martin Flöser ---
On X11 the problem is that windows position themselves. KWin is almost never
involved. You can easily check with xprop.
Neither on X11 not on Wayland we have a chance to truly recognize a window.
Without protocol
https://bugs.kde.org/show_bug.cgi?id=409352
Martin Flöser changed:
What|Removed |Added
Resolution|--- |UPSTREAM
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=409378
Martin Flöser changed:
What|Removed |Added
Component|decorations |aurorae
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=407917
--- Comment #3 from Martin Flöser ---
Maybe it's a problem with translucent windows? Especially if window background
is blurred a performance degrading is to be expected with more open windows.
--
You are receiving this mail because:
You are wat
https://bugs.kde.org/show_bug.cgi?id=407917
--- Comment #6 from Martin Flöser ---
Shadows are translucent and Konsole is translucent. That sounds a lot like an
issue in our translucent windows rendering path.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=407917
--- Comment #8 from Martin Flöser ---
Iirc Qt on Wayland uses an alpha channel by default, so we are always in the
"Konsole" Case.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=407917
--- Comment #10 from Martin Flöser ---
(In reply to Christoph Feck from comment #9)
> If Qt doesn't inform Wayland of opaque surfaces, that sure would be worth a
> bug report.
Yes and no. I would say it was a bug on X11 that argb was not su
https://bugs.kde.org/show_bug.cgi?id=409476
Martin Flöser changed:
What|Removed |Added
Resolution|--- |BACKTRACE
Status|REPORTED
1 - 100 of 3031 matches
Mail list logo
