after update: failed to start x-server

Forum Forums New users New Users and General Questions after update: failed to start x-server

This topic contains 7 replies, has 6 voices, and was last updated by skidoo Apr 15-4:05 pm.

Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • #20389
    Member
    Avatar
    jerry99

    I started installing antiX with 17.3.1, it run satisfying
    Then made an update. Which version I use now I do not know, because I did not find where to see the version number.
    Now the system stops at the login.
    I can proceed by logging in as a user and type startx, but I want the startup to icewm or jwm

    #20394
    Forum Admin
    anticapitalista
    anticapitalista

    It seems you are using testing or sid repos as I have the same intermittent issue on my antiX-sid install.
    I haven’t found the cause nor a solution yet.

    Philosophers have interpreted the world in many ways; the point is to change it.

    #20493
    Member
    wildstar84
    wildstar84

    I’d check your slim log (/var/log/slim.log), then auth.log and Xorg.0.log from the terminal. Should be something amiss shown in one of those.

    Regards,

    Jim

    #20496
    Member
    male
    male

    I am using antiX-17.4 sid here

    This is where I wrote, https://forum.mxlinux.org/viewtopic.php?f=40&t=41039&start=130#p495697
    I always have to log on to slim twice when starting cold. After the first try I always see short tty1 to have to use Slim a second time.

    A warm start is always correct.

    What I don’t understand is, why is sudo listed in the auth.log protocol again and again, when I explicitly don’t use sudo on the system, but su.

    auth.log excerpt from 10 to 13 April 2019 (anti, maybe you can take a look at it)

    auth.log_vom10-13-April19
    
    Apr 10 10:46:56 antix17-4 slim: pam_unix(slim:session): session opened for user male by (uid=0)
    Apr 10 10:46:56 antix17-4 slim: pam_unix(slim:session): session closed for user male
    Apr 10 10:47:03 antix17-4 slim: pam_unix(slim:session): session opened for user male by (uid=0)
    Apr 10 11:02:37 antix17-4 su: (to root) male on pts/1
    Apr 10 11:02:37 antix17-4 su: pam_unix(su:session): session opened for user root by (uid=1000)
    Apr 10 11:16:41 antix17-4 su: pam_unix(su:session): session closed for user root
    Apr 10 11:17:01 antix17-4 CRON[9273]: pam_unix(cron:session): session opened for user root by (uid=0)
    Apr 10 11:17:01 antix17-4 CRON[9273]: pam_unix(cron:session): session closed for user root
    Apr 10 11:17:39 antix17-4 su: (to root) male on pts/0
    Apr 10 11:17:39 antix17-4 su: pam_unix(su:session): session opened for user root by (uid=1000)
    Apr 10 11:22:31 antix17-4 su: pam_unix(su:session): session closed for user root
    Apr 10 11:22:57 antix17-4 sudo:     male : TTY=unknown ; PWD=/home/male ; USER=root ; COMMAND=/bin/chvt 1
    Apr 10 11:22:57 antix17-4 sudo: pam_unix(sudo:session): session opened for user root by (uid=0)
    Apr 10 11:22:57 antix17-4 sudo: pam_unix(sudo:session): session closed for user root
    Apr 10 11:22:57 antix17-4 sudo:     male : TTY=unknown ; PWD=/home/male ; USER=root ; COMMAND=/sbin/reboot
    Apr 10 11:22:57 antix17-4 sudo: pam_unix(sudo:session): session opened for user root by (uid=0)
    Apr 10 11:22:57 antix17-4 sudo: pam_unix(sudo:session): session closed for user root
    Apr 10 11:24:04 antix17-4 slim: pam_unix(slim:session): session opened for user male by (uid=0)
    Apr 10 11:24:05 antix17-4 slim: pam_unix(slim:session): session closed for user male
    Apr 10 11:24:11 antix17-4 slim: pam_unix(slim:session): session opened for user male by (uid=0)
    Apr 10 12:07:35 antix17-4 su: (to root) male on pts/0
    Apr 10 12:07:35 antix17-4 su: pam_unix(su:session): session opened for user root by (uid=1000)
    Apr 10 12:08:49 antix17-4 su: pam_unix(su:session): session closed for user root
    Apr 10 12:09:17 antix17-4 slim: pam_unix(slim:session): session closed for user male
    Apr 10 12:09:26 antix17-4 slim: pam_unix(slim:session): session opened for user male by (uid=0)
    Apr 10 12:17:01 antix17-4 CRON[15063]: pam_unix(cron:session): session opened for user root by (uid=0)
    Apr 10 12:17:01 antix17-4 CRON[15063]: pam_unix(cron:session): session closed for user root
    Apr 10 13:17:01 antix17-4 CRON[16133]: pam_unix(cron:session): session opened for user root by (uid=0)
    Apr 10 13:17:01 antix17-4 CRON[16133]: pam_unix(cron:session): session closed for user root
    Apr 10 14:17:01 antix17-4 CRON[17150]: pam_unix(cron:session): session opened for user root by (uid=0)
    Apr 10 14:17:01 antix17-4 CRON[17150]: pam_unix(cron:session): session closed for user root
    Apr 10 15:17:01 antix17-4 CRON[17884]: pam_unix(cron:session): session opened for user root by (uid=0)
    Apr 10 15:17:01 antix17-4 CRON[17884]: pam_unix(cron:session): session closed for user root
    Apr 10 15:59:35 antix17-4 su: (to root) male on pts/0
    Apr 10 15:59:35 antix17-4 su: pam_unix(su:session): session opened for user root by (uid=1000)
    Apr 10 16:00:12 antix17-4 su: pam_unix(su:session): session closed for user root
    Apr 10 16:05:01 antix17-4 su: (to root) male on pts/1
    Apr 10 16:05:01 antix17-4 su: pam_unix(su:session): session opened for user root by (uid=1000)
    Apr 10 16:05:25 antix17-4 su: pam_unix(su:session): session closed for user root
    Apr 10 16:05:32 antix17-4 su: (to root) male on pts/0
    Apr 10 16:05:32 antix17-4 su: pam_unix(su:session): session opened for user root by (uid=1000)
    Apr 10 16:06:16 antix17-4 su: pam_unix(su:session): session closed for user root
    Apr 10 16:17:01 antix17-4 CRON[19329]: pam_unix(cron:session): session opened for user root by (uid=0)
    Apr 10 16:17:01 antix17-4 CRON[19329]: pam_unix(cron:session): session closed for user root
    Apr 10 17:06:24 antix17-4 sudo:     male : TTY=unknown ; PWD=/home/male ; USER=root ; COMMAND=/usr/sbin/pm-suspend
    Apr 10 17:06:24 antix17-4 sudo: pam_unix(sudo:session): session opened for user root by (uid=0)
    Apr 10 19:26:32 antix17-4 sudo: pam_unix(sudo:session): session closed for user root
    Apr 10 20:17:01 antix17-4 CRON[22902]: pam_unix(cron:session): session opened for user root by (uid=0)
    Apr 10 20:17:01 antix17-4 CRON[22902]: pam_unix(cron:session): session closed for user root
    Apr 10 20:30:33 antix17-4 su: (to root) male on pts/1
    Apr 10 20:30:33 antix17-4 su: pam_unix(su:session): session opened for user root by (uid=1000)
    Apr 10 20:36:40 antix17-4 su: pam_unix(su:session): session closed for user root
    Apr 10 21:17:01 antix17-4 CRON[8169]: pam_unix(cron:session): session opened for user root by (uid=0)
    Apr 10 21:17:01 antix17-4 CRON[8169]: pam_unix(cron:session): session closed for user root
    Apr 10 21:34:47 antix17-4 sudo:     male : TTY=unknown ; PWD=/home/male ; USER=root ; COMMAND=/bin/chvt 1
    Apr 10 21:34:47 antix17-4 sudo: pam_unix(sudo:session): session opened for user root by (uid=0)
    Apr 10 21:34:47 antix17-4 sudo: pam_unix(sudo:session): session closed for user root
    Apr 10 21:34:47 antix17-4 sudo:     male : TTY=unknown ; PWD=/home/male ; USER=root ; COMMAND=/sbin/reboot
    Apr 10 21:34:47 antix17-4 sudo: pam_unix(sudo:session): session opened for user root by (uid=0)
    Apr 10 21:34:47 antix17-4 sudo: pam_unix(sudo:session): session closed for user root
    Apr 10 21:36:01 antix17-4 slim: pam_unix(slim:session): session opened for user male by (uid=0)
    Apr 10 21:36:01 antix17-4 slim: pam_unix(slim:session): session closed for user male
    Apr 10 21:36:09 antix17-4 slim: pam_unix(slim:session): session opened for user male by (uid=0)
    Apr 10 21:38:45 antix17-4 su: (to root) male on pts/0
    Apr 10 21:38:45 antix17-4 su: pam_unix(su:session): session opened for user root by (uid=1000)
    Apr 10 21:42:12 antix17-4 su: pam_unix(su:session): session closed for user root
    Apr 10 21:42:20 antix17-4 sudo:     male : TTY=unknown ; PWD=/home/male ; USER=root ; COMMAND=/bin/chvt 1
    Apr 10 21:42:20 antix17-4 sudo: pam_unix(sudo:session): session opened for user root by (uid=0)
    Apr 10 21:42:20 antix17-4 sudo: pam_unix(sudo:session): session closed for user root
    Apr 10 21:42:20 antix17-4 sudo:     male : TTY=unknown ; PWD=/home/male ; USER=root ; COMMAND=/sbin/reboot
    Apr 10 21:42:20 antix17-4 sudo: pam_unix(sudo:session): session opened for user root by (uid=0)
    Apr 10 21:42:20 antix17-4 sudo: pam_unix(sudo:session): session closed for user root
    Apr 12 12:06:22 antix17-4 slim: pam_unix(slim:session): session opened for user male by (uid=0)
    Apr 12 12:06:22 antix17-4 slim: pam_unix(slim:session): session closed for user male
    Apr 12 12:06:29 antix17-4 slim: pam_unix(slim:session): session opened for user male by (uid=0)
    Apr 12 12:08:28 antix17-4 su: (to root) male on pts/0
    Apr 12 12:08:28 antix17-4 su: pam_unix(su:session): session opened for user root by (uid=1000)
    Apr 12 12:09:48 antix17-4 su: pam_unix(su:session): session closed for user root
    Apr 12 12:11:17 antix17-4 su: (to root) male on pts/0
    Apr 12 12:11:17 antix17-4 su: pam_unix(su:session): session opened for user root by (uid=1000)
    Apr 12 12:13:27 antix17-4 su: pam_unix(su:session): session closed for user root
    Apr 12 12:17:01 antix17-4 CRON[4995]: pam_unix(cron:session): session opened for user root by (uid=0)
    Apr 12 12:17:01 antix17-4 CRON[4995]: pam_unix(cron:session): session closed for user root
    Apr 12 12:28:28 antix17-4 sudo:     male : TTY=unknown ; PWD=/home/male ; USER=root ; COMMAND=/bin/chvt 1
    Apr 12 12:28:28 antix17-4 sudo: pam_unix(sudo:session): session opened for user root by (uid=0)
    Apr 12 12:28:28 antix17-4 sudo: pam_unix(sudo:session): session closed for user root
    Apr 12 12:28:28 antix17-4 sudo:     male : TTY=unknown ; PWD=/home/male ; USER=root ; COMMAND=/sbin/reboot
    Apr 12 12:28:28 antix17-4 sudo: pam_unix(sudo:session): session opened for user root by (uid=0)
    Apr 12 12:28:28 antix17-4 sudo: pam_unix(sudo:session): session closed for user root
    Apr 12 17:16:57 antix17-4 slim: pam_unix(slim:session): session opened for user male by (uid=0)
    Apr 12 17:17:01 antix17-4 CRON[2454]: pam_unix(cron:session): session opened for user root by (uid=0)
    Apr 12 17:17:01 antix17-4 CRON[2454]: pam_unix(cron:session): session closed for user root
    Apr 12 17:49:34 antix17-4 sudo:     male : TTY=unknown ; PWD=/home/male ; USER=root ; COMMAND=/bin/chvt 1
    Apr 12 17:49:34 antix17-4 sudo: pam_unix(sudo:session): session opened for user root by (uid=0)
    Apr 12 17:49:34 antix17-4 sudo: pam_unix(sudo:session): session closed for user root
    Apr 12 17:49:34 antix17-4 sudo:     male : TTY=unknown ; PWD=/home/male ; USER=root ; COMMAND=/sbin/reboot
    Apr 12 17:49:34 antix17-4 sudo: pam_unix(sudo:session): session opened for user root by (uid=0)
    Apr 12 17:49:34 antix17-4 sudo: pam_unix(sudo:session): session closed for user root
    Apr 13 19:53:56 antix17-4 slim: pam_unix(slim:session): session opened for user male by (uid=0)
    Apr 13 19:53:57 antix17-4 slim: pam_unix(slim:session): session closed for user male
    Apr 13 19:54:03 antix17-4 slim: pam_unix(slim:session): session opened for user male by (uid=0)
    Apr 13 19:54:54 antix17-4 su: (to root) male on pts/0
    Apr 13 19:54:54 antix17-4 su: pam_unix(su:session): session opened for user root by (uid=1000)
    Apr 13 19:55:59 antix17-4 su: pam_unix(su:session): session closed for user root
    Apr 13 20:13:34 antix17-4 sudo:     male : TTY=unknown ; PWD=/home/male ; USER=root ; COMMAND=/bin/chvt 1
    Apr 13 20:13:34 antix17-4 sudo: pam_unix(sudo:session): session opened for user root by (uid=0)
    Apr 13 20:13:34 antix17-4 sudo: pam_unix(sudo:session): session closed for user root
    Apr 13 20:13:34 antix17-4 sudo:     male : TTY=unknown ; PWD=/home/male ; USER=root ; COMMAND=/sbin/reboot
    Apr 13 20:13:34 antix17-4 sudo: pam_unix(sudo:session): session opened for user root by (uid=0)
    Apr 13 20:13:34 antix17-4 sudo: pam_unix(sudo:session): session closed for user root
    
    #20516
    Member
    Avatar
    skidoo

    “why is sudo listed in the auth.log protocol again and again, when I explicitly don’t use sudo on the system”

    Apr 10 11:22:57 antix17-4 sudo: male : TTY=unknown ; PWD=/home/male ; USER=root ; COMMAND=/bin/chvt 1
    Apr 10 11:22:57 antix17-4 sudo: pam_unix(sudo:session): session opened for user root by (uid=0)
    Apr 10 11:22:57 antix17-4 sudo: pam_unix(sudo:session): session closed for user root
    Apr 10 11:22:57 antix17-4 sudo: male : TTY=unknown ; PWD=/home/male ; USER=root ; COMMAND=/sbin/reboot

    This indicates the PAM pluggable authentication module invoked sudo backend
    (is not “a user manually typed sudo at the commandline”)

    man pam.conf
    If desired, you can add rules into /etc/pam.conf to suppress these “success” log entries.

    #20518
    Member
    ile
    ile

    hello jerry99 and everyone
    the login slim twice machine here Helen Keller, the log of ConsoleKit / history is a place that shows something changed here on 21 March. is that the near date for you, male?

    #20519
    Member
    male
    male

    @ile
    so I have explicitly (we are here at sid)
    apt-listchanges installed
    and, that shows me no changes in the package consolekit

    male@antix17-4:~
    $ apt changelog consolekit
    E: Fehlschlag beim Holen von changelog:/consolekit.changelog Änderungsprotokoll (Changelog) nicht verfügbar für consolekit=0.4.6-6
    

    @skidoo
    isn’t here again and again an exchange of the uid ?

    Apr 13 19:53:56 antix17-4 slim: pam_unix(slim:session): session opened for user male by (uid=0)
    Apr 13 19:53:57 antix17-4 slim: pam_unix(slim:session): session closed for user male
    Apr 13 19:54:03 antix17-4 slim: pam_unix(slim:session): session opened for user male by (uid=0)
    Apr 13 19:54:54 antix17-4 su: (to root) male on pts/0
    Apr 13 19:54:54 antix17-4 su: pam_unix(su:session): session opened for user root by (uid=1000)
    Apr 13 19:55:59 antix17-4 su: pam_unix(su:session): session closed for user root
    
    male@antix17-4:~
    $ id
    uid=1000(male) gid=1000(male) Gruppen=1000(male),7(lp),20(dialout),24(cdrom),25(floppy),27(sudo),29(audio),30(dip),44(video),46(plugdev),100(users),108(netdev)
    
    male@antix17-4:~
    $ su
    Passwort: 
    root@antix17-4:/home/male# id
    uid=0(root) gid=0(root) Gruppen=0(root)
    

    I can live with it, because it is a test installation anyway…. 😉

    #20520
    Member
    Avatar
    skidoo

    “why is sudo listed in the auth.log protocol again and again, when I explicitly don’t use sudo on the system”

    COMMAND=

    notice the logged COMMAND= detail
    we can see that pam_auth calls sudo when you chvt and login, when suspend/resume occurs, when reboot command is processed

Viewing 8 posts - 1 through 8 (of 8 total)

You must be logged in to reply to this topic.