Black screen after installing kernel 6.10

[MW_J97]

Hello there,

After I updated the kernel to 6.10.0-1, I can’t boot to my DE with this error

Failed to start Samba NMB deamon

How can I fix this, please?
Thanks in advance.

[Mirdarthos]

Hi @MW_J97,

Had you searched first as you should have, you’d have found:

Samba nmb daemon won't start. Can't boot into DE

The nmb service is not necessary for the system to boot - the only thing it does is enabling netbios hostname resolution. You are having another issue … I suggest you disable smb and nmb alltogether and then troubleshoot you nic sudo systemctl disable --now smb nmb On your question on reinstalling Reinstall Manjaro preserving the $USER files and settings

[MW_J97]

Hi @Mirdarthos
Thanks for replying.
Yes, I found this post, but I don’t know what’s the fix in it.

I suggest you disable smb and nmb alltogether and then troubleshoot you nic

sudo systemctl disable --now smb nmb

This disables the smb and nmb, then what should I do?

[Mirdarthos]

Are you in a live environment? That probably wouldn’t have done anything. In my humble opinion the easiest would be to enter a chroot environment, and then disable it.
In a chroot environment? Exit the chroot environment, then reboot and see.
If it happens after reboot, then more information is required. Enter a chroot environment, and provide the lawgs here:

How to chroot

1. Ensure you’ve got a relatively new ISO or at least one with a still supported LTS kernel.

2. Write/copy/dd the ISO to a USB thumb drive.

3. When done, boot with the above mentioned USB thumb drive into the live environment.

4. Once booted, open a terminal and enter the following command to enter the chroot environment:

manjaro-chroot -a

5. If you have more than one Linux installation, select the correct one to use from the list provided.

When done, you should now be in the chroot environment.

But, be careful, as you’re now in an actual root environment on your computer, so any changes you make will persist after a restart.

Finding errors for specific boot

journalctl --priority=warning..crit --no-pager --boot=-1

Where:

• The --priority=warning..err argument limits the output to warnings and errors only;
• and the --no-pager formats the output nicely for use here, on the forum;
• the --boot=-1 argument limits the output to log messages from the previous boot. This can be adjusted to -2 for the boot before that, -3 to the boot before that, and so on and so forth.

---

Tip

When posting terminal output, copy the output and paste it here, wrapped in three (3) backticks, before AND after the pasted text. Like this:

```
pasted text
```

Or three (3) tilde signs, like this:

~~~
pasted text
~~~

This will just cause it to be rendered like this:

Sed
sollicitudin dolor
eget nisl elit id
condimentum
arcu erat varius
cursus sem quis eros.

Instead of like this:

Sed sollicitudin dolor eget nisl elit id condimentum arcu erat varius cursus sem quis eros.

Alternatively, paste the text you wish to format as terminal output, select all pasted text, and click the </> button on the taskbar. This will indent the whole pasted section with one TAB, causing it to render the same way as described above.

Thereby increasing legibility thus making it easier for those trying to provide assistance.

For more information, please see:

@Fabby

On this forum here you need to have Trust Level 1 (=TL1) to be able to post screenshots and links in-line.

That’s dumb! Why is that?

Well, that’s because on our old forum we got tons of screenshots of text, links to SPAM, PR0N and other things you don’t want on a forum, so all the new users are prohibited from posting links and pics because of a few bad actors.

---

Additionally

If your language isn’t English, please prepend any and all terminal commands with LC_ALL=C. For example:

LC_ALL=C bluetoothctl

This will just cause the terminal output to be in English, making it easier to understand and debug.

[MW_J97]

@Mirdarthos

journalctl --priority=warning..crit --no-pager --boot=-1

For this command, here it’s the result:

