Xorg? 'startx' session problem

**yarooh** · July 2nd, 2018

Hello to Everyone,
I am on ubuntu 18.04 based on Openbox only. I have no display/login manager. I log into system by typing 'startx'. I just run sudo apt upgrade and something went wrong. Now to log in after booting up the system when I run 'startx' nothing happens - I need to press Ctrl+ C and run 'startx' several times to succeed.How can I fix this?
Thank you for advance.

**ubfan1** · July 2nd, 2018

What errors show up in the /var/log/Xorg.0.log (or older log file like Xorg.1.log) ? They should be tagged with a "EE".

**yarooh** · July 3rd, 2018

Thanks for reply ubfan1.
There are no any errors. Actually my problem looks the same like in post
https://ubuntuforums.org/showthread.php?t=2395452
what means that if I run "startx" and wait, then after 2-3 minutes the system starts up.

Presently I upgraded the kernel up to 4.17.3-041703-generic and the still after hit 'startx' I need to wait 2-3 minutes before system starts.

Does anyone have any idea how to fix this or I must do a fresh install again and do not do the upgrades on kernel?

**Bashing-om** · July 3rd, 2018

yarooh; Hummmm ...

Could be any number of factors .
Any hints:

Code:

journalctl -b -0
systemd-analyze blame
systemd-analyze critical-chain

what DE are you booting up ?

Code:

systemctl status gdm
echo $XDG_SESSION_TYPE

inquiring minds want to know

**yarooh** · July 3rd, 2018

Hello Bashing-om,
I have only Openbox WM and based on it I am building my DE. presently I have no any display/login manager.

systemd-analyze blame

Code:

          5.096s apt-daily.service
           921ms systemd-resolved.service
           872ms systemd-timesyncd.service
           599ms udisks2.service
           482ms systemd-logind.service
           379ms systemd-journal-flush.service
           376ms motd-news.service
           330ms nvidia-persistenced.service
           265ms dev-sda2.device
            96ms networkd-dispatcher.service
            90ms systemd-udev-trigger.service
            89ms upower.service
            77ms keyboard-setup.service
            55ms systemd-journald.service
            48ms ModemManager.service
            39ms apparmor.service
            37ms accounts-daemon.service
            34ms systemd-fsck@dev-disk-by\x2duuid-5611\x2dBD65.service
            34ms ufw.service
            34ms systemd-fsck@dev-disk-by\x2duuid-de2c2634\x2de397\x2d4c89\x2d94c7\x2dd5e8f3db8124.service
            32ms dev-mqueue.mount
            32ms dev-hugepages.mount
            29ms systemd-networkd.service
            29ms apport.service
            29ms user@1000.service
            28ms avahi-daemon.service
            27ms wpa_supplicant.service
            26ms grub-common.service
            25ms boot-efi.mount
            25ms systemd-tmpfiles-clean.service
            23ms systemd-remount-fs.service
            22ms rsyslog.service
            18ms systemd-modules-load.service
            17ms kmod-static-nodes.service
            17ms alsa-restore.service
            17ms systemd-tmpfiles-setup-dev.service
            16ms systemd-udevd.service
            16ms sys-kernel-debug.mount
            15ms plymouth-read-write.service
            14ms polkit.service
            12ms plymouth-quit.service
            12ms systemd-sysctl.service
            11ms dev-disk-by\x2duuid-ce34a78d\x2dcce3\x2d4568\x2d8b39\x2d29ea78b1190d.swap
             9ms home.mount
             8ms systemd-tmpfiles-setup.service
             5ms sys-kernel-config.mount
             5ms systemd-random-seed.service
             5ms sys-fs-fuse-connections.mount
             4ms ureadahead-stop.service
             4ms console-setup.service
             4ms systemd-user-sessions.service
             3ms systemd-update-utmp-runlevel.service
             3ms systemd-update-utmp.service
             2ms plymouth-quit-wait.service
             2ms setvtrgb.service

