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

Issue 593098 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Chrome Start screen shortcut and App pane shortcut are broken on update to Chrome M49(49.0.2623.87)

Project Member Reported by pbomm...@chromium.org, Mar 8 2016

Issue description

Version: 49.0.2623.87
OS: Windows 8.1 

What steps will reproduce the problem?
(1) Install and launch Chrome 47.0.2526.111_chrome_installer.exe --chrome --multi-install --verbose-logging --do-not-launch-chrome --system-level 
(2) Make sure all the Shortcuts are launching Chrome properly
(3)Update to Chrome version 49.0.2623.87_47.0.2526.111_chrome_updater.exe --multi-install --verbose-logging --do-not-launch-chrome --system-level



What is the expected output?
Upon Chrome update to M49 all existing Chrome shortcuts should work normally.

What do you see instead?
When tried to launch Chrome from Start screen shortcut it doesn't get launched(Upon unpinning and repinning back works fine), Where in other case the Start screen Apps pane doesn't ahve Chrome shortcut icon and when tried to launch from there it doesn't get launched.

 
Cc: sshruthi@chromium.org anan...@chromium.org
Cc: grt@chromium.org
Owner: bcwh...@chromium.org
Please find the attached screenshot when I try to open the path of the shortcut after update.

Redirecting to bcshite@ based on offline chat with grt@.
Untitled.png
28.6 KB View Download
So far I saw this behavior from M47 --> M49 update, haven't observed the behavior on M48 --> M49. I will test further more and update the bug.
Status: WontFix (was: Assigned)
This is as expected.  There was a problem with M47.  M48 introduced the fix which allowed M49 to update the shortcuts.

Comment 5 by gab@chromium.org, Mar 8 2016

Status: Unconfirmed (was: WontFix)
Hmmm, the M47->M49 update (skipping M48) is known to temporarily break chrome://restart (or any other restart path). But it shouldn't break the Start Screen shortcut, @pbommana: does restarting Chrome fix it or is it permanently broken?
Gab restarting Chrome didn't fixed the issue, If you want to take further look at the issue please let me know I can share the VM details you can remote in.

Comment 7 by gab@chromium.org, Mar 9 2016

Status: Assigned (was: Unconfirmed)
That'd be great yes. Please share them with bcwhite and I can look at it with him.

If this isn't a self-healing issue I think we want to take a closer look at it.
Labels: Hotlist-ConOps
We are observing user feedback spike about this issue.

Please feel free to ping me in case you are looking for user feedback or data (like user environment, Installed version breakup etc).

Comment 9 by sshru...@google.com, Mar 16 2016

jainabhishek@, can you please go ahead and send the details to bcwhite@ and gab@? Can you guys please take a closer look and see if this is what we are expecting. Could you also send me details on the feedback spike, please?

Comment 10 by gab@chromium.org, Mar 17 2016

I'm not sure this is what we're seeing in conops.

The M47->M49 (skipping M48) update is only known to break the initial chrome restart, but not shortcuts should break, and manually clicking the shortcut should work as intended after the single failed relaunch.
Cc: fdoray@chromium.org
Cc: bcwh...@chromium.org
Owner: gab@chromium.org

Comment 13 by gab@chromium.org, Jun 27 2016

Labels: Needs-Feedback
Hey Prudhvi, I failed to get back to this in time, does this still repro? Or is it only when updating from M47? trying to assess whether we still care..?

Sign in to add a comment