[00:12] <hggdh> Cheesehead: as a general rule, I think that the option of renaming a coredump so that it gets to be unique-ish is not a bad idea
[00:13] <hggdh> Cheesehead: but I would tend to have it put under /var/crash (but we would have to check what apport would do in this case)
[00:14] <Cheesehead> hggdh: Thank You! That's exactly the type of input I needed.
[00:14] <Cheesehead> His idea will clear the first hurdle.
[00:14] <hggdh> good -- and thank you for working on it
[05:43] <somethinginteres> hi all, running 11.10 - my PC won't shutdown. I am wondering if this is a bug currently being experienced by others (so as not to report a currently known problem) and what steps I can take to generate useful information for developers? Thanks!
[08:35] <wagafo> Can anybody confirm if bug 873468  is solved by changing from some mirror repository to the Main Server, for instance? If so this bug could be closed by saying that the affected users should change to another mirror or the Main Server.
[08:35] <ubot4> Launchpad bug 873468 in update-manager (Ubuntu) "Update to Oneiric failed with a request from the update-manager to report a bug. (affects: 27) (dups: 22) (heat: 235)" [Undecided,Confirmed] https://launchpad.net/bugs/873468
[08:40] <mvo> wagafo: this does indeed usually means that hte server is overloaded, I will ask on #ubuntu-mirrors about this, but it maybe that the issues is now solved and it was a peak from the release day and weekend
[08:41] <wagafo> mvo: I ask because there are still these bugs popping up. If you confirm I close the bug as I think I have now duplicated most of them in one.
[08:43] <mvo> wagafo: I'm pretty sure its solved with changing the mirror. thanks a lot for doing doing the work of identifiying the dupes!
[08:43] <mvo> wagafo: if a specific mirror is not responding, especially a $countrymirror.archive.ubuntu.com one its worth raising it in #ubuntu-mirrors as well, I need to find out if there is a better way for this then irc to avoid reports about overloaded mirrors getting lost
[08:49] <wagafo> mvo: OK, I will close the bug, but may be it would be worth trying to find a way to tell the affected users that this may be a momentary problem, because right now what they get is a message saying the ubuntu-minimal cannot be found any more. If it is worth keeping the bug open for this to get some attention I will not close it.
[08:52] <mvo> wagafo: thanks, that is a very good point, the error is pretty bad indeed
[08:53] <wagafo> mvo: So I don't close it and I think there enough information there if anybody want to mark it as triaged
[08:53] <snadge> i upgraded a headless box from 11.04 to 11.10, its now using lightdm.. is it supposed to work with vnc? because i havn't had much success with that
[08:54] <wagafo> mvo: on the mirrors I'll keep an eye
[08:55] <mvo> wagafo: thanks, I updated the description of the bug and set it to triage plus added a precise task so that its on the radar
[10:06] <snadge> nm, you can get a 640x480x16 color vnc session from lightdm if you install tightvncserver
[13:09] <bil21al> some body please set the importance of this bug thankx
[13:09] <bil21al> https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/871646
[13:09] <ubot4> Launchpad bug 871646 in empathy (Ubuntu) "No notification for new messages (affects: 8) (dups: 3) (heat: 50)" [Undecided,Confirmed]
[17:57] <cdavis> Can I mark something as a duplicate of a Debian bug #?
[18:02] <hggdh> cdavis: no; instead, you should set the Debian bug as the upstream bug for ours
[18:02] <cdavis> ok
[18:02] <greg-g> it makes sense because they might be (and probably will be) fixed at different times
[18:21] <micahg> cdavis: no, but you can link the Debian bug, "Also Affects Distribution"
[19:12] <seb128> jibel, hey
[19:13] <seb128> jibel, "document this report with a test case detailing the steps to reliably reproduce"... that's nice but it's often not possible for apport bugs
[19:13] <seb128> jibel, some just "randomly happen"
[19:18] <jibel> seb128, ok, how do we verify, push it and hope for the best ?
[19:18] <seb128> jibel, I commented on the bugs but it's usually "check that you get no new issue during the week where you are using it"
[19:19] <seb128> but yeah, ken or ted should have written that as a testcase
[19:21] <jibel> seb128, that also means that there is nothing (i.e unit test corresponding to the failure) to prevent a future regression.
[19:21] <seb128> jibel, yeah, but well the other option is to not take the fixes...
[19:22] <seb128> when we know they are right code wise
[19:32] <jibel> seb128, I agree and understand, but at least, the bug report should explain the impact, describe the fix and the risks of regression and that installing the package and letting it bake for a week is good enough to verify the SRU.
[19:32] <jibel> the only documentation on the 2 SRUs I bounced is a stacktrace and a branch.
[19:33] <seb128> jibel, right, agreed and I pinged ted and ken about fixing that ;-)
[19:34] <seb128> jibel, I just wanted to explain as well why we can't really have a good testcases in some cases
[19:34] <jibel> seb128, thanks. we'll have a session at UDS to talk about it :)
[19:34] <seb128> jibel, great ;-)
[19:35] <seb128> jibel, with some luck with automatic testing improving we can cover those by testsuit testcases next cycle
[19:35] <seb128> but we are just not there yet for this cycle
[19:42] <blkperl> can someone set importance and set status to triaged for #876130
[19:42] <jibel> bug 876130
[19:42] <ubot4> Launchpad bug 876130 in facter (Ubuntu) "Incorrect operatingsystem reported in puppet run (affects: 3) (heat: 20)" [Undecided,Confirmed] https://launchpad.net/bugs/876130
[19:44] <blkperl> it blocks the use of puppet in oneric :(
[19:45] <jibel> blkperl, what importance would you set ?
[19:46] <blkperl> high
[19:47] <blkperl> or something higher than that
[19:47] <jibel> blkperl, done, set to high because it breaks puppet deployments
[19:47] <blkperl> thanks jibel
[19:47] <jibel> yw
[19:49] <cdavis> When marking bugs as duplicates, does it matter the order in which you mark them?
[19:52] <jibel> blkperl, the fix is in debian already and will autosync to Precise hopefully soon. Once the fix is in it's worth proposing  an update for 11.10 IMO.
[19:53] <blkperl> jibel: thanks
[20:01] <jibel> cdavis, it usually doesn't matter. A good practice is to choose the report with the best documentation as master report.
[20:26] <cdavis> thanks
[21:36] <taowa> can i be a member of Ubuntu Bug Control
[21:37] <micahg> taowa: https://launchpad.net/~ubuntu-bugcontrol
[21:38] <taowa> i joined but i need it o be approved/declined
[21:38] <micahg> taowa: there are instructions on that page on what's required
[21:38] <taowa> Bye
[21:45] <hggdh> taowa: I think I have declined your request to join Bug Control at least 2 times already
[21:45] <hggdh> and on each you received a link to go to, and read the requirements
[21:46] <hggdh> (dclined on Dec 2010 and March 2011)
[21:48] <bdmurray> hggdh: the 3rd time is the charm!
[21:49] <hggdh> bdmurray: indeed, if one may hope against hope
[22:13] <blkperl> so bug 819044 looks solved on the debian side, definately fixed for oneric, not sure about natty
[22:13] <ubot4> Launchpad bug 819044 in puppet (Debian) (and 3 other projects) "puppet in natty can't enable services (affects: 3) (heat: 18)" [Unknown,Unknown] https://launchpad.net/bugs/819044
[22:34] <hggdh> blkperl: check on the #ubuntu-server channel, they are very active with puppet
[22:40] <rdesfo> hello
[22:40] <rdesfo> I'm using xubuntu 11.10 and my terminal wont write 'a'
[22:41] <rdesfo> it will still write 'A' and 'a' appears in my other applications.  Does any one know how to fix this?
[22:42] <penguin42> what happens if you type a ?
[22:42] <rdesfo> nothing
[22:42] <penguin42> hmm
[22:43] <penguin42> rdesfo: The only time I've seen something similar is where I accidentally set 'a' as a shortcut for one of the menus
[22:45] <rdesfo> I checked the shortcut preference in the terminal and in settings manager and I don't see anything setup for a
[22:48] <rdesfo> I tried reinstalling xterm.  Is there something else I could try to reinstall to try and fix the issue?
[22:50] <penguin42> I'm not sure it's a reinstallation problem, it's more likely a config file somewhere in your home directory
[22:53] <rdesfo> I also get "Error stating file '/home/ryan/.gvfs': Transport endpoint is not connected." when I open thunar
[22:58] <hggdh> gvfs is gnome, not KDE. I would not worry about that