How to find out which application have a problem
0
It'a a couple of days that each time I boot up Ubuntu (18.04) I get an alert window that claims that a system program have had a problem and the only two options given to me is to send a notification or close the alert.
Since there's no clue to which application have had the problem and I am a so not-expert of Linux at all, I would like to know if there's a way to find out which application is in order to try to solve the problem in some way.
Thanks everybody
Edit
So, I tryed to see in /var/crash/ but there's only two elements there and both of them are from three days ago, so nothing to do with the daily problem I suppose. So I tryed the journal option as suggested but the result doesn't mean anything to me due to my incomparable ignorance. I post here part of it, the bit I think is relevant due to the timecode, hoping someone can understand it and explain it to me.
mar 14 08:55:03 ezabba-Aspire kernel: tpm_crb MSFT0101:00: can't request region for resour
mar 14 08:55:03 ezabba-Aspire kernel: Problem loading UEFI:db X.509 certificate (-65)
mar 14 08:55:03 ezabba-Aspire kernel: Problem loading UEFI:db X.509 certificate (-65)
mar 14 08:55:03 ezabba-Aspire kernel: Couldn't get size: 0x800000000000000e
mar 14 08:55:31 ezabba-Aspire kernel: dell_smbios: Unable to run on non-Dell system
mar 14 08:55:31 ezabba-Aspire kernel: [drm:construct [amdgpu]] *ERROR* construct: Invalid
mar 14 08:55:31 ezabba-Aspire kernel: [drm:hwss_wait_for_blank_complete [amdgpu]] *ERROR*
mar 14 08:55:31 ezabba-Aspire kernel: kfd kfd: error getting iommu info. is the iommu enab
mar 14 08:55:31 ezabba-Aspire kernel: kfd kfd: Error initializing iommuv2 for device 1002:
mar 14 08:55:31 ezabba-Aspire kernel: kfd kfd: device 1002:9874 NOT added due to errors
mar 14 08:55:31 ezabba-Aspire kernel: amdgpu: [powerplay] Voltage value looks like a Leaka
mar 14 08:55:31 ezabba-Aspire kernel: amdgpu: [powerplay] Voltage value looks like a Leaka
mar 14 08:55:31 ezabba-Aspire kernel: amdgpu: [powerplay] Voltage value looks like a Leaka
mar 14 08:55:31 ezabba-Aspire kernel: amdgpu: [powerplay] Voltage value looks like a Leaka
mar 14 08:55:31 ezabba-Aspire kernel: amdgpu: [powerplay] Voltage value looks like a Leaka
mar 14 08:55:31 ezabba-Aspire kernel: amdgpu: [powerplay] Voltage value looks like a Leaka
mar 14 08:55:31 ezabba-Aspire kernel: amdgpu: [powerplay] Voltage value looks like a Leaka
mar 14 08:55:31 ezabba-Aspire kernel: [drm:dc_create [amdgpu]] *ERROR* DC: Number of conne
mar 14 08:55:29 ezabba-Aspire systemd-backlight[815]: Failed to get backlight or LED devic
mar 14 08:55:29 ezabba-Aspire systemd-backlight[817]: Failed to get backlight or LED devic
mar 14 08:55:29 ezabba-Aspire systemd[1]: Failed to start Load/Save Screen Backlight Brigh
mar 14 08:55:29 ezabba-Aspire systemd[1]: Failed to start Load/Save Screen Backlight Brigh
mar 14 08:55:40 ezabba-Aspire bluetoothd[993]: Loading LTKs timed out for hci0
mar 14 08:55:48 ezabba-Aspire wpa_supplicant[1027]: dbus: wpa_dbus_get_object_properties:
mar 14 08:55:48 ezabba-Aspire wpa_supplicant[1027]: dbus: Failed to construct signal
mar 14 08:56:15 ezabba-Aspire spice-vdagent[1517]: Cannot access vdagent virtio channel /d
mar 14 08:57:19 ezabba-Aspire pulseaudio[1918]: [pulseaudio] backend-ofono.c: Failed to re
mar 14 08:57:25 ezabba-Aspire spice-vdagent[2035]: Cannot access vdagent virtio channel /d
lines 1-29...skipping...
-- Logs begin at Sat 2018-11-10 14:10:14 CET, end at Thu 2019-03-14 23:39:02 CET. --
mar 14 08:55:03 ezabba-Aspire kernel: tpm_crb MSFT0101:00: can't request region for resource [mem 0xbfbba000-0xbfbbdfff]
mar 14 08:55:03 ezabba-Aspire kernel: Problem loading UEFI:db X.509 certificate (-65)
mar 14 08:55:03 ezabba-Aspire kernel: Problem loading UEFI:db X.509 certificate (-65)
mar 14 08:55:03 ezabba-Aspire kernel: Couldn't get size: 0x800000000000000e
mar 14 08:55:31 ezabba-Aspire kernel: dell_smbios: Unable to run on non-Dell system
mar 14 08:55:31 ezabba-Aspire kernel: [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:2!
mar 14 08:55:31 ezabba-Aspire kernel: [drm:hwss_wait_for_blank_complete [amdgpu]] *ERROR* DC: failed to blank crtc!
mar 14 08:55:31 ezabba-Aspire kernel: kfd kfd: error getting iommu info. is the iommu enabled?
mar 14 08:55:31 ezabba-Aspire kernel: kfd kfd: Error initializing iommuv2 for device 1002:9874
mar 14 08:55:31 ezabba-Aspire kernel: kfd kfd: device 1002:9874 NOT added due to errors
mar 14 08:55:31 ezabba-Aspire kernel: amdgpu: [powerplay] Voltage value looks like a Leakage ID but it's not patched
mar 14 08:55:31 ezabba-Aspire kernel: amdgpu: [powerplay] Voltage value looks like a Leakage ID but it's not patched
mar 14 08:55:31 ezabba-Aspire kernel: amdgpu: [powerplay] Voltage value looks like a Leakage ID but it's not patched
mar 14 08:55:31 ezabba-Aspire kernel: amdgpu: [powerplay] Voltage value looks like a Leakage ID but it's not patched
mar 14 08:55:31 ezabba-Aspire kernel: amdgpu: [powerplay] Voltage value looks like a Leakage ID but it's not patched
mar 14 08:55:31 ezabba-Aspire kernel: amdgpu: [powerplay] Voltage value looks like a Leakage ID but it's not patched
mar 14 08:55:31 ezabba-Aspire kernel: amdgpu: [powerplay] Voltage value looks like a Leakage ID but it's not patched
mar 14 08:55:31 ezabba-Aspire kernel: [drm:dc_create [amdgpu]] *ERROR* DC: Number of connectors is zero!
mar 14 08:55:29 ezabba-Aspire systemd-backlight[815]: Failed to get backlight or LED device 'backlight:acpi_video1': No such device
mar 14 08:55:29 ezabba-Aspire systemd-backlight[817]: Failed to get backlight or LED device 'backlight:acpi_video0': No such device
mar 14 08:55:29 ezabba-Aspire systemd[1]: Failed to start Load/Save Screen Backlight Brightness of backlight:acpi_video1.
mar 14 08:55:29 ezabba-Aspire systemd[1]: Failed to start Load/Save Screen Backlight Brightness of backlight:acpi_video0.
mar 14 08:55:40 ezabba-Aspire bluetoothd[993]: Loading LTKs timed out for hci0
mar 14 08:55:48 ezabba-Aspire wpa_supplicant[1027]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (none) none
mar 14 08:55:48 ezabba-Aspire wpa_supplicant[1027]: dbus: Failed to construct signal
mar 14 08:56:15 ezabba-Aspire spice-vdagent[1517]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
mar 14 08:57:19 ezabba-Aspire pulseaudio[1918]: [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.o
mar 14 08:57:25 ezabba-Aspire spice-vdagent[2035]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
mar 14 08:57:46 ezabba-Aspire gnome-session-binary[1390]: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop
mar 14 08:57:46 ezabba-Aspire gnome-session-binary[1390]: CRITICAL: We failed, but the fail whale is dead. Sorry....
system
asked Mar 14 at 8:31
luzzucluzzuc
363
add a comment |
0
It'a a couple of days that each time I boot up Ubuntu (18.04) I get an alert window that claims that a system program have had a problem and the only two options given to me is to send a notification or close the alert.
Since there's no clue to which application have had the problem and I am a so not-expert of Linux at all, I would like to know if there's a way to find out which application is in order to try to solve the problem in some way.
Thanks everybody
Edit
So, I tryed to see in /var/crash/ but there's only two elements there and both of them are from three days ago, so nothing to do with the daily problem I suppose. So I tryed the journal option as suggested but the result doesn't mean anything to me due to my incomparable ignorance. I post here part of it, the bit I think is relevant due to the timecode, hoping someone can understand it and explain it to me.
mar 14 08:55:03 ezabba-Aspire kernel: tpm_crb MSFT0101:00: can't request region for resour
mar 14 08:55:03 ezabba-Aspire kernel: Problem loading UEFI:db X.509 certificate (-65)
mar 14 08:55:03 ezabba-Aspire kernel: Problem loading UEFI:db X.509 certificate (-65)
mar 14 08:55:03 ezabba-Aspire kernel: Couldn't get size: 0x800000000000000e
mar 14 08:55:31 ezabba-Aspire kernel: dell_smbios: Unable to run on non-Dell system
mar 14 08:55:31 ezabba-Aspire kernel: [drm:construct [amdgpu]] *ERROR* construct: Invalid
mar 14 08:55:31 ezabba-Aspire kernel: [drm:hwss_wait_for_blank_complete [amdgpu]] *ERROR*
mar 14 08:55:31 ezabba-Aspire kernel: kfd kfd: error getting iommu info. is the iommu enab
mar 14 08:55:31 ezabba-Aspire kernel: kfd kfd: Error initializing iommuv2 for device 1002:
mar 14 08:55:31 ezabba-Aspire kernel: kfd kfd: device 1002:9874 NOT added due to errors
mar 14 08:55:31 ezabba-Aspire kernel: amdgpu: [powerplay] Voltage value looks like a Leaka
mar 14 08:55:31 ezabba-Aspire kernel: amdgpu: [powerplay] Voltage value looks like a Leaka
mar 14 08:55:31 ezabba-Aspire kernel: amdgpu: [powerplay] Voltage value looks like a Leaka
mar 14 08:55:31 ezabba-Aspire kernel: amdgpu: [powerplay] Voltage value looks like a Leaka
mar 14 08:55:31 ezabba-Aspire kernel: amdgpu: [powerplay] Voltage value looks like a Leaka
mar 14 08:55:31 ezabba-Aspire kernel: amdgpu: [powerplay] Voltage value looks like a Leaka
mar 14 08:55:31 ezabba-Aspire kernel: amdgpu: [powerplay] Voltage value looks like a Leaka
mar 14 08:55:31 ezabba-Aspire kernel: [drm:dc_create [amdgpu]] *ERROR* DC: Number of conne
mar 14 08:55:29 ezabba-Aspire systemd-backlight[815]: Failed to get backlight or LED devic
mar 14 08:55:29 ezabba-Aspire systemd-backlight[817]: Failed to get backlight or LED devic
mar 14 08:55:29 ezabba-Aspire systemd[1]: Failed to start Load/Save Screen Backlight Brigh
mar 14 08:55:29 ezabba-Aspire systemd[1]: Failed to start Load/Save Screen Backlight Brigh
mar 14 08:55:40 ezabba-Aspire bluetoothd[993]: Loading LTKs timed out for hci0
mar 14 08:55:48 ezabba-Aspire wpa_supplicant[1027]: dbus: wpa_dbus_get_object_properties:
mar 14 08:55:48 ezabba-Aspire wpa_supplicant[1027]: dbus: Failed to construct signal
mar 14 08:56:15 ezabba-Aspire spice-vdagent[1517]: Cannot access vdagent virtio channel /d
mar 14 08:57:19 ezabba-Aspire pulseaudio[1918]: [pulseaudio] backend-ofono.c: Failed to re
mar 14 08:57:25 ezabba-Aspire spice-vdagent[2035]: Cannot access vdagent virtio channel /d
lines 1-29...skipping...
-- Logs begin at Sat 2018-11-10 14:10:14 CET, end at Thu 2019-03-14 23:39:02 CET. --
mar 14 08:55:03 ezabba-Aspire kernel: tpm_crb MSFT0101:00: can't request region for resource [mem 0xbfbba000-0xbfbbdfff]
mar 14 08:55:03 ezabba-Aspire kernel: Problem loading UEFI:db X.509 certificate (-65)
mar 14 08:55:03 ezabba-Aspire kernel: Problem loading UEFI:db X.509 certificate (-65)
mar 14 08:55:03 ezabba-Aspire kernel: Couldn't get size: 0x800000000000000e
mar 14 08:55:31 ezabba-Aspire kernel: dell_smbios: Unable to run on non-Dell system
mar 14 08:55:31 ezabba-Aspire kernel: [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:2!
mar 14 08:55:31 ezabba-Aspire kernel: [drm:hwss_wait_for_blank_complete [amdgpu]] *ERROR* DC: failed to blank crtc!
mar 14 08:55:31 ezabba-Aspire kernel: kfd kfd: error getting iommu info. is the iommu enabled?
mar 14 08:55:31 ezabba-Aspire kernel: kfd kfd: Error initializing iommuv2 for device 1002:9874
mar 14 08:55:31 ezabba-Aspire kernel: kfd kfd: device 1002:9874 NOT added due to errors
mar 14 08:55:31 ezabba-Aspire kernel: amdgpu: [powerplay] Voltage value looks like a Leakage ID but it's not patched
mar 14 08:55:31 ezabba-Aspire kernel: amdgpu: [powerplay] Voltage value looks like a Leakage ID but it's not patched
mar 14 08:55:31 ezabba-Aspire kernel: amdgpu: [powerplay] Voltage value looks like a Leakage ID but it's not patched
mar 14 08:55:31 ezabba-Aspire kernel: amdgpu: [powerplay] Voltage value looks like a Leakage ID but it's not patched
mar 14 08:55:31 ezabba-Aspire kernel: amdgpu: [powerplay] Voltage value looks like a Leakage ID but it's not patched
mar 14 08:55:31 ezabba-Aspire kernel: amdgpu: [powerplay] Voltage value looks like a Leakage ID but it's not patched
mar 14 08:55:31 ezabba-Aspire kernel: amdgpu: [powerplay] Voltage value looks like a Leakage ID but it's not patched
mar 14 08:55:31 ezabba-Aspire kernel: [drm:dc_create [amdgpu]] *ERROR* DC: Number of connectors is zero!
mar 14 08:55:29 ezabba-Aspire systemd-backlight[815]: Failed to get backlight or LED device 'backlight:acpi_video1': No such device
mar 14 08:55:29 ezabba-Aspire systemd-backlight[817]: Failed to get backlight or LED device 'backlight:acpi_video0': No such device
mar 14 08:55:29 ezabba-Aspire systemd[1]: Failed to start Load/Save Screen Backlight Brightness of backlight:acpi_video1.
mar 14 08:55:29 ezabba-Aspire systemd[1]: Failed to start Load/Save Screen Backlight Brightness of backlight:acpi_video0.
mar 14 08:55:40 ezabba-Aspire bluetoothd[993]: Loading LTKs timed out for hci0
mar 14 08:55:48 ezabba-Aspire wpa_supplicant[1027]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (none) none
mar 14 08:55:48 ezabba-Aspire wpa_supplicant[1027]: dbus: Failed to construct signal
mar 14 08:56:15 ezabba-Aspire spice-vdagent[1517]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
mar 14 08:57:19 ezabba-Aspire pulseaudio[1918]: [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.o
mar 14 08:57:25 ezabba-Aspire spice-vdagent[2035]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
mar 14 08:57:46 ezabba-Aspire gnome-session-binary[1390]: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop
mar 14 08:57:46 ezabba-Aspire gnome-session-binary[1390]: CRITICAL: We failed, but the fail whale is dead. Sorry....
system
asked Mar 14 at 8:31
luzzucluzzuc
363
inspect the journal for the current bootjouralctl -p 3 -b
– j-money
Mar 14 at 8:33
fyi: j-money mistypedjournalctl(it's journal & ctl short for control). You could also look in /var/crash/ for crash reports (& see what get's report); the file name provides a pretty good clue as to which program crashed
– guiverc
Mar 14 at 8:45
I tryed thejournalctlbut sadly the report is far from something I can understand. I edited the question with the journal result
– luzzuc
Mar 14 at 23:05
add a comment |
0
0
0
It'a a couple of days that each time I boot up Ubuntu (18.04) I get an alert window that claims that a system program have had a problem and the only two options given to me is to send a notification or close the alert.
Since there's no clue to which application have had the problem and I am a so not-expert of Linux at all, I would like to know if there's a way to find out which application is in order to try to solve the problem in some way.
Thanks everybody
Edit
So, I tryed to see in /var/crash/ but there's only two elements there and both of them are from three days ago, so nothing to do with the daily problem I suppose. So I tryed the journal option as suggested but the result doesn't mean anything to me due to my incomparable ignorance. I post here part of it, the bit I think is relevant due to the timecode, hoping someone can understand it and explain it to me.
mar 14 08:55:03 ezabba-Aspire kernel: tpm_crb MSFT0101:00: can't request region for resour
mar 14 08:55:03 ezabba-Aspire kernel: Problem loading UEFI:db X.509 certificate (-65)
mar 14 08:55:03 ezabba-Aspire kernel: Problem loading UEFI:db X.509 certificate (-65)
mar 14 08:55:03 ezabba-Aspire kernel: Couldn't get size: 0x800000000000000e
mar 14 08:55:31 ezabba-Aspire kernel: dell_smbios: Unable to run on non-Dell system
mar 14 08:55:31 ezabba-Aspire kernel: [drm:construct [amdgpu]] *ERROR* construct: Invalid
mar 14 08:55:31 ezabba-Aspire kernel: [drm:hwss_wait_for_blank_complete [amdgpu]] *ERROR*
mar 14 08:55:31 ezabba-Aspire kernel: kfd kfd: error getting iommu info. is the iommu enab
mar 14 08:55:31 ezabba-Aspire kernel: kfd kfd: Error initializing iommuv2 for device 1002:
mar 14 08:55:31 ezabba-Aspire kernel: kfd kfd: device 1002:9874 NOT added due to errors
mar 14 08:55:31 ezabba-Aspire kernel: amdgpu: [powerplay] Voltage value looks like a Leaka
mar 14 08:55:31 ezabba-Aspire kernel: amdgpu: [powerplay] Voltage value looks like a Leaka
mar 14 08:55:31 ezabba-Aspire kernel: amdgpu: [powerplay] Voltage value looks like a Leaka
mar 14 08:55:31 ezabba-Aspire kernel: amdgpu: [powerplay] Voltage value looks like a Leaka
mar 14 08:55:31 ezabba-Aspire kernel: amdgpu: [powerplay] Voltage value looks like a Leaka
mar 14 08:55:31 ezabba-Aspire kernel: amdgpu: [powerplay] Voltage value looks like a Leaka
mar 14 08:55:31 ezabba-Aspire kernel: amdgpu: [powerplay] Voltage value looks like a Leaka
mar 14 08:55:31 ezabba-Aspire kernel: [drm:dc_create [amdgpu]] *ERROR* DC: Number of conne
mar 14 08:55:29 ezabba-Aspire systemd-backlight[815]: Failed to get backlight or LED devic
mar 14 08:55:29 ezabba-Aspire systemd-backlight[817]: Failed to get backlight or LED devic
mar 14 08:55:29 ezabba-Aspire systemd[1]: Failed to start Load/Save Screen Backlight Brigh
mar 14 08:55:29 ezabba-Aspire systemd[1]: Failed to start Load/Save Screen Backlight Brigh
mar 14 08:55:40 ezabba-Aspire bluetoothd[993]: Loading LTKs timed out for hci0
mar 14 08:55:48 ezabba-Aspire wpa_supplicant[1027]: dbus: wpa_dbus_get_object_properties:
mar 14 08:55:48 ezabba-Aspire wpa_supplicant[1027]: dbus: Failed to construct signal
mar 14 08:56:15 ezabba-Aspire spice-vdagent[1517]: Cannot access vdagent virtio channel /d
mar 14 08:57:19 ezabba-Aspire pulseaudio[1918]: [pulseaudio] backend-ofono.c: Failed to re
mar 14 08:57:25 ezabba-Aspire spice-vdagent[2035]: Cannot access vdagent virtio channel /d
lines 1-29...skipping...
-- Logs begin at Sat 2018-11-10 14:10:14 CET, end at Thu 2019-03-14 23:39:02 CET. --
mar 14 08:55:03 ezabba-Aspire kernel: tpm_crb MSFT0101:00: can't request region for resource [mem 0xbfbba000-0xbfbbdfff]
mar 14 08:55:03 ezabba-Aspire kernel: Problem loading UEFI:db X.509 certificate (-65)
mar 14 08:55:03 ezabba-Aspire kernel: Problem loading UEFI:db X.509 certificate (-65)
mar 14 08:55:03 ezabba-Aspire kernel: Couldn't get size: 0x800000000000000e
mar 14 08:55:31 ezabba-Aspire kernel: dell_smbios: Unable to run on non-Dell system
mar 14 08:55:31 ezabba-Aspire kernel: [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:2!
mar 14 08:55:31 ezabba-Aspire kernel: [drm:hwss_wait_for_blank_complete [amdgpu]] *ERROR* DC: failed to blank crtc!
mar 14 08:55:31 ezabba-Aspire kernel: kfd kfd: error getting iommu info. is the iommu enabled?
mar 14 08:55:31 ezabba-Aspire kernel: kfd kfd: Error initializing iommuv2 for device 1002:9874
mar 14 08:55:31 ezabba-Aspire kernel: kfd kfd: device 1002:9874 NOT added due to errors
mar 14 08:55:31 ezabba-Aspire kernel: amdgpu: [powerplay] Voltage value looks like a Leakage ID but it's not patched
mar 14 08:55:31 ezabba-Aspire kernel: amdgpu: [powerplay] Voltage value looks like a Leakage ID but it's not patched
mar 14 08:55:31 ezabba-Aspire kernel: amdgpu: [powerplay] Voltage value looks like a Leakage ID but it's not patched
mar 14 08:55:31 ezabba-Aspire kernel: amdgpu: [powerplay] Voltage value looks like a Leakage ID but it's not patched
mar 14 08:55:31 ezabba-Aspire kernel: amdgpu: [powerplay] Voltage value looks like a Leakage ID but it's not patched
mar 14 08:55:31 ezabba-Aspire kernel: amdgpu: [powerplay] Voltage value looks like a Leakage ID but it's not patched
mar 14 08:55:31 ezabba-Aspire kernel: amdgpu: [powerplay] Voltage value looks like a Leakage ID but it's not patched
mar 14 08:55:31 ezabba-Aspire kernel: [drm:dc_create [amdgpu]] *ERROR* DC: Number of connectors is zero!
mar 14 08:55:29 ezabba-Aspire systemd-backlight[815]: Failed to get backlight or LED device 'backlight:acpi_video1': No such device
mar 14 08:55:29 ezabba-Aspire systemd-backlight[817]: Failed to get backlight or LED device 'backlight:acpi_video0': No such device
mar 14 08:55:29 ezabba-Aspire systemd[1]: Failed to start Load/Save Screen Backlight Brightness of backlight:acpi_video1.
mar 14 08:55:29 ezabba-Aspire systemd[1]: Failed to start Load/Save Screen Backlight Brightness of backlight:acpi_video0.
mar 14 08:55:40 ezabba-Aspire bluetoothd[993]: Loading LTKs timed out for hci0
mar 14 08:55:48 ezabba-Aspire wpa_supplicant[1027]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (none) none
mar 14 08:55:48 ezabba-Aspire wpa_supplicant[1027]: dbus: Failed to construct signal
mar 14 08:56:15 ezabba-Aspire spice-vdagent[1517]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
mar 14 08:57:19 ezabba-Aspire pulseaudio[1918]: [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.o
mar 14 08:57:25 ezabba-Aspire spice-vdagent[2035]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
mar 14 08:57:46 ezabba-Aspire gnome-session-binary[1390]: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop
mar 14 08:57:46 ezabba-Aspire gnome-session-binary[1390]: CRITICAL: We failed, but the fail whale is dead. Sorry....
system
asked Mar 14 at 8:31
luzzucluzzuc
363
It'a a couple of days that each time I boot up Ubuntu (18.04) I get an alert window that claims that a system program have had a problem and the only two options given to me is to send a notification or close the alert.
Since there's no clue to which application have had the problem and I am a so not-expert of Linux at all, I would like to know if there's a way to find out which application is in order to try to solve the problem in some way.
Thanks everybody
Edit
So, I tryed to see in /var/crash/ but there's only two elements there and both of them are from three days ago, so nothing to do with the daily problem I suppose. So I tryed the journal option as suggested but the result doesn't mean anything to me due to my incomparable ignorance. I post here part of it, the bit I think is relevant due to the timecode, hoping someone can understand it and explain it to me.
mar 14 08:55:03 ezabba-Aspire kernel: tpm_crb MSFT0101:00: can't request region for resour
mar 14 08:55:03 ezabba-Aspire kernel: Problem loading UEFI:db X.509 certificate (-65)
mar 14 08:55:03 ezabba-Aspire kernel: Problem loading UEFI:db X.509 certificate (-65)
mar 14 08:55:03 ezabba-Aspire kernel: Couldn't get size: 0x800000000000000e
mar 14 08:55:31 ezabba-Aspire kernel: dell_smbios: Unable to run on non-Dell system
mar 14 08:55:31 ezabba-Aspire kernel: [drm:construct [amdgpu]] *ERROR* construct: Invalid
mar 14 08:55:31 ezabba-Aspire kernel: [drm:hwss_wait_for_blank_complete [amdgpu]] *ERROR*
mar 14 08:55:31 ezabba-Aspire kernel: kfd kfd: error getting iommu info. is the iommu enab
mar 14 08:55:31 ezabba-Aspire kernel: kfd kfd: Error initializing iommuv2 for device 1002:
mar 14 08:55:31 ezabba-Aspire kernel: kfd kfd: device 1002:9874 NOT added due to errors
mar 14 08:55:31 ezabba-Aspire kernel: amdgpu: [powerplay] Voltage value looks like a Leaka
mar 14 08:55:31 ezabba-Aspire kernel: amdgpu: [powerplay] Voltage value looks like a Leaka
mar 14 08:55:31 ezabba-Aspire kernel: amdgpu: [powerplay] Voltage value looks like a Leaka
mar 14 08:55:31 ezabba-Aspire kernel: amdgpu: [powerplay] Voltage value looks like a Leaka
mar 14 08:55:31 ezabba-Aspire kernel: amdgpu: [powerplay] Voltage value looks like a Leaka
mar 14 08:55:31 ezabba-Aspire kernel: amdgpu: [powerplay] Voltage value looks like a Leaka
mar 14 08:55:31 ezabba-Aspire kernel: amdgpu: [powerplay] Voltage value looks like a Leaka
mar 14 08:55:31 ezabba-Aspire kernel: [drm:dc_create [amdgpu]] *ERROR* DC: Number of conne
mar 14 08:55:29 ezabba-Aspire systemd-backlight[815]: Failed to get backlight or LED devic
mar 14 08:55:29 ezabba-Aspire systemd-backlight[817]: Failed to get backlight or LED devic
mar 14 08:55:29 ezabba-Aspire systemd[1]: Failed to start Load/Save Screen Backlight Brigh
mar 14 08:55:29 ezabba-Aspire systemd[1]: Failed to start Load/Save Screen Backlight Brigh
mar 14 08:55:40 ezabba-Aspire bluetoothd[993]: Loading LTKs timed out for hci0
mar 14 08:55:48 ezabba-Aspire wpa_supplicant[1027]: dbus: wpa_dbus_get_object_properties:
mar 14 08:55:48 ezabba-Aspire wpa_supplicant[1027]: dbus: Failed to construct signal
mar 14 08:56:15 ezabba-Aspire spice-vdagent[1517]: Cannot access vdagent virtio channel /d
mar 14 08:57:19 ezabba-Aspire pulseaudio[1918]: [pulseaudio] backend-ofono.c: Failed to re
mar 14 08:57:25 ezabba-Aspire spice-vdagent[2035]: Cannot access vdagent virtio channel /d
lines 1-29...skipping...
-- Logs begin at Sat 2018-11-10 14:10:14 CET, end at Thu 2019-03-14 23:39:02 CET. --
mar 14 08:55:03 ezabba-Aspire kernel: tpm_crb MSFT0101:00: can't request region for resource [mem 0xbfbba000-0xbfbbdfff]
mar 14 08:55:03 ezabba-Aspire kernel: Problem loading UEFI:db X.509 certificate (-65)
mar 14 08:55:03 ezabba-Aspire kernel: Problem loading UEFI:db X.509 certificate (-65)
mar 14 08:55:03 ezabba-Aspire kernel: Couldn't get size: 0x800000000000000e
mar 14 08:55:31 ezabba-Aspire kernel: dell_smbios: Unable to run on non-Dell system
mar 14 08:55:31 ezabba-Aspire kernel: [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:2!
mar 14 08:55:31 ezabba-Aspire kernel: [drm:hwss_wait_for_blank_complete [amdgpu]] *ERROR* DC: failed to blank crtc!
mar 14 08:55:31 ezabba-Aspire kernel: kfd kfd: error getting iommu info. is the iommu enabled?
mar 14 08:55:31 ezabba-Aspire kernel: kfd kfd: Error initializing iommuv2 for device 1002:9874
mar 14 08:55:31 ezabba-Aspire kernel: kfd kfd: device 1002:9874 NOT added due to errors
mar 14 08:55:31 ezabba-Aspire kernel: amdgpu: [powerplay] Voltage value looks like a Leakage ID but it's not patched
mar 14 08:55:31 ezabba-Aspire kernel: amdgpu: [powerplay] Voltage value looks like a Leakage ID but it's not patched
mar 14 08:55:31 ezabba-Aspire kernel: amdgpu: [powerplay] Voltage value looks like a Leakage ID but it's not patched
mar 14 08:55:31 ezabba-Aspire kernel: amdgpu: [powerplay] Voltage value looks like a Leakage ID but it's not patched
mar 14 08:55:31 ezabba-Aspire kernel: amdgpu: [powerplay] Voltage value looks like a Leakage ID but it's not patched
mar 14 08:55:31 ezabba-Aspire kernel: amdgpu: [powerplay] Voltage value looks like a Leakage ID but it's not patched
mar 14 08:55:31 ezabba-Aspire kernel: amdgpu: [powerplay] Voltage value looks like a Leakage ID but it's not patched
mar 14 08:55:31 ezabba-Aspire kernel: [drm:dc_create [amdgpu]] *ERROR* DC: Number of connectors is zero!
mar 14 08:55:29 ezabba-Aspire systemd-backlight[815]: Failed to get backlight or LED device 'backlight:acpi_video1': No such device
mar 14 08:55:29 ezabba-Aspire systemd-backlight[817]: Failed to get backlight or LED device 'backlight:acpi_video0': No such device
mar 14 08:55:29 ezabba-Aspire systemd[1]: Failed to start Load/Save Screen Backlight Brightness of backlight:acpi_video1.
mar 14 08:55:29 ezabba-Aspire systemd[1]: Failed to start Load/Save Screen Backlight Brightness of backlight:acpi_video0.
mar 14 08:55:40 ezabba-Aspire bluetoothd[993]: Loading LTKs timed out for hci0
mar 14 08:55:48 ezabba-Aspire wpa_supplicant[1027]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (none) none
mar 14 08:55:48 ezabba-Aspire wpa_supplicant[1027]: dbus: Failed to construct signal
mar 14 08:56:15 ezabba-Aspire spice-vdagent[1517]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
mar 14 08:57:19 ezabba-Aspire pulseaudio[1918]: [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.o
mar 14 08:57:25 ezabba-Aspire spice-vdagent[2035]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
mar 14 08:57:46 ezabba-Aspire gnome-session-binary[1390]: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop
mar 14 08:57:46 ezabba-Aspire gnome-session-binary[1390]: CRITICAL: We failed, but the fail whale is dead. Sorry....
system
system
asked Mar 14 at 8:31
luzzucluzzuc
363
asked Mar 14 at 8:31
luzzucluzzuc
363
edited Mar 14 at 23:01
luzzuc
asked Mar 14 at 8:31
luzzucluzzuc
363
asked Mar 14 at 8:31
luzzucluzzuc
363
asked Mar 14 at 8:31
luzzucluzzuc
363
363
inspect the journal for the current bootjouralctl -p 3 -b
– j-money
Mar 14 at 8:33
fyi: j-money mistypedjournalctl(it's journal & ctl short for control). You could also look in /var/crash/ for crash reports (& see what get's report); the file name provides a pretty good clue as to which program crashed
– guiverc
Mar 14 at 8:45
I tryed thejournalctlbut sadly the report is far from something I can understand. I edited the question with the journal result
– luzzuc
Mar 14 at 23:05
add a comment |
inspect the journal for the current bootjouralctl -p 3 -b
– j-money
Mar 14 at 8:33
fyi: j-money mistypedjournalctl(it's journal & ctl short for control). You could also look in /var/crash/ for crash reports (& see what get's report); the file name provides a pretty good clue as to which program crashed
– guiverc
Mar 14 at 8:45
I tryed thejournalctlbut sadly the report is far from something I can understand. I edited the question with the journal result
– luzzuc
Mar 14 at 23:05
inspect the journal for the current boot
jouralctl -p 3 -b– j-money
Mar 14 at 8:33
inspect the journal for the current boot
jouralctl -p 3 -b– j-money
Mar 14 at 8:33
fyi: j-money mistyped
journalctl (it's journal & ctl short for control). You could also look in /var/crash/ for crash reports (& see what get's report); the file name provides a pretty good clue as to which program crashed– guiverc
Mar 14 at 8:45
fyi: j-money mistyped
journalctl (it's journal & ctl short for control). You could also look in /var/crash/ for crash reports (& see what get's report); the file name provides a pretty good clue as to which program crashed– guiverc
Mar 14 at 8:45
I tryed the
journalctl but sadly the report is far from something I can understand. I edited the question with the journal result– luzzuc
Mar 14 at 23:05
I tryed the
journalctl but sadly the report is far from something I can understand. I edited the question with the journal result– luzzuc
Mar 14 at 23:05
add a comment |
1 Answer
1
active
oldest
votes
0
The ubuntu crash reports are stored in /var/crash.
You could do "ls -l /var/crash/" to get a list of the error reports.
Note down the most recent and see if you can address whatever problem that application is having.
answered Mar 14 at 9:49
Amiga85Amiga85
112
I tryed thels -l /var/crash/but there's only two files there from three days ago, so I think nothing to do with my problem
– luzzuc
Mar 14 at 23:04
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1125538%2fhow-to-find-out-which-application-have-a-problem%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
0
The ubuntu crash reports are stored in /var/crash.
You could do "ls -l /var/crash/" to get a list of the error reports.
Note down the most recent and see if you can address whatever problem that application is having.
answered Mar 14 at 9:49
Amiga85Amiga85
112
I tryed thels -l /var/crash/but there's only two files there from three days ago, so I think nothing to do with my problem
– luzzuc
Mar 14 at 23:04
add a comment |
0
The ubuntu crash reports are stored in /var/crash.
You could do "ls -l /var/crash/" to get a list of the error reports.
Note down the most recent and see if you can address whatever problem that application is having.
answered Mar 14 at 9:49
Amiga85Amiga85
112
I tryed thels -l /var/crash/but there's only two files there from three days ago, so I think nothing to do with my problem
– luzzuc
Mar 14 at 23:04
add a comment |
0
0
0
The ubuntu crash reports are stored in /var/crash.
You could do "ls -l /var/crash/" to get a list of the error reports.
Note down the most recent and see if you can address whatever problem that application is having.
answered Mar 14 at 9:49
Amiga85Amiga85
112
The ubuntu crash reports are stored in /var/crash.
You could do "ls -l /var/crash/" to get a list of the error reports.
Note down the most recent and see if you can address whatever problem that application is having.
answered Mar 14 at 9:49
Amiga85Amiga85
112
answered Mar 14 at 9:49
Amiga85Amiga85
112
answered Mar 14 at 9:49
Amiga85Amiga85
112
answered Mar 14 at 9:49
Amiga85Amiga85
112
112
I tryed thels -l /var/crash/but there's only two files there from three days ago, so I think nothing to do with my problem
– luzzuc
Mar 14 at 23:04
add a comment |
I tryed thels -l /var/crash/but there's only two files there from three days ago, so I think nothing to do with my problem
– luzzuc
Mar 14 at 23:04
I tryed the
ls -l /var/crash/ but there's only two files there from three days ago, so I think nothing to do with my problem– luzzuc
Mar 14 at 23:04
I tryed the
ls -l /var/crash/ but there's only two files there from three days ago, so I think nothing to do with my problem– luzzuc
Mar 14 at 23:04
add a comment |
draft saved
draft discarded
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1125538%2fhow-to-find-out-which-application-have-a-problem%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
inspect the journal for the current boot
jouralctl -p 3 -b– j-money
Mar 14 at 8:33
fyi: j-money mistyped
journalctl(it's journal & ctl short for control). You could also look in /var/crash/ for crash reports (& see what get's report); the file name provides a pretty good clue as to which program crashed– guiverc
Mar 14 at 8:45
I tryed the
journalctlbut sadly the report is far from something I can understand. I edited the question with the journal result– luzzuc
Mar 14 at 23:05