How to disable tty login prompt before login screen?

Questions about Grub, UEFI,the liveCD and the installer
Forum rules
Before you post please read how to get help
Post Reply
meric07
Level 1
Level 1
Posts: 12
Joined: Fri Mar 29, 2019 6:22 pm

How to disable tty login prompt before login screen?

Post by meric07 »

Hi, I'm running latest xfce build (19.1) on my laptop now. There's no problems in my installation but on every boot i see a "tty login" prompt on black screen (like DOS). The system waits for me to input a user name and password but proceeds to login after some time (like 15-20 seconds, maybe more) regardless whether i enter credentials or not.

Is there a way to disable this?
User avatar
karlchen
Level 21
Level 21
Posts: 14964
Joined: Sat Dec 31, 2011 7:21 am
Location: Germany

Re: How to disable tty login prompt before login screen?

Post by karlchen »

Hello, meric07.

Actually it is part of the normal startup procedure that Linux Mint will display the text only console login prompt on tty1 before proceeding to startup the graphical desktop environment.

Only in most cases, even on slower older computers, the text only console login prompt on tty1 will be visible for such a short period of time (or not at all on faster machines) that there is no chance of entering login credentials there, before the graphical login screen will appear.

So the question raises what precisely causes a delay of around 20 seconds on your system specifically between login prompt on tty1 and startup of the graphical environment?

Please, post the terminal output of the command:

Code: Select all

systemd-analyze
and

Code: Select all

systend-analyze blame
(yes, output of both commands please)

In case you know how to read the output of the command

Code: Select all

journalctl -b
then you can use this output and check for errors and for delays between two operations, which can be told from their timestamps.

Best regards,
Karl
Image
Linux Mint 19.3 64-bit Cinnamon, Total Commander 10.00 64-bit
The Prophet's Song
User avatar
karlchen
Level 21
Level 21
Posts: 14964
Joined: Sat Dec 31, 2011 7:21 am
Location: Germany

Re: How to disable tty login prompt before login screen?

Post by karlchen »

Hi, meric07.

Realized I had not clearly answered the question, asked in your title:
You should not try to figure out how to prevent the Linux Mint startup from making available the text only console monitors tty1 to tty6 even before starting up the graphical environment.
Specifically in cases where the graphical environment does not come up, it is one of the big advantages of Linux over Windows that you still have the pseudo console monitors tty1 to tty6 for troubleshooting.

The real problem is that the tty1 login prompt remains visible for a long time, before it becomes hidden by the starting graphical environment. See post above.

Karl
Image
Linux Mint 19.3 64-bit Cinnamon, Total Commander 10.00 64-bit
The Prophet's Song
meric07
Level 1
Level 1
Posts: 12
Joined: Fri Mar 29, 2019 6:22 pm

Re: How to disable tty login prompt before login screen?

Post by meric07 »

Hi karlchen, thanks for the response. Firstly i'd like to give my pc's specs:
Core i7 720 qm
Intel PM55 motherboard
4GB DDR3
AMD Mobility Radeon HD 5650 1GB GDDR3
karlchen wrote:
Tue Apr 30, 2019 10:02 am
Please, post the terminal output of the command:

Code: Select all

systemd-analyze
and

Code: Select all

systend-analyze blame
(yes, output of both commands please)
Output of

Code: Select all

systemd-analyze
Startup finished in 16.772s (kernel) + 36.783s (userspace) = 53.556s
graphical.target reached after 36.752s in userspace
Output of

Code: Select all

systemd-analyze blame
(entries above 1 second)
14.258s ufw.service
         11.489s dev-sda1.device
         11.481s systemd-journal-flush.service
         10.177s apt-daily.service
          8.233s lvm2-monitor.service
          7.223s systemd-udevd.service
          6.886s systemd-sysctl.service
          6.450s colord.service
          6.230s lightdm.service
          6.226s plymouth-quit-wait.service
          5.449s setvtrgb.service
          4.530s udisks2.service
          4.262s NetworkManager.service
          3.402s networkd-dispatcher.service
          3.074s thermald.service
          2.685s ubuntu-system-adjustments.service
          2.652s ModemManager.service
          2.553s accounts-daemon.service
          2.253s keyboard-setup.service
          1.819s media-mero-DATA.mount
          1.810s swapfile.swap
          1.804s gpu-manager.service
          1.785s systemd-modules-load.service
lines 1-23...skipping...
         14.258s ufw.service
         11.489s dev-sda1.device
         11.481s systemd-journal-flush.service
         10.177s apt-daily.service
          8.233s lvm2-monitor.service
          7.223s systemd-udevd.service
          6.886s systemd-sysctl.service
          6.450s colord.service
          6.230s lightdm.service
          6.226s plymouth-quit-wait.service
          5.449s setvtrgb.service
          4.530s udisks2.service
          4.262s NetworkManager.service
          3.402s networkd-dispatcher.service
          3.074s thermald.service
          2.685s ubuntu-system-adjustments.service
          2.652s ModemManager.service
          2.553s accounts-daemon.service
          2.253s keyboard-setup.service
          1.819s media-mero-DATA.mount
          1.810s swapfile.swap
          1.804s gpu-manager.service
          1.785s systemd-modules-load.service
          1.769s lm-sensors.service
          1.686s systemd-remount-fs.service
          1.650s dev-hugepages.mount
          1.650s sys-kernel-debug.mount
          1.590s dev-mqueue.mount
          1.507s avahi-daemon.service
          1.456s grub-common.service
          1.238s systemd-tmpfiles-setup-dev.service
karlchen wrote:
Tue Apr 30, 2019 10:02 am
In case you know how to read the output of the command

Code: Select all

journalctl -b
then you can use this output and check for errors and for delays between two operations, which can be told from their timestamps.
There are some messages about TPM and Bluetooth but i got those both disabled so no big deal for me. But there are some error messages in red font (in separate lines) like:

Code: Select all

May 01 09:52:53 mero-NBLB2 ntpd[997]: error resolving pool 0.ubuntu.pool.ntp.org: Name or service not known (-2)
May 01 09:52:54 mero-NBLB2 wpa_supplicant[866]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (none) none
May 01 09:52:54 mero-NBLB2 wpa_supplicant[866]: dbus: Failed to construct signal
May 01 09:52:54 mero-NBLB2 ntpd[997]: error resolving pool 1.ubuntu.pool.ntp.org: Name or service not known (-2)
May 01 09:52:55 mero-NBLB2 ntpd[997]: error resolving pool 2.ubuntu.pool.ntp.org: Name or service not known (-2)
May 01 09:52:56 mero-NBLB2 ntpd[997]: error resolving pool 3.ubuntu.pool.ntp.org: Name or service not known (-2)
May 01 09:52:57 mero-NBLB2 ntpd[997]: error resolving pool ntp.ubuntu.com: Name or service not known (-2)
May 01 09:53:53 mero-NBLB2 lightdm[1293]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
May 01 09:53:53 mero-NBLB2 lightdm[1293]: PAM adding faulty module: pam_kwallet.so
May 01 09:53:53 mero-NBLB2 lightdm[1293]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
May 01 09:53:53 mero-NBLB2 lightdm[1293]: PAM adding faulty module: pam_kwallet5.so
May 01 09:53:58 mero-NBLB2 lightdm[1383]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
May 01 09:53:58 mero-NBLB2 lightdm[1383]: PAM adding faulty module: pam_kwallet.so
May 01 09:53:58 mero-NBLB2 lightdm[1383]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
May 01 09:53:58 mero-NBLB2 lightdm[1383]: PAM adding faulty module: pam_kwallet5.so


There seems to be not an important message about tty or such. If you need any more specific info please don't hesitate to ask.
Last edited by karlchen on Wed May 01, 2019 4:09 am, edited 2 times in total.
Reason: added more[code] tags where appropriate
User avatar
karlchen
Level 21
Level 21
Posts: 14964
Joined: Sat Dec 31, 2011 7:21 am
Location: Germany

Re: How to disable tty login prompt before login screen?

Post by karlchen »

Hello, meric07.

The PC's specs, which you provide, are a bit meaningless, to tell the truth. A complete inxi -Fxz report, however, would be really helpful. :-)

Here is how to generate the report and post it:
  • Open a terminal window. Make it fullscreen to avoid unneeded linebreaks or chopped lines.
  • Execute the command

    Code: Select all

    inxi -Fxz
    exactly as it has been typed here.
  • Mark the complete text output which inxi -Fxz will display with your mouse.
  • Press the keyboard shortcut <Shift><Ctrl>C to copy the marked text into the clipboard.
  • Paste it into your next reply.