systemd-analyze critical-chain

Code:

The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.

graphical.target @2.137s

└─udisks2.service @1.537s +599ms
  └─basic.target @1.510s
    └─sockets.target @1.509s
      └─avahi-daemon.socket @1.507s
        └─sysinit.target @1.502s
          └─systemd-timesyncd.service @628ms +872ms
            └─systemd-tmpfiles-setup.service @616ms +8ms
              └─systemd-journal-flush.service @235ms +379ms
                └─systemd-journald.service @177ms +55ms
                  └─syslog.socket @160ms
                    └─system.slice @135ms
                      └─-.slice @117ms

And by the way - after first boot and login whenever I log out and log in system starts strightaway.

And journalctl -b -0 is here:

https://paste.ubuntu.com/p/GdzH3Kv96Z/plain/

I did netinstall without any DE.

In the outcome of: systemd-analyze blame there is the line shows:
26ms grub-common.service
however I removed any grub file including grub-common.
When I launched systemctl status grub-common.service- this shows that this service is loaded and active? How come?
Is it right?

**Bashing-om** · July 3rd, 2018

yarooh; Well ....

Are the system's packages now in a consistent state ?
Any errors:

Code:

sudo apt update
sudo apt full-upgrade
sudo apt -f install
sudo dpkg -C

I do see a few things will bear looking into.

1st: is fsck running ... does the file system check happen at each boot ??

2nd: How did you install the nvidia driver ? And why a proprietary driver with no GUI ?

3rd: raid array ? how is it set up as we have the system screaming:

lip 03 20:32:27 ubuntu udisksd[662]: failed to load module mdraid: libbd_mdraid.so.2: cannot open shared object file: No such file or directory

4th: samba: configured properly ? as we have a lot of:

lip 03 20:46:22 ubuntu gvfsd[915]: mkdir failed on directory /var/cache/samba: Brak dostÄ™pu

5th: A long delay in starting the terminal - almost 5 seconds - ??

lip 03 20:35:41 ubuntu systemd[818]: Started GNOME Terminal Server.
lip 03 20:40:32 ubuntu dbus-daemon[888]: [session uid=1000 pid=888] Activating via systemd: service name='org.gtk.vfs.Metadata' unit='gvfs-m

But overall the system starts up rather quick at about 45 seconds ,,, not too shabby

look'n to learn the why

**yarooh** · July 3rd, 2018

Bashing-om - thanks for reply.

Code:

sudo apt update
sudo apt full-upgrade
sudo apt -f install
sudo dpkg -C

gone smoothly.

After I press power button on my machine there is an about 4-5 sec listings
then I reach the point where system asks me for login and password.
After I loged in, in console mode I run 'startx'
Then I need to wait approx. 2 minutes an 9 sec until my desktop show up.
Before upgrading the kernel my start up process from pressing button to display the desktop took me an about 18 seconds including entering login an password and run 'startx'.
I installed nvidia in this way:

Code:

sudo add-apt-repository ppa:graphics-drivers/ppa
sudo apt update
sudo ubuntu-drivers autoinstall

I have a GUI - Openbox with compton etc.
I did not use raid. My partitions looks like that:
/dev/sda1 fat32 680MB esp, efi
/dev/sda2 ext4 41 GB root
/dev/sda3 swap 6G
/dev/sda4 ext4 home rest of the disk space

During the installation I am pretty sure I ticked out and did not install SAMBA. Definitely I did not do anything with samba.

This 45 seconds - it is not right time waiting to display a desktop with icons etc.

**Bashing-om** · July 3rd, 2018

yarooh; welll ...

I do have an 18.04 - minimal - install . Later this eve when I re-boot the system will boot back up in the minimal install and see what the differences are in my boot log.
And yes, the boot time does not reflect the time to start the GUI once the kernel has booted up.

Any hints in:

Code: