Deepin Desktop Environment

The Deepin Desktop Environment (DDE) is the desktop environment of the deepin Linux distribution. It is designed by the Wuhan Deepin Technology Co.,Ltd. deepin is a Linux distribution devoted to providing a beautiful, easy to use, safe and reliable system for global users. deepin is an open source GNU/Linux operating system, based on Linux kernel and mainly on desktop applications, supporting laptops, desktops, and all-in-ones. The DDE is comprised of the Desktop Environment, deepin Window Manager, Control Center, Launcher and Dock.

Installation

Install deepin and deepin-kwin for the basic components for a minimal desktop interface.

Optionally, also install deepin-extra for some extra applications for a more complete desktop environment.

Starting

Via a display manager

LightDM is the default display manager for DDE, and it will installed as dependency. Simply enable lightdm.service to use it.

Note: A valid home directory must exist for a user other than root for the greeter to work.

Via xinit

To use Deepin via xinit, you will need to add the following to your .xinitrc file.

Configuration

Networking

NetworkManager is integrated in DDE network administration and is installed together. Enable to use it.

Customize touchpad gesture behavior

Deepin does not officially support customizing the gesture behaviors, but it is possible to manually change this by editing the configuration file /usr/share/dde-daemon/gesture.json.

For instance, if you want to disable tapping gesture activity, set its action to :

To apply the changes, reboot your system or log off and log in again.

Changing default deepin sounds

While this is not officially supported, it is possible to change or even remove the default sounds that are used by Deepin (ex. login sound). Simply replace the sounds in the directory:

/usr/share/sounds/deepin/stereo

Note: If you simply want to disable the sound effects entirely, it can be done from Deepin's system settings (sound section).

Troubleshooting

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 to create the following systemd service

That executes the following script

Once those two files are created in the correct directories, make the script executable and start/enable resume@user

Wireless network does not connect

NetworkManager sets the MAC address generated randomly. This was already enabled by default, to disable it add the following lines to the NetworkManager configuration file.

Bluetooth Menu does not show up / work

Start/enable . This service is not enabled by default.

Bug reporting

Any bugs related to Arch packaging should be reported in the bug tracker.

Any upstream related bugs should be reported here. All the Deepin developers will see the bug reports and solve them as soon as possible.

gollark: It's on my laptop, which isn't currently on WiFi or anything, so yes.
gollark: ```rust let multicast_addr: Ipv6Addr = "ff02::aeae".parse().unwrap(); let socket = Socket::new(Domain::ipv6(), Type::dgram(), Some(Protocol::udp()))?; socket.set_only_v6(true)?; socket.set_multicast_loop_v6(false)?; socket.join_multicast_v6(&multicast_addr, 0).with_context(|| "join multicast failed")?; socket.bind(&SocketAddr::from((Ipv6Addr::UNSPECIFIED, PORT)).into())?;```
gollark: It's likely that my code is just setting up the socket wrong somehow, since I mostly just used the multicast-looking things in the docs and rearranged the calls until it stopped saying stupid things like "OS error 22".
gollark: ```192.168.1.148 dev enp0s31f6 lladdr 90:8d:6c:1f:0f:fd STALE192.168.1.1 dev enp0s31f6 lladdr a4:08:f5:7d:a3:d3 REACHABLE192.168.1.179 dev enp0s31f6 lladdr 00:4c:74:86:00:2f STALE2a00:23c7:5415:d300:adf8:5e75:241f:8e7d dev enp0s31f6 lladdr 00:4c:74:86:00:2f STALEfe80::7c31:e6f9:7182:4856 dev enp0s31f6 lladdr 00:4c:74:86:00:2f STALEfe80::22bb:223:5b9:1efd dev enp0s31f6 lladdr a0:b3:cc:ea:e3:8b REACHABLEfe80::a608:f5ff:fe7d:a3d3 dev enp0s31f6 lladdr a4:08:f5:7d:a3:d3 router REACHABLE2a00:23c7:5415:d300:6209:a461:6fb4:931d dev enp0s31f6 lladdr a0:b3:cc:ea:e3:8b REACHABLE```
gollark: `ip neigh show`, right?

See also

This article is issued from Archlinux. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.