Nach Update: Bildschirm friert nach einiger Zeit ein, nur Maus beweglich

Siduction Forum > Installation - Support

<< < (3/4) > >>

melmarker:
ok - wait-online for every manager make sense if ${HOME} is on a network-device - i forget, sorry 8)

tomsiduction:
Hello an thank you

The screen-freeze still appears.

The following things I see:

May be this has to do with the problem or not

1. service ntp status
ends up with:

--- Code: --- kernel reports TIME_ERROR: 0x2041: Clock
ntpd[30502]: bind(24) AF_INET6 fe80::e2ca:94ff:fec2:4dd1%3#123 flags 0x11 failed: Cannot assign
ntpd[30502]: unable to create socket on wlp10s0 (6) for fe80::e2ca:94ff:fec2:4dd1%3#123

--- End code ---
2. Even after

--- Code: --- systemctl disable NetworkManager-wait-online.service

--- End code ---
I get a

systemd-analyze blame

--- Code: --- 6.932s NetworkManager-wait-online.service

--- End code ---

Q: How can i permanent disable that service?

3. The time the screen freezes (or just has freezed) I get the following message

--- Code: ---Dez 21 13:39:06 siduction org.kde.KScreen[2769]: kscreen.xcb.helper: RRNotify_OutputProperty (ignored)
Dez 21 13:39:06 siduction org.kde.KScreen[2769]: kscreen.xcb.helper: Output: 66
Dez 21 13:39:06 siduction org.kde.KScreen[2769]: kscreen.xcb.helper: Property: Backlight
Dez 21 13:39:06 siduction org.kde.KScreen[2769]: kscreen.xcb.helper: State (newValue, Deleted): 0
Dez 21 13:39:06 siduction org.kde.KScreen[2769]: kscreen.xcb.helper: RRNotify_OutputProperty (ignored)
Dez 21 13:39:06 siduction org.kde.KScreen[2769]: kscreen.xcb.helper: Output: 66
Dez 21 13:39:06 siduction org.kde.KScreen[2769]: kscreen.xcb.helper: Property: Backlight
Dez 21 13:39:06 siduction org.kde.KScreen[2769]: kscreen.xcb.helper: State (newValue, Deleted): 0
Dez 21 13:39:06 siduction org.kde.KScreen[2769]: kscreen.xcb.helper: RRNotify_OutputProperty (ignored)
Dez 21 13:39:06 siduction org.kde.KScreen[2769]: kscreen.xcb.helper: Output: 66
Dez 21 13:39:06 siduction org.kde.KScreen[2769]: kscreen.xcb.helper: Property: Backlight
Dez 21 13:39:06 siduction org.kde.KScreen[2769]: kscreen.xcb.helper: State (newValue, Deleted): 0
Dez 21 13:39:06 siduction org.kde.KScreen[2769]: kscreen.xcb.helper: RRNotify_OutputProperty (ignored)
Dez 21 13:39:06 siduction org.kde.KScreen[2769]: kscreen.xcb.helper: Output: 66
Dez 21 13:39:06 siduction org.kde.KScreen[2769]: kscreen.xcb.helper: Property: Backlight
Dez 21 13:39:06 siduction org.kde.KScreen[2769]: kscreen.xcb.helper: State (newValue, Deleted): 0
Dez 21 13:39:06 siduction org.kde.KScreen[2769]: kscreen.xcb.helper: RRNotify_OutputProperty (ignored)
Dez 21 13:39:06 siduction org.kde.KScreen[2769]: kscreen.xcb.helper: Output: 66
Dez 21 13:39:06 siduction org.kde.KScreen[2769]: kscreen.xcb.helper: Property: Backlight
Dez 21 13:39:06 siduction org.kde.KScreen[2769]: kscreen.xcb.helper: State (newValue, Deleted): 0

--- End code ---

Thank you in advance

piper:
I seen a bug posted at redhat

--- Code: ---NetworkManager.service starts on boot, regardless of disabling the systemd unit.

disabled does not mean that a service cannot start. If another service requires NM.service, it will still be started. If you don't want it to ever start, you need to mask it.
--- End code ---

https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=28b97f02f64ecf94e22c8929dfd0ba64151bd9d3

Some people got around this by doing

--- Code: ---systemctl disable NetworkManager.service
systemctl disable NetworkManager-wait-online.service
--- End code ---

This was back in 2017-11-15, so not sure if it still matters

tomsiduction:
Thank you

Just a question:

--- Code: ---systemctl disable NetworkManager.service
systemctl disable NetworkManager-wait-online.service

--- End code ---

will not disable the Networkmanager permanently?

Regards

melmarker:
@tomsiduction - i would suggest only to disable the wait-online service - it might be that n-m is your main networking service, so disabling that would be funny but not cool. :)

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version