New issue
Advanced search Search tips

Issue 778890 link

Starred by 1 user

Issue metadata

Status: Duplicate
Owner: ----
Closed: Oct 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Native Printing causing ChromeOS to shut down

Reported by jeff.rol...@gmail.com, Oct 27 2017

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13) AppleWebKit/604.1.38 (KHTML, like Gecko) Version/11.0 Safari/604.1.38
Platform: 9766.85.0

Steps to reproduce the problem:
1. Settings
2. Advanced
3. Printing
4. Click on Printers and ChromeOS shuts down.

What is the expected behavior?
Should show native printing page of printers or ability to add printer.

What went wrong?
Configured two printers on Acer Chromebox.  Began getting the above results every time I try to access the Printers page.  I tried with a different account on same hardware, page displayed correctly.  Logged into original account on Chromebook and have same results.  Logged in with different account on Chromebook and displayed the Printers page.  Problem is following user account and now hardware.

Have Reset devices and power washed.  Have disabled and removed all extensions.

Did this work before? Yes In this version, but stopped after configuring.

Chrome version: 61.0.3163.123  Channel: stable
OS Version: 61.0.3163.123
Flash Version: 

Cannot figure out how to reset native printing sub-system or configuration of printers.
 
Can reproduce with the following command:  chrome://md-settings/cupsPrinters 

Comment 2 by zork@chromium.org, Oct 27 2017

Components: -UI Internals>Printing>CUPS

Comment 3 by skau@chromium.org, Oct 27 2017

Cc: skau@chromium.org
I'm sorry that you're having this problem.  Did you setup the printers after upgrading to M61 or before?  Also, are they USB or network printers?
I setup the printers after upgrading.  The printers are one of each; One USB and One IP.

Comment 5 by skau@chromium.org, Oct 29 2017

Mergedinto: 778383
Status: Duplicate (was: Unconfirmed)
Since this was merged with another bug report, I can no longer see the
results of the new bug report.

Comment 7 by skau@chromium.org, Nov 2 2017

My apologies.  The fix is in versions of Chrome after 62.0.3202.83
Thanks for the update.

Sign in to add a comment