You are not logged in.
Pages: 1
Systemd-227-1 won't start gnome.. Stays hanging at "reached target graphical interface"....
systemd-226-3 does not have the same problem..
Anybody else has this problem..
Last edited by whoop (2015-10-21 22:25:33)
Offline
Anybody else has this problem..
No, been running GNOME with systemd 227 for a bit now with no problems.
Can you start GNOME manually (ie, via .xinitrc & `startx`) if you set default.target to multi-user?
Offline
I have the same problem. At first, thought it was linux-ck issue, but as I tried to boot using linux and it fallback image, I noticed this conflict too.
I can't even switch between tty
Edit1: later today, I'll grab my /var/log/pacman.log and post it here
Edit2:
For me, it was really conflict between systemd and gnome. Using abs, I downgraded to systemd 226-3 and everything is fine now. I would have used downgrade, but I'm stupid and for some reason that I really can't explain, I cleared my cache.
I recommend as a temporary fix, a downgrade. If you didn't clear pacman cache, try to boot using a live USB or a DVD, mount your partitions and follow the wiki to downgrade your systemd.
Using the pacman cache
If a package was installed at an earlier stage, and the pacman cache was not cleaned, install an earlier version from /var/cache/pacman/pkg/.
This process will remove the current package and install the older version. Dependency changes will be handled, but pacman will not handle version conflicts. If a library or other package needs to be downgraded with the packages, please be aware that you will have to downgrade this package yourself as well.
# cd /var/cache/pacman/pkg/
# pacman -U <file_name_of_the_package>
Last edited by vinnom (2015-10-18 06:08:03)
Offline
Also had this issue, downgrading systemd to 226-3 worked for me as well. gnome-shell and friends version 3.18.1-2. Thank you!
Offline
same issue - also solved by downgrading systemd to 226-3 - thank you !
Offline
same issue and "solution" - systemd downgrade
Offline
Can you start GNOME manually (ie, via .xinitrc & `startx`) if you set default.target to multi-user?
I can start it manually with systemd-227-1.
Last edited by whoop (2015-10-19 23:57:01)
Offline
Same issue in my desktop and downgrade systemd-226-3 to solve.
It is strange that systemd-227-1 works fine with gnome3 in my notebook but breakes gnome3 in my desktop. The difference is the desktop with an nvidia video card and the NB with an intel video.
Last edited by fanlusi (2015-10-20 13:54:25)
Offline
Please stop with the "me too" posts: they add nothing to the thread
https://wiki.archlinux.org/index.php/Fo … mpty_posts
Offline
The following solves my problem (mostly):
uncomment the WaylandEnable=false line in /etc/gdm/custom.conf
Hit Escape key to jump to desktop workes for me (wait for fix from gnome to bypass this)..
Offline
Hey whoop,
thank you very much for the hint
uncomment the WaylandEnable=false line in /etc/gdm/custom.conf
Since installing gnome on my new laptop I have had issues with mouse lags in the greeter's login screen(s) in gdm. (When using the nvidia drivers. Nouveau seems OK) Also, in the password screen, the first character of the password was automatically doubled. Once the gnome shell started, the mouse was OK.
Solution so far was to switch to sddm. It offers Gnome and Gnome on Wayland as shell to start, and when I picked the Wayland option, the mouse lag was equally bad. So it's probably a Wayland problem.
Offline
Since installing gnome on my new laptop I have had issues with mouse lags in the greeter's login screen(s) in gdm. (When using the nvidia drivers. Nouveau seems OK)
afaik nvidia drivers still don't have full wayland support yet (nouveau should work though), and gdm tries to start on wayland instead of X by default since 3.16. Uncommenting the line whoop mentioned disables wayland support from gdm, so it should work as a solution for now.
Offline
Why then did this problem not occur with 3.16 or even 3.18 until systemd 227?
Offline
Pages: 1