Jul 20 11:27:04 mina-manjaro kernel: MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for more details.
Jul 20 11:27:04 mina-manjaro kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Jul 20 11:27:04 mina-manjaro kernel: integrity: Problem loading X.509 certificate -74
Jul 20 11:27:04 mina-manjaro kernel: ata2.01: failed to resume link (SControl 30)
Jul 20 11:27:04 mina-manjaro kernel: ata2.00: supports DRM functions and may not be fully accessible
Jul 20 11:27:04 mina-manjaro kernel: ata2.00: supports DRM functions and may not be fully accessible
Jul 20 11:27:04 mina-manjaro systemd-modules-load[315]: Failed to find module 'nvidia'
Jul 20 11:27:04 mina-manjaro systemd-modules-load[315]: Failed to find module 'nvidia-drm'
Jul 20 11:27:04 mina-manjaro systemd-modules-load[315]: Failed to find module 'nvidia-uvm'
Jul 20 11:27:05 mina-manjaro kernel: ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000400-0x000000000000047F (\PMIO) (20240322/utaddress-204)
Jul 20 11:27:05 mina-manjaro kernel: ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20240322/utaddress-204)
Jul 20 11:27:05 mina-manjaro kernel: ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20240322/utaddress-204)
Jul 20 11:27:05 mina-manjaro kernel: ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20240322/utaddress-204)
Jul 20 11:27:05 mina-manjaro kernel: lpc_ich: Resource conflict(s) found affecting gpio_ich
Jul 20 11:27:05 mina-manjaro kernel: at24 0-0050: supply vcc not found, using dummy regulator
Jul 20 11:27:05 mina-manjaro kernel: at24 0-0053: supply vcc not found, using dummy regulator
Jul 20 11:27:08 mina-manjaro systemd-tmpfiles[608]: Detected unsafe path transition /etc/ssh (owned by minaw) → /etc/ssh/ssh_config.d (owned by root) during canonicalization of etc/ssh/ssh_config.d.
Jul 20 11:27:08 mina-manjaro systemd-tmpfiles[608]: Detected unsafe path transition /etc/ssh (owned by minaw) → /etc/ssh/sshd_config.d (owned by root) during canonicalization of etc/ssh/sshd_config.d.
Jul 20 11:27:08 mina-manjaro systemd-tmpfiles[608]: Detected unsafe path transition /etc/ssh (owned by minaw) → /etc/ssh/sshd_config.d (owned by root) during canonicalization of etc/ssh/sshd_config.d.
Jul 20 11:27:08 mina-manjaro systemd-tmpfiles[608]: Detected unsafe path transition /etc (owned by minaw) → /etc/redis (owned by root) during canonicalization of etc/redis.
Jul 20 11:27:08 mina-manjaro systemd-tmpfiles[608]: Detected unsafe path transition /etc (owned by minaw) → /etc/audisp (owned by root) during canonicalization of etc/audisp.
Jul 20 11:27:08 mina-manjaro systemd-tmpfiles[608]: Detected unsafe path transition /etc (owned by minaw) → /etc/audit (owned by root) during canonicalization of etc/audit.
Jul 20 11:27:08 mina-manjaro systemd-tmpfiles[608]: Detected unsafe path transition /etc (owned by minaw) → /etc/audit (owned by root) during canonicalization of etc/audit/audisp-remote.conf.
Jul 20 11:27:08 mina-manjaro systemd-tmpfiles[608]: Detected unsafe path transition /etc (owned by minaw) → /etc/audit (owned by root) during canonicalization of etc/audit/plugins.d.
Jul 20 11:27:08 mina-manjaro systemd-tmpfiles[608]: Detected unsafe path transition /etc (owned by minaw) → /etc/audit (owned by root) during canonicalization of etc/audit/plugins.d/syslog.conf.
Jul 20 11:27:08 mina-manjaro systemd-tmpfiles[608]: Detected unsafe path transition /etc (owned by minaw) → /etc/audit (owned by root) during canonicalization of etc/audit/plugins.d/filter.conf.
Jul 20 11:27:08 mina-manjaro systemd-tmpfiles[608]: Detected unsafe path transition /etc (owned by minaw) → /etc/audit (owned by root) during canonicalization of etc/audit/plugins.d/af_unix.conf.
Jul 20 11:27:08 mina-manjaro systemd-tmpfiles[608]: Detected unsafe path transition /etc (owned by minaw) → /etc/audit (owned by root) during canonicalization of etc/audit/plugins.d/au-remote.conf.
Jul 20 11:27:08 mina-manjaro systemd-tmpfiles[608]: Detected unsafe path transition /etc (owned by minaw) → /etc/audit (owned by root) during canonicalization of etc/audit/plugins.d/audispd-zos-remote.conf.
Jul 20 11:27:08 mina-manjaro systemd-tmpfiles[608]: Detected unsafe path transition /etc (owned by minaw) → /etc/libaudit.conf (owned by root) during canonicalization of etc/libaudit.conf.
Jul 20 11:27:08 mina-manjaro systemd[1]: systemd-swap.service: Failed with result 'exit-code'.
Jul 20 11:27:08 mina-manjaro systemd[1]: Failed to start Manage swap spaces on zram, files and partitions..
Jul 20 11:27:11 mina-manjaro sddm[740]: Failed to read display number from pipe
Jul 20 11:27:11 mina-manjaro sddm[740]: Attempt 1 starting the Display server on vt 2 failed
Jul 20 11:27:13 mina-manjaro sddm[740]: Failed to read display number from pipe
Jul 20 11:27:13 mina-manjaro sddm[740]: Attempt 2 starting the Display server on vt 2 failed
Jul 20 11:27:15 mina-manjaro nmbd[755]: [2024/07/20 11:27:15.258288,  0] ../../source3/nmbd/nmbd_subnetdb.c:252(create_subnets)
Jul 20 11:27:15 mina-manjaro nmbd[755]:   NOTE: NetBIOS name resolution is not supported for Internet Protocol Version 6 (IPv6).
Jul 20 11:27:15 mina-manjaro sddm[740]: Failed to read display number from pipe
Jul 20 11:27:15 mina-manjaro sddm[740]: Attempt 3 starting the Display server on vt 2 failed
Jul 20 11:27:15 mina-manjaro sddm[740]: Could not start Display server on vt 2
Jul 20 11:28:45 mina-manjaro systemd[1]: nmb.service: start operation timed out. Terminating.
Jul 20 11:28:45 mina-manjaro systemd[1]: nmb.service: Failed with result 'timeout'.
Jul 20 11:28:45 mina-manjaro systemd[1]: Failed to start Samba NMB Daemon.
Jul 20 11:29:09 mina-manjaro sddm[740]: Signal received: SIGTERM
Jul 20 11:29:09 mina-manjaro dbus-broker-launch[625]: Activation request for 'org.freedesktop.Avahi' failed.
Jul 20 11:29:09 mina-manjaro dbus-broker-launch[625]: Activation request for 'org.freedesktop.nm_dispatcher' failed.

I saw the error inside it despite I am on another kernel 6.9.9-1, so I can boot from it. But, from kernel 6.10 I can’t.

[linux-aarhus]

I think this is an xy problem.

How did you arrive at the conclusion that nmb daemon is halting your system start ?

Why do you have the nmb daemon enabled in the first place?

@MW_J97

Jul 20 11:27:08 mina-manjaro systemd-tmpfiles[608]: Detected unsafe path transition /etc/ssh (owned by minaw) → /etc/ssh/ssh_config.d (owned by root) during canonicalization of etc/ssh/ssh_config.d.

You have been messing with file system permissions - and this may be the root cause of your issues.

Messed up folder and file permissions - restore defaults for /run

Hello everyone, I never thought this happens to me so soon, but I messed up my system and many things like copy and paste from and to Firefox, starting apps, having sound and so stopped working when I changed permissions for subfolders and files recursive for the /var/lib/docker/overlay2/ folder after the security checker wazuh-agent complaint about world-write permissions on files owned by root. I thought this was only docker related, I don’t use it any time soon and if something fails with d…

[MW_J97]

Thanks for replying.

@linux-aarhus

I think this is an xy problem.

What is xy, please?

@linux-aarhus

How did you arrive at the conclusion that nmb daemon is halting your system start ?

