[kde] [Bug 481937] After plasma6 update, VirtualBox VM is unusable with 3D acceleration turned off
https://bugs.kde.org/show_bug.cgi?id=481937 Aaron Rainbolt changed: What|Removed |Added CC||arraybo...@gmail.com --- Comment #10 from Aaron Rainbolt --- Blindly enabling 3d acceleration in a VM could be dangerous for security reasons - the 3d drivers provide a potential for VM escape. A solution that works for me is to change the graphics controller to VBoxSVGA - this does not require enabling 3d acceleration, and I get a full Plasma 6 desktop. Seems to work so far - Firefox is working, video on Reddit is working, Plasma Welcome is working. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 473669] KRunner can give erroneous output when evaluating equations involving implicit mutiplication
https://bugs.kde.org/show_bug.cgi?id=473669 --- Comment #2 from Aaron Rainbolt --- I was working on it last night, but isma pointed out (in the Plasma dev room) that KRunner supports unknown variables when solving equations (for instance you can type =2x=5 and it will tell you that x = 2.5). Setting conventional mode would cause the expression 1/2x to be parsed as 1/(2x) rather than (1/2)x. Perhaps this isn't actually a bug? If a user doesn't want the implicit multiply to be applied first, they can make it explicit by inserting a * where it belongs, or they can use extra parentheses. Worthy of note, libqalculate's Adaptive mode (which I *think* we're using now) allows an easy way of disambiguating this kind of expression: 1/2x is parsed as 1/(2x), but 1/2 x (notice the space) is parsed as (1/2)x. However when inserting a space into the equation in KRunner (as =6/2 (2+1)), the result is still 1. That may actually be a bug, however I'm unsure if fixing it would help matters much since I don't think most users will know about this interesting libqalculate behavior and be able to use it to their advantage. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 473669] New: KRunner can give erroneous output when evaluating equations involving implicit mutiplication
https://bugs.kde.org/show_bug.cgi?id=473669 Bug ID: 473669 Summary: KRunner can give erroneous output when evaluating equations involving implicit mutiplication Classification: Plasma Product: krunner Version: 5.27.7 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: calculator Assignee: plasma-b...@kde.org Reporter: arraybo...@gmail.com CC: alexander.loh...@gmx.de, natalie_clar...@yahoo.de Target Milestone: --- SUMMARY KRunner's calculator fails to apply the order of operations properly when dealing with implicit multiplication. It appears to use libqalculate's default Adaptive parsing mode, which is able to apply implicit multiplication before applying any other operation (even if this violates PEMDAS). This probably comes in handy for expressions involving variables, like "5/2x" (where 2x is meant to be taken as it's own thing), but for expressions consisting solely of known values (like what KRunner's calculator probably usually handles), it can result in extremely odd output. For instance, 6/2(2+1) = 9 according to PEMDAS, but KRunner outputs a 1 as the implicit multiply of 2(2+1) gets done before the division. STEPS TO REPRODUCE 1. Open KRunner by pressing Alt+F2. 2. Type "=6/2(2+1)" OBSERVED RESULT 1 EXPECTED RESULT 9 SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 22.04 LTS (available in About System) KDE Plasma Version: 5.27.7 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION I believe this can be fixed by using libqalculate's "conventional" parsing mode on all calculations. This should be as easy as adding one line of code into https://invent.kde.org/plasma/plasma-workspace/-/blob/master/runners/calculator/qalculate_engine.cpp in the QalculateEngine::evaluate function. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454946] plasmashell crashes in ShellCorona::loadLookAndFeelDefaultLayout() when switching between Global Theme desktop layouts
https://bugs.kde.org/show_bug.cgi?id=454946
--- Comment #37 from Aaron Rainbolt ---
I had found the bug-fixing commit, and the only commit that affected the bugged
file after the bug-fixing commit is this one:
https://invent.kde.org/plasma/plasma-workspace/-/commit/1262bc6cf574fb97f74302c4019fa637a87eb42a
Perhaps try changing line 163 from "OpacityMask {" back to "property Item mask:
OpacityMask {" and see if that fixes things? There's another affected QML file
in that commit that might affect things, I'm not sure.
--
You are receiving this mail because:
You are watching all bug changes.
[NeoChat] [Bug 473271] New: Leaving an apparently empty space while viewing it results in the joined room list being hidden until next NeoChat restart
https://bugs.kde.org/show_bug.cgi?id=473271 Bug ID: 473271 Summary: Leaving an apparently empty space while viewing it results in the joined room list being hidden until next NeoChat restart Classification: Applications Product: NeoChat Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: fe...@posteo.de Reporter: arraybo...@gmail.com CC: c...@carlschwan.eu Target Milestone: --- NOTE: I suspect this is a duplicate of https://bugs.kde.org/show_bug.cgi?id=472836 but since the way I caused the problem mentioned here was slightly different, I'm reporting it as a different bug. SUMMARY If you join a space in NeoChat, you will see a button for your "home" (where your main room list is), and a button for the space you just joined (both of these buttons will appear at the top of the room list). If the space you joined appears to be empty, and you leave that space while you still have it selected, the button that allows you to go back to your home list will vanish and you will not be able to see any of the rooms you are in. Resolving this requires restarting NeoChat. STEPS TO REPRODUCE 1. Join some rooms. 2. Join a space that appears to be empty in NeoChat (#solus:matrix.org did the trick for me). 3. Make sure that the space you just joined is selected. 4. Right-click on the space and click "Leave space". OBSERVED RESULT You are left looking at an empty room list. EXPECTED RESULT You should be switched back to your "home" room list after leaving the space. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 22.04 LTS (available in About System) KDE Plasma Version: 5.27.7 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 473003] New: The snap version of NeoChat Stable can't fetch auth info from KWallet due to AppArmor policy
https://bugs.kde.org/show_bug.cgi?id=473003 Bug ID: 473003 Summary: The snap version of NeoChat Stable can't fetch auth info from KWallet due to AppArmor policy Classification: Applications Product: NeoChat Version: unspecified Platform: Snap OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: fe...@posteo.de Reporter: arraybo...@gmail.com CC: c...@carlschwan.eu Target Milestone: --- SUMMARY When using the NeoChat snap, you can log in and chat without problems. However, if you close NeoChat entirely and then relaunch it, it sticks on the "Loading..." screen and displays an AppArmor-related error indicating that it can't request auth information from KWallet. STEPS TO REPRODUCE 1. Install NeoChat with `sudo snap install neochat`. 2. Launch NeoChat and log into your account. 3. Close NeoChat. 4. Right-click on the NeoChat icon in the system tray (if it's even there - it may just be a blank space like it was on my system) and click "Quit". 5. Open System Monitor and search for NeoChat to make sure it actually has closed. If not, close it from within System Monitor. 6. Launch NeoChat again. 6. OBSERVED RESULT NeoChat displays the "Loading..." screen and never gets past it. A very long AppArmor related error is shown mentioning NeoChat, kwalletd5, and AppArmor policy (I already uninstalled the snap NeoChat and so don't have the exact error here). EXPECTED RESULT NeoChat should display the "Loading..." screen for a brief period of time (depending on system and network speed obviously), then display the chats of the logged-in user. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 22.04 LTS (available in About System) KDE Plasma Version: 5.27.7 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION This bug does **not** occur using the Flatpak version of NeoChat. -- You are receiving this mail because: You are watching all bug changes.
[plasma-simplemenu] [Bug 472822] New: "Show KRunner" button in "Places" menu can end up masquerading as some other button
https://bugs.kde.org/show_bug.cgi?id=472822 Bug ID: 472822 Summary: "Show KRunner" button in "Places" menu can end up masquerading as some other button Classification: Plasma Product: plasma-simplemenu Version: unspecified Platform: Ubuntu OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: h...@kde.org Reporter: arraybo...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- Created attachment 160635 --> https://bugs.kde.org/attachment.cgi?id=160635&action=edit Bug screenshot SUMMARY In the "Places" menu of the application launcher, the "Computer" submenu has a "Show KRunner" button at the top. It's possible to make this button's appearance (but not its behavior) change entirely by fiddling with the UI - this will make the button look like it's going to open a folder on the system, when in fact it still will show KRunner when clicked. NOTICE! This bug is not 100% reproducible. However, it happens frequently enough when trying to reproduce it that it should be easy to reproduce. STEPS TO REPRODUCE 1. Click on the Application Menu. 2. Click the "Places" tab at the bottom. The topmost button should say "Show KRunner". 3. Mouse over the "History" submenu. 4. Move the mouse into the history list, scroll all the way down, then scroll all the way up again. 5. Mouse over the "Computer" submenu again. OBSERVED RESULT Some item from the History menu now appears to be the topmost button. Clicking this button will show KRunner. EXPECTED RESULT The button should always say "Show KRunner" and not take on the identity of any other button. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 22.04 KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION Using the X11 display server and the Breeze Dark theme. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 472812] Can't re-arrange pinned-and-running apps in Icons-Only Task Manager
https://bugs.kde.org/show_bug.cgi?id=472812 Aaron Rainbolt changed: What|Removed |Added CC||arraybo...@gmail.com --- Comment #1 from Aaron Rainbolt --- Cannot reproduce on Plasma 5.27.6, X11, Qt 5.15.3, Kubuntu 22.04 LTS using the Breeze Dark theme and a floating panel. I can drag pinned apps (both launched and non-launched) freely. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 453918] When CapsLock is on, Alt+Tab window switching operates backwards.
https://bugs.kde.org/show_bug.cgi?id=453918 --- Comment #4 from Aaron Rainbolt --- I mean KDE 5.27.6 in the above comment, sorry -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 453918] When CapsLock is on, Alt+Tab window switching operates backwards.
https://bugs.kde.org/show_bug.cgi?id=453918 Aaron Rainbolt changed: What|Removed |Added CC||arraybo...@gmail.com --- Comment #3 from Aaron Rainbolt --- Cannot reproduce on KDE 5.27, Qt 5.15.3, Kubuntu 22.04 LTS. The window switcher moves as expected whether Caps Lock is on or off. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 458936] Stability issues related to notifications (or images in them?) on debian testing/unstable
https://bugs.kde.org/show_bug.cgi?id=458936 --- Comment #4 from Aaron Rainbolt --- (Also I believe Element (a Matrix chat client) is good at causing this problem on my system.) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 458936] Stability issues related to notifications (or images in them?) on debian testing/unstable
https://bugs.kde.org/show_bug.cgi?id=458936 Aaron Rainbolt changed: What|Removed |Added CC||arraybo...@gmail.com --- Comment #3 from Aaron Rainbolt --- This is happening to me on Plasma 5.27.4 on Kubuntu 22.04 (using an experimental backports repo to get the newer version of Plasma). Usually it takes out kwin_x11 first, then Plasmashell shortly thereafter. I have to kill and relaunch both to get things stable again - just restarting kwin_x11 usually results in Plasmashell locking up later on. Enabling permanent Do Not Disturb works around the issue for me, but is less than ideal. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454946] plasmashell crashes in ShellCorona::loadLookAndFeelDefaultLayout() when switching between Global Theme desktop layouts
https://bugs.kde.org/show_bug.cgi?id=454946 --- Comment #34 from Aaron Rainbolt --- After much fiddling, diffing, bisecting, and fighting, the code change that fixed this bug has finally been found. And it is... https://invent.kde.org/plasma/plasma-workspace/-/commit/d8c6f30cfe66a3e6bc05ba0b2ced7c5ffaf1a871 Of all the code changes I would imagine that would have fixed this, that was not what I expected. However, that's what `git bisect` finally gave me. I was able to test this change (albeit with quite a bit of extra changes to try and make things compatible) on Plasma/5.24 and can confirm that this does indeed fix the bug, so this isn't a fluke - this is the fixing change. Here's my current attempt at backporting the above commit to Plasma/5.24: https://invent.kde.org/arraybolt/plasma-workspace/-/commit/cf7703e1019fe7fdc92edb4cc30388d87612fbf1 I don't know if all of the changes here are necessary, but I do know that Plasma appears to still work after doing that, and that I can change global themes without having plasmashell crash after applying this change, rebuilding, and installing Ubuntu's plasma-workspace package. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454946] plasmashell crashes in ShellCorona::loadLookAndFeelDefaultLayout() when switching between Global Theme desktop layouts
https://bugs.kde.org/show_bug.cgi?id=454946 --- Comment #33 from Aaron Rainbolt --- OK so that didn't work. I tried to diff between what I thought was a working point on the master branch, and the tip of the Plasma/5.26 branch, and got a diff that was, I kid you not, nearly two million lines long. So. Looking at the backtrace Erich provided, I noticed this: #13 0x7f2c8e4e808a in Plasma::Applet::destroy (this=0x556422a17b90) at ./src/plasma/applet.cpp:309 #14 0x556420a68254 in ShellCorona::unload (this=this@entry=0x5564227b7b20) at ./shell/shellcorona.cpp:834 #15 0x556420a6bdd8 in ShellCorona::unload (this=0x5564227b7b20) at ./shell/shellcorona.cpp:606 #16 ShellCorona::loadLookAndFeelDefaultLayout (this=0x5564227b7b20, packageName=...) at ./shell/shellcorona.cpp:602 The fact that ShellCorona::unload gets called twice in a row is very suspicious to me, so I'm going to try to reproduce the backtrace with Plasma/5.26 and see if it's still happening, then hope that the line numbers lead me to the right spot. If that fails, I'll try and find a "bad" spot on the master branch. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454946] plasmashell crashes in ShellCorona::loadLookAndFeelDefaultLayout() when switching between Global Theme desktop layouts
https://bugs.kde.org/show_bug.cgi?id=454946 --- Comment #32 from Aaron Rainbolt --- Most recent findings: 1. I can successfully run a KDE Plasma build that is mostly from the tip of Plasma/5.26, but with only plasma-workspace built from master. 2. When everything is built from Plasma/5.26 (taking care to build everything in RelWithDebInfo mode), the crash appears (including the massive number of "requesting unexisting screen 0" messages). 3. When only plasma-workspace is build from master (again in RelWithDebInfo mode), the crash vanishes. Therefore, it's very likely that somewhere between Plasma/5.26 and master, the fix was introduced. And now that I finally know about RelWithDebInfo, I think the repo can finally be bisected. (The last attempt at a bisect was stymied because I was accidentally building everything in Debug mode, which was producing a possibly different but related crash that was throwing me off.) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454946] plasmashell crashes in ShellCorona::loadLookAndFeelDefaultLayout() when switching between Global Theme desktop layouts
https://bugs.kde.org/show_bug.cgi?id=454946 --- Comment #30 from Aaron Rainbolt --- Alright, I built Plasma from master with kdesrc-build again, and now the crash has vanished. Whew. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454946] plasmashell crashes in ShellCorona::loadLookAndFeelDefaultLayout() when switching between Global Theme desktop layouts
https://bugs.kde.org/show_bug.cgi?id=454946 --- Comment #29 from Aaron Rainbolt --- Also I didn't get a stack trace from my crashes to ensure that they were the same, so it's within the realm of possibility I'm doing this to myself with a version mismatch. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454946] plasmashell crashes in ShellCorona::loadLookAndFeelDefaultLayout() when switching between Global Theme desktop layouts
https://bugs.kde.org/show_bug.cgi?id=454946 --- Comment #28 from Aaron Rainbolt --- I should specify, I'm building from source manually, cloning directly from the Git repos and using cmake and make myself for this latest build that has the crash, so perhaps the problem is in a dependency that wasn't getting rebuilt by skipping kdesrc-build? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454946] plasmashell crashes in ShellCorona::loadLookAndFeelDefaultLayout() when switching between Global Theme desktop layouts
https://bugs.kde.org/show_bug.cgi?id=454946 --- Comment #27 from Aaron Rainbolt --- Crud. Not sure what changed, but I can reproduce the bug with git master again. :( -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454946] plasmashell crashes in ShellCorona::loadLookAndFeelDefaultLayout() when switching between Global Theme desktop layouts
https://bugs.kde.org/show_bug.cgi?id=454946 --- Comment #26 from Aaron Rainbolt --- Verified that the bug is in plasma-workspace - building from an earlier commit shows the crash, but the latest one doesn't crash. I am actively bisecting the repo (about 5 steps left) and should hopefully have a commit ID with the fix by tomorrow. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454946] plasmashell crashes in ShellCorona::loadLookAndFeelDefaultLayout() when switching between Global Theme desktop layouts
https://bugs.kde.org/show_bug.cgi?id=454946 --- Comment #25 from Aaron Rainbolt --- I can reproduce the crash using the tip of the Plasma/5.26 branch for all components. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454946] plasmashell crashes in ShellCorona::loadLookAndFeelDefaultLayout() when switching between Global Theme desktop layouts
https://bugs.kde.org/show_bug.cgi?id=454946
--- Comment #24 from Aaron Rainbolt ---
And this is the output of the working plasmashell from master:
kf.plasma.quick: Applet preload policy set to 1
QObject::connect: No such slot DesktopProtocol::_k_slotRedirection(KIO::Job *,
QUrl)
Trying to use rootObject before initialization is completed, whilst using
setInitializationDelayed. Forcing completion
Failed to register unity service
org.kde.plasma.notifications: Failed to register JobViewServer service on DBus,
is kuiserver running?
file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/DigitalClock.qml:534:9:
QML Label: Binding loop detected for property "height"
file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/DigitalClock.qml:499:13:
QML Label: Binding loop detected for property "height"
file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/DigitalClock.qml:499:13:
QML Label: Binding loop detected for property "height"
file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/DigitalClock.qml:534:9:
QML Label: Binding loop detected for property "height"
file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/DigitalClock.qml:556:5:
QML Label: Binding loop detected for property "height"
Cyclic dependency detected between
"file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml"
and
"file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationHeader.qml"
Cyclic dependency detected between
"file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml"
and
"file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/ThumbnailStrip.qml"
org.kde.plasma.notifications: Failed to register JobViewServer DBus object
org.kde.plasma.notifications: Failed to register JobViewServer DBus object
org.kde.plasma.notifications: Failed to register JobViewServer DBus object
libkcups: CUPS-Get-Printers last error: 1030 No destinations added.
libkcups: Get-Jobs last error: 0 successful-ok
libkcups: Create-Printer-Subscriptions last error: 0 successful-ok
libkcups: Get-Jobs last error: 0 successful-ok
libkcups: 0
libkcups: 0
QFont::setPointSizeF: Point size <= 0 (0.00), must be greater than 0
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5:
QML Heading: Binding loop detected for property "verticalAlignment"
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5:
QML Heading: Binding loop detected for property "verticalAlignment"
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5:
QML Heading: Binding loop detected for property "verticalAlignment"
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5:
QML Heading: Binding loop detected for property "verticalAlignment"
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5:
QML Heading: Binding loop detected for property "verticalAlignment"
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5:
QML Heading: Binding loop detected for property "verticalAlignment"
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5:
QML Heading: Binding loop detected for property "verticalAlignment"
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5:
QML Heading: Binding loop detected for property "verticalAlignment"
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5:
QML Heading: Binding loop detected for property "verticalAlignment"
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5:
QML Heading: Binding loop detected for property "verticalAlignment"
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5:
QML Heading: Binding loop detected for property "verticalAlignment"
Could not find the Plasmoid for Plasma::FrameSvgItem(0x5572e93700d0)
QQmlContext(0x5572e6a06010)
QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasma.private.systemtray/contents/ui/main.qml")
Could not find the Plasmoid for Plasma::FrameSvgItem(0x5572e93700d0)
QQmlContext(0x5572e6a06010)
QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasma.private.systemtray/contents/ui/main.qml")
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5:
QML Heading: Binding loop detected for property "verticalAlignment"
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/components.3/ScrollView.qml:45:27:
QML Sc
[plasmashell] [Bug 454946] plasmashell crashes in ShellCorona::loadLookAndFeelDefaultLayout() when switching between Global Theme desktop layouts
https://bugs.kde.org/show_bug.cgi?id=454946 --- Comment #23 from Aaron Rainbolt --- Alright, I modified the plasma-workspace code slightly (using the version in Kubuntu's repos), and edited all of the lines that said "requesting unexisting screen" to specify what function the messages was in. The results are: ``` kf.plasma.quick: Applet preload policy set to 1 trying to show an empty dialog qml: PlasmaExtras.ScrollArea is deprecated. Use PlasmaComponents3.ScrollView instead. trying to show an empty dialog file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:118:19: QML Loader: Binding loop detected for property "height" file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:118:19: QML Loader: Binding loop detected for property "height" Trying to take space not available BasicAppletContainer_QMLTYPE_159_QML_168(0x55d3ad4ea890, parent=0x55d3ad0e3000, geometry=482.846,485.91 432x384) Plasma Shell startup completed file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/DigitalClock.qml:531:9: QML Label: Binding loop detected for property "height" file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/DigitalClock.qml:496:13: QML Label: Binding loop detected for property "height" trying to show an empty dialog Trying to use rootObject before initialization is completed, whilst using setInitializationDelayed. Forcing completion Entry is not valid "org.kde.kontact.desktop" QSharedPointer(0x55d3adf91360) Entry is not valid "org.kde.kontact.desktop" QSharedPointer(0x55d3ad3fbc80) file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/DigitalClock.qml:496:13: QML Label: Binding loop detected for property "height" file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/DigitalClock.qml:531:9: QML Label: Binding loop detected for property "height" file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/DigitalClock.qml:553:5: QML Label: Binding loop detected for property "height" trying to show an empty dialog file:///usr/share/plasma/plasmoids/org.kde.panel/contents/ui/main.qml:18:1: QML DropArea (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "minimumWidth" Cyclic dependency detected between "file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml" and "file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationHeader.qml" libkcups: CUPS-Get-Printers last error: 1030 No destinations added. libkcups: Create-Printer-Subscriptions last error: 0 successful-ok libkcups: Get-Jobs last error: 0 successful-ok libkcups: Get-Jobs last error: 0 successful-ok file:///usr/share/plasma/plasmoids/org.kde.plasma.private.systemtray/contents/ui/ExpandedRepresentation.qml:165:9: QML HiddenItemsView: Binding loop detected for property "implicitHeight" libkcups: 0 libkcups: 0 trying to show an empty dialog file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:118:19: QML Loader: Binding loop detected for property "height" file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:118:19: QML Loader: Binding loop detected for property "height" trying to show an empty dialog QFont::setPointSizeF: Point size <= 0 (0.00), must be greater than 0 file:///usr/share/plasma/plasmoids/org.kde.plasma.battery/contents/ui/CompactRepresentation.qml:71:17: Unable to assign [undefined] to int Trying to take space not available BasicAppletContainer_QMLTYPE_159_QML_168(0x55d3ad4ea890, parent=0x55d3ad0e3000, geometry=480,384 432x384) trying to show an empty dialog trying to show an empty dialog file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/Task.qml:370: Unable to assign [undefined] to QString file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/Task.qml:370: Unable to assign [undefined] to QString file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/ApplicationItem.qml:151:9: QML Shortcut: Shortcut: Only binding to one of multiple key bindings associated with 13. Use 'sequences: [ ]' to bind to all of them. file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/ApplicationItem.qml:147:9: QML Shortcut: Shortcut: Only binding to one of multiple key bindings associated with 14. Use 'sequences: [ ]' to bind to all of them. file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/PageRow.qml:674:5: QML Shortcut: Shortcut: Only binding to one of multiple key bindings associated with 14. Use 'sequences: [ ]' to bind to all of them. file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/PageRow.qml:670:5: QML Shortcut: Shortcut: Only binding to one of multiple key bindings associated wi
[plasmashell] [Bug 454946] plasmashell crashes in ShellCorona::loadLookAndFeelDefaultLayout() when switching between Global Theme desktop layouts
https://bugs.kde.org/show_bug.cgi?id=454946 --- Comment #21 from Aaron Rainbolt --- @NateGraham Where is that code at? I'm looking for it and having a hard time finding it in Plasma 5.24. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454946] plasmashell crashes in ShellCorona::loadLookAndFeelDefaultLayout() when switching between Global Theme desktop layouts
https://bugs.kde.org/show_bug.cgi?id=454946 --- Comment #19 from Aaron Rainbolt --- If I reproduce the crash with "plasmashell --replace" running in a terminal, I see a ton of "requesting unexisting screen 0" messages appear just before crash. This on Kubuntu 22.04.1, which uses a version of KDE that still contains the bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454946] plasmashell crashes in ShellCorona::loadLookAndFeelDefaultLayout() when switching between Global Theme desktop layouts
https://bugs.kde.org/show_bug.cgi?id=454946 --- Comment #18 from Aaron Rainbolt --- Nevermind, I actually failed to notice the crashes. I can now see that plasmashell crashed several times during my latest testing with the Plasma/5.24 testing. Sorry. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454946] plasmashell crashes in ShellCorona::loadLookAndFeelDefaultLayout() when switching between Global Theme desktop layouts
https://bugs.kde.org/show_bug.cgi?id=454946 --- Comment #17 from Aaron Rainbolt --- I also cannot reproduce this with the tip of the Plasma/5.24 branch. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454946] plasmashell crashes in ShellCorona::loadLookAndFeelDefaultLayout() when switching between Global Theme desktop layouts
https://bugs.kde.org/show_bug.cgi?id=454946 --- Comment #15 from Aaron Rainbolt --- Currently unable to reproduce this with the latest git master. Using KDE neon 22.04 Developer Edition (KForge virtual appliance on VirtualBox 6.1). I built the full KDE Plasma stack with kdesrc-build as described in https://community.kde.org/Get_Involved/development. I then put the VM into full-screen mode, opened a slew of applications, and then proceeded to switch themes and layouts 25 times (switching irregularly between Breeze, Breeze Dark, and Breeze Twilight). Unless the effects of a plasmashell crash are nearly invisible to the end user (which I don't think is the case), there was not a single plasmashell crash as a result of the theme and layout switching. I made sure that the "Desktop and window layout" box was checked every time I switched themes. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 460618] Can't remember desktop widget positions after relogin
https://bugs.kde.org/show_bug.cgi?id=460618 --- Comment #9 from Aaron Rainbolt --- Hmm, and it's happening *without* a resolution change? That's weird. Fushan Wen thought that perhaps a Qt bug had something to do with one aspect of this mess, but I've been having a ridiculously hard time getting Qt to build at all, thus why I still have yet to try it. I'll make it my top priority and see if it fixes anything, though I don't have very high hopes that it will if a resolution change isn't part of the problem now. I'll also try the original bugfix I had for this and see if it helps anything. Interestingly enough, I have been totally unable to reproduce this problem in any version of Plasma that I've tried using an emulated 4K display in VirtualBox. Are you guys who can reproduce the bug using discrete graphics hardware by any chance? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413645] Can't remember desktop widget positions after reboot
https://bugs.kde.org/show_bug.cgi?id=413645 Aaron Rainbolt changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/plasma-workspace/commit/ |ma/plasma-desktop/commit/23 |0a01c8910309fb9f289fe0aa584 |4cd860532449f017ecbbca6a8ca |92e106d154548 |ad5473fcf8b --- Comment #65 from Aaron Rainbolt --- Git commit 234cd860532449f017ecbbca6a8caad5473fcf8b by Aaron Rainbolt, on behalf of Marco Martin. Committed on 13/10/2022 at 21:46. Pushed by ngraham into branch 'Plasma/5.24'. Use relayout locking This makes use of the layout locking freature introduced in The resize of the layout area can happen either by screen resolution change or available screen area change (a panel appears or is resized) This is not an atomic operation, as width and height are usually set in 2 different operations, and even worse the layout area is resized to match the available one with an animation, so many intermediate resizes that should never cause a relayout happen. A compression timer limits the actual relayouts to hopefully one, but if the system is really slowed down (for instance, startup) the timer may expire and cause relayouts in non useful sizes, losing the needed configuration The lock blocks all relayout and config writes when the size of the layout area doesn't correspond to corona availablescreenrect, which are the only "settled" cases. M +3-2containments/desktop/package/contents/ui/main.qml https://invent.kde.org/plasma/plasma-desktop/commit/234cd860532449f017ecbbca6a8caad5473fcf8b -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413645] Can't remember desktop widget positions after reboot
https://bugs.kde.org/show_bug.cgi?id=413645 Aaron Rainbolt changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/plasma-desktop/commit/22 |ma/plasma-workspace/commit/ |fa69d96d64422318e83cc57d9ed |0a01c8910309fb9f289fe0aa584 |1d0a08c17b0 |92e106d154548 --- Comment #64 from Aaron Rainbolt --- Git commit 0a01c8910309fb9f289fe0aa58492e106d154548 by Aaron Rainbolt, on behalf of Marco Martin. Committed on 13/10/2022 at 21:45. Pushed by ngraham into branch 'Plasma/5.24'. Introduce a lock that blocks relayouts and config writes The resize of the layout area can happen either by screen resolution change or available screen area change (a panel appears or is resized) This is not an atomic operation, as width and height are usually set in 2 different operations, and even worse the layout area is resized to match the available one with an animation, so many intermediate resizes that should never cause a relayout happen. In normal operation an event compression timer limits the actual relayouts to hopefully one, but if the system is really slowed down (for instance, startup) the timer may expire and cause relayouts in non useful sizes, losing the needed configuration In combination with The lock blocks all relayout and config writes when the size of the layout area doesn't correspond to corona availablescreenrect, which are the only "settled" cases. M +24 -2components/containmentlayoutmanager/appletslayout.cpp M +7-0components/containmentlayoutmanager/appletslayout.h https://invent.kde.org/plasma/plasma-workspace/commit/0a01c8910309fb9f289fe0aa58492e106d154548 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438312] Restarting kwin_x11 forgets activities assigned to windows
https://bugs.kde.org/show_bug.cgi?id=438312 Aaron Rainbolt changed: What|Removed |Added Resolution|--- |FIXED Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/kwin/commit/d47137679d08 |ma/kwin/commit/16c6c3d84795 |21722e3c3f528709fc6650b5d19 |257e1576a20775d8e15f09c5aad |a |3 Status|ASSIGNED|RESOLVED --- Comment #23 from Aaron Rainbolt --- Git commit 16c6c3d84795257e1576a20775d8e15f09c5aad3 by Aaron Rainbolt, on behalf of David Edmundson. Committed on 12/10/2022 at 23:00. Pushed by ngraham into branch 'Plasma/5.24'. Sync activities after kwin restart Activities are loaded async. During this time any fetch of activity information is incorrect as we will treat any settings as invalid. We need to ignore attempts to set activities during this time, but also refresh Window's concept of activities once we are loaded. (cherry picked from commit d4713767 and adapted for KWin 5.24.6) M +3-0src/abstract_client.cpp M +6-0src/abstract_client.h M +15 -0src/activities.cpp M +1-0src/activities.h M +1-1src/x11client.h https://invent.kde.org/plasma/kwin/commit/16c6c3d84795257e1576a20775d8e15f09c5aad3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413645] Can't remember desktop widget positions after reboot
https://bugs.kde.org/show_bug.cgi?id=413645 --- Comment #59 from Aaron Rainbolt --- Writing this as a comment and not a bug report since there's still some more work to be done, but here's some extra info: While attempting to test the backports of this bug fix (https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/1178 and https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/2167), I used a special setup with a painfully slow emulated display in order to reproduce the bug and see if the fix worked. Initially, I was led to believe that the fix was failing in my testing, however on closer investigation, I believe there is a different though related bug that my setup is making show up. How to reproduce the setup: 1: Install GNOME Boxes. This virtualization software has been able to reliably reproduce the issue for me most of the time. VirtualBox has a significantly faster emulated display and may not work. 2: Install Kubuntu 22.04 into GNOME Boxes, providing 8 GB of RAM and 100 GB of disk space. (NOTE: KDE neon Developer Edition won't work - this bug only is appearing on Kubuntu for me, possibly due to the use of KDE Plasma 5.24 in Kubuntu, as opposed to a build from Master in Neon.) 3: When the installation is finished, do `sudo apt update && sudo apt -y full-upgrade` in a terminal, then reboot the VM. 4: Change the display resolution within the VM to the maximum possible resolution. 5: Place some widgets on the desktop. 6: Log out and log back in. The widgets will end up being shifted or scrambled around. 7: Download the KDE Plasma 5.24.6 tarballs and signature files from https://download.kde.org/stable/plasma/5.24.6/ and GPG verify them, then extract them. 8: Build and install all of KDE Plasma 5.24.6 once piece at a time, using `sudo make install` for installation. 9: Reboot the VM. 10: Place widgets on the screen where you want them (repositioning the existing ones if you so desire). 11: Reboot the VM again. The widgets will become scrambled/shifted again, as expected. 12: Apply the code changes in the two linked merge requests, then rebuild plasma-desktop and plasma-workspace. 13: Reposition your widgets, and reboot again. The widgets will become scrambled/shifted again, despite the applied bug fix. Note that, if you do this whole process on KDE neon Developer Edition, the widgets will never be shifted or scrambled around, *not even in step 11.* This indicates that this particular bug is outside of KDE Plasma, as two different distros running the exact same version of Plasma display different behavior. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454946] plasmashell crashes in ShellCorona::loadLookAndFeelDefaultLayout() when switching between Global Theme desktop layouts
https://bugs.kde.org/show_bug.cgi?id=454946 Aaron Rainbolt changed: What|Removed |Added CC||arraybo...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456511] VLC and Firefox freeze / stop updating their window contents after being used for a while
https://bugs.kde.org/show_bug.cgi?id=456511 --- Comment #19 from Aaron Rainbolt --- (In reply to Vlad Zahorodnii from comment #18) > (In reply to Aaron Rainbolt from comment #17) > > This *might* be Qt related - I'm experiencing a similar problem on Lubuntu > > 22.04.1 with LXQt and Openbox on one system over here. Yes, I know that's > > not KDE, but KDE and LXQt both use Qt, so perhaps the problem is there? > > Might be totally unrelated, just throwing that out there in case it turns > > out to be helpful. > > VLC uses Qt, but FF does not. What compositing manager do you use? I don't think Lubuntu uses any compositor at all by default. The WM is Openbox, Compton *can* be enabled but usually isn't. VLC isn't used much on this system and I've not experienced any problems with it, but Firefox is used quite frequently and this behavior happens somewhat frequently with it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413645] Can't remember desktop widget positions after reboot
https://bugs.kde.org/show_bug.cgi?id=413645 --- Comment #51 from Aaron Rainbolt --- Alright, looks like everything's now working right! Merge request: https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/2118 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413645] Can't remember desktop widget positions after reboot
https://bugs.kde.org/show_bug.cgi?id=413645 --- Comment #50 from Aaron Rainbolt --- Bah, and now there it is again! Fickle thing. Alright, sorry for bug spam. I'll be back once I figure out what it's doing this time. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413645] Can't remember desktop widget positions after reboot
https://bugs.kde.org/show_bug.cgi?id=413645 --- Comment #49 from Aaron Rainbolt --- Nevermind, I guess the bug seeming to still be there was a fluke? Now I can't get the wrong behavior to happen anymore. :/ Task failed successfully, I guess. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413645] Can't remember desktop widget positions after reboot
https://bugs.kde.org/show_bug.cgi?id=413645 --- Comment #48 from Aaron Rainbolt --- Er, no, probably in GridLayoutManager. (Note to self, look at code before declaring where you think a bug is.) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413645] Can't remember desktop widget positions after reboot
https://bugs.kde.org/show_bug.cgi?id=413645 --- Comment #47 from Aaron Rainbolt --- Crud. Well the solution that I was about to post a merge request for turned out to only solve the problem partway. While the widgets are no longer scrambled on startup, you can still cause them to be scrambled by starting KDE in a way where the resolution *doesn't* change during early startup, then change the resolution (tested by increasing the resolution). Bam, the widgets go crazy again. So the situation has been much improved, but there's still a bug lurking somewhere (probably in AbstractLayoutManager). :-( -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413645] Can't remember desktop widget positions after reboot
https://bugs.kde.org/show_bug.cgi?id=413645 --- Comment #46 from Aaron Rainbolt --- Looks like the resolution change was indeed (at least part of) the problem. Changing AppletsLayout::AppletsLayout to ignore any screen resolution changes the first time it is ran fixed the bug, while still allowing the widgets to be repositioned when the user intentionally changes the screen resolution. I've only tested this in a single-monitor setup within a VM, but it entirely resolved the problem for me. Expect a merge request soon. \o/ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413645] Can't remember desktop widget positions after reboot
https://bugs.kde.org/show_bug.cgi?id=413645 --- Comment #42 from Aaron Rainbolt --- So, looking at the logic here, I think the problem might actually be the result of a resolution change during early startup - for instance, on an NVIDIA machine of mine, the SDDM display on bootup is rather distorted (renders in 640x480, maybe?), but the resolution changes during early startup to match the screen's correct resolution. I think when this happens with a big enough screen, it causes the relayout to trigger at the wrong time and thus scrambles the widgets. If this is the case, the problematic else if statement may simply need to check for the presence of a component of KDE that only finishes loading after any early-startup resolution changes. Perhaps checking for KWin's presence would be sufficient here? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456511] VLC and Firefox freeze / stop updating their window contents after being used for a while
https://bugs.kde.org/show_bug.cgi?id=456511 Aaron Rainbolt changed: What|Removed |Added CC||arraybo...@gmail.com --- Comment #17 from Aaron Rainbolt --- This *might* be Qt related - I'm experiencing a similar problem on Lubuntu 22.04.1 with LXQt and Openbox on one system over here. Yes, I know that's not KDE, but KDE and LXQt both use Qt, so perhaps the problem is there? Might be totally unrelated, just throwing that out there in case it turns out to be helpful. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438312] Restarting kwin_x11 forgets activities assigned to windows
https://bugs.kde.org/show_bug.cgi?id=438312 --- Comment #18 from Aaron Rainbolt --- (In reply to Aaron Rainbolt from comment #17) > OK, nevermind, upon closer inspection I'm looking at the wrong code. No > changes I make to bool Activities::start(const QString &id) seem to have any > effect (not even a blatant null pointer dereference or an std::terminate()). > So I'm not sure when this code gets called, but I don't think it's called > when kwin_x11 is launched. Either that or else KWin is insanely robust. And it looks like even this comment was thanks to me not knowing what I was doing when I originally wrote it. Thankfully, though, it looks like this bug has finally been figured out for the most part. A PR to fix it is here: https://invent.kde.org/plasma/kwin/-/merge_requests/2941 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438312] Restarting kwin_x11 forgets activities assigned to windows
https://bugs.kde.org/show_bug.cgi?id=438312 --- Comment #17 from Aaron Rainbolt --- OK, nevermind, upon closer inspection I'm looking at the wrong code. No changes I make to bool Activities::start(const QString &id) seem to have any effect (not even a blatant null pointer dereference or an std::terminate()). So I'm not sure when this code gets called, but I don't think it's called when kwin_x11 is launched. Either that or else KWin is insanely robust. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438312] Restarting kwin_x11 forgets activities assigned to windows
https://bugs.kde.org/show_bug.cgi?id=438312
--- Comment #16 from Aaron Rainbolt ---
Wow, in retrospect that code is SO BAD. A typo, I'm probably missing C++
syntax, and the pseudocode logic is itself flawed. :facepalm:
I think I meant something more like this:
> bool Activities::start(const QString &id)
> {
> Workspace *ws = Workspace::self();
> //pseudocode starts here
> foreach(Window w in ws.WindowList) {
> if(w.IsOnActivity(id) {
> toggleWindowOnActivity(w, id, true);
> toggleWindowOnActivity(w, id, true);
> }
> }
> //pseudocode ends here
> if (ws->sessionManager()->state() == SessionState::Saving) {
> return false; // ksmserver doesn't queue requests (yet)
> }
> ...
Still probably messed up the syntax horribly, but at least the logic is right
this time.
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 438312] Restarting kwin_x11 forgets activities assigned to windows
https://bugs.kde.org/show_bug.cgi?id=438312
--- Comment #15 from Aaron Rainbolt ---
Maybe it would be better if, rather than implementing the fix in ksmserver, we
implemented it in kwin/src/activities.cpp? I'm realizing it might be rather
trivial to do something like this:
> bool Activities::start(const QString &id)
> {
> Workspace *ws = Workspace::self();
> //pseudocode starts here
> foreach(Windows w in ws) {
> toggleWindowOnActivity(w, id, true);
> toggleWindowOnActivity(w, id, true);
> }
> //pseudocode ends here
> if (ws->sessionManager()->state() == SessionState::Saving) {
> return false; // ksmserver doesn't queue requests (yet)
> }
> ...
That might fix the problem.
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 438312] Restarting kwin_x11 forgets activities assigned to windows
https://bugs.kde.org/show_bug.cgi?id=438312 --- Comment #13 from Aaron Rainbolt --- Interesting. Using "killall kwin_x11 && kwin_x11" in KDE neon Unstable Edition results in identical behavior as when using "kwin_x11 --replace". -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438312] Restarting kwin_x11 forgets activities assigned to windows
https://bugs.kde.org/show_bug.cgi?id=438312 --- Comment #11 from Aaron Rainbolt --- The kwin/src/activities.cpp file is https://invent.kde.org/plasma/kwin/-/blob/master/src/activities.cpp, sorry to accidentally fail to specify that. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438312] Restarting kwin_x11 forgets activities assigned to windows
https://bugs.kde.org/show_bug.cgi?id=438312
--- Comment #10 from Aaron Rainbolt ---
OK, I've read through the code and I think I see why this bug is occurring. My
understanding of C++ is not all that great since I don't actually know the
language, so this could be partially wrong. It appears that KWin tells
ksmserver to restore the previous session when the user logs back in,
relaunching programs that were open when the user logged out. However, when
"kwin_x11 --replace" is used, the applications are already launched, so the
session restoration code isn't run and the apps end up visible on all
activities.
In kwin/src/activities.cpp, bool Activities::start(const QString &id), lines
117-123:
> QDBusInterface ksmserver("org.kde.ksmserver", "/KSMServer",
> "org.kde.KSMServerInterface");
> if (ksmserver.isValid()) {
> ksmserver.asyncCall("restoreSubSession", id);
> } else {
> qCDebug(KWIN_CORE) << "couldn't get ksmserver interface";
> return false;
> }
ksmserver's "restoreSubSession" member function is called.
In
https://invent.kde.org/plasma/plasma-workspace/-/blob/master/ksmserver/server.cpp,
the member function void KSMServer::restoreSubSession(const QString &name)
calls void KSMServer::tryRestoreNext(), which appears to go through a list of
apps that need relaunched, determine whether they are already launched or not,
relaunches them if they are not launched, and skips over them when they are
already launched. Particularly, lines 986-994 of the above mentioned file:
> bool alreadyStarted = false;
> foreach (KSMClient *c, clients) {
> if (QString::fromLocal8Bit(c->clientId()) == clientId) {
> alreadyStarted = true;
> break;
> }
> }
> if (alreadyStarted)
> continue;
I believe this is where the bug is. The "if (alreadyStarted)" block needs to
determine which activity the window(s) of the already launched app are supposed
to be on, and specifically set the window(s) of that app to that activity.
Otherwise, when "kwin_x11 --replace" is called, none of the session restoration
really works, and thus you end up with a big lump of windows on all your
activities. I'd guess the reason that the activities still seem to be set
correctly for each app (as described in my previous comment) would be because
the windows themselves still retain memory of what activity they're supposed to
be on, but the restarted kwin process isn't taking that into account.
This might not be the best place for the fix to go, and it's possible I've
misunderstood the code, but this is what I have so far. I'm not quite sure how
to implement the proposed fix, I'm still working on that part. But here's the
progress I've made, hopefully this will be helpful.
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 438312] Restarting kwin_x11 forgets activities assigned to windows
https://bugs.kde.org/show_bug.cgi?id=438312 Aaron Rainbolt changed: What|Removed |Added CC||arraybo...@gmail.com --- Comment #9 from Aaron Rainbolt --- Worthy of note - on my own build of KWin running on Kubuntu 22.04, the "kwin_x11 --restart" does result in the windows showing on the wrong activities, but switching between activities reveals that the windows appear to still be assigned to their respective activities properly (you can right-click an application button, hover over the "Show in Activities" menu, and see that the window is still assigned to the right activity). They're simply displaying on all activities, even though they seem to be assigned correctly. This is just from my own brief testing and work so far, so this might not be totally correct, but I noticed it and thought it might be useful to know. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413645] Can't remember desktop widget positions after reboot
https://bugs.kde.org/show_bug.cgi?id=413645 --- Comment #41 from Aaron Rainbolt --- (In reply to Aaron Rainbolt from comment #40) > The patch: https://termbin.com/kv20 > Plasma version - 5.25.5 (built from source with kdesrc-build with > build-group set to stable-kf5-qt5) > > WARNING: I do not know C++. All this patch does is comment out a chunk of > code - while this has the result of eliminating the bug in my testing, it > also has the result of disabling whatever functionality was served by the > code being commented out, and it might have unforseen consequences. Treat > this like actively reacting uranium. Use in a VM or dedicating testing > machine is highly encouraged! :facepalm: Forgot to give the file path. Assuming you have everything set up according to https://community.kde.org/Get_Involved/development, the file you want to patch is ~/kde/src/plasma-workspace/components/containmentlayoutmanager/appletslayout.cpp. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413645] Can't remember desktop widget positions after reboot
https://bugs.kde.org/show_bug.cgi?id=413645 --- Comment #40 from Aaron Rainbolt --- The patch: https://termbin.com/kv20 Plasma version - 5.25.5 (built from source with kdesrc-build with build-group set to stable-kf5-qt5) WARNING: I do not know C++. All this patch does is comment out a chunk of code - while this has the result of eliminating the bug in my testing, it also has the result of disabling whatever functionality was served by the code being commented out, and it might have unforseen consequences. Treat this like actively reacting uranium. Use in a VM or dedicating testing machine is highly encouraged! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413645] Can't remember desktop widget positions after reboot
https://bugs.kde.org/show_bug.cgi?id=413645
--- Comment #38 from Aaron Rainbolt ---
Looking at my previous comment, it may appear misleading - the comment within
the "else if" block actually applies to the following "else" block if I'm
understanding correctly. Here's the snippet of code (including the offending
else if block) with more context:
> } else if (m_layoutChanges & SizeChange) {
> const QRect newGeom(x(), y(), width(), height());
> // The size has been restored from the last one it has been
> saved: restore that exact same layout
> if (newGeom.size() == m_savedSize) {
> m_layoutManager->resetLayoutFromConfig();
>
> // If the resize is consequence of a screen resolution
> change, queue a relayout maintaining the distance between screen edges
> } else if (!m_geometryBeforeResolutionChange.isEmpty()) {
> m_layoutManager->layoutGeometryChanged(newGeom,
> m_geometryBeforeResolutionChange);
> m_geometryBeforeResolutionChange = QRectF();
>
> // Heuristically relayout items only when the plasma startup
> is fully completed
> } else {
> polish();
> }
> }
> m_layoutChanges = NoChange;
> });
From
https://invent.kde.org/plasma/plasma-workspace/-/blob/Plasma/5.25/components/containmentlayoutmanager/appletslayout.cpp,
lines 76 to 93.
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 413645] Can't remember desktop widget positions after reboot
https://bugs.kde.org/show_bug.cgi?id=413645
--- Comment #37 from Aaron Rainbolt ---
In
https://invent.kde.org/plasma/plasma-workspace/-/blob/Plasma/5.25/components/containmentlayoutmanager/appletslayout.cpp,
lines 83-88:
>} else if (!m_geometryBeforeResolutionChange.isEmpty()) {
>m_layoutManager->layoutGeometryChanged(newGeom,
> m_geometryBeforeResolutionChange);
>m_geometryBeforeResolutionChange = QRectF();
>
>// Heuristically relayout items only when the plasma startup is fully
> completed
>} else {
Commenting out the "else if" in this section of code causes the bug to
disappear.
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 413645] Can't remember desktop widget positions after reboot
https://bugs.kde.org/show_bug.cgi?id=413645 --- Comment #36 from Aaron Rainbolt --- > (I believe the bug trigger here was a multi-monitor setup with different > resolutions for each monitor, one full-HD one 4K. When I upgraded to > matching-resolution 4Ks it stopped triggering for me so I've not seen the bug > in awhile. Thus the "presumably still works" qualification above.) I think this is probably a race condition, because when my VM window was in a lower resolution (close to but not quite 1366x768), the bug didn't occur. When I set it to a high resolution, then it occurred. I'm guessing with 2 4K monitors, things must initialize quickly enough to hide the condition, but with mismatched monitors, the initialization goes slower and the condition appears. Changing the floating-point values to whole numbers had no effect. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413645] Can't remember desktop widget positions after reboot
https://bugs.kde.org/show_bug.cgi?id=413645 --- Comment #34 from Aaron Rainbolt --- I can also resolve the problem by entirely removing the "ItemGeometries" line and leaving the "ItemGeometriesHorizontal" line. However, again, this line is recreated at login, and if left at logout, the widget will again "wander" and then snap. So something about the two entries coexisting is causing things to go wrong. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413645] Can't remember desktop widget positions after reboot
https://bugs.kde.org/show_bug.cgi?id=413645 Aaron Rainbolt changed: What|Removed |Added CC||arraybo...@gmail.com --- Comment #33 from Aaron Rainbolt --- I believe I've located the source of this bug. Using a clean install of Kubuntu 22.04 in a virtual machine with a screen resolution of 2560x1600. In /home/user/.config/plasma-org.kde.plasma.desktop-appletsrc: > [Containments][1] > ItemGeometries-2560x1600=Applet-24:767.806,688.073,224,208,0; > ItemGeometriesHorizontal=Applet-24:767.806,688.073,224,208,0; > activityId=24ffa803--40a5-94cb-76f0419052d1 > formfactor=0 > immutability=1 > lastScreen=0 > location=0 > plugin=org.kde.plasma.folder > wallpaperplugin=org.kde.image > > [Containments][1][Applets][24] > immutability=1 > plugin=org.kde.plasma.notifications > > [Containments][1][Applets][24][Configuration] > PreloadWeight=6 "Applet-24" is a Notifications widget that I've plopped somewhere in the middle of the desktop. If I log out and log back in at this point, I watch the widget initially render where it belongs. It then appears to "wander" around (moving very noticeably all on its own), then suddenly snaps to the edge of the screen (usually into the lower-right corner). I think I'm capturing this movement because I'm using a VM. If I remove the "ItemGeometriesHorizontal" line entirely from the file, then save it, close everything (but leave the widget in the middle of the screen), then log out and log back in, the widget stays where it was left last time. However, the "ItemGeometriesHorizontal" line appears to be automatically recreated, and if I log out and log back in again without modifying the file, the widget again "wanders" then snaps into the wrong location. I have attempted to and succeeded in reproducing this behavior twice. This leads me to believe that the "ItemGeometriesHorizontal" entry is the source of the problem. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455881] New: Would like the ability to resize widgets that are placed in the panel
https://bugs.kde.org/show_bug.cgi?id=455881 Bug ID: 455881 Summary: Would like the ability to resize widgets that are placed in the panel Product: plasmashell Version: master Platform: Neon Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: arraybo...@gmail.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 Setting version as "master" since my version is newer than all of the other versions in the list. KDE makes it quite easy to resize widgets that are placed on the desktop. However, it's not currently possible to resize widgets placed in the panel. Some of us find the current size of some of the widgets (like the Color Picker) to be uncomfortable when placed in the panel, so it would be handy if there was some way to resize them. STEPS TO REPRODUCE 1. Right-click on the panel, and click "Enter Edit Mode". 2. Increase the panel height to 72. 3. Click "Add Widgets...". 4. Select "Color Picker", and drag it onto the panel. OBSERVED RESULT There's no way to resize the widget when placed in the panel. EXPECTED RESULT (more like "desired result" in this instance) There should be some way to resize the widget. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon Unstable Edition KDE Plasma Version: 5.25.80 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.4 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 453883] Version 21.12.3 and above are 4 times slower than 21.08.2 in rendering
https://bugs.kde.org/show_bug.cgi?id=453883 Aaron Rainbolt changed: What|Removed |Added CC||arraybo...@gmail.com --- Comment #1 from Aaron Rainbolt --- Just reproduced this bug on Ubuntu Studio 22.04, Kdenlive 22.04.0 Appimage, on an HP Z220 SFF Workstation with a EVGA GeForce 1050 Ti Using the experimental hardware accelerated render profiles with NVENC. Render speeds were ~200 FPS in 21.04.3, now getting ~75 fps in 22.04.0. The videos I've been rendering are just screen captures made by OBS Studio of a 1080p screen @ 30fps, recording Impress presentations or VM installations. For anyone else who hits this bug, you can get the older version of Kdenlive here: https://download.kde.org/Attic/kdenlive/21.04/linux/ The Appimage provides me the same high speeds that I was getting before. -- You are receiving this mail because: You are watching all bug changes.
