[03:35] <jolish_> Hello!
[03:36] <jolish_> ô_O
[03:38] <jolish_> anybody?
[03:38] <micahg> jolish_: how can we help you?
[03:39] <jolish_> oh hi!! I just joined the BugSquad team on launchpad
[03:39] <micahg> great
[03:39] <jolish_> I'd like to help... what should I do next?
[03:40] <micahg> have you read the documentation on how to triagE?
[03:40] <jolish_> I'm about to
[03:41] <micahg> ok, why don't you read through that first
[03:42] <jolish_> ok :)
[03:43] <micahg> then we can talk about how you'd like to help :)
[03:43] <jolish_> great
[03:51] <greg-g> jolish_: welcome to the team, feel free to get started with whatever task fancies you, and ask questions here
[03:52] <jolish_> thank you!
[04:19] <on3_g> <0/
[05:06] <jolish_> hi!
[05:09] <jolish_> micahg: sorry for taking so long
[05:10] <micahg> no probelm
[05:13] <jolish_> so, I'd like to fix bugs... but I'm not familiar with any package nor I know which one to choose
[05:15] <jolish_> maybe I should start Triaging and move later to code.
[05:19] <micahg> well, triaging is gathering all the information for a problem so the developer can fix
[05:19] <micahg> we don't "fix" bugs here
[05:19] <micahg> we triage
[05:19] <micahg> the developers fix the bugs
[05:20] <micahg> I mean specifically in this channel and this team
[05:20] <micahg> so, jolish_, what apps do you use?
[05:21] <micahg> it helps to have a baseline understanding of the app you are triaging
[05:21] <micahg> so you know what's expected and what's not
[05:22] <micahg> jolish_: I hope I didn't scare you
[05:22] <jolish_> lols nope, im thinking how to answer
[05:23] <micahg> ok
[05:23] <jolish_> I dont install a lot of software
[05:24] <micahg> that's ok
[05:24] <jolish_> Firefox 3.5
[05:24] <micahg> ok
[05:24] <jolish_> emesene as MSN client
[05:24] <jolish_> Compiz config manager
[05:25] <jolish_> umm google desktop
[05:25] <jolish_> open office
[05:25] <micahg> ok, so choose one of those and go to the bugs section in launchpad for that package
[05:26] <jolish_> ok, lets say emesene
[05:26] <micahg> ok
[05:26] <micahg> doyou know where to find the bugs?
[05:27] <jolish_> as said in the how to triage document
[05:29] <jolish_> umm now I cant find it
[05:32] <micahg> https://bugs.launchpad.net/ubuntu/+source/emesene
[05:33] <jolish_> ok, thanks
[05:36] <micahg> so, you want to choose a new bug to start
[05:36] <jolish_> yup
[05:37] <jolish_> a "new" bug?
[05:38] <micahg> yes, one with a status of new
[05:38] <jolish_> ok
[05:40] <jolish_> ok, its a bug about colors in nicknames
[05:40] <micahg> ok which bug?
[05:40] <jolish_> and I see its a suggestion
[05:40] <jolish_> https://bugs.launchpad.net/ubuntu/+source/emesene/+bug/291796
[05:40] <ubot4> Launchpad bug 291796 in emesene "Hard to read nick colour using dark themes" [Undecided,New]
[05:40] <jolish_> that one
[05:41] <micahg> ok, which version of Ubuntu are you on?
[05:42] <micahg> indeed
[05:42] <micahg> so, suggestions are generally marked wishlist
[05:42] <micahg> but you need to make sure they are valid still
[05:43] <jolish_> im using Jaunty
[05:43] <micahg> so you have pretty much the same version as the reporter
[05:44] <micahg> the problem is that 1.5 is in karmic
[05:44] <micahg> do you have virtualbox or another virtualization environment installed?
[05:44] <jolish_> Well the reporter uses ubuntu 8.10
[05:45] <jolish_> with emesene 1.0.1-1
[05:45] <micahg> yes, but we don't release new features into old releases
[05:45] <jolish_> XD
[05:45] <micahg> this might be classified as a bug, idk
[05:45] <jolish_> i have VMware installed
[05:46] <micahg> ok, do you have a karmic desktop cd you can load up in VMWare?
[05:46] <jolish_> not yet
[05:46] <micahg> iso?
[05:47] <jolish_> nope...
[05:47] <micahg> well, you can either try to duplicate yourself on a live cd, or ask the reporter to test on a live cd
[05:48] <micahg> or rather duplicate the issue, not yourself :)
[05:48] <jolish_> umm why do you think its a bug?
[05:49] <micahg> well, if the text isn't visible with a certain theme that might constitute a bug
[05:49] <micahg> idk
[05:49] <micahg> that's what I meant when I said it helps to have a baseline understanding of how the app should work (I don't in this case)
[05:50] <micahg> bcurtiswx: do you use emesene?
[05:50] <jolish_> yes i do
[05:50] <jolish_> lols
[05:50] <jolish_> sry
[05:51] <micahg> jolish_: in either case, it needs to be verified if the issue still exists in Karmic
[05:51] <jolish_> ok
[05:53] <micahg> jolish_: if you'd like to d/l an iso to test with you can do it here: http://cdimage.ubuntu.com/releases/karmic/rc/
[05:53] <micahg> oops
[05:53] <micahg> sorry
[05:53] <micahg> http://releases.ubuntu.com/karmic/
[05:53] <jolish_> I use a dark theme in my ubuntu and the text is perfectly visible
[05:54] <micahg> oh, well that's a different story
[05:55] <micahg1> maybe the theme was fixed?
[05:55] <micahg> jolish_: well have you seen the responses page?
[05:55] <jolish_> nope :S
[05:55] <micahg> !responses
[05:55] <ubot4> response is https://wiki.ubuntu.com/Bugs/Responses
[05:57] <micahg> ugh, none of these are right
[05:57] <micahg> oops
[05:57] <micahg> I was wrong
[05:57] <micahg> https://wiki.ubuntu.com/Bugs/Responses#Old%20untouched%20bugs
[05:59] <jolish_> oooh so how do I answer this to the reporter?
[06:02] <micahg> so, that response about old, untouched bugs is appropriate
[06:02] <micahg> the reporter could now be on jaunty or karmic, we don't know
[06:02] <micahg> reporter could have solved the issue and never told ys
[06:02] <micahg> *us
[06:03] <micahg> so, you copy the text from the gray box there
[06:03] <micahg> click the little arrow next to the task on top
[06:03] <micahg> of the bug, paste the text and change the status to Incomplete
[06:04] <micahg> You can also say you're not affected by it on jaunty
[06:04] <micahg> note: the text is a guide
[06:04] <micahg> you can change a few words if it makes sense
[06:06] <jolish_> ok :)
[06:08] <jolish_> I cant find the little arrow next to the task on top *blush*
[06:09] <micahg> next to the package name under affects
[06:10] <jolish_> oooh!
[06:11] <jolish_> that should be more visible lol
[06:15] <jolish_> so I should have a fresh Karmic version installed on a virtual machine to try further bugs
[06:15] <micahg> it's a good idea at least to be able to load in a VM
[06:16] <micahg> a Live CD
[06:16] <micahg> if you can't ascertain the problem with your current setup
[06:16] <micahg> that would be only if somethings broke for you as well as the reporter
[06:16] <micahg> jolish_: nice job on the bug
[06:17] <jolish_> thanx =)
[06:18] <micahg> wanna try another
[06:18] <jolish_> yup. something harder
[06:22] <micahg> ok, grab one
[06:24] <jolish_> uhmm
[06:24] <jolish_> https://bugs.launchpad.net/ubuntu/+source/emesene/+bug/295066
[06:24] <ubot4> Launchpad bug 295066 in emesene "Traceback No hay espacio libre en el dispositivo" [Undecided,New]
[06:24] <micahg> ok
[06:25] <micahg> so read the bug and tell me what you think should be done
[06:25] <micahg> hablas espanol?
[06:25] <jolish_> sip
[06:25] <micahg> ok
[06:26] <jolish_> de donde eres?
[06:27] <jolish_> podemos seguir en español?
[06:27] <micahg> No, yo tome muchos anos en la escuela, pero yo olvide mucho
[06:28] <micahg> I was commenting because part of the bug was in spanish
[06:28] <micahg> just wanted to make sure you understood it :)
[06:29] <jolish_> ok, english then ^^
[06:29] <micahg> I grew up in Las vegas
[06:29] <micahg> hence the option for Spanish
[06:30] <jolish_> =)
[06:31] <jolish_> should I translate it
[06:31] <micahg> if you want, I usually do since most of the triagers speak english
[06:33] <jolish_> ok, I notice it was changed to incomplete and then to new again
[06:33] <micahg> yes, but look at the dates
[06:34] <jolish_> oh same date
[06:34] <micahg> no, I mean how old is it
[06:34] <jolish_> yes, also that
[06:35] <micahg> also, emesene isn't supporting 1.0
[06:35] <micahg> so I'd say same as the last one
[06:35] <micahg> and that link is to a trac instance that no longer exists
[06:35] <jolish_> ok
[06:35] <jolish_> same then
[06:40] <micahg> jolish_: you still there?
[06:41] <jolish_> im here
[06:41] <jolish_> I posted the comment
[06:42] <micahg> wow
[06:42] <micahg> multi-lingual! awesome :)
[06:42] <jolish_> lols just bi-lingual
[06:42] <jolish_> Im not good at languages
[06:45] <jolish_> so why does those bugs are that old?
[06:45] <micahg> we have over 71k bugs
[06:45] <jolish_> and how do I look for New "New" bugs?
[06:45] <micahg> and not enough people to triage then all
[06:46] <micahg> sort by newest first
[06:47] <jolish_> ok, but then old bugs are doomed to be "new" forever XD
[06:50] <ikt> http://ubuntuforums.org/showthread.php?t=1298593 <- omg lookit, papercut!
[06:51] <micahg> jolish_: yes, but triaging newer bugs is preferable since the issues are current
[06:51] <micahg> ikt: probably not a papercut
[06:51] <ikt> y?
[06:51] <micahg> idk
[06:51] <ikt> should I report as samba issue?
[06:52] <jolish_> papercut??
[06:52] <ikt> problem easy to fix or small issue
[06:53] <micahg> ikt: I'd file against dbus
[06:53] <ikt> cheers :)
[06:53] <jolish_> oooh!
[06:54] <micahg> ikt: wait
[06:54] <micahg> which app are you browsing in?
[06:55] <ikt> just standard nautilus
[06:55] <micahg> hmm, maybe file against nautilus
[06:55] <micahg> they'll move it to dbus if appropriate
[06:55] <wgrant> Very unlikely to be dbus.
[06:55] <micahg> they might not be handling the error properly at a higher level, idk
[06:55] <wgrant> Probably nautilus, but otherwise devicekit-disks.
[06:55] <wgrant> Oh, network share? Maybe not.
[06:56] <micahg> nautilus is a good starting point
[06:56] <ikt> just made a quick movie
[06:56] <wgrant> Anyway, not a dbus bug.
[06:56] <micahg> jolish_: more examples of why it helps to know the apps :)
[06:56]  * micahg only knows firefox ;)(
[06:58] <jolish_> XD
[06:58] <jolish_> which IRC client do you use?
[06:59] <micahg> pidgin
[07:00] <jolish_> ok, cuz I think I cant post actions like you
[07:00] <jolish_> with XChat
[07:00] <micahg> '/me'
[07:01]  * jolish_ learning to chat lol!
[07:01] <jolish_> yay!
[07:03] <jolish_> https://bugs.launchpad.net/ubuntu/+source/emesene/+bug/456856
[07:03] <ubot4> Launchpad bug 456856 in emesene "msn contact unable to add me to emesene" [Undecided,New]
[07:03] <ikt> micahg: http://dl.getdropbox.com/u/2161836/video/dbus
[07:04] <jolish_> uhm I need karmic to reproduce that one
[07:04] <ikt> jolish_: run karmic or ubuntu+1 in virtualbox :D
[07:05] <micahg> ikt: ok, well, file a bug in nautilus, you can attach the moview
[07:05] <micahg> *movie
[07:05] <ikt> kk :)
[07:05] <micahg> thanks ik
[07:05] <micahg> ikt
[07:05] <ikt> cheers as well, good to get it in the right spot
[07:05] <jolish_> well... thank you for all the help
[07:06] <jolish_> g2g
[07:06] <micahg> ok jolish_, thanks for the help with bugs
[07:06] <jolish_> im falling asleep
[07:06] <micahg> come back anytime
[07:06]  * micahg needs to do that soon
[07:06] <jolish_> I will... this is fun!
[07:06] <micahg> jolish_: what timezone?
[07:07] <jolish_> -6 gmt XD
[07:07] <jolish_> 1 am here
[07:07] <micahg> ok
[07:07] <micahg> same as me
[07:07] <micahg> night jolish_
[07:07] <jolish_> Im from Mexico by the way
[07:08] <jolish_> nice to meet you, ciao
[07:09] <micahg> that explains the spanish :)
[07:10] <jolish_> =)
[07:11] <ikt> is launchpad extremely slow for anyone else?
[07:13] <micahg> seems about normal for me
[07:13] <ikt> hrmm must be on my end
[07:14] <micahg> ikt: normal is relative ;)
[07:14] <ikt> haha
[07:46] <thekorn> good morning
[09:01] <thekorn> wgrant, I was wondering why there are no python bindings for XPCOM in karmic anymore, and found bug 358887, can you please tell me what you mean by 'this' in your first comment (python-xpcom or the python2.6 dependency)
[09:01] <ubot4> Launchpad bug 358887 in xulrunner "python-xpcom cannot be loaded on Jaunty" [Undecided,Won't fix] https://launchpad.net/bugs/358887
[09:03] <wgrant> thekorn: python-xpcom
[09:04] <wgrant> I think.
[09:04] <wgrant> I can't think I would have meant anything else.
[09:04] <thekorn> wgrant, do you know of a reason for this, is this explained somewhere
[09:04] <wgrant> But it was a long time ago.
[09:04] <wgrant> thekorn: IIRC I discussed it with some mozillateam people. Let me find logs.
[09:04] <thekorn> wgrant, super, thanks
[09:05] <micahg> I think it became its own project
[09:05] <wgrant> thekorn: Oh, right, it was part of xulrunner.
[09:05] <wgrant> xulrunner was 1.8.
[09:05] <wgrant> So it was always intended to be removed.
[09:05] <wgrant> (superseded by xulrunner-1.9, ie. firefox 3)
[09:07] <thekorn> wgrant, ah ok, thanks
[09:10] <thekorn> hmm, something is looking wrong there
[09:10] <wgrant> Hm?
[09:10] <thekorn> there is a python-xpcom package in karmic which depends on python2.5
[09:11] <wgrant> Right.
[09:11] <thekorn> it comes from this old xulrunner
[09:11] <wgrant> xulrunner never got removed.
[09:11] <wgrant> (I hadn't checked until just now)
[09:11] <thekorn> I guess there is a good reason for this ;)
[09:11] <wgrant> I doubt it.
[09:12] <thekorn> this multi version in the mozilla world is strage
[09:12] <wgrant> Duh. It is Mozilla.
[09:12] <micahg> ugh, we'll have to upgrade it for lucid
[09:12] <wgrant> micahg: Upgrade it to what?
[09:13] <micahg> I believe pyxpcom was broken out into its own project
[09:13] <thekorn> yeah, I want python-xpcom back in lucid, no matter how ;)
[09:13] <micahg> or it was replaced with something better
[09:13] <micahg> I don't remember exactly
[09:13] <wgrant> Something better... like WebKit?
[09:14] <micahg> no :P
[09:15] <micahg> http://benjamin.smedbergs.us/blog/2009-08-07/pyxpcom-welcome-todd-whitema/
[09:15] <thekorn> wgrant, in my understanding webkit does not replace python-xpcom, python-xpcom allows me to write a component for a Firefox extension in python
[09:16] <wgrant> thekorn: Ah. Even less useful.
[09:18] <micahg> well, I think xpcom is being replaced with Jetpack
[09:18] <micahg> maybe not replaced
[09:18] <micahg> but there's a new extension building suite coming for firefox 4
[09:19] <thekorn> micahg, ok, but this is far future
[09:20] <micahg> yes
[09:20] <micahg> so, we can try to package it for lucid
[09:28] <bo> The Ubuntu 9.10 RC livecd fails to boot for me, and I have filed a bug, but it appears that it is not associated with the karmic release in any way, and I can not find any to add it either. What to do?
[10:51] <matti> :)
[15:29] <wild_oscar> hey! anyone here working on alsa bugs?
[15:29] <wild_oscar> I know bug day was yesterday (though the channel was kinda dead)
[15:30] <wild_oscar> but I'd like to help regarding the bug https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/385076
[15:30] <ubot4> Launchpad bug 385076 in alsa-driver "[9.10 regression] HDA NVIDIA HDMI no sound after alsa 1.0.20 update" [Undecided,New]
[15:30] <wild_oscar> I found *a* solution to this issue, but I believe some improvements could be made
[15:32] <hggdh> wild_oscar: I am not really familiar with sound issues, but please comment on the bug what you found
[15:33] <hggdh> and this will be looked at (sound bugs are being actively pursued by some folks)
[15:33] <wild_oscar> hggdh: I have (comments #5 and 6)
[15:33] <wild_oscar> basically, I have found a way to solve the issue, but this isn't something john doe would do
[15:33] <wild_oscar> (running alsa mixer from the shell)
[15:34] <wild_oscar> and I'm not sure it can be achieve in the sound control from the tray applet)
[15:35] <hggdh> wild_oscar: good work
[15:35] <wild_oscar> hence the suggestion for improvement
[17:57] <dooglus> hi guys
[17:57] <dooglus> I found a bug which is already in the launchpad tracker, but marked as 'fix committed' from 2 years ago.  should I raise a duplicate?  or change the status of the old bug?  or what?
[17:59] <greg-g> dooglus: what is the bug?
[17:59] <greg-g> the bug number, rather
[17:59] <dooglus> greg-g: 126148
[17:59] <dooglus> I added a comment to it
[17:59] <dooglus> but the status probably means nobody will see it
[18:00] <greg-g> people subscribed to it will still see it
[18:00] <hggdh> bug 126148
[18:00] <ubot4> Launchpad bug 126148 in software-properties "GUTSY: synaptic select best server chooses repository without Gutsy packages" [High,Fix committed] https://launchpad.net/bugs/126148
[18:01] <hggdh> interesting bug, this one
[18:03] <dooglus> I noticed that the bug was talking about 'synaptic' and I saw it in 'software sources' - so maybe it's not a dup, I don't know
[18:03] <dooglus> I added a comment to that effect
[18:03] <dooglus> but didn't the 'pick best server' stuff just migrate from synaptic to 'software sources'?
[18:04] <hggdh> well, both of them can update the sources
[18:04] <dooglus> oh, I see
[18:04] <dooglus> so perhaps I can just use synaptic and that might work...
[18:04] <dooglus> I'll try that
[18:05] <hggdh> and -- I guess -- they both use the same back-end for that
[18:05] <dooglus> right, that's what I'm wondering
[18:06] <dooglus> can't check at the moment - apt-get is installing a bunch of updates
[18:06] <dooglus> but will when it's finished
[18:06] <hggdh> k
[18:07] <hggdh> but this one probably fell through a crack...
[18:14] <dooglus> synaptic actually runs 'software sources' to update the apt repository list
[18:15] <dooglus> so the bug happens there too
[18:18] <ikt> they changed over from apt-daemon iirc
[18:38] <joaopinto> bt_audio_service_open: connect() failed: Connection refused (111)
[18:38] <joaopinto> is this related to bluetooth ?
[18:39] <joaopinto> can someone else install and run glest and check ?
[18:39] <joaopinto> it seems to affect multiple games
[19:22] <hggdh> joaopinto: just running glest should show the issue?
[19:24] <hggdh> I am installing glest -- but it is slow, 25kps. I will walk my dogs, and be back in ~50m
[20:22] <bdmurray> mvo: I've a question about update-manager and recommends
[20:37] <dragonfi> Hello, if I have a bug about stuttering "login" sounds before and after the login screen in Karmik Koala, where should I post it? (alsa, gdm, or is there a special section for beta testing?)
[20:39] <joaopinto> hggdh, https://bugs.launchpad.net/ubuntu/+bugs?field.searchtext=bt_audio_service_open&orderby=-importance&search=Search&field.status%3Alist=NEW&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.assignee=&field.bug_reporter=&field.omit_dupes=on&field.has_patch=&field.has_
[20:39] <joaopinto> no_package=
[20:39] <joaopinto> it's filed for multiple packages but it seems to be asound/pulseaudio related
[20:41] <dragonfi> I would suspect the sound service too, but it actually only happens once, when I log in, every other sound works perfectley.
[20:41] <dragonfi> or it wasn't for me ? heh :)
[20:42] <hggdh> joaopinto: they all have PA installed?
[20:43] <hggdh> interesting, espeak seems to work fine here
[20:44] <joaopinto> hggdh, I believe i have disabled the bluetooth service
[20:44] <joaopinto> that could be the X factor :P
[20:45] <hggdh> joaopinto: bug 426437 seems to be both bad parameters and the errno=111
[20:45] <ubot4> Launchpad bug 426437 in espeak "espeak outputs incomprehensible audio, perhaps just too fast." [Undecided,New] https://launchpad.net/bugs/426437
[20:45] <hggdh> the reporter forgot to pass a *string*
[20:46] <joaopinto> I don't have any bt device, I don't understand this bt_audio* error
[20:46] <maco> screenreaders are usually incredibly fast anyway...thatd be normal
[20:46] <hggdh> I just disabled bluetooth (via right-click on the BT icon), and still no error. How did you disable it?
[20:47] <hggdh> maco, the user error is running 'espeak one two' as opposed to 'espeak "one two"'
[20:47] <maco> i would make the same error
[20:47] <maco> unless the docs specify "put quotes around it"
[20:47] <maco> if they dont specify that, doc bug
[20:48] <hggdh> well... I just run it again -- now it works (with BT disabled), but only speaks the first word
[20:48] <hggdh> which sounds more, er, correct
[20:49] <hggdh> this is crazy
[20:49] <hggdh> sometimes it works, sometimes it does not
[20:51] <slacker_nl> hello, can someone invalidate the following bug? 420098. The bug is also marked duplicate.
[20:52] <hggdh> slacker_nl: if it is a duplicate, it is already off the radar
[20:52] <hggdh> bug 420098
[20:52] <ubot4> Launchpad bug 420098 in resolvconf "[karmic] resolvconf not started at system boot (dup-of: 448095)" [Undecided,New] https://launchpad.net/bugs/420098
[20:52] <ubot4> Launchpad bug 448095 in resolvconf "resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces" [Undecided,Confirmed] https://launchpad.net/bugs/448095
[20:53] <hggdh> this is why you cannot invalidate it, even though it is still shown as "New"
[20:53] <slacker_nl> mmm, k
[20:54] <slacker_nl> but the duplicate status is invalid, imho
[20:54] <hggdh> ah.
[20:54] <hggdh> so you would like to un-duplicate it, and then mark invalid?
[20:54] <micahg> status is ignores on duplicates
[20:54] <slacker_nl> yes
[20:55] <micahg> *ignored
[20:55] <hggdh> click on "mark as duplicate", clear the field, click on OK
[20:55] <hggdh> then edit the status as needed
[20:55] <micahg> what's the point?
[20:55] <micahg> it'll just create bug noise
[20:56] <hggdh> micahg: yes, I agree. But for correcteness, it should be done
[20:57] <micahg> the only bug that people see if the one that it is a dupe of
[20:57] <micahg> the status of that one matters
[20:57] <slacker_nl> hggdh: thnx, overlooked the edit sign next to the duplicate bug
[20:58] <micahg> and there should be a flag for "All bugs reported" if a bug is a dupe
[21:05] <mvo> bdmurray: sure
[21:05] <mvo> bdmurray: what is the question
[21:06] <bdmurray> mvo: if a package gains recommends those are install by update-manager during a dist-upgrade right?  I have a couple of systems w/o some recommended packages and I'm trying to figure out why.
[21:06] <bdmurray> mvo: gains them between releases
[21:08] <mvo> bdmurray: it should add them if they are new
[21:08] <mvo> bdmurray: if you have a system like this, I would like to have the logs in /var/log/dist-upgrade
[21:09] <bdmurray> mvo: a system missing recommended packages?
[21:09] <mvo> yes
[21:10] <mvo> a system that got upgrade and where the new recommends are missing afterwards
[21:10] <bdmurray> Is there anyway to tell if I did an apt-get dist-upgrade instead of update-manager?  Or would that matter?
[21:10] <mvo> it should not matter
[21:11] <bdmurray> okay, great!
[21:11] <mvo> but with update-manager the log is better
[21:11] <mvo> :)
[21:12] <bdmurray> I saw synaptic has a filter for missing recommends is there a good way to get a dump of that?
[21:14] <mvo> bdmurray: apt-get install --fix-policy should give you a list as well
[21:33] <sbeattie> mvo: why do file conflicts only seem to go one way sometimes? e.g. if you install svk on karmic, it fails to install due to a conflict with a file from bash-completion. But if you then purge bash-completion and reinstall it, everything succeeds.
[21:34] <sbeattie> mvo: foh, nevermind
[21:35] <sbeattie> doh, even
[21:36] <sbeattie> it fails both ways, I just need afternoon coffee.
[21:36] <joaopinto> what's the package containing softaware center translations ?
[21:37] <joaopinto> Free Software is translated to "Gratis" Software
[21:48] <joaopinto> is anyone else experiencing high cpu usage with SDL games in general ?
[22:10] <BUGabundo> boas noites o/
[22:11] <joaopinto> oi BUGabundo
[22:11] <mvo> bdmurray: oh, and the synpatic filter should work too :)
[22:15] <BUGabundo> hey look, its mvo
[22:15] <BUGabundo> you are out of your time zone
[22:15] <BUGabundo> or at least time habbits :)
[22:16] <mvo> I am :)
[22:16] <mvo> its releae time
[22:20] <BUGabundo> not yet
[22:20] <BUGabundo> maybe release week !
[22:20] <BUGabundo> UM seems good
[22:20] <BUGabundo> what other packages are you looking after?
[22:21] <zorael> Should a bug report be filed if my sound chipset pops after returning from inactivity? (snd-hda-intel powersave feature)
[22:23] <zorael> (as per https://lists.ubuntu.com/archives/ubuntu-devel-discuss/2009-May/008239.html)