I try to figure out why my print function in Chromium is not working. When I use CTRL-p to print, Chromium crashes and becomes unresponsive.
However, there is nothing relevant in the shell output:
[orschiro@thinkpad ~]$ chromium [20014:20034:0224/102037:ERROR:object_proxy.cc(624)] Failed to get name owner. Got org.freedesktop.DBus.Error.NameHasNoOwner: Could not get owner of name 'org.chromium.Mtpd': no such name [20014:20034:0224/102037:ERROR:object_proxy.cc(624)] Failed to get name owner. Got org.freedesktop.DBus.Error.NameHasNoOwner: Could not get owner of name 'org.chromium.Mtpd': no such name [20014:20014:0224/102037:ERROR:object_proxy.cc(529)] Failed to call method: org.chromium.Mtpd.EnumerateStorages: object_path= /org/chromium/Mtpd: org.freedesktop.DBus.Error.ServiceUnknown: The name org.chromium.Mtpd was not provided by any .service files [20014:20014:0224/102037:ERROR:omnibox_view_gtk.cc(431)] Not implemented reached in virtual void OmniboxViewGtk::ApplyCaretVisibility() Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
Did anyone have the same problem?
I can confirm above.
I know it's not an answer to your question, but firefox is unaffected.
So, Firefox does not rely on CUPS to print PDFs?
No idea, I do not own a printer, therefore no CUPS.
The only reason I use the print function is for "print to file" of cinema tickets purchased online.
As detailed above, if I try to do this in chrome it causes application freeze, but no problem at all with firefox.
(as explained previously, I have obviously not offered this as a "solution", merely a temporary alternative)
Last edited by flipper T (2013-02-25 12:50:43)
I have just re-read my last post & realized that it sounds very ,very defensive.
I was only trying to clarify & no offense meant.
I filed a bug report in the Chromium tracker: https://code.google.com/p/chromium/issu … ?id=178235
I am curious to know what the developers say on this CUPS dependency.
There are already bug reports about this issue upstream.
GTK+ bug report: https://bugzilla.gnome.org/show_bug.cgi?id=686838
Chromium issue: http://code.google.com/p/chromium/issue … ?id=160574
Firefox handles printing through GTK+ as well, but calls gtk_enumerate_printers() in a separate thread (or something to that effect) and, therefore, doesn't freeze.
So it can indeed be considered a bug in Chromium.
I wouldn't consider it a Chromium bug; the actual bug is in GTK+.
Firefox is just fortunate enough not to be affected by it in any significant way.