[13:38] <csegui> hi there
[13:39] <csegui> i found a bug related to gnome, print layer in gnome to be more specific. Bugs only affects 16.04 but i can't find out the package to associate the bug with. Should i associate it to gnome meta package ?
[13:39] <csegui> Thanks for your answers
[13:55] <Vej> csegui: Please try to find the package using this link: https://wiki.ubuntu.com/Bugs/FindRightPackage.
[13:57] <Vej> If this does not work out it is better to file against Ubuntu in general. This might get the attention of people who try to find packages for bugs not appropriately filed. But please check the mentioned manual first.
[13:59] <csegui> Vej: already checked. Thanks for your answer
[13:59] <Vej> csegui: You're welcome
[14:00] <csegui> does someone know, in which package is now included the previous lib libgnomeprint ?
[14:05] <Vej> "Bugs about printing problems should be assigned to the cups  package if you don't know which package they belong to. To report  printing bugs preferably use 'ubuntu-bug cups' from a terminal window  which will gather useful information about your system related to  printing like the version of Ubuntu you use, configured printers and the  versions of important printing packages installed and automatically  attach them to your bug report" (Source:
[14:05] <Vej> csegui: Hope that helps
[14:05] <csegui> Vej: thanks !
[14:12] <csegui> Vej: i see you found out my issue. Quite critial. Over 300+ nodes, this bug can kill a lot of tree :/
[14:12] <csegui> *critical
[14:13] <Vej> csegui: I am still trying to understand your problem. I normaly triage backup programms ;)
[14:15] <csegui> Vej: sorry if it's not clear. In fact, it's quite easy to repdouuce. Take any pdf document, open it with evince, print 2 copies, you'll get 4
[14:15] <csegui> 3 gives you 9 and so on
[14:16] <csegui> it's not related to the underlying cups. I printed out the same document from a diffrent machine (different gnome version) on the cups server on the failing node, and i get the correct number of copies.
[14:17] <csegui> Okular, on the failing node, don't show up this issue.... it's in gnome/gtk i think.
[14:17] <Vej> csegui: Frankly I had to look up the meaning of "collate". I am not a native speaker and my Ubuntu is in German.
[14:17] <csegui> but it's very very annonying  (in my case, many nodes using 16.10 with users (teahcers) printing many copies).
[14:18] <csegui> Vej: ok, collate is one way to aggregate copies
[14:18] <csegui> the other way is not buggy
[14:19] <Vej> csegui: Could not reproduce on Ubuntu 16.04.2. Must be something more specific to trigger this.
[14:19] <csegui> oh
[14:20] <csegui> that's odd. I got this issue on many nodes
[14:20] <csegui> is there any input i can give to enlight the issue ?
[14:22] <Vej> csegui: The printing experts will hopefully ask you the right questions to figure this out. If you run "apport-collect 1670630" from a affected node, you might collect relevant informations. Although I have to admit, that I do not know which apport hooks are registered for cups.
[14:39] <csegui> Vej: apport done
[14:42] <Vej> csegui: Thanks. That Looks like a lot of related informations.
[14:43] <Vej> csegui: Good luck with that bug!
[14:43] <csegui> Vej: thanks. Really hope to get support on this