search for: logind

...nsive. Running the following system OS: Fedora 25 64 bit Arch: 64-bit Graphics Card: GeForce GTX 660 Kernel: 4.10.15-200.fc25.x86_64 Nouveau Driver: xorg-x11-drv-nouveau-1.0.15-1.fc25.x86_64 Get the following Errors from dmesg [May28 11:56] nouveau 0000:01:00.0: gr: TRAP ch 6 [023f718000 systemd-logind[757]] [ +0.000011] nouveau 0000:01:00.0: gr: GPC1/PROP trap: 00000020 [RT_HEIGHT_OVERRUN] x = 1888, y = 1060, format = 2a, storage type = 0 [ +0.000884] nouveau 0000:01:00.0: gr: TRAP ch 6 [023f718000 systemd-logind[757]] [ +0.000010] nouveau 0000:01:00.0: gr: GPC1/PROP trap: 00000020 [RT_HEIGHT...

...annoying problem not sure where the root of it lies When running FLdigi it runs fine for about 10 mineuts then i start getting errors leading to a complete lock up that needs a power button to free it up i get the following [ 653.080497] nouveau 0000:01:00.0: fifo: DMA_PUSHER - ch 3 [systemd-logind[462]] get 00000d3a24 [ 653.081461] nouveau 0000:01:00.0: gr: DATA_ERROR 0000000c [INVALID_BITFIELD] [ 653.081473] nouveau 0000:01:00.0: gr: 00100000 [] ch 3 [003fa2a000 systemd-logind[462]] subc 3 [ 860.658821] nouveau 0000:01:00.0: fifo: DMA_PUSHER - ch 3 [systemd-logind[462]] get 00001b1f20 [...

On my Centos 7 update, into "journalctl -f" I have tons of this kind of message > feb 17 23:52:09 s-ispc.local systemd-logind[663]: Got message type=signal sender=:1.0 destination=n/a object=/org/freedesktop/systemd1/unit/php_2dfpm_2eservice interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=17152 reply_cookie=0 error=n/a > feb 17 23:52:09 s-ispc.local systemd-logind[663]: Got message type=signal...

...04 12:24:41 dashesy.wavelet kernel: nouveau 0000:01:00.0: Invalid PCI ROM header signature: expecting 0xaa55, got 0xffff Jul 09 09:59:48 dashesy.wavelet kernel: nouveau 0000:01:00.0: fifo: read fault at 0000260000 engine 00 [GR] client 01 [GPC0/T1_0] reason 02 [PTE] on channel 6 [007fb61000 systemd-logind[859]] Jul 09 09:59:48 dashesy.wavelet kernel: nouveau 0000:01:00.0: fifo: gr engine fault on channel 6, recovering... Jul 09 09:59:48 dashesy.wavelet kernel: nouveau 0000:01:00.0: gr: TRAP ch 6 [007fb61000 systemd-logind[859]] Jul 09 09:59:48 dashesy.wavelet kernel: nouveau 0000:01:00.0: gr: GPC0/T...

...ivating systemd to hand-off: service name='org.freedesktop.login1' unit='dbus-org.freedesktop.login1.service' Jan 21 16:10:50 linux7-7.mpc.local dbus[817]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out Jan 21 16:10:50 linux7-7.mpc.local systemd-logind[1221]: Failed to enable subscription: Failed to activate service 'org.freedesktop.systemd1': timed out Jan 21 16:10:50 linux7-7.mpc.local systemd-logind[1221]: Failed to fully start up daemon: Connection timed out Jan 21 16:10:50 linux7-7.mpc.local systemd[1]: systemd-logind.service: ma...

...y added in mesa 11.2. > I just upgraded to 11.2. I'm getting errors like this in the log: [ 5383.723240] nouveau 0000:09:00.0: fifo: read fault at 0000011000 engine 07 [PBDMA0] client 06 [HOST] reason 00 [PDE] on channel -1 [007f9ed000 unknown] [ 5398.722676] nouveau 0000:09:00.0: systemd-logind[30778]: failed to idle channel 2 [systemd-logind[30778]] [ 5413.722853] nouveau 0000:09:00.0: systemd-logind[30778]: failed to idle channel 2 [systemd-logind[30778]] and the display output in general is unreliable enough that I'm having trouble telling whether the performance is remotely reaso...

...to 11.2. I'm getting errors like this in the log: >> >> [ 5383.723240] nouveau 0000:09:00.0: fifo: read fault at 0000011000 >> engine 07 [PBDMA0] client 06 [HOST] reason 00 [PDE] on channel -1 >> [007f9ed000 unknown] >> [ 5398.722676] nouveau 0000:09:00.0: systemd-logind[30778]: failed to >> idle channel 2 [systemd-logind[30778]] >> [ 5413.722853] nouveau 0000:09:00.0: systemd-logind[30778]: failed to >> idle channel 2 [systemd-logind[30778]] >> >> and the display output in general is unreliable enough that I'm having >> trou...

How can I prevent the laptop from sleeping when the lid is closed. I tried messing with the settings in gnome-power-preferences but that doesn't seem to prevent it when no one is logged in. Any suggestions? Thanks, Dave

...I prevent the laptop from sleeping when the lid is closed. I tried > messing with the settings in gnome-power-preferences but that doesn't seem > to prevent it when no one is logged in. Any suggestions? > Thanks, > Dave With C7 that is caused by systemd. Somewhere in /etc/systemd/logind.conf there is a option about "suspend" or "lid" "grep Lid /etc/systemd/logind.conf" gives: logind.conf:#HandleLidSwitch=suspend logind.conf:#HandleLidSwitchDocked=ignore logind.conf:#LidSwitchIgnoreInhibited=yes "man 5 logind.conf" for further info on defau...

....258571] systemd[1]: Sent message type=signal sender=n/a destination=n/a object=/org/freedesktop/systemd1/unit/httpd_2eservice interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=436 reply_cookie=0 error=n/a [ 478.258971] systemd[1]: Got notification message for unit systemd-logind.service [ 478.258980] systemd[1]: systemd-logind.service: Got notification message from PID 821 (WATCHDOG=1) [ 478.258985] systemd[1]: systemd-logind.service: got WATCHDOG=1 What *is* all that garbage, and is there some way to turn it down to WARN and ERR messages? mark

...ice name='org.freedesktop.login1' >> unit='dbus-org.freedesktop.login1.service' >> Jan 21 16:10:50 linux7-7.mpc.local dbus[817]: [system] Failed to >> activate service 'org.freedesktop.systemd1': timed out >> Jan 21 16:10:50 linux7-7.mpc.local systemd-logind[1221]: Failed to >> enable subscription: Failed to activate service >> 'org.freedesktop.systemd1': timed out >> Jan 21 16:10:50 linux7-7.mpc.local systemd-logind[1221]: Failed to fully >> start up daemon: Connection timed out >> Jan 21 16:10:50 linux7-7.mpc.loc...

...25/162405.614008:ERROR:gl_surface_presentation_helper.cc(115)] GetVSyncParametersIfAvailable() failed! Eventually the display appears to have crashed, and the following log messages occurred: kernel: [514889.808652] nouveau 0000:02:00.0: fifo: PBDMA0: 04000000 [ACQUIRE] ch 6 [007f576000 systemd-logind[957]] subc 0 mthd 001c data 00001004 /usr/lib/gdm3/gdm-x-session[15566]: (**) Option "fd" "25" /usr/lib/gdm3/gdm-x-session[15566]: (II) event1 - (II) Power Button: (II) device removed /usr/lib/gdm3/gdm-x-session[15566]: (**) Option "fd" "28" /usr/lib/gdm3/gd...

...nected over a 10/100 Ethernet. All of us would prefer a gb Ethernet but this is what we have available. First, an extract from /var/log/messages showing the start and end times for virt-p2v-server, about 3 1/2 hours. [root at Fedora16-64P2V log]# tail /var/log/messages -c 1000 16-64P2V systemd-logind[704]: Removed session 16. Nov 22 19:04:46 Fedora16-64P2V systemd-logind[704]: New session 17 of user root. Nov 22 19:04:48 Fedora16-64P2V virt-v2v[1733]: p2v-server started. Nov 22 20:01:01 Fedora16-64P2V systemd-logind[704]: New session 18 of user root. Nov 22 20:01:02 Fedora16-64P2V systemd-login...

...o hand-off: service name='org.freedesktop.login1' > unit='dbus-org.freedesktop.login1.service' > Jan 21 16:10:50 linux7-7.mpc.local dbus[817]: [system] Failed to > activate service 'org.freedesktop.systemd1': timed out > Jan 21 16:10:50 linux7-7.mpc.local systemd-logind[1221]: Failed to > enable subscription: Failed to activate service > 'org.freedesktop.systemd1': timed out > Jan 21 16:10:50 linux7-7.mpc.local systemd-logind[1221]: Failed to fully > start up daemon: Connection timed out > Jan 21 16:10:50 linux7-7.mpc.local systemd[1]: syste...

...-locker is a simple locker (forked from gnome-screensaver) that aims to have simple, sane, secure defaults and be well integrated with the desktop while not carrying any desktop-specific dependencies. Technically, it relies on LightDM for locking and unlocking your session via ConsoleKit/UPower or logind/systemd. Release notes for 1.1.0 ======================= [Please note that this is a development release.] - Lock the session after the X11 screen saver kicks in === Call for translations === With this development release of light-locker, we're also asking for your translating help! We'v...

...g.freedesktop.login1' >>> unit='dbus-org.freedesktop.login1.service' >>> Jan 21 16:10:50 linux7-7.mpc.local dbus[817]: [system] Failed to >>> activate service 'org.freedesktop.systemd1': timed out >>> Jan 21 16:10:50 linux7-7.mpc.local systemd-logind[1221]: Failed to >>> enable subscription: Failed to activate service >>> 'org.freedesktop.systemd1': timed out >>> Jan 21 16:10:50 linux7-7.mpc.local systemd-logind[1221]: Failed to >>> fully >>> start up daemon: Connection timed out >>>...

.... I am on Ubuntu 18.04.3 LTS, tested on kernels 4.15/4.18/5.0, xserver-xorg-video-nouveau 1:1.0.15-2, libdrm-nouveau2 2.4.97-1ubuntu1~18.04.1 Have also tested it with xserver-xorg-video-nouveau-hwe-18.04 1:1.0.16-1~18.04.1 dmesg is full of these lines: [ 199.658774] nouveau 0000:04:00.0: systemd-logind[1352]: validate: -22 [ 199.658902] nouveau 0000:04:00.0: systemd-logind[1352]: fail set_domain [ 199.658905] nouveau 0000:04:00.0: systemd-logind[1352]: validating bo list [ 199.658907] nouveau 0000:04:00.0: systemd-logind[1352]: validate: -22 [ 200.075155] nouveau 0000:04:00.0: systemd-logind[...

...gt; I just upgraded to 11.2. I'm getting errors like this in the log: > > [ 5383.723240] nouveau 0000:09:00.0: fifo: read fault at 0000011000 > engine 07 [PBDMA0] client 06 [HOST] reason 00 [PDE] on channel -1 > [007f9ed000 unknown] > [ 5398.722676] nouveau 0000:09:00.0: systemd-logind[30778]: failed to > idle channel 2 [systemd-logind[30778]] > [ 5413.722853] nouveau 0000:09:00.0: systemd-logind[30778]: failed to > idle channel 2 [systemd-logind[30778]] > > and the display output in general is unreliable enough that I'm having > trouble telling whether the...

...e │ ├─17306 /usr/lib/systemd/systemd │ ├─machine.slice │ │ └─machine-lxc\x2dmycontainer.scope │ │ └─user.slice │ │ └─user-0.slice │ │ └─user@0.service │ │ └─17400 /usr/lib/systemd/systemd --user │ ├─system.slice │ │ ├─systemd-logind.service │ │ │ └─17373 /usr/lib/systemd/systemd-logind │ │ ├─dbus.service │ │ │ └─17372 /bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation │ │ ├─sshd.service │ │ │ └─17379 /usr/sbin/sshd -D │ │ └─systemd-journald.service │...

...is in the log: >>>> >>>> [ 5383.723240] nouveau 0000:09:00.0: fifo: read fault at 0000011000 >>>> engine 07 [PBDMA0] client 06 [HOST] reason 00 [PDE] on channel -1 >>>> [007f9ed000 unknown] >>>> [ 5398.722676] nouveau 0000:09:00.0: systemd-logind[30778]: failed to >>>> idle channel 2 [systemd-logind[30778]] >>>> [ 5413.722853] nouveau 0000:09:00.0: systemd-logind[30778]: failed to >>>> idle channel 2 [systemd-logind[30778]] >>>> >>>> and the display output in general is unreliable...