Bug 78285 - UI: "can not start printer"
Summary: UI: "can not start printer"
Status: RESOLVED DUPLICATE of bug 77776
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Printing and PDF export (show other bugs)
Version:
(earliest affected)
4.2.3.3 release
Hardware: Other Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks:
 
Reported: 2014-05-05 07:52 UTC by Ed Emmons
Modified: 2014-05-16 20:12 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ed Emmons 2014-05-05 07:52:18 UTC 
Problem description: 

LibreOffice is the only print capable program on my Ubuntu 14.04 system that will not automatically "authenticate" for a printing job.

Steps to reproduce:
1. ....click print in any of the LibreOffice "Components"
2. ....
3. ....

Current behavior: I have to go into the "CUPS" UI interface and manually open up the print queue to validate each and every LibreOffice print job. 

Expected behavior:to click on print and have it print just as it does in all of the other Linux programs (and the LibreOffice 4.2.3.3 suite that is installed on the Windows 8 system that the HP Photosmart C4210 printer is physically connected to. 

              
Operating System: Ubuntu
Version: 4.2.3.3 release
Comment 1 tommy27 2014-05-05 08:39:28 UTC 
did you try resetting the user profile?
https://wiki.documentfoundation.org/UserProfile

please specify exact version of you Ubuntu system
Comment 2 Ed Emmons 2014-05-05 10:18:29 UTC 

My system was updated from Ubuntu 13.10 to the 14.04 LTS release as soon as it became available. The LibreOffice suite was updated to 4.2.3.3 as part of that.
Comment 3 Jorendc 2014-05-05 17:38:27 UTC 
This is a dupe of bug 77776?

Kind regards,
Joren
Comment 4 Jorendc 2014-05-16 20:12:42 UTC 
Please update to LibreOffice 4.2.4. Should be fixed (see bug 77776).

Kind regards,
Joren

*** This bug has been marked as a duplicate of bug 77776 ***