Hi, I have my Manjaro stops booting and shows strange error. What to do wit this? Step by step, please

OK, I opened terminal, type "sudo nano /etc/NetworkManager/NetworkManager.conf"

what I see on screen:

[main]
plugins=keyfile
dns=default

HTTP-based connectivity check

#[connectivity]
#uri=://nmcheck.gnome.org/check_network_status.txt
#interval=100

Good morning! Can you go down with with :arrow_down: key?
If there is no entry for [device] like above, then write it.

After saving changes and rebooting, the system gets stuck on "Starting Network Manager Script Dispatcher Service..." :thumbsdown: :frowning:

I'm reading this https://wiki.archlinux.org/index.php/NetworkManager#Network_services_with_NetworkManager_dispatcher
Hope we will find a solution.

I can reach my data on harddisk using bootable USB, so probably best and fastest solution will be to reinstall system. Thanks for help and your time!

This is not the "right" way to solve it. But if you cannot wait for a more knowledgeable person than me to join then reinstall. I was reading but don't understand what to do. However this problem might happen again after reinstall, because it is hardware related and the hardware won't change. :frowning:

What is the output of

systemctl status NetworkManager-dispatcher

Re-installing every time you encounter an issue is not really a solution, especially if the issue is either hardware related or caused by a particular system update. It will just happen again and you won't undertand why it occurred.

