Bug #17294
Double-check journalctl output in 4.1
Start date:
Due date:
% Done:
0%
Description
Skipping things related to spice or floppies, here are the most important messages in journalctl (priority=3):
déc. 03 00:56:08 amnesia gdm-password][2373]: PAM unable to dlopen(pam_gnome_keyring.so): /lib/security/pam_gnome_keyring.so: cannot open shared object file: No such file or directory
déc. 03 00:56:08 amnesia gdm-password][2373]: PAM adding faulty module: pam_gnome_keyring.so
déc. 03 00:56:12 amnesia systemd-localed[2227]: Failed to issue method call: Unit systemd-vconsole-setup.service not found.
déc. 03 00:56:12 amnesia systemd-localed[2227]: Failed to convert keymap data: No such file or directory
Nothing seems like that should be blocking the release, but I thought I’d file this ticket just to be extra sure.
At a lower priority (4), there are some more things.
udisksd is very chatty, for all loop devices:
déc. 03 00:55:28 amnesia udisksd[1032]: Error determining whether device '/dev/loop12' seems to be encrypted: Failed to read device (g-bd-crypto-error-quark, 0)
plus at the beginning:
déc. 03 00:55:28 amnesia udisksd[1032]: failed to load module mdraid: libbd_mdraid.so.2: cannot open shared object file: No such file or directory
déc. 03 00:55:28 amnesia udisksd[1032]: Failed to load the 'mdraid' libblockdev plugin
Skipping Xorg logs and so on, more things from the desktop side:
déc. 03 00:56:16 amnesia gnome-keyring-ssh.desktop[2784]: gnome-keyring-daemon: insufficient process capabilities, insecure memory might get used
déc. 03 00:56:16 amnesia gnome-keyring-pkcs11.desktop[2782]: gnome-keyring-daemon: insufficient process capabilities, insecure memory might get used
déc. 03 00:56:16 amnesia gnome-keyring-secrets.desktop[2783]: gnome-keyring-daemon: insufficient process capabilities, insecure memory might get used
déc. 03 00:56:16 amnesia org.gnome.Shell.desktop[2795]: can't load /usr/lib/x86_64-linux-gnu/spa/support/libspa-support.so: /usr/lib/x86_64-linux-gnu/spa/support/libspa-support.so: Ne peut ouvrir le fichier d'objet partagé: Aucun fichier ou dossier de ce type
déc. 03 00:56:16 amnesia /usr/lib/gdm3/gdm-x-session[2633]: (II) modeset(0): Disabling kernel dirty updates, not required.
déc. 03 00:56:18 amnesia gnome-shell[2795]: g_dir_open_with_errno: assertion 'path != NULL' failed
déc. 03 00:56:18 amnesia gnome-shell[2795]: g_filename_to_utf8: assertion 'opsysstring != NULL' failed
déc. 03 00:56:18 amnesia gnome-shell[2795]: g_dir_open_with_errno: assertion 'path != NULL' failed
déc. 03 00:56:18 amnesia gnome-shell[2795]: g_filename_to_utf8: assertion 'opsysstring != NULL' failed
déc. 03 00:56:20 amnesia gsd-sharing[2920]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit gnome-user-share-webdav.service not loaded.
déc. 03 00:56:20 amnesia gsd-sharing[2920]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit rygel.service not loaded.
déc. 03 00:56:20 amnesia gsd-sharing[2920]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit gnome-remote-desktop.service not loaded.
déc. 03 00:56:20 amnesia gsd-sharing[2920]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit vino-server.service not loaded.
déc. 03 00:56:20 amnesia gsd-xsettings[2923]: Failed to get current display configuration state: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.gnome.Mutter.DisplayConfig" does not exist
déc. 03 00:56:20 amnesia spice-vdagent[3021]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
déc. 03 00:56:20 amnesia gnome-session-binary[2672]: WARNING: App 'spice-vdagent.desktop' exited with code 1
déc. 03 00:56:21 amnesia gsd-media-keys[2950]: g_variant_get_va: assertion 'value != NULL' failed
déc. 03 00:56:21 amnesia gsd-media-keys[2950]: g_variant_unref: assertion 'value != NULL' failed
déc. 03 00:56:22 amnesia gsd-media-keys[2950]: g_variant_get_va: assertion 'value != NULL' failed
déc. 03 00:56:22 amnesia gsd-media-keys[2950]: g_variant_unref: assertion 'value != NULL' failed
déc. 03 00:56:23 amnesia /usr/lib/gdm3/gdm-x-session[1807]: (WW) xf86CloseConsole: KDSETMODE failed: Input/output error
déc. 03 00:56:23 amnesia /usr/lib/gdm3/gdm-x-session[1807]: (WW) xf86CloseConsole: VT_GETMODE failed: Input/output error
déc. 03 00:56:23 amnesia /usr/lib/gdm3/gdm-x-session[1807]: (WW) xf86CloseConsole: VT_ACTIVATE failed: Input/output error
déc. 03 00:56:23 amnesia /usr/lib/gdm3/gdm-x-session[1807]: (II) Server terminated successfully (0). Closing log file.
déc. 03 00:56:23 amnesia systemd[1738]: xdg-permission-store.service: Main process exited, code=killed, status=9/KILL
déc. 03 00:56:23 amnesia systemd[1738]: xdg-permission-store.service: Failed with result 'signal'.
déc. 03 00:56:23 amnesia systemd[1738]: pulseaudio.service: Main process exited, code=killed, status=9/KILL
déc. 03 00:56:23 amnesia systemd[1738]: pulseaudio.service: Failed with result 'signal'.
déc. 03 00:56:23 amnesia gsd-media-keys[2950]: g_variant_get_va: assertion 'value != NULL' failed
déc. 03 00:56:23 amnesia gsd-media-keys[2950]: g_variant_unref: assertion 'value != NULL' failed
déc. 03 00:56:23 amnesia systemd[1]: user@112.service: Main process exited, code=killed, status=9/KILL
déc. 03 00:56:24 amnesia gsd-media-keys[2950]: g_variant_get_va: assertion 'value != NULL' failed
déc. 03 00:56:24 amnesia gsd-media-keys[2950]: g_variant_unref: assertion 'value != NULL' failed
déc. 03 00:56:29 amnesia gsd-color[2947]: failed to get edid: unable to get EDID for output
déc. 03 00:56:29 amnesia gsd-color[2947]: unable to get EDID for xrandr-Virtual-1: unable to get EDID for output
déc. 03 00:56:31 amnesia org.gnome.Nautilus[2669]: Failed to register: Unable to acquire bus name 'org.gnome.Nautilus'
déc. 03 00:56:32 amnesia openpgp-applet[3027]: gdk_window_thaw_toplevel_updates: assertion 'window->update_and_descendants_freeze_count > 0' failed
Subtasks
Related issues
Related to Tails - Bug #17351: udisksd reports tons of errors about failure to determine whether loop devices seem to be encrypted | Confirmed |
History
#1 Updated by intrigeri 2019-12-12 07:22:24
- Status changed from Confirmed to Resolved
Thank you. I’ve double-checked and all this is expected (and does not differ substantially from 4.0).
#2 Updated by intrigeri 2019-12-15 10:14:33
- related to Bug #17351: udisksd reports tons of errors about failure to determine whether loop devices seem to be encrypted added