Nope, `/lib` is on the system's partition.
Besides / there is the /home partition
only those a symlinks:
`/opt` -> `/home/opt`
`/tmp` -> `/home/tmp`
```
sebastian@home:/$ ll
insgesamt 1551233
drwxr-xr-x 25 root root 4096 Feb 13 20:12 ./
drwxr-xr-x 25 root root 4096 Feb 13 20:12 ../
drwxr-xr-x 2 root root 4096 Feb 19 14:28 bin/
drwxr-xr-x 5 root root 1024 Feb 19 14:28 boot/
drwxr-xr-x 2 root root 4096 Dez 13 00:54 cdrom/
drwxr-xr-x 23 root root 4660 Feb 20 13:32 dev/
drwxr-xr-x 162 root root 12288 Feb 20 13:42 etc/
drwxr-xr-x 6 root root 4096 Feb 13 20:12 home/
lrwxrwxrwx 1 root root 33 Jan 31 16:55 initrd.img ->
boot/initrd.img-4.15.0-45-generic
lrwxrwxrwx 1 root root 33 Jan 31 16:55 initrd.img.old ->
boot/initrd.img-4.15.0-44-generic
drwxr-xr-x 25 root root 4096 Dez 13 20:17 lib/
drwxr-xr-x 2 root root 4096 Jan 31 23:51 lib32/
drwxr-xr-x 2 root root 4096 Jul 25 2018 lib64/
drwxr-xr-x 2 root root 4096 Jan 31 23:51 libx32/
drwx------ 2 root root 16384 Dez 13 00:53 lost+found/
drwxr-xr-x 3 root root 4096 Dez 13 02:01 media/
drwxr-xr-x 2 root root 4096 Jul 25 2018 mnt/
lrwxrwxrwx 1 root root 9 Feb 13 20:02 opt -> /home/opt/
dr-xr-xr-x 329 root root 0 Feb 20 13:30 proc/
drwx------ 10 root root 4096 Jan 11 21:09 root/
drwxr-xr-x 40 root root 1340 Feb 20 13:32 run/
drwxr-xr-x 2 root root 12288 Feb 19 14:28 sbin/
drwxr-xr-x 9 root root 4096 Dez 20 18:40 snap/
drwxr-xr-x 2 root root 4096 Jul 25 2018 srv/
-rw------- 1 root root 1588346880 Dez 13 00:53 swapfile
dr-xr-xr-x 13 root root 0 Feb 20 13:30 sys/
lrwxrwxrwx 1 root root 9 Feb 13 20:02 tmp -> /home/tmp/
drwx------ 4 root root 4096 Dez 17 23:16 .Trash-0/
drwxr-xr-x 12 root root 4096 Jan 31 23:51 usr/
drwxr-xr-x 15 root root 4096 Dez 16 21:54 var/
lrwxrwxrwx 1 root root 30 Jan 31 16:55 vmlinuz ->
boot/vmlinuz-4.15.0-45-generic
lrwxrwxrwx 1 root root 30 Jan 31 16:55 vmlinuz.old ->
boot/vmlinuz-4.15.0-44-generic
```
Running /lib/systemd/systemd-timedated manually
```
sebastian@home:~$ /lib/systemd/systemd-timedated
Failed to run event loop: Transport endpoint is not connected
sebastian@home:~$ sudo /lib/systemd/systemd-timedated
[sudo] Passwort für sebastian:
sebastian@home:~$ gnome-control-center
Failed to register: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message
recipient disconnected from message bus without replying
sebastian@home:~$ sudo /lib/systemd/systemd-timedated
sebastian@home:~$ gnome-control-center
(gnome-control-center:29931): datetime-cc-panel-WARNING **: 18:14:43.899: could
not get proxy for DateTimeMechanism: Fehler beim Aufruf von StartServiceByName
für org.freedesktop.timedate1: GDBus.Error:org.freedesktop.DBus.Error.TimedOut:
Failed to activate service 'org.freedesktop.timedate1': timed out
(service_start_timeout=25000ms)
**
ERROR:../shell/cc-panel.c:202:cc_panel_size_allocate: assertion failed: (child)
Abgebrochen (Speicherabzug geschrieben)
sebastian@home:~$ sudo /lib/systemd/systemd-timedated
sebastian@home:~$ gnome-control-center
(gnome-control-center:32363): datetime-cc-panel-WARNING **: 18:15:57.084: could
not get proxy for DateTimeMechanism: Fehler beim Aufruf von StartServiceByName
für org.freedesktop.timedate1: GDBus.Error:org.freedesktop.DBus.Error.TimedOut:
Failed to activate service 'org.freedesktop.timedate1': timed out
(service_start_timeout=25000ms)
**
ERROR:../shell/cc-panel.c:202:cc_panel_size_allocate: assertion failed: (child)
Abgebrochen (Speicherabzug geschrieben)
sebastian@home:~$ sudo systemctl status systemd-timedated
● systemd-timedated.service - Time & Date Service
Loaded: loaded (/lib/systemd/system/systemd-timedated.service; static;
vendor preset: enabled)
Active: failed (Result: exit-code) since Wed 2019-02-20 18:15:32 CET; 30s ago
Docs: man:systemd-timedated.service(8)
man:localtime(5)
https://www.freedesktop.org/wiki/Software/systemd/timedated
Process: 32371 ExecStart=/lib/systemd/systemd-timedated (code=exited,
status=226/NAMESPACE)
Main PID: 32371 (code=exited, status=226/NAMESPACE)
Feb 20 18:15:32 home systemd[1]: Starting Time & Date Service...
Feb 20 18:15:32 home systemd[32371]: systemd-timedated.service: Failed to set
up mount namespacing: No such file or directory
Feb 20 18:15:32 home systemd[32371]: systemd-timedated.service: Failed at step
NAMESPACE spawning /lib/systemd/systemd-timedated: No such file or directory
Feb 20 18:15:32 home systemd[1]: systemd-timedated.service: Main process
exited, code=exited, status=226/NAMESPACE
Feb 20 18:15:32 home systemd[1]: systemd-timedated.service: Failed with result
'exit-code'.
Feb 20 18:15:32 home systemd[1]: Failed to start Time & Date Service.
sebastian@home:~$ sudo systemctl start systemd-timedated
Job for systemd-timedated.service failed because the control process exited
with error code.
See "systemctl status systemd-timedated.service" and "journalctl -xe" for
details.
sebastian@home:~$ systemctl status systemd-timedated.service
● systemd-timedated.service - Time & Date Service
Loaded: loaded (/lib/systemd/system/systemd-timedated.service; static;
vendor preset: enabled)
Active: failed (Result: exit-code) since Wed 2019-02-20 18:16:08 CET; 12s ago
Docs: man:systemd-timedated.service(8)
man:localtime(5)
https://www.freedesktop.org/wiki/Software/systemd/timedated
Process: 1434 ExecStart=/lib/systemd/systemd-timedated (code=exited,
status=226/NAMESPACE)
Main PID: 1434 (code=exited, status=226/NAMESPACE)
Feb 20 18:16:08 home systemd[1]: Starting Time & Date Service...
Feb 20 18:16:08 home systemd[1434]: systemd-timedated.service: Failed to set up
mount namespacing: No such file or directory
Feb 20 18:16:08 home systemd[1434]: systemd-timedated.service: Failed at step
NAMESPACE spawning /lib/systemd/systemd-timedated: No such file or directory
Feb 20 18:16:08 home systemd[1]: systemd-timedated.service: Main process
exited, code=exited, status=226/NAMESPACE
Feb 20 18:16:08 home systemd[1]: systemd-timedated.service: Failed with result
'exit-code'.
Feb 20 18:16:08 home systemd[1]: Failed to start Time & Date Service.
sebastian@home:~$ journalctl -xe
Feb 20 18:16:08 home systemd[1]: Starting Time & Date Service...
-- Subject: Unit systemd-timedated.service has begun start-up
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Unit systemd-timedated.service has begun starting up.
Feb 20 18:16:08 home systemd[1434]: systemd-timedated.service: Failed to set up
mount namespacing: No such file or directory
Feb 20 18:16:08 home systemd[1434]: systemd-timedated.service: Failed at step
NAMESPACE spawning /lib/systemd/systemd-timedated: No such file or directory
-- Subject: Process /lib/systemd/systemd-timedated could not be executed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- The process /lib/systemd/systemd-timedated could not be executed and failed.
--
-- The error number returned by this process is 2.
Feb 20 18:16:08 home systemd[1]: systemd-timedated.service: Main process
exited, code=exited, status=226/NAMESPACE
Feb 20 18:16:08 home systemd[1]: systemd-timedated.service: Failed with result
'exit-code'.
Feb 20 18:16:08 home systemd[1]: Failed to start Time & Date Service.
-- Subject: Unit systemd-timedated.service has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Unit systemd-timedated.service has failed.
--
-- The result is RESULT.
Feb 20 18:16:08 home sudo[1431]: pam_unix(sudo:session): session closed for
user root
Feb 20 18:16:17 home signal-desktop.desktop[11899]:
{"name":"log","hostname":"home","pid":11899,"level":30,"msg":"Sending a
keepalive message","time":"2019-02-20T17:16:17.669Z","v":0}
```
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1816630
Title:
Gnome Control Center does not start due to
GDBus.Error:org.freedesktop.DBus.Error.TimedOut
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1816630/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
