[01:27] <ahmadtarek> hi
[01:27] <ahmadtarek> I think that bug #268946 should be marked as wishlist
[01:59] <hggdh> ahmadtarek, first we have to figure out what package would the bug be in
[02:03] <ahmadtarek> OK
[02:37] <persia> hggdh: If gpg-encrypted files did have an icon, what application do you think they ought launch?  I know gedit has a plugin which works fairly well, but I'm not sure if either kate is still the default or kate has such a plugin.  What do you think of a multi-task bug?
[02:43] <hggdh> persia, I was thinking about the same lines... this cannot be a single package thingy
[02:44] <hggdh> but I cannot figure out which packages should be in (and I would hate to put in the wrong ones)
[02:44] <persia> hggdh: Well, it could be, in that gnupg could provide the necessary MIME hints, or we could create a wrapper that provided the MIME hints, decrypted, rechecked the file, and passed it to the MIME-open handler for the DE (if it exists).
[02:45] <hggdh> yes, certainly the icon should be provided by gpg, but would mime be better used out of the standard mime-type supplier?
[02:45] <persia> Alternately, we could expect each DE to extend the MIME-open handler to auto-decrypt gpg-encrypted data (with pinentry), and then pass to the appropriate owning application for the data itself.
[02:45] <hggdh> persia, this now is more like a project than a simple bug
[02:46] <hggdh> no matter what, I think indeed the icon should be provided with gnupg
[02:47] <persia> hggdh: Indeed.  Mind you, it's only a one or two day project, and some real bugs take a week or more to sort, so I'm not sure it belongs external to the bugtracker, but I do agree it's wishlist (with the affected package to be determined by whoever develops a good idea of how to implement)
[02:47] <hggdh> persia, OK. I will add gnupg as a base package, and note in there this chat
[02:48] <persia> Why should gnupg provide the icon?  It's deep base, so it's quite possible that when the gpg postinst runs, there is no available icon cache in which to register the icon.  Remember: dpkg likes to have gpg available when starting the install.
[02:49] <persia> Not registering the icon means that it's not in the icon cache, which might cause a broken icon in some environments (although one presumes another package will refresh the icon cache later, there's no guarantee)
[02:49] <hggdh> then...
[02:49] <hggdh> this would be part of a desktop package
[02:51] <persia> That's what I'm thinking.  Probably the responsibility of the MIME-open handler for the DE, and absent in environments without such a handler.
[02:51] <persia> So, in the case of GNOME, nautilus and gnome-open would be able to handle the idea of decrypting, and redirecting to the appropriate place.
[02:52] <persia> Note that such an implementation may be considered a possible security issue, as there's no guarantee that the contents of the cleartext will not be committed to disk somewhere for applications without native handling of encypted files, which is why I thought gedit, vim, kate, etc. might also be a good set of candidates for the affected package.
[02:53] <hggdh> hum
[02:53] <hggdh> nautilus already offers a decrypt option
[02:53] <persia> Yes, but as currently implemented, it does store cleartext on disc, which may not be what a user expects from just double-clicking an icon.
[02:53] <hggdh> (actually two, in may case: kgpg and "Decrypt file"
[02:54] <persia> Of course, we could just provide an icon and no MIME handlers, but I expect we'll get anothe wishlist bug saying it should open something.
[02:54] <hggdh> but persia, this is a different issue: where a cleartext should be stored is a problem of the application creating it
[02:55] <hggdh> (meaning memory, clean-up, etc)
[02:55] <hggdh> hum -- persia the mime-handler already exists, at least on Intrepid
[02:56] <persia> In that case, the provider of the mime-handler ought also provide an icon.
[02:57] <hggdh> cool. this simplifies the issue: kgpg does not provide it (the default application that opened to deal with the file), and "Decrypt File" (which I am going to find out what it is)
[02:58] <persia> And that covers GNOME and KDE.  Anyone running xfce that can check this?  How does thunar handle it?
[02:58] <hggdh> this begs another question: is it an application responsability to provide the icons, or should they be provided by, say, nautilus?
[02:59] <hggdh> user scenario: I received a file for which I do not have the correct application installed. Should it be shown without an icon (if this is a, huh, common, application)?
[03:00] <persia> Generally it's the responsibility of the provider of the MIME hints to provide the icons as well.
[03:00] <persia> Yeah, but most users are going to have a decryptor as part of their install, and those who fussed with the install can go install one.
[03:01] <hggdh> for gpg, yes, I agree. The question was generic, though
[03:02] <persia> The generic argument is "If it's a common file type, the MIME handler is included in the default install.  If you think there isn't a handler for something that is a common filetype, please file a bug", and then we look at whether a given application should be installed by default.
[03:03] <persia> There are also ways to provide mime-handlers that cause installs to happen (c.f. easy-codec-installs), but ideally these are kept to a minimum, as it's a fair amount of overhead.
[03:06] <hggdh> so we are back to kgpg & friends
[03:07] <hggdh> and no icon unless a application that deals with it is installed. OK. For this specific case, kgpg and the "Decrypt File" should then be selected for starters
[03:08] <hggdh> seahorse, it seems
[03:18] <persia> That makes sense to me, and then kgpg and seahorse can decide what to do with the file.
[03:19] <persia> Also, kgpg and seahorse can provide icons that work well with the general ideas, and can likely be themeable.
[03:24] <hggdh> just checked -- seahorse does provide the icons, at /usr/share/pixmaps/seahorse
[03:25] <hggdh> so what is missing is for the icons to be registered
[03:25] <hggdh> ergo, it is out of a wishlist, and back as a bug
[03:32] <persia> I still think it's "wishlist", as it doesn't really interfere with much, but at least you found a candidate package :)
[03:32] <hggdh> roger willco
[03:34] <hggdh> done
[03:40] <persia> Excellent detective work there.  I start wondering how to solve the problem in a vacuum, and you've discovered someone just forgot to hint the icon in the MIME registration :)
[03:41]  * hggdh blushes
[03:41] <hggdh> well tell you the truth, I was completely lost... you gave me the idea of where to look for it. Guess it is what you get for using the command line for 30 yearas
[03:43] <persia> heh.
[05:58] <techno_freak> bug 269667 - is it a bug or a question?
[06:01] <nullack> persia : ok moved it here :)
[06:02] <persia> nullack: So, what was the question?
[06:02] <nullack> Whats the criteria for being eligible?
[06:03] <persia> Anyone is welcome to join bugsquad, and help out.
[06:03] <nullack> I noticed your one and I know your online :)
[06:03] <nullack> Im in bug squad
[06:03] <nullack> Im asking about bug control
[06:03] <nullack> https://launchpad.net/~ubuntu-bugcontrol
[06:03] <persia> Joining bug control generally requires one to have at least 5 examples of bugs well triaged, and to get good comments to the application by other members of bug control.
[06:04] <nullack> Well my karma is 1126 so I should be able to come up with some examples
[06:04] <persia> https://wiki.ubuntu.com/UbuntuBugControl lists the explicit criteria, and describes the application process.
[06:04] <nullack> Thanks persia
[06:04] <persia> nullack: good luck with your applicaiton.
[07:17] <fabrice_sp> Hi. How do I convert a bug into a sync request? (bug 119959)
[07:23] <persia> !sync
[07:23] <persia> Grumble
[07:24] <persia> fabrice_sp: You'd edit the description to match https://wiki.ubuntu.com/SyncRequestProcess
[07:25] <persia> Note that the archive is currently under freeze restrictions for features and UI changes.  See https://wiki.ubuntu.com/IntrepidReleaseSchedule andhttps://wiki.ubuntu.com/FreezeExceptionProcess
[07:28] <fabrice_sp> persia: thanks for the link. That's right that I forget this freezing issue. Anyway, I'll update the descriptionfor compliance purpose
[07:28] <persia> fabrice_sp: No point updating the description unless you think it deserves a freeze exception.  Everything will get updated after release anyway.
[07:29] <danbh_intrepid> hey, if a bug is fixed in intrepid, but not hardy, what do you mark it as?  Fix released?  Fix commited?  of just leave it as confirmed?
[07:29] <persia> danbh_intrepid: Fix Released
[07:29] <danbh_intrepid> mk, thanks
[07:30] <fabrice_sp> persia: ok
[08:11] <NCommander> Is there anyone here who is a gnucash user who's willing to help me test an update to gnucash?
[09:36] <Hobbsee> Bug #269656
[09:39] <nullack> Hobbsee I noticed that, can confirm on intrepid it does occur
[09:39] <Hobbsee> nullack: yeah, I just hit it and went wtf.
[09:39] <nullack> :)
[09:39]  * Hobbsee hits it with the ZOMGIMPORTANT stick.
[09:39] <nullack> Want me to confirm it or are you ok traiging it?
[09:40] <Hobbsee> i've already shot it far beyond where you can triage it, but thanks for the offer.
[09:40] <nullack> :)
[09:40] <Hobbsee> :)
[17:36] <joumetal> hello. is bug 220717 enough to get rungetty updated?
[17:36] <joumetal> It's fixed in Debian.
[18:00] <james_w> joumetal: hi, yes it is, it's a bit difficult though
[18:01] <james_w> joumetal: it's not clear what the fix is, so it's hard to fix just that
[18:01] <james_w> joumetal: we could take the whole update, but as it will be rebuilt there is no guarantee that it will be fixed
[18:02] <joumetal> james_w: fortunately debian changelog is not massive.
[18:02] <james_w> yes, but it's still not a targetted fix
[18:07] <joumetal> I understand. thanks.
[18:07] <james_w> I'm trying to find a release team member to consult, but there don't seem to be any around at this moment
[21:44] <Flimm> Can I divide a bug into two bugs?
[22:09] <mrooney> Flimm: well sure, just file a new bug and take the parts about that out of the original
[22:09] <mrooney> and then perhaps link them in the description if they are related
[22:31] <mrooney> when I file an upstream bug report on gnome bugzilla, what is the proper way to link to the LP bug?
[22:33] <nellery> mrooney, create a bug watch on the LP bug
[22:34] <nellery> https://wiki.ubuntu.com/Bugs/Watches
[22:34] <mrooney> nellery: I was referring to the other way
[22:34] <nellery> mrooney, ah
[22:35] <nellery> I'm unaware if that's possible
[22:35] <mrooney> nellery: do you know if there is some syntax to use that it will parse into a link, or anything?
[22:35] <nellery> mrooney, don't think so
[22:35] <mrooney> okay so I can just say like "forwarded from Ubuntu bug #xxxxx"?
[22:36] <nellery> yes, that's what I generally do
[22:36] <nellery> mrooney, here's the documentated info
[22:36] <nellery> https://wiki.ubuntu.com/Bugs/Upstream/GNOME
[22:41] <mrooney> nellery: thanks!
[22:42] <mrooney> would anyone mind seeing if my forwarding of bug 269901 seems okay, it is my first forward
[23:28] <hggdh> mrooney, you hust state something like "original Ubuntu bug: https://etc.etc/etc
[23:28] <hggdh> s/hust/just/
[23:30] <hggdh> mrooney, yes, it looks as a kosher forward
[23:30] <mrooney> hggdh: thanks :)