-- Logs begin at Wed 2017-05-10 17:17:09 CEST, end at Wed 2017-05-10 18:39:35 CEST. --
maj 10 17:17:09 pi-MS-7A34 kernel: ACPI BIOS Warning (bug): Optional FADT field Pm2ControlBlock has valid Length but zero Address: 0x0000000000000000/0x1 (20160930/tbfadt-658)
maj 10 17:17:09 pi-MS-7A34 kernel: [Firmware Bug]: AMD-Vi: IOAPIC[17] not in IVRS table
maj 10 17:17:09 pi-MS-7A34 kernel: [Firmware Bug]: AMD-Vi: IOAPIC[18] not in IVRS table
maj 10 17:17:09 pi-MS-7A34 kernel: [Firmware Bug]: AMD-Vi: No southbridge IOAPIC found
maj 10 17:17:09 pi-MS-7A34 kernel: AMD-Vi: Disabling interrupt remapping
maj 10 17:17:09 pi-MS-7A34 kernel: PCCT header not found.
maj 10 17:17:09 pi-MS-7A34 kernel: pmd_set_huge: Cannot satisfy [mem 0xf8000000-0xf8200000] with a huge-page mapping due to MTRR override.
maj 10 17:17:09 pi-MS-7A34 kernel: amdgpu 0000:24:00.0: Invalid PCI ROM header signature: expecting 0xaa55, got 0xffff
maj 10 17:17:09 pi-MS-7A34 kernel: Can't find requested voltage id in vdd_dep_on_sclk table!
maj 10 17:17:09 pi-MS-7A34 kernel: ata5.00: supports DRM functions and may not be fully accessible
maj 10 17:17:09 pi-MS-7A34 kernel: ata5.00: supports DRM functions and may not be fully accessible
maj 10 17:17:10 pi-MS-7A34 kernel: kvm: disabled by bios
maj 10 17:17:10 pi-MS-7A34 systemd-tmpfiles[851]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
maj 10 17:17:10 pi-MS-7A34 colord[1128]: failed to get session [pid 1027]: No such device or address
maj 10 17:17:10 pi-MS-7A34 NetworkManager[1031]: ((devices/nm-device.c:970)): assertion '<dropped>' failed
maj 10 17:17:14 pi-MS-7A34 colord-sane[1153]: io/hpmud/pp.c 627: unable to read device-id ret=-1
maj 10 17:17:19 pi-MS-7A34 lightdm[1304]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
maj 10 17:17:19 pi-MS-7A34 lightdm[1356]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
maj 10 17:17:19 pi-MS-7A34 lightdm[1356]: PAM adding faulty module: pam_kwallet.so
maj 10 17:17:19 pi-MS-7A34 lightdm[1356]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
maj 10 17:17:19 pi-MS-7A34 lightdm[1356]: PAM adding faulty module: pam_kwallet5.so
maj 10 17:17:20 pi-MS-7A34 indicator-sound[1420]: volume-control-pulse.vala:735: unable to get pulse unix socket: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.PulseAudio1 was not provided by any .service files
maj 10 17:17:20 pi-MS-7A34 indicator-keybo[1418]: gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed
maj 10 17:17:20 pi-MS-7A34 pulseaudio[1463]: [pulseaudio] alsa-mixer.c: Volume element Master has 8 channels. That's too much! I can't handle that!
maj 10 17:17:20 pi-MS-7A34 pulseaudio[1463]: [pulseaudio] alsa-mixer.c: Volume element Master has 8 channels. That's too much! I can't handle that!
maj 10 17:17:20 pi-MS-7A34 pulseaudio[1463]: [pulseaudio] alsa-mixer.c: Volume element Master has 8 channels. That's too much! I can't handle that!
maj 10 17:17:20 pi-MS-7A34 pulseaudio[1463]: [pulseaudio] alsa-mixer.c: Volume element Master has 8 channels. That's too much! I can't handle that!
maj 10 17:17:20 pi-MS-7A34 pulseaudio[1463]: [pulseaudio] alsa-mixer.c: Volume element Master has 8 channels. That's too much! I can't handle that!
maj 10 17:17:20 pi-MS-7A34 lightdm[1502]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
maj 10 17:17:20 pi-MS-7A34 lightdm[1502]: PAM adding faulty module: pam_kwallet.so
maj 10 17:17:20 pi-MS-7A34 lightdm[1502]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
maj 10 17:17:20 pi-MS-7A34 lightdm[1502]: PAM adding faulty module: pam_kwallet5.so
maj 10 17:17:20 pi-MS-7A34 pulseaudio[1510]: [pulseaudio] pid.c: Daemon already running.
maj 10 17:17:44 pi-MS-7A34 pulseaudio[1463]: [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.
maj 10 17:32:30 pi-MS-7A34 systemd-tmpfiles[1625]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
maj 10 17:47:55 pi-MS-7A34 lightdm[1304]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
maj 10 17:47:56 pi-MS-7A34 gnome-session-c[1783]: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-uLZFpEtE0J: Connection refused
maj 10 17:47:56 pi-MS-7A34 gnome-screensav[1816]: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-uLZFpEtE0J: Connection refused
maj 10 17:47:56 pi-MS-7A34 gnome-screensav[1816]: Couldn't get presence status: The name org.gnome.SessionManager was not provided by any .service files
maj 10 17:47:56 pi-MS-7A34 gnome-shell[1832]: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-uLZFpEtE0J: Connection refused
maj 10 17:47:56 pi-MS-7A34 pulseaudio[1845]: [pulseaudio] alsa-mixer.c: Volume element Master has 8 channels. That's too much! I can't handle that!
maj 10 17:47:56 pi-MS-7A34 pulseaudio[1845]: [pulseaudio] alsa-mixer.c: Volume element Master has 8 channels. That's too much! I can't handle that!
maj 10 17:47:56 pi-MS-7A34 pulseaudio[1845]: [pulseaudio] alsa-mixer.c: Volume element Master has 8 channels. That's too much! I can't handle that!
maj 10 17:47:56 pi-MS-7A34 pulseaudio[1845]: [pulseaudio] alsa-mixer.c: Volume element Master has 8 channels. That's too much! I can't handle that!
maj 10 17:47:56 pi-MS-7A34 pulseaudio[1845]: [pulseaudio] alsa-mixer.c: Volume element Master has 8 channels. That's too much! I can't handle that!
maj 10 17:47:57 pi-MS-7A34 org.gnome.Shell.desktop[1832]: current session already has an ibus-daemon.
maj 10 17:47:57 pi-MS-7A34 gsd-power[1945]: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-uLZFpEtE0J: Connection refused
maj 10 17:47:57 pi-MS-7A34 gsd-print-notif[1951]: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-uLZFpEtE0J: Connection refused
maj 10 17:47:57 pi-MS-7A34 gsd-wacom[1967]: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-uLZFpEtE0J: Connection refused
maj 10 17:47:57 pi-MS-7A34 at-spi-dbus-bus.desktop[1981]: Activating service name='org.a11y.atspi.Registry'
maj 10 17:47:57 pi-MS-7A34 at-spi-dbus-bus.desktop[1981]: Successfully activated service 'org.a11y.atspi.Registry'
maj 10 17:47:58 pi-MS-7A34 gsd-sharing[1960]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit rygel.service not loaded.
maj 10 17:47:58 pi-MS-7A34 at-spi2-registr[2001]: Failed to register client: GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register client
maj 10 17:47:58 pi-MS-7A34 at-spi2-registr[2001]: Unable to register client with session manager
maj 10 17:47:58 pi-MS-7A34 nautilus-deskto[2060]: Can not calculate _NET_NUMBER_OF_DESKTOPS
maj 10 17:47:58 pi-MS-7A34 nautilus-deskto[2060]: Can not calculate _NET_NUMBER_OF_DESKTOPS
maj 10 17:47:58 pi-MS-7A34 nautilus-deskto[2060]: Can not get _NET_WORKAREA
maj 10 17:47:58 pi-MS-7A34 nautilus-deskto[2060]: Can not determine workarea, guessing at layout
maj 10 17:47:58 pi-MS-7A34 nautilus-deskto[2060]: Can not calculate _NET_NUMBER_OF_DESKTOPS
maj 10 17:47:58 pi-MS-7A34 nautilus-deskto[2060]: Can not calculate _NET_NUMBER_OF_DESKTOPS
maj 10 17:47:58 pi-MS-7A34 nautilus-deskto[2060]: Can not get _NET_WORKAREA
maj 10 17:47:58 pi-MS-7A34 nautilus-deskto[2060]: Can not determine workarea, guessing at layout
maj 10 17:47:59 pi-MS-7A34 fwupd[2179]: disabling plugin because: failed to startup dell: Firmware updating not supported
maj 10 17:48:00 pi-MS-7A34 fwupd[2179]: ignoring add-delay as device usb:00:08:03 already pending
maj 10 17:48:00 pi-MS-7A34 fwupd[2179]: disabling plugin because: failed to coldplug raspberrypi: Raspberry PI firmware updating not supported, no /boot/start.elf
maj 10 17:48:00 pi-MS-7A34 fwupd[2179]: disabling plugin because: failed to coldplug synapticsmst: MST firmware updating not supported by OEM
maj 10 17:48:00 pi-MS-7A34 fwupd[2179]: ignoring add-delay as device ro__sys_devices_pci0000_00_0000_00_03_1_0000_24_00_0 already pending
maj 10 17:48:02 pi-MS-7A34 gnome-keyring-daemon[1655]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered
maj 10 17:48:02 pi-MS-7A34 gnome-keyring-daemon[1655]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered
maj 10 17:48:17 pi-MS-7A34 zeitgeist-datah[2520]: zeitgeist-datahub.vala:227: Unable to get name "org.gnome.zeitgeist.datahub" on the bus!
maj 10 17:48:21 pi-MS-7A34 pulseaudio[1845]: [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.
maj 10 17:48:27 pi-MS-7A34 zeitgeist-datah[2502]: zeitgeist-datahub.vala:210: Error during inserting events: GDBus.Error:org.gnome.zeitgeist.EngineError.InvalidArgument: Incomplete event: interpretation, manifestation and actor are required
maj 10 18:20:23 pi-MS-7A34 kernel: show_signal_msg: 42 callbacks suppressed
maj 10 18:20:49 pi-MS-7A34 indicator-multi[2064]: Unable to connect to the Notification Watcher: Timeout was reached
maj 10 18:20:49 pi-MS-7A34 indicator-multi[2064]: Unable to connect to the Notification Watcher: Timeout was reached
maj 10 18:20:50 pi-MS-7A34 indicator-multi[2064]: Unable to connect to the Notification Watcher: Timeout was reached
maj 10 18:20:50 pi-MS-7A34 indicator-multi[2064]: Unable to connect to the Notification Watcher: Timeout was reached
maj 10 18:20:51 pi-MS-7A34 indicator-multi[2064]: Unable to connect to the Notification Watcher: Timeout was reached
maj 10 18:20:51 pi-MS-7A34 indicator-multi[2064]: Unable to connect to the Notification Watcher: Timeout was reached
maj 10 18:20:52 pi-MS-7A34 indicator-multi[2064]: Unable to connect to the Notification Watcher: Timeout was reached
maj 10 18:20:52 pi-MS-7A34 indicator-multi[2064]: Unable to connect to the Notification Watcher: Timeout was reached
maj 10 18:20:53 pi-MS-7A34 indicator-multi[2064]: Unable to connect to the Notification Watcher: Timeout was reached
maj 10 18:20:53 pi-MS-7A34 indicator-multi[2064]: Unable to connect to the Notification Watcher: Timeout was reached
maj 10 18:20:54 pi-MS-7A34 indicator-multi[2064]: Unable to connect to the Notification Watcher: Timeout was reached
maj 10 18:20:54 pi-MS-7A34 indicator-multi[2064]: Unable to connect to the Notification Watcher: Timeout was reached
maj 10 18:20:55 pi-MS-7A34 indicator-multi[2064]: Unable to connect to the Notification Watcher: Timeout was reached
maj 10 18:20:55 pi-MS-7A34 indicator-multi[2064]: Unable to connect to the Notification Watcher: Timeout was reached
maj 10 18:20:56 pi-MS-7A34 indicator-multi[2064]: Unable to connect to the Notification Watcher: Timeout was reached
maj 10 18:20:56 pi-MS-7A34 indicator-multi[2064]: Unable to connect to the Notification Watcher: Timeout was reached
maj 10 18:20:57 pi-MS-7A34 indicator-multi[2064]: Unable to connect to the Notification Watcher: Timeout was reached
maj 10 18:20:57 pi-MS-7A34 indicator-multi[2064]: Unable to connect to the Notification Watcher: Timeout was reached
maj 10 18:20:58 pi-MS-7A34 indicator-multi[2064]: Unable to connect to the Notification Watcher: Timeout was reached
maj 10 18:20:58 pi-MS-7A34 indicator-multi[2064]: Unable to connect to the Notification Watcher: Timeout was reached
maj 10 18:20:59 pi-MS-7A34 indicator-multi[2064]: Unable to connect to the Notification Watcher: Timeout was reached
maj 10 18:20:59 pi-MS-7A34 indicator-multi[2064]: Unable to connect to the Notification Watcher: Timeout was reached
maj 10 18:21:00 pi-MS-7A34 indicator-multi[2064]: Unable to connect to the Notification Watcher: Timeout was reached
maj 10 18:21:00 pi-MS-7A34 indicator-multi[2064]: Unable to connect to the Notification Watcher: Timeout was reached
maj 10 18:21:01 pi-MS-7A34 indicator-multi[2064]: Unable to connect to the Notification Watcher: Timeout was reached
maj 10 18:21:01 pi-MS-7A34 indicator-multi[2064]: Unable to connect to the Notification Watcher: Timeout was reached
maj 10 18:21:02 pi-MS-7A34 indicator-multi[2064]: Unable to connect to the Notification Watcher: Timeout was reached
maj 10 18:21:02 pi-MS-7A34 indicator-multi[2064]: Unable to connect to the Notification Watcher: Timeout was reached
maj 10 18:21:03 pi-MS-7A34 indicator-multi[2064]: Unable to connect to the Notification Watcher: Timeout was reached
maj 10 18:21:03 pi-MS-7A34 indicator-multi[2064]: Unable to connect to the Notification Watcher: Timeout was reached
maj 10 18:21:04 pi-MS-7A34 gnome-session-binary[1658]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11
maj 10 18:21:04 pi-MS-7A34 indicator-multi[2064]: Unable to connect to the Notification Watcher: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
maj 10 18:21:04 pi-MS-7A34 indicator-multi[2064]: Unable to connect to the Notification Watcher: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
maj 10 18:21:04 pi-MS-7A34 indicator-multi[2064]: Unable to connect to the Notification Watcher: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
maj 10 18:21:04 pi-MS-7A34 indicator-multi[2064]: Unable to connect to the Notification Watcher: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
maj 10 18:21:04 pi-MS-7A34 indicator-multi[2064]: Unable to connect to the Notification Watcher: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
maj 10 18:21:04 pi-MS-7A34 indicator-multi[2064]: Unable to connect to the Notification Watcher: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
maj 10 18:21:04 pi-MS-7A34 indicator-multi[2064]: Unable to connect to the Notification Watcher: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
maj 10 18:21:04 pi-MS-7A34 indicator-multi[2064]: Unable to connect to the Notification Watcher: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
maj 10 18:21:04 pi-MS-7A34 indicator-multi[2064]: Unable to connect to the Notification Watcher: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
maj 10 18:21:04 pi-MS-7A34 indicator-multi[2064]: Unable to connect to the Notification Watcher: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
maj 10 18:21:04 pi-MS-7A34 indicator-multi[2064]: Unable to connect to the Notification Watcher: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
maj 10 18:21:04 pi-MS-7A34 indicator-multi[2064]: Unable to connect to the Notification Watcher: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
maj 10 18:21:04 pi-MS-7A34 indicator-multi[2064]: Unable to connect to the Notification Watcher: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
maj 10 18:21:04 pi-MS-7A34 indicator-multi[2064]: Unable to connect to the Notification Watcher: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
maj 10 18:21:04 pi-MS-7A34 indicator-multi[2064]: Unable to connect to the Notification Watcher: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
maj 10 18:21:04 pi-MS-7A34 indicator-multi[2064]: Unable to connect to the Notification Watcher: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
maj 10 18:21:04 pi-MS-7A34 indicator-multi[2064]: Unable to connect to the Notification Watcher: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
maj 10 18:21:04 pi-MS-7A34 indicator-multi[2064]: Unable to connect to the Notification Watcher: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
maj 10 18:21:04 pi-MS-7A34 indicator-multi[2064]: Unable to connect to the Notification Watcher: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
maj 10 18:21:04 pi-MS-7A34 indicator-multi[2064]: Unable to connect to the Notification Watcher: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
maj 10 18:21:04 pi-MS-7A34 indicator-multi[2064]: Unable to connect to the Notification Watcher: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
maj 10 18:21:04 pi-MS-7A34 indicator-multi[2064]: Unable to connect to the Notification Watcher: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
maj 10 18:21:04 pi-MS-7A34 indicator-multi[2064]: Unable to connect to the Notification Watcher: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
maj 10 18:21:04 pi-MS-7A34 indicator-multi[2064]: Unable to connect to the Notification Watcher: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
maj 10 18:21:04 pi-MS-7A34 indicator-multi[2064]: Unable to connect to the Notification Watcher: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
maj 10 18:21:04 pi-MS-7A34 indicator-multi[2064]: Unable to connect to the Notification Watcher: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
maj 10 18:21:04 pi-MS-7A34 indicator-multi[2064]: Unable to connect to the Notification Watcher: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
maj 10 18:21:04 pi-MS-7A34 indicator-multi[2064]: Unable to connect to the Notification Watcher: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
maj 10 18:21:04 pi-MS-7A34 indicator-multi[2064]: Unable to connect to the Notification Watcher: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
maj 10 18:21:04 pi-MS-7A34 indicator-multi[2064]: Unable to connect to the Notification Watcher: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
maj 10 18:21:04 pi-MS-7A34 indicator-multi[2064]: Unable to connect to the Notification Watcher: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
maj 10 18:21:04 pi-MS-7A34 indicator-multi[2064]: Unable to connect to the Notification Watcher: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
maj 10 18:21:04 pi-MS-7A34 indicator-multi[2064]: Unable to connect to the Notification Watcher: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
maj 10 18:21:04 pi-MS-7A34 indicator-multi[2064]: Unable to connect to the Notification Watcher: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
maj 10 18:21:04 pi-MS-7A34 indicator-multi[2064]: Unable to connect to the Notification Watcher: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
maj 10 18:21:04 pi-MS-7A34 indicator-multi[2064]: Unable to connect to the Notification Watcher: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
maj 10 18:21:05 pi-MS-7A34 org.gnome.Shell.desktop[3389]: current session already has an ibus-daemon.
maj 10 18:39:29 pi-MS-7A34 gnome-system-mo[3813]: Allocating size to gnome-system-monitor 0x55abe73522b0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
maj 10 18:39:33 pi-MS-7A34 gnome-system-mo[3813]: Allocating size to gnome-system-monitor 0x55abe73522b0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?