New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 668779 link

Starred by 2 users

Issue metadata

Status: Archived
Owner: ----
Closed: Sep 13
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug-Regression



Sign in to add a comment

kde environment,does not autostart

Reported by episteme...@gmail.com, Nov 26 2016

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64; rv:50.0) Gecko/20100101 Firefox/50.0

Steps to reproduce the problem:
1. install hangouts
2. minimize chrome in systray
3. close kde session
4. open kde session
chrome is not started thus hangouts is not started

What is the expected behavior?
hangouts is started

What went wrong?
in the contrary of opensuse 13.1 x86_64
in kde settings in "start/stop" in "automatic start"
there is no chrome task to start
see 13.1_autostart.png
and 42.2_autostart.png

Did this work before? N/A 

Chrome version: 54.0.2840.100 (Build officiel) (64 bits)  Channel: stable
OS Version: 
Flash Version: 

opensuse 42.2 x86_64
kde environment
 
/13.1_autostart.png
105 KB View Download
/42.2_autostart.png
79.9 KB View Download

Comment 1 by ajha@chromium.org, Nov 27 2016

Labels: M-54
Cc: kkaluri@chromium.org
Components: UI
Labels: Needs-Feedback Needs-Milestone
Unable to reproduce this issue on OpenSuse 42.3 with chrome #54.0.2840.100 & #62.0.3202.75

Steps Followed :

1. Installed chrome and logged in
2. Installed google hangouts extension
3. Logged out from machine
4. And again logged into machine

Observed that chrome is launching as expected for both chrome versions

episteme.promeneur@ Could you please retry the same scenario on latest chrome stable and and let us know your observations.

Comment 3 Deleted

Project Member

Comment 4 by sheriffbot@chromium.org, Nov 2 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "kkaluri@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Cc: sc00335...@techmahindra.com
Labels: Triaged-ET Needs-Feedback
@Reporter: Could you please respond to comment#2 and let us know the the behaviour on latest stable 62.0.3202.75. 

Thanks!
OpenSuse 42.3 with chrome #62.0.3202.89

problem still there.
Project Member

Comment 7 by sheriffbot@chromium.org, Nov 8 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "sc00335628@techmahindra.com" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Cc: vamshi.k...@techmahindra.com
Labels: TE-NeedsTriageFromHYD
As ET team doesn't have OpenSuse 42.3, hence requesting some one from TE-Hyd team to have a look into this issue for further investigation. Adding label TE-NeedsTriageFromHYD.

Thanks!
Cc: pnangunoori@chromium.org
Labels: Needs-Feedback
episteme.promeneur@ -- Could you please update your Chrome to latest stable #64.0.3282.119 and let us know your observations.

Thanks in advance!
chrome Version 64.0.3282.140 (Build officiel) (64 bits)

problem still there
Project Member

Comment 11 by sheriffbot@chromium.org, Feb 6 2018

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "pnangunoori@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Cc: sandeepkumars@chromium.org
Labels: -TE-NeedsTriageFromHYD TE-NeedsTriageHelp Needs-Feedback
Adding triage help label as we are not able to reproduce the from our end.

@episteme: Request you to update Chrome to latest version #65.0.3325.146 and check the behavior?

Thanks!!
Status: Archived (was: Unconfirmed)
Archiving old bugs that haven't been actively assigned in over 180 days.

If you feel this issue should still be addressed, feel free to reopen it or to file a new issue. Thanks!
Archiving old bugs that haven't been actively assigned in over 180 days.

If you feel this issue should still be addressed, feel free to reopen it or to file a new issue. Thanks!

Sign in to add a comment