| Summary: | After resume from suspend, non-primary display in multi-screen setup is black | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | jamese <james.ellis> |
| Component: | generic-multiscreen | Assignee: | Aleix Pol <aleixpol> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | linux, murat.ursavas, plasma-bugs |
| Priority: | NOR | ||
| Version: | 5.3.1 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Kubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
Screenshot showing non-primary black screen
krunner crash after unplugging displayport cable. plasmashell crash after unplugging DP cable |
||
|
Description
jamese
2015-06-22 00:36:18 UTC
Created attachment 93286 [details]
Screenshot showing non-primary black screen
Screen on right is 'primary'. Left is-non primary.
Screenshot taken immediately post-resume.
Still getting this issue in Kubuntu 15.10 on the Plasma 5.4 it comes with. This is on a Displayport setup using Intel drivers with an Integrated Graphics Chipset: Intel(R) Iris(TM) Pro Graphics 5200 (from Xorg logs). $ aptitude show xserver-xorg-video-intel Package: xserver-xorg-video-intel State: installed Automatically installed: no Version: 2:2.99.917+git20150808-0ubuntu3 Priority: optional Section: x11 Maintainer: Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com> Architecture: amd64 Uncompressed Size: 3,187 k Depends: libc6 (>= 2.17), libdrm-intel1 (>= 2.4.38), libdrm2 (>= 2.4.25), libpciaccess0 (>= 0.8.0+git20071002), libpixman-1-0 (>= 0.30.0), libudev1 (>= 183), libx11-6, libx11-xcb1, libxcb-dri2-0, libxcb-dri3-0, libxcb-sync1, libxcb-util1 (>= 0.4.0), libxcb1, libxcursor1 (> 1.1.2), libxdamage1 (>= 1:1.1), libxext6, libxfixes3, libxinerama1, libxrandr2 (>= 2:1.2.99.2), libxrender1, libxshmfence1, libxtst6, libxv1, libxvmc1, xorg-video-abi-19, xserver-xorg-core (>= 2:1.16.99.901) Conflicts: xserver-xorg-video-intel Provides: xorg-driver-video Description: X.Org X server -- Intel i8xx, i9xx display driver This package provides the driver for the Intel i8xx and i9xx family of chipsets, including i810, i815, i830, i845, i855, i865, i915, i945 and i965 series chips. This package also provides XvMC (XVideo Motion Compensation) drivers for i810/i815 and i9xx and newer chipsets. This package is built from the X.org xf86-video-intel driver module. Homepage: http://www.x.org/ Created attachment 94998 [details]
krunner crash after unplugging displayport cable.
Was able to trigger the empty black screen on the non-primary display by unplugging the Displayport cable and plugging it back in again.
Krunner crashed when this happened, this is the trace which is marked "useful".
Created attachment 94999 [details]
plasmashell crash after unplugging DP cable
Was able to trigger the empty black screen on the non-primary display by unplugging the Displayport cable and plugging it back in again.
Plasmashell crashed when this happened, this is the trace which is marked "useful".
Likely the same issue as bug 353975. The crash mentioned was fixed lately (at least I haven't seen plasma crashing on screen changes since a few weeks). I have the same issue but with different trigger. I was testing multi screen setup with Arch + Plasma 5.5.2 (compiled with Qt 5.5.1). While there were not just one unexpected behavior, this was one of them. I was plugging in and out my HDMI monitor. After couple of tries (without any suspend or log out operation) my second screen turned to black. Of course it's still active, I can see windows, pointer etc, but the wallpaper is gone. I'll try to find other behaviors in other threads or create one for them. After reading https://bugs.kde.org/show_bug.cgi?id=353975 this appears to be the same thing. Since updating to Plasma 5.5 from Kubuntu Backports, Plasma crashes have all but disappeared but I still have funky multi-screen support, possibly related to other bugs, in KDE... Generally ending with unusable desktops and me having to kill sddm and rm .local/share/kscreen/*, then signing in again. *** This bug has been marked as a duplicate of bug 353975 *** |