Bug#812791: xserver-xorg-core: Kills DM controlled session when opening X from another tty
On Tue, Oct 04, 2016 at 11:43:07AM +0200, Agustin Martin wrote:
> On Wed, Sep 07, 2016 at 12:08:15PM +0200, Agustin Martin wrote:
> > On Wed, Jan 27, 2016 at 03:51:22PM +0100, Agustin Martin wrote:
> > > On Wed, Jan 27, 2016 at 08:29:21AM +0100, Julien Cristau wrote:
> > > > On Tue, Jan 26, 2016 at 16:51:27 +0100, Agustin Martin wrote:
> > > >
> > > > > Package: xserver-xorg-core
> > > > > Version: 2:1.17.3-2
> > > > > Severity: normal
> > > > >
> > > > > Dear Maintainers,
> > > > >
> > > > > I am having a strange problem apparently starting with 2:1.17.2-3.
> > > > >
> > > > > I often have a display-manager controlled X session for one user and open
> > > > > another X session in a free tty for a different user with startx.
> > > > >
> > > > > This has been working for a long time. However, after a recent testing
> > > > > upgrade including xserver-xorg-core 2:1.17.2-3 this started to fail
> > > > > (failure happened before in a sid box, but there were more upgrades to
> > > > > look when trying to locate which change might be responsible).
> > > > >
> > > > > When I have a display-mamager controlled X session and, without leaving the
> > > > > session, switch to a free tty, login as another user and start an X session
> > > > > with startx original X session gets killed and I am sent to DM greeter.
> > > > >
> > > > Please provide the log from both X processes.
> > >
> > > Hi, thanks for quick reply.
> > >
> > > Please find them attached.
> >
> > Hi,
> >
> > Just to add some additional info. This problem is happening not only with
> > the xserver-xorg-video-nouveau driver, but also if I remove it leaving the fbdev
> > or vesa drivers.
Hi, some funny info about this problem,
I am using a sysvinit box and it is currently suffering from
https://bugs.debian.org/844785 [systemd-shim not fully compatible with systemd 232]
and similar bugs against lightdm
#770885 lightdm: Restart, Suspend, Hibernate, Shut Down all greyed out and nonfunctional
#804165 lightdm: Options reboot,suspend,hibernate are all greyed out
The funny thing is that as soon as this systemd-shim bug reappeared my
original problem reported in this bug #812791 report become no longer present
when using "sysvinit"+"buggy systemd-shim".
I have booted with systemd to see what happens and my original problem
reappeared, cannot switch.
So, this may be related to interaction with policykit or friends, but apart
from that guess I am clueless.
Regards,
--
Agustin
Reply to: