After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 165569 - shouldn't be able to print to file when disable_save_to_disk is enabled
shouldn't be able to print to file when disable_save_to_disk is enabled
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Printing
3.6.x
Other All
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on: 345590
Blocks:
 
 
Reported: 2005-01-29 01:18 UTC by spark
Modified: 2018-04-15 00:32 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description spark 2005-01-29 01:18:34 UTC 
shouldn't be able to print to file when disable_save_to_disk is enabled.
Comment 1 Allison Karlitskaya (desrt) 2005-01-29 02:07:36 UTC 
Fixing this properly probably involves making changes to EphyDialog since if you
call ephy_dialog_get_control (dialog, print_props[PRINTON_PROP].id) then you get
the "Printer" radiobutton when you want to get the "File" one (to disable it).

Alternatively, this could be cheated by monkeying around with the order of
things in the .glade file.  This is an evil hack but maybe it's good enough for
now if the plan is to replace this with the gnome print dialog.
Comment 2 Christian Persch 2007-05-31 12:39:57 UTC 
GeckoPrintService::TranslateSetting just needs to check whether the printer is the "print-to-file" printer and return NS_ERROR_GFX_PRINTER_ACCESS_DENIED if it is and save_to_disk is disabled. But that depends on the gtk bug.
Comment 3 Jean-François Fortin Tam 2012-10-07 03:22:56 UTC 
This is GTK filechooser's job now.
Comment 4 Federico Mena Quintero 2012-10-08 18:26:51 UTC 
You mean the print dialog.  Reassigning to the right component.
Comment 5 Matthias Clasen 2018-02-10 05:08:51 UTC 
We're moving to gitlab! As part of this move, we are moving bugs to NEEDINFO if they haven't seen activity in more than a year. If this issue is still important to you and still relevant with GTK+ 3.22 or master, please reopen it and we will migrate it to gitlab.
Comment 6 Matthias Clasen 2018-04-15 00:32:50 UTC 
As announced a while ago, we are migrating to gitlab, and bugs that haven't seen activity in the last year or so will be not be migrated, but closed out in bugzilla.

If this bug is still relevant to you, you can open a new issue describing the symptoms and how to reproduce it with gtk 3.22.x or master in gitlab:

https://gitlab.gnome.org/GNOME/gtk/issues/new