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=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=453558
Martin Flöser changed:
What|Removed |Added
Component|client |wayland-generic
Product|frameworks
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=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=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 #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=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=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=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 #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=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=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=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
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=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=428195
Martin Flöser changed:
What|Removed |Added
Resolution|--- |WORKSFORME
Status|CONFIRMED
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=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 #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
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=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=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 #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 #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
Martin Flöser changed:
What|Removed |Added
CC||mgraess...@kde.org
--
You are receiving this
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=394772
--- Comment #26 from Martin Flöser ---
For unfocused windows a mouse grab is always installed. So that is probably the
same issue.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=394772
--- Comment #24 from Martin Flöser ---
KWin holds a passive mouse grab. This is established in events.cpp in method
X11Client::updateMouseGrab (https://cgit.kde.org/kwin.git/tree/events.cpp#n861
). I assume this is the relevant piece of code especially
https://bugs.kde.org/show_bug.cgi?id=386114
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=411636
Martin Flöser changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=411636
--- Comment #20 from Martin Flöser ---
Yeah pipewire should socket-activate, but it doesn't - at least on my system. I
tried system restart already. That might be a local issue or a general issue in
the upstream package. It's a new technology
https://bugs.kde.org/show_bug.cgi?id=411636
--- Comment #17 from Martin Flöser ---
I got it working: one just needs to start pipewire
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=411636
--- Comment #16 from Martin Flöser ---
and on xdg-desktop-portal-kde side:
dp-kde-remotedesktop: CreateSession called with parameters:
xdp-kde-remotedesktop: handle:
"/org/freedesktop/portal/desktop/request/1_167/krfb1156724296&quo
https://bugs.kde.org/show_bug.cgi?id=411636
--- Comment #15 from Martin Flöser ---
Error point in krfb:
https://cgit.kde.org/krfb.git/tree/framebuffers/pipewire/pw_framebuffer.cpp#n385
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=411636
--- Comment #14 from Martin Flöser ---
With pipewire installed xdg-desktop-portal-kde no longer crashes, but krfb
still doesn't work and I get now:
Using FrameBuffer: "pw"
Initializing D-Bus connectivity with XDG Desktop Portal
DBus
https://bugs.kde.org/show_bug.cgi?id=411636
--- Comment #13 from Martin Flöser ---
Looks like we need a (runtime) dependency on pipewire. The package pipewire
contains that file but on my system pipewire isn't installed yet, only
libpipewire.
--
You are receiving this mail because:
Yo
https://bugs.kde.org/show_bug.cgi?id=411636
--- Comment #12 from Martin Flöser ---
Running xdg-desktop-portal-kde from command line gives the right hint:
can't load /usr/lib/x86_64-linux-gnu/spa/support/libspa-support.so:
/usr/lib/x86_64-linux-gnu/spa/support/libspa-support.so: cannot
https://bugs.kde.org/show_bug.cgi?id=411636
--- Comment #11 from Martin Flöser ---
Yet another step, but still no success. We get a dialog from
xdg-desktop-portal-kde asking whether we want to allow and then a crash :-(
Application: xdg-desktop-portal-kde (xdg-desktop-portal-kde), signal
https://bugs.kde.org/show_bug.cgi?id=411636
--- Comment #9 from Martin Flöser ---
And I think I found it. xdg-desktop-portal-kde also needs the pipewire
dependency. From build.neon log:
-- The following features have been disabled:
02:36:40
02:36:40 * Screencast portal, Support for screen
https://bugs.kde.org/show_bug.cgi?id=411636
--- Comment #8 from Martin Flöser ---
Another step in the right direction, but we are still not there :-(
Krfb starts now without an error message, but in log I see:
"Failed to create session: 2"
and as soon as a client connects, krfb cra
https://bugs.kde.org/show_bug.cgi?id=411636
--- Comment #6 from Martin Flöser ---
I think I found it :-)
20:44:10 dh_auto_configure -- \
20:44:10--enable-docbook-docs \
20:44:10--enable-geoclue \
20:44:10--enable-installed-tests \
20:44:10--disable-pipewire
https://bugs.kde.org/show_bug.cgi?id=411636
--- Comment #5 from Martin Flöser ---
Weird, I still get the same error and looking in qdbusviewer it indeed does not
have the required interface.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=412969
Bug ID: 412969
Summary: Rendering issue with window decoration borders and
fractional scaling
Product: kwin
Version: git master
Platform: Other
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=412969
Martin Flöser changed:
What|Removed |Added
Flags||Wayland+
Keywords
https://bugs.kde.org/show_bug.cgi?id=411636
Martin Flöser changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|FIXED
https://bugs.kde.org/show_bug.cgi?id=411636
Bug ID: 411636
Summary: krfb misses pipewire plugin
Product: neon
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Prio
https://bugs.kde.org/show_bug.cgi?id=15329
--- Comment #42 from Martin Flöser ---
Sorry, but this is not possible to implement for a window manager. We lack
information to identify that a window is the same as previous window. Please
see Thomas's comments on that. As Thomas states th
https://bugs.kde.org/show_bug.cgi?id=411369
Martin Flöser changed:
What|Removed |Added
Component|general |general
Product|kwin
https://bugs.kde.org/show_bug.cgi?id=411199
Martin Flöser changed:
What|Removed |Added
Assignee|kwin-bugs-n...@kde.org |unassigned-b...@kde.org
Version|git
https://bugs.kde.org/show_bug.cgi?id=411049
Martin Flöser changed:
What|Removed |Added
Resolution|BACKTRACE |---
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=411071
Martin Flöser changed:
What|Removed |Added
Resolution|--- |UPSTREAM
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=411044
Martin Flöser changed:
What|Removed |Added
Resolution|--- |NOT A BUG
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=411049
Martin Flöser changed:
What|Removed |Added
Resolution|--- |BACKTRACE
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=410839
Martin Flöser changed:
What|Removed |Added
Status|NEEDSINFO |REPORTED
Resolution|BACKTRACE
https://bugs.kde.org/show_bug.cgi?id=410869
Martin Flöser changed:
What|Removed |Added
Status|REPORTED|NEEDSINFO
Resolution
https://bugs.kde.org/show_bug.cgi?id=410856
--- Comment #3 from Martin Flöser ---
You are running multiple KWin instances. This is probably the reason for the
high cpu usage. Please kill the additional ones.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=410839
Martin Flöser changed:
What|Removed |Added
Resolution|--- |BACKTRACE
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=410827
Martin Flöser changed:
What|Removed |Added
Resolution|--- |LATER
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=410795
Martin Flöser changed:
What|Removed |Added
Resolution|--- |INTENTIONAL
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=410298
Martin Flöser changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=410296
Martin Flöser changed:
What|Removed |Added
Resolution|--- |NOT A BUG
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=410294
Martin Flöser changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=407917
Martin Flöser changed:
What|Removed |Added
Summary|Poor performance when open |Poor performance when open
https://bugs.kde.org/show_bug.cgi?id=407917
Martin Flöser changed:
What|Removed |Added
Component|platform-wayland|compositing
Flags
https://bugs.kde.org/show_bug.cgi?id=391322
Martin Flöser changed:
What|Removed |Added
Flags||Wayland-, X11+
Component|input
https://bugs.kde.org/show_bug.cgi?id=409548
--- Comment #4 from Martin Flöser ---
What's your keyboard layout?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=410154
--- Comment #3 from Martin Flöser ---
Do I understand correctly that you want to drag and drop while this context
menu is open?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=410181
Martin Flöser changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=410178
Martin Flöser changed:
What|Removed |Added
Component|core|platform-x11-standalone
Flags
https://bugs.kde.org/show_bug.cgi?id=410154
--- Comment #1 from Martin Flöser ---
Could you please illustrate with a screenshot where you click?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=410146
Martin Flöser changed:
What|Removed |Added
Resolution|--- |BACKTRACE
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=400658
--- Comment #26 from Martin Flöser ---
Interesting, so numlock is not active, but a "mod2". The event resolving shows
Keypad modifier to be active. Something is weird.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=410093
Martin Flöser changed:
What|Removed |Added
Status|REPORTED|NEEDSINFO
Resolution
https://bugs.kde.org/show_bug.cgi?id=400658
--- Comment #22 from Martin Flöser ---
Could you please open KWin debug console and check in the input event tab what
keysyms are reported when triggering the not working shortcut. Also the
keyboard tab could be interesting as it lists the active
https://bugs.kde.org/show_bug.cgi?id=409919
--- Comment #12 from Martin Flöser ---
Actually no. KWin only performs a sanity check for windows requesting a size
larger than the screen. This isn't meant for restore of windows, but for screen
layout changes. Such a sanity check is useful
https://bugs.kde.org/show_bug.cgi?id=409919
--- Comment #9 from Martin Flöser ---
I assume the problem lies in a library. Either Qt or a KDE Framework.
Unfortunately I do not know which part is responsible here. So I would suggest
to report against an application so that they can investigate
https://bugs.kde.org/show_bug.cgi?id=409919
--- Comment #6 from Martin Flöser ---
Well, as I said: restoring size (including maximized state) is task of the
applications.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=400658
--- Comment #19 from Martin Flöser ---
Can you please try with us layout?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=400658
--- Comment #17 from Martin Flöser ---
What's the used keyboard layout?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=409979
--- Comment #1 from Martin Flöser ---
Rules are not evaluated when the screen layout changes. Only apply initial and
apply now makes sense for the screen rule. If you want dynamic actions use a
script instead.
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=409919
--- Comment #1 from Martin Flöser ---
Restoring the size is the task of the applications.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=409889
--- Comment #4 from Martin Flöser ---
Please be aware that stacking order would be read only. To manipulate you would
have to use the existing API calls.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=409903
Martin Flöser changed:
What|Removed |Added
Product|kwin|systemsettings
Component|wayland
https://bugs.kde.org/show_bug.cgi?id=409490
--- Comment #13 from Martin Flöser ---
Yes of course all of them. There is no screen recording interface on X11. So
what do the applications do? None of them created a performant screen recording
interface. So they all abuse functionality which is not
https://bugs.kde.org/show_bug.cgi?id=409490
--- Comment #11 from Martin Flöser ---
@Nick: Did you try recordmydesktop with the --no-wm-check command line option?
Are you recording the complete desktop or do you use the --windowid command
line switch to just capture the game?
I'm now in fro
https://bugs.kde.org/show_bug.cgi?id=409845
Martin Flöser changed:
What|Removed |Added
Status|REPORTED|NEEDSINFO
Resolution
https://bugs.kde.org/show_bug.cgi?id=409838
Martin Flöser changed:
What|Removed |Added
Status|REPORTED|NEEDSINFO
Resolution
https://bugs.kde.org/show_bug.cgi?id=409490
Martin Flöser changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=409490
Martin Flöser changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=409396
Martin Flöser changed:
What|Removed |Added
Resolution|--- |NOT A BUG
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=409763
--- Comment #8 from Martin Flöser ---
(In reply to aska990 from comment #7)
> Fair enough.
>
> Then I have 2 more questions, if you don't mind :
>
> - Is there a reliable way to measure the actual refresh rate used by KWin ?
No.
https://bugs.kde.org/show_bug.cgi?id=409490
--- Comment #2 from Martin Flöser ---
This is a problem of the recorder you use. If compositing is disabled KWin is
not involved at all.
Please be aware that recording adds a huge lag no matter whether compositing is
enabled or not. X11 is not
https://bugs.kde.org/show_bug.cgi?id=409797
--- Comment #1 from Martin Flöser ---
Not all rules are supported yet.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=409763
Martin Flöser changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=403421
--- Comment #4 from Martin Flöser ---
Please provide the output of qdbus org.kde.KWin /KWin supportInformation
Please also attach screenshots to the bug report instead of link to external
page.
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=403421
Martin Flöser changed:
What|Removed |Added
Severity|critical|normal
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=409763
Martin Flöser changed:
What|Removed |Added
Resolution|--- |NOT A BUG
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=409760
Martin Flöser changed:
What|Removed |Added
Version|5.16.2 |unspecified
Assignee|kwin-bugs-n
https://bugs.kde.org/show_bug.cgi?id=400645
Martin Flöser changed:
What|Removed |Added
Resolution|--- |UPSTREAM
Status|REPORTED
1 - 100 of 3031 matches
Mail list logo