problem detected

AmigaOne X5000 platform specific issues related to Linux only.

problem detected

Postby kilaueabart » Fri Mar 22, 2019 11:29 pm

It seems to me that as long as I have been running Ubuntu, I have gotten, right away, a notice on the order of, "Sorry, Ubuntu 16.04 has experienced an internal error." I never worried about this much. If I checked for details it would be something about Bluetooth.

For a couple weeks now, I have been getting another, more immediate, notice: "System program problem detected." The details are given as
Code: Select all
polkit.subject-pid: 5828
polkit.caller-pid: 6313
Action: com.ubuntu.appart.appart-gtk-ret

I have not noticed any new problems aside from this notice. Is it something I should look into further?

I used to get the first message mentioning Bluetooth in the details even when I had given up trying to make my dongle work and stopped plugging it in. But lately I tried again, successfuly, but still the strange details. I attach pictures in case anybody has any idea whether they mean anything important.
internalerror1.png
Attachments
internalerror2.png
(Tried various ways to get these side by side, but now I'm not sure either one will show up.)
User avatar
kilaueabart
 
Posts: 593
Joined: Mon Mar 05, 2012 3:36 am

Re: problem detected

Postby xeno74 » Sat Mar 23, 2019 6:54 am

The bluetooth daemon crashed. I don’t know why. Have you seen any other error messages? You can look in the log file /var/log/syslog because of the error messages.
http://www.amigalinux.org
http://www.supertuxkart-amiga.de

Running Linux on AmigaONEs can require some tinkering.
User avatar
xeno74
 
Posts: 4946
Joined: Fri Mar 23, 2012 8:58 am

Re: problem detected

Postby kilaueabart » Sun Mar 24, 2019 1:29 am

xeno74 wrote:The bluetooth daemon crashed. I don’t know why. Have you seen any other error messages? You can look in the log file /var/log/syslog because of the error messages.

Syslog looks weird. Mostly this, over and over again:

Mar 23 09:23:15 X5000 systemd[1]: Time has been changed
Mar 23 09:23:15 X5000 rsyslogd-2007: action 'action 10' suspended, next retry is Sat Mar 23 09:24:45 2019 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
Mar 23 09:29:54 X5000 systemd[1]: Time has been changed
Mar 23 09:29:54 X5000 systemd[5658]: Time has been changed
Mar 23 09:29:54 X5000 rsyslogd-2007: action 'action 10' suspended, next retry is Sat Mar 23 09:31:24 2019 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
Mar 23 09:38:20 X5000 systemd[5658]: Time has been changed

I tried searching "blue" and "blu." Not found.

Meanwhile, as I noted, Bluetooth is working fine:
bluetooth.png
That brings up another question. Is there any way of finding out what "9C-30-5B-0F-64-EC" and "KSMT" are? Or which of my Tiles is referenced? (BLKBOX POP360 is really a speaker, not a microphone, but I can play music on it from Ubuntu now.)
User avatar
kilaueabart
 
Posts: 593
Joined: Mon Mar 05, 2012 3:36 am

Re: problem detected

Postby kilaueabart » Tue Mar 26, 2019 12:21 am

xeno74 wrote:The bluetooth daemon crashed. I don’t know why. Have you seen any other error messages? You can look in the log file /var/log/syslog because of the error messages.

I looked again, the next day, and found lots of bluetooth stuff that doesn't tell me anything:

Mar 23 07:47:45 X5000 bluetoothd[4479]: Bluetooth daemon 5.37
Mar 23 07:47:47 X5000 systemd[1]: Started Bluetooth service.
Mar 23 07:47:47 X5000 bluetoothd[4479]: Starting SDP server
Mar 23 07:47:48 X5000 bluetoothd[4479]: Failed to obtain handles for "Service Changed" characteristic
Mar 23 07:47:48 X5000 bluetoothd[4479]: Not enough free handles to register service
Mar 23 07:47:48 X5000 bluetoothd[4479]: Error adding Link Loss service
Mar 23 07:47:48 X5000 bluetoothd[4479]: Not enough free handles to register service
Mar 23 07:47:48 X5000 bluetoothd[4479]: message repeated 2 times: [ Not enough free handles to register service]
Mar 23 07:47:48 X5000 bluetoothd[4479]: Current Time Service could not be registered
Mar 23 07:47:48 X5000 bluetoothd[4479]: gatt-time-server: Input/output error (5)
Mar 23 07:47:48 X5000 bluetoothd[4479]: Not enough free handles to register service
Mar 23 07:47:48 X5000 bluetoothd[4479]: Not enough free handles to register service
Mar 23 07:47:48 X5000 bluetoothd[4479]: Sap driver initialization failed.
Mar 23 07:47:48 X5000 bluetoothd[4479]: sap-server: Operation not permitted (1)
Mar 23 07:47:52 X5000 NetworkManager[4562]: <info> [1553352472.2767] Loaded device plugin: NMBluezManager (/usr/lib/powerpc-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so)
Mar 23 07:47:52 X5000 NetworkManager[4562]: <info> [1553352472.6001] bluez: use BlueZ version 5
Mar 23 07:48:17 X5000 bluetoothd[4479]: Endpoint registered: sender=:1.49 path=/MediaEndpoint/A2DPSource
Mar 23 07:48:17 X5000 bluetoothd[4479]: Endpoint registered: sender=:1.49 path=/MediaEndpoint/A2DPSink

Mar 24 08:04:34 X5000 kernel: [ 46.334245] Bluetooth: RFCOMM TTY layer initialized
Mar 24 08:04:34 X5000 kernel: [ 46.334257] Bluetooth: RFCOMM socket layer initialized
Mar 24 08:04:34 X5000 kernel: [ 46.334266] Bluetooth: RFCOMM ver 1.11
Mar 24 08:04:38 X5000 dbus[4506]: [system] Activating service name='org.blueman.Mechanism' (using servicehelper)
Mar 24 08:04:39 X5000 org.blueman.Mechanism[4506]: Failed to connect to Mir: Failed to connect to server socket: No such file or directory
Mar 24 08:04:39 X5000 org.blueman.Mechanism[4506]: Unable to init server: Could not connect: Connection refused
Mar 24 08:04:39 X5000 org.blueman.Mechanism[4506]: Failed to connect to Mir: Failed to connect to server socket: No such file or directory
Mar 24 08:04:39 X5000 org.blueman.Mechanism[4506]: Unable to init server: Could not connect: Connection refused
Mar 24 08:04:39 X5000 blueman-mechanism: Starting blueman-mechanism
Mar 24 08:04:39 X5000 dbus[4506]: [system] Successfully activated service 'org.blueman.Mechanism'
Mar 24 08:04:39 X5000 org.blueman.Mechanism[4506]: (blueman-mechanism:6091): Gtk-CRITICAL **: gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed
Mar 24 08:04:39 X5000 blueman-mechanism: loading RfKill
Mar 24 08:04:39 X5000 blueman-mechanism: loading Network
Mar 24 08:04:39 X5000 blueman-mechanism: loading Rfcomm
Mar 24 08:04:39 X5000 blueman-mechanism: loading Ppp
Mar 24 08:05:09 X5000 blueman-mechanism: Exiting

I repeat: Bluetooth seems to be working OK. I'm more concerned about the System program problem, which seems to be related. Apport.log has this from yesterday:

ERROR: apport (pid 6661) Sun Mar 24 15:18:22 2019: called for pid 4485, signal 11, core limit 0, dump mode 1
ERROR: apport (pid 6661) Sun Mar 24 15:18:22 2019: executable: /usr/lib/bluetooth/bluetoothd (command line "/usr/lib/bluetooth/bluetoothd")
ERROR: apport (pid 6661) Sun Mar 24 15:18:22 2019: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment
ERROR: apport (pid 6661) Sun Mar 24 15:18:22 2019: wrote report /var/crash/_usr_lib_bluetooth_bluetoothd.0.crash
ERROR: apport (pid 15548) Sun Mar 24 21:39:59 2019: called for pid 4483, signal 11, core limit 0, dump mode 1
ERROR: apport (pid 15548) Sun Mar 24 21:39:59 2019: executable: /usr/lib/bluetooth/bluetoothd (command line "/usr/lib/bluetooth/bluetoothd")
ERROR: apport (pid 15548) Sun Mar 24 21:39:59 2019: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment
ERROR: apport (pid 15548) Sun Mar 24 21:39:59 2019: apport: report /var/crash/_usr_lib_bluetooth_bluetoothd.0.crash already exists and unseen, doing nothing to avoid disk usage DoS

The crash log is 13,906 lines long. I skimmed a few thousand then jumped to the end which has a lot of lines apparently copied out of today's syslog about bluetooth.
User avatar
kilaueabart
 
Posts: 593
Joined: Mon Mar 05, 2012 3:36 am


Return to Platform: AmigaOne X5000 - Linux Only

Who is online

Users browsing this forum: No registered users and 3 guests