[lattedock] [Bug 440899] Latte is not working properly after desktop startup
https://bugs.kde.org/show_bug.cgi?id=440899 --- Comment #29 from Jeff Hodd --- ok. thanks Michail. that was the only thing i thought might have impacted it too. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 440899] Latte is not working properly after desktop startup
https://bugs.kde.org/show_bug.cgi?id=440899 --- Comment #27 from Jeff Hodd --- i know you've changed the status to resolved, but i was wondering if you could clarify something. the lock/logout widget is pretty innocuous - it does nothing really on startup - and was working in the dock without any problems as of v0.9.12. what changed in 0.10.0 that might have impacted its inclusion in the dock? it's a pretty standard widget... -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 440899] Latte is not working properly after desktop startup
https://bugs.kde.org/show_bug.cgi?id=440899 --- Comment #26 from Jeff Hodd --- the standard kde panelspacers work just fine, Michail. for now i'll stick with those and work the latte spacers in to future releases. the lock/logout widget was the issue. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 440899] Latte is not working properly after desktop startup
https://bugs.kde.org/show_bug.cgi?id=440899 --- Comment #25 from Jeff Hodd --- ends up it's the Lock/Logout widget. wouldn;t have guessed that one. i'm going to try the plasma spacers again, since it appears they weren;t the issue. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 440899] Latte is not working properly after desktop startup
https://bugs.kde.org/show_bug.cgi?id=440899 --- Comment #24 from Jeff Hodd --- well, it's not the spacers. same issue. i'll start replacing the other pieces. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 440899] Latte is not working properly after desktop startup
https://bugs.kde.org/show_bug.cgi?id=440899 --- Comment #23 from Jeff Hodd --- yeah. figured out the spacer. about to restart, again... -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 440899] Latte is not working properly after desktop startup
https://bugs.kde.org/show_bug.cgi?id=440899 --- Comment #20 from Jeff Hodd --- Created attachment 140669 --> https://bugs.kde.org/attachment.cgi?id=140669=edit Screenshot of restarted dock with latte spacer -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 440899] Latte is not working properly after desktop startup
https://bugs.kde.org/show_bug.cgi?id=440899 --- Comment #19 from Jeff Hodd --- Also, the latte spacer doesn't appear to actually provide a space... -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 440899] Latte is not working properly after desktop startup
https://bugs.kde.org/show_bug.cgi?id=440899 --- Comment #18 from Jeff Hodd --- Ok. It came up with the default layout, so I changed the layout to my modified one. Same issue. The bottom of the screen became inaccessible. I opened a terminal and killed the latte process and restarted it via the system menu. It came up no problem, as I'd already described in the bug description. Any ideas? Also, I do want a pager in the dock. This is part of my distro and I consider the pager to be an important component. I've been using latte since your very first release (0.1.0) and everything has worked fine right through 0.9.12. What's changed? -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 440899] Latte is not working properly after desktop startup
https://bugs.kde.org/show_bug.cgi?id=440899 --- Comment #17 from Jeff Hodd --- The interesting thing is that once the bad instance is killed and the desktop restored, you can start latte from the system menu without any problems... Anyway, I've built and installed the plasma5-applets-latte-spacer package and made the related change to the layout file. I'll let you know if that works. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 440899] Latte is not working properly after desktop startup
https://bugs.kde.org/show_bug.cgi?id=440899 --- Comment #15 from Jeff Hodd --- Sorry. Just saw your comment on panelspacer. let me look into that. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 440899] Latte is not working properly after desktop startup
https://bugs.kde.org/show_bug.cgi?id=440899 --- Comment #14 from Jeff Hodd --- Ok. The default layout works. Is there anything in my layout file that you can see that might be questionable? -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 440899] Latte is not working properly after desktop startup
https://bugs.kde.org/show_bug.cgi?id=440899 --- Comment #11 from Jeff Hodd --- I want to reiterate that I am *not* seeing multiple instances of a latte-dock process. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 440899] Latte is not working properly after desktop startup
https://bugs.kde.org/show_bug.cgi?id=440899 --- Comment #9 from Jeff Hodd --- (In reply to Michail Vourlakos from comment #7) > (In reply to Jeff Hodd from comment #5) > > Created attachment 140668 [details] > > Screenshot of systemsettings->Startup and Shutdown->Desktop Session > > 5. are you sure that comma is the way to separate multiple application > records in there? Yes -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 440899] Latte is not working properly after desktop startup
https://bugs.kde.org/show_bug.cgi?id=440899 --- Comment #8 from Jeff Hodd --- [root@bslxenvy64 latte]# cat Bluestar.layout.latte [ActionPlugins][1] RightButton;NoModifier=org.kde.latte.contextmenu [Containments][1] activityId= byPassWM=false enableKWinEdges=true formfactor=2 immutability=1 isPreferredForShortcuts=false lastScreen=-1 location=4 name= onPrimary=true plugin=org.kde.latte.containment raiseOnActivityChange=false raiseOnDesktopChange=false settingsComplexity=4 timerHide=700 timerShow=200 viewType=0 visibility=2 wallpaperplugin=org.kde.image [Containments][1][Applets][2] immutability=1 plugin=org.kde.latte.plasmoid [Containments][1][Applets][2][Configuration] PreloadWeight=0 [Containments][1][Applets][2][Configuration][General] isInLatteDock=true launchers59=file:///usr/share/applications/org.kde.dolphin.desktop,file:///usr/share/applications/org.kde.konsole.desktop,file:///usr/share/applications/gimp.desktop,file:///usr/share/applications/vlc.desktop,applications:libreoffice-writer.desktop,applications:virtualbox.desktop,file:///usr/share/applications/filezilla.desktop,file:///usr/share/applications/thunderbird.desktop,file:///usr/share/applications/firefox.desktop,file:///usr/share/applications/chromium.desktop,applications:google-chrome.desktop,file:///usr/share/applications/pidgin.desktop,file:///usr/share/applications/transmission-qt.desktop,applications:gucharmap.desktop,file:///usr/share/applications/systemsettings.desktop [Containments][1][Applets][3] immutability=1 plugin=org.kde.plasma.lock_logout [Containments][1][Applets][3][Configuration] PreloadWeight=0 [Containments][1][Applets][3][Configuration][ConfigDialog] DialogHeight=540 DialogWidth=720 [Containments][1][Applets][3][Configuration][General] show_lockScreen=false [Containments][1][Applets][4] immutability=1 plugin=org.kde.plasma.pager [Containments][1][Applets][4][Configuration] PreloadWeight=0 [Containments][1][Applets][4][Configuration][General] showWindowIcons=true [Containments][1][Applets][6] immutability=1 plugin=org.kde.plasma.panelspacer [Containments][1][Applets][6][Configuration] PreloadWeight=0 [Containments][1][Applets][6][Configuration][General] expanding=false [Containments][1][Applets][7] immutability=1 plugin=org.kde.plasma.panelspacer [Containments][1][Applets][7][Configuration] PreloadWeight=0 [Containments][1][Applets][7][Configuration][General] expanding=false [Containments][1][Applets][8] immutability=1 plugin=org.kde.plasma.showdesktop [Containments][1][Applets][8][Configuration] PreloadWeight=0 [Containments][1][Applets][9] immutability=1 plugin=org.kde.plasma.trash [Containments][1][Applets][9][Configuration] PreloadWeight=0 [Containments][1][ConfigDialog] DialogHeight=658 DialogWidth=539 [Containments][1][Configuration] PreloadWeight=0 [Containments][1][General] advanced=true alignmentUpgraded=true appletOrder=8;4;7;2;6;3;9 durationTime=x1 iconSize=32 shadowsUpgraded=true shrinkThickMargins=true tasksUpgraded=true threeColorsWindows=true titleTooltips=true zoomLevel=16 [Containments][1][Indicator] customType= enabled=true enabledForApplets=true padding=0.0799821186066 type=org.kde.latte.default [LayoutSettings] activities= background= backgroundStyle=0 color=blue customBackground= customTextColor= disableBordersForMaximizedWindows=false icon= lastUsedActivity=6014f639-5a00-4ab1-8d37-cc778272db68 launchers= popUpMargin=-1 preferredForShortcutsTouched=false schemeFile= sharedLayout= showInMenu=true textColor=fcfcfc version=2 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 440899] Latte is not working properly after desktop startup
https://bugs.kde.org/show_bug.cgi?id=440899 --- Comment #5 from Jeff Hodd --- Created attachment 140668 --> https://bugs.kde.org/attachment.cgi?id=140668=edit Screenshot of systemsettings->Startup and Shutdown->Desktop Session -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 440899] Latte is not working properly after desktop startup
https://bugs.kde.org/show_bug.cgi?id=440899 --- Comment #4 from Jeff Hodd --- Created attachment 140667 --> https://bugs.kde.org/attachment.cgi?id=140667=edit Screenshot of systemsettings->Startup and Shutdown->Autostart -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 440899] Latte autostart interfering with Plasma desktop startup
https://bugs.kde.org/show_bug.cgi?id=440899 --- Comment #2 from Jeff Hodd --- I already add latte-dock to the ignore list, Michail. >From ksmserverrc: excludeApps=latte-dock,octopi-notifier,thunderbird I can also provide a screenshot of systemsettings->Startup and Shutdown->Desktop Session if you want, but those settings are stored in ksmserverrc, as above. Same for systemsettings->Startup and Shutdown->Autostart. Latte is setup there correctly. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 440899] New: Latte autostart interfering with Plasma desktop startup
https://bugs.kde.org/show_bug.cgi?id=440899 Bug ID: 440899 Summary: Latte autostart interfering with Plasma desktop startup Product: lattedock Version: 0.10.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: jgh...@gmail.com Target Milestone: --- Created attachment 140666 --> https://bugs.kde.org/attachment.cgi?id=140666=edit Screenshot of desktop on startup with latte autostart SUMMARY The latest version, v0.10.0, is not functioning properly when started via KDE/Plasma Autostart. On login, the bottom half of the screen is blacked out and blocks any desktop functionality from mid-screen down. If you open a terminal and kill the latte-dock process, all desktop functionality returns. You can then start latte-dock from the system menu, and it starts and functions as expected. I have tried clearing the qmlcache, rebuilding the package in my build environment, building the master version from github, autostarting from xdg and attempted to start it from session restore. None of these approaches fix the problem. It does not appear that the latte-dock process has crashed, it's simply interfering with the normal desktop startup. I have checked the logs for any sign of crashes - none exist. STEPS TO REPRODUCE 1. Install v0.10.0 of latte-dock 2. Install latte autostart 3. Reboot system 4. Log in to Plasma desktop OBSERVED RESULT The bottom half of the screen is either non-functional or blacked out. Latte-dock is inaccessible. Parts of graphical apps running below the halfway mark are also inaccessible. EXPECTED RESULT Should have full desktop functionality and see the dock at the bottom of the screen. SOFTWARE/OS VERSIONS Windows: macOS: Linux: 5.13.9 (available in About System) KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION After the desktop is started up, if you kill the latte process, full desktop functionality is returned. If latte is then restarted via the system menu, it starts as expected. This issue reminds me of a plasma bug that was fixed several months ago, where plasma components/widgets were being created too early - before the corona was fully instantiated (that bug produced a black screen with latte dock running at the bottom). -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 440832] Latte crashes after boot from autostart
https://bugs.kde.org/show_bug.cgi?id=440832 --- Comment #8 from Jeff Hodd --- BTW, this is not resolved or fixed. I see the same issue with your master code base, so whatever the issue is, it's still there. I had a similar issue a few months ago with plasma, and it turned out the plasma developer who helped out found that components were being started before the corona startup was complete. Same issue here perhaps? -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 440832] Latte crashes after boot from autostart
https://bugs.kde.org/show_bug.cgi?id=440832 --- Comment #7 from Jeff Hodd --- Created attachment 140665 --> https://bugs.kde.org/attachment.cgi?id=140665=edit 3 of 3 - same session - restart of latte-dock from sys menu Restart latte-dock from the system menu. It seems as if instead of a double-start, it may be starting too early. I only ever find one running instance. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 440832] Latte crashes after boot from autostart
https://bugs.kde.org/show_bug.cgi?id=440832 --- Comment #6 from Jeff Hodd --- Created attachment 140664 --> https://bugs.kde.org/attachment.cgi?id=140664=edit 2 of 3 - locate and kill single instance of latte-dock. Desktop restored Shows the terminal where I locate the latte-dock process and kill it, showing how it clears the desktop. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 440832] Latte crashes after boot from autostart
https://bugs.kde.org/show_bug.cgi?id=440832 --- Comment #5 from Jeff Hodd --- Created attachment 140663 --> https://bugs.kde.org/attachment.cgi?id=140663=edit Screenshot after login First of 3 screenshots. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 440832] Latte crashes after boot from autostart
https://bugs.kde.org/show_bug.cgi?id=440832 --- Comment #4 from Jeff Hodd --- [root@bslxenvy64 latte]# cd /home/jghodd/.config/autostart [root@bslxenvy64 autostart]# ll total 8 -rw--- 1 jghodd jghodd 590 Jun 16 2020 kdock-thunderbird.desktop -rw-r--r-- 1 jghodd jghodd 301 Sep 17 2020 megasync.desktop lrwxrwxrwx 1 jghodd jghodd 50 Aug 9 16:52 org.kde.latte-dock.desktop -> /usr/share/applications/org.kde.latte-dock.desktop Don't need to reset my autostart. I use a symlink, so it's always pointing to whatever was most recently installed. The only time I found a double-start was if I logged out and logged back in without killing the latte-dock process before doing so. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 440832] Latte crashes after boot from autostart
https://bugs.kde.org/show_bug.cgi?id=440832 Jeff Hodd changed: What|Removed |Added CC||jgh...@gmail.com --- Comment #1 from Jeff Hodd --- I can confirm that latte-dock v0.10.0 is broken. It's not functioning properly when started via KDE/Plasma Autostart. On login, the bottom half of the screen is blacked out and blocks any desktop functionality from mid-screen down. If you open a terminal and kill the latte-dock process, all desktop functionality returns. You can then start latte-dock from the system menu, and it starts and functions as expected. I have tried clearing the qmlcache, rebuilding the package in my build environment, building the master version from github, autostarting from xdg and attempted to start it from session restore. None of these approaches fix the problem. I have not found any evidence that the latte-dock process has crashed, it's simply interfering with the normal desktop startup. I have checked the logs for any sign of crashes - I haven't found any. I did note that my build of the master code did produce a drkonqi process which I have never been able to access. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433799] item geometries not created for new user accounts created using lookandfeel and/or layout templates
https://bugs.kde.org/show_bug.cgi?id=433799 --- Comment #22 from Jeff Hodd --- sorry - *sub-version of 5.21.3 and - *these random timing issues -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433799] item geometries not created for new user accounts created using lookandfeel and/or layout templates
https://bugs.kde.org/show_bug.cgi?id=433799 --- Comment #21 from Jeff Hodd --- Any chance we could re-open this bug? I'm seeing the same issue, and worse, again. I'm building my own sub-version 5.21.3 for my users with this code-change added, and I'm getting reports that the theme is still only randomly coming up. The worse is that latte-dock, autostarted from ~/.config/autostart, is also only starting randomly now. What kind of changes are being made to cause all of these random timing issue on startup? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433799] item geometries not created for new user accounts created using lookandfeel and/or layout templates
https://bugs.kde.org/show_bug.cgi?id=433799 --- Comment #17 from Jeff Hodd --- My apologies, Marco. Somehow managed to get your name reversed. Thank you for the merge-request. It resolves the issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433799] item geometries not created for new user accounts created using lookandfeel and/or layout templates
https://bugs.kde.org/show_bug.cgi?id=433799 --- Comment #16 from Jeff Hodd --- That does indeed fix the issue. Thanks much, Martin. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433799] item geometries not created for new user accounts created using lookandfeel and/or layout templates
https://bugs.kde.org/show_bug.cgi?id=433799 --- Comment #15 from Jeff Hodd --- Am doing a test build. I'll let you know if that fixes it. The source code changes appear to be what's needed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433799] item geometries not created for new user accounts created using lookandfeel and/or layout templates
https://bugs.kde.org/show_bug.cgi?id=433799 --- Comment #14 from Jeff Hodd --- That sounds like a good place to start. Thanks, Martin. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433799] item geometries not created for new user accounts created using lookandfeel and/or layout templates
https://bugs.kde.org/show_bug.cgi?id=433799 --- Comment #12 from Jeff Hodd --- I do want to add, though, that the usual behaviour of saving off the geometries on logout is absolutely not working on first login (initial session). Resizing or moving any of the applets after first login (during the initial session) will flush out the geometries. I cannot use this as a workaround, however. I distribute to a couple of thousand users a month and getting them all to move or resize an applet on initial session would absolutely not work. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433799] item geometries not created for new user accounts created using lookandfeel and/or layout templates
https://bugs.kde.org/show_bug.cgi?id=433799 --- Comment #11 from Jeff Hodd --- I've attached a sample look-and-feel with layout-template that includes 7 desktop applets. They're assigned in the following .config files: kdeglobals:LookAndFeelPackage=org.bluestarlinux.archlogo kscreenlockerrc:Theme=org.bluestarlinux.archlogo ksplashrc:Theme=org.bluestarlinux.archlogo kwinrc:DesktopLayout=org.bluestarlinux.archlogo kwinrc:DesktopListLayout=org.bluestarlinux.archlogo kwinrc:LayoutName=org.bluestarlinux.archlogo startupconfig:ksplashrc_ksplash_theme=org.bluestarlinux.archlogo In the past, I've found that often timing is the issue. The more complex the setup, the longer it takes. If plasma assesses the layout too soon, it misses most of the setup. Might be that now, might not. Let me know if you need the wallpaper. The look-and-feel pulls it from its own artwork, so if the lnf is added to the config files in your skel directory, you should be able to create a new user, then login as that user to see the issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433799] item geometries not created for new user accounts created using lookandfeel and/or layout templates
https://bugs.kde.org/show_bug.cgi?id=433799 --- Comment #10 from Jeff Hodd --- Created attachment 136400 --> https://bugs.kde.org/attachment.cgi?id=136400=edit Sample look-and-feel with layout-template -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433799] item geometries not created for new user accounts created using lookandfeel and/or layout templates
https://bugs.kde.org/show_bug.cgi?id=433799 --- Comment #8 from Jeff Hodd --- Let me see if I can snag a copy of the 5.20.x plasma-workspace source code and I'll see if I can pinpoint some of the more interesting differences. I'll also dig around some in the 5.21.x code and try to pinpoint the geometryChanged event method signature - that would at least be something I can easily trace through the rest of the code. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433799] item geometries not created for new user accounts created using lookandfeel and/or layout templates
https://bugs.kde.org/show_bug.cgi?id=433799 --- Comment #6 from Jeff Hodd --- Yeah, I saw the assignee, but no response at all. This is a fairly significant change in behavior between v5.20 and 5.21, so I'd have expected some response by now. Are you experiencing the same issue, Nate? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433799] item geometries not created for new user accounts created using lookandfeel and/or layout templates
https://bugs.kde.org/show_bug.cgi?id=433799 --- Comment #4 from Jeff Hodd --- Can this be assigned to someone else, then? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433799] item geometries not created for new user accounts created using lookandfeel and/or layout templates
https://bugs.kde.org/show_bug.cgi?id=433799 --- Comment #2 from Jeff Hodd --- Given the sheer volume of code to pour through, I was kinda hoping someone who knows plasma-workspace inside and out might be the best kind of person to look into this, Nate. Just a cursory investigation reveals that geometry is manipulated in dozens of source files, although shell/shellcorona.h/cpp appears to be a key component. There are also quite a number of locations where geometry-changed signals are set up (connected) and/or activated. But I don;t have any kind of birds-eye view of how the whole thing works - thus the need for a developer who knows how all the pieces fit together. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433799] item geometries not created for new user accounts created using lookandfeel and/or layout templates
https://bugs.kde.org/show_bug.cgi?id=433799 Jeff Hodd changed: What|Removed |Added CC||jgh...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433799] New: item geometries not created for new user accounts created using lookandfeel and/or layout templates
https://bugs.kde.org/show_bug.cgi?id=433799 Bug ID: 433799 Summary: item geometries not created for new user accounts created using lookandfeel and/or layout templates Product: plasmashell Version: 5.21.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: Desktop Containment Assignee: notm...@gmail.com Reporter: jgh...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 136288 --> https://bugs.kde.org/attachment.cgi?id=136288=edit plasma desktop update javascript file SUMMARY When a new user account is created that uses a look-and-feel and/or layout template, although the applets are sized and situated correctly on first login, their geometries are not created on login or saved during logout. On second login, the applets are scrambled across the the desktop. My observations are that a plasma shell update named move_desktop_layout_config.js is supposed to read the appletsrc file and rename ItemsGeometries under the General config group, rename it to ItemGeometriesHorizontal and move it to the top level Containment. This has apparently worked for a while, but as of plasma 5.21, ItemsGeometries is not created during the initial login, so move_desktop_layout_config.js is reading a non-existent property for a non-existent value and then assigning that empty value to ItemGeometriesHorizontal. On second (and subsequent) login(s), the applets are, of course, scrambled across the the desktop. Although moving the applets back into position and re-adjusting their sizes does update ItemGeometriesHorizontal, this is not an acceptable workaround. Another observation is that moving or resizing any applet on your desktop after first login also flushes out ItemGeometriesHorizontal to appletsrc. And the last observation is that, as of plasma 5.21, the desktop geometries are no longer being updated on logout. They are being updated when added, moved or resized (but not when added via look-and-feel and/or layout template). STEPS TO REPRODUCE 1. Setup /etc/skel to use a look-and-feel and/or layout template by adding the lnf or template name to kdeglobals, kscreenlockerrc, ksplashrc, kwinrc and startupconfig. 2. Create a new user. 3. Login to the new account and check for ItemsGeometries or ItemGeometriesHorizontal in plasma-org.kde.plasma.desktop-appletsrc - neither exists 4. Logout from the new account 5. Login to the new account and check for ItemsGeometries or ItemGeometriesHorizontal in plasma-org.kde.plasma.desktop-appletsrc - neither exists and the desktop applets are completely scrambled across the desktop. OBSERVED RESULT ItemGeometriesHorizontal is not being created (or updated) in plasma-org.kde.plasma.desktop-appletsrc EXPECTED RESULT ItemGeometriesHorizontal should be created in plasma-org.kde.plasma.desktop-appletsrc SOFTWARE/OS VERSIONS Linux/KDE Plasma: linux-5.11.2, plasma-5.21 (available in About System) KDE Plasma Version: 5.21 KDE Frameworks Version: 5.2.2 Qt Version: 5.15.1 ADDITIONAL INFORMATION I've created a workaround script installed into /usr/share/plasma/shells/org.kde.plasma.desktop/contents/updates named verify_geometries.js so that it runs last. I tried other positions for running this script and last is the only position that works. I've attached the javascript file. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396871] LibreOffice 6 isnt identified correctly from libtaskmanager
https://bugs.kde.org/show_bug.cgi?id=396871 --- Comment #31 from Jeff Hodd --- Will do. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396871] LibreOffice 6 isnt identified correctly from libtaskmanager
https://bugs.kde.org/show_bug.cgi?id=396871 --- Comment #29 from Jeff Hodd --- Yeah, but I don;t think it's a thunderbird bug, either, since the same behaviour crops up in other apps. That was kinda my response to your comment. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396871] LibreOffice 6 isnt identified correctly from libtaskmanager
https://bugs.kde.org/show_bug.cgi?id=396871 --- Comment #27 from Jeff Hodd --- OK. I understand. Thunderbird and QTransmission do conform to expected behaviour then. However, both also display the same odd launcher behaviour Michail describes, and they do not appear to fall into the same category as the gimp bug. Do we have yet a 3rd class of bug here then? I inserted myself into this thread after emailing Michail about the annoying thunderbird behaviour, which is made more annoying since I run it at all times throughout all my sessions. He pointed me in this direction, but apparently we have a case of same strange behaviour, different bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396871] LibreOffice 6 isnt identified correctly from libtaskmanager
https://bugs.kde.org/show_bug.cgi?id=396871 --- Comment #25 from Jeff Hodd --- I understand that wm_class contains 2 strings, but, for example, "caprine" and "Caprine" are a different difference than "Mail" and "Thunderbird", or "transmission-qt" and "transmission". I've been using Michail's software for quite some time and I'm seeing fairly consistently that the odd launcher behaviour he describes occurs with apps that have fundamentally differently wm_class strings. Perhaps I'm not fully understanding the issue, but I am contributing my observations. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396871] LibreOffice 6 isnt identified correctly from libtaskmanager
https://bugs.kde.org/show_bug.cgi?id=396871 --- Comment #22 from Jeff Hodd --- I'm not convinced this is a thunderbird bug or a libre-office bug, or, for that matter, a bug in the dozens of other apps where this issue manifests. This is far more likely to be an issue with plasmashell:taskmanager or some other DE component (windowmanager?) that's not providing the ability to reconcile changes to wm_class - it was indeed pointed out that apps can and do change wm_class, so I doubt this will be viewed as a bug at the app level. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396871] LibreOffice 6 isnt identified correctly from libtaskmanager
https://bugs.kde.org/show_bug.cgi?id=396871 --- Comment #20 from Jeff Hodd --- 60. but it's been this way for a long while. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396871] LibreOffice 6 isnt identified correctly from libtaskmanager
https://bugs.kde.org/show_bug.cgi?id=396871 --- Comment #18 from Jeff Hodd --- The problem exists with qTransmission as well, btw. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396871] LibreOffice 6 isnt identified correctly from libtaskmanager
https://bugs.kde.org/show_bug.cgi?id=396871 --- Comment #17 from Jeff Hodd --- When I run xprop against thunderbird, I'm seeing WM_CLASS(STRING) = "Mail", "Thunderbird", so is this another case of WM_CLASS changing at runtime? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396871] LibreOffice 6 isnt identified correctly from libtaskmanager
https://bugs.kde.org/show_bug.cgi?id=396871 Jeff Hodd changed: What|Removed |Added CC||jgh...@gmail.com --- Comment #15 from Jeff Hodd --- I'm seeing the same issue with other apps, including thunderbird and gimp. This isn't isolated to just libreoffice-writer. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 366324] [REGRESSION] Show CPUs separately no longer works
https://bugs.kde.org/show_bug.cgi?id=366324 Jeff Hodd <jgh...@gmail.com> changed: What|Removed |Added CC||jgh...@gmail.com --- Comment #3 from Jeff Hodd <jgh...@gmail.com> --- This bug is still present in kdeplasma-addons-5.8.3, with a new bug. The new bug is definitely a systemloadviewer coding issue (undefined variable - memApplication) added since v5.8.2, but I concur that the other issues may very well be with a different package - perhaps plasma-workspace which provides systemmonitor. plasmashell[1205]: file:///usr/share/plasma/plasmoids/org.kde.plasma.systemloadviewer/contents/ui/SystemLoadViewer.qml:225: ReferenceError: memApplication is not defined plasmashell[1205]: file:///usr/share/plasma/plasmoids/org.kde.plasma.systemloadviewer/contents/ui/SystemLoadViewer.qml:225: ReferenceError: memApplication is not defined plasmashell[1205]: file:///usr/share/plasma/plasmoids/org.kde.plasma.systemloadviewer/contents/ui/SystemLoadViewer.qml:225: ReferenceError: memApplication is not defined plasmashell[1205]: file:///usr/share/plasma/plasmoids/org.kde.plasma.systemloadviewer/contents/ui/SystemLoadViewer.qml:225: ReferenceError: memApplication is not defined plasmashell[1205]: file:///usr/share/plasma/plasmoids/org.kde.plasma.systemloadviewer/contents/ui/SystemLoadViewer.qml:246: TypeError: Cannot read property 'value' of undefined plasmashell[1205]: file:///usr/share/plasma/plasmoids/org.kde.plasma.systemloadviewer/contents/ui/SystemLoadViewer.qml:246: TypeError: Cannot read property 'value' of undefined plasmashell[1205]: file:///usr/share/plasma/plasmoids/org.kde.plasma.systemloadviewer/contents/ui/SystemLoadViewer.qml:246: TypeError: Cannot read property 'value' of undefined plasmashell[1205]: file:///usr/share/plasma/plasmoids/org.kde.plasma.systemloadviewer/contents/ui/SystemLoadViewer.qml:225: ReferenceError: memApplication is not defined plasmashell[1205]: file:///usr/share/plasma/plasmoids/org.kde.plasma.systemloadviewer/contents/ui/SystemLoadViewer.qml:225: ReferenceError: memApplication is not defined plasmashell[1205]: file:///usr/share/plasma/plasmoids/org.kde.plasma.systemloadviewer/contents/ui/SystemLoadViewer.qml:253: TypeError: Cannot read property 'value' of undefined plasmashell[1205]: file:///usr/share/plasma/plasmoids/org.kde.plasma.systemloadviewer/contents/ui/CompactBarMonitor.qml:45:20: Unable to assign [undefined] to QColor I'm guessing that the "Cannot read property 'value' of undefined" errors are due to bad data in dataSource, which is seeded by systemmonitor - was there perhaps a change in the interface between systemloadviewer and systemmonitor that wasn't properly accommodated in the source code? -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 371946] System Load plasmoid can't display load for each separate CPU
https://bugs.kde.org/show_bug.cgi?id=371946 --- Comment #2 from Jeff Hodd <jgh...@gmail.com> --- It's my guess that the last error message: plasmashell[1205]: file:///usr/share/plasma/plasmoids/org.kde.plasma.systemloadviewer/contents/ui/CompactBarMonitor.qml:45:20: Unable to assign [undefined] to QColor is at the root of the missing cpu display columns. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 371946] System Load plasmoid can't display load for each separate CPU
https://bugs.kde.org/show_bug.cgi?id=371946 Jeff Hodd <jgh...@gmail.com> changed: What|Removed |Added CC||jgh...@gmail.com --- Comment #1 from Jeff Hodd <jgh...@gmail.com> --- I can confirm that this is still an issue in kdeplasma-addons-5.8.3. There appear to be a couple of separate errors now, one for an undefined variable - memApplication - in SystemLoadViewer.qml, and another that appears to be a failure to retrieve the correct data from systemmonitor. Here are the relevant log file entries: plasmashell[1205]: file:///usr/share/plasma/plasmoids/org.kde.plasma.systemloadviewer/contents/ui/SystemLoadViewer.qml:225: ReferenceError: memApplication is not defined plasmashell[1205]: file:///usr/share/plasma/plasmoids/org.kde.plasma.systemloadviewer/contents/ui/SystemLoadViewer.qml:225: ReferenceError: memApplication is not defined plasmashell[1205]: file:///usr/share/plasma/plasmoids/org.kde.plasma.systemloadviewer/contents/ui/SystemLoadViewer.qml:225: ReferenceError: memApplication is not defined plasmashell[1205]: file:///usr/share/plasma/plasmoids/org.kde.plasma.systemloadviewer/contents/ui/SystemLoadViewer.qml:225: ReferenceError: memApplication is not defined plasmashell[1205]: file:///usr/share/plasma/plasmoids/org.kde.plasma.systemloadviewer/contents/ui/SystemLoadViewer.qml:246: TypeError: Cannot read property 'value' of undefined plasmashell[1205]: file:///usr/share/plasma/plasmoids/org.kde.plasma.systemloadviewer/contents/ui/SystemLoadViewer.qml:246: TypeError: Cannot read property 'value' of undefined plasmashell[1205]: file:///usr/share/plasma/plasmoids/org.kde.plasma.systemloadviewer/contents/ui/SystemLoadViewer.qml:246: TypeError: Cannot read property 'value' of undefined plasmashell[1205]: file:///usr/share/plasma/plasmoids/org.kde.plasma.systemloadviewer/contents/ui/SystemLoadViewer.qml:225: ReferenceError: memApplication is not defined plasmashell[1205]: file:///usr/share/plasma/plasmoids/org.kde.plasma.systemloadviewer/contents/ui/SystemLoadViewer.qml:225: ReferenceError: memApplication is not defined plasmashell[1205]: file:///usr/share/plasma/plasmoids/org.kde.plasma.systemloadviewer/contents/ui/SystemLoadViewer.qml:253: TypeError: Cannot read property 'value' of undefined plasmashell[1205]: file:///usr/share/plasma/plasmoids/org.kde.plasma.systemloadviewer/contents/ui/CompactBarMonitor.qml:45:20: Unable to assign [undefined] to QColor The "Cannot read property 'value' of undefined" errors are related to dataSource.memFree and dataSource.swapFree. The workaround described by spiolli...@googlemail.com does seem to alleviate the "all CPUs" issue in the compact bar display itself (although unsatisfactorily), although the mouseover-tooltip now, in v5.8.3, shows nothing but "System load" without any data. -- You are receiving this mail because: You are watching all bug changes.
[kmix] [Bug 370650] Crash on session restore
https://bugs.kde.org/show_bug.cgi?id=370650 --- Comment #5 from Jeff Hodd <jgh...@gmail.com> --- (In reply to Maarten ter Huurne from comment #4) > (In reply to Jeff Hodd from comment #3) > > Please let me know if this should be filed as a new bug for korgac vs. kmix. > > It's certainly very possible that the issue is related to session management > > and is not necessarily application-specific. > > Looking at the backtraces, I think it's a different issue: the cause of the > crash is different (abort vs segfault) and the functions on the stack are > different as well (event vs disconnect). So please open a separate bug > report for it. Thanks. Now submitted as bug 370883. -- You are receiving this mail because: You are watching all bug changes.
[korgac] [Bug 370883] Crash on session restore
https://bugs.kde.org/show_bug.cgi?id=370883 --- Comment #1 from Jeff Hodd <jgh...@gmail.com> --- Possible duplicates by query: bug 369325 -- You are receiving this mail because: You are watching all bug changes.
[korgac] [Bug 370883] New: Crash on session restore
https://bugs.kde.org/show_bug.cgi?id=370883 Bug ID: 370883 Summary: Crash on session restore Product: korgac Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: korganizer-de...@kde.org Reporter: jgh...@gmail.com The crash occurs during login. If I disable session management or add korgac to excluded applications, the crash does not occur. Otherwise, it happens during every login. Reproducible: Always Steps to Reproduce: 1. Enable session management (SystemSettings->Startup and Shutdown->Desktop Session->On Login->Restore previous session) 2. Make sure that korgac is not in the list of excluded apps 3. Logout->Login Actual Results: korgac throws a segmentation violation (SEGV) and dumps core. Expected Results: No crash korgac v16.08.2 -- Backtrace: Application: korgac (korgac), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0xa945a7c0 (LWP 919))] Thread 5 (Thread 0xa3c4db40 (LWP 1099)): #0 0xb7716d41 in __kernel_vsyscall () #1 0xb3750c8b in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #2 0xa77a7a4a in ?? () from /usr/lib/xorg/modules/dri/swrast_dri.so #3 0xb374b301 in start_thread () from /usr/lib/libpthread.so.0 #4 0xb4f720ae in clone () from /usr/lib/libc.so.6 Thread 4 (Thread 0xa444eb40 (LWP 1098)): #0 0xb7716d41 in __kernel_vsyscall () #1 0xb3750c8b in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #2 0xa77a7a4a in ?? () from /usr/lib/xorg/modules/dri/swrast_dri.so #3 0xb374b301 in start_thread () from /usr/lib/libpthread.so.0 #4 0xb4f720ae in clone () from /usr/lib/libc.so.6 Thread 3 (Thread 0xa8667b40 (LWP 1087)): [KCrash Handler] #7 0xb5475e45 in QObject::disconnect(QObject const*, char const*, QObject const*, char const*) () from /usr/lib/libQt5Core.so.5 #8 0xb56e685d in ?? () from /usr/lib/libQt5DBus.so.5 #9 0xb56d3195 in ?? () from /usr/lib/libQt5DBus.so.5 #10 0xb52736fa in ?? () from /usr/lib/libQt5Core.so.5 #11 0xb374b301 in start_thread () from /usr/lib/libpthread.so.0 #12 0xb4f720ae in clone () from /usr/lib/libc.so.6 Thread 2 (Thread 0xa90e8b40 (LWP 1061)): #0 0xb7716d41 in __kernel_vsyscall () #1 0xb4f6815f in poll () from /usr/lib/libc.so.6 #2 0xb387094d in ?? () from /usr/lib/libxcb.so.1 #3 0xb3872cc3 in xcb_wait_for_event () from /usr/lib/libxcb.so.1 #4 0xa91761e3 in ?? () from /usr/lib/libQt5XcbQpa.so.5 #5 0xb52736fa in ?? () from /usr/lib/libQt5Core.so.5 #6 0xb374b301 in start_thread () from /usr/lib/libpthread.so.0 #7 0xb4f720ae in clone () from /usr/lib/libc.so.6 Thread 1 (Thread 0xa945a7c0 (LWP 919)): #0 0xb7716d41 in __kernel_vsyscall () #1 0xb3750c8b in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #2 0xb52745a3 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQt5Core.so.5 #3 0xb5273242 in QThread::wait(unsigned long) () from /usr/lib/libQt5Core.so.5 #4 0xb56d2ebf in ?? () from /usr/lib/libQt5DBus.so.5 #5 0xb56d2f78 in ?? () from /usr/lib/libQt5DBus.so.5 #6 0xb4eb78cb in __run_exit_handlers () from /usr/lib/libc.so.6 #7 0xb4eb7931 in exit () from /usr/lib/libc.so.6 #8 0xb6757937 in KDBusService::KDBusService(QFlags, QObject*) () from /usr/lib/libKF5DBusAddons.so.5 #9 0x0805572e in ?? () #10 0xb4ea1196 in __libc_start_main () from /usr/lib/libc.so.6 #11 0x080559d3 in _start () This can be worked around by adding korgac to the list of "Applications to be excluded from sessions" via SystemSettings->Startup and Shutdown->Desktop Session->On Login. -- You are receiving this mail because: You are watching all bug changes.
[kmix] [Bug 370650] Crash on session restore
https://bugs.kde.org/show_bug.cgi?id=370650 --- Comment #3 from Jeff Hodd <jgh...@gmail.com> --- Please let me know if this should be filed as a new bug for korgac vs. kmix. It's certainly very possible that the issue is related to session management and is not necessarily application-specific. -- You are receiving this mail because: You are watching all bug changes.
[kmix] [Bug 370650] Crash on session restore
https://bugs.kde.org/show_bug.cgi?id=370650 --- Comment #2 from Jeff Hodd <jgh...@gmail.com> --- Sorry about the formatting of the duplicate bug line - I can't seem to edit it. It should read: Possible duplicates by query: bug 369325 -- You are receiving this mail because: You are watching all bug changes.
[kmix] [Bug 370650] Crash on session restore
https://bugs.kde.org/show_bug.cgi?id=370650 Jeff Hodd <jgh...@gmail.com> changed: What|Removed |Added CC||jgh...@gmail.com --- Comment #1 from Jeff Hodd <jgh...@gmail.com> --- Application: korgac (16.08.2) Qt Version: 5.7.0 Frameworks Version: 5.27.0 Operating System: Linux 4.7.6-1-ARCH x86_64 GNU/Linux Distribution: "Arch Linux (x86_64)" -- Information about the crash: - What I was doing when the application crashed: Logging in The crash can be reproduced every time. -- Backtrace: Application: korgac (korgac), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0xa945a7c0 (LWP 919))] Thread 5 (Thread 0xa3c4db40 (LWP 1099)): #0 0xb7716d41 in __kernel_vsyscall () #1 0xb3750c8b in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #2 0xa77a7a4a in ?? () from /usr/lib/xorg/modules/dri/swrast_dri.so #3 0xb374b301 in start_thread () from /usr/lib/libpthread.so.0 #4 0xb4f720ae in clone () from /usr/lib/libc.so.6 Thread 4 (Thread 0xa444eb40 (LWP 1098)): #0 0xb7716d41 in __kernel_vsyscall () #1 0xb3750c8b in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #2 0xa77a7a4a in ?? () from /usr/lib/xorg/modules/dri/swrast_dri.so #3 0xb374b301 in start_thread () from /usr/lib/libpthread.so.0 #4 0xb4f720ae in clone () from /usr/lib/libc.so.6 Thread 3 (Thread 0xa8667b40 (LWP 1087)): [KCrash Handler] #7 0xb5475e45 in QObject::disconnect(QObject const*, char const*, QObject const*, char const*) () from /usr/lib/libQt5Core.so.5 #8 0xb56e685d in ?? () from /usr/lib/libQt5DBus.so.5 #9 0xb56d3195 in ?? () from /usr/lib/libQt5DBus.so.5 #10 0xb52736fa in ?? () from /usr/lib/libQt5Core.so.5 #11 0xb374b301 in start_thread () from /usr/lib/libpthread.so.0 #12 0xb4f720ae in clone () from /usr/lib/libc.so.6 Thread 2 (Thread 0xa90e8b40 (LWP 1061)): #0 0xb7716d41 in __kernel_vsyscall () #1 0xb4f6815f in poll () from /usr/lib/libc.so.6 #2 0xb387094d in ?? () from /usr/lib/libxcb.so.1 #3 0xb3872cc3 in xcb_wait_for_event () from /usr/lib/libxcb.so.1 #4 0xa91761e3 in ?? () from /usr/lib/libQt5XcbQpa.so.5 #5 0xb52736fa in ?? () from /usr/lib/libQt5Core.so.5 #6 0xb374b301 in start_thread () from /usr/lib/libpthread.so.0 #7 0xb4f720ae in clone () from /usr/lib/libc.so.6 Thread 1 (Thread 0xa945a7c0 (LWP 919)): #0 0xb7716d41 in __kernel_vsyscall () #1 0xb3750c8b in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #2 0xb52745a3 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQt5Core.so.5 #3 0xb5273242 in QThread::wait(unsigned long) () from /usr/lib/libQt5Core.so.5 #4 0xb56d2ebf in ?? () from /usr/lib/libQt5DBus.so.5 #5 0xb56d2f78 in ?? () from /usr/lib/libQt5DBus.so.5 #6 0xb4eb78cb in __run_exit_handlers () from /usr/lib/libc.so.6 #7 0xb4eb7931 in exit () from /usr/lib/libc.so.6 #8 0xb6757937 in KDBusService::KDBusService(QFlags, QObject*) () from /usr/lib/libKF5DBusAddons.so.5 #9 0x0805572e in ?? () #10 0xb4ea1196 in __libc_start_main () from /usr/lib/libc.so.6 #11 0x080559d3 in _start () Thus far, the only workarounds I've been able to find for this issue are 1) to turn off session management (SystemSettings->Startup and Shutdown->Desktop Session->On Login->Start with an empty session) OR 2) (SystemSettings->Startup and Shutdown->Desktop Session->On Login->Restore previous session) and add korgac to "Applications to be excluded from sessions". Possible duplicates by query: https://bugs.kde.org/show_bug.cgi?id=369325;>bug 369325 -- You are receiving this mail because: You are watching all bug changes.
