Activity log for bug #314408

Date Who What changed Old value New value Message
2009-01-06 15:50:43 Martin Pitt bug added bug
2009-01-06 15:50:56 Martin Pitt bug assigned to gtk
2009-01-06 15:51:09 Martin Pitt bug added subscriber Till Kamppeter
2009-01-06 15:51:27 Martin Pitt gtk+2.0: status New Triaged
2009-01-06 15:51:27 Martin Pitt gtk+2.0: importance Undecided Wishlist
2009-01-06 15:51:27 Martin Pitt gtk+2.0: statusexplanation
2009-01-06 17:12:34 Martin Pitt bug assigned to qt4-x11 (Ubuntu)
2009-01-06 17:13:09 Martin Pitt qt4-x11: status New Triaged
2009-01-06 17:13:09 Martin Pitt qt4-x11: importance Undecided Wishlist
2009-01-06 17:13:09 Martin Pitt qt4-x11: statusexplanation I also filed it at the upstream Qt tracker, but did not get a ticket ID/URL. Maybe they need to approve it, or something.
2009-01-07 08:21:06 Bug Watch Updater gtk: status Unknown New
2009-01-19 08:18:18 Martin Pitt gtk+2.0: assignee pitti
2010-08-16 12:05:49 Till Kamppeter description The main reason why Debian/Ubuntu does not enable automatic printer detection in cups by default is that there is no way to tell apart locally configured (and thus trusted) printers from those which got detected automatically (and thus open the possibility of luring someone into printing confidential material onto a rogue network printer). E. g. I have a locally configured "local_ps" printer, and an ML-1610 which comes through cups browsing detection. The print dialog currently looks like this: http://people.ubuntu.com/~pitti/screenshots/print_dialog_gtk.png the printers look exactly the same, I have no way to tell which ones can be considered trusted. It would be great to separate the locally configured from the remotely detected ones: |_| Print to file | |=| HP DeskJet 123 | room 10 | |=| Samsung Foo Color | | Automatically detected remote printers: |=| ML-1610 | dagobert | They can be told apart with the CUPS_PRINTER_DISCOVERED flag (see cups/cups.h). The main reason why Debian/Ubuntu does not enable automatic use of network printers broadcasted by remote CUPS servers by default is that there is no way to tell apart locally configured (and thus trusted) printers from those which got advertized by remote CUPS servers (and thus open the possibility of luring someone into printing confidential material onto a rogue network printer). E. g. I have a locally configured "local_ps" printer, and an ML-1610 configured on a remote server which appears through cups browsing detection. The print dialog currently looks like this:   http://people.ubuntu.com/~pitti/screenshots/print_dialog_gtk.png the printers look exactly the same, I have no way to tell which ones can be considered trusted. It would be great to separate the locally configured from the remotely detected ones:   |_| Print to file | Locally configured printers:   |=| HP DeskJet 123 | room 10 |   |=| Samsung Foo Color | |   Automatically detected remote printers:   |=| ML-1610 | dagobert | Locally configured and automatically discovered remote printers can be told apart with the CUPS_PRINTER_DISCOVERED flag (see cups/cups.h).
2010-08-16 12:06:49 Till Kamppeter summary Please separate autodetected from locally configured printers Please separate automatically discovered remote printers from locally configured printers
2010-08-16 12:08:17 Till Kamppeter bug task added hundredpapercuts
2010-08-16 12:09:19 Till Kamppeter bug task added qt
2010-08-16 12:32:13 Till Kamppeter attachment added Screenshot of the bug description https://bugs.edge.launchpad.net/qt/+bug/314408/+attachment/1493206/+files/print_dialog_gtk.png
2010-09-15 19:44:54 Bug Watch Updater gtk: importance Unknown Wishlist
2010-12-23 17:11:57 Chris Wilson hundredpapercuts: status New Confirmed
2011-01-20 18:29:48 Chris Wilson hundredpapercuts: importance Undecided Medium
2011-05-23 12:59:13 Martin Pitt affects gtk+2.0 (Ubuntu) gtk+3.0 (Ubuntu)
2012-06-01 17:15:49 Martin Pitt gtk+3.0 (Ubuntu): assignee Martin Pitt (pitti)
2012-07-20 15:55:21 Matthew Paul Thomas affects gtk+3.0 (Ubuntu) ubuntu
2012-07-20 15:55:21 Matthew Paul Thomas ubuntu: status Triaged Confirmed
2012-07-20 15:55:21 Matthew Paul Thomas ubuntu: assignee Matthew Paul Thomas (mpt)
2012-07-20 16:56:28 Martin Pitt affects ubuntu gtk+3.0 (Ubuntu)
2012-12-18 20:22:41 John Swing bug added subscriber John Swing
2013-05-29 13:49:37 Alberto Salvia Novella gtk+3.0 (Ubuntu): status Confirmed Triaged
2013-05-29 13:49:43 Alberto Salvia Novella hundredpapercuts: status Confirmed Triaged
2013-05-29 13:50:13 Alberto Salvia Novella hundredpapercuts: assignee Paper Cuts Ninja (papercuts-ninja)
2013-05-29 19:16:07 Chris Wilson hundredpapercuts: milestone papercuts-s-gtk
2013-10-21 12:26:20 Catalin Hritcu bug added subscriber Catalin Hritcu
2014-01-08 11:44:29 Matthew Paul Thomas gtk+3.0 (Ubuntu): status Triaged In Progress
2014-01-08 15:27:43 Matthew Paul Thomas affects gtk+3.0 (Ubuntu) ubuntu
2014-01-08 15:27:43 Matthew Paul Thomas ubuntu: status In Progress Triaged
2014-01-08 15:27:43 Matthew Paul Thomas ubuntu: assignee Matthew Paul Thomas (mpt)
2014-01-08 15:28:12 Matthew Paul Thomas description The main reason why Debian/Ubuntu does not enable automatic use of network printers broadcasted by remote CUPS servers by default is that there is no way to tell apart locally configured (and thus trusted) printers from those which got advertized by remote CUPS servers (and thus open the possibility of luring someone into printing confidential material onto a rogue network printer). E. g. I have a locally configured "local_ps" printer, and an ML-1610 configured on a remote server which appears through cups browsing detection. The print dialog currently looks like this:   http://people.ubuntu.com/~pitti/screenshots/print_dialog_gtk.png the printers look exactly the same, I have no way to tell which ones can be considered trusted. It would be great to separate the locally configured from the remotely detected ones:   |_| Print to file | Locally configured printers:   |=| HP DeskJet 123 | room 10 |   |=| Samsung Foo Color | |   Automatically detected remote printers:   |=| ML-1610 | dagobert | Locally configured and automatically discovered remote printers can be told apart with the CUPS_PRINTER_DISCOVERED flag (see cups/cups.h). The main reason why Debian/Ubuntu does not enable automatic use of network printers broadcasted by remote CUPS servers by default is that there is no way to tell apart locally configured (and thus trusted) printers from those which got advertized by remote CUPS servers (and thus open the possibility of luring someone into printing confidential material onto a rogue network printer). E. g. I have a locally configured "local_ps" printer, and an ML-1610 configured on a remote server which appears through cups browsing detection. The print dialog currently looks like this:   http://people.ubuntu.com/~pitti/screenshots/print_dialog_gtk.png the printers look exactly the same, I have no way to tell which ones can be considered trusted. It would be great to separate the locally configured from the remotely detected ones:   |_| Print to file |   Locally configured printers:   |=| HP DeskJet 123 | room 10 |   |=| Samsung Foo Color | |   Automatically detected remote printers:   |=| ML-1610 | dagobert | Locally configured and automatically discovered remote printers can be told apart with the CUPS_PRINTER_DISCOVERED flag (see cups/cups.h). <https://wiki.ubuntu.com/Printing#listing>: "whenever available printers are listed, they should be listed in up to two sections: * Whenever at least one manually configured printer is available, a section beginning with an insensitive item, “Configured printers”. * Whenever at least one broadcast printer is available, a section beginning with an insensitive item, “Discovered printers”."
2014-01-08 15:42:00 Alberto Salvia Novella hundredpapercuts: assignee Papercuts Ninjas (papercuts-ninja)
2014-01-08 16:06:25 Sebastien Bacher affects ubuntu gtk+3.0 (Ubuntu)
2014-10-13 07:27:43 Roman Shipovskij bug added subscriber Roman Shipovskij
2014-10-13 07:30:30 Roman Shipovskij removed subscriber Roman Shipovskij
2014-10-13 07:31:17 Roman Shipovskij bug added subscriber Roman Shipovskij
2018-02-10 05:32:12 Bug Watch Updater gtk: status New Expired