After installing kernel 6.10 and reboot, I am stuck on a black screen with this message

Failed to start Samba NMB deamon

[quote=“linux-aarhus, post:6, topic:165792”]
Why do you have the nmb daemon enabled in the first place?

@MW_J97

I have no idea what does this do, actually.

@linux-aarhus

You have been messing with file system permissions - and this may be the root cause of your issues.

I didn’t do anything except for installing new kernel.

[Mirdarthos]

@MW_J97

What is xy, please?

https://xyproblem.info/

[linux-aarhus]

@MW_J97

I didn’t do anything except for installing new kernel.

But you did - the log is proof of that.

The XY problem is asking about your attempted solution rather than your actual problem. This leads to enormous amounts of wasted time and energy, both on the part of people asking for help, and on the part of those providing help.
– https://xyproblem.info/

The system depends on the permissions to be correct - some services refuse to run if their configuration file permissions has been altered - such as is explained in the error message in the log I qouted above.

[MW_J97]

@linux-aarhus

But you did - the log is proof of that.

From the beginning of using Manjaro, I didn’t do anything except updates.
But, for now, what should I do for this issue? Rolling back to the last kernel?

[linux-aarhus]

@MW_J97

From the beginning of using Manjaro, I didn’t do anything except updates.

@MW_J97

Jul 20 11:27:08 mina-manjaro systemd-tmpfiles[608]: Detected unsafe path transition /etc/ssh (owned by minaw) → /etc/ssh/ssh_config.d (owned by root) during canonicalization of etc/ssh/ssh_config.d.
Jul 20 11:27:08 mina-manjaro systemd-tmpfiles[608]: Detected unsafe path transition /etc/ssh (owned by minaw) → /etc/ssh/sshd_config.d (owned by root) during canonicalization of etc/ssh/sshd_config.d.
Jul 20 11:27:08 mina-manjaro systemd-tmpfiles[608]: Detected unsafe path transition /etc/ssh (owned by minaw) → /etc/ssh/sshd_config.d (owned by root) during canonicalization of etc/ssh/sshd_config.d.
Jul 20 11:27:08 mina-manjaro systemd-tmpfiles[608]: Detected unsafe path transition /etc (owned by minaw) → /etc/redis (owned by root) during canonicalization of etc/redis.
Jul 20 11:27:08 mina-manjaro systemd-tmpfiles[608]: Detected unsafe path transition /etc (owned by minaw) → /etc/audisp (owned by root) during canonicalization of etc/audisp.
Jul 20 11:27:08 mina-manjaro systemd-tmpfiles[608]: Detected unsafe path transition /etc (owned by minaw) → /etc/audit (owned by root) during canonicalization of etc/audit.
Jul 20 11:27:08 mina-manjaro systemd-tmpfiles[608]: Detected unsafe path transition /etc (owned by minaw) → /etc/audit (owned by root) during canonicalization of etc/audit/audisp-remote.conf.
Jul 20 11:27:08 mina-manjaro systemd-tmpfiles[608]: Detected unsafe path transition /etc (owned by minaw) → /etc/audit (owned by root) during canonicalization of etc/audit/plugins.d.
Jul 20 11:27:08 mina-manjaro systemd-tmpfiles[608]: Detected unsafe path transition /etc (owned by minaw) → /etc/audit (owned by root) during canonicalization of etc/audit/plugins.d/syslog.conf.
Jul 20 11:27:08 mina-manjaro systemd-tmpfiles[608]: Detected unsafe path transition /etc (owned by minaw) → /etc/audit (owned by root) during canonicalization of etc/audit/plugins.d/filter.conf.
Jul 20 11:27:08 mina-manjaro systemd-tmpfiles[608]: Detected unsafe path transition /etc (owned by minaw) → /etc/audit (owned by root) during canonicalization of etc/audit/plugins.d/af_unix.conf.
Jul 20 11:27:08 mina-manjaro systemd-tmpfiles[608]: Detected unsafe path transition /etc (owned by minaw) → /etc/audit (owned by root) during canonicalization of etc/audit/plugins.d/au-remote.conf.
Jul 20 11:27:08 mina-manjaro systemd-tmpfiles[608]: Detected unsafe path transition /etc (owned by minaw) → /etc/audit (owned by root) during canonicalization of etc/audit/plugins.d/audispd-zos-remote.conf.
Jul 20 11:27:08 mina-manjaro systemd-tmpfiles[608]: Detected unsafe path transition /etc (owned by minaw) → /etc/libaudit.conf (owned by root) during canonicalization of etc/libaudit.conf.