Regards,
Karl
Image
Linux Mint 19.3 64-bit Cinnamon, Total Commander 10.00 64-bit
The Prophet's Song
User avatar
karlchen
Level 21
Level 21
Posts: 14964
Joined: Sat Dec 31, 2011 7:21 am
Location: Germany

Re: How to disable tty login prompt before login screen?

Post by karlchen »

Hello, meric07.

About the startup time which systemd-analyze reports:

Code: Select all

systemd-analyze
Startup finished in 16.772s (kernel) + 36.783s (userspace) = 53.556s
graphical.target reached after 36.752s in userspace
Well, depending on the hardware specifications, the total startup time might be ok or slow. :wink:

Yet, as you already reported about the delay during startup, which makes the tty1 login prompt visible for roughly 20 seconds, before the graphical environment starts up, we know we are looking for some issue.

The part of the "journalctl -b" output, which you posted, might give a first hint where to look for a delay:

Code: Select all

May 01 09:52:53 mero-NBLB2 ntpd[997]: error resolving pool 0.ubuntu.pool.ntp.org: Name or service not known (-2)
May 01 09:52:54 mero-NBLB2 wpa_supplicant[866]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (none) none
May 01 09:52:54 mero-NBLB2 wpa_supplicant[866]: dbus: Failed to construct signal
May 01 09:52:54 mero-NBLB2 ntpd[997]: error resolving pool 1.ubuntu.pool.ntp.org: Name or service not known (-2)
May 01 09:52:55 mero-NBLB2 ntpd[997]: error resolving pool 2.ubuntu.pool.ntp.org: Name or service not known (-2)
May 01 09:52:56 mero-NBLB2 ntpd[997]: error resolving pool 3.ubuntu.pool.ntp.org: Name or service not known (-2)
May 01 09:52:57 mero-NBLB2 ntpd[997]: error resolving pool ntp.ubuntu.com: Name or service not known (-2)
This looks as if there might be some DNS issue affecting your network connectivity.
Yet, it might also just be a normal network startup behaviour, as it seems to take 3 seconds only; unless journalctl keeps on reporting so more often than you posted.

Code: Select all

May 01 09:53:53 mero-NBLB2 lightdm[1293]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
May 01 09:53:53 mero-NBLB2 lightdm[1293]: PAM adding faulty module: pam_kwallet.so
May 01 09:53:53 mero-NBLB2 lightdm[1293]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
May 01 09:53:53 mero-NBLB2 lightdm[1293]: PAM adding faulty module: pam_kwallet5.so
May 01 09:53:58 mero-NBLB2 lightdm[1383]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
May 01 09:53:58 mero-NBLB2 lightdm[1383]: PAM adding faulty module: pam_kwallet.so
May 01 09:53:58 mero-NBLB2 lightdm[1383]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
May 01 09:53:58 mero-NBLB2 lightdm[1383]: PAM adding faulty module: pam_kwallet5.so
This part looks like something serious, but actually is not. It happens on any system (mine too), where PAM looks for kwallet.so, although kwallet.so is neither in use, nor even present on the system. - This may be safely ignored.


About "systemd-analyze blame":

Code: Select all

systemd-analyze blame
(entries above 1 second)
14.258s ufw.service
         11.489s dev-sda1.device
         11.481s systemd-journal-flush.service
         10.177s apt-daily.service

Your software firewall seems a bit slow to come up: 14 seconds on your system, 3.5 seconds here.

11.5 seconds for disk device sda1 is not really fast. But in case disk device SDA is an older Sata disk, then it is a normal timespan nonetheless and does not necessarily indicate any problem. - It is not much faster here, either.

I am pretty sure that some people will come up advising you to disable ufw and apt-daily services to reduce startup times: Nonsense.
"systemd-analyze blame" lists the startup times sequentially. But systemd launches services, which do not depend on each other, in parallel. So randomly disabling services will not necessarily reduce the total startup times.


