https://bugs.kde.org/show_bug.cgi?id=505954
--- Comment #9 from Jean-Francois Roy ---
(In reply to Nate Graham from comment #8)
> Could be the direct scanout fix in 6.4.1. Good news, and thanks for
> following up!
I just did some regression testing on this using the changelog, and it'
https://bugs.kde.org/show_bug.cgi?id=505954
--- Comment #6 from Jean-Francois Roy ---
The issue appears to in fact only reproduce with the Steam version of the game.
Even with the Steam overlay disabled, the llvmpipe OpenGL implementation gets
picked. The same game version downloaded from the
https://bugs.kde.org/show_bug.cgi?id=505954
--- Comment #5 from Jean-Francois Roy ---
A forum member pointed out from the log that Factorio had fallen off to
software rendering (llvmpipe). So something is preventing SDL from initializing
a hardware context.
I have an Nvidia GPU using the Arch
https://bugs.kde.org/show_bug.cgi?id=505954
Bug ID: 505954
Summary: Dramatic Factorio Wayland rendering performance
regression
Classification: Plasma
Product: kwin
Version First 6.4.0
Reported In:
Platform: Arch Linux
https://bugs.kde.org/show_bug.cgi?id=495846
Bug ID: 495846
Summary: Aborted drags can break input handling in Chromium and
Electron (e.g. VS Code, Chrome, Discord, etc)
Classification: Plasma
Product: kwin
Version: 6.2.2
https://bugs.kde.org/show_bug.cgi?id=491579
Jean-Francois Roy changed:
What|Removed |Added
CC||j...@devklog.net
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=482142
--- Comment #32 from Jean-Francois Roy ---
(In reply to Ted Parvu from comment #31)
> Found a work-a-round that is working for me.
>
> https://bbs.archlinux.org/viewtopic.php?pid=2166339#p2166339
Completely disabling drag and drop is a pr
https://bugs.kde.org/show_bug.cgi?id=482142
--- Comment #26 from Jean-Francois Roy ---
We ideally need a solution in KWin because other applications based on Chromium
are also affected and those tend to be on much slower upgrade cycles. Anything
Electron (Discord, Slack, VS Code) are affected
https://bugs.kde.org/show_bug.cgi?id=482142
Jean-Francois Roy changed:
What|Removed |Added
CC||j...@devklog.net
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=457284
--- Comment #46 from Jean-Francois Roy ---
(In reply to Nate Graham from comment #44)
> Re-opening as it's clearly not fixed since we're still getting bug reports
> about it, unfortunately.
There is some confusion in this bug, 475605,
https://bugs.kde.org/show_bug.cgi?id=475605
--- Comment #28 from Jean-Francois Roy ---
(In reply to Victor Ryzhykh from comment #26)
> (In reply to Jean-Francois Roy from comment #25)
> > I think I am seeing this regularly but on Wayland. If I kill
> > kscreenlocker_greet fro
https://bugs.kde.org/show_bug.cgi?id=475605
--- Comment #27 from Jean-Francois Roy ---
(In reply to Jean-Francois Roy from comment #25)
> I think I am seeing this regularly but on Wayland. If I kill
> kscreenlocker_greet from an ssh or tty session, I can see and use my
> graphical sess
https://bugs.kde.org/show_bug.cgi?id=475605
--- Comment #25 from Jean-Francois Roy ---
I think I am seeing this regularly but on Wayland. If I kill
kscreenlocker_greet from an ssh or tty session, I can see and use my graphical
session again, without needing to unlock the session first with
https://bugs.kde.org/show_bug.cgi?id=479083
Jean-Francois Roy changed:
What|Removed |Added
CC||j...@devklog.net
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=479359
Bug ID: 479359
Summary: sddm-helper-start-wayland fails/exits after manually
turn on monitors
Classification: Plasma
Product: kwin
Version: 5.91.0
Platform: Arch Linux
https://bugs.kde.org/show_bug.cgi?id=478804
Jean-Francois Roy changed:
What|Removed |Added
CC||j...@devklog.net
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=478866
Jean-Francois Roy changed:
What|Removed |Added
CC||j...@devklog.net
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=478531
--- Comment #1 from Jean-Francois Roy ---
Created attachment 164174
--> https://bugs.kde.org/attachment.cgi?id=164174&action=edit
Energy Saving
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=478531
Bug ID: 478531
Summary: Energy Saving and Screen Locking disagree on lock
screen time
Classification: Applications
Product: systemsettings
Version: 5.90.0
Platform: Arch Linux
https://bugs.kde.org/show_bug.cgi?id=478515
Bug ID: 478515
Summary: Disabling "Enable menu accelerators" does not work
Classification: Applications
Product: konsole
Version: 24.01.80
Platform: Arch Linux
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=477738
Jean-Francois Roy changed:
What|Removed |Added
CC||j...@devklog.net
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=475605
--- Comment #17 from Jean-Francois Roy ---
> (In reply to Jean-Francois Roy from comment #15)
> > For what it's worth, I get this issue with the KDE Plasma 6.0 Beta 1 release
> > (as installed by arch's kde-unstable repo) usi
https://bugs.kde.org/show_bug.cgi?id=448866
Jean-Francois Roy changed:
What|Removed |Added
CC||j...@devklog.net
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=475605
Jean-Francois Roy changed:
What|Removed |Added
CC||j...@devklog.net
--- Comment #15 from Jean
https://bugs.kde.org/show_bug.cgi?id=475542
--- Comment #6 from Jean-Francois Roy ---
I've been following the xwayland nvidia situation (both that bug and the patch
to add explicit sync to xwayland
https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/967). I filed this
report becaus
https://bugs.kde.org/show_bug.cgi?id=475542
--- Comment #4 from Jean-Francois Roy ---
I've made a video recording of Element (desktop electron version) in plasma 5
and plasma 6 on the exact same system. It shows the issue pretty well,
especially with audio to hear the keyboard keys. Fro
https://bugs.kde.org/show_bug.cgi?id=475542
--- Comment #2 from Jean-Francois Roy ---
Only plasma 6. Does not repro in plasma 5 on the exact same system.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=475542
Bug ID: 475542
Summary: plasma 6 wayland nvidia: Keyboard input is very laggy
in Electron apps
Classification: I don't know
Product: kde
Version: unspecified
Platform: Archlin
https://bugs.kde.org/show_bug.cgi?id=473483
Jean-Francois Roy changed:
What|Removed |Added
CC||j...@devklog.net
--- Comment #14 from Jean
https://bugs.kde.org/show_bug.cgi?id=475494
Bug ID: 475494
Summary: kwin_wayland_drm: atomic commit failed: Invalid
argument
Classification: Plasma
Product: kwin
Version: git master
Platform: Archlinux
O
https://bugs.kde.org/show_bug.cgi?id=475493
Bug ID: 475493
Summary: pw.context: params Spa:Enum:ParamId:EnumFormat: 0:0
Invalid argument (input format (no more input
formats))
Classification: Frameworks and Libraries
Pro
https://bugs.kde.org/show_bug.cgi?id=475492
Bug ID: 475492
Summary: libkwinglutils: 0x501: GL_INVALID_VALUE error
generated. , and must be 1 or
greater
Classification: Plasma
Product: kwin
Version: git maste
https://bugs.kde.org/show_bug.cgi?id=470503
--- Comment #2 from Jean-Francois Roy ---
Created attachment 159497
--> https://bugs.kde.org/attachment.cgi?id=159497&action=edit
compositor recursion
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=470503
--- Comment #1 from Jean-Francois Roy ---
It is less reproducible than I initially thought. There may need to be some
memory pressure or some extended use of the session for the issue to repro.
I'll keep trying to figure out a reliable method. Onc
https://bugs.kde.org/show_bug.cgi?id=470503
Bug ID: 470503
Summary: [nvidia] Screen corruption after changing theme
Classification: Plasma
Product: kwin
Version: 5.27.5
Platform: Archlinux
OS: Linux
Status: REPO
35 matches
Mail list logo
