[kdenlive] [Bug 475173] Kdenlive crash on startup
https://bugs.kde.org/show_bug.cgi?id=475173 Allistar changed: What|Removed |Added CC||allista...@gmail.com --- Comment #10 from Allistar --- I am also getting this issue. I use Gentoo, so everything is compile from source. My system details are: Application: kdenlive (23.08.3) (Compiled from sources) Qt Version: 5.15.11 Frameworks Version: 5.112.0 Operating System: Linux 6.1.67-gentoo x86_64 Windowing System: X11 Distribution: "Gentoo Linux" DrKonqi: 5.27.10 [KCrashBackend] The stack trace in my case is: [KCrash Handler] #4 0x7f821a1657b6 in QOpenGLContext::functions() const () at /usr/lib64/libQt5Gui.so.5 #5 0x560e4aaa918e in () #6 0x7f8219ab94e1 in () at /usr/lib64/libQt5Core.so.5 #7 0x7f821b669193 in QQuickWindowPrivate::renderSceneGraph(QSize const&, QSize const&) () at /usr/lib64/libQt5Quick.so.5 #8 0x7f821b6f7c77 in QQuickRenderControl::render() () at /usr/lib64/libQt5Quick.so.5 #9 0x7f821bade476 in () at /usr/lib64/libQt5QuickWidgets.so.5 #10 0x7f821bae24a9 in QQuickWidget::event(QEvent*) () at /usr/lib64/libQt5QuickWidgets.so.5 #11 0x7f821ad62e7e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #12 0x7f8219a87728 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #13 0x7f821adbd626 in () at /usr/lib64/libQt5Widgets.so.5 #14 0x7f821adbd656 in () at /usr/lib64/libQt5Widgets.so.5 #15 0x7f821adbd656 in () at /usr/lib64/libQt5Widgets.so.5 #16 0x7f821adbd656 in () at /usr/lib64/libQt5Widgets.so.5 #17 0x7f821adbd656 in () at /usr/lib64/libQt5Widgets.so.5 #18 0x7f821adbd71e in () at /usr/lib64/libQt5Widgets.so.5 #19 0x7f8219ab95f0 in () at /usr/lib64/libQt5Core.so.5 #20 0x7f821a129d1f in QWindow::screenChanged(QScreen*) () at /usr/lib64/libQt5Gui.so.5 #21 0x7f821a12a6d3 in QWindowPrivate::emitScreenChangedRecursion(QScreen*) () at /usr/lib64/libQt5Gui.so.5 #22 0x7f821ad972e5 in QWidgetPrivate::create() () at /usr/lib64/libQt5Widgets.so.5 #23 0x7f821ad9763b in QWidget::create(unsigned long long, bool, bool) () at /usr/lib64/libQt5Widgets.so.5 #24 0x7f821ad999bb in QWidget::winId() const () at /usr/lib64/libQt5Widgets.so.5 #25 0x7f821c5a71c1 in () at /usr/lib64/libKF5XmlGui.so.5 #26 0x7f821c5ab3a1 in KMainWindow::event(QEvent*) () at /usr/lib64/libKF5XmlGui.so.5 #27 0x7f821c5ed9f7 in KXmlGuiWindow::event(QEvent*) () at /usr/lib64/libKF5XmlGui.so.5 #28 0x7f821ad62e7e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #29 0x7f8219a87728 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #30 0x7f821ada0df2 in QWidget::ensurePolished() const () at /usr/lib64/libQt5Widgets.so.5 #31 0x7f821ad82540 in QLayout::totalMinimumSize() const () at /usr/lib64/libQt5Widgets.so.5 #32 0x7f821ad8394e in QLayout::activate() () at /usr/lib64/libQt5Widgets.so.5 #33 0x7f821aec1845 in () at /usr/lib64/libQt5Widgets.so.5 #34 0x7f821ae895e1 in () at /usr/lib64/libQt5Widgets.so.5 #35 0x7f821ae92146 in () at /usr/lib64/libQt5Widgets.so.5 #36 0x7f821ae95ca2 in () at /usr/lib64/libQt5Widgets.so.5 #37 0x7f821aebf605 in () at /usr/lib64/libQt5Widgets.so.5 #38 0x560e4ad642b0 in () #39 0x560e4ad28a71 in () #40 0x560e4a773172 in () #41 0x7f82192509ca in () at /lib64/libc.so.6 #42 0x7f8219250a85 in __libc_start_main () at /lib64/libc.so.6 #43 0x560e4a774b41 in () [Inferior 1 (process 20791) detached] -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454621] Plasmashell doesn't start on all monitors in multi-xscreen environment
https://bugs.kde.org/show_bug.cgi?id=454621 --- Comment #18 from Allistar --- If it identifies monitors by something unique (e.g. the GPU or screen number they're on appended with the QScreen name) then it's likely that when plasmashell starts up it will start on both xscreens which would be a bonus. I admit though that running a multiple xscreen environment will be rare. I think the display control panel app should ask us which xscreen to run on if it detects there's more than one xscreen running. I have no idea what this would mean in a Wayland environment or whether that has a concept of "xscreen". -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454621] Plasmashell doesn't start on all monitors in a multi xscreen environment
https://bugs.kde.org/show_bug.cgi?id=454621 --- Comment #16 from Allistar --- My fix as provided in the patch works for me but it's not a good general purpose fix. I filter out monitors by their serial number as that's unique, but the only easy way I could find the serial number was to add debugging in the code to output this from the QScreen instances. This isn't suitable for most people. The "Display and Monitor -> Display Configuration" system settings app correctly only shows monitors from the current xscreen. Another fix would be to just filter out monitors not in the current xscreen in the screenpool.cpp file. I looked at the QScreen class and couldn't see an easy way to get this information. Should QApp::getScreens only provide monitors in the current xscreen? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454621] Plasmashell doesn't start on all monitors in a multi xscreen environment
https://bugs.kde.org/show_bug.cgi?id=454621 Allistar changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454621] Plasmashell doesn't start on all monitors in a multi xscreen environment
https://bugs.kde.org/show_bug.cgi?id=454621 Allistar changed: What|Removed |Added Attachment #150133|0 |1 is obsolete|| --- Comment #14 from Allistar --- Created attachment 158416 --> https://bugs.kde.org/attachment.cgi?id=158416=edit Patch for 5.27.4.1 to filter monitors by serial number -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454621] Plasmashell doesn't start on all monitors in a multi xscreen environment
https://bugs.kde.org/show_bug.cgi?id=454621 --- Comment #13 from Allistar --- I have tried with 5.27.4.1 (the currently stable version on Gentoo) and the problem is still there. I have fixed this locally by modifying plasma-workspace/shell/screenpool.cpp by telling it to ignore two of my monitors by their serial number. I'll attach my patch file. The fundamental issue is the same and that's that the code identifies monitors by QScreen.name(). This is not unique. It's possible to have two monitors on the same system with the same name. The name is the xrandr output name. I have these monitors on my system: GPU 1: DVI-I-1, HDMI-0, DVI-D-0, HDMI-1 GPU 2: DVI-I-1, DVI-D-0 Note that there are two monitors that both have the name "DV!-I-1" and "DVI-D-0". The bug is primarily in ScreenPool::handleOutputOrderChanged and handleScreenAdded. The class "OutputOrderWatcher" also has a bug because it's using the screen name to identify the screen. My patch looks in plasmashellrc for a "[IgnoredScreens]" setting which is a list of the serial numbers to ignore. I've modified handleScreenAdded and handleOutputOrderChanged to skip over QScreens that have a matching serial number. A proper fix for this is to not assume the screen name is unique and instead have a method that returns something that is unique. I recommend the screen name prefixed with the DISPLAY number (e.g. ":0.0" or "0.1"). I have used serial number because that works for me but I don't think monitors will always provide a serial number. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454621] Plasmashell doesn't start on all monitors in a multi xscreen environment
https://bugs.kde.org/show_bug.cgi?id=454621 --- Comment #12 from Allistar --- Hi all. 5.27 is now available on Gentoo so I'm installing that from source. I'll update here if it now handles multiple xscreens properly or not when it's completed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454621] Plasmashell doesn't start on all monitors in a multi xscreen environment
https://bugs.kde.org/show_bug.cgi?id=454621 --- Comment #10 from Allistar --- Thanks. I'll wait for my distro (Gentoo) to stabilise Plasma 5.27. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 353975] Black screen on second display (no wallpaper, can't get a context menu on right-click)
https://bugs.kde.org/show_bug.cgi?id=353975 --- Comment #233 from Allistar --- I face a separate issue caused by Plasma identifying monitors by their xrandr connector name. Plasma seems to assume that these are unique in a system but they aren't. In my case I have 6 monitors across 2 GPUs and each of them has a DVI-I-1 monitor. Because ScreenConnectors uses this name it causes issues of it starting a plasma shell on the wrong monitor. I fixed this by modifying /shell/screenpool.cpp to get it to ignore monitors by serial number. This was the only property on the QScreen instance that seemed to be unique. This solution works well, though each time a new release comes out I need to repatch the source (I run Gentoo Linux). Any solution that is looking to identifying monitors needs to make sure the identifier is consistent across reboots and is unique. I know the issue in this bug is about display name consistency, but can we please also consider the uniqueness problem in the solution? For reference there are more details of my issue here, as well as a link to the patch that fixes it. https://invent.kde.org/plasma/plasma-workspace/-/issues/51 Thanks, Allistar. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 353975] Black screen on second display (no wallpaper, can't get a context menu on right-click)
https://bugs.kde.org/show_bug.cgi?id=353975 --- Comment #198 from Allistar --- I know there's a bug in the way ScreenConnectors works because of how the screens are identified. Screen names aren't unique as they're identified by xrandr output name. My ScreenConnectors looks like this: [ScreenConnectors] 0=DVI-I-1 1=HDMI-0 2=HDMI-1 3=DVI-D-0 But my system has two different displays both called DVI-I-1. This is because I have 6 displays across 2 GPUs. In my case I only want plasma to run on the 1st GPU (as xscreen 0), but when DVI-I-1 on the second GPU (on xscreen 1) connects Plasma sees this and runs a shell on that one. This prevents it from running a shell on the screen0 one. ScreenConnectors should include either a GPU identifier or xscreen number to fix this issue. I have fixed this myself with a patch that adds a new "IgnoredScreens" section to plasmashellrc and I get plasma to ignore any monitor that has a serial number that's in that list. This is slightly annoying because each time a new version of plasma-workspace comes out I have to redo my patch. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454621] Plasmashell doesn't start on all monitors in a multi xscreen environment
https://bugs.kde.org/show_bug.cgi?id=454621 --- Comment #8 from Allistar --- (In reply to Andreas Sturmlechner from comment #7) > Please create an MR over at https://invent.kde.org/plasma/plasma-workspace > instead of attaching here, it will get much more attention. Thanks. My patch fixes my individual problem but it's not necessarily the best solution. I think that QT/Plasma should be ignoring monitors that aren't on the current xscreen. My patch allows us to blacklist monitors by serial number. Should Plasma only run on screen0? It would be great if it ran on all xscreens, but that we should have a choice through config. I think the [ScreenConnectors] config should be changed from this format: [ScreenConnectors] 0=DVI-I-1 1=HDMI-1 To this: [ScreenConnectors] 0=0:DVI-I-1 1=0:HDMI-1 Where the "0:" is the screen number. This way we can run Plasma on only one xscreen, or on both even when monitors have the same name. -- You are receiving this mail because: You are watching all bug changes.
[plasma4] [Bug 290424] Lock screen/screen saver hangs when home directory mounted over Kerberized NFS expires
https://bugs.kde.org/show_bug.cgi?id=290424 Allistar changed: What|Removed |Added CC||allista...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454621] Plasmashell doesn't start on all monitors in a multi xscreen environment
https://bugs.kde.org/show_bug.cgi?id=454621 --- Comment #6 from Allistar --- Comment on attachment 150133 --> https://bugs.kde.org/attachment.cgi?id=150133 Allows monitors to be blacklisted from Plasma by their serial number Note: this patch is from a gentoo system and is made for plasma-workspace-5.24-5. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454621] Plasmashell doesn't start on all monitors in a multi xscreen environment
https://bugs.kde.org/show_bug.cgi?id=454621 Allistar changed: What|Removed |Added CC||allista...@gmail.com --- Comment #5 from Allistar --- Created attachment 150133 --> https://bugs.kde.org/attachment.cgi?id=150133=edit Allows monitors to be blacklisted from Plasma by their serial number This allows us to tell the Plasma Shell to not run on particular monitors by their serial number. The blacklist of monitors is set in plasmashellrc. Serial number is used as it's the only unique way of identifying a monitor. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454621] Plasmashell doesn't start on all monitors in a multi xscreen environment
https://bugs.kde.org/show_bug.cgi?id=454621 --- Comment #4 from Allistar --- I have identified that this issue is caused by the change between 5.23 and 5.24 in screenpool.cpp ScreenPool::load. I have fixed this with a patch which allows me to blacklist monitors from Plasma by their serial number. Unfortunately QScreen doesn't expose the xscreen that the monitor is on (eg. :0.0 or :0.1) which means that it's not easy to stop shells from running on a monitor for a particular xscreen. The only unique identifier for screens is their serial number. With my patch you can add a section like this to the plasmarc: [IgnoreScreens] 0=G455H97ABNCL- 1=D59H25C8BJ3S- And Plasma shell won't start on those displays. This fixes the bug for me and reverts Plasma workspace back to the previous behaviour. The patch file is attached. I think a proper fix it to limit Plasma (or QT) to one xscreen. Even with "DISPLAY=":0.1" or --display=":0.0" set when running plasmashell it's still picking up monitors from ":0.1". This is a bug, it shouldn't be looking at displays that aren't the DISPLAY variable. Another fix it to change QScreen to expose the xscreen number which would then allow plasmashell to decide which screens it can and can't run on. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454621] Plasmashell doesn't start on all monitors in a multi xscreen environment
https://bugs.kde.org/show_bug.cgi?id=454621
--- Comment #3 from Allistar ---
Could this be due to this code in ScreenPool::load
// Populate allthe screen based on what's connected at startup
for (QScreen *screen : qGuiApp->screens()) {
// On some devices QGuiApp::screenAdded is always emitted for some
screens at startup so at this point that screen would already be managed
if (!m_allSortedScreens.contains(screen)) {
handleScreenAdded(screen);
} else if (!m_idForConnector.contains(screen->name())) {
insertScreenMapping(firstAvailableId(), screen->name());
}
}
This is matching screens based on the name of the screen. It looks like the QT
structure at QGuiApplication::screens contains all screens from both of my
xscreens (xscreen0 and xscreen1) when it used to only provide those from
xscreen0. Matching by name won't work as these aren't unique. I'll check
previous versions of ScreenPool to try and isolate the regression to that class
(and hence Plasma) before looking at QT.
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 454621] Plasmashell doesn't start on all monitors in a multi xscreen environment
https://bugs.kde.org/show_bug.cgi?id=454621 --- Comment #2 from Allistar --- I wonder if this is related to one of these issues: https://bugreports.qt.io/browse/QTBUG-101203 https://codereview.qt-project.org/c/qt/qtbase/+/412385 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454621] Plasmashell doesn't start on all monitors in a multi xscreen environment
https://bugs.kde.org/show_bug.cgi?id=454621 --- Comment #1 from Allistar --- I suspect this may be related to how [ScreenConnectors] work. In my .config/plasmashellrc file I have this: [ScreenConnectors] 0=DVI-I-1 1=HDMI-1 2=DVI-D-0 3=HDMI-0 When running "xrandr --listmonitors" on xcreen0 it returns: Monitors: 4 0: +*DVI-I-1 1920/598x1080/336+1920+1080 DVI-I-1 1: +HDMI-0 1680/473x1050/296+240+30 HDMI-0 2: +DVI-D-0 1920/521x1080/293+1920+0 DVI-D-0 3: +HDMI-1 1920/480x1080/270+0+1080 HDMI-1 When running it on xscreen1 it returns: Monitors: 2 0: +DVI-I-1 1680/433x1050/271+0+0 DVI-I-1 1: +DVI-D-0 1920/509x1080/286+0+1050 DVI-D-0 Notice that both xscreen0 and xscreen1 have a monitor with the same name (e.g. "DVI-I-1"). My current hypothesis is that this fact is confusing the startup of the plasma shells. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454621] New: Plasmashell doesn't start on all monitors in a multi xscreen environment
https://bugs.kde.org/show_bug.cgi?id=454621 Bug ID: 454621 Summary: Plasmashell doesn't start on all monitors in a multi xscreen environment Product: plasmashell Version: master Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Multi-screen support Assignee: plasma-b...@kde.org Reporter: allista...@gmail.com CC: aleix...@kde.org, notm...@gmail.com Target Milestone: 1.0 SUMMARY My Linux desktop has 6 monitors (connected to two Nvidia 750Ti GPUs). This is across two xscreens. The first GPU is for xscreen0 which has 4 monitors, the second GPU is for xscreen1 which has 2 monitors. I run KDE and plasma on the first screen only, and the second xscreen I don't run a desktop environment (instead I use compiz for display). This configuration has worked well up to plasma version 5.23.5. After upgrading to 5.24.4 (and also 5.24.5) Plasma is starting on xscreen1, and two of the xscreen0 monitors don't have Plasma running (there's no context menu, no wallpaper). STEPS TO REPRODUCE Run plasma in a environment with more than one xscreen. OBSERVED RESULT Plasma tries to run on both xscreens but only runs on as many monitors in total as there are on the first xscreen. EXPECTED RESULT Either: Plasma should only run on xscreen0 (as it used to) OR Plasma should run fully on both xscreens OR There should be configuration somewhere to control which xscreen it runs on. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Gentoo 5.15.41 (available in About System) KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 353975] Black screen on second display (no wallpaper, can't get a context menu on right-click)
https://bugs.kde.org/show_bug.cgi?id=353975 --- Comment #174 from Allistar --- I'm running Gentoo and after upgrading plasma from 5.24.4 to 5.24.5 I'm facing the same issue as before: I run two xscreens and I only want plasma to run on xscreen0. It now tries to run on both xscreens and does so incorrectly: xscreen0 has 4 displays and xscreen1 has 2. Now it only runs on two of the screen0 displays and on the 2 screen1 displays. How do I tell plasma to leave xscreen1 alone? I.e. I only want it to run on xscreen0. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 353975] Black screen on second display (no wallpaper, can't get a context menu on right-click)
https://bugs.kde.org/show_bug.cgi?id=353975 Allistar changed: What|Removed |Added CC||allista...@gmail.com --- Comment #155 from Allistar --- I can confirm that I have just had this same issue. OS: Gentoo Linux 5.15.32-gentoo-r1 #1 SMP Thu Apr 7 13:56:33 NZST 2022 x86_64 Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz GenuineIntel GNU/Linux GPU: Nvidia 750Ti Screen layout on xscreen 0: 4 monitors in a grid in this layout: 1680x1050+240+30 1920x1080+0+1080 1920x1080+1920+0 1920x1080+1920+1080 Screen layout on screen 1: 2 monitors: 1680x1050+0+0 1920x1080+0+1050 The plasma desktop loads on the left two monitors but won't load on the right two. The primary monitor is the bottom right monitor. I can drag windows to all monitors ok, but no widgets display and the desktop wallpaper isn't showing. It's as if plasma-desktop isn't running on those two monitors. This started happening after updating from plasma 5.23.5 to 5.24.4-r1. I have a separate xscreen with two monitors on which I don't run plasma. I have noticed that plasma decided to run on that xscreen. This is a change in behaviour. Does anyone know how to make plasma only run on xscreen 0 and not on xscreen 1? -- You are receiving this mail because: You are watching all bug changes.
