G suite usernames not appearing at cloud connected legacy printer.
Reported by
mrmcgr...@bxs.org.uk,
Jan 17 2018
|
||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.132 Safari/537.36 Platform: submitting issue from remote macintosh Steps to reproduce the problem: 1. Print something from ChromeOS/browser on any device 2. 3. What is the expected behavior? I would expect each G Suite username to appear on the printer log rather than "chronos". What went wrong? I don't think anything is wrong, however this would be an amazing feature, especially for admins. Did this work before? N/A Chrome version: 63.0.3239.132 Channel: stable OS Version: Multiple devices always maintained to latest version Flash Version:
,
Jan 17 2018
Which printer log are you referring to?
,
Jan 17 2018
We have a Toshiba e-studio copier in our office and the print log shows mac/windows users username from their machines. It shows the username 'chronos' whenever a Google Cloud print job is sent/received/printed. I think it would be great if the G suite username of whoever is logged into that Chrome session (ChromeOS or Chrome browser) would appear on the Toshiba just like any other OS.
,
Jan 19 2018
,
Jan 19 2018
Is the "Toshiba e-studio copier" a printer device that has Cloud Print functionality built-in, or is there Cloud Print Connector software involved? i.e. What's the route for a print document from the Chromebook to the printer? A) Chromebook -> Google Cloud Print Server -> Toshiba Copier or B) Chromebook -> Google Cloud Print Server -> Cloud Print Connector -> Toshiba Copier
,
Jan 19 2018
Cloud connector in line. Toshiba e-studio > toshiba Windows pc (laptop) > cloud connector > master g suite account for shared printing.
,
Jan 19 2018
Is the connector https://github.com/google/cloud-print-connector, or Chrome running on a desktop, as described in https://support.google.com/a/answer/3179170 ? On Chromebooks, I believe the local UNIX user account for the user is "chronos". Not sure if that's what is being eventually sent to the printer, or if something else like the connector is sending that. I took a quick look at the Cloud Job Ticket sent from the Chromebook to the server, and I don't see a field for the username there. https://developers.google.com/cloud-print/docs/cdd#cjt
,
Jan 20 2018
Yeah, like I say I'm not sure if this is a feature Google are adopting but I thought I'd mention it. Seeing 'chronos' instead of someone@domain.com is not very helpful for administrative purposes. Just to say, thanks for fixing the bug a few weeks ago, Cloud print running smoothly now :)
,
Jan 23 2018
I agree someone@domain.com is more useful than "chronos". Can you answer the question in comment 7 regarding which cloud connector you are using?
,
Jan 23 2018
Hi, I downloaded the github connector but I already had the Google Cloud Print service application installed. Not sure what the difference is but I didn't get a 'console' for the connector I do with the 'service'.
,
May 4 2018
We have a similar issue with Toshiba e-Studio copier/printers, but we are using Chrome native printing, not a cloud connector. When printing from any Windows app jobs to these printers are correctly sent with the user's Windows username and job name. The job is held until the user goes to the copier, finds their user name, and prints their job. When printing from Chrome OS with ipp or lpd, however, the username is always "chronos", and there is no print job name. Therefore all prints from Chrome OS have the same username and no job name, making it impossible to tell which job belongs to which user. This makes the scenario completely impractical. We would like to see the jobs appear with job name and the user's Chrome OS logon name. Thanks.
,
Sep 19
re: comment 10 - So did you ever get the "Cloud Print Connector" working? Does it behave differently compared to the "Cloud Print Service" ? re: comment 11 - Can you file a different bug for your issue? Happy to route that to the appropriate folks.
,
Sep 19
Hi. The connector appear to be more stable and does crash as often. However, the features are hit and miss. I do realise it’s still in beta.
,
Sep 19
If there are missing features in the Cloud Print Connector, try filing bugs on their issue tracker: https://github.com/google/cloud-print-connector/issues For this issue in particular, with the Cloud Print Connector, does it show the right user name in the printer logs?
,
Sep 19
Hi, yeah it shows up when I check the Google cloud console page, but I'm talking about on the connected printer/copier. It only says "Chronos" which lets me know it's from the connected Windows laptop where the connector is loaded, but it doesn't tell me *who* sent the print job on the printer. Is this a feature that can be written in? |
||
►
Sign in to add a comment |
||
Comment 1 by sdantul...@chromium.org
, Jan 17 2018