![]() Jun 09 20:34:16 vischium systemd-coredump: Process 634 (gnome-shell) of user 120 dumped core. ![]() Jun 09 20:34:15 vischium at-spi-bus-launcher: after 21 requests (21 known processed) with 0 events remaining. Jun 09 20:34:15 vischium at-spi-bus-launcher: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":1024" Jun 09 20:34:15 vischium gnome-session-binary: Unrecoverable failure in required component Jun 09 20:34:15 vischium gnome-session-binary: WARNING: Application '' killed by signal 11 Jun 09 20:34:15 vischium polkitd: Unregistered Authentication Agent for unix-session:c1 (system bus name :1.30, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_GB.UTF-8) (disconnected from bus) Jun 09 20:34:15 vischium gnome-session: gnome-session-binary: WARNING: Application '' killed by signal 11 Jun 09 20:34:15 vischium : (EE) failed to read Wayland events: Broken pipe Jun 09 20:34:15 vischium systemd: Started Process Core Dump (PID 1829/UID 0). Jun 09 20:34:15 vischium systemd: Created slice system-systemd\x2dcoredump.slice. Jun 09 20:34:15 vischium gnome-shell: Failed to set CRTC mode 1920x1080: Permission denied Jun 09 20:34:15 vischium : Errors from xkbcomp are not fatal to the X server Jun 09 20:34:15 vischium : > Internal error: Could not resolve keysym XF86Keyboard Jun 09 20:34:15 vischium : > Internal error: Could not resolve keysym XF86RFKill Jun 09 20:34:15 vischium : > Internal error: Could not resolve keysym XF86WWAN Jun 09 20:34:15 vischium : > This warning only shows for the first high keycode. Jun 09 20:34:15 vischium : > Warning: Unsupported high keycode 372 for name ignored Jun 09 20:34:15 vischium : > X11 cannot support keycodes above 255. Jun 09 20:34:15 vischium : > Warning: Unsupported maximum keycode 374, clipping. Jun 09 20:34:15 vischium : The XKEYBOARD keymap compiler (xkbcomp) reports: Jun 09 20:34:15 vischium gnome-shell: Failed to set power save mode for output eDP-1: Permission denied Jun 09 20:34:15 vischium gnome-shell: Failed to apply DRM plane transform 0: Permission denied ![]() Jun 09 20:34:14 vischium kernel: rfkill: input handler enabled Jun 09 20:34:14 vischium systemd: Started Show Plymouth Boot Screen. Jun 09 20:34:14 vischium systemd: Received SIGRTMIN 20 from PID 1824 (plymouthd). Jun 09 20:34:14 vischium systemd: Starting Show Plymouth Boot Screen. Jun 09 20:34:14 vischium systemd: Started Setup Virtual Console. Jun 09 20:34:14 vischium systemd: Starting Setup Virtual Console. Jun 09 20:34:14 vischium sudo: pam_unix(sudo:session): session closed for user root Jun 09 20:34:13 vischium systemd: Reloading. I'm a GNOME user, and when using X, switching back to the proper VT is all that's needed, but when using Wayland, switching back causes the following messages in the journal and needs a restart of gdm to recover: Jun 09 20:34:13 vischium sudo: pam_unix(sudo:session): session opened for user root by (uid=0) Reloading systemd with systemctl daemon-reload triggers rvice, hence switching to the boot splash. Installationsgrund : Ausdrücklich installiertĪny idea what might be the culprit? It is working with exactly the same config files (apart from the video driver) on another pure intel laptop. In Konflikt mit : plymouth-git plymouth-legacy plymouth-nosystemd I have also 'quiet splash' in the grub kernel command line.īeschreibung : A graphical boot splash screen with kernel mode-setting support This also happens with the udev/plymouth hooks. HOOKS=(base systemd sd-plymouth autodetect modconf block filesystems keyboard fsck) Changes to this file will get overwritten during upgrades. Sometimes when rebooting I can see the breeze splash when shutting down.Ĭat /etc/plymouth/nf Distribution defaults. I must also add that displaying the themes worked beforehand without any problem. My graphic card is a radeon HD 6850M and, yes, I am including the radeon driver into the initramfs. Instead, I get the three squares from the standard theme. Since a few months (five or so) plymouth does not work with any other themes (in particular breeze) anymore. if cryptsetup isLuks $ creation failed, aborting." I try to solve this problem, maybe it can be for your reference:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |