[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#706466: marked as done (general: graphical applications launch in wrong session)

Your message dated Mon, 9 Dec 2013 15:45:52 +0100
with message-id <201312091545.53569.holger@layer-acht.org>
and subject line crystal ball broken
has caused the Debian Bug report #706466,
regarding general: graphical applications launch in wrong session
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
706466: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706466
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
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

--- End Message ---
--- Begin Message --- 
Hi,

closing this bug as the submitter didnt give more info when asked, so we can 
only guess whether this "Chrome" thing which isnt in Debian is too blame, or 
this "NetSarang XManager 4" thing which isnt in Debian neither or whether 
something from Debian is too blame. 

And this really hard with broken tools (see subject!) so I rather close this 
bug.


cheers,
	Holger

Attachment: signature.asc
Description: This is a digitally signed message part.


--- End Message ---
Reply to: