https://bugs.kde.org/show_bug.cgi?id=477238
Stefan Hoffmeister changed:
What|Removed |Added
CC||stefan.hoffmeister@econos.d
https://bugs.kde.org/show_bug.cgi?id=478309
--- Comment #13 from Stefan Hoffmeister ---
The Pipewire output suggests the following:
* the preview source data (i.e. "the window" == output) offers only format
DRM_FORMAT_ARGB (VideoFormat:BGRA, VideoFormat:BGRx)
* the preview sink
https://bugs.kde.org/show_bug.cgi?id=478309
--- Comment #12 from Stefan Hoffmeister ---
To reconfirm my challenge on vmwgfx, this is the log output with KDE Plasma 6
from git master (kdesrc-build plasma-desktop) with the commit included
---
```
Jan 05 08:59:58 fedora kwin_wayland[1829
https://bugs.kde.org/show_bug.cgi?id=478309
Stefan Hoffmeister changed:
What|Removed |Added
Summary|Pipwire format negotiation |Pipewire format negotiation
https://bugs.kde.org/show_bug.cgi?id=478309
Stefan Hoffmeister changed:
What|Removed |Added
Resolution|FIXED |---
Status|RESOLVED
https://bugs.kde.org/show_bug.cgi?id=479293
--- Comment #9 from Stefan Hoffmeister ---
Created attachment 164620
--> https://bugs.kde.org/attachment.cgi?id=164620=edit
Left 6.0 Wayland (broken) <-> Right X11 5.27 (working)
Attached a screenshot which shows the material difference(s
https://bugs.kde.org/show_bug.cgi?id=479293
--- Comment #8 from Stefan Hoffmeister ---
Created attachment 164619
--> https://bugs.kde.org/attachment.cgi?id=164619=edit
drm_info with legacy mode setting in broken state (left-extend not working)
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=479293
--- Comment #7 from Stefan Hoffmeister ---
Created attachment 164618
--> https://bugs.kde.org/attachment.cgi?id=164618=edit
X11 5.27 left-extend working
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=479293
--- Comment #6 from Stefan Hoffmeister ---
The matching Fedora Rawhide (40) GNOME setup, which runs in legacy mode (no
atomic mode-setting) exposes the exact same behavior as KDE Plasma 6 b2+ (git
master) on Wayland.
To that extent, there may
https://bugs.kde.org/show_bug.cgi?id=479293
--- Comment #5 from Stefan Hoffmeister ---
No difference in behaviour with KWIN_DRM_NO_AMS _not_ set - right now (on my
kernel) this implies no atomic mode-setting.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=479293
--- Comment #4 from Stefan Hoffmeister ---
FWIW, and possibly a separate challenge:
Take the working "extend to the right" setup from above and move the secondary
screen to _extend to the bottom_. This does not render correctly, either (f
https://bugs.kde.org/show_bug.cgi?id=479293
--- Comment #3 from Stefan Hoffmeister ---
Attached drm_info dumps where VMware Workstation adds the monitor "to the left"
and "to the right", respectively, where KDE Desktop Configuration matches the
extend intent exactly
* left-e
https://bugs.kde.org/show_bug.cgi?id=479293
--- Comment #2 from Stefan Hoffmeister ---
Created attachment 164617
--> https://bugs.kde.org/attachment.cgi?id=164617=edit
drm_info in working state (right-extend working well)
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=479293
--- Comment #1 from Stefan Hoffmeister ---
Created attachment 164616
--> https://bugs.kde.org/attachment.cgi?id=164616=edit
drm_info in broken state (left-extend not working)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=479293
Bug ID: 479293
Summary: Multi-monitor Wayland surface does not extend to the
left (Plasma 6)
Classification: Plasma
Product: kwin
Version: git master
Platform: Other
https://bugs.kde.org/show_bug.cgi?id=479154
--- Comment #3 from Stefan Hoffmeister ---
Created attachment 164561
--> https://bugs.kde.org/attachment.cgi?id=164561=edit
Screenshot shows correct rendering, but that's not what is shown
Funny enough, taking a screenshot (with Spectacle) sh
https://bugs.kde.org/show_bug.cgi?id=479154
Stefan Hoffmeister changed:
What|Removed |Added
Status|NEEDSINFO |REPORTED
Resolution
https://bugs.kde.org/show_bug.cgi?id=479154
Bug ID: 479154
Summary: Cursor does not scale with output scale (Wayland,
Plasma 6)
Classification: Plasma
Product: kwin
Version: git master
Platform: Other
https://bugs.kde.org/show_bug.cgi?id=478301
--- Comment #2 from Stefan Hoffmeister ---
The root cause of this is a combination of factors that hit with kwin running
in "legacy mode" (this is the default right now due to driver detection and
workarounds applied), on the DRM back
https://bugs.kde.org/show_bug.cgi?id=478487
--- Comment #4 from Stefan Hoffmeister ---
I am currently digging into cursors in general, have already reached out in the
matter of drmCloseBufferHandle (and the TTM/GEM mess) - and have received a
response from Zack Rusin of VMware / Broadcom, see
https://bugs.kde.org/show_bug.cgi?id=478487
Stefan Hoffmeister changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=479002
Stefan Hoffmeister changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=479002
--- Comment #1 from Stefan Hoffmeister ---
Note that for atomic mode-setting and "hardware" cursors to work on the VMware
vmwgfx driver, a kernel patch is required to prevent kernel oopses, see
https://bugs.kde.org/show_bug.cgi?id=47830
https://bugs.kde.org/show_bug.cgi?id=478308
--- Comment #8 from Stefan Hoffmeister ---
There is a working patch in
https://lore.kernel.org/all/20231225202541.horde.txckv5njboomrzjolmts...@webmail.your-server.de/
which fixes the oops.
With that patch in place, it is now possible to detect
https://bugs.kde.org/show_bug.cgi?id=479002
Bug ID: 479002
Summary: Wayland atomic mode-setting cursors not shown on
vmwgfx driver
Classification: Plasma
Product: kwin
Version: git master
Platform: Other
https://bugs.kde.org/show_bug.cgi?id=478308
--- Comment #7 from Stefan Hoffmeister ---
VMware have reacted on the dri gitlab issue tracker, ACKed the report,
confirmed reproduction on their end, and noted that they now have an internal
tracking item for this.
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=478616
--- Comment #7 from Stefan Hoffmeister ---
This does not seem to be related to NVIDIA. Right now I suspect multi-monitor
support on the Intel 11800H iGPU (there is a 4K screen attached to that GPU,
but the monitor has been working very fine going
https://bugs.kde.org/show_bug.cgi?id=478476
--- Comment #10 from Stefan Hoffmeister ---
As far as I can see, this defect only hits systems where an output does not
_physically_ disappear. Or, in other words, if you plug the cable, well, there
is nothing coming down that wire any more, right?
So
https://bugs.kde.org/show_bug.cgi?id=478476
--- Comment #9 from Stefan Hoffmeister ---
The root cause of this defect is a design challenge in the atomic commit code.
Whenever an output is changed ("DrmGpu::updateOutputs"), among other things,
the 1:1 matched up internal processin
https://bugs.kde.org/show_bug.cgi?id=478476
--- Comment #8 from Stefan Hoffmeister ---
Tested the "cycle multiple monitors" feature of VMware Workstation on Fedora
Workstation Rawhide F40 - it works there.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=478616
--- Comment #6 from Stefan Hoffmeister ---
It appears as if - somehow - this is indeed related to the NVIDIA driver "being
around".
With all prior changes reverted and only the following changes on place, I now
again get reliable boots
https://bugs.kde.org/show_bug.cgi?id=478616
--- Comment #5 from Stefan Hoffmeister ---
Right now it is a lottery game whether I get to the sddm prompt, without
""kwin_core: Failed to open /dev/dri/card0 device (Did not receive a reply. "
Some findings:
* Intel firmware (removing
https://bugs.kde.org/show_bug.cgi?id=478616
--- Comment #4 from Stefan Hoffmeister ---
FWIW, I am concerned that this issue here has been sent into the direction of
"NVIDIA" - while there certainly is NVIDIA hardware in this system, at least
some failures were with KWIN_DRM_DEVICE
https://bugs.kde.org/show_bug.cgi?id=478616
--- Comment #3 from Stefan Hoffmeister ---
I got the reject on the Intel card ("/dev/dri/card0") again this morning, on a
modified system configuration. I had tried to mitigate this issue by modifying
the following two configuration parts on
https://bugs.kde.org/show_bug.cgi?id=478616
--- Comment #2 from Stefan Hoffmeister ---
Based on comments in https://bbs.archlinux.org/viewtopic.php?id=250684 I looked
at there being a chance of racing between drm and systemd-logind (which
apparently is responsible for handing out the file handle
https://bugs.kde.org/show_bug.cgi?id=478616
--- Comment #1 from Stefan Hoffmeister ---
I am reporting this against kwin because of the implementation in `int
LogindSession::openRestricted(const QString )` with the origin of the
log entry evidently being
```
const QDBusMessage reply
https://bugs.kde.org/show_bug.cgi?id=478616
Bug ID: 478616
Summary: System hangs dead on sddm start: "kwin_core: Failed to
open /dev/dri/card0 device (Did not receive a reply.
..."
Classification: Plasma
Product: kwin
https://bugs.kde.org/show_bug.cgi?id=478090
--- Comment #5 from Stefan Hoffmeister ---
I just had this happen again.
It may correlate with timeouts, where "something" turns off? My VM is running
in the background - KDE will simply (eventually) turn off the virtual screen.
Curious:
https://bugs.kde.org/show_bug.cgi?id=478090
Stefan Hoffmeister changed:
What|Removed |Added
CC||stefan.hoffmeister@econos.d
https://bugs.kde.org/show_bug.cgi?id=477985
--- Comment #12 from Stefan Hoffmeister ---
Another MR with a different change detection strategy:
https://invent.kde.org/plasma/kwin/-/merge_requests/4799
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=478601
Bug ID: 478601
Summary: Each unlock "qt.qpa.wayland: Could not create EGL
surface (EGL error 0x3000)"
Classification: Plasma
Product: kscreenlocker
Version: git-master
https://bugs.kde.org/show_bug.cgi?id=478600
--- Comment #1 from Stefan Hoffmeister ---
Note that this actually may be running KDE Plasma 6 git master (self-built); if
so, I am able to rebuild plasma-desktop and test fixes.
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=478600
Bug ID: 478600
Summary: Error: Cannot assign to non-existent property
"accentColor"
Classification: Plasma
Product: kscreenlocker
Version: git-master
Platform: Other
https://bugs.kde.org/show_bug.cgi?id=478421
--- Comment #11 from Stefan Hoffmeister ---
I have installed gnome-boxes on Fedora 39 now, created Rawhide virtual machines
for GNOME and KDE.
Somehow, my setup does seem to work "nicely" in general (very janky), but I
could see by runnin
https://bugs.kde.org/show_bug.cgi?id=478421
--- Comment #8 from Stefan Hoffmeister ---
I see you raising two points in your bug report:
a) "The panel disappeared" inside the VM, i.e. with KDE
b) "spice ... trying to connect to mutter by dbus"
Point a) seems t
https://bugs.kde.org/show_bug.cgi?id=477985
--- Comment #11 from Stefan Hoffmeister ---
Somehow gitlab did not auto-tag
https://invent.kde.org/plasma/kwin/-/merge_requests/4790 ...
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=478308
--- Comment #6 from Stefan Hoffmeister ---
A really good way to make this problem appear is
* have KDE Plasma run with atomic mode-setting on, no software cursors
* switch to a TTY
--> immediate hang of system (in virtual machine)
So KDE Pla
https://bugs.kde.org/show_bug.cgi?id=478487
--- Comment #2 from Stefan Hoffmeister ---
Digging through the net finds https://github.com/swaywm/sway/issues/5834 and
https://github.com/swaywm/sway/issues/3814 - also no way to get hardware
cursors to work on the vmwgfx driver, with the workaround
https://bugs.kde.org/show_bug.cgi?id=478308
--- Comment #5 from Stefan Hoffmeister ---
As the drm project does not read the issue tracker that they have open for use,
I have sent email to the mailing list, see
https://lore.kernel.org/all/20231214122709.horde.5iibixwybtitseoti0k2...@webmail.your
https://bugs.kde.org/show_bug.cgi?id=478421
Stefan Hoffmeister changed:
What|Removed |Added
CC||stefan.hoffmeister@econos.d
https://bugs.kde.org/show_bug.cgi?id=478487
--- Comment #1 from Stefan Hoffmeister ---
With the environment set as above, this seems to work quite well.
I used Firefox to render two Youtube videos
* one on 4K fullscreen resolution at FullHD
* one on 3.5K fullscreen resolution at FullHD
plus
https://bugs.kde.org/show_bug.cgi?id=478487
Bug ID: 478487
Summary: VMware Workstation + atomic mode-settings needs
KWIN_FORCE_SW_CURSOR=1
Classification: Plasma
Product: kwin
Version: git master
Platform: Other
https://bugs.kde.org/show_bug.cgi?id=478476
--- Comment #7 from Stefan Hoffmeister ---
There are two ways to get a virtual screen removed
a) the way described earlier - basically this retains the configuration of the
primary screen
b) un-maximizing the whole setup, which cause VMware
https://bugs.kde.org/show_bug.cgi?id=477985
--- Comment #9 from Stefan Hoffmeister ---
And then there are
* https://github.com/swaywm/wlroots/issues/2188
* https://gitlab.freedesktop.org/wlroots/wlroots/-/issues/2188
referring to
https://drmdb.emersion.fr/properties/3233857728
https://bugs.kde.org/show_bug.cgi?id=478481
Stefan Hoffmeister changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=478481
--- Comment #1 from Stefan Hoffmeister ---
I have an obvious fix locally, will submit MR.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=478481
Bug ID: 478481
Summary: DrmPipeline::setCursorLegacy inappropriate invoke of
DRM_IOCTL_MODE_CURSOR2
Classification: Plasma
Product: kwin
Version: git master
Platform: Other
https://bugs.kde.org/show_bug.cgi?id=478476
--- Comment #6 from Stefan Hoffmeister ---
>From the implementation, I cannot tell how the framebuffer(?) backing the
ouput(?) ever gets removed.
Basically, as part of the change sequence, the second screen goes into
!isConnected with resolut
https://bugs.kde.org/show_bug.cgi?id=478476
Stefan Hoffmeister changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=478476
--- Comment #4 from Stefan Hoffmeister ---
Created attachment 164146
--> https://bugs.kde.org/attachment.cgi?id=164146=edit
After removing screen
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=478476
--- Comment #3 from Stefan Hoffmeister ---
Created attachment 164145
--> https://bugs.kde.org/attachment.cgi?id=164145=edit
After adding screen
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=478476
--- Comment #2 from Stefan Hoffmeister ---
Created attachment 164144
--> https://bugs.kde.org/attachment.cgi?id=164144=edit
Immediately after login (before adding screen) ...
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=478476
Bug ID: 478476
Summary: Output removal ("remove screen") does not work
(Wayland, Plasma 6)
Classification: Plasma
Product: kwin
Version: git master
Platform: Other
https://bugs.kde.org/show_bug.cgi?id=478301
--- Comment #1 from Stefan Hoffmeister ---
I believe this significantly correlates with Xwayland running into problems in
legacy mode; the logs are full of this, too:
```
Dec 13 08:38:30 fedora kwin_wayland_wrapper[6521]: (EE) glamor0: GL error
https://bugs.kde.org/show_bug.cgi?id=477985
--- Comment #8 from Stefan Hoffmeister ---
The root cause of this seems to be a well-intentioned, but eventually
inapplicable, assertion of configuration change, resulting in faulty
suppression of updating:
The implementation tries hard to _not_
https://bugs.kde.org/show_bug.cgi?id=478308
--- Comment #4 from Stefan Hoffmeister ---
(In reply to Stefan Hoffmeister from comment #3)
> (In reply to Neal Gompa from comment #2)
> > The issue tracker for Linux Direct Rendering Manager (DRM) is:
> > https://gitlab.freedeskt
https://bugs.kde.org/show_bug.cgi?id=478308
--- Comment #3 from Stefan Hoffmeister ---
(In reply to Neal Gompa from comment #2)
> The issue tracker for Linux Direct Rendering Manager (DRM) is:
> https://gitlab.freedesktop.org/drm/misc/-/issues
>
> Please file an issue there.
Re
https://bugs.kde.org/show_bug.cgi?id=477985
--- Comment #6 from Stefan Hoffmeister ---
Running `~/kde/build/kwin/bin/kwin_wayland --replace` from a separate session
(ssh) recovers fine for the KDE Plasma Desktop world, and brings the complete
desktop back with the expected (updated!) screen
https://bugs.kde.org/show_bug.cgi?id=477985
--- Comment #5 from Stefan Hoffmeister ---
Hunting around on the net found
https://bugzilla.redhat.com/show_bug.cgi?id=1986240#c32 where Zack Rusin
comments in 2021
```
The KDE issue is a little different. KDE had (it still might, as I haven't
tested
https://bugs.kde.org/show_bug.cgi?id=477985
--- Comment #4 from Stefan Hoffmeister ---
In a different failure mode, the whole desktop becomes unusable due to kwin
getting stuck on
```
Dec 10 13:38:31 fedora kwin_wayland[79391]: kwin_wayland_drm: Page flip failed:
No space left on device
https://bugs.kde.org/show_bug.cgi?id=478309
--- Comment #3 from Stefan Hoffmeister ---
Note that Fedora Rawhide 40, as I am writing this, does not have the H.264
codec available (yet), so openh264 is not installed (in case that matters)
--
You are receiving this mail because:
You are watching
https://bugs.kde.org/show_bug.cgi?id=478309
--- Comment #2 from Stefan Hoffmeister ---
Created attachment 164042
--> https://bugs.kde.org/attachment.cgi?id=164042=edit
Screenshot showing empty preview
Attached screenshot showing the empty preview (and parts of the pipewire
challen
https://bugs.kde.org/show_bug.cgi?id=478309
--- Comment #1 from Stefan Hoffmeister ---
At the same time that "no content" pops up up, journalctl shows pipewire
errors. I suspect that this unrelated, as pipewire is (largely) about audio,
but I am pasting this still:
```
Dec 09 16:36
https://bugs.kde.org/show_bug.cgi?id=478309
Bug ID: 478309
Summary: Content preview windows empty (Wayland, VMware)
Classification: Plasma
Product: plasmashell
Version: master
Platform: Other
OS: Other
Status:
https://bugs.kde.org/show_bug.cgi?id=478308
Bug ID: 478308
Summary: VMware kernel oops with KWIN_DRM_NO_AMS=0; desktop
does not repaint
Classification: Plasma
Product: kwin
Version: git master
Platform: Other
https://bugs.kde.org/show_bug.cgi?id=478301
Bug ID: 478301
Summary: Log spam "drmPrimeHandleToFD() failed: No such file or
directory" (Wayland, virtualization)
Classification: Plasma
Product: kwin
Version: git master
https://bugs.kde.org/show_bug.cgi?id=477985
--- Comment #3 from Stefan Hoffmeister ---
More debug output suggests
```
Dec 03 20:30:30 fedora kwin_wayland[1674]: kwin_xwl: Setting primary
KWin::DrmOutput(0x55c476dd1b00, name="Virtual-1", geometry=QRect(0,0
1664x1154), s
https://bugs.kde.org/show_bug.cgi?id=477985
--- Comment #2 from Stefan Hoffmeister ---
Looking at the code at
https://invent.kde.org/plasma/kwin/-/blob/3cc8e9f13bd011670c3a763bdaf3a508b5270a1d/src/backends/drm/drm_connector.cpp#L267
I am not sure how missing EDID data could result
https://bugs.kde.org/show_bug.cgi?id=477985
--- Comment #1 from Stefan Hoffmeister ---
I added
```
export QT_LOGGING_RULES="kwin*=true"
```
and whenever I resize the virtual screen from the host, I get
```
Dec 03 19:50:30 fedora kwin_wayland[7208]: kwin_wayland_drm: Received ch
https://bugs.kde.org/show_bug.cgi?id=477985
Bug ID: 477985
Summary: Regression on VMware setting screen resolution
(Wayland)
Classification: Plasma
Product: kwin
Version: git master
Platform: Other
OS:
https://bugs.kde.org/show_bug.cgi?id=477905
Stefan Hoffmeister changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=477905
--- Comment #1 from Stefan Hoffmeister ---
Note that, apparently, VirtualBox and VMware Workstation / Player cannot
co-exist on the same Linux installation.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=477905
Bug ID: 477905
Summary: VMware dynamic guest screen resolution broken
(regression on Autofit Guest)
Classification: Plasma
Product: kwin
Version: 5.90.0
Platform: Other
https://bugs.kde.org/show_bug.cgi?id=476352
--- Comment #4 from Stefan Hoffmeister ---
On Fedora Rawhide, with the addition of
https://copr.fedorainfracloud.org/coprs/g/kdesig/kde-nightly/, application
windows appear as expected. Explored with vscode and chromium, both on XWayland
and natively
https://bugs.kde.org/show_bug.cgi?id=476352
--- Comment #3 from Stefan Hoffmeister ---
This defect appears to be specific to Wayland sessions; on X11 (same
installation of KDE Neon unstable), Chrome / Electron applications do render.
Note that, historically, KDE has been working very well
https://bugs.kde.org/show_bug.cgi?id=476352
--- Comment #2 from Stefan Hoffmeister ---
FWIW, this is a regression relative to a freshly installed KDE Neon _stable_ on
the same platform (VMware Workstation 17.5)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=476352
--- Comment #1 from Stefan Hoffmeister ---
Created attachment 162757
--> https://bugs.kde.org/attachment.cgi?id=162757=edit
Visual Studio Code running, task manager preview has the right number of
entries, but the content is not presented at
https://bugs.kde.org/show_bug.cgi?id=476352
Bug ID: 476352
Summary: No app window shown - vscode / Chrome/ Electron -
Wayland, KDE6
Classification: Plasma
Product: kwin
Version: git master
Platform: Neon
https://bugs.kde.org/show_bug.cgi?id=468748
Bug ID: 468748
Summary: Kate on Microsoft Store is out of date
Classification: Applications
Product: kate
Version: unspecified
Platform: Microsoft Windows
OS: Other
https://bugs.kde.org/show_bug.cgi?id=467771
--- Comment #3 from Stefan Hoffmeister ---
https://www.reddit.com/r/Fedora/comments/12j8j1n/have_you_guys_seen_this_screen_glitch_in_kde_what/?utm_source=share_medium=web2x=3
looks interesting and possibly related - the symptoms are very similar.
Note
https://bugs.kde.org/show_bug.cgi?id=467771
--- Comment #2 from Stefan Hoffmeister ---
Note: _drawing_ something that is "alive" works just perfectly fine - so
putting real content into those affected areas renders just fine.
It's, for whatever reason, only whenever content is _no
https://bugs.kde.org/show_bug.cgi?id=467771
--- Comment #1 from Stefan Hoffmeister ---
Created attachment 157564
--> https://bugs.kde.org/attachment.cgi?id=157564=edit
drm_info output of system affected
Added drm_info output which might be more effective in communicating the setup
than pr
https://bugs.kde.org/show_bug.cgi?id=467771
Bug ID: 467771
Summary: Wayland screen corruption, dual output, dual GPU,
different screen resolution
Classification: Plasma
Product: kwin
Version: 5.27.3
Platform: Fedora
https://bugs.kde.org/show_bug.cgi?id=452219
--- Comment #25 from Stefan Hoffmeister ---
IIUC, NVIDIA have posted MRs on swaywm and wlroots which touch the rough area
of the specific problem reported here:
* https://github.com/swaywm/sway/pull/7509
* https://gitlab.freedesktop.org/wlroots
https://bugs.kde.org/show_bug.cgi?id=457130
--- Comment #9 from Stefan Hoffmeister ---
My plan of action is to sprinkle log statements into bluedevil - at least on
the restore path -, to add some observability.
I am trying to set up a reasonably complete KDE build environment (master
https://bugs.kde.org/show_bug.cgi?id=457130
--- Comment #7 from Stefan Hoffmeister ---
>From casual browsing of master of
https://invent.kde.org/plasma/bluedevil/-/tree/master/src (i.e. upcoming 5.26)
it would seem as if up to
https://invent.kde.org/plasma/bluedevil/-/b
https://bugs.kde.org/show_bug.cgi?id=457130
--- Comment #6 from Stefan Hoffmeister ---
Confirmed with KDE 5.25.5 (which just came via Fedora 36 updates).
The contents of `~/.config/bluedevilglobalrc ` are
```
[Adapters]
xx:xx:xx:xx:xx:xx_powered=false
[Devices]
connectedDevices
https://bugs.kde.org/show_bug.cgi?id=457130
--- Comment #5 from Stefan Hoffmeister ---
Elsewhere it was mentioned that Microsoft Windows fast start-up could play a
role; this is definintely not the case for me.
a) While I do have an installation of Microsoft Windows, my reproducing
scenario
https://bugs.kde.org/show_bug.cgi?id=457130
Stefan Hoffmeister changed:
What|Removed |Added
CC||stefan.hoffmeister@econos.d
https://bugs.kde.org/show_bug.cgi?id=452219
--- Comment #9 from Stefan Hoffmeister ---
No (observable) change in behaviour for the current Nvidia 515 driver.
--
You are receiving this mail because:
You are watching all bug changes.
1 - 100 of 106 matches
Mail list logo