About the "journalctl -b" extract:
You merely posted some more or less random part of the whole "journalctl -b" output. In order to really find reasons for a delay on your system during startup, however, it would be required to have the complete "journalctl -b" output.
There are 2 problems when trying to post the complete output of journalctl:
+ the complete output will have more lines than the forum accepts
+ journalctl displays the output pagewise, for posting the pager has to be disabled

How to provide journalctl output for inspection in the forum:

I suggest you proceed like this in order to post the current systemlog entries for inspection, please:
  • Open a terminal window.
  • Execute the following commandline, please:

    Code: Select all

    journalctl --no-pager -b 0 > journalctl_meric07.txt
    This command will write the whole current system log to the file journalctl_meric07.txt. The file will be located in your $HOME directory (very likely /home/meric07).
  • Now gzip the file journalctl_meric07.txt by executing the commandline:

    Code: Select all

    gzip journalctl_meric07.txt
    The resulting .gz file will be named journalctl_meric07.txt.gz.
  • Attach this file to your next reply, please.
If we are lucky the systemlog will put us on the right track. Hopefully.

Regards,
Karl
Image
Linux Mint 19.3 64-bit Cinnamon, Total Commander 10.00 64-bit
The Prophet's Song
meric07
Level 1
Level 1
Posts: 12
Joined: Fri Mar 29, 2019 6:22 pm

Re: How to disable tty login prompt before login screen?

Post by meric07 »

Okay :) Here's the output:

Code: Select all

System:
  Host: mero-NBLB2 Kernel: 4.15.0-48-generic x86_64 bits: 64 compiler: gcc 
  v: 7.3.0 Desktop: Xfce 4.12.3 Distro: Linux Mint 19.1 Tessa 
  base: Ubuntu 18.04 bionic 
Machine:
  Type: Laptop System: Compal product: NBLB2 v: F.00 serial: <filter> 
  Mobo: Compal model: NBLB2 serial: <filter> BIOS: INSYDE v: F.05 
  date: 02/09/2010 
CPU:
  Topology: Quad Core model: Intel Core i7 Q 720 bits: 64 type: MT MCP 
  arch: Nehalem rev: 5 L2 cache: 6144 KiB 
  flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 25600 
  Speed: 933 MHz min/max: 933/1600 MHz Core speeds (MHz): 1: 936 2: 947 
  3: 939 4: 947 5: 994 6: 957 7: 935 8: 940 
Graphics:
  Device-1: AMD Madison [Mobility Radeon HD 5650/5750 / 6530M/6550M] 
  vendor: COMPAL driver: radeon v: kernel bus ID: 01:00.0 
  Display: x11 server: X.Org 1.19.6 driver: ati,radeon 
  unloaded: fbdev,modesetting,vesa resolution: 1366x768~60Hz 
  OpenGL: renderer: AMD REDWOOD (DRM 2.50.0 / 4.15.0-48-generic LLVM 7.0.0) 
  v: 3.3 Mesa 18.2.8 direct render: Yes 
Audio:
  Device-1: Intel 5 Series/3400 Series High Definition Audio vendor: COMPAL 
  driver: snd_hda_intel v: kernel bus ID: 00:1b.0 
  Device-2: AMD Redwood HDMI Audio [Radeon HD 5000 Series] 
  driver: snd_hda_intel v: kernel bus ID: 01:00.1 
  Sound Server: ALSA v: k4.15.0-48-generic 
Network:
  Device-1: Qualcomm Atheros AR928X Wireless Network Adapter vendor: Accton 
  driver: ath9k v: kernel port: 6000 bus ID: 03:00.0 
  IF: wlp3s0 state: up mac: <filter> 
  Device-2: Qualcomm Atheros AR8131 Gigabit Ethernet vendor: COMPAL 
  driver: atl1c v: 1.0.1.1-NAPI port: 3000 bus ID: 04:00.0 
  IF: enp4s0 state: down mac: <filter> 
Drives:
  Local Storage: total: 372.61 GiB used: 74.16 GiB (19.9%) 
  ID-1: /dev/sda vendor: Samsung model: HM400JI size: 372.61 GiB 
Partition:
  ID-1: / size: 98.04 GiB used: 24.92 GiB (25.4%) fs: ext4 dev: /dev/sda1 
Sensors:
  System Temperatures: cpu: 47.0 C mobo: N/A gpu: radeon temp: 49 C 
  Fan Speeds (RPM): N/A 