[petja@petja ~]$ systemctl status NetworkManager-dispatcher
● NetworkManager-dispatcher.service - Network Manager Script Dispatcher Servi
Loaded: loaded (/usr/lib/systemd/system/NetworkManager-dispatcher.service;
Active: inactive (dead)

lis 22 15:44:34 petja systemd[1]: Starting Network Manager Script Dispatcher
lis 22 15:44:34 petja systemd[1]: Started Network Manager Script Dispatcher S
lis 22 15:44:35 petja nm-dispatcher[785]: req:1 'hostname': new request (1 sc
lis 22 15:44:35 petja nm-dispatcher[785]: req:1 'hostname': start running ord
lis 22 15:45:24 petja systemd[1]: Starting Network Manager Script Dispatcher
lis 22 15:45:24 petja systemd[1]: Started Network Manager Script Dispatcher S
lis 22 15:45:24 petja nm-dispatcher[1243]: req:1 'connectivity-change': new r
lis 22 15:45:24 petja nm-dispatcher[1243]: req:1 'connectivity-change': start
lis 22 15:45:24 petja nm-dispatcher[1243]: req:2 'up' [wlo1]: new request (1
lis 22 15:45:24 petja nm-dispatcher[1243]: req:2 'up' [wlo1]: start running o
lines 1-14/14 (END)...skipping...
● NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service
Loaded: loaded (/usr/lib/systemd/system/NetworkManager-dispatcher.service; enabled; vendor preset: disabled)
Active: inactive (dead)

lis 22 15:44:34 petja systemd[1]: Starting Network Manager Script Dispatcher Service...
lis 22 15:44:34 petja systemd[1]: Started Network Manager Script Dispatcher Service.
lis 22 15:44:35 petja nm-dispatcher[785]: req:1 'hostname': new request (1 scripts)
lis 22 15:44:35 petja nm-dispatcher[785]: req:1 'hostname': start running ordered scripts...
lis 22 15:45:24 petja systemd[1]: Starting Network Manager Script Dispatcher Service...
lis 22 15:45:24 petja systemd[1]: Started Network Manager Script Dispatcher Service.
lis 22 15:45:24 petja nm-dispatcher[1243]: req:1 'connectivity-change': new request (1 scripts)
lis 22 15:45:24 petja nm-dispatcher[1243]: req:1 'connectivity-change': start running ordered scripts...
lis 22 15:45:24 petja nm-dispatcher[1243]: req:2 'up' [wlo1]: new request (1 scripts)
lis 22 15:45:24 petja nm-dispatcher[1243]: req:2 'up' [wlo1]: start running ordered scripts...

Please format your output using code tags, you have truncated the end of the error messages.

Makes it difficult to help without all the info.

Have you searched the web and the Arch Forums for info releated to this service not starting, or for specific error messages listed above?

Also, what were you doing prior to this issue occurring? Was this update related or did you make any changes?

What is your networking config? Are you using wireless? Are you connecting to a VPN at startup?

EDIT:

Can you also run journalctl | grep nm-dispatcher. If this output is large can you please pastebin it.

[quote="sueridgepipe, post:27, topic:13023"]
Please format your output using code tags
[/quote]Really? "code tags" ... for this guy ... :rofl:
You might as well have written:
Chonde mtundu linanena bungwe lanu ntchito Tags kachidindo :laughing:

This guy is a total newbie for Linux and CLI. Think of instructing him like teaching a five year old how to ride a bike. ...which includes how to use the brakes, ;). IOW, e v e r y single step is required, which is laborious as well as trickier and more difficult than it sounds.

You and eugen-b get my vote for bravery for the attempt. :laughing:

[quote="sueridgepipe, post:27, topic:13023"]you have truncated the end of the error messages.[/quote]That's actually an artifact of copy&paste for at least systemctl(or journalctl) messages to terminal/shell. Systemctl does not wrap messages so when right edge of shell/terminal window/screen is reached the text is cut.
E.g.,
On a 80x24 shell:

$>  systemctl status iptables
● iptables.service - Packet Filtering Framework
   Loaded: loaded (/usr/lib/systemd/system/iptables.service; enabled; vendor pre
   Active: active (exited) since Tue 2016-11-22 15:40:51 CST; 15h ago
  Process: 28200 ExecStart=/usr/bin/iptables-restore /etc/iptables/iptables.rule
 Main PID: 28200 (code=exited, status=0/SUCCESS)
    Tasks: 0 (limit: 4915)
   CGroup: /system.slice/iptables.service

Enlarge the shell(Xterm in this case).
On a 130x24 terminal:

$>  systemctl status iptables
● iptables.service - Packet Filtering Framework
   Loaded: loaded (/usr/lib/systemd/system/iptables.service; enabled; vendor preset: disabled)
   Active: active (exited) since Tue 2016-11-22 15:40:51 CST; 15h ago
  Process: 28200 ExecStart=/usr/bin/iptables-restore /etc/iptables/iptables.rules (code=exited, status=0/SUCCESS)
 Main PID: 28200 (code=exited, status=0/SUCCESS)
    Tasks: 0 (limit: 4915)
   CGroup: /system.slice/iptables.service

I have not ascertained specifically what the cause is, yet, however I have only seen it with systemd commands like systemctl & journalctl ...so far.

Small shell:

$>  journalctl
-- Logs begin at Sat 2016-10-15 19:04:58 CDT, end at Tue 2016-11-22 22:16:51 CST. 
Oct 15 19:04:58 Manjaro16061 systemd-journald[219]: Runtime journal (/run/log/jour
Oct 15 19:04:59 Manjaro16061 systemd-journald[219]: System journal (/var/log/journ
Oct 15 19:04:59 Manjaro16061 systemd-journald[219]: Time spent on flushing to /var
Oct 15 19:04:59 Manjaro16061 kernel: sd 0:1:0:0: [sdc] No Caching mode page found
Oct 15 19:04:59 Manjaro16061 kernel: sd 0:1:0:0: [sdc] Assuming drive cache: write
Oct 15 19:04:59 Manjaro16061 systemd-journald[219]: Missed 1 kernel messages
Oct 15 19:04:59 Manjaro16061 systemd-journald[219]: Journal started

Large shell:

$>  journalctl
-- Logs begin at Sat 2016-10-15 19:04:58 CDT, end at Tue 2016-11-22 22:16:51 CST. --
Oct 15 19:04:58 Manjaro16061 systemd-journald[219]: Runtime journal (/run/log/journal/) is 8.0M, max 201.0M, 193.0M free.
Oct 15 19:04:59 Manjaro16061 systemd-journald[219]: System journal (/var/log/journal/) is 344.0M, max 1.9G, 1.6G free.
Oct 15 19:04:59 Manjaro16061 systemd-journald[219]: Time spent on flushing to /var is 1.703ms for 2 entries.
Oct 15 19:04:59 Manjaro16061 kernel: sd 0:1:0:0: [sdc] No Caching mode page found
Oct 15 19:04:59 Manjaro16061 kernel: sd 0:1:0:0: [sdc] Assuming drive cache: write through
Oct 15 19:04:59 Manjaro16061 systemd-journald[219]: Missed 1 kernel messages
Oct 15 19:04:59 Manjaro16061 systemd-journald[219]: Journal started

Anyway, ... unless this guy is fscking with us and actually is using DE, the tty terminal characters are too big to get the entire message on a single line.
Indeed some are nearly impossible to get.
This is journalctl output from as large a shell(XTerm) as I can make:

Oct 15 19:05:09 Manjaro16061 ntpd[882]: bind(24) AF_INET6 fe80::cbe4:20f:8652:e917%2#123 flags 0x11 failed: Cannot assign requested addres

Do not have a clue what is remaining part unless konsole is used and font is reduced:

Oct 15 19:05:09 Manjaro16061 ntpd[882]: bind(24) AF_INET6 fe80::cbe4:20f:8652:e917%2#123 flags 0x11 failed: Cannot assign requested address       

Trivial in that case but not for "*-coredump" messages and others that have extended lines.

I have no idea if this is the norm for systemd messages or is Arch/Manjaro specific...

1 Like

@Petja,

[quote="Petja, post:9, topic:13023, full:true"]Terrible when I have no idea what I'm doing..[/quote]Learning for humans involves making mistakes. No big deal. Do not worry about it. ...we all make them and anyone that thinks they do not is suffering from delusions of grandeur, ;).

Petr, would you type
startx
at a virtual terminal("tty") Command Line Interface(CLI) for your "Manjaro" computer laptop and tell us what happens, please?
You can always get to the second tty by pressing three keys at same time:

CTRL+ALT+F2

Then just login.
If "tty" and "CLI" still hurts your head, :slight_smile:, tell me and I will explain it/them.

If you prefer, because the output is a long error message you can post the output.
I hope that will not be the case, however, WHENEVER one makes a post of some output,
Place three backquote marks ``` on a line by themselves before the text one is going to post.
Then after the end of the text place three more backquote marks ``` on a line by themselves.

The difference is, without the backquotes it looks like this(or similar):

resource id: 35382564, major code: 3 (GetWindowAttributes), minor code: 0
[78648.934806] kwin_x11[1094]: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 56364, resource id: 35382564, major code: 14 (GetGeometry), minor code: 0
[78654.260111] kwin_x11[1094]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 60055, resource id: 35418273, major code: 3 (GetWindowAttributes), minor code: 0
[80990.172047] kwin_x11[1094]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 4628, resource id: 35418644, major code: 3 (GetWindowAttributes), minor code: 0
[80990.172094] kwin_x11[1094]: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 4629, resource id: 35418644, major code: 14 (GetGeometry), minor code: 0
[82970.873802] [UFW BLOCK] IN=enp0s10 OUT= MAC=***************** SRC=74.125.196.113 DST=192.168.1.178 LEN=40 TOS=0x00 PREC=0x00 TTL=46 ID=64033 PROTO=TCP SPT=443 DPT=41192 WINDOW=0 RES=0x00 RST URGP=0
[82971.871187] [UFW BLOCK] IN=enp0s10 OUT= MAC=***************** SRC=216.58.193.142 DST=192.168.1.178 LEN=40 TOS=0x00 PREC=0x00 TTL=55 ID=15252 PROTO=TCP SPT=443 DPT=38972 WINDOW=0 RES=0x00 RST URGP=0

and with the backquotes:

 resource id: 35382564, major code: 3 (GetWindowAttributes), minor code: 0
[78648.934806] kwin_x11[1094]: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 56364, resource id: 35382564, major code: 14 (GetGeometry), minor code: 0
[78654.260111] kwin_x11[1094]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 60055, resource id: 35418273, major code: 3 (GetWindowAttributes), minor code: 0
[80990.172047] kwin_x11[1094]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 4628, resource id: 35418644, major code: 3 (GetWindowAttributes), minor code: 0
[80990.172094] kwin_x11[1094]: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 4629, resource id: 35418644, major code: 14 (GetGeometry), minor code: 0
[82970.873802] [UFW BLOCK] IN=enp0s10 OUT= MAC=***************** SRC=74.125.196.113 DST=192.168.1.178 LEN=40 TOS=0x00 PREC=0x00 TTL=46 ID=64033 PROTO=TCP SPT=443 DPT=41192 WINDOW=0 RES=0x00 RST URGP=0 
[82971.871187] [UFW BLOCK] IN=enp0s10 OUT= MAC=***************** SRC=216.58.193.142 DST=192.168.1.178 LEN=40 TOS=0x00 PREC=0x00 TTL=55 ID=15252 PROTO=TCP SPT=443 DPT=38972 WINDOW=0 RES=0x00 RST URGP=0 

One is easily readable by humans and the other is not.
If one wants assistance then post(s) of output(s) must be easily readable by humans, ;).
That is not too much to ask for free assistance is it?

c-ya

FYI: "backquotes" might be known to you as "grave accent" marks.

1 Like

I understand his stress. When I started out with Linux and my system broke, I was hopeless.

Before I made backups before every update cycle or when tinkering with my system I used to be fearful of system breakage.

Now I simply make a full system backup using Clonezilla before every update and that gives me a lot of peace of mind. It took the stress and fear away and has saved my ass/system a few times.

2 Likes

That being said the same stress occurs with cars these day for people who depend on their car to get to work.

Cars have become so technologically advanced and so dependent on electronics and the software that runs on it, that you can't see what's wrong or fix it yourself.

With cars it's too untransparent for consumers, but with Linux you have access to everything on your system, allowing you to figure things out, even if it takes a lot of effort.

They don't get daily system updates yet, despite being "rolling" by their nature.

3 Likes

No not daily updates but they get regular software updates/upgrades usually every service?

classic! :joy:

Thank you all guys as you spent so much time helping me with my issue. I really like Manjaro community and Manjaro itself, it is the most beautiful Linux distribution. Now, it's time to learn to work on it :wink: All the best!

1 Like

Hi everyone! Again the same problem, but I´m sure it´s not caused by wi-fi. Before my laptop stop to boot I changed graphic card driver from bumblebee to nvidia and run command "sudo nvidia-xconfig", then reboot computer. Now laptop stops booting, shows "wl_set_mac_address: error settings MAC addr override"

after command "startx" it shows "(EE) Fatal server error: no screens found, please consult the The X.Org Foundation support for help (EE) Please also check the log file at "/var/log/Xorg.0.log for additional information (EE) Server terminated with error (1) Closing log file
xinit:giving up
xinit: unable to connect to X server: connection refused
xinit: server error

Boot to prompt [1] and fix your graphics at prompt using mhwd commands [2].

[1] - to boot to prompt
At grub menu, press 'e' at Manjaro entry.
Arrow down to linux line
Arrow right past 'quiet' and 'splash'
Backspace to remove 'quiet' and 'splash' (careful not to remove 'rw')
Add '3' (no appostrophes)
F10 or 'ctl' + 'x' to boot
Login in with password.

[2] remove 'not applicable' drivers first before installing correct driver
and don't forget, after mhwd commands to
mhwd-gpu --setgl nvidia
mhwd-gpu --setxorg

1 Like

Forum kindly sponsored by