After logging in the dde-dock isn’t appearing. Checking via htop I see that there is a processing running. After killing it the dde-dock is restarting and appears.
New user here and after a couple of days of event-free use of EndeavourOS I’m suddenly experiencing the same thing you reported here. The difference is that I can’t even run htop because even though I can open the terminal with Ctrl-Alt-T, the cursor is an empty square and the keyboard will not record any characters at all.
I notice you have not received a reply in the 8 months since you posted your message. I’m just going to let it run while connected to AC (so as not to sleep) and see what happens. I’ve rebooted 4 times already and once using the “fallback” choice…and the results are the same.
Follow-up to above (and remember, new user here and still learning Linux):
I finally got a cursor to appear in terminal and ran sudo htop
I could see that 1 or 2 processes were running (it alternated) but then realized that I had no idea how to ID what was a process in all of those lines of display. Went online both for text and YouTube…didn’t find anything other than references to processes (that much, I knew) and finally decided that anything that said “dock” would be tagged with the spacebar and then killed.
I don’t know if it was coincidence or what but…the dock reappeared. And it was functional (meaning, stuff worked when I clicked on them). But then I decided that curing the problem just within the existing session was not the ultimate goal – it needed to be fixed permanently.
No such luck. A re-boot produced the very same problem all over again. I’m back where I was with the DDE dock not appearing at startup. Does anyone have any ideas what’s going on (after days of use with no problem) and how to fix this?
Can’t help you but this also started for me today. Was running fine 8 hours ago, then rebooted about 4 hours ago and the same problem as you describe. So I suspect the kwin or kdecoration update of today. I’m using XFCE while I wait for a new set of deepin packages:
[2020-06-09T16:59:44+0200] [PACMAN] Running ‘pacman -Syu’
[2020-06-09T16:59:44+0200] [PACMAN] synchronizing package lists
[2020-06-09T16:59:45+0200] [PACMAN] starting full system upgrade
[2020-06-09T16:59:49+0200] [ALPM] transaction started
[2020-06-09T16:59:49+0200] [ALPM] upgraded kdecoration (5.18.5-1 -> 5.19.0-1)
[2020-06-09T16:59:49+0200] [ALPM] upgraded breeze (5.18.5-1 -> 5.19.0-1)
[2020-06-09T16:59:50+0200] [ALPM] upgraded imagemagick (7.0.10.17-1 -> 7.0.10.18-1)
[2020-06-09T16:59:50+0200] [ALPM] upgraded kscreenlocker (5.18.5-1 -> 5.19.0-1)
[2020-06-09T16:59:50+0200] [ALPM] installed kwayland-server (5.19.0-1)
[2020-06-09T16:59:50+0200] [ALPM] upgraded kwin (5.18.5-3 -> 5.19.0-1)
[2020-06-09T16:59:50+0200] [ALPM] transaction completed
[2020-06-09T16:59:50+0200] [ALPM] running ‘30-systemd-update.hook’…
[2020-06-09T16:59:50+0200] [ALPM] running ‘detect-old-perl-modules.hook’…
[2020-06-09T16:59:50+0200] [ALPM] running ‘gtk-update-icon-cache.hook’…
I just tried installing on virtualbox and i got no dock either.
Same here, same update … Only “fix” is to start kwin_x11 from terminal.
I totally get why/how a rolling release DE could have problems (though we all would appreciate taking that extra day) but…when the problem is the dock and the panel it’s in (which includes the Launcher), that kinda puts a crimp in what you can do get work your way out of the jam.
At the moment I am not having any issues with the dock. I have installed neither kwin nor kdecoration.
More permanent solution is to install deepin-wm and remove kwin ( sudo pacman -Rcns kwin).
I’m not sure that’s permanent - deepin-kwin is part of the deepin group now and not deepin-wm. Also deein-wm listed as legacy for startdde:
- deepin-kwin (optional) - Preferred window manager
- deepin-metacity (optional) - Legacy 2D window manager
- deepin-wm (optional) - Legacy 3D window manager
Well,
it seems that deepin-kwin is broken at the moment so better option is to use deepin-wm.
Don’t forget that DDE is currently in beta version (that’s very curious) and many bugs have been reported
And it’s fixed, new set of deepin updates have been pushed into the repositories.
So here’s a rather noob question for you: during the EndeavourOS DDE downtime, I’d installed (for the first time!) an additional DE…choosing to go with XFCE. And I used that successfully the last day or two. With the news of the fixed Deepin, I booted up that laptop, made sure I was in the DDE…and then, fortunately, before I had to wrestle with the accompanying balky terminal cursor, a notification appeared telling me of upstream updates. So getting the fixes for Deepin was no harder than clicking on that notification.
But what if I’d been in the XFCE desktop and that same notification appeared at login…would the update still have included the fixes for Deepin?
Yes. When you update all your packages are updated. It doesn’t matter which DE you are in.
Maybe create a startup command ~
killall dde-dock
and,
dde-dock