Info:
  Processes: 241 Uptime: 2h 35m Memory: 3.84 GiB used: 3.18 GiB (82.6%) 
  Init: systemd runlevel: 5 Compilers: gcc: 7.4.0 Shell: bash v: 4.4.19 
  inxi: 3.0.27 

By the way, i just realised my cpu runs at like 900 mhz which is not right. It should be running at 1.6ghz at minimum (with boost to 2.8 ghz). Why does it run so slow now?
User avatar
karlchen
Level 21
Level 21
Posts: 14964
Joined: Sat Dec 31, 2011 7:21 am
Location: Germany

Re: How to disable tty login prompt before login screen?

Post by karlchen »

Hi, meric07.

Thanks for posting the inxi -Fxz report. :-)

Looks a bit that your machine is not too much younger than my Quad Core. (2010 vs 2008) But yours has got an i7 CPU already. I am stuck with the first generation Quad Core CPU.

About the low CPU speed:
The CPU runs as fast as the current work load requires. Mine does the same.
inxi tells on your machine the minimum speed were 933 MHz and the maximum speed were 1600 MHz. So, if it runs at 947 MHz, this may mean that while inxi created its report your machine was more or less idling along.

Please, note my second post today above as well, about the journalctl output, which you had posted, and about how to provide the complete "journalctl -b" output, too.

Regards,
Karl
Image
Linux Mint 19.3 64-bit Cinnamon, Total Commander 10.00 64-bit
The Prophet's Song
User avatar
Larry78723
Level 13
Level 13
Posts: 4935
Joined: Wed Jan 09, 2019 7:01 pm
Location: Jasper County, SC, USA

Re: How to disable tty login prompt before login screen?

Post by Larry78723 »

I think it would be helpful to also see the output of the following command:

Code: Select all

journalctl -b -p err
This would let us see all errors encountered during the boot.
Image
meric07
Level 1
Level 1
Posts: 12
Joined: Fri Mar 29, 2019 6:22 pm

Re: How to disable tty login prompt before login screen?

Post by meric07 »

Here's the output of journalctl command in a text file like you asked for. By the way thank you so much for your time and effort assisting me.
Attachments
journalctl_meric07.txt.gz
(31.38 KiB) Downloaded 70 times
meric07
Level 1
Level 1
Posts: 12
Joined: Fri Mar 29, 2019 6:22 pm

Re: How to disable tty login prompt before login screen?

Post by meric07 »

Larry78723 wrote:
Wed May 01, 2019 6:29 am
I think it would be helpful to also see the output of the following command:

Code: Select all

journalctl -b -p err
This would let us see all errors encountered during the boot.
Thank you sir, here's the command output you asked for:

Code: Select all