Your log says otherwise - permissions does not change from root to a user without intervention by the user.

See the topic linked above on messed up folder and file permissions.

Install the package pacutils - then see

man pacrepairfile

[MW_J97]

@Mirdarthos

I think that’s a good idea.

Can disabling nmb and smb affect anything on the system?

[Mirdarthos]

@linux-aarhus

permissions does not change from root to a user without intervention by the user

Can confirm. In ±4 years, if there was any issue, it was because of me. Things don’t just happen.

[MW_J97]

@linux-aarhus

See the topic linked above on messed up folder and file permissions

Okay, I will see it. But, this issue appeared only after the kernel update and works fine on the kernel 6.9.9-1. So, shall I do anything for it?

[linux-aarhus]

@MW_J97

this issue appeared only after the kernel update

It has nothing to do with the kernel update.

Classical xy-problem

@MW_J97

So, shall I do anything for it?

You should most certainly fix the permissions so your system is in supportable state.

If your filesystem permissions for system files is different than default - it is unsupported.

As for smb and nmb - those are for the samba filesharing service and is not required for correct system operation - in fact - incorrectly configured smb service may cause severe issue for your data.

So unless you run a samba file sharing service it recommended to not enable those services.

They are NOT required if all you do is access your home router data share or a NAS in your local network.

[Mirdarthos]

@MW_J97

Can disabling nmb and smb affect anything on the system?

Nah. I don’t think so. Mine is also disabled:

$ systemctl status {s,n}mb.service
○ smb.service - Samba SMB Daemon
Loaded: loaded (/usr/lib/systemd/system/smb.service; disabled; preset: disabled)
Active: inactive (dead)
Docs: man:smbd(8)
man:samba(7)
man:smb.conf(5)

○ nmb.service - Samba NMB Daemon
Loaded: loaded (/usr/lib/systemd/system/nmb.service; disabled; preset: disabled)
Active: inactive (dead)
Docs: man:nmbd(8)
man:samba(7)
man:smb.conf(5)

And it can be enabled again.

[MW_J97]

@linux-aarhus

So unless you run a samba file sharing service it recommended to not enable those services.

I disabled them, whit the same issue except for giving me full black screen without the error in the post title

systemctl status {s,n}mb.service                  ✔ 
○ smb.service - Samba SMB Daemon
     Loaded: loaded (/usr/lib/systemd/system/smb.service; disabl>
     Active: inactive (dead)
       Docs: man:smbd(8)
             man:samba(7)
             man:smb.conf(5)

○ nmb.service - Samba NMB Daemon
     Loaded: loaded (/usr/lib/systemd/system/nmb.service; disabl>
     Active: inactive (dead)
       Docs: man:nmbd(8)
             man:samba(7)
             man:smb.conf(5)

[linux-aarhus]

@MW_J97

I disabled them, whit the same issue

So you see - it was not nmb daemon.

This is a GPU issue - graphics configuration - possibly caused by using an Nvidia GPU

Plymouth may also cause issues when Nvidia GPU is used.

We will rename your topic to something more appropriate.

While I do that you should provide some insight in your system.

The link provided by this command

inxi -Fazy | curl -F 'file=@-' https://0x0.st

[Mirdarthos]

I’m going with out well-known bad actor: plymouth

[linux-aarhus]

@Mirdarthos

well-known bad actor: plymouth

Not bad actor - it all depends on the system at hand…