[lattedock] [Bug 440832] Latte crashes after boot from autostart
https://bugs.kde.org/show_bug.cgi?id=440832 --- Comment #9 from Michail Vourlakos --- (In reply to Jeff Hodd from comment #8) > 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? Open a new topic, with details etc. The topic about the crash is fixed. Your topic is different. -- 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 --- Comment #3 from Michail Vourlakos --- (In reply to Jeff Hodd from comment #1) > 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. for the autostart issues: 1. You must make sure that the auto start desktop file used is updated properly 2. Remove all latte desktop files from: ~/.config/autostart/ 3. Add in ~/.config/autostart/ the new desktop file provided from Latte The crash comes when the system tries to autostart Latte more than two times. -- 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 Michail Vourlakos changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Michail Vourlakos --- In the crash topic this is fixed -- 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.
[lattedock] [Bug 440832] Latte crashes after boot from autostart
https://bugs.kde.org/show_bug.cgi?id=440832 Nate Graham changed: What|Removed |Added Assignee|unassigned-b...@kde.org |mvourla...@gmail.com Product|kde |lattedock CC||n...@kde.org Component|general |application -- You are receiving this mail because: You are watching all bug changes.
