• \[SOLVED\] System Crashes Twice after Updates Applied


    I applied the updates today and my system has crashed twice after reboot. I assume some kind of log is required to be posted. If someone can tell me where to find it, I would be happy to supply it.

    Thanks!

  • I applied the updates today and my system has crashed twice after reboot. I assume some kind of log is required to be posted. If someone can tell me where to find it, I would be happy to supply it.

    Thanks!

  • Hi,

    See this post for how to get the logs: [http://forum.antergos.com/viewtopic.php?f=32&t=2227&p=10438&hilit=journal+logs#p10417][0]">viewtopic.php?f=32&t=2227&p=10438&hilit=journal+logs#p10417

    Cheers!

    [0]: <a href=

  • Thanks, I will check it out. Oddly enough, the issue has not happened today.

  • Hi,

    Just out of curiosity, could you post here also /var/log/pacman.log? This way we’ll see what you did update.

  • @“karasu”:xkx00qf0 said:

    Hi,

    Just out of curiosity, could you post here also /var/log/pacman.log? This way we’ll see what you did update.[/quote:xkx00qf0]
    For some reason I can’t get the code tag to work. I’ve done this before so I’m not sure what is going on. My computer just froze so I would like the file looked at…

    Help! 🙂

    Could that file be too large?

    Edit: That file is too large. What can I do about this?

  • @“parkslope”:swng2bv5 said:

    I applied the updates today and my system has crashed twice after reboot. I assume some kind of log is required to be posted. If someone can tell me where to find it, I would be happy to supply it.

    Thanks![/quote:swng2bv5]

    sure you dont have any hardware issues? i noticed this thread and the firefox thread about crashing.

    i would check memory 1st. smooth on my side.

  • Hi,

    Get me the last 20 lines, you can use tail for this:

    tail -n 20 /var/log/pacman.log \> /tmp/pacman20.log
    

    And then post here /tmp/pacman20.log

    Cheers!

  • @“karasu”:312996xe said:

    Hi,

    Get me the last 20 lines, you can use tail for this:

    tail -n 20 /var/log/pacman.log \> /tmp/pacman20.log
    

    And then post here /tmp/pacman20.log

    Cheers![/quote:312996xe]

    Thanks, I’m curious as to what is going on. I hope it isn’t serious.

    [2014-09-30 14:50] [PACMAN] starting full system upgrade  
    > [2014-09-30 16:40] [PACMAN] Running 'pacman -Syu --color never'  
    > [2014-09-30 16:40] [PACMAN] synchronizing package lists  
    > [2014-09-30 16:40] [PACMAN] starting full system upgrade  
    > [2014-09-30 17:22] [PACMAN] Running 'pacman -Syu --color never'  
    > [2014-09-30 17:22] [PACMAN] synchronizing package lists  
    > [2014-09-30 17:22] [PACMAN] starting full system upgrade  
    > [2014-09-30 17:22] [PACMAN] Running 'pacman --color never -Sy'  
    > [2014-09-30 17:22] [PACMAN] synchronizing package lists  
    > [2014-09-30 17:22] [PACMAN] starting full system upgrade  
    > [2014-09-30 18:10] [PACMAN] Running 'pacman -Syu --color never'  
    > [2014-09-30 18:10] [PACMAN] synchronizing package lists  
    > [2014-09-30 18:10] [PACMAN] starting full system upgrade  
    > [2014-09-30 18:11] [PACMAN] Running 'pacman --color never -Sy'  
    > [2014-09-30 18:11] [PACMAN] synchronizing package lists  
    > [2014-09-30 18:11] [PACMAN] starting full system upgrade  
    > [2014-09-30 18:11] [PACMAN] Running 'pacman -Sy --color never'  
    > [2014-09-30 18:11] [PACMAN] synchronizing package lists  
    > [2014-09-30 18:11] [PACMAN] Running 'pacman -Sc --color never'  
    > [2014-09-30 18:11] [PACMAN] Running 'pacman -Scc --color never'
    
  • I gave you the last 50 lines as the the 20 lines only had yesterday and this happened three days ago.

    [2014-09-29 16:35] [PACMAN] Running 'pacman -Syu --color never'  
    [2014-09-29 16:35] [PACMAN] synchronizing package lists  
    [2014-09-29 16:35] [PACMAN] starting full system upgrade  
    [2014-09-29 19:09] [PACMAN] Running 'pacman -Syu --color never'  
    [2014-09-29 19:09] [PACMAN] synchronizing package lists  
    [2014-09-29 19:09] [PACMAN] starting full system upgrade  
    [2014-09-30 10:39] [PACMAN] Running 'pacman -Syu --color never'  
    [2014-09-30 10:39] [PACMAN] synchronizing package lists  
    [2014-09-30 10:39] [PACMAN] starting full system upgrade  
    [2014-09-30 10:39] [PACMAN] upgraded libva (1.3.1-2 -\> 1.4.0-1)  
    [2014-09-30 10:39] [PACMAN] upgraded wayland (1.5.0-1 -\> 1.6.0-1)  
    [2014-09-30 10:40] [PACMAN] Running 'pacman --color never -Sy'  
    [2014-09-30 10:40] [PACMAN] synchronizing package lists  
    [2014-09-30 10:40] [PACMAN] starting full system upgrade  
    [2014-09-30 12:51] [PACMAN] Running 'pacman -Syu --color never'  
    [2014-09-30 12:51] [PACMAN] synchronizing package lists  
    [2014-09-30 12:51] [PACMAN] starting full system upgrade  
    [2014-09-30 14:50] [PACMAN] Running 'pacman -Syu --color never'  
    [2014-09-30 14:50] [PACMAN] synchronizing package lists  
    [2014-09-30 14:50] [PACMAN] starting full system upgrade  
    [2014-09-30 16:40] [PACMAN] Running 'pacman -Syu --color never'  
    [2014-09-30 16:40] [PACMAN] synchronizing package lists  
    [2014-09-30 16:40] [PACMAN] starting full system upgrade  
    [2014-09-30 17:22] [PACMAN] Running 'pacman -Syu --color never'  
    [2014-09-30 17:22] [PACMAN] synchronizing package lists  
    [2014-09-30 17:22] [PACMAN] starting full system upgrade  
    [2014-09-30 17:22] [PACMAN] Running 'pacman --color never -Sy'  
    [2014-09-30 17:22] [PACMAN] synchronizing package lists  
    [2014-09-30 17:22] [PACMAN] starting full system upgrade  
    [2014-09-30 18:10] [PACMAN] Running 'pacman -Syu --color never'  
    [2014-09-30 18:10] [PACMAN] synchronizing package lists  
    [2014-09-30 18:10] [PACMAN] starting full system upgrade  
    [2014-09-30 18:11] [PACMAN] Running 'pacman --color never -Sy'  
    [2014-09-30 18:11] [PACMAN] synchronizing package lists  
    [2014-09-30 18:11] [PACMAN] starting full system upgrade  
    [2014-09-30 18:11] [PACMAN] Running 'pacman -Sy --color never'  
    [2014-09-30 18:11] [PACMAN] synchronizing package lists  
    [2014-09-30 18:11] [PACMAN] Running 'pacman -Sc --color never'  
    [2014-09-30 18:11] [PACMAN] Running 'pacman -Scc --color never'  
    [2014-10-01 10:28] [PACMAN] Running 'pacman -Syu --color never'  
    [2014-10-01 10:28] [PACMAN] synchronizing package lists  
    [2014-10-01 10:28] [PACMAN] starting full system upgrade  
    [2014-10-01 10:28] [PACMAN] upgraded cinnamon-control-center (2.2.10-3 -\> 2.2.11-1)  
    [2014-10-01 10:28] [PACMAN] upgraded git (2.1.1-1 -\> 2.1.2-1)  
    [2014-10-01 10:28] [ALPM] warning: /etc/lightdm/lightdm.conf installed as /etc/lightdm/lightdm.conf.pacnew  
    [2014-10-01 10:28] [PACMAN] upgraded lightdm (1:1.10.1-3 -\> 1:1.12.0-1)  
    [2014-10-01 10:28] [PACMAN] upgraded os-prober (1.58-1 -\> 1.58-3)  
    [2014-10-01 10:28] [PACMAN] Running 'pacman --color never -Sy'  
    [2014-10-01 10:28] [PACMAN] synchronizing package lists  
    [2014-10-01 10:28] [PACMAN] starting full system upgrade
    
  • Hi,

    I don’t see anything strange in those updates (in fact I have the same ones).

    Please, post your logs as lots0logs suggested before.

    Cheers!

  • @“karasu”:3u67fc7a said:

    Hi,

    I don’t see anything strange in those updates (in fact I have the same ones).

    Please, post your logs as lots0logs suggested before.

    Cheers![/quote:3u67fc7a]
    After reviewing that thread, I assume you mean this command (sudo journalctl -b 0 > ~/journal.log), which gives me today’s log. I assume I would need to do this the next time any event like a reboot or freeze were to occur. If I’m wrong, please let me know. So far today, nothing has happened! 🙂

  • There is a problem with lightdm. Log out of Cinnamon, click my user name and I log right back into Cinnamon.

    If memory serves, there was some error message this week about lightdm during one of the updates. I didn’t take notice as I rarely use Gnome.

    Any thoughts guys? The log is way to large to post.

    Thanks.

    Edit: I thought the lightdm log might help.

     DEBUG: Logging to /var/log/lightdm/lightdm.log  
    [+0.09s] DEBUG: Starting Light Display Manager 1.12.0, UID=0 PID=400  
    [+0.09s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d  
    [+0.09s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d  
    [+0.09s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d  
    [+0.09s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf  
    [+0.09s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager  
    [+0.09s] DEBUG: Registered seat module xlocal  
    [+0.09s] DEBUG: Registered seat module xremote  
    [+0.09s] DEBUG: Registered seat module unity  
    [+0.93s] DEBUG: Monitoring logind for seats  
    [+0.93s] DEBUG: New seat added from logind: seat0  
    [+0.93s] DEBUG: Seat seat0: Starting  
    [+0.93s] DEBUG: Seat seat0: Creating user session  
    [+2.66s] DEBUG: Loading users from org.freedesktop.Accounts  
    [+2.66s] DEBUG: User /org/freedesktop/Accounts/User1000 added  
    [+2.71s] DEBUG: Seat seat0: Creating display server of type x  
    [+2.71s] DEBUG: Could not run plymouth --ping: Failed to execute child process "plymouth" (No such file or directory)  
    [+2.71s] DEBUG: Using VT 1  
    [+2.71s] DEBUG: Seat seat0: Starting local X display on VT 1  
    [+2.71s] DEBUG: DisplayServer x-0: Logging to /var/log/lightdm/x-0.log  
    [+2.71s] DEBUG: DisplayServer x-0: Writing X server authority to /run/lightdm/root/:0  
    [+2.71s] DEBUG: DisplayServer x-0: Launching X Server  
    [+2.74s] DEBUG: Launching process 430: /usr/sbin/X :0 -seat seat0 -auth /run/lightdm/root/:0 -nolisten tcp vt1 -novtswitch  
    [+2.74s] DEBUG: DisplayServer x-0: Waiting for ready signal from X server :0  
    [+2.74s] DEBUG: Acquired bus name org.freedesktop.DisplayManager  
    [+2.74s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0  
    [+8.24s] DEBUG: Got signal 10 from process 430  
    [+8.24s] DEBUG: DisplayServer x-0: Got signal from X server :0  
    [+8.24s] DEBUG: DisplayServer x-0: Connecting to XServer :0  
    [+8.24s] DEBUG: Seat seat0: Display server ready, starting session authentication  
    [+8.24s] DEBUG: Session pid=467: Started with service 'lightdm-autologin', username 'chazdg50'  
    [+8.42s] DEBUG: Session pid=467: Authentication complete with return value 0: Success  
    [+8.42s] DEBUG: Seat seat0: Session authenticated, running command  
    [+8.42s] DEBUG: Registering session with bus path /org/freedesktop/DisplayManager/Session0  
    [+8.42s] DEBUG: Session pid=467: Running command /etc/lightdm/Xsession cinnamon-session-cinnamon  
    [+8.42s] DEBUG: Creating shared data directory /var/lib/lightdm-data/chazdg50  
    [+8.42s] DEBUG: Session pid=467: Logging to .xsession-errors  
    [+8.73s] DEBUG: Activating VT 1  
    [+8.73s] DEBUG: Activating login1 session c1  
    [+9.93s] DEBUG: User /org/freedesktop/Accounts/User1000 changed  
    [+105.92s] DEBUG: Session pid=467: Exited with return value 0  
    [+105.92s] DEBUG: Seat seat0: Session stopped  
    [+105.92s] DEBUG: Seat seat0: Stopping display server, no sessions require it  
    [+105.92s] DEBUG: Sending signal 15 to process 430  
    [+106.47s] DEBUG: Process 430 exited with return value 0  
    [+106.47s] DEBUG: DisplayServer x-0: X server stopped  
    [+106.47s] DEBUG: Releasing VT 1  
    [+106.47s] DEBUG: DisplayServer x-0: Removing X server authority /run/lightdm/root/:0  
    [+106.47s] DEBUG: Seat seat0: Display server stopped  
    [+106.47s] DEBUG: Seat seat0: Active display server stopped, starting greeter  
    [+106.47s] DEBUG: Seat seat0: Creating greeter session  
    [+106.51s] DEBUG: Seat seat0: Creating display server of type x  
    [+106.51s] DEBUG: Using VT 1  
    [+106.51s] DEBUG: Seat seat0: Starting local X display on VT 1  
    [+106.51s] DEBUG: DisplayServer x-0: Logging to /var/log/lightdm/x-0.log  
    [+106.51s] DEBUG: DisplayServer x-0: Writing X server authority to /run/lightdm/root/:0  
    [+106.51s] DEBUG: DisplayServer x-0: Launching X Server  
    [+106.51s] DEBUG: Launching process 797: /usr/sbin/X :0 -seat seat0 -auth /run/lightdm/root/:0 -nolisten tcp vt1 -novtswitch  
    [+106.51s] DEBUG: DisplayServer x-0: Waiting for ready signal from X server :0  
    [+107.02s] DEBUG: Got signal 10 from process 797  
    [+107.02s] DEBUG: DisplayServer x-0: Got signal from X server :0  
    [+107.02s] DEBUG: DisplayServer x-0: Connecting to XServer :0  
    [+107.02s] DEBUG: Seat seat0: Display server ready, starting session authentication  
    [+107.02s] DEBUG: Session pid=808: Started with service 'lightdm-greeter', username 'lightdm'  
    [+107.09s] DEBUG: Session pid=808: Authentication complete with return value 0: Success  
    [+107.09s] DEBUG: Seat seat0: Session authenticated, running command  
    [+107.09s] DEBUG: Session pid=808: Running command /usr/sbin/lightdm-webkit-greeter  
    [+107.09s] DEBUG: Creating shared data directory /var/lib/lightdm-data/lightdm  
    [+107.09s] DEBUG: Session pid=808: Logging to /var/log/lightdm/x-0-greeter.log  
    [+107.13s] DEBUG: Activating VT 1  
    [+107.13s] DEBUG: Activating login1 session c2  
    [+107.44s] DEBUG: User /org/freedesktop/Accounts/User1000 changed  
    [+109.73s] DEBUG: Session pid=808: Greeter connected version=1.12.0 resettable=false  
    [+114.51s] DEBUG: Session pid=808: Greeter start authentication for chazdg50  
    [+114.51s] DEBUG: Session pid=836: Started with service 'lightdm-autologin', username 'chazdg50'  
    [+114.53s] DEBUG: Session pid=836: Authentication complete with return value 0: Success  
    [+114.53s] DEBUG: Session pid=808: Authenticate result for user chazdg50: Success  
    [+114.53s] DEBUG: Session pid=808: User chazdg50 authorized  
    [+114.53s] DEBUG: Session pid=808: Greeter requests session cinnamon  
    [+114.53s] DEBUG: Seat seat0: Stopping greeter; display server will be re-used for user session  
    [+114.53s] DEBUG: Session pid=808: Sending SIGTERM  
    [+114.59s] DEBUG: Session pid=808: Greeter closed communication channel  
    [+114.59s] DEBUG: Session pid=808: Exited with return value 0  
    [+114.59s] DEBUG: Seat seat0: Session stopped  
    [+114.59s] DEBUG: Seat seat0: Greeter stopped, running session  
    [+114.59s] DEBUG: Registering session with bus path /org/freedesktop/DisplayManager/Session1  
    [+114.59s] DEBUG: Session pid=836: Running command /etc/lightdm/Xsession cinnamon-session-cinnamon  
    [+114.59s] DEBUG: Creating shared data directory /var/lib/lightdm-data/chazdg50  
    [+114.59s] DEBUG: Session pid=836: Logging to .xsession-errors  
    [+114.61s] DEBUG: Activating VT 1  
    [+114.61s] DEBUG: Activating login1 session c3  
    [+116.04s] DEBUG: User /org/freedesktop/Accounts/User1000 changed  
    [+124.15s] DEBUG: Session pid=836: Exited with return value 0  
    [+124.15s] DEBUG: Seat seat0: Session stopped  
    [+124.15s] DEBUG: Seat seat0: Stopping display server, no sessions require it  
    [+124.15s] DEBUG: Sending signal 15 to process 797  
    [+124.68s] DEBUG: Process 797 exited with return value 0  
    [+124.68s] DEBUG: DisplayServer x-0: X server stopped  
    [+124.68s] DEBUG: Releasing VT 1  
    [+124.68s] DEBUG: DisplayServer x-0: Removing X server authority /run/lightdm/root/:0  
    [+124.68s] DEBUG: Seat seat0: Display server stopped  
    [+124.68s] DEBUG: Seat seat0: Active display server stopped, starting greeter  
    [+124.68s] DEBUG: Seat seat0: Creating greeter session  
    [+124.68s] DEBUG: Seat seat0: Creating display server of type x  
    [+124.68s] DEBUG: Using VT 1  
    [+124.68s] DEBUG: Seat seat0: Starting local X display on VT 1  
    [+124.68s] DEBUG: DisplayServer x-0: Logging to /var/log/lightdm/x-0.log  
    [+124.68s] DEBUG: DisplayServer x-0: Writing X server authority to /run/lightdm/root/:0  
    [+124.68s] DEBUG: DisplayServer x-0: Launching X Server  
    [+124.68s] DEBUG: Launching process 1046: /usr/sbin/X :0 -seat seat0 -auth /run/lightdm/root/:0 -nolisten tcp vt1 -novtswitch  
    [+124.68s] DEBUG: DisplayServer x-0: Waiting for ready signal from X server :0  
    [+125.12s] DEBUG: Got signal 10 from process 1046  
    [+125.12s] DEBUG: DisplayServer x-0: Got signal from X server :0  
    [+125.12s] DEBUG: DisplayServer x-0: Connecting to XServer :0  
    [+125.13s] DEBUG: Seat seat0: Display server ready, starting session authentication  
    [+125.13s] DEBUG: Session pid=1060: Started with service 'lightdm-greeter', username 'lightdm'  
    [+125.14s] DEBUG: Session pid=1060: Authentication complete with return value 0: Success  
    [+125.14s] DEBUG: Seat seat0: Session authenticated, running command  
    [+125.14s] DEBUG: Session pid=1060: Running command /usr/sbin/lightdm-webkit-greeter  
    [+125.14s] DEBUG: Creating shared data directory /var/lib/lightdm-data/lightdm  
    [+125.14s] DEBUG: Session pid=1060: Logging to /var/log/lightdm/x-0-greeter.log  
    [+125.15s] DEBUG: Activating VT 1  
    [+125.15s] DEBUG: Activating login1 session c4  
    [+125.27s] DEBUG: Session pid=1060: Greeter connected version=1.12.0 resettable=false  
    [+125.68s] DEBUG: User /org/freedesktop/Accounts/User1000 changed  
    [+136.39s] DEBUG: Session pid=1060: Greeter start authentication for chazdg50  
    [+136.39s] DEBUG: Session pid=1087: Started with service 'lightdm-autologin', username 'chazdg50'  
    [+136.41s] DEBUG: Session pid=1087: Authentication complete with return value 0: Success  
    [+136.41s] DEBUG: Session pid=1060: Authenticate result for user chazdg50: Success  
    [+136.41s] DEBUG: Session pid=1060: User chazdg50 authorized  
    [+136.41s] DEBUG: Session pid=1060: Greeter requests session cinnamon  
    [+136.41s] DEBUG: Seat seat0: Stopping greeter; display server will be re-used for user session  
    [+136.41s] DEBUG: Session pid=1060: Sending SIGTERM  
    [+136.42s] DEBUG: Session pid=1060: Greeter closed communication channel  
    [+136.42s] DEBUG: Session pid=1060: Exited with return value 0  
    [+136.42s] DEBUG: Seat seat0: Session stopped  
    [+136.42s] DEBUG: Seat seat0: Greeter stopped, running session  
    [+136.42s] DEBUG: Registering session with bus path /org/freedesktop/DisplayManager/Session2  
    [+136.43s] DEBUG: Session pid=1087: Running command /etc/lightdm/Xsession cinnamon-session-cinnamon  
    [+136.43s] DEBUG: Creating shared data directory /var/lib/lightdm-data/chazdg50  
    [+136.43s] DEBUG: Session pid=1087: Logging to .xsession-errors  
    [+136.45s] DEBUG: Activating VT 1  
    [+136.45s] DEBUG: Activating login1 session c5  
    [+137.92s] DEBUG: User /org/freedesktop/Accounts/User1000 changed  
    [+3693.53s] DEBUG: User /org/freedesktop/Accounts/User1000 changed  
    [+3695.85s] DEBUG: User /org/freedesktop/Accounts/User1000 changed
    
  • Yes, you’ll need to wait for the problem to occur and then post the logs. You should compress the log files and post them as an attachment 🙂

  • @“lots.0.logs”:f7gjlzv2 said:

    Yes, you’ll need to wait for the problem to occur and then post the logs. You should compress the log files and post them as an attachment :-)[/quote:f7gjlzv2]
    Yeah, I thought of that. The problem is my 7zip file will not open, never has. I just reinstalled it with no luck, which is what I’m having lately. 😉

    The problem with lightdm started with the cinnamon update earlier this week, if that is at all helpful.

    Edit: Isn’t 7zip a command line program? If so, I have no idea how to use it.

  • Yes 7zip is a command line program. However, just use tar which is more than sufficient for a few log files:[command:3a7vxag7]tar -cvf mylogs.tar journals[/command:3a7vxag7]The command assumes you’ve saved the journals in a directory named “journals” and that you cd to the same dir as the “journals” dir before running it.

    Cheers!

  • @“lots.0.logs”:2wv5b35k said:

    Yes 7zip is a command line program. However, just use tar which is more than sufficient for a few log files:[command:2wv5b35k]tar -cvf mylogs.tar journals[/command:2wv5b35k]The command assumes you’ve saved the journals in a directory named “journals” and that you cd to the same dir as the “journals” dir before running it.

    Cheers![/quote:2wv5b35k]
    Clearly I don’t have much of a clue with the command line. I created a Journals file. I have my Journal.log file in there but can’t seem to get the light.dm.log file to save. I think you need a third log file (pacman.log) which isn’t saving in my Journal folder. Can you give me a hint how to to do this? 😉

    I think the main issue is the lightdm problem. Reinstalling completely removes the Antegros lightdm theme.

  • I updated my system, rebooted and now I get a black screen, as I suspected would happen at some point.

    How do I work around this as my user name and password are not recognized.

    Help…

  • When you reach the black screen follow these steps:

    1. Ctrl+Alt +F2 should give you a terminal login. Go ahead and log in.
    2. [command:3d57clk0]sudo pacman -Syyu
    sudo pacman -R lightdm-webkit-theme-antergos --nosave
    sudo pacman -S lightdm-webkit-theme-antergos --force
    sudo sed -i ‘s/#user-session=.*/user-session=cinnamon/2’ /etc/lightdm/lightdm.conf[/command:3d57clk0]
    3. Reboot

    Let me know how it goes.

  • @“lots.0.logs”:10b56jn3 said:

    When you reach the black screen follow these steps:

    1. Ctrl+Alt +F2 should give you a terminal login. Go ahead and log in.
    2. [command:10b56jn3]sudo pacman -Syyu
    sudo pacman -R lightdm-webkit-theme-antergos --nosave
    sudo pacman -S lightdm-webkit-theme-antergos --force
    sudo sed -i ‘s/#user-session=.*/user-session=cinnamon/2’ /etc/lightdm/lightdm.conf[/command:10b56jn3]
    3. Reboot

    Let me know how it goes.[/quote:10b56jn3]
    Ctrl+Alt +F2 does not bring up a terminal. I can’t login as Antergos is not recognizing my user name or password. I think I’m screwed.

Posts 33Views 4186
Log in to reply
Bloom Email Optin Plugin

Looks like your connection to Antergos Community Forum was lost, please wait while we try to reconnect.