[arch-general] systemd problems
Hello, I've got problems with bluetooth (service does not start), which seem to be caused by systemd problems, as several services are "dead". Output of info --test´ is at https://dpaste.de/LC2h Kind regards Peter
Hi Peter, On 2016-10-13 08:37:13 (+0200), Peter Nabbefeld wrote:
Hello,
I've got problems with bluetooth (service does not start), which seem to be caused by systemd problems, as several services are "dead".
you might want to check the log output of those services then.
Output of info --test´ is at https://dpaste.de/LC2h
That's not very helpful (especially now that the formatting is gone) or specific (enough). Try (as root): systemctl --all --full |grep failed to see which services failed. Check their status: systemctl status --all --full $name_of_service [ $name_of_service ] Attach journalctl to the service (in another shell instance), before trying to restart it: journalctl -f -u $name_of_service then: systemctl restart $name_of_service The above outputs should give you enough information to track down the problem (hopefully).
Kind regards Peter
Best, David -- https://sleepmap.de
Hi David, Am 13.10.2016 um 11:35 schrieb David Runge:
Hi Peter,
On 2016-10-13 08:37:13 (+0200), Peter Nabbefeld wrote:
Hello,
I've got problems with bluetooth (service does not start), which seem to be caused by systemd problems, as several services are "dead".
you might want to check the log output of those services then.
Output of info --test´ is at https://dpaste.de/LC2h
That's not very helpful (especially now that the formatting is gone) or specific (enough).
This pastebin is a bit tricky: The "text" output format shifts everything to the left. If You klick on "View raw", it's correctly formatted. However, I now noticed there's a direct address to the raw, formatted data: https://dpaste.de/LC2h/raw
Try (as root):
systemctl --all --full |grep failed
to see which services failed.
No results shown. Tried with systemctl --all --full |grep "not-found" then, gettings these results: apparmor.service auditd.service display-manager.service iscsid.service plymouth-quit-wait.service plymouth-start.service syslog.service As these are not found, I guess these are outdated and should be removed. "systemctl disable" does not work, as the services itself don't exist - how can I remove those sevices from systemd?
[...]
Kind regards Peter
Best, David
Hey again, On 2016-10-13 12:01:42 (+0200), Peter Nabbefeld wrote:
I've got problems with bluetooth (service does not start), which seem to be caused by systemd problems, as several services are "dead". you might want to check the log output of those services then. What does bluetooth/bluetoothd service log? journalctl -f -u bluetoothd -u bluetooth
Are all dependencies installed to make it run? Have you read the wiki: https://wiki.archlinux.org/index.php/Bluetooth ?
https://dpaste.de/LC2h/raw You seem to have initialized bluetooth hardware. The bluetooth/bluetoothd services don't seem to run though.
No results shown. That means, no services have failed. Why do you think, your bluetooth service has failed?
Tried with systemctl --all --full |grep "not-found" then, gettings these results:
apparmor.service auditd.service display-manager.service iscsid.service plymouth-quit-wait.service plymouth-start.service syslog.service Those are pretty irrelevant. What systemd can't find, it won't start. ;-)
I'm still a bit unsure, what the exact issue is. Best, David -- https://sleepmap.de
Hello David, Am 13.10.2016 um 13:04 schrieb David Runge:
Hey again,
On 2016-10-13 12:01:42 (+0200), Peter Nabbefeld wrote:
I've got problems with bluetooth (service does not start), which seem to be caused by systemd problems, as several services are "dead". you might want to check the log output of those services then. What does bluetooth/bluetoothd service log? journalctl -f -u bluetoothd -u bluetooth
Okt 13 05:05:47 tuchola systemd[1]: Starting Bluetooth service... Okt 13 05:05:48 tuchola bluetoothd[485]: Bluetooth daemon 5.41 Okt 13 05:05:48 tuchola systemd[1]: Started Bluetooth service. Okt 13 05:05:48 tuchola bluetoothd[485]: Starting SDP server Okt 13 05:05:48 tuchola bluetoothd[485]: Bluetooth management interface 1.12 initialized Okt 13 05:05:48 tuchola bluetoothd[485]: Failed to obtain handles for "Service Changed" characteristic Okt 13 05:05:48 tuchola bluetoothd[485]: Sap driver initialization failed. Okt 13 05:05:48 tuchola bluetoothd[485]: sap-server: Operation not permitted (1) Okt 13 05:06:45 tuchola bluetoothd[485]: Endpoint registered: sender=:1.25 path=/MediaEndpoint/A2DPSource Okt 13 05:06:45 tuchola bluetoothd[485]: Endpoint registered: sender=:1.25 path=/MediaEndpoint/A2DPSink
Are all dependencies installed to make it run? Have you read the wiki: https://wiki.archlinux.org/index.php/Bluetooth ?
Yes, Ihad bluetooth up and running before. I only needed to downgrad bluez* from version 5.42 to 5.41 because it has a known bug rejecting file trnsmission originating from a mobile phone to my linux laptop.
https://dpaste.de/LC2h/raw You seem to have initialized bluetooth hardware. The bluetooth/bluetoothd services don't seem to run though.
No results shown. That means, no services have failed. Why do you think, your bluetooth service has failed?
blueman-applet doesn't show any bluetooth devices and doesn't even search for those.
Tried with systemctl --all --full |grep "not-found" then, gettings these results:
apparmor.service auditd.service display-manager.service iscsid.service plymouth-quit-wait.service plymouth-start.service syslog.service Those are pretty irrelevant. What systemd can't find, it won't start. ;-)
Can I remove those, however, somehow?
I'm still a bit unsure, what the exact issue is.
Best, David
Kind regards Peter
Okt 13 05:05:47 tuchola systemd[1]: Starting Bluetooth service... Okt 13 05:05:48 tuchola bluetoothd[485]: Bluetooth daemon 5.41 Okt 13 05:05:48 tuchola systemd[1]: Started Bluetooth service. Okt 13 05:05:48 tuchola bluetoothd[485]: Starting SDP server Okt 13 05:05:48 tuchola bluetoothd[485]: Bluetooth management interface 1.12 initialized Okt 13 05:05:48 tuchola bluetoothd[485]: Failed to obtain handles for "Service Changed" characteristic Okt 13 05:05:48 tuchola bluetoothd[485]: Sap driver initialization failed. Okt 13 05:05:48 tuchola bluetoothd[485]: sap-server: Operation not permitted (1) Okt 13 05:06:45 tuchola bluetoothd[485]: Endpoint registered: sender=:1.25 path=/MediaEndpoint/A2DPSource Okt 13 05:06:45 tuchola bluetoothd[485]: Endpoint registered: sender=:1.25 path=/MediaEndpoint/A2DPSink I'm also getting the Sap driver errors. They don't seem to be a problem
Hello Peter, On 2016-10-13 13:33:27 (+0200), Peter Nabbefeld wrote: though. If you want to disable that error message, you can follow the instructions in the following bug report: https://bugs.archlinux.org/task/41247 As there's endpoints connected (with pulseaudio), you should also be able to find other devices through your bluetooth adapter. Works fine here at least (and also seems to work on your side).
Are all dependencies installed to make it run? Have you read the wiki: https://wiki.archlinux.org/index.php/Bluetooth ?
Yes, Ihad bluetooth up and running before. I only needed to downgrad bluez* from version 5.42 to 5.41 because it has a known bug rejecting file trnsmission originating from a mobile phone to my linux laptop.
Yeah, transmission is painful. I never use bluetooth for that. It's unsafe and slow.
blueman-applet doesn't show any bluetooth devices and doesn't even search for those. Hm, does it show your builtin hardware in the "Adapter" menu? If so, you're all set to go, just have to make your computer visible (if needed) and get your device in pairing mode. Just tried it, and it works.
apparmor.service auditd.service display-manager.service iscsid.service plymouth-quit-wait.service plymouth-start.service syslog.service Those are pretty irrelevant. What systemd can't find, it won't start. ;-)
Can I remove those, however, somehow? I would recommend against it ;) They are linked in some services shipped with systemd. As I wrote before: If they're not there, they won't be started.
display-manager.service however will be a symlink to whatever display manager you use (lightdm, gdm, etc.) though and therefore is a kind of placeholder. There's no need to change anything about them. Best, David -- https://sleepmap.de
Hello David, Am 13.10.2016 um 14:51 schrieb David Runge:
Hello Peter,
[...]
blueman-applet doesn't show any bluetooth devices and doesn't even search for those. Hm, does it show your builtin hardware in the "Adapter" menu? If so, you're all set to go, just have to make your computer visible (if needed) and get your device in pairing mode. Just tried it, and it works.
seems most of the problems arose from a device name change I didn't notice, so other devices couldn't detect the original device name. However, pairing is lost now - where is such configuration data usually stored (so I can make a backup next time before doing any changes)?
[...]
Best, David
Kind regards Peter
participants (2)
-
David Runge
-
Peter Nabbefeld