Same problem here:
gnome-shell: JS ERROR: Gio.DBusError: Unable to create transient display: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.DisplayManager was not provided by any .service files Indicator<._onLoginScreenActivate/<@resource:///org/gnome/shell/ui/status/system.js:459:13
Seems that gdm doesn’t have this problem
Because is an upstream incompatibility gnome-shell / lightdm (gnome-shell only supports GDM), that some distributions fix
As a workaround without installing gdm I found this (create a desktop icon):
Hi, I had a similar problem after upgrading my UEFI/BIOS, I couldn’t boot my Antergos.
I couldn’t fixit with the instructions in https://wiki.archlinux.org/index.php/GRUB#UEFI_systems and I was ready to reinstall from the beginning with a copy (dd) of the root partition to restore after, but thanks to this topic i’m back again in my systems in a few minutes, so thanks a lot.
This is a summary of what I did for completeness in case anyone else have this problem:
Boot with the Antegos Live ISO
Check the partition layout:
parted /dev/sda print Number Start End Size File system Name Flags 1 1049kB 211MB 210MB fat32 UEFI_SYSTEM boot 2 211MB 479MB 268MB ext4 ANTERGOS_BOOT 3 479MB 267GB 266GB ext4 ANTERGOS_ROOT 4 267GB 275GB 8398MB linux-swap(v1) ANTERGOS_SWAP
mount /dev/sda3 /mnt mount /dev/sda2 /mnt/boot mount /dev/sda1 /mnt/boot/efi arch-chroot /mnt
pacman -S efibootmgr grub-mkconfig -o /boot/grub/grub.cfg grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=grub exit reboot
and back to normal.
PD: I think this topic could be marked as resolved :)
Re: Dropbox error
Hello, I’m new to Antergos, so first I want to thank everyone involved in this incredible project. I’ve always wanted to try Arch but never had time to install it by myself, Antergos is definitely the way to go.
Yesterday I was playing with dnscrypt and I found this warning in the journal:
[/usr/lib/systemd/system/dropbox.service:3] The dependency could not be added in systemd-user-sessions, ignoring: Invalid argument
It shows when I type “start systemctl start / reload-or-restart d[TAB]” or “systemctl edit dropbox.service --full”
I have added .target to the systemd-user sessions in /usr/lib/systemd/system/dropbox.service and the warning has disappeared.
In the AUR repository they are using this (in case you want to stay in sync):
[Unity] Description = Dropbox [Service] Type = simple ExecStart = / usr / bin / dropbox ExecReload = / bin / kill -HUP $ MAINPID KillMode = process Reset = in case of failure [Install] WantedBy = default.target
[Unity] Description = Dropbox After = local-fs.target network.target [Service] Type = simple ExecStart = / usr / bin / dropbox ExecReload = / bin / kill -HUP $ MAINPID KillMode = process Reset = in case of failure User =% I [Install] WantedBy = multi-user.target
But in my config I have just changed “After = local-fs.target network.target systemd-user-sessions” to “After = local-fs.target network.target systemd-user-sessions.target” and the problem is fixed.
Dropbox is working fine with the .desktop file, but it would be cleaner to have this fixed to avoid the warnings in the journal.
Issued reported and fixed in github
Thanks in advance