[Touch-packages] [Bug 1816630] Re: Gnome Control Center does not start due to GDBus.Error:org.freedesktop.DBus.Error.TimedOut
@Sebastien Bacher thank you very much for looking into this issue. I don't know if it is worth tracking this further. I just moved the /tmp directory back to the / partition, to avoid further trouble. And this actually solved the issue. Like they did here: https://bbs.archlinux.org/viewtopic.php?id=217072 where this was mentioned: ``` systemd[476]: systemd-timesyncd.service: Failed at step NAMESPACE spawning /usr/lib/systemd/systemd-timesyncd: Too many levels of symbolic links systemd[1]: systemd-timesyncd.service: Main process exited, code=exited, status=226/NAMESPACE ``` I gave again full access `chmod 777 /tmp` and set the sticky flag `chmod +t /tmp`: ``` sebastian@home:/$ ll insgesamt 1551245 drwxr-xr-x 26 root root 4096 Feb 20 21:24 ./ drwxr-xr-x 26 root root 4096 Feb 20 21:24 ../ 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 21:25 dev/ drwxr-xr-x 162 root root 12288 Feb 20 19:18 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 298 root root 0 Feb 20 21:25 proc/ drwx-- 10 root root 4096 Jan 11 21:09 root/ drwxr-xr-x 40 root root 1320 Feb 20 21:25 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 21:25 sys/ drwxrwxrwt 16 root root 12288 Feb 20 21:27 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 ``` -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1816630 Title: Gnome Control Center does not start due to GDBus.Error:org.freedesktop.DBus.Error.TimedOut Status in systemd package in Ubuntu: New Bug description: When I try to start the `gnome-control-center`, then it hangs after a few seconds. I recently changed the timezone due to travelling. I can login normally. Another source of the error could be, that I symlinked the `/tmp` and `/opt` directory to another partition. ``` $ gnome-control-center (gnome-control-center:29386): datetime-cc-panel-WARNING **: 10:13:23.508: 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) ``` ``` $ gdbus introspect --system --dest org.freedesktop.timedate1 --object-path /org/freedesktop/timedate1 Fehler: Zeitüberschreitung wurde erreicht ``` ``` $ gdbus introspect --system --dest org.freedesktop.timedate1 --object-path / Fehler: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.freedesktop.timedate1': timed out (service_start_timeout=25000ms) ``` ``` $ timedatectl Failed to query server: Failed to activate service 'org.freedesktop.timedate1': timed out (service_start_timeout=25000ms) ``` ``` $ timedatectl --version systemd 237 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid ``` systemd-timedated service is not starting: ``` $ sudo 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 Tue 2019-02-19 10:47:33 CST; 2min 53s ago Docs: man:systemd-timedated.service(8)
[Touch-packages] [Bug 1816630] Re: Gnome Control Center does not start due to GDBus.Error:org.freedesktop.DBus.Error.TimedOut
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
[Touch-packages] [Bug 1816630] Re: Gnome Control Center does not start due to GDBus.Error:org.freedesktop.DBus.Error.TimedOut
that are my permissions on /home: ``` sebastian@home:/home$ ll insgesamt 44 drwxr-xr-x 6 root root 4096 Feb 13 20:12 ./ drwxr-xr-x 25 root root 4096 Feb 13 20:12 ../ drwx-- 2 root root 16384 Dez 13 00:53 lost+found/ drwxr-xr-x 11 sebastian sebastian 4096 Feb 13 19:43 opt/ drwxr-xr-x 59 sebastian sebastian 4096 Feb 20 17:59 sebastian/ drwxrwxrwt 66 root root 12288 Feb 20 18:19 tmp/ ``` -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1816630 Title: Gnome Control Center does not start due to GDBus.Error:org.freedesktop.DBus.Error.TimedOut Status in systemd package in Ubuntu: New Bug description: When I try to start the `gnome-control-center`, then it hangs after a few seconds. I recently changed the timezone due to travelling. I can login normally. Another source of the error could be, that I symlinked the `/tmp` and `/opt` directory to another partition. ``` $ gnome-control-center (gnome-control-center:29386): datetime-cc-panel-WARNING **: 10:13:23.508: 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) ``` ``` $ gdbus introspect --system --dest org.freedesktop.timedate1 --object-path /org/freedesktop/timedate1 Fehler: Zeitüberschreitung wurde erreicht ``` ``` $ gdbus introspect --system --dest org.freedesktop.timedate1 --object-path / Fehler: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.freedesktop.timedate1': timed out (service_start_timeout=25000ms) ``` ``` $ timedatectl Failed to query server: Failed to activate service 'org.freedesktop.timedate1': timed out (service_start_timeout=25000ms) ``` ``` $ timedatectl --version systemd 237 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid ``` systemd-timedated service is not starting: ``` $ sudo 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 Tue 2019-02-19 10:47:33 CST; 2min 53s ago Docs: man:systemd-timedated.service(8) man:localtime(5) https://www.freedesktop.org/wiki/Software/systemd/timedated Process: 3618 ExecStart=/lib/systemd/systemd-timedated (code=exited, status=226/NAMESPACE) Main PID: 3618 (code=exited, status=226/NAMESPACE) Feb 19 10:47:33 home systemd[1]: Starting Time & Date Service... Feb 19 10:47:33 home systemd[3618]: systemd-timedated.service: Failed to set up mount namespacing: No such file or directory Feb 19 10:47:33 home systemd[3618]: systemd-timedated.service: Failed at step NAMESPACE spawning /lib/systemd/systemd-timedated: No such file or directory Feb 19 10:47:33 home systemd[1]: systemd-timedated.service: Main process exited, code=exited, status=226/NAMESPACE Feb 19 10:47:33 home systemd[1]: systemd-timedated.service: Failed with result 'exit-code'. Feb 19 10:47:33 home systemd[1]: Failed to start Time & Date Service. ``` ``` $ journalctl -xe Feb 19 18:03:59 home ntpd[21785]: 176.221.42.125 local addr 192.168.0.102 -> Feb 19 18:04:05 home sudo[17719]: sebastian : TTY=pts/0 ; PWD=/home/sebastian ; USER=root ; COMMAND=/bin/systemctl start systemd-timedated Feb 19 18:04:05 home sudo[17719]: pam_unix(sudo:session): session opened for user root by (uid=0) Feb 19 18:04:05 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 19 18:04:05 home systemd[17724]: systemd-timedated.service: Failed to set up mount namespacing: No such file or directory Feb 19 18:04:05 home systemd[17724]: 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 19 18:04:05 home systemd[1]: systemd-timedated.service: Main process exited, code=exited, status=226/NAMESPACE Feb 19 18:04:05
[Touch-packages] [Bug 1816630] Re: Gnome Control Center does not start due to GDBus.Error:org.freedesktop.DBus.Error.TimedOut
``` root@home:/var/lib/polkit-1/localauthority/10-vendor.d# ll insgesamt 44 drwxr-xr-x 2 root root 4096 Feb 19 17:12 ./ drwxr-xr-x 7 root root 4096 Jul 25 2018 ../ -rw-r--r-- 1 root root 196 Apr 20 2018 50-com.canonical.indicator.sound.AccountsService.pkla -rw-r--r-- 1 root root 154 Nov 9 07:42 60-libvirt.pkla -rw-r--r-- 1 root root 2363 Nov 6 2015 com.ubuntu.desktop.pkla -rw-r--r-- 1 root root 135 Sep 11 20:33 fwupd.pkla -rw-r--r-- 1 root root 217 Jul 14 2017 geoclue-2.0.pkla -rw-r--r-- 1 root root 485 Okt 31 13:01 gnome-initial-setup.pkla -rw-r--r-- 1 root root 212 Mär 26 2018 org.freedesktop.NetworkManager.pkla -rw-r--r-- 1 root root 209 Nov 9 02:24 org.freedesktop.packagekit.pkla -rw-r--r-- 1 root root 199 Jan 28 2018 systemd-networkd.pkla ``` ``` root@home:/var/lib/polkit-1/localauthority/10-vendor.d# cat systemd-networkd.pkla [Allow systemd-networkd to set timezone and transient hostname] Identity=unix-user:systemd-network Action=org.freedesktop.hostname1.set-hostname;org.freedesktop.timedate1.set-timezone; ResultAny=yes ``` -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1816630 Title: Gnome Control Center does not start due to GDBus.Error:org.freedesktop.DBus.Error.TimedOut Status in systemd package in Ubuntu: New Bug description: When I try to start the `gnome-control-center`, then it hangs after a few seconds. I recently changed the timezone due to travelling. I can login normally. Another source of the error could be, that I symlinked the `/tmp` and `/opt` directory to another partition. ``` $ gnome-control-center (gnome-control-center:29386): datetime-cc-panel-WARNING **: 10:13:23.508: 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) ``` ``` $ gdbus introspect --system --dest org.freedesktop.timedate1 --object-path /org/freedesktop/timedate1 Fehler: Zeitüberschreitung wurde erreicht ``` ``` $ gdbus introspect --system --dest org.freedesktop.timedate1 --object-path / Fehler: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.freedesktop.timedate1': timed out (service_start_timeout=25000ms) ``` ``` $ timedatectl Failed to query server: Failed to activate service 'org.freedesktop.timedate1': timed out (service_start_timeout=25000ms) ``` ``` $ timedatectl --version systemd 237 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid ``` systemd-timedated service is not starting: ``` $ sudo 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 Tue 2019-02-19 10:47:33 CST; 2min 53s ago Docs: man:systemd-timedated.service(8) man:localtime(5) https://www.freedesktop.org/wiki/Software/systemd/timedated Process: 3618 ExecStart=/lib/systemd/systemd-timedated (code=exited, status=226/NAMESPACE) Main PID: 3618 (code=exited, status=226/NAMESPACE) Feb 19 10:47:33 home systemd[1]: Starting Time & Date Service... Feb 19 10:47:33 home systemd[3618]: systemd-timedated.service: Failed to set up mount namespacing: No such file or directory Feb 19 10:47:33 home systemd[3618]: systemd-timedated.service: Failed at step NAMESPACE spawning /lib/systemd/systemd-timedated: No such file or directory Feb 19 10:47:33 home systemd[1]: systemd-timedated.service: Main process exited, code=exited, status=226/NAMESPACE Feb 19 10:47:33 home systemd[1]: systemd-timedated.service: Failed with result 'exit-code'. Feb 19 10:47:33 home systemd[1]: Failed to start Time & Date Service. ``` ``` $ journalctl -xe Feb 19 18:03:59 home ntpd[21785]: 176.221.42.125 local addr 192.168.0.102 -> Feb 19 18:04:05 home sudo[17719]: sebastian : TTY=pts/0 ; PWD=/home/sebastian ; USER=root ; COMMAND=/bin/systemctl start systemd-timedated Feb 19 18:04:05 home sudo[17719]: pam_unix(sudo:session): session opened for user root by (uid=0) Feb 19 18:04:05 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 19 18:04:05 home systemd[17724]: systemd-timedated.service: Failed to set up
[Touch-packages] [Bug 1816630] Re: Gnome Control Center does not start due to GDBus.Error:org.freedesktop.DBus.Error.TimedOut
@Sebastien Bacher thank you for looking into this! ``` $ dpkg -l | grep systemd ii dbus-user-session 1.12.2-1ubuntu1 amd64simple interprocess messaging system (systemd --user integration) ii libnss-systemd:amd64 237-3ubuntu10.13 amd64nss module providing dynamic user and group name resolution ii libpam-systemd:amd64 237-3ubuntu10.13 amd64system and service manager - PAM module ii libsystemd0:amd64 237-3ubuntu10.13 amd64systemd utility library ii networkd-dispatcher 1.7-0ubuntu3.3 all Dispatcher service for systemd-networkd connection status changes ii python3-systemd 234-1build1 amd64Python 3 bindings for systemd ii systemd 237-3ubuntu10.13 amd64system and service manager ii systemd-sysv 237-3ubuntu10.13 amd64system and service manager - SysV links ``` See last line: Permission denied. ``` $ debsums systemd /bin/journalctl OK /bin/loginctl OK /bin/networkctl OK /bin/systemctlOK /bin/systemd-ask-password OK /bin/systemd-escape OK /bin/systemd-inhibit OK /bin/systemd-machine-id-setup OK /bin/systemd-notify OK /bin/systemd-sysusers OK /bin/systemd-tmpfiles OK /bin/systemd-tty-ask-password-agent OK /lib/lsb/init-functions.d/40-systemd OK /lib/modprobe.d/systemd.conf OK /lib/systemd/libsystemd-shared-237.so OK /lib/systemd/network/80-container-host0.network OK /lib/systemd/network/80-container-ve.network OK /lib/systemd/network/80-container-vz.network OK /lib/systemd/resolv.conf OK /lib/systemd/set-cpufreq OK /lib/systemd/system-generators/systemd-cryptsetup-generator OK /lib/systemd/system-generators/systemd-debug-generatorOK /lib/systemd/system-generators/systemd-fstab-generatorOK /lib/systemd/system-generators/systemd-getty-generatorOK /lib/systemd/system-generators/systemd-gpt-auto-generator OK /lib/systemd/system-generators/systemd-hibernate-resume-generator OK /lib/systemd/system-generators/systemd-rc-local-generator OK /lib/systemd/system-generators/systemd-system-update-generatorOK /lib/systemd/system-generators/systemd-sysv-generator OK /lib/systemd/system-generators/systemd-veritysetup-generator OK /lib/systemd/system-preset/90-systemd.preset OK /lib/systemd/system/basic.target OK /lib/systemd/system/bluetooth.target OK /lib/systemd/system/console-getty.service OK /lib/systemd/system/container-getty@.service OK /lib/systemd/system/cryptsetup-pre.target OK /lib/systemd/system/cryptsetup.target OK /lib/systemd/system/debug-shell.service OK /lib/systemd/system/dev-hugepages.mount OK /lib/systemd/system/dev-mqueue.mount OK /lib/systemd/system/emergency.service OK /lib/systemd/system/emergency.target OK /lib/systemd/system/exit.target OK
[Touch-packages] [Bug 1752938] Re: Upgrading Ubuntu 18.04 disables GPU hardware acceleration
*** This bug is a duplicate of bug 1768610 *** https://bugs.launchpad.net/bugs/1768610 Thank you @xjbhenry (xjbhenry)! His fix [21](https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1752938/comments/21), helped me for my NVIDIA card. Instead of "llvmpipe (LLVM 6.0, 256 bits)" the active OpenGL renderer is now: $ glxgears -info Running synchronized to the vertical refresh. The framerate should be approximately the same as the monitor refresh rate. GL_RENDERER = GeForce 940M/PCIe/SSE2 GL_VERSION= 4.6.0 NVIDIA 396.37 GL_VENDOR = NVIDIA Corporation -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1752938 Title: Upgrading Ubuntu 18.04 disables GPU hardware acceleration Status in xorg package in Ubuntu: Confirmed Bug description: I don't know which package causes this problem. The thing is ugrading Ubuntu 18.04 disables my GPU hardware acceleration. glxinfo_before_upgrade OpenGL vendor string: X.Org OpenGL renderer string: Radeon RX 560 Series (POLARIS11 / DRM 3.23.0 / 4.15.0-10-generic, LLVM 5.0.1) OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.3.3 glxinfo_after_upgrade OpenGL vendor string: VMware, Inc. OpenGL renderer string: llvmpipe (LLVM 5.0, 256 bits) OpenGL core profile version string: 3.3 (Core Profile) Mesa 17.3.3 This problem is reproducible. Steps to reproduce: 1. Install Ubuntu 18.04 daily live. I've tried Kubuntu 18.04 Feb 26's daily live(the installer in Mar 1 crashes which prevents me from installing it) and Xubuntu 18.04 Mar 2's daily live. Ubuntu is utilizing my GPU in live cd session and after the fresh install Ubuntu is also utilizing my GPU. 2. Reboot into the newly installed system, do a dist-upgrade and reboot again. Opengl renderer falls back to llvmpipe. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: XFCE Date: Sat Mar 3 00:58:35 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Polaris11] [1002:67ff] (rev cf) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Baffin [Radeon RX 560] [1043:04be] InstallationDate: Installed on 2018-03-02 (0 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180302) MachineType: Gigabyte Technology Co., Ltd. B85M-D3V-A ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=d2dcc7eb-84ca-4102-9ae1-239de26d113c ro quiet splash vt.handoff=1 Renderer: Software SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-D3V-A dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd02/12/2015:svnGigabyteTechnologyCo.,Ltd.:pnB85M-D3V-A:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB85M-D3V-A:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: B85M-D3V-A dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.90-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.3.3-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.3.3-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1752938/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1636865] Re: keyboard key stroke threshold too high - one has to push a key really hard
** Summary changed: - key stroke threshold too high - one has to push a key really hard + keyboard key stroke threshold too high - one has to push a key really hard -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1636865 Title: keyboard key stroke threshold too high - one has to push a key really hard Status in console-setup package in Ubuntu: New Bug description: I don't know why, but after logging in the keyboard behaves weird. One has to push a key really hard to be able to trigger an event. This is serious, because it makes the system unusable. I think this is a threshold issue. It just started while I was writing with the atom editor. First I thought it might be a hardware issue, but under windows and before logging in at ubuntu everything is just fine. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: keyboard-configuration 1.108ubuntu15.2 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Oct 26 15:51:42 2016 InstallationDate: Installed on 2016-08-31 (55 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: console-setup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1636865/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1636865] Re: key stroke threshold too high - one has to push a key really hard
** Description changed: I don't know why, but after logging in the keyboard behaves weird. One has to push a key really hard to be able to trigger an event. This is - serious, because it makes the system non usable. I think this is a + serious, because it makes the system unusable. I think this is a threshold issue. + + It just started while I was writing with the atom editor. First I + thought it might be a hardware issue, but under windows and before + logging in at ubuntu everything is just fine. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: keyboard-configuration 1.108ubuntu15.2 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Oct 26 15:51:42 2016 InstallationDate: Installed on 2016-08-31 (55 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: console-setup UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1636865 Title: key stroke threshold too high - one has to push a key really hard Status in console-setup package in Ubuntu: New Bug description: I don't know why, but after logging in the keyboard behaves weird. One has to push a key really hard to be able to trigger an event. This is serious, because it makes the system unusable. I think this is a threshold issue. It just started while I was writing with the atom editor. First I thought it might be a hardware issue, but under windows and before logging in at ubuntu everything is just fine. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: keyboard-configuration 1.108ubuntu15.2 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Oct 26 15:51:42 2016 InstallationDate: Installed on 2016-08-31 (55 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: console-setup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1636865/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1636865] [NEW] key stroke threshold too high - one has to push a key really hard
Public bug reported: I don't know why, but after logging in the keyboard behaves weird. One has to push a key really hard to be able to trigger an event. This is serious, because it makes the system non usable. I think this is a threshold issue. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: keyboard-configuration 1.108ubuntu15.2 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Oct 26 15:51:42 2016 InstallationDate: Installed on 2016-08-31 (55 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: console-setup UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: console-setup (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1636865 Title: key stroke threshold too high - one has to push a key really hard Status in console-setup package in Ubuntu: New Bug description: I don't know why, but after logging in the keyboard behaves weird. One has to push a key really hard to be able to trigger an event. This is serious, because it makes the system non usable. I think this is a threshold issue. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: keyboard-configuration 1.108ubuntu15.2 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Oct 26 15:51:42 2016 InstallationDate: Installed on 2016-08-31 (55 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: console-setup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1636865/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1512826] Re: when i delete .trash_1000 folder frm usb nautilus freeses
The update from `wily-proposed` to glib2.0 (2.46.2-1ubuntu1) is fixing that nautilus does not crash any more, but I can't move the files actually to the trash. I get a message that I only can cancel or skip the attempt or delete the file, but I really like to move it to the trash. As in https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1510587 I am pointing with an symbolic link to the actual resource from within my home folder to a mounted ext4 file system. Is this a bug or rights problem? I mount the file system like this in my /etc/fstab: # LABEL=Data/mnt/data ext4defaults 0 2 This are my rights on /mnt/data: $ ll /mnt/data/ drwxr-xr-x 5 root plugdev 4096 Jan 15 12:32 ./ drwxr-xr-x 5 root root 4096 Okt 19 11:14 ../ drwx-- 2 root plugdev 16384 Jan 15 12:16 lost+found/ drwxr-xr-x 3 root plugdev 4096 Jan 15 12:14 user/ and on the underlying folders I have these rights: $ ll /mnt/data/user/sebastian drwxrwx--- 18 sebastian sebastian 4096 Jan 18 16:43 ./ drwxr-xr-x 3 root plugdev 4096 Jan 15 12:14 ../ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1512826 Title: when i delete .trash_1000 folder frm usb nautilus freeses Status in GLib: Fix Released Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Wily: Fix Committed Bug description: when i delete .trash_1000 folder frm usb nautilus freeses on ubuntu 15.10. please help To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1512826/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
