Difference between revisions of "Deepin Desktop Environment"

From ArchWiki
Jump to navigation Jump to search
(Add Interlanguage link : French)
(It appears that part about networkmanager is not mentioned anywhere else.)
Line 21: Line 21:
 
* {{Pkg|deepin-screenshot}}: Deepin screen-shot tools
 
* {{Pkg|deepin-screenshot}}: Deepin screen-shot tools
 
* {{Pkg|deepin-terminal}}: Deepin terminal
 
* {{Pkg|deepin-terminal}}: Deepin terminal
 +
 +
To be able to use the integrated network administration, the {{Pkg|networkmanager}} package is required, and the {{ic|NetworkManager.service}} must be [[systemd#Using units|started and enabled]].
  
 
== Launching Deepin Desktop Environment ==
 
== Launching Deepin Desktop Environment ==

Revision as of 10:15, 7 August 2016

zh-CN:Deepin Desktop Environment

DDE (Deepin Desktop Environment) is the default desktop environment originally created for the linux Deepin distribution.

Installation

To get a minimal desktop interface, you may start by installing deepin group. This will pull all the basic components.

However, it is recommended to also install deepin-extra group to get a fully working DDE:

To be able to use the integrated network administration, the networkmanager package is required, and 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 [SeatDefaults] section, to state:.

/etc/lightdm/lightdm.conf
[SeatDefaults]
...
greeter-session=lightdm-deepin-greeter

Using xinitrc

See the xinitrc page for more information.

~/.xinitrc
exec startdde

Execute startx or xinit to start DDE.

Note: If you want to start Xorg at boot, please read the Start X at login article.

Troubleshooting

Does not start

Type startdde in virtual console and see the output. If you see error with file mentioned libgo.so.9 - ensure you have installed the latest gcc-libs package.

Bug Reporting

Any upstream or arch packaging related bugs should be reported here. FaSheng is one of the Deepin developers and also a contributor/maintainer for arch-deepin and if you file bug reports on his github page then there's much greater chance that the bug will be fixed. ;-)