mero@mero-NBLB2:~$ journalctl -b -p err
-- Logs begin at Thu 2019-04-18 21:01:47 +03, end at Wed 2019-05-01 13:37:39 +03
May 01 09:52:33 mero-NBLB2 kernel: tpm tpm0: A TPM error (7) occurred attempting
May 01 09:52:33 mero-NBLB2 kernel: tpm tpm0: A TPM error (7) occurred attempting
May 01 09:52:48 mero-NBLB2 bluetoothd[859]: Failed to set mode: Blocked through 
May 01 09:52:53 mero-NBLB2 ntpd[997]: error resolving pool 0.ubuntu.pool.ntp.org
May 01 09:52:54 mero-NBLB2 wpa_supplicant[866]: dbus: wpa_dbus_get_object_proper
May 01 09:52:54 mero-NBLB2 wpa_supplicant[866]: dbus: Failed to construct signal
May 01 09:52:54 mero-NBLB2 ntpd[997]: error resolving pool 1.ubuntu.pool.ntp.org
May 01 09:52:55 mero-NBLB2 ntpd[997]: error resolving pool 2.ubuntu.pool.ntp.org
May 01 09:52:56 mero-NBLB2 ntpd[997]: error resolving pool 3.ubuntu.pool.ntp.org
May 01 09:52:57 mero-NBLB2 ntpd[997]: error resolving pool ntp.ubuntu.com: Name 
May 01 09:53:02 mero-NBLB2 ntpdate[1133]: the NTP socket is in use, exiting
May 01 09:53:53 mero-NBLB2 lightdm[1293]: PAM unable to dlopen(pam_kwallet.so): 
May 01 09:53:53 mero-NBLB2 lightdm[1293]: PAM adding faulty module: pam_kwallet.
May 01 09:53:53 mero-NBLB2 lightdm[1293]: PAM unable to dlopen(pam_kwallet5.so):
May 01 09:53:53 mero-NBLB2 lightdm[1293]: PAM adding faulty module: pam_kwallet5
May 01 09:53:58 mero-NBLB2 lightdm[1383]: PAM unable to dlopen(pam_kwallet.so): 
May 01 09:53:58 mero-NBLB2 lightdm[1383]: PAM adding faulty module: pam_kwallet.
May 01 09:53:58 mero-NBLB2 lightdm[1383]: PAM unable to dlopen(pam_kwallet5.so):
May 01 09:53:58 mero-NBLB2 lightdm[1383]: PAM adding faulty module: pam_kwallet5
May 01 09:56:58 mero-NBLB2 pulseaudio[1879]: [pulseaudio] backend-ofono.c: Faile
May 01 09:56:58 mero-NBLB2 pulseaudio[1941]: [pulseaudio] pid.c: Daemon already 
May 01 09:57:02 mero-NBLB2 bluetoothd[859]: Failed to set mode: Blocked through 
lines 1-23...skipping...
-- Logs begin at Thu 2019-04-18 21:01:47 +03, end at Wed 2019-05-01 13:37:39 +03. --
May 01 09:52:33 mero-NBLB2 kernel: tpm tpm0: A TPM error (7) occurred attempting to read a pcr value
May 01 09:52:33 mero-NBLB2 kernel: tpm tpm0: A TPM error (7) occurred attempting to read a pcr value
May 01 09:52:48 mero-NBLB2 bluetoothd[859]: Failed to set mode: Blocked through rfkill (0x12)
May 01 09:52:53 mero-NBLB2 ntpd[997]: error resolving pool 0.ubuntu.pool.ntp.org: Name or service not known (-2)
May 01 09:52:54 mero-NBLB2 wpa_supplicant[866]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (none) none
May 01 09:52:54 mero-NBLB2 wpa_supplicant[866]: dbus: Failed to construct signal
May 01 09:52:54 mero-NBLB2 ntpd[997]: error resolving pool 1.ubuntu.pool.ntp.org: Name or service not known (-2)
May 01 09:52:55 mero-NBLB2 ntpd[997]: error resolving pool 2.ubuntu.pool.ntp.org: Name or service not known (-2)
May 01 09:52:56 mero-NBLB2 ntpd[997]: error resolving pool 3.ubuntu.pool.ntp.org: Name or service not known (-2)
May 01 09:52:57 mero-NBLB2 ntpd[997]: error resolving pool ntp.ubuntu.com: Name or service not known (-2)
May 01 09:53:02 mero-NBLB2 ntpdate[1133]: the NTP socket is in use, exiting
May 01 09:53:53 mero-NBLB2 lightdm[1293]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
May 01 09:53:53 mero-NBLB2 lightdm[1293]: PAM adding faulty module: pam_kwallet.so
May 01 09:53:53 mero-NBLB2 lightdm[1293]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
May 01 09:53:53 mero-NBLB2 lightdm[1293]: PAM adding faulty module: pam_kwallet5.so
May 01 09:53:58 mero-NBLB2 lightdm[1383]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
May 01 09:53:58 mero-NBLB2 lightdm[1383]: PAM adding faulty module: pam_kwallet.so
May 01 09:53:58 mero-NBLB2 lightdm[1383]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
May 01 09:53:58 mero-NBLB2 lightdm[1383]: PAM adding faulty module: pam_kwallet5.so
May 01 09:56:58 mero-NBLB2 pulseaudio[1879]: [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUn
May 01 09:56:58 mero-NBLB2 pulseaudio[1941]: [pulseaudio] pid.c: Daemon already running.
May 01 09:57:02 mero-NBLB2 bluetoothd[859]: Failed to set mode: Blocked through rfkill (0x12)
May 01 12:28:05 mero-NBLB2 sudo[11328]:     mero : a password is required ; TTY=pts/0 ; PWD=/home/mero ; USER=root ; COMMAND=/usr/sbin/hddtemp -nq -u C /dev/sda
Note that i disabled tpm (in bios) and bluetooth (within system) since i haven't yet needed these. I sometimes use printer
User avatar
karlchen
Level 21
Level 21
Posts: 14964
Joined: Sat Dec 31, 2011 7:21 am
Location: Germany

Re: How to disable tty login prompt before login screen?

Post by karlchen »

Hi, meric07.
meric07 wrote:
Wed May 01, 2019 6:29 am
Here's the output of journalctl command in a text file like you asked for.
Now I am a bit lost. :(
Went through the whole "journalctl -b" output, from the first line to where lightdm has come up and the graphical slick greeter screen is displayed (graphical login screen).
For whichever reason I failed to notice any delay of roughly 20 seconds or several delays, summing up to 20 seconds, which would explain why the tty1 login prompt should be visible for 20 seconds.
If it is inside the journalctl output, then I have missed it.
Maybe somebody else will spot what I must have missed.

Regards,
Karl
Image
Linux Mint 19.3 64-bit Cinnamon, Total Commander 10.00 64-bit
The Prophet's Song
meric07
Level 1
Level 1
Posts: 12
Joined: Fri Mar 29, 2019 6:22 pm

Re: How to disable tty login prompt before login screen?

Post by meric07 »

karlchen wrote:
Wed May 01, 2019 7:39 am
Hi, meric07.
meric07 wrote:
Wed May 01, 2019 6:29 am
Here's the output of journalctl command in a text file like you asked for.
Now I am a bit lost. :(
Went through the whole "journalctl -b" output, from the first line to where lightdm has come up and the graphical slick greeter screen is displayed (graphical login screen).
For whichever reason I failed to notice any delay of roughly 20 seconds or several delays, summing up to 20 seconds, which would explain why the tty1 login prompt should be visible for 20 seconds.
If it is inside the journalctl output, then I have missed it.
Maybe somebody else will spot what I must have missed.

Regards,
Karl
Hello again karlchen and thanks again for your time. It's strange indeed cause i restarted my pc just now and i used chronometer (on my phone) to measure the tty prompt duration. It is 21 seconds. And during that time hard disk light doesn't blink at all, indicating a system wait? Here's the new journalctl output in text file if it helps.
Attachments
journalctl_meric07.txt.gz
(29.23 KiB) Downloaded 79 times
User avatar
Larry78723
Level 13
Level 13
Posts: 4935
Joined: Wed Jan 09, 2019 7:01 pm
Location: Jasper County, SC, USA

Re: How to disable tty login prompt before login screen?

Post by Larry78723 »

Karl, check this out from his latest log:
May 01 14:53:34 mero-NBLB2 systemd-journald[413]: Time spent on flushing to /var is 11.087630s for 847 entries.
May 01 14:53:34 mero-NBLB2 systemd-journald[413]: System journal (/var/log/journal/1975cc0879614ce88a5940de34910d44) is 80.0M, max 4.0G, 3.9G free.
May 01 14:53:52 mero-NBLB2 kernel: Adding 2097148k swap on /swapfile. Priority:-2 extents:6 across:2260988k FS
May 01 14:53:52 mero-NBLB2 kernel: ip6_tables: (C) 2000-2006 Netfilter Core Team
That accounts for 18 secs
Image
meric07
Level 1
Level 1
Posts: 12
Joined: Fri Mar 29, 2019 6:22 pm

Re: How to disable tty login prompt before login screen?

Post by meric07 »

Larry78723 wrote:
Wed May 01, 2019 8:23 am
Karl, check this out from his latest log:
May 01 14:53:34 mero-NBLB2 systemd-journald[413]: Time spent on flushing to /var is 11.087630s for 847 entries.
May 01 14:53:34 mero-NBLB2 systemd-journald[413]: System journal (/var/log/journal/1975cc0879614ce88a5940de34910d44) is 80.0M, max 4.0G, 3.9G free.
May 01 14:53:52 mero-NBLB2 kernel: Adding 2097148k swap on /swapfile. Priority:-2 extents:6 across:2260988k FS
May 01 14:53:52 mero-NBLB2 kernel: ip6_tables: (C) 2000-2006 Netfilter Core Team
That accounts for 18 secs
What's the issue here? Can you identify it?
Post Reply