Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

process org.freedesktop.systemd1 exited with status 1 #5247

Closed
soloturn opened this issue Feb 6, 2017 · 37 comments
Closed

process org.freedesktop.systemd1 exited with status 1 #5247

soloturn opened this issue Feb 6, 2017 · 37 comments
Labels

Comments

@soloturn
Copy link

@soloturn soloturn commented Feb 6, 2017

Submission type

  • Bug report

systemd version the issue has been seen with

$ pacman -Q systemd
systemd 232-8
linux 4.9.6-1-ARCH

NOTE: Do not submit bug reports about anything but the two most recently released systemd versions upstream!

Used distribution

arch linux

In case of bug report: Unexpected behaviour you saw

Activating service name='org.freedesktop.systemd1'
Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
Activating service name='org.freedesktop.systemd1'
Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
Activating service name='org.freedesktop.systemd1'
Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
Activating service name='org.freedesktop.systemd1'
Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
Activating service name='org.freedesktop.systemd1'
Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
Activating service name='org.freedesktop.systemd1'
Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
Activating service name='org.freedesktop.systemd1'
Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
Activating service name='org.gtk.vfs.Daemon'
Successfully activated service 'org.gtk.vfs.Daemon'
Activating service name='org.freedesktop.systemd1'
Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
Activating service name='org.freedesktop.systemd1'
Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
Activating service name='org.a11y.Bus'
Successfully activated service 'org.a11y.Bus'
Activating service name='org.gnome.Shell.CalendarServer'
Activated service 'org.gnome.Shell.CalendarServer' failed: Process org.gnome.Shell.CalendarServer exited with status 127
Activating service name='org.freedesktop.Telepathy.AccountManager'
Successfully activated service 'org.freedesktop.Telepathy.AccountManager'
Activating service name='org.gtk.vfs.UDisks2VolumeMonitor'
Successfully activated service 'org.gtk.vfs.UDisks2VolumeMonitor'
Activating service name='org.gtk.vfs.MTPVolumeMonitor'
Successfully activated service 'org.gtk.vfs.MTPVolumeMonitor'
Activating service name='org.gtk.vfs.AfcVolumeMonitor'
Successfully activated service 'org.gtk.vfs.AfcVolumeMonitor'
Activating service name='org.freedesktop.systemd1'
Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
Activating service name='org.freedesktop.systemd1'
Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
Activating service name='org.freedesktop.systemd1'
Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
Activating service name='org.freedesktop.systemd1'
Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
Activating service name='org.freedesktop.systemd1'
Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
Activating service name='org.freedesktop.systemd1'
Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1

In case of bug report: Steps to reproduce the problem

start gnome on command line:
XDG_SESSION_TYPE=wayland nohup dbus-run-session gnome-session

@soloturn soloturn changed the title rocess org.freedesktop.systemd1 exited with status 1 process org.freedesktop.systemd1 exited with status 1 Feb 7, 2017
@poettering
Copy link
Member

@poettering poettering commented Feb 7, 2017

this suggests you aren't actually running dbus from the systemd --user instance...

@CounterfeitLlama
Copy link

@CounterfeitLlama CounterfeitLlama commented Feb 18, 2017

I am having the exact same issue as above. Has anyone found a solution to this yet?

@soloturn
Copy link
Author

@soloturn soloturn commented Feb 19, 2017

lennart, what do you mean with your comment, resp what do you want me to do? i am following what florian müllner suggested here: https://bugzilla.gnome.org/show_bug.cgi?id=774774

@poettering
Copy link
Member

@poettering poettering commented Feb 20, 2017

@soloturn well, is "systemctl --user dbus.service" showing that the user dbus is running as user service off systemd --user?

@soloturn
Copy link
Author

@soloturn soloturn commented Feb 26, 2017

to add, i was starting gnome wayland for quite a while like this, and there was no systemd error. it showed up recently - i.e. in the last weeks.

$ systemctl --user dbus.service
Unknown operation dbus.service.

$ systemctl --user | grep loaded
...
51 loaded units listed. Pass --all to see loaded but inactive units, too.

$ cat /etc/pam.d/system-login | grep systemd
-session optional pam_systemd.so

i saw:
https://www.archlinux.org/news/d-bus-now-launches-user-buses/
https://wiki.archlinux.org/index.php/D-Bus

@poettering
Copy link
Member

@poettering poettering commented Feb 26, 2017

$ systemctl --user dbus.service

Sorry, I meant "systemctl --user status dbus.service"...

@soloturn
Copy link
Author

@soloturn soloturn commented Mar 19, 2017

it says, entered into a gnome terminal:
$ systemctl --user status dbus.service
● dbus.service - D-Bus User Message Bus
Loaded: loaded (/usr/lib/systemd/user/dbus.service; static; vendor preset: enabled)
Active: active (running) since Sun 2017-03-19 05:58:41 CET; 4h 49min ago
Docs: man:dbus-daemon(1)
Main PID: 1773 (dbus-daemon)
CGroup: /user.slice/user-1000.slice/user@1000.service/dbus.service
└─1773 /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation

would you be able to describe how it is supposed to be, or where this can go wrong? i boot, i log in on text tty, then start gnome as my user with "XDG_SESSION_TYPE=wayland dbus-run-session gnome-session".

@nbdsp
Copy link

@nbdsp nbdsp commented Mar 28, 2017

@soloturn

I just had the same symptoms with Gnome not starting on Arch and the problem was resolved by installing 'nvidia' package instead of 'nvidia-340xx-utils'.

@soloturn
Copy link
Author

@soloturn soloturn commented Apr 1, 2017

nbdsp, do you start it on a command line or you have gdm running?

@raindev
Copy link

@raindev raindev commented Apr 11, 2017

I have exactly the same symptoms when starting GNOME with XDG_SESSION_TYPE=wayland dbus-run-session gnome-session. Shell starts successfully anyway and seems to be running without issues.

@soloturn
Copy link
Author

@soloturn soloturn commented Apr 15, 2017

this one does not seem related but i am putting it here in case there is a relation i cannot see. when i do not log in on the command line but put the command into bash_profile, starting falls into an endless loop, "cannot initialise inotify" and then "dbus-run-session ignoring unknown child process ...". i opened a bug here:
https://bugzilla.gnome.org/show_bug.cgi?id=780801

for the inotify i did something in the lines of:
echo fs.inotify.max_user_watches=524288 | sudo tee /etc/sysctl.d/40-max-user-watches.conf && sudo sysctl --system

@FranklinYu
Copy link

@FranklinYu FranklinYu commented Apr 17, 2017

I met both issues as well.

I suspect that the endless loop issue is caused by the dbus-run-session process somehow sourcing .bash_profile (.zprofile in my case) again, so each message indicates a level of call stack. I avoided this issue by

if [[ -z $DISPLAY ]] && [[ $(tty) = /dev/tty1 ]] && [[ -z $XDG_SESSION_TYPE ]]
then XDG_SESSION_TYPE=wayland exec dbus-run-session gnome-session
fi
@eliriand
Copy link

@eliriand eliriand commented Apr 26, 2017

I can reproduce this bug too with Arch using systemd 232 and dbus 1.10.18. After running XDG_SESSION_TYPE=wayland dbus-run-session gnome-session

Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
Activating service name='org.freedesktop.systemd1'
Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
Activating service name='org.freedesktop.systemd1'
Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
Activating service name='org.freedesktop.systemd1'
Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
Activating service name='org.freedesktop.systemd1'
Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
Activating service name='org.freedesktop.systemd1'
Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
Activating service name='org.gtk.vfs.Daemon'
Successfully activated service 'org.gtk.vfs.Daemon'
Activating service name='org.freedesktop.systemd1'
Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
Activating service name='org.freedesktop.systemd1'
Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1

Dbus user service is running fine:

   Loaded: loaded (/usr/lib/systemd/user/dbus.service; static; vendor preset: enabled)
   Active: active (running) since Tue 2017-04-25 17:10:50 MSK; 18h ago
     Docs: man:dbus-daemon(1)
 Main PID: 1029 (dbus-daemon)
   CGroup: /user.slice/user-1000.slice/user@1000.service/dbus.service
           └─1029 /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation```
@eomanis
Copy link

@eomanis eomanis commented Apr 28, 2017

I am hit by this too since Arch updated to GNOME 3.24 a few days ago.

GDM appears to be unable to start a Wayland-based GNOME session and falls back to Xorg, that's why I started investigating.
When I run XDG_SESSION_TYPE=wayland dbus-run-session gnome-session from one of the system terminals, I get the same result as eliriand. The dbus user service is up and running.

I only got rid of the GNOME Xorg session a few weeks ago. Now my desktop is again insecure, and the activities overview lags again, it owns :-/ It was so smooth when running in Wayland mode

@FranklinYu
Copy link

@FranklinYu FranklinYu commented Apr 29, 2017

@eomanis I believe that's a situation worse than some of us here. In my case, I saw those messages, but GNOME session works fine. Same for @raindev. In you case GNOME session can't even start under Wayland, right (neither from GDM nor from terminal)?

And I'm wondering why this issue is still labeled with "needs-reporter-feedback" although @soloturn has already replied a month ago. Maybe there are way too many issues in the queue (over 600 now).

@BinaryHexer
Copy link

@BinaryHexer BinaryHexer commented May 19, 2017

@FranklinYu is there a temporary solution or workaround for this? I cannot now start my wayland Gnome DE and it's the only DE on my Arch installation.

@keszybz
Copy link
Member

@keszybz keszybz commented May 19, 2017

This seems to be an issue with the way the user session is started on arch, i.e. not something that we can solve here. Please move this discussion to the arch bugtracker. (Also, if somebody could later paste a link, for the sake of other people encountering this issue, that'd be appreciated.)

@FranklinYu
Copy link

@FranklinYu FranklinYu commented May 19, 2017

@BinaryHexer It shouldn't stop GNOME from being started. Are you trying to start GNOME from GDM or from terminal? Or you tried both?

@BinaryHexer
Copy link

@BinaryHexer BinaryHexer commented May 19, 2017

@FranklinYu terminal.

This is the script I am using

#!/bin/bash

export QT_QPA_PLATFORM=wayland
if [[ -z $DISPLAY ]] && [[ $(tty) = /dev/tty1 ]] && [[ -z $XDG_SESSION_TYPE ]]
  then XDG_SESSION_TYPE=wayland exec dbus-run-session gnome-session
fi
@FranklinYu
Copy link

@FranklinYu FranklinYu commented May 19, 2017

@BinaryHexer I assume that the script is neither .profile nor .xsession nor any dot file? Maybe it's just a script which you run with ./start-gnome?

@BinaryHexer
Copy link

@BinaryHexer BinaryHexer commented May 19, 2017

@FranklinYu yes, correct assumption. It has worked in the past without any problems, I don't know what happened.

@FranklinYu
Copy link

@FranklinYu FranklinYu commented May 19, 2017

@BinaryHexer Then how about simply

XDG_SESSION_TYPE=wayland dbus-run-session gnome-session

in log-in shell session? (Note the absence of exec.)

@raindev
Copy link

@raindev raindev commented May 19, 2017

@FranklinYu, sorry I've missed your previous mention.

In you case GNOME session can't even start under Wayland, right (neither from GDM nor from terminal)?

Actually, that's not the case: I still can successfully Stuart GNOME session both from tty and using GDM.

@FranklinYu
Copy link

@FranklinYu FranklinYu commented May 20, 2017

@raindev Yes, I knew about that; I was actually referring to @eomanis's case. I think the behavior on your system is the same as mine, while @eomanis unfortunately met some more issue.

Sorry for causing misunderstanding. (Non-native speaker here.)

@BinaryHexer
Copy link

@BinaryHexer BinaryHexer commented May 20, 2017

@FranklinYu thanks for helping me, but

XDG_SESSION_TYPE=wayland dbus-run-session gnome-session

has the same result as before.

Here is result of debug

I can't figure out how to fix this.

@polyjitter
Copy link

@polyjitter polyjitter commented Jun 16, 2017

I'd like to chime in and say I've had a similar problem. For me, any Wayland session immediately crashes back to GDM.

When I run dbus-run-session -- gnome-shell --display-server --wayland, it WILL run a legitimate GNOME Shell wayland session; however, most custom icon theming and gtk2 themes don't work, my touchpad is unresponsive, and some apps (such as Rhythmbox) don't show headerbars.

When I try to run budgie-desktop with the same method, however, I get the error stated in the issue.

I am running a Intel HD/Nvidia laptop. I'm not sure if this is the same symptoms, if it's multiple issues, or where to go from here.

Any help would be appreciated.

@udovdh
Copy link

@udovdh udovdh commented Aug 28, 2017

$ systemctl --user start vino-server.service
Failed to start vino-server.service: Process org.freedesktop.systemd1 exited with status 1
See user logs and 'systemctl --user status vino-server.service' for details.
$ systemctl --user status vino-server.service
Failed to get properties: Process org.freedesktop.systemd1 exited with status 1

What is org.freedesktop.systemd1?
What use is it if it exits with status 1 and does not offer a decent place to find out what is causing this brouha?
Previously we could simply start a daemon.

@udovdh
Copy link

@udovdh udovdh commented Aug 28, 2017

$ systemctl --user status
Failed to read server status: Process org.freedesktop.systemd1 exited with status 1
$ systemctl --state=failed --all
0 loaded units listed.
To show all installed unit files use 'systemctl list-unit-files'.

How can this be?

@dpc
Copy link

@dpc dpc commented Aug 28, 2017

On Archlinux, I've enabled [testing], upgraded everything, and the problem went away.

@stev-it
Copy link

@stev-it stev-it commented Apr 27, 2018

This is not just an arch problem. Im having the same issue on my raspberry pi too now.

@udovdh
Copy link

@udovdh udovdh commented Apr 27, 2018

$ systemctl --user start vino
Failed to start vino.service: Process org.freedesktop.systemd1 exited with status 1
See user logs and 'systemctl --user status vino.service' for details.

System was taken to runlevel 3 and then to 5.
This impiies that this does not cleanly kill all GUI-related processes and/or does not perfectly start all GUI-related processes.

@soloturn
Copy link
Author

@soloturn soloturn commented May 21, 2018

@poettering the error message meanwhile slightly changed, this is the nohop file after starting gnome on the command line and then immeditaely press "logout".

$ XDG_SESSION_TYPE=wayland nohup dbus-run-session gnome-session 
$ cat nohup.out
dbus-daemon[17775]: [session uid=1000 pid=17775] Activating service name='org.freedesktop.systemd1' requested by ':1.1' (uid=1000 pid=17776 comm="/usr/lib/gnome-session-binary ")
dbus-daemon[17775]: [session uid=1000 pid=17775] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
dbus-daemon[17775]: [session uid=1000 pid=17775] Activating service name='org.freedesktop.systemd1' requested by ':1.3' (uid=1000 pid=17776 comm="/usr/lib/gnome-session-binary ")
dbus-daemon[17775]: [session uid=1000 pid=17775] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
dbus-daemon[17775]: [session uid=1000 pid=17775] Activating service name='org.freedesktop.systemd1' requested by ':1.5' (uid=1000 pid=17776 comm="/usr/lib/gnome-session-binary ")
dbus-daemon[17775]: [session uid=1000 pid=17775] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
dbus-daemon[17775]: [session uid=1000 pid=17775] Activating service name='org.freedesktop.systemd1' requested by ':1.7' (uid=1000 pid=17776 comm="/usr/lib/gnome-session-binary ")
dbus-daemon[17775]: [session uid=1000 pid=17775] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
dbus-daemon[17775]: [session uid=1000 pid=17775] Activating service name='org.freedesktop.systemd1' requested by ':1.8' (uid=1000 pid=17776 comm="/usr/lib/gnome-session-binary ")
dbus-daemon[17775]: [session uid=1000 pid=17775] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
dbus-daemon[17775]: [session uid=1000 pid=17775] Activating service name='org.gtk.vfs.Daemon' requested by ':1.9' (uid=1000 pid=17820 comm="/usr/bin/gnome-shell ")
dbus-daemon[17775]: [session uid=1000 pid=17775] Successfully activated service 'org.gtk.vfs.Daemon'
fusermount: failed to access mountpoint /run/user/1000/gvfs: Permission denied
dbus-daemon[17775]: [session uid=1000 pid=17775] Activating service name='org.freedesktop.systemd1' requested by ':1.8' (uid=1000 pid=17776 comm="/usr/lib/gnome-session-binary ")
dbus-daemon[17775]: [session uid=1000 pid=17775] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
dbus-daemon[17775]: [session uid=1000 pid=17775] Activating service name='org.freedesktop.systemd1' requested by ':1.8' (uid=1000 pid=17776 comm="/usr/lib/gnome-session-binary ")
dbus-daemon[17775]: [session uid=1000 pid=17775] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
dbus-daemon[17775]: [session uid=1000 pid=17775] Activating service name='org.a11y.Bus' requested by ':1.11' (uid=1000 pid=17820 comm="/usr/bin/gnome-shell ")
dbus-daemon[17775]: [session uid=1000 pid=17775] Successfully activated service 'org.a11y.Bus'
dbus-daemon[17853]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=1000 pid=17820 comm="/usr/bin/gnome-shell ")
dbus-daemon[17853]: Successfully activated service 'org.a11y.atspi.Registry'
SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
dbus-daemon[17775]: [session uid=1000 pid=17775] Activating service name='org.gnome.Shell.CalendarServer' requested by ':1.9' (uid=1000 pid=17820 comm="/usr/bin/gnome-shell ")
/usr/lib/gnome-shell-calendar-server: error while loading shared libraries: libecal-1.2.so.19: cannot open shared object file: No such file or directory
dbus-daemon[17775]: [session uid=1000 pid=17775] Activated service 'org.gnome.Shell.CalendarServer' failed: Process org.gnome.Shell.CalendarServer exited with status 127
dbus-daemon[17775]: [session uid=1000 pid=17775] Activating service name='ca.desrt.dconf' requested by ':1.9' (uid=1000 pid=17820 comm="/usr/bin/gnome-shell ")
dbus-daemon[17775]: [session uid=1000 pid=17775] Successfully activated service 'ca.desrt.dconf'
dbus-daemon[17775]: [session uid=1000 pid=17775] Activating service name='org.gtk.vfs.UDisks2VolumeMonitor' requested by ':1.9' (uid=1000 pid=17820 comm="/usr/bin/gnome-shell ")
dbus-daemon[17775]: [session uid=1000 pid=17775] Successfully activated service 'org.gtk.vfs.UDisks2VolumeMonitor'
dbus-daemon[17775]: [session uid=1000 pid=17775] Activating service name='org.gtk.vfs.MTPVolumeMonitor' requested by ':1.9' (uid=1000 pid=17820 comm="/usr/bin/gnome-shell ")
dbus-daemon[17775]: [session uid=1000 pid=17775] Successfully activated service 'org.gtk.vfs.MTPVolumeMonitor'
dbus-daemon[17775]: [session uid=1000 pid=17775] Activating service name='org.freedesktop.Tracker1' requested by ':1.35' (uid=1000 pid=17989 comm="gdbus call -e -d org.freedesktop.DBus -o /org/free")
dbus-daemon[17775]: [session uid=1000 pid=17775] Successfully activated service 'org.freedesktop.Tracker1'
dbus-daemon[17775]: [session uid=1000 pid=17775] Activating service name='org.gnome.Terminal' requested by ':1.36' (uid=1000 pid=17987 comm="gnome-terminal ")
Display does not support owner-change; copy/paste will be broken!
dbus-daemon[17775]: [session uid=1000 pid=17775] Successfully activated service 'org.gnome.Terminal'
dbus-daemon[17775]: [session uid=1000 pid=17775] Activating service name='org.freedesktop.systemd1' requested by ':1.8' (uid=1000 pid=17776 comm="/usr/lib/gnome-session-binary ")
dbus-daemon[17775]: [session uid=1000 pid=17775] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
A connection to the bus can't be made
$ systemctl --user status dbus.service
● dbus.service - D-Bus User Message Bus
   Loaded: loaded (/usr/lib/systemd/user/dbus.service; static; vendor preset: enabled)
   Active: active (running) since Mon 2018-05-21 10:39:42 CEST; 8h ago
     Docs: man:dbus-daemon(1)
 Main PID: 1484 (dbus-daemon)
   CGroup: /user.slice/user-1000.slice/user@1000.service/dbus.service
           ├─ 1484 /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
           ├─ 2254 /usr/lib/dconf-service
           └─10765 /usr/bin/nautilus --gapplication-service
@chrissound
Copy link

@chrissound chrissound commented Mar 9, 2019

I'm also encountering this issue on Nixos... Anyone else?

@chrissound
Copy link

@chrissound chrissound commented Mar 9, 2019

https://serverfault.com/a/887298/135542

export XDG_RUNTIME_DIR=/run/user/$(id -u) seems to fix it...

@udovdh
Copy link

@udovdh udovdh commented Mar 10, 2019

Not here. some dbus process is not properly started in the init 3/init 5 circus.
Same as gnome-shell not being fully killed when doing init 3.

@caleb-allen
Copy link

@caleb-allen caleb-allen commented Mar 23, 2020

Also not working for me on Manjaro

@bphd
Copy link

@bphd bphd commented Apr 7, 2020

Not working on Arch today (Freshly installed gnome, normal Arch repo.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
You can’t perform that action at this time.