journalctl -b -p err Meldungen

Ich habe gerade mal ein “journalctl -b -p err” ausgeführt und da wurden mir einige Fehler angezeigt. Was haben die zu bedeuten und wie kann ich sie beheben?

-- Logs begin at Fr 2016-06-03 13:24:47 CEST, end at Fr 2016-06-03 16:44:50 CEST. --
Jun 03 13:24:47 panther kernel: k10temp 0000:00:18.3: unreliable CPU thermal sensor; monitoring disabled
Jun 03 13:24:47 panther nvidia-persistenced[578]: Failed to query NVIDIA devices. Please ensure that the NVIDIA device files (/dev/nvidia*) exist, and that user 108 has read and write permissions for those files.
Jun 03 13:24:49 panther NetworkManager[779]: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed
Jun 03 13:24:51 panther NetworkManager[779]: <error> [1464953091.511541] [dns-manager/nm-dns-dnsmasq.c:387] update(): dnsmasq owner not found on bus: Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such name
Jun 03 13:24:52 panther kernel: snd_hda_intel 0000:00:07.0: azx_get_response timeout, switching to single_cmd mode: last cmd=0x000f0000
Jun 03 13:24:52 panther kernel: hdaudio hdaudioC0D0: no AFG or MFG node found
Jun 03 13:24:52 panther kernel: snd_hda_intel 0000:00:07.0: no codecs initialized
Jun 03 13:28:40 panther /hp-systray[1672]: hp-systray[1672]: error: option -s not recognized
Jun 03 13:29:05 panther pulseaudio[1648]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jun 03 13:31:51 panther console-kit-daemon[1417]: GLib-CRITICAL: Source ID 35 was not found when attempting to remove it
Jun 03 13:31:51 panther console-kit-daemon[1417]: GLib-CRITICAL: Source ID 49 was not found when attempting to remove it
Jun 03 13:33:00 panther console-kit-daemon[1417]: GLib-CRITICAL: Source ID 62 was not found when attempting to remove it
Jun 03 13:33:00 panther console-kit-daemon[1417]: GLib-CRITICAL: Source ID 62 was not found when attempting to remove it

Sound habe ich, ich nutze die C-Media Karte. Was ist das mit dem Network-Manager und dem /dev/nvidia?

inxi:

System:    Host: panther Kernel: 4.2.0-37-generic x86_64 (64 bit gcc: 5.2.1) Desktop: KDE 5
           Distro: Ubuntu 17 wily
Machine:   Mobo: Gigabyte model: M720-US3 v: x.x Bios: Award v: F2 date: 01/08/2009
CPU:       Quad core AMD Phenom 9550 (-MCP-) cache: 2048 KB flags: (lm nx sse sse2 sse3 sse4a svm) bmips: 17598 
           clock speeds: max: 2200 MHz 1: 1100 MHz 2: 1100 MHz 3: 1100 MHz 4: 1100 MHz
Memory:    Using dmidecode: you must be root to run dmidecode
Graphics:  Card: NVIDIA GF119 [GeForce GT 610] bus-ID: 02:00.0
           Display Server: X.Org 1.17.2 driver: nvidia Resolution: 1920x1200@59.95hz
           GLX Renderer: GeForce GT 610/PCIe/SSE2 GLX Version: 4.5.0 NVIDIA 352.63 Direct Rendering: Yes
Audio:     Card-1 NVIDIA MCP72XE/MCP72P/MCP78U/MCP78S High Definition Audio
           driver: snd_hda_intel bus-ID: 00:07.0
           Card-2 C-Media CMI8738/CMI8768 PCI Audio driver: snd_cmipci port: 9000 bus-ID: 01:09.0
           Card-3 NVIDIA GF119 HDMI Audio Controller driver: snd_hda_intel bus-ID: 02:00.1
           Sound: Advanced Linux Sound Architecture v: k4.2.0-37-generic
Network:   Card: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
           driver: r8169 v: 2.3LK-NAPI port: b000 bus-ID: 03:00.0
           IF: enp3s0 state: up speed: 100 Mbps duplex: full mac: 00:24:1d:65:08:95
Drives:    HDD Total Size: 1340.3GB (49.5% used) ID-1: /dev/sda model: SAMSUNG_HD642JJ size: 640.1GB
           ID-2: /dev/sdb model: SAMSUNG_HD642JJ size: 640.1GB ID-3: /dev/sdc model: KingFast size: 60.0GB
           Optical: /dev/sr0 model: TSST CDDVDW SH-S223Q rev: SB03 dev-links: cdrom,cdrw,dvd,dvdrw
Partition: ID-1: / size: 55G used: 14G (26%) fs: ext4 dev: /dev/sdc1
           label: N/A uuid: b539ee26-7df8-46df-8cee-7aa12bce2695
           ID-2: /home size: 165G used: 122G (78%) fs: ext4 dev: /dev/sda5
           label: N/A uuid: 75bacc27-95ca-4a56-b982-c43fbb886627
           ID-3: swap-1 size: 2.15GB used: 0.00GB (0%) fs: swap dev: /dev/sda3
           label: N/A uuid: 49d5dff9-3ff1-4d1f-99f9-7c0860b2422d
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   System Temperatures: cpu: 52.0C mobo: 40.0C gpu: 0.0:47C
           Fan Speeds (in rpm): cpu: 762 fan-1: 2051 fan-3: 739 fan-4: 1044
Info:      Processes: 243 Uptime: 3:29 Memory: 4529.7/7983.4MB Init: systemd runlevel: 5 Gcc sys: 5.2.1
           Client: Shell (bash 4.3.421) inxi: 2.2.16 

Wenn alles funktioniert möglicherweise nur timing Probleme während des hochfahrens. Systemd fährt ja alles gleichzeitig hoch und das klappt bei allen Diensten nicht immer sofort und muss nacheinander passieren. Da aber die Sockets alle schon offen sind, kann es zu solchen Meldungen kommen.

Naja, ist halt “log-pollution”… Das mit dem “console-kit-daemon[1417]: GLib-CRITICAL” scheint ein bekannter Bug zu sein, der das Patchen und Neukompilieren von consolekit erfordern würde https://bugs.launchpad.net/ubuntu/+source/consolekit/+bug/1313042/comments/7 was aber von Maintainerseite nicht passiert, da das Teil zur Zeit unmaintained ist: https://freedesktop.org/wiki/Software/ConsoleKit/