Bug#706466: general: graphical applications launch in wrong session
Package: general
Severity: normal
Dear Maintainer,
* What led up to the situation?
Routine operation
* What exactly did you do (or not do) that was effective (or
ineffective)?
See below. Logged into the same user account locally and remotely.
* What was the outcome of this action?
See below. Browser launched in wrong login session.
* What outcome did you expect instead?
See below. I expected the browser to open in the session from which it was
launched
! IMPORTANT ! I don't know if this is a Debian bug or a Google Chrome bug.
I'm reporting it here to allow you to make that determination. I have
reported this to Google as well, with no response.
Set-up:
1. Log in locally (gnome non-root login)
2. Install latest Google Chrome, if not already installed
3. Log in to the same system remotely with the same login (I use NetSarang
XManager 4 from a Windows system)
Steps to reproduce:
1. Launch Google Chrome from the remote session.
Result:
1. Google Chrome launches in the local session rather than the remote
session.
Expected:
1. Google Chrome should always launch in the session from which it was
launched.
Notes:
1. The behavior changes depending on which session logs in first. For
example, if the remote session logs in first, when Google Chrome is launched
from the local session, the browser opens in the remote session. That is,
the browser always and only opens in the first established session.
2. Again, this might be a Google Chrome bug, not a Debian bug. I have
reported it to Google as well, with no response from Google.
3. This is potentially a security issue, albeit a minor one since, as far as
I know, the same user would need to be logged into both accounts at the same
time.
-- System Information:
Debian Release: 7.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-4-686-pae (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Reply to: