Deepin Desktop Environment
DDE (Deepin Desktop Environment) is the default desktop environment originally created for the linux Deepin distribution.
To get a minimal desktop interface, you may start by installing group. This will pull all the basic components.
Thegroups contains some extra applications for a more complete desktop environment.
To be able to use the integrated network administration, the
NetworkManager.service must be started and enabled.
Launching Deepin Desktop Environment
Via a Display Manager
To use the default DDE's lightdm greeter you have to modify the configuration file under the
[Seat:*] section, to state:.
[Seat:*] ... greeter-session=lightdm-deepin-greeter
Note that a valid home directory must exist for a user other than root for the greeter to work.
To have the greeter run at startup:
systemctl enable lightdm.service
To immediately start the desktop environment:
systemctl start lightdm.service
See the xinitrc page for more information.
xinit to start DDE.
No background after resuming from standby
Because of the way the NVIDIA driver stores its FBOs , it happens that after resuming from standby the background suddenly disappears, leaving only a white screen with possibly some color noise on it. The bug appears to be fixed in GNOME upstream, but the Deepin desktop environment still has it.
A possible workaround would be restarting the window manager every time the computer resumes from suspension. A way to do that would be creating the following systemd service
[Unit] Description=User resume actions After=suspend.target [Service] User=%I Type=simple ExecStart=/usr/bin/deepin-wm-restart.sh [Install] WantedBy=suspend.target
That executes the following script
#!/bin/bash export DISPLAY=:0 deepin-wm --replace
Once those two files are created in the correct directories, in order to enable the script it's sufficient to run these commands:
# chmod +x /usr/bin/deepin-wm-restart.sh # systemctl enable resume@user # systemctl start resume@user
The first command makes the script you created executable, the second makes sure that the service always start at boot and the last one starts the service immediately so you can test the workaround without having to reboot the system.
Any upstream or arch packaging related bugs should be reported here. All deepin developers will see the bug reports and solve them as soon as possible.