[22:54] <bdmurray> gf2: Hi, you saw my notes about the crashs from the Error Tracker right?
[23:00] <gf2> Hi Bd. I didn't realize you were in. :) I was hoping to ask you a few questions. Do you have time?
[23:00] <bdmurray> Yes, its Brian by the way.
[23:00] <gf2> Thanks Brian. I wasn't sure if we could use first names here. My name is Glady.
[23:02] <gf2> Kovid Goyal won't touch any bug that is using an older version of calibre. He says it has to be the latest version from his website (manually installed) or he won't touch it.  I have a similar response from the Tbunderbird people. But it's always a catch up game. The distro is never going to have the latest.
[23:03] <rbasak> Some upstreams hold that opinion.
[23:03] <rbasak> It's fundamentally at odds with the policies of many distributions. And users use those distributions at least in part because they align with distribution policies.
[23:04] <gf2> a circle, Robbie :)
[23:04] <rbasak> Usually though we try to reproduce bugs on current upstream releases before forwarding to them.
[23:05] <gf2> I did that with a couple of TBird bugs and all they said was, is it still a problem in version 60? (their latest)
[23:05] <rbasak> It's the same with Debian - if filing a bug in Debian, I test against a Debian release first and frame the bug report in terms of Debian. No need to hide its real origin or anything; it's just easier for upstreams to handle their reports that way.
[23:06] <gf2> So, I should test it in the latest and then, if still a problem, report it upstream?
[23:08] <rbasak> Right
[23:09] <gf2> And if it is not a problem with the latest version, I should ask the user to wait until the latest comes out?
[23:09] <gf2> (sorry if I keep asking similar questions)
[23:09] <gf2> (still learning)
[23:09] <rbasak> If it is confirmed as a problem in an Ubuntu release, but you cannot reproduce the problem upstream, then there are a few possibilities.
[23:10] <rbasak> First, the bug is probably Triaged because the report is validated and it's clear what the problem is.
[23:10] <rbasak> It's possible that the problem has been fixed but wasn't yet fixed in the affected Ubuntu releases.
[23:11] <rbasak> In that case the user can wait for a new release, and/or an Ubuntu developer can try to backport the fix. For stable Ubuntu releases, that's subject to SRU policy.
[23:11] <rbasak> It's also possible that the bug has been introduced in the act of packaging it, in which case waiting for the fix will be futile for the user.
[23:12] <rbasak> Whichever way the bug will have been accurately triaged assuming the findings are documented there.
[23:12] <gf2> ok
[23:13] <rbasak> This kind of thing generally depends on how far volunteers want to go, and/or are able to go.
[23:13] <rbasak> Does that help?
[23:13] <rbasak> Don't worry about asking questions. You're asking good questions :)
[23:14] <gf2> I remember you telling me about the backporting. I have been working on New and Undecided bugs so far. So, no documentation has been done on them.
[23:14] <gf2> I figure I should...
[23:14] <gf2> have two versions installed - the original from the distro (with regular updates) and ..
[23:15] <gf2> and, in a virtual machine or different partition, the latest and greatest, manually installed.
[23:16] <gf2> On the latest and greatest, should I also be using Ubuntu daily builds?
[23:17] <bdmurray> Just updating regularly will get you the same thing
[23:17] <rbasak> Nowadays I tend to update my machine less often, but use containers and things for testing far more often.
[23:18] <gf2> I am not familiar with containers. Can you direct me to a wiki on how to install them?
[23:18] <rbasak> I usually try (but fail) to move my laptop up to the development release after beta1. I keep my desktop machine the same though.
[23:19] <gf2> I am familiar with dual booting and have left room on my drive for testing partitions. But containers are new to me.
[23:19] <rbasak> https://linuxcontainers.org/lxd/getting-started-cli/ maybe
[23:20] <gf2> ok, thanks, Robie. I will look at that.
[23:21] <gf2> Another question: I have finished all the old new-undecided tickets for Thunderbird and synaptic. Any recommendations for another package for me to clear the old unaddressed tickets?
[23:22] <gf2> Or shoudl I go back and clear up the other older tickets from TBird (not new, not undecided)?
[23:23] <bdmurray> I'd work on software that interests you or that you use a lot e.g. calibre
[23:23] <gf2> yes, I use Calibre every day :)
[23:25] <gf2> I have gone through most of those tickets too. :)
[23:26] <gf2> Another question: I have sometimes found tickets that have been at incomplete status for years and they never got "deleted"  Is there a circumstance where the incomplete status does not delete the ticket after 60days?
[23:28] <rbasak> There are some criteria. Detailed here: https://help.launchpad.net/Bugs/Expiry?
[23:28] <bdmurray> gf2: Yes ^^ that sounds right
[23:29] <gf2> Super! I'll read that.  Another question...
[23:31] <gf2> On those automated error messages that come from  errors.ubuntu.com   (eg.    https://bugs.launchpad.net/bugs/1587570)  the title keeps going way off to the right. It makes it hard to push the "Post comment" button while using my cell phone, for some reason.  Is there a reason it goes off the right like that. Is it because it is one long unbroken sentence?
[23:33] <rbasak> I guess so.
[23:33] <rbasak> That looks like a UX issue on Launchpad to me.
[23:34] <rbasak> It might be worth a bug report against Launchpad itself.
[23:35] <gf2> I can push the button but only after changing landscape to portrait and back, so I am able to do it. So, where do I file a bug to launchpad?
[23:37] <gf2> Also only on my phone, the post comment button disappears when I paste a long comment in the comment box. I again switch between landscape and portrait view to get the button to show up again.
[23:39] <bdmurray> bugs.launchpad.net/launchpad
[23:41] <gf2> Or it could be just my phone :)  Another question: am I able to access the " https://errors.ubuntu.com/problem/..." site? Or is that a bug team area?
[23:41] <gf2> Thanks for the link Brian!
[23:41] <bdmurray> errors.ubuntu.com is generally for developers
[23:42] <gf2> OK, just checking if I should be using my regular login for that or something.  Thanks guys! I can't think of anything else right now to ask. Thanks for your patience! :)
[23:43] <gf2> Have a great night/day/evening/morning   ??  :D
[23:45] <rbasak> gf2: thank you for helping out!
[23:45] <gf2> No problem - I am learning a lot :)