Re: [arch-general] systemd problems

2016-10-13 Thread Peter Nabbefeld
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

Re: [arch-general] systemd problems

2016-10-13 Thread David Runge
Hello Peter, On 2016-10-13 13:33:27 (+0200), Peter Nabbefeld wrote: > 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

Re: [arch-general] systemd problems

2016-10-13 Thread Peter Nabbefeld
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

Re: [arch-general] systemd problems

2016-10-13 Thread 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

Re: [arch-general] systemd problems

2016-10-13 Thread Peter Nabbefeld
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

Re: [arch-general] systemd problems

2016-10-13 Thread 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