You are not logged in.
Okay, so I had systemd installed already on to my computer before arch made the switch to systemd. Then I ran updates one day, rebooted to check how everything turned out and arch put me out to tty1. Now the thing that had me puzzled is when I switched manually to tty7 lightdm and my DE loaded fine.
Reproducable: Every system boot.
Things I've tried: relinking all the right systemd files to start graphical.target and lightdm.service, reinstalling all programs related
Any help appreciated
EDIT: IGNORE THE TITLE THERE WAS NO OFFICIAL SWITCH
ALSO IF YOU ARE GOING TO POST PLEASE READ THE RELEVANT INFO DON'T JUST READ HALF AND BE DETRIMENTAL TO THE POST BY TAKING AWAY VALUABLE SPACE MAKING IT HARDER TO FIND THE TRUE INFO.
Last edited by neighborhoodhacker (2012-08-20 05:29:16)
Offline
How did you start your DM before? GDM, KDM, Slim?? Did you use /etc/inittab, or had you used your DAEMONS array?
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way
Offline
The way I started DM before was lightdm through systemd it was set up correctly and nothing changes besides the update
sudo systemctl enable graphical.target
sudo systemctl enable lightdm.serviceworked through systemd before update
Last edited by neighborhoodhacker (2012-08-19 04:41:36)
Offline
Sorry, I misunderstood.
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way
Offline
Any ideas sir ewaller?
Offline
Is the lightdm service file the one that has been suggested in the AUR comments (https://aur.archlinux.org/packages.php?ID=40708)? Because this one isn't quite right:
WantedBy=graphical.target
Alias=display-manager.serviceas far as I can see, this will cause lightdm to be started twice, which may be what is causing the problem.
Remove the WantedBy=graphical.target (you may also want to suggest this in the AUR comments). Then do a "systemctl reenable lightdm.service".
Offline
What official switch? There's no such thing on the front page.
The systemd-tools package is not systemd: http://www.archlinux.org/news/systemd-t … aces-udev/
Please choose your titles more carefully.
I have made a personal commitment not to reply in topics that start with a lowercase letter. Proper grammar and punctuation is a sign of respect, and if you do not show any, you will NOT receive any help (at least not from me).
Offline
Any ideas sir ewaller?
Nothing solid. It had been working before, now it is not.
If it were my machine, I would use systemctl to check the status of services -- which one's did it try to start, which ones terminated normally, what died, what is still running.
I would check the links in /etc/systemd/system to ensure they are there for every service you explicitly enabled, and that they point to something valid.
I would look at your pacman logs and see what packages were updated, then I would go through the list of files in all the relevant packages and see if any of them are related to your problem. If you find a relevant .service file was in the package, find out if and how it changed.
Look through the output of sudo journalctl for any clues.
Try hand starting the service that starts your DM. I don't know which file it is - sorry ![]()
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way
Offline
What official switch? There's no such thing on the front page.
The systemd-tools package is not systemd: http://www.archlinux.org/news/systemd-t … aces-udev/
Please choose your titles more carefully.
Please read the post more carefully. I said looking back there probably wasn't one I was basing it off all the buzz and a weird update screwing with my system
Offline
Is the lightdm service file the one that has been suggested in the AUR comments (https://aur.archlinux.org/packages.php?ID=40708)? Because this one isn't quite right:
WantedBy=graphical.target Alias=display-manager.serviceas far as I can see, this will cause lightdm to be started twice, which may be what is causing the problem.
Remove the WantedBy=graphical.target (you may also want to suggest this in the AUR comments). Then do a "systemctl reenable lightdm.service".
If you read what I wrote I said it worked beforehand and then not after. I tried both services, but beforehand I had also got the service mentioned by you working by tweaking it to match certain things in the default lightdm service and still getting the seemless transition. THE ONLY THING CHANGED WAS THE UPDATE
Last edited by neighborhoodhacker (2012-08-19 20:16:07)
Offline
neighborhoodhacker wrote:Any ideas sir ewaller?
Nothing solid. It had been working before, now it is not.
If it were my machine, I would use systemctl to check the status of services -- which one's did it try to start, which ones terminated normally, what died, what is still running.
I would check the links in /etc/systemd/system to ensure they are there for every service you explicitly enabled, and that they point to something valid.
I would look at your pacman logs and see what packages were updated, then I would go through the list of files in all the relevant packages and see if any of them are related to your problem. If you find a relevant .service file was in the package, find out if and how it changed.Look through the output of sudo journalctl for any clues.
Try hand starting the service that starts your DM. I don't know which file it is - sorry
I have relinked everything already. Reinstalled all related packages. Tried a normal and modified service file. I don't really know what else to do. I will check the journalctl to see if I can find anything relevant.
EDIT: found nothing relevant in journalctl. It doesn't seem to throw any error or do anything funny besides just not start to the right tty
Also, what could I gain from manually starting the service. I will try but idk how it will help. Many many thanks for your valuable time.
EDIT AGAIN: I manually stopped/started lightdm-plymouth.service and it brought me back to tty7... idk. Is this where I go write a systemd bug report?
Last edited by neighborhoodhacker (2012-08-19 20:20:49)
Offline
Have you enabled multi-user.target? If so it will default to init 3..
If yes disable multi-user.target. This happened to me when switching to systemd. I have xfce and slim.
Offline
Great idea but:
sudo systemctl is-enabled multi-user.target
disabledOffline
Okay well I got rid of initscripts and switched to pure systemd boot up. No longer do I stay on tty1, but a new problem has arrised seeing as how plymouth quit working correctly. Oh well. Now at least I have a smooth boot and am going to be figuring out how to switch the title to solved... hmm..
Offline