[17:34] <hjd> Hi :) Could someone please mark bug 533623 as Triaged/Low. Contains enough information to start digging into / easy to work around, nice-to-have not critical feature and from what I can see no duplicates reported either.
[17:41] <hjd> Also is there a tag or other way to mark Ubuntu-specific bugs? I wasn't able to reproduce the issue above in Debian Sid, so it might have been introduced by an Ubuntu delta in some library.
[17:44] <penguin42> hjd: https://wiki.ubuntu.com/Bugs/Tags   I don't see anything appropriate?
[18:10] <teward> hjd: if it's an Ubuntu specific bug just file it on Launchpad - if it also affects debian then you'd file a bug against Debian and link it to the Ubuntu bug here on Launchpad, indicating the upstream link.
[18:10] <teward> i don't think there's a 'tag' that is appropriate for what you're trying to mark.  A comment to the affect that Debian Unstable is not affected is a good starting point.
[18:10] <teward> (I don't think we need a tag)
[18:22] <hjd> teward: Sure. :) In this case the bug wasn't reproducible in Debian so it doesn't make sense to forward it. Just wondered if there was some way to mark that the bug doesn't appear to be reproducible upstream.
[18:22] <hjd> I added a comment stating I wasn't able to trigger it in Debian Sid.
[18:24] <teward> hjd: then i think that's all you need.  looking at the changelogs though I don't see much of a delta between Ubuntu and Debian
[18:24] <teward> https://launchpad.net/ubuntu/+source/gimp - expand the Vivid one and you'll see the changelogs from the last version in Utopic
[18:25] <teward> the only changes i see there is that there's string changes for Ubuntu (probably a common delta), and some patches were dropped because included upstream
[18:25] <teward> so i'm not sure where the issue comes up.
[18:29] <teward> (it doesn't immediately appear to me that the delta that exists would keep this issue, but I'm not a gimp expert)
[18:32] <hjd> I don't know either. Didn't see anything immediately suspicious in Ubuntu's gimp patches.
[18:33] <hjd> Since it is related to the behaviour of the dialog, I wonder whether if the actual issue might be located in some underlying library (like gtk2 or something else). I'm afraid I don't know how to test this theory though.
[19:02] <Roanapur> Hello, I have recently installed 15.04 on my laptop. I'm having issues booting under systemd but have no issues booting in upstart. Should I submit a bug under the systemd-boot tag?
[19:02] <penguin42> sounds reasonable - how does it fail?
[19:04] <Roanapur> It asks me to supply a encryption passphase which hasn't been setup.
[19:05] <penguin42> oh that's nasty of it
[19:05] <penguin42> do you have any encrypted partitions at all?
[19:06] <Roanapur> I don't believe so, I encrypt my home folder though. When I use upstart to boot then I am not prompted for any passwords except at the lightdm prompt.
[19:06] <Roanapur> I can get a systemd debug shell but i'm not sure what I should do to effectively submit the report.
[19:07] <penguin42> ok, start by reporting it as a bug, and include that information
[19:09] <Roanapur> Okay, thanks for the help!
[19:10] <penguin42> Roanapur: Does your /etc/fstab look sane?
[19:16] <Roanapur> It looks like it. I have encrypted swap which might be part of the issue
[19:21] <penguin42> ahhhh!
[19:21] <penguin42> Roanapur: Well, if you've got encrypted swap then it needs the key
[19:23] <penguin42> Roanapur: If you've got encrypted swap, then I don't understand how the non-systemd world starts up without asking you
[19:25] <Roanapur> I've done some digging, it looks like its failed silently, swap isnt mounted. I previously had an LTS installed and I done a clean install today, perhaps the same swap is being used?