Long time for the desktop to show up after boot

[yaBoyNC]

So im using Linux Mint 21.1 Cinnamon, and its been going great ever since i've switched from windows, and my boot times have always been good taking about 30~ seconds, but recently, after the system boots and the linux mint icon shows up the computer sits with a black screen for 5 extra minutes until the desktop eventually shows up

i am still not used to this and have looked everywhere for this issue and couldnt find it, the extra time isnt even shown when i run systemd-analyze, when i run it it just shows the time the boot would normally take without taking into account the extra 5 minutes for the desktop to show up

this is what systemd-analyze shows:
Startup finished in 14.575s (firmware) + 5.829s (loader) + 5.378s (kernel) + 3.861s (userspace) = 29.644s
graphical.target reached after 3.858s in userspace

my system info:
CPU: AMD Ryzen 5 5600X 6-Core Processor × 6
MEMORY: 7.7 GB
STORAGE: 512GB SSD
GPU: GeForce GTX 750

am i doing something wrong? please tell me how to fix this

[zcot]

GPU: GeForce GTX 750

probably related to that.

post your system info please, as mentioned above.

[yaBoyNC]

GPU: GeForce GTX 750

probably related to that.

post your system info please, as mentioned above.

if by system info you mean the one copied from system info then here:

Code: Select all

System:
  Kernel: 5.15.0-56-generic x86_64 bits: 64 compiler: gcc v: 11.3.0 Desktop: Cinnamon 5.6.5
    tk: GTK 3.24.33 wm: muffin dm: LightDM Distro: Linux Mint 21.1 Vera base: Ubuntu 22.04 jammy
Machine:
  Type: Desktop Mobo: ASRock model: A520M Phantom Gaming 4 serial: <superuser required>
    UEFI: American Megatrends LLC. v: P1.60 date: 02/24/2022
CPU:
  Info: 6-core model: AMD Ryzen 5 5600X bits: 64 type: MT MCP arch: Zen 3 rev: 2 cache:
    L1: 384 KiB L2: 3 MiB L3: 32 MiB
  Speed (MHz): avg: 2465 high: 2817 min/max: 2200/4650 boost: enabled cores: 1: 2683 2: 2300
    3: 2784 4: 2238 5: 2246 6: 2234 7: 2562 8: 2241 9: 2811 10: 2303 11: 2363 12: 2817
    bogomips: 88628
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
  Device-1: NVIDIA GM107 [GeForce GTX 750] driver: nvidia v: 525.78.01 pcie: speed: 8 GT/s
    lanes: 16 ports: active: none off: HDMI-A-1 empty: DVI-D-1,DVI-I-1 bus-ID: 04:00.0
    chip-ID: 10de:1381
  Device-2: Z-Star Micro ZC0305 Webcam type: USB driver: gspca_zc3xx bus-ID: 1-2:2
    chip-ID: 0ac8:305b
  Display: x11 server: X.Org v: 1.21.1.3 driver: X: loaded: nvidia
    unloaded: fbdev,modesetting,nouveau,vesa gpu: nvidia display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1440x900 s-dpi: 121
  Monitor-1: HDMI-0 res: 1440x900 dpi: 23 diag: 1836mm (72.3")
  OpenGL: renderer: NVIDIA GeForce GTX 750/PCIe/SSE2 v: 4.6.0 NVIDIA 525.78.01
    direct render: Yes
Audio:
  Device-1: NVIDIA GM107 High Definition Audio [GeForce 940MX] driver: snd_hda_intel v: kernel
    pcie: speed: 8 GT/s lanes: 16 bus-ID: 04:00.1 chip-ID: 10de:0fbc
  Device-2: AMD Starship/Matisse HD Audio vendor: ASRock driver: snd_hda_intel v: kernel pcie:
    speed: 16 GT/s lanes: 16 bus-ID: 06:00.4 chip-ID: 1022:1487
  Sound Server-1: ALSA v: k5.15.0-56-generic running: yes
  Sound Server-2: PulseAudio v: 15.99.1 running: yes
  Sound Server-3: PipeWire v: 0.3.48 running: yes
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASRock driver: r8169
    v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: f000 bus-ID: 03:00.0 chip-ID: 10ec:8168
  IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:
  Local Storage: total: 476.94 GiB used: 368.85 GiB (77.3%)
  ID-1: /dev/sda model: SWR512G-202II size: 476.94 GiB speed: 6.0 Gb/s serial: <filter>
Partition:
  ID-1: / size: 467.89 GiB used: 368.85 GiB (78.8%) fs: ext4 dev: /dev/sda2
  ID-2: /boot/efi size: 511 MiB used: 6.1 MiB (1.2%) fs: vfat dev: /dev/sda1
Swap:
  ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2 file: /swapfile
Sensors:
  System Temperatures: cpu: N/A mobo: N/A gpu: nvidia temp: 38 C
  Fan Speeds (RPM): N/A gpu: nvidia fan: 33%
Repos:
  Packages: 3043 apt: 3023 flatpak: 20
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list
    1: deb [signed-by=/usr/share/keyrings/brave-browser-archive-keyring.gpg] https: //brave-browser-apt-release.s3.brave.com/ stable main
  Active apt repos in: /etc/apt/sources.list.d/ksp-ckan.list
    1: deb [arch=amd64 signed-by=/usr/share/keyrings/ksp-ckan-archive-keyring.gpg] https: //ksp-ckan.s3-us-west-2.amazonaws.com/deb stable main
  Active apt repos in: /etc/apt/sources.list.d/lutris-team-lutris-jammy.list
    1: deb [arch=amd64 signed-by=/etc/apt/keyrings/lutris-team-lutris-jammy.gpg] https: //ppa.launchpadcontent.net/lutris-team/lutris/ubuntu jammy main
  Active apt repos in: /etc/apt/sources.list.d/microsoft-prod.list
    1: deb [arch=amd64,arm64,armhf] https: //packages.microsoft.com/ubuntu/22.10/prod kinetic main
  Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
    1: deb http: //packages.linuxmint.com vera main upstream import backport
    2: deb http: //archive.ubuntu.com/ubuntu jammy main restricted universe multiverse
    3: deb http: //archive.ubuntu.com/ubuntu jammy-updates main restricted universe multiverse
    4: deb http: //archive.ubuntu.com/ubuntu jammy-backports main restricted universe multiverse
    5: deb http: //security.ubuntu.com/ubuntu/ jammy-security main restricted universe multiverse
  Active apt repos in: /etc/apt/sources.list.d/playit-cloud.list
    1: deb https: //playit-cloud.github.io/ppa/data ./
  Active apt repos in: /etc/apt/sources.list.d/spotify.list
    1: deb http: //repository.spotify.com stable non-free
Info:
  Processes: 371 Uptime: 4m Memory: 7.68 GiB used: 3.14 GiB (40.9%) Init: systemd v: 249
  runlevel: 5 Compilers: gcc: 11.3.0 alt: 11 Client: Cinnamon v: 5.6.5 inxi: 3.3.13

hope i understood it right

im going to sleep now so will be unresponsive for like 6 hours

[MiZoG]

ID-1: / size: 467.89 GiB used: 368.85 GiB (78.8%) fs: ext4 dev: /dev/sda2

SSDs tend to slow down as they're getting filled up, though older models are more affected by this.
Your "SeWoo" disk is kind of... obscure.

You haven't changed / resized / created any disk partitions lately, have you?

BTW (most likely not related to belated loading of desktop environment)
1: deb [arch=amd64,arm64,armhf] https: //packages.microsoft.com/ubuntu/22.10/prod kinetic main
Shouldn't it be "jammy" instead of "kinetic"?

[yaBoyNC]

ID-1: / size: 467.89 GiB used: 368.85 GiB (78.8%) fs: ext4 dev: /dev/sda2

SSDs tend to slow down as they're getting filled up, though older models are more affected by this.
Your "SeWoo" disk is kind of... obscure.

You haven't changed / resized / created any disk partitions lately, have you?

BTW (most likely not related to belated loading of desktop environment)
1: deb [arch=amd64,arm64,armhf] https: //packages.microsoft.com/ubuntu/22.10/prod kinetic main
Shouldn't it be "jammy" instead of "kinetic"?

Well for some answers, yeah my ssd is obscure, it came with the pc when i had a prebuilt some time ago, its probably a pretty cheap local-ish brand, but its quality isnt that bad

I have not created any disk partitions lately as far as i am aware, nor messed with the overall storage, if i could trace anything i did before it started having the delay heres some actions i did that day, to see if any tick any boxes.
- deleting old stuff to clear space
- downloaded and ran a minecraft server
- modified my firewall/opened port to run the server online

Thats all i could think of really though... also im not sure what "jammy" or "kinetic" means, should i worry about that?

[SMG]

I have not created any disk partitions lately as far as i am aware, nor messed with the overall storage, if i could trace anything i did before it started having the delay heres some actions i did that day, to see if any tick any boxes.
- deleting old stuff to clear space
- downloaded and ran a minecraft server
- modified my firewall/opened port to run the server online

Thats all i could think of really though... also im not sure what "jammy" or "kinetic" means, should i worry about that?

Jammy is the PPAs you are supposed to be using because LM21.1 is based on Jammy.

System:
Kernel: 5.15.0-56-generic x86_64 bits: 64 compiler: gcc v: 11.3.0 Desktop: Cinnamon 5.6.5
tk: GTK 3.24.33 wm: muffin dm: LightDM Distro: Linux Mint 21.1 Vera base: Ubuntu 22.04 jammy

Is there a particular reason your system is not updated? That's not the latest kernel, latest Cinnamon, nor the latest version of gcc.

Have you checked the server logs to see how long it is taking to initialize? I don't know how it might affect start-up.

[yaBoyNC]

I have not created any disk partitions lately as far as i am aware, nor messed with the overall storage, if i could trace anything i did before it started having the delay heres some actions i did that day, to see if any tick any boxes.
- deleting old stuff to clear space
- downloaded and ran a minecraft server
- modified my firewall/opened port to run the server online

Thats all i could think of really though... also im not sure what "jammy" or "kinetic" means, should i worry about that?

Jammy is the PPAs you are supposed to be using because LM21.1 is based on Jammy.

System:
Kernel: 5.15.0-56-generic x86_64 bits: 64 compiler: gcc v: 11.3.0 Desktop: Cinnamon 5.6.5
tk: GTK 3.24.33 wm: muffin dm: LightDM Distro: Linux Mint 21.1 Vera base: Ubuntu 22.04 jammy

Is there a particular reason your system is not updated? That's not the latest kernel, latest Cinnamon, nor the latest version of gcc.

Have you checked the server logs to see how long it is taking to initialize? I don't know how it might affect start-up.

im still pretty new to linux so im not too understanding but im thought my OS was pretty updated, how would i go about changing that or checking the server logs? im not exactly running a server, this is my main pc.

if you mean the boot.log this is what it says

Code: Select all

GNU nano 6.2                                                                         boot.log                                                                                         
[^[[0;32m  OK  ^[[0m] Stopped ^[[0;1;39mCUPS Scheduler^[[0m.
         Stopping ^[[0;1;39mCUPS Scheduler^[[0m...
[^[[0;32m  OK  ^[[0m] Started ^[[0;1;39mCUPS Scheduler^[[0m.
[^[[0;32m  OK  ^[[0m] Closed ^[[0;1;39mCUPS Scheduler^[[0m.
         Stopping ^[[0;1;39mCUPS Scheduler^[[0m...
[^[[0;32m  OK  ^[[0m] Listening on ^[[0;1;39mCUPS Scheduler^[[0m.
[^[[0;32m  OK  ^[[0m] Started ^[[0;1;39mUser Login Management^[[0m.
[^[[0;32m  OK  ^[[0m] Started ^[[0;1;39mAvahi mDNS/DNS-SD Stack^[[0m.
[^[[0;32m  OK  ^[[0m] Started ^[[0;1;39mThermal Daemon Service^[[0m.
[^[[0;32m  OK  ^[[0m] Started ^[[0;1;39mAuthorization Manager^[[0m.
         Starting ^[[0;1;39mModem Manager^[[0m...
         Starting ^[[0;1;39mfirewalld - dynamic firewall daemon^[[0m...
[^[[0;32m  OK  ^[[0m] Finished ^[[0;1;39mUbuntu system adjustments^[[0m.
[^[[0;32m  OK  ^[[0m] Started ^[[0;1;39mAccounts Service^[[0m.
[^[[0;32m  OK  ^[[0m] Started ^[[0;1;39mDispatcher daemon for systemd-networkd^[[0m.
[^[[0;32m  OK  ^[[0m] Started ^[[0;1;39mModem Manager^[[0m.
[^[[0;32m  OK  ^[[0m] Started ^[[0;1;39mDisk Manager^[[0m.
[^[[0;32m  OK  ^[[0m] Started ^[[0;1;39mfirewalld - dynamic firewall daemon^[[0m.
[^[[0;32m  OK  ^[[0m] Started ^[[0;1;39mBluetooth management mechanism^[[0m.
[^[[0;32m  OK  ^[[0m] Finished ^[[0;1;39mnetfilter persistent configuration^[[0m.
[^[[0;1;31mFAILED^[[0m] Failed to start ^[[0;1;39mUncomplicated firewall^[[0m.
See 'systemctl status ufw.service' for details.
[^[[0;32m  OK  ^[[0m] Reached target ^[[0;1;39mPreparation for Network^[[0m.
         Starting ^[[0;1;39mNetwork Manager^[[0m...
         Starting ^[[0;1;39mRaise network interfaces^[[0m...
[^[[0;32m  OK  ^[[0m] Finished ^[[0;1;39mRaise network interfaces^[[0m.
[^[[0;32m  OK  ^[[0m] Started ^[[0;1;39mNetwork Manager^[[0m.
[^[[0;32m  OK  ^[[0m] Reached target ^[[0;1;39mNetwork^[[0m.
[^[[0;32m  OK  ^[[0m] Reached target ^[[0;1;39mNetwork is Online^[[0m.
         Starting ^[[0;1;39mCUPS Scheduler^[[0m...
         Starting ^[[0;1;39mdnsmasq - A lightweight DHCP and caching DNS server^[[0m...
[^[[0;32m  OK  ^[[0m] Started ^[[0;1;39mGlances^[[0m.
         Starting ^[[0;1;39mOpenVPN service^[[0m...
         Starting ^[[0;1;39mPermit User Sessions^[[0m...
         Starting ^[[0;1;39mLSB: VirtualBox Linux kernel module^[[0m...
[^[[0;32m  OK  ^[[0m] Finished ^[[0;1;39mOpenVPN service^[[0m.
[^[[0;32m  OK  ^[[0m] Finished ^[[0;1;39mPermit User Sessions^[[0m.
         Starting ^[[0;1;39mLight Display Manager^[[0m...
         Starting ^[[0;1;39mHold until boot process finishes up^[[0m...
         Starting ^[[0;1;39mHostname Service^[[0m...
[^[[0;32m  OK  ^[[0m] Started ^[[0;1;39mHostname Service^[[0m.
[^[[0;1;31mFAILED^[[0m] Failed to start ^[[0;1;39mdnsmasq - A lightweight DHCP and caching DNS server^[[0m.
See 'systemctl status dnsmasq.service' for details.
[^[[0;32m  OK  ^[[0m] Reached target ^[[0;1;39mHost and Network Name Lookups^[[0m.
         Starting ^[[0;1;39mTool to automatically collect and submit kernel crash signatures^[[0m...
         Starting ^[[0;1;39mA high performance web server and a reverse proxy server^[[0m...
[^[[0;32m  OK  ^[[0m] Started ^[[0;1;39mTool to automatically collect and submit kernel crash signatures^[[0m.
[^[[0;32m  OK  ^[[0m] Started ^[[0;1;39mCUPS Scheduler^[[0m.
[^[[0;32m  OK  ^[[0m] Started ^[[0;1;39mMake remote CUPS printers available locally^[[0m.
[^[[0;32m  OK  ^[[0m] Started ^[[0;1;39mLSB: VirtualBox Linux kernel module^[[0m.
         Starting ^[[0;1;39mNetwork Manager Script Dispatcher Service^[[0m...
[^[[0;32m  OK  ^[[0m] Started ^[[0;1;39mNetwork Manager Script Dispatcher Service^[[0m.
[^[[0;1;31mFAILED^[[0m] Failed to start ^[[0;1;39mA high performance web server and a reverse proxy server^[[0m.
See 'systemctl status nginx.service' for details.

it says a lot of things failed to start and this worries me, i have run the commands it says for details and this is what i get:

Code: Select all

nginx.service - A high performance web server and a reverse proxy server
     Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Wed 2023-03-22 10:22:26 -03; 13min ago
       Docs: man:nginx(8)
    Process: 1170 ExecStartPre=/usr/sbin/nginx -t -q -g daemon on; master_process on; (code=exited, s>
        CPU: 7ms

Mar 22 10:22:26 NCdtp systemd[1]: Starting A high performance web server and a reverse proxy server...
Mar 22 10:22:26 NCdtp nginx[1170]: nginx: [emerg] bind() to 192.168.1.87:80 failed (99: Unknown error)
Mar 22 10:22:26 NCdtp nginx[1170]: nginx: configuration file /etc/nginx/nginx.conf test failed
Mar 22 10:22:26 NCdtp systemd[1]: nginx.service: Control process exited, code=exited, status=1/FAILURE
Mar 22 10:22:26 NCdtp systemd[1]: nginx.service: Failed with result 'exit-code'.
Mar 22 10:22:26 NCdtp systemd[1]: Failed to start A high performance web server and a reverse proxy s>

~
they mostly end up like this or asking me to do iptables-restore -h for more info yet i dont understand anything
please someone who has a high IQ unlike me teach me whats wrong and how to solve it
(btw i ran iptables-restore, not sure if i should have but yeah)

[SMG]

im still pretty new to linux so im not too understanding but im thought my OS was pretty updated

One opens Update Manager and runs the updates which show there. If you are not seeing updates there, then something is wrong with your system because what you posted is not the latest packages.

how would i go about changing that or checking the server logs? im not exactly running a server, this is my main pc.

You said you downloaded and installed a Minecraft server and made changes to your computer's firewall so others could access that server. That is the server I am referencing.

nginx.service is a web server. Linux Mint does not come with a web server so it is likely the addition of that Minecraft server that is causing the slow boot.

teach me whats wrong and how to solve it

Do you have a Timeshift snapshot of your system before you installed the Minecraft server? If so, revert back to it and you will probably have fast boots again.

I do not know anything about installing or running a Minecraft server so I can not help with that.

[deck_luck]

Sometimes, you will find clues of a stalling process or service in the syslog. You can run the journalctl -b -p notice from a bash command line in a terminal session and pay particular attention to the time stamps. It will start with the bootup and work to the end of the log displaying anything with a notice to more severe levels. Again, watch the time stamp at the left looking for a stalling process or service. If it gets too involved for you, a TimeShift snapshot restoration is a valid option per SMG previous suggestion.

[yaBoyNC]

im still pretty new to linux so im not too understanding but im thought my OS was pretty updated

One opens Update Manager and runs the updates which show there. If you are not seeing updates there, then something is wrong with your system because what you posted is not the latest packages.

how would i go about changing that or checking the server logs? im not exactly running a server, this is my main pc.

You said you downloaded and installed a Minecraft server and made changes to your computer's firewall so others could access that server. That is the server I am referencing.

nginx.service is a web server. Linux Mint does not come with a web server so it is likely the addition of that Minecraft server that is causing the slow boot.

teach me whats wrong and how to solve it

Do you have a Timeshift snapshot of your system before you installed the Minecraft server? If so, revert back to it and you will probably have fast boots again.

I do not know anything about installing or running a Minecraft server so I can not help with that.

alright back i am
i have fully updated the system on update manager, there was quite a lot to update there, purged nginx.service and also added an extra 16GB of ram to my system (unrelated to the matter) and now have 24GB, yet the boot time remains unchanged

i also dont have any snapshots of before the incident so reverting is impossible

Sometimes, you will find clues of a stalling process or service in the syslog. You can run the journalctl -b -p notice from a bash command line in a terminal session and pay particular attention to the time stamps. It will start with the bootup and work to the end of the log displaying anything with a notice to more severe levels. Again, watch the time stamp at the left looking for a stalling process or service. If it gets too involved for you, a TimeShift snapshot restoration is a valid option per SMG previous suggestion.

after running journalctl -b -p notice, as for clarification the first time stamp is at 17:05:08
from what i can see the worst offenders are:

ar 22 17:05:11 NCdtp systemd[1]: ufw.service: Main process exited, code=exited, status=1/FAILURE
Mar 22 17:05:11 NCdtp systemd[1]: ufw.service: Failed with result 'exit-code'.
Mar 22 17:05:11 NCdtp systemd[1]: Failed to start Uncomplicated firewall.
Mar 22 17:05:11 NCdtp lightdm[1165]: Seat type 'xlocal' is deprecated, use 'type=local' instead
Mar 22 17:05:11 NCdtp dnsmasq[1174]: failed to create listening socket for port 53: Address already in use
Mar 22 17:05:11 NCdtp dnsmasq[1174]: FAILED to start up
Mar 22 17:05:11 NCdtp systemd[1]: dnsmasq.service: Control process exited, code=exited, status=2/INVALIDARGUMENT
Mar 22 17:05:11 NCdtp systemd[1]: dnsmasq.service: Failed with result 'exit-code'.
Mar 22 17:05:11 NCdtp systemd[1]: Failed to start dnsmasq - A lightweight DHCP and caching DNS server.


Mar 22 17:05:12 NCdtp systemd[1]: nginx.service: Control process exited, code=exited, status=1/FAILURE
Mar 22 17:05:12 NCdtp systemd[1]: nginx.service: Failed with result 'exit-code'.
Mar 22 17:05:12 NCdtp systemd[1]: Failed to start A high performance web server and a reverse proxy server.
(somehow nginx is still here..?)


Mar 22 17:05:18 NCdtp dnsmasq[1414]: chown of PID file /run/NetworkManager/dnsmasq.pid failed: Operation not permitted
Mar 22 17:05:18 NCdtp dnsmasq[1414]: warning: no upstream servers configured
Mar 22 17:05:40 NCdtp dbus-daemon[885]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms)
Mar 22 17:05:40 NCdtp pulseaudio[1279]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application >
Mar 22 17:07:25 NCdtp gnome-keyring-daemon[1597]: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory
Mar 22 17:07:25 NCdtp gnome-keyring-daemon[1598]: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory
Mar 22 17:07:25 NCdtp gnome-keyring-daemon[1599]: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory
Mar 22 17:07:25 NCdtp goa-daemon[1717]: goa-daemon version 3.44.0 starting
Mar 22 17:07:26 NCdtp cinnamon-session[1280]: WARNING: t+1,09562s: Failed to start app: Unable to start application: Failed to execute child process “/usr/lib/x86_64-linux-gnu/l>
Mar 22 17:07:26 NCdtp polkitd(authority=local)[904]: Registered Authentication Agent for unix-session:c1 (system bus name :1.59 [/usr/lib/policykit-1-gnome/polkit-gnome-authenti>
Mar 22 17:07:27 NCdtp cinnamon-session[1280]: WARNING: t+1,60020s: Detected that screensaver has appeared on the bus
Mar 22 17:07:28 NCdtp gnome-keyring-daemon[1597]: asked to register item /org/freedesktop/secrets/collection/login/2, but it's already registered
Mar 22 17:07:31 NCdtp kernel: [drm:nv_drm_fence_context_create_ioctl [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000400] Failed to allocate fence signaling event
Mar 22 17:07:36 NCdtp kernel: [drm:nv_drm_fence_context_create_ioctl [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000400] Failed to allocate fence signaling event
Mar 22 17:07:36 NCdtp kernel: [drm:nv_drm_fence_context_create_ioctl [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000400] Failed to allocate fence signaling event
Mar 22 17:07:37 NCdtp kernel: [drm:nv_drm_fence_context_create_ioctl [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000400] Failed to allocate fence signaling event
Mar 22 17:07:37 NCdtp kernel: [drm:nv_drm_fence_context_create_ioctl [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000400] Failed to allocate fence signaling event
Mar 22 17:07:57 NCdtp cinnamon-session[1280]: WARNING: t+31,60361s: Detected that screensaver has left the bus
Mar 22 17:08:28 NCdtp sudo[3954]: nicolas : TTY=pts/0 ; PWD=/home/nicolas ; USER=root ; COMMAND=/usr/local/bin/apt purge nginx
Mar 22 17:08:37 NCdtp sudo[3966]: nicolas : TTY=pts/0 ; PWD=/home/nicolas ; USER=root ; COMMAND=/usr/local/bin/apt upgrade
(and this area specially, the jump from 17:05 to 17:07 leads me to believe the delay lies here, not sure how to fix yet and i fear messing it up more if i try fixing it with my limited knowledge)

please guide me here, now's the home stretch.

[SMG]

purged nginx.service

What steps did you do to purge it? I have noticed (as you have also noticed) that is still appears to be on your system which is why I ask the question.

What is the output of

Code: Select all

systemd-analyze critical-chain

after running journalctl -b -p notice, as for clarification the first time stamp is at 17:05:08
from what i can see the worst offenders are:

ufw is the firewall which comes with Linux Mint (although you do have to enable it if you want to use it). You said you modified the firewall so did you reverse those changes when you removed nginx.service?

[yaBoyNC]

purged nginx.service

What steps did you do to purge it? I have noticed (as you have also noticed) that is still appears to be on your system which is why I ask the question.

What is the output of

Code: Select all

systemd-analyze critical-chain

after running journalctl -b -p notice, as for clarification the first time stamp is at 17:05:08
from what i can see the worst offenders are:

ufw is the firewall which comes with Linux Mint (although you do have to enable it if you want to use it). You said you modified the firewall so did you reverse those changes when you removed nginx.service?

well to purge it i just did sudo apt purge nginx, and if i try it again it says it doesnt exist anymore
i also have reverted the changes to the best of my ability but may have missed some
im not too worried about the ufw part, more the
"gnome-keyring-daemon[1597]: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory"
that increased time by 2 minutes, couldnt find anything conclusive about it after searching

also systemd-analyze, (along with critical-chain), only shows the time before the icon disappears and the black screen stays, so it only says the boot took ~30s.

[SMG]

well to purge it i just did sudo apt purge nginx, and if i try it again it says it doesnt exist anymore

That command only removes system level config files (as well as the packages). Maybe there is still something in your home directory?

im not too worried about the ufw part, more the
"gnome-keyring-daemon[1597]: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory"
that increased time by 2 minutes, couldnt find anything conclusive about it after searching

I believe your sockets are your server ports. That's why I thought the firewall might be a factor.

Check through this link to see if there might be anything helpful How to Uninstall Nginx Completely. It mentions some places to check and in section 2.3 what to do if it seems like it failed to remove. (Ignore the RPM stuff. Linux Mint is Debian based.)

[zcot]

With this output, why is there no - in the user-host label?

It shows NCdtp but I can't figure out why.

The user's home is nicolas but I can't make sense of it all.

Initially it would seem like, perhaps, iptables has a failing config, the initial errors are showing from ufw, it was mentioned, but then again the errors just continue from that point and get into stuff that wouldn't especially be related to just a misconfigured iptables/ufw setup.

[yaBoyNC]

With this output, why is there no - in the user-host label?

It shows NCdtp but I can't figure out why.

The user's home is nicolas but I can't make sense of it all.

Initially it would seem like, perhaps, iptables has a failing config, the initial errors are showing from ufw, it was mentioned, but then again the errors just continue from that point and get into stuff that wouldn't especially be related to just a misconfigured iptables/ufw setup.

THATS WHAT IM SAYING
It doesnt make sense
I have found no other case like mine online, i have been overclocking my brain for the past week trying to umderstand this but its just impossible...

Does anyone know about the parts that slowed down the boot by minutes? Thats the main worry i have at the moment cause im slower than my old hard drive at the moment and its attacking my sanity

[SMG]

Does anyone know about the parts that slowed down the boot by minutes? Thats the main worry i have at the moment cause im slower than my old hard drive at the moment and its attacking my sanity

There is nothing specifically slowing down your boot in the sense of putting the brakes on something.

What appears to be happening is a process is failing and keeps trying again. The repeat attempts until the system gives up would be why the overall process is slower.

Going back to your earlier outputs, I see firewalld - dynamic firewall daemon so it seems you replaced ufw with firewalld.

It appears you also have mdnsmasq - A lightweight DHCP and caching DNS server installed.

And then you also had nginx installed which you have removed. Do you still have the other two installed?

The below line is cut off at the end so we don't know what app failed to start, but problem apps will cause slow boot time.

Code: Select all

Mar 22 17:07:26 NCdtp cinnamon-session[1280]: WARNING: t+1,09562s: Failed to start app: Unable to start application: Failed to execute child process “/usr/lib/x86_64-linux-gnu/l>

This looks to be a permissions issue and it happened for three different processes. (This is just after the two minute gap.)

Code: Select all

Mar 22 17:07:25 NCdtp gnome-keyring-daemon[1597]: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory
Mar 22 17:07:25 NCdtp gnome-keyring-daemon[1598]: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory
Mar 22 17:07:25 NCdtp gnome-keyring-daemon[1599]: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory

THATS WHAT IM SAYING
It doesnt make sense

It appears you did not undo everything you did.

One installs the system. When it is working one either takes a Timeshift snapshot or clones the drive or does some other backup so if the system gets messed up one can revert to a working system. You did not do that so you are now in the process of trying to remember everything you did so you can undo it.

There is also the option to back up your personal data and re-install and this time have a back-up restore plan in place before making changes.

[zcot]

So, digging further, I see most of these lines are prior to user login so that's the reference for the host only.

It seems like one initial problem is a failure at ufw, -the default firewall already installed. You can just reset it to default, but no clue if that will adversely affect some other things, because I see reference to OpenVPN as well as the whatever is going on with the playit-cloud system, -which I know nothing about. So if they are requiring a specific firewall set it could affect them.

I didn't even catch was SMG mentioned about a secondary firewall as well.

On a default setup dnsmasq is not in use, but the software is actually there, but it seems like, probably, one of those previously mentioned items is probably trying to use it. But systemd-resolve is using the same setup and default port so you have to do some management. I think you typically use one or the other, but there's the case where you can specifically have both in use with various manual configurations and maybe related within the previous software configurations as well.

Checking about how to setup a minecraft server that seems pretty straight forward and doesn't involve installing a web server or tinkering with dns, only open a firewall port.

Anyway, there's some issue that might be just be one simple thing, but I can't see it like that, for me it appears an entire spider web of possibility, because we are missing other info.

So much is unknown. you mentioned what you "just previously did" and just said setup a minecraft server but was openvpn a part of that or not and the playit-cloud thing? A lot going on there.

[yaBoyNC]

alright so back i am here
i have solved the most problematic parts with one exception...

Code: Select all

Mar 23 12:19:32 NCdtp gnome-keyring-daemon[1607]: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory
Mar 23 12:19:32 NCdtp gnome-keyring-daemon[1608]: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory
Mar 23 12:19:32 NCdtp gnome-keyring-daemon[1611]: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory

this slows me down by a full 2 minutes
i have only found stuff about this in arch linux forums wich im pretty sure is different than mint so yeah...
does anyone here know what this means and specially how to fix it?

[SMG]

does anyone here know what this means and specially how to fix it?

Here is GNOME wiki's information for GNOME Keyring. My system only has one process accessing it (however I do not use VPNs). Your system appears to have three different processes (the numbers in brackets) trying to access it.

Do you normally log into your system or do you bypass having to input a password? As indicated on gnome-keyring-daemon (1) - Linux Man Pages, "It is normally started automatically when a user logs into a desktop session."

[yaBoyNC]

I resign

i ended up deciding to do a fresh install after backing up my data since it was a lot easier than continuing to be stressed trying to find out what slows everything down...

yeah thats about it now tho, if anyone else ends up with this problem, which i find unlikely, hope you find a better solution than me.