[Bug 1174566] New: after a successful login, the Plasma does not start ,
http://bugzilla.opensuse.org/show_bug.cgi?id=1174566 Bug ID: 1174566 Summary: after a successful login, the Plasma does not start , Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs@opensuse.org Reporter: ndordea@gmail.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Created attachment 840084 --> http://bugzilla.opensuse.org/attachment.cgi?id=840084&action=edit sudo journalctl -a contents Hello, After I did some maintenance for R on the next boot Plasma does not start . It seems that other components were part of that maintenance . Everything works as before except that the Plasma does not start , After login all applications defined in start automation work with out any problems . The operational status of KDE is very limited . I was able to get a full journalctl -a immediately after a new boot . It is attached ..... journalctl_a_27-07-2020_Plasma_does_not_start.txt Could you please have a look at this issue ? Please let me know if you need any additional information . Thank you, Regards, Nick -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1174566 Nick Dordea <ndordea@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ndordea@gmail.com -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1174566 http://bugzilla.opensuse.org/show_bug.cgi?id=1174566#c1 Fabian Vogt <fvogt@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fvogt@suse.com Flags| |needinfo?(ndordea@gmail.com | |) --- Comment #1 from Fabian Vogt <fvogt@suse.com> --- Judging by the logs, it seems like you have GNOME and Plasma installed next to each other, both DEs have their services running. That can cause conflicts and weird issues. Jul 27 14:05:50 suse4Rocco.dom plasmashell[4905]: Aborting shell load: The activity manager daemon (kactivitymanagerd) is not running. Does krunner still work? What happens when you run "qdbus-qt5 org.kde.ActivityManager" and "/usr/lib64/libexec/kactivitymanagerd"? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1174566 http://bugzilla.opensuse.org/show_bug.cgi?id=1174566#c2 --- Comment #2 from Nick Dordea <ndordea@gmail.com> --- Hello Fabian, 1) I had this configuration for years and I did not have issues, because very seldom I used another desktop manager. When I had issues at login time, one of GNOME, LXDE, Enlightment was selected and I had an operational desktop from which I did some research and changes . Please note that I do not use kactivities. 2) Yes ... krunner is available and can be used . 3) As far as kactivitymanagerd ... the journalctl log shows that it was successfully started .... -------------------- Jul 27 14:05:42 suse4Rocco.dom klauncher[4847]: Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) Jul 27 14:05:44 suse4Rocco.dom kdeinit5[4853]: Initializing "kcm_style" : "kcminit_style" Jul 27 14:05:44 suse4Rocco.dom dbus-daemon[3228]: [session uid=1000 pid=3228] Activating service name='org.kde.ActivityManager' requested by ':1.5' (uid=1000 pid=4850 comm="kded5 [kdeinit5] ") ====> Jul 27 14:05:44 suse4Rocco.dom dbus-daemon[3228]: [session uid=1000 pid=3228] Successfully activated service 'org.kde.ActivityManager' Jul 27 14:05:44 suse4Rocco.dom dbus-daemon[3228]: [session uid=1000 pid=3228] Activating service name='org.kde.kglobalaccel' requested by ':1.5' (uid=1000 pid=4850 comm="kded5 [kdeinit5] ") ====> Jul 27 14:05:44 suse4Rocco.dom kactivitymanagerd[4866]: Config timer connecting... Jul 27 14:05:45 suse4Rocco.dom dbus-daemon[3228]: [session uid=1000 pid=3228] Successfully activated service 'org.kde.kglobalaccel' ===> Jul 27 14:05:45 suse4Rocco.dom kactivitymanagerd[4866]: Setting the name of 0x5643a45adb90 to "org.kde.ActivityManager.ActivityTemplates" ===> Jul 27 14:05:45 suse4Rocco.dom kactivitymanagerd[4866]: Setting the name of 0x5643a45cf9e0 to "org.kde.ActivityManager.Resources.Scoring" ===> Jul 27 14:05:45 suse4Rocco.dom kactivitymanagerd[4866]: Creating directory: "/home/rocco/.local/share/kactivitymanagerd/resources/" ---------------------------- The above directory exists and contains 3 objects database database-shm database-wal and it proves that kactivitymanagerd was active before the message was displayed Jul 27 14:05:50 suse4Rocco.dom plasmashell[4905]: Aborting shell load: The activity manager daemon (kactivitymanagerd) is not running. Something happened between Jul 27 14:05:45 when the daemon was active and Jul 27 14:05:50 when it was detected that the daemon is not running . My feeling is that during the intended R update something in KDE was also updated/changed. I do not know any of KDE internals/intricacies to understand what's going on in the journalctl log as well as what KDE component is the culprit . Over the years I understand that KDE is a collection of packages distributed over many repositories at different versions etc. I just noticed that opensuse leap 15.,2 was released. I will have a look at 15.2 release notes and see if an upgrade does not require fundamental changes on my PC. If not, I rather perform an upgrade to 15.2 that will solve/synchronize/fix all relationships between KDE components with workable plasma than fixing the actual/broken KDE then upgrading to 15.2 . I did DVD/NW upgrade several times so I hope that the upgrade is not taking more than 2-3 hours . I will keep you posted with my decision . Thank you for your help. Regards, Nick -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1174566 http://bugzilla.opensuse.org/show_bug.cgi?id=1174566#c3 --- Comment #3 from Fabian Vogt <fvogt@suse.com> --- (In reply to Nick Dordea from comment #2)
Hello Fabian,
1) I had this configuration for years and I did not have issues, because very seldom I used another desktop manager. When I had issues at login time, one of GNOME, LXDE, Enlightment was selected and I had an operational desktop from which I did some research and changes . Please note that I do not use kactivities.
2) Yes ... krunner is available and can be used .
3) As far as kactivitymanagerd ... the journalctl log shows that it was successfully started ....
It appears like it, but it probably isn't running anymore when plasmashell starts. In a broken session, use krunner to start a terminal and run the two mentioned commands, they should tell what's wrong.
... The above directory exists and contains 3 objects database database-shm database-wal
It's possible that the database got corrupted and deleting those files would recreate them.
and it proves that kactivitymanagerd was active before the message was displayed Jul 27 14:05:50 suse4Rocco.dom plasmashell[4905]: Aborting shell load: The activity manager daemon (kactivitymanagerd) is not running.
Something happened between Jul 27 14:05:45 when the daemon was active and Jul 27 14:05:50 when it was detected that the daemon is not running . My feeling is that during the intended R update something in KDE was also updated/changed. I do not know any of KDE internals/intricacies to understand what's going on in the journalctl log as well as what KDE component is the culprit . Over the years I understand that KDE is a collection of packages distributed over many repositories at different versions etc.
I just noticed that opensuse leap 15.,2 was released. I will have a look at 15.2 release notes and see if an upgrade does not require fundamental changes on my PC. If not, I rather perform an upgrade to 15.2 that will solve/synchronize/fix all relationships between KDE components with workable plasma than fixing the actual/broken KDE then upgrading to 15.2 . I did DVD/NW upgrade several times so I hope that the upgrade is not taking more than 2-3 hours .
It contains an upgrade to Plasma 5.18, but there weren't any relevant changes in kactivitymanagerd. So I expect that if this is an issue with kactivitymanagerd it won't make a difference.
I will keep you posted with my decision .
Thank you for your help.
Regards, Nick
-- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1174566 http://bugzilla.opensuse.org/show_bug.cgi?id=1174566#c4 --- Comment #4 from Nick Dordea <ndordea@gmail.com> --- Hello Fabian, Here are the results of the commands : (1) qdbus-qt5 org.kde.ActivityManager / /ActivityManager /ActivityManager/Activities /ActivityManager/Features /ActivityManager/Resources /ActivityManager/Resources/Linking /ActivityManager/Resources/Scoring /MainApplication /SLC /Templates /org /org/kde /org/kde/ActivityManager (2) /usr/lib64/libexec/kactivitymanagerd no messages displayed (3) ps -ef | grep kactivitymanagerd rocco 5564 3746 0 09:44 ? 00:00:00 /usr/lib64/libexec/kactivitymanagerd rocco 26950 7232 0 10:03 pts/5 00:00:00 grep --color=auto kactivitymanagerd It seems that kactivitymanagerd is running ---------- I don't use kactivity . Maybe under the hood it is used . Based on the release notes , some packages will be removed, plasma will be upgraded . I will take the risk to upgrade to 15.2 and hope for the best ... i.e. getting the plasma working . I will keep you posted with the results of the upgrade . Thank you for your help . Regards, Nick -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1174566 Nick Dordea <ndordea@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(ndordea@gmail.com | |) | -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1174566 http://bugzilla.opensuse.org/show_bug.cgi?id=1174566#c5 --- Comment #5 from Nick Dordea <ndordea@gmail.com> --- Hello Fabian, I proceeded with upgrading my machine from leap 15.1 to leap 15.2 via DVD . The upgrade lasted approx 3 hours without any incidents. The machine booted fine and the plasma started as usual. The only issue was the larger spacing between icons. I am using the virtual desktops. I tried to fix it with config desktop. The old icons etting was "small" + "medium" + 2lines so I could not go to lower size than small. After some research in internet I got some directions on customizing the FoldetView.qml cellWidth and cellHeight values were changed by -10 (height) and -5 (width). The results are better. I have to think to a solution of "maintaining" FolderView.qml whenever the maintenance updates it. Also, I noticed that the virtual desktop definition was changed. The total number of desktops was removed. The only "user option " available is Nr-Rows. Now the user must use the "new" add option to add desktops !?! It is strange that old simpler solutions are changed with new solutions that require more user---error prone---interventions. I worked 25+ years as MVS/DB2/IMS systems programmer and the idea was to make any change backward compatible. The regression testing was [almost] mandatory to make sure that the old procedures/jobs/etc. don't suffer. I'm wondering why so many changes in Linux---more specifically in KDE--- are not backward compatible. Based on zypper lifecycle info ... opensuse 15 has 2 more upgrades end of 2021 and end of 2022. Bottom line, the risk to upgrade to 15.2 was worthful . The machine is upgraded at 15.2 level, the plasma-shell starts, and the desktop is in good shape. As far as I am concerned this ticket can be closed. Thank you for your help. Regards, Nick -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@suse.com