Problem description: It seems LibreOffice only reads the list of printers when it starts, and keeps the connection live all the time. If the CUPS printserver restarts, or if the laptop with LibreOffice is moved between the networks, LibreOffice cannot print anymore until relaunched. This is quite serious inconvenience for users with laptops. Steps to reproduce: 1. Open new empty document in LibreOffice Writer 2. Print it 3. Restart CUPS on the printserver (sudo service cups restart) 4. Try printing the document again Current behavior: LibreOffice silently fails to print without showing any error message. Expected behavior: Ideal: re-read the list of printers when Print dialog is shown, print the document. Less ideal: show error message that it couldn't print. Operating System: Ubuntu Version: 4.3.0.0.alpha0+ Master
hi did you try with a recent 4.3 beta2 build? is issue still there?
Tested with recently released 4.3.1.2, the bug is still there.
Could not reproduce silent error or any error for that matter. Ubuntu 14.10 64-bit Version: 4.3.3.2 Build ID: 430m0(Build:2) and Version: 4.4.0.0.alpha2+ Build ID: 5bff4b016c4b44f4123e0e6a4fd4c0c4dc0cfa2d TinderBox: Linux-rpm_deb-x86_64@46-TDF-dbg, Branch:master, Time: 2014-11-13_00:14:29
Looks like it handles it better with this version. It still cannot hanlde the situation when printserver changes via /etc/cups/client.conf: 1. Add your printserver to /etc/cups/client.conf using ServerName yourprintserver.tld 2. Check the list of printers: lpstat -a 3. Start libreoffice, check the list of printers 4. Edit /etc/cups/client.conf, ServerName anotherprintserver.tld 5. Check the list of printers: lpstat -a Should see printers from another printserver 6. In currently opened LibreOffice check the list of printers: You will see the same old list of printers. This scenario might look unusual, but it helps people who move between buildings or floors with their laptops. They might change client.conf manually, or ServerName might point to a cname that resolves to a different server in each network. lpstat -a and GTK dialog always correctly show the printers. LibreOffice insists on showing the printers from the original printserver that was there when it started.
hi, would you please give an update of the bug current status with latest LibO 4.4.x releases?
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team Sun, 11 Sep 2016 12:29:16 +0200
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-20161010