Bug#806256: libpam-systemd: log out from a TTY and your X input devices get lost!

Package: bash Version: 5.1-2+b1 Followup-For: Bug #806256 Hi. This bug seems the same as "fixed" bugs #805605 and #810660, which are definitely not fixed yet. The freeze is caused by vt switch performed by 'clear_console', and the commited "fix" just changed vt (choosed for switch) from 1 and 2

Bug#806256: libpam-systemd: log out from a TTY and your X input devices get lost!

On Mon, 12 Mar 2018 23:45:44 +0100 Michael Biebl wrote: [...] > Am 12.03.2018 um 23:16 schrieb Francesco Poli: [...] > > I've just performed the test, after commenting out the three above > > quoted lines. > > The bug was not triggered. > > Thanks for testing. Thanks to you for investigating

Bug#806256: libpam-systemd: log out from a TTY and your X input devices get lost!

Am 12.03.2018 um 23:45 schrieb Michael Biebl: > Am 12.03.2018 um 23:16 schrieb Francesco Poli: >> It really seems that the bug is caused by some interaction with >> clear_console ... > > I'm going to reassing to bash and merge with > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791342 > >

Bug#806256: libpam-systemd: log out from a TTY and your X input devices get lost!

Control: reassign -1 bash Control: forcemerge 791342 -1 Am 12.03.2018 um 23:16 schrieb Francesco Poli: > On Sun, 11 Mar 2018 20:11:03 +0100 Michael Biebl wrote: > >> Am 11.03.2018 um 19:12 schrieb Francesco Poli: >> >>> My ~/.bash_logout is attached, but it's nothing special: it should be >>>

Bug#806256: libpam-systemd: log out from a TTY and your X input devices get lost!

On Sun, 11 Mar 2018 20:11:03 +0100 Michael Biebl wrote: > Am 11.03.2018 um 19:12 schrieb Francesco Poli: > > > My ~/.bash_logout is attached, but it's nothing special: it should be > > identical to the one provided by the bash package in /etc/skel/ > > Can you comment out / remove the following

Bug#806256: libpam-systemd: log out from a TTY and your X input devices get lost!

Am 11.03.2018 um 19:12 schrieb Francesco Poli: > My ~/.bash_logout is attached, but it's nothing special: it should be > identical to the one provided by the bash package in /etc/skel/ Can you comment out / remove the following three lines: if [ "$SHLVL" = 1 ]; then [ -x

Bug#806256: libpam-systemd: log out from a TTY and your X input devices get lost!

Am 25.11.2015 um 22:20 schrieb Francesco Poli (wintermute): > Package: libpam-systemd > Version: 228-2 > Severity: normal > > Hello, > I noticed a weird bug that is possibly caused by libpam-systemd. > > Steps to reproduce (on a box with systemd as PID 1 process): > > 0) login on TTY1

Bug#806256: libpam-systemd: log out from a TTY and your X input devices get lost!

Hello, I found that this bug should be related to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885318, something is wrong with bash clear_console, you can test that by executing clear_console in the tty instead of exiting from logging out from it, and that should reproduce the problem. Best

Bug#806256: libpam-systemd: log out from a TTY and your X input devices get lost!

Hello, I am also experiencing the same problem and can consistently reproduce it on both my laptop and desktop, which are both running Debian Stretch. I was able to reproduce a similar problem (x11 crashes instead of no input) in a qemu virtual machine, but for some reason it's not crashing

Bug#806256: libpam-systemd: log out from a TTY and your X input devices get lost!

Control: found -1 systemd/234-2.3 On Sat, 31 Dec 2016 16:10:13 +0100 Francesco Poli wrote: [...] > On Fri, 30 Dec 2016 19:37:48 +0100 Michael Biebl wrote: > > > On Sat, 13 Feb 2016 22:02:02 +0100 Francesco Poli > > wrote: > [...] > > > Hello again, > > > have you

Bug#806256: libpam-systemd: log out from a TTY and your X input devices get lost!

Control: found -1 systemd/232-8 On Fri, 30 Dec 2016 19:37:48 +0100 Michael Biebl wrote: > On Sat, 13 Feb 2016 22:02:02 +0100 Francesco Poli > wrote: [...] > > Hello again, > > have you found a way to reproduce the bug? > > > > Unfortunately I have not. Can you

Bug#806256: libpam-systemd: log out from a TTY and your X input devices get lost!

On Sat, 13 Feb 2016 22:02:02 +0100 Francesco Poli wrote: > Control: found -1 systemd/228-6 > > > On Sun, 29 Nov 2015 01:05:44 +0100 Michael Biebl wrote: > > > Am 28.11.2015 um 19:23 schrieb Francesco Poli: > > > > > Please tell me whether you need any further

Bug#806256: libpam-systemd: log out from a TTY and your X input devices get lost!

Control: found -1 systemd/228-6 On Sun, 29 Nov 2015 01:05:44 +0100 Michael Biebl wrote: > Am 28.11.2015 um 19:23 schrieb Francesco Poli: > > > Please tell me whether you need any further information in order to > > investigate. Otherwise, please drop the moreinfo tag. > > So far I don't know

Bug#806256: libpam-systemd: log out from a TTY and your X input devices get lost!

On Tue, 1 Dec 2015 11:23:45 -0300 Felipe Sateler wrote: [...] > Upstream claims the problem is either X or the graphics driver: > > https://github.com/systemd/systemd/issues/2061 > > (Not exactly the same reproducer, but similar). Hello Felipe, thanks for your comment. However, the upstream

Bug#806256: libpam-systemd: log out from a TTY and your X input devices get lost!

On 1 December 2015 at 10:49, Brian Potkin wrote: > On Mon 30 Nov 2015 at 23:04:37 +0100, Francesco Poli wrote: > >> I am more and more suspecting that this issue is ultimately caused by >> systemd-logind / libpam-systemd... > > I have installed Jessie without any tasks.

Bug#806256: libpam-systemd: log out from a TTY and your X input devices get lost!

On Mon 30 Nov 2015 at 23:04:37 +0100, Francesco Poli wrote: > I am more and more suspecting that this issue is ultimately caused by > systemd-logind / libpam-systemd... I have installed Jessie without any tasks. The minimum for a working X on this machine is xserver-xorg-video-nouveau.

Bug#806256: libpam-systemd: log out from a TTY and your X input devices get lost!

On Mon, 30 Nov 2015 16:52:26 + Brian Potkin wrote: > On Sun 29 Nov 2015 at 18:19:18 +, Brian Potkin wrote: [...] > > I can reproduce the problem and experience almost the same behaviour as > > Francesco. For me, it only happens when X is started on tty1 but Ctrl+D > > on any other

Bug#806256: libpam-systemd: log out from a TTY and your X input devices get lost!

On Sun 29 Nov 2015 at 18:19:18 +, Brian Potkin wrote: > On Sun 29 Nov 2015 at 01:05:44 +0100, Michael Biebl wrote: > > > Am 28.11.2015 um 19:23 schrieb Francesco Poli: > > > > > Please tell me whether you need any further information in order to > > > investigate. Otherwise, please drop the

Bug#806256: libpam-systemd: log out from a TTY and your X input devices get lost!

On Sun 29 Nov 2015 at 01:05:44 +0100, Michael Biebl wrote: > Am 28.11.2015 um 19:23 schrieb Francesco Poli: > > > Please tell me whether you need any further information in order to > > investigate. Otherwise, please drop the moreinfo tag. > > So far I don't know yet, how I can reproduce the

Bug#806256: libpam-systemd: log out from a TTY and your X input devices get lost!

On Fri, 27 Nov 2015 00:16:45 +0100 Francesco Poli wrote: > On Thu, 26 Nov 2015 00:06:56 +0100 Michael Biebl wrote: [...] > > Does it make a difference if you use > > a different window manager? > > I'll try and find the time to install a different window manager / > desktop environment and test

Bug#806256: libpam-systemd: log out from a TTY and your X input devices get lost!

Am 28.11.2015 um 19:23 schrieb Francesco Poli: > Please tell me whether you need any further information in order to > investigate. Otherwise, please drop the moreinfo tag. So far I don't know yet, how I can reproduce the problem. So I'll keep the moreinfo tag. -- Why is it that all of the

Bug#806256: libpam-systemd: log out from a TTY and your X input devices get lost!

On Fri, 27 Nov 2015 00:29:33 +0100 Michael Biebl wrote: > Am 27.11.2015 um 00:16 schrieb Francesco Poli: [...] > > Could you please specify the exact steps needed to obtain the log you > > would like to see? > > A Xorg.0.log and a journalctl -alb log might be helpful. These two logs are

Bug#806256: libpam-systemd: log out from a TTY and your X input devices get lost!

On Thu, 26 Nov 2015 00:06:56 +0100 Michael Biebl wrote: > Am 11/25/2015 um 10:20 PM schrieb Francesco Poli (wintermute): > > Package: libpam-systemd > > Version: 228-2 > > Severity: normal > > > > Hello, > > I noticed a weird bug that is possibly caused by libpam-systemd. > > > > Steps to

Bug#806256: libpam-systemd: log out from a TTY and your X input devices get lost!

Am 27.11.2015 um 00:16 schrieb Francesco Poli: > On Thu, 26 Nov 2015 00:06:56 +0100 Michael Biebl wrote: > >> Am 11/25/2015 um 10:20 PM schrieb Francesco Poli (wintermute): >>> Package: libpam-systemd >>> Version: 228-2 >>> Severity: normal >>> >>> Hello, >>> I noticed a weird bug that is

Bug#806256: libpam-systemd: log out from a TTY and your X input devices get lost!

Am 11/25/2015 um 10:20 PM schrieb Francesco Poli (wintermute): > Package: libpam-systemd > Version: 228-2 > Severity: normal > > Hello, > I noticed a weird bug that is possibly caused by libpam-systemd. > > Steps to reproduce (on a box with systemd as PID 1 process): > 1..7 Tried those steps

Bug#806256: libpam-systemd: log out from a TTY and your X input devices get lost!

Package: libpam-systemd Version: 228-2 Severity: normal Hello, I noticed a weird bug that is possibly caused by libpam-systemd. Steps to reproduce (on a box with systemd as PID 1 process): 0) login on TTY1 (virtual terminal 1) as a regular user 1) start an X session with $ startx

Bug#806256: libpam-systemd: log out from a TTY and your X input devices get lost!

Control: found -1 systemd/227-2 On Wed, 25 Nov 2015 22:20:05 +0100 Francesco Poli (wintermute) wrote: [...] > I noticed this bug some days ago with libpam-systemd/227-2: I waited > for version 228-2 to migrate to testing, before reporting the bug. > After reproducing the same exact misbehavior