search for: loginctl

Hi list, I installed on my workstation C8.1 (1911) and performed a minimal install and then installed XFCE from EPEL. I noticed a strange behaviour (don't know if this is the wanted default). If I try ,from normal user shell, to run command like "reboot" or "shutdown -h now" system will reboot/shutdown. This happens on tty console, on xfce terminal and ssh session.

I just updated a system - as in minutes ago, and log back in after it reboots, and this is in dmesg: [ 88.202272] systemd-readahead[484]: open(/var/tmp/dracut.fP4yj1/initramfs/usr/bin/loginctl) failed: Too many levels of symbolic links [ 88.202515] systemd-readahead[484]: open(/var/tmp/dracut.fP4yj1/initramfs/usr/lib/systemd/system/dracut-emergency.service) failed: Too many levels of symbolic links Anyone know what this is - some weird bug, a garbage message? mark

...able to shutdown the system > without privileges. > > This is a bug or a wanted default? So, as you figured out from the polkit setting - "active" user's (i.e. with a "seat") have access to shut a machine down. Now to figure out who has a seat - and you use "loginctl" to see that. For e.g. from my non-privileged user logged into my CentOS 8.1 VM via ssh: $ loginctl SESSION UID USER SEAT TTY 1 ##### user it shows that I don't have a "seat" and so: $ shutdown -h now Failed to set wall message, ignoring: Connection timed out Failed...

...computers but the XGL project > is too outdated so i can't use it anymore. > > How can i make a multiseatcomputer with more then one user on one card with > systemd? I have asked already to the makers of systemd but they said it's a > kernel problem. > > With Systemd loginctl and the nouveau drivers you have this: > > ?/sys/devices/pci0000:00/0000:00:03.1/0000:08:00.0/drm/card0 > ?? ???? ? ? [MASTER] drm:card0 > ?? ???? ? ? > ??/sys/devices/pci0000:00/0000:00:03.1/0000:08:00.0/drm/card0/card0-DVI-D-1 > ?? ???? ? ? ? [MASTER] drm:card0-DVI-D-1 > ??...

...te: > On Wed, Jun 07, 2017 at 10:10:14AM -0400, m.roth at 5-cent.us wrote: >> I just updated a system - as in minutes ago, and log back in after it >> reboots, and this is in dmesg: >> [ 88.202272] systemd-readahead[484]: >> open(/var/tmp/dracut.fP4yj1/initramfs/usr/bin/loginctl) failed: Too many >> levels of symbolic links >> [ 88.202515] systemd-readahead[484]: >> open(/var/tmp/dracut.fP4yj1/initramfs/usr/lib/systemd/system/dracut-emergency.service) >> failed: Too many levels of symbolic links >> Anyone know what this is - some weird bug,...

On Wed, Jun 07, 2017 at 10:10:14AM -0400, m.roth at 5-cent.us wrote: > I just updated a system - as in minutes ago, and log back in after it > reboots, and this is in dmesg: > [ 88.202272] systemd-readahead[484]: > open(/var/tmp/dracut.fP4yj1/initramfs/usr/bin/loginctl) failed: Too many > levels of symbolic links > [ 88.202515] systemd-readahead[484]: > open(/var/tmp/dracut.fP4yj1/initramfs/usr/lib/systemd/system/dracut-emergency.service) > failed: Too many levels of symbolic links > Anyone know what this is - some weird bug, a garbage message?...

...Jun 07, 2017 at 10:10:14AM -0400, m.roth at 5-cent.us wrote: >>> I just updated a system - as in minutes ago, and log back in after it >>> reboots, and this is in dmesg: >>> [ 88.202272] systemd-readahead[484]: >>> open(/var/tmp/dracut.fP4yj1/initramfs/usr/bin/loginctl) failed: Too many >>> levels of symbolic links >>> [ 88.202515] systemd-readahead[484]: >>> open(/var/tmp/dracut.fP4yj1/initramfs/usr/lib/systemd/system/dracut-emergency.service) >>> failed: Too many levels of symbolic links >>> Anyone know what this i...

On 06/07/2017 09:10 AM, m.roth at 5-cent.us wrote: > I just updated a system - as in minutes ago, and log back in after it > reboots, and this is in dmesg: > [ 88.202272] systemd-readahead[484]: > open(/var/tmp/dracut.fP4yj1/initramfs/usr/bin/loginctl) failed: Too many > levels of symbolic links > [ 88.202515] systemd-readahead[484]: > open(/var/tmp/dracut.fP4yj1/initramfs/usr/lib/systemd/system/dracut-emergency.service) > failed: Too many levels of symbolic links > > Anyone know what this is - some weird bug, a garbage mess...

...stub_open` (WCHAN column in `top`; status is `D` — “uninterruptible sleep”). I can’t even `kill -9` them: the command succeeds but nothing happens. The first app to hang seems to be the screen locker; it locks the session but fails to present anything on the screen, so I have to go to VT2 and use `loginctl`. But VT switch becomes unreliable: switching from X to console succeeds at second attempt (while switching back seems to succeed always). Also I just found one app hanging in `nouveau_drm_preclose` (`D` too), consuming zero RAM. (pid=6455, noticed in the log) It’s strange but already running app...

...System: Arch Linux KDE Plasma Version: 5.14.5 Qt Version: 5.12.1 KDE Frameworks Version: 5.54.0 Kernel Version: 4.20.6-arch1-1-ARCH Graphics Card: NVIDIA GeForce GT 650M Plasma locks up after splash screen, and it is sometimes (but not always) possible to switch to tty2 and kill the session using loginctl. The magic SysRq keys Alt+SysRq+REISUB and Alt+SysRq+REISUO always work though. This seems to be a problem related to acceleration because adding the 'nouveau.noaccel=1' kernel parameter solves the problem, but disables some desktop effects as well. -- You are receiving this mail because...

https://bugs.freedesktop.org/show_bug.cgi?id=105626 Bug ID: 105626 Summary: BUG: unable to handle kernel NULL pointer dereference at 0000000000000040 Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium

...77 - btrfs-find-root 100755 245368 0:0 298 - chacl 100755 14752 0:0 361 - ntfswipe 100755 47752 0:0 408 - zless 100755 2037 0:0 340 - mknod 100755 64496 0:0 348 - ntfs-3g 104755 142032 0:0 385 - systemd-notify 100755 35248 0:0 333 - loginctl 100755 453848 0:0 305 - date 100755 68464 0:0 311 - egrep 100755 28 0:0 284 - btrfstune 100755 249464 0:0 367 - readlink 100755 39632 0:0 377 - sync 100755 31408 0:0 403 - zdiff 100755 5764 0:0 325 - kill...

...pfiles 100755 133704 0:0 344 - mountpoint 100755 14768 0:0 314 - findmnt 100755 49576 0:0 381 - systemd-escape 100755 39344 0:0 301 - chown 100755 64368 0:0 336 - lsblk 100755 77280 0:0 323 - ip 100755 376192 0:0 333 - loginctl 100755 453848 0:0 355 - ntfsfallocate 100755 34928 0:0 379 l systemd 120777 20 0:0 -> 5\x12 289 l bzegrep 120777 6 0:0 -> \x19\v 308 - dir 100755 126584 0:0 291 l bzfgrep 120777 6 0:0 -> \x1c\v 388 - tailf...