[00:00] <bdmurray> visik7: hmmm, so meebo.com is the only tab is that right?
[00:01] <bdmurray> I'm not really in a position to close all my web browsers
[00:01] <visik7> yes no previous session
[00:01] <visik7> bdmurray: both for ff3 or epiphany ?
[00:01] <visik7> one of this 2 is enough for me
[00:03] <bdmurray> visik7: so new epiphany session, goto meebo.com, no crash
[00:03] <visik7> and running epiphany from the cli with meebo.com
[00:03] <visik7> as parameter
[00:03] <bdmurray> still no problem
[00:04] <visik7> ok so the bug is only for me :(
[00:11] <sectech> Launchpad offline for scheduled maintenance...  heh... I have been seeing that a lot lately with various sites
[00:14] <sectech> Hey does that mean you Canonical employees get a 2 hour lunch break? j/k
[00:15] <visik7> asd :)
[00:29] <bdmurray> bug 200009
[00:32] <n00dle> Anybody know what "https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/237278" contains? I picked the WORST time to run the updates....
[00:32] <n00dle> Yah...
[00:32]  * n00dle wants to shoot himself.
[00:32] <n00dle> ...but ubuntu's updater did it for me.
[00:53] <n00dle> Anyone here at all, or just no help for kernel update breaking VirtualBox?
[01:16] <chuckf> I have a question. I'm putting together the global bug jam day for the Maryland Loco team. One of the things I'm doing is getting a presentation to start off the day. How to file bugs/triage/5-a-day and other basics for beginners
[01:17] <chuckf> Is there a presentation already done that I can start from?
[01:23] <bdmurray> chuckf: I think wolfger, from the Michigan Loco, might have one that would be helpful
[01:23] <greg-g> bdmurray: do you have a copy of the 5-a-day playbook that jorge made?
[01:24] <chuckf> cool, I'll try to get in touch with him
[03:37] <mrooney> anyone know how to debug a pulseaudio issue, why apps can't play to it? anything I try to play in totem and rhythmbox sit at 0:00 (don't actually start), but switching to also and restarting the apps plays fine
[03:37] <mrooney> this is a not uncommon thing, whenever it happens I just have to restart
[04:04] <calc> cool LP is back up :)
[05:10] <kcormier> howdy
[05:10] <mrooney> allo
[05:10] <mrooney> and good night!
[05:11] <kcormier> so i'm new around here but i'm interested in learning to help out.  Any advice on where to get started?
[05:13] <persia> kcormier: I recommend starting with your bugs.  Pick things that you know broken, look for related bug reports, and help get them in shape.
[05:13] <persia> As you get more familiar with the bugs, you'll likely want to start chasing others in those packages you know well.  From there it gets interesting :)
[05:37] <kcormier> The problem is I'm not too familiar with anything specifically.  I'm kinda new to the linux scene.  Honestly I don't even understand how linux is developed entirely but I'm looking for someone who can help me learn and help me dive in.  I'm the type of person who prefers to just dive in and learn by doing in the thick of it.
[06:18] <shirish> ﻿hi all, I want to file a bug about the clock-applet in gnome-panel, what package should I file the bug against?
[06:19] <Hobbsee> shirish: it's part of gnome-panel, afaik
[06:19] <shirish> hi Hobbsee, thought so but still asked
[06:20] <shirish> thanx
[12:02] <snap-l> Any insight on what to do next about this bug re: gnuplot not being free? (bug 195111)
[12:03] <snap-l> It's confirmed, but how should I tag it, and mark it as something to be looked into?
[12:38] <james_w> hi snap-l
[12:39] <james_w> There was an idea to try escalating bugs via the bugsquad list, so could you post a summary and a link there please?
[12:43] <LimCore> hi, can anyone with amd64 (best, dual core) CPU confirm my bug?  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/240018
[12:44] <snap-l> james_w: The mailing list, right?
[12:44] <james_w> snap-l: yeah, sorry, ubuntu-bugsquad@lists.ubuntu.com
[12:45] <snap-l> Thanks!
[12:45] <afflux> LimCore: looking
[12:45] <james_w> the idea being that it can get some review there, and then someone will pass it on to somewhere more appropriate.
[12:46] <james_w> bdmurray: was escalating bugs via the bugsquad list something that it was decided we should try, or was it just an idea? Do you want to make a proposal to the list?
[12:48] <snap-l> james_w: posted. thanks again!
[12:48] <afflux> LimCore: I use the gnome frequency scaling applet (with setuid, for making it actually work) and it works on my AMD X2 3800+
[12:48] <afflux> LimCore: powernow-k8 is loaded
[12:48] <james_w> snap-l: thankyou
[12:49] <LimCore> afflux: so the problem is that powernow-k8 don't load for me
[12:49] <LimCore> can it be fault of mainboard?
[12:50] <afflux> seems to be the mainboard or the bios, not sure. I'm not a hardware/kernel guru though.
[12:50] <LimCore> what kernel?    2.6.24-16-generic     is it SMP?
[12:50] <afflux> Linux hegg 2.6.24-18-generic #1 SMP Wed May 28 19:28:38 UTC 2008 x86_64 GNU/Linux
[12:51] <LimCore> how you got this newer kernel?
[12:52] <afflux> I'm actually on intrepid, but it worked on my hardy system too.
[12:53] <james_w> LimCore: do you have -proposed enabled?
[12:53] <LimCore> no, how to do it?
[12:53] <LimCore> but ok, I do have kernel -19 in regular 8.04 it seems.
[12:54] <LimCore> james_w: how to use it? it's experimental repo?  Can I easly have all applications from normal 8.04 but only manually install some for -proposed to test them?
[12:54] <afflux> LimCore: in gnome you'll find it in system->administration->software sources, tab "updates"
[12:55] <afflux> LimCore: -proposed is actually the testing area for -updates. Every update after hardy release goes to proposed for testing and after that, will be copied to -updates.
[12:55] <james_w> LimCore: you could do with apt pinning. If -19 is in -updates now then there is no need at the moment I don't think. I didn't think it had transitioned yet.
[12:56] <LimCore> btw, how about addiging ubuntu packages for kernel.org packages?
[12:56] <LimCore> no ubuntu patches so  1) easy to package  2) good for people working on kernel development/testing
[12:57] <LimCore> i.e.:  linux-kernel.org-stable  and  linux-kernel.org-prepatch
[13:07] <Hobbsee> snap-l: replied to 195111
[13:08] <snap-l> Hobbsee: Thanks! Will check it out.
[13:31] <james_w> bug 240924
[13:31] <james_w> good title
[13:31] <afflux> hehe
[13:31] <afflux> any ideas on how to debug bug 221499? I don't own the hardware myself, but a friend does.
[13:37] <james_w> afflux: anything interesting in syslog?
[13:38] <afflux> james_w: "[  118.034393] NETDEV WATCHDOG: eth0: transmit timed out" as well as immediately afterwards: "[  118.050507] r8169: eth0: link up"
[13:40] <james_w> afflux: I'd stick that in the report, I didn't see it anywhere.
[13:40] <james_w> the first line at least.
[13:41] <afflux> they are the last two lines in the dmesg.log
[13:41] <james_w> ah, sorry, I missed it then
[13:41] <afflux> np
[13:57] <LimCore> my bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/240018  is a duplicate of old, now-closed bug https://launchpad.net/linux/+bug/33116   What to do? reopen the old? Close mine as duplicate?
[14:04] <LimCore> brb
[14:09] <qense> hello
[14:40] <cottima> hello, I do not know what words to search for or to file a bug with.
[14:41] <techno_freak> cottima, explain the bug you are speaking about
[14:42] <cottima> I am having trouble with some gnome or gtk programs catching keystrokes.  when I use nautilus it only respond to special shortcuts like F# keys and ctrl-*
[14:42] <techno_freak> ok
[14:43] <cottima> in firefox, it will sometimes it will either stop responding to keystrokes or i will have to alt-tab to another program and back before it will recognise the keystrokes
[14:43] <techno_freak> cottima, a bug should be explained with 4 points [1] what's the package or s/w you think the bug is, including it's version you are using [2] what did you expect to happen [3] what happened [4] how can we reproduce it?
[14:44] <cottima> and the save dialog box will not recognize keystrokes
[14:44] <techno_freak> cottima, so your bug is "firefox doesn
[14:44] <techno_freak> cottima, so your bug is "firefox doesn't recognize keystrokes at times, until the focus is swapped'
[14:46] <cottima> not really, I think it is with gnome or gtk not passing keystrokes.  but yes, with firefox it has to be swapped and swapped back to firefox
[14:46] <techno_freak> cottima, you may file the bug on firefox until you can reproduce the same on many other gnome apps
[14:47] <techno_freak> cottima, but first check firefox bugs whether something similar has been already reported
[14:48] <cottima> what about the fact that nautilus and save-dialog box never responds to char keystrokes?
[14:48] <techno_freak> cottima, so you say "nautilus and firefox doesn't respond to key strokes"
[14:49] <cottima> nautilus always (although a couple times it did) and less than half the time for firefox
[14:50] <techno_freak> cottima, then file a bug with similar description, specifying the s/w you encountered the bug
[14:50] <cottima> okay, Thank you techno_freak!
[14:50] <techno_freak> cottima, welcome :)
[15:21] <calc> i've found the source to probably most of the OOo crashes recently
[15:21] <calc> bug 18311
[15:21] <calc> er bug 185311
[15:30] <Balachmar> Hi when I boot normally I get a busybox command prompt, however when I boot in recovery mode, it boots normally
[15:31] <Balachmar> I have heard I should file a bug against the kernel, however I assume that more information is needed, so I want to ask what information I can gather
[15:35] <techno_freak> Balachmar, you can refer this - https://wiki.kubuntu.org/DebuggingKernelBoot
[15:36] <Balachmar> @techno_freak thanks
[15:44] <Balachmar> mmm, strange I removed the splash and the quiet and now it seems to hang @attached scsi generic sg7 type 0
[15:44] <Balachmar> which is probably the multimediacard reader
[15:44] <techno_freak> Balachmar, now you found where it hangs, you can find why it hangs ;)
[15:45] <Balachmar> @techno_freak but there aren't any errors and it doesn't end up with the busybox prompt anymore, is that normal?
[15:47] <techno_freak> Balachmar, by that you mean nothing is wrong?
[15:47] <Balachmar> no, it only goes to the prompt when I press enter
[15:48] <Balachmar> But I see something weird in the kernel parameters in the normal one, it has root= twice!
[15:48] <techno_freak> Balachmar, can you somewhere pastebin what you see? you might need to either look at it and type or write it down and then type
[15:49] <Balachmar> this one boots: kernel /vmlinuz-2.6.24-19-generic root=/dev/md1 ro single
[15:50] <techno_freak> ok
[15:50] <Balachmar> this one doesn't: kernel /vmliniz-2.6.24-19-generic root=/dev/md1 ro quiet splash root=/dev/md0
[15:51] <techno_freak> Balachmar, remove the second root and try to boot
[15:51] <techno_freak> Balachmar, just "kernel /vmliniz-2.6.24-19-generic root=/dev/md1 ro quiet splash"
[15:53] <Balachmar> that works, where did the second root come from...
[15:53] <techno_freak> Balachmar, was there a kernel update you did sometime in the near past?
[15:54] <Balachmar> I just installed the system today :)
[15:54] <Balachmar> the only update was the update after fresh install, but straight after fresh install I had the same problem
[15:54] <techno_freak> Balachmar, something that edited grub's menu.list might have made a mistake
[15:54] <techno_freak> Balachmar, so you mean you had the problem with fresh install?
[15:54] <Balachmar> yes
[15:55] <techno_freak> Balachmar, if possible can you try another fresh install and confirm whether the bug repeats?
[15:55] <Balachmar> I did mess up the install a bit, because first I had everything in raid5 and then had to redo it, since grub doesn't likt raid5
[15:55] <techno_freak> Balachmar, if would be of great use if the bug repeats, that you can confirm :)
[15:56] <Balachmar> I think it was cause by me redoing the partitions and maybe something remained on the mbr
[15:56] <techno_freak> Balachmar, that might have.if it is possible to do a fresh install and confirm yes/no, that would be great :)
[15:56] <Balachmar> (I don't really feel like reinstalling... been busy with building/installing the box like 6 hours
[15:56] <Balachmar> sorry...
[15:56] <techno_freak> Balachmar, it shouldn't be hard, just redo the install with same partition and stuff
[15:57] <techno_freak> Balachmar, no problem :) if you encounter the same problem again somewhere sometime, feel free to file a bug
[15:57] <Balachmar> will do, for now I think I was the bug :)
[15:57] <techno_freak> Balachmar, of course not, we are always ready to help with bugs, especially whether it is one or not ;)
[15:58] <Balachmar> If I edit the menu.lst now, will it be fine with another kernel update?
[15:58] <techno_freak> Balachmar, shouldn't be a problem
[15:58] <Balachmar> ok thank you very much
[15:58] <techno_freak> Balachmar, and you know where to check if the same problem occurs ;)
[15:58] <techno_freak> welcome :)
[15:59] <Balachmar> definitely
[16:23] <bdmurray> james_w: that's on my list of things to do - write wiki page, then e-mail list
[16:24] <james_w> bdmurray: great, thanks.
[16:40] <jibel> what do we do with old untouched bugs explicitly filed against edgy ?
[16:42] <bdmurray> jibel: determine if they still occur in Hardy
[16:44] <persia> jibel: If you're feeling especially adventerous and want to check any of feisty, gutsy, or intrepid, that may also be helpful (but not as much as hardy right now)
[16:45] <jibel> ok, we process them the same way as other untouched bugs even if edgy is not supported anymore ?
[16:46] <bdmurray> jibel: unless it is something we don't package any more like the 2.6.17 kernel
[16:50] <jibel> understood. thanks
[17:32] <jcastro> bdmurray: I'm going to ask a seemingly stupid question
[17:32] <persia> No such thing
[17:32] <jcastro> bdmurray: Are people supposed to be using triaged instead of confirmed?
[17:32] <bdmurray> persia: come on let me mock him
[17:33] <jcastro> heh
[17:33] <bdmurray> jcastro: that has actually 2Ca bit contentious
[17:33] <bdmurray> hmm
[17:33] <bdmurray> that has actually been a subject of great debate
[17:34] <bdmurray> However, I think that it should be used for no other reason than it is access controlled.
[17:34] <jcastro> ok, because right now +upstreamreport is tracking things that are triaged only.
[17:34] <bdmurray> s/no other/the simple/
[17:34] <jcastro> and kiko wants to keep it that way because an ACLed person is probably the one filing the bug upstream and creating the watch
[17:35] <jcastro> so we know there's a good chance it won't be wrong
[17:35] <bdmurray> I think that is unfortunate because confirmed has been around a lot longer than triager and we have a large backlog of bug reports
[17:35] <jcastro> yeah
[17:36] <jcastro> so any idea when the debate will be concluded? :)
[17:37] <jcastro> I think we need to decide sooner in the cycle rather than later
[17:37] <bdmurray> The debate stopped but feel free to start it again. ;)
[17:37] <jcastro> well, if we're going to do triaged then we should tell people to use it
[17:37] <bdmurray> One thing I've been doing is looking at Confirmed bugs to see if they are still valid and moving them to triaged.
[17:38] <jcastro> because I've been asking around because some of the numbers are really low for say .. openoffice
[17:38] <jcastro> but once calc moved a bunch to triaged the number made sense.
[17:38] <bdmurray> Right, I saw that discussion.
[17:39] <jcastro> so I am guessing that we need to let people know to move bugs to triaged.
[17:39] <bdmurray> Does that report give an indication of the packages not using Triaged much?
[17:39] <bdmurray> I think start with the biggest "offenders" would help.
[17:39] <jcastro> well, it shows open bugs then triaged, so you just subtract the two
[17:39] <seb128> jcastro: don't move confirmed bugs to triaged
[17:40] <jcastro> what about confirmed bugs that have an upstream watch?
[17:40] <seb128> or don't mass move those, that's not worth spamming subscribers, you will really annoy some people if you do that
[17:40] <jcastro> seb128: I'm just thinking outloud. :D
[17:40] <seb128> jcastro: still over a thousand desktop bugs to change in this case
[17:41] <seb128> and that's only a subset of bugs I'm speaking about ;-)
[17:41] <bdmurray> seb128: my thought was we would review the validity of the bug, manually, and if it is still valid then move it to triaged
[17:41] <jcastro> what if we say "from now on, used triaged"?
[17:41] <jcastro> which is what we're supposed to be doing, right? (or wrong?)
[17:41] <seb128> jcastro: we already do that no?
[17:41] <seb128> confirmed = somebody else has the issue
[17:41] <seb128> triaged = the bug has enough informations
[17:41] <jcastro> seb128: you guys do, but not everyone
[17:41] <jcastro> you guys being the desktop team
[17:42] <seb128> well, that's the wiki documentation says
[17:42] <seb128> not really, I don't like confirmed and we don't use it
[17:42] <jcastro> yeah I'm just not sure people are doing that
[17:42] <bdmurray> jcastro: this is why I think we should target specific packages not just "everyone"
[17:42] <jcastro> bdmurray: ok, so I would track down say, wine, and tell them to use triaged because their numbers look wrong, right?
[17:43] <bdmurray> jcastro: sure, however I'm not certain how many people looking at wine bugs have access to that state so that might be a different problem
[17:43] <seb128> jcastro: wrong metric still
[17:44] <seb128> what do you try to measure there?
[17:44] <seb128> things send upstream have an upstream task open
[17:44] <bdmurray> So far in June - 917 bugs have been set to Confirmed and 598 to Triaged.  So that seems like people are using it now.
[17:44] <jcastro> seb128: out of the # of bugs that are determined to be upstream, how many have an actual watch is what we want to track
[17:44] <seb128> jcastro: so count the watchs?
[17:45] <seb128> jcastro: number of upstream watch compared to the number of upstream tasks open give you the correct number
[17:46] <jcastro> seb128: right
[17:47] <jcastro> seb128: so you're saying, ignore the status?
[17:48] <seb128> yes
[17:48] <seb128> what information does it give you anyway?
[17:49] <jcastro> good point
[17:49] <seb128> we have lot of nicely forwarded bugs that are confirmed
[17:49] <seb128> what if somebody forget to change the ubuntu task and let it to new, does it mean the upstream bug should not count?
[17:49] <seb128> etc
[17:50] <jcastro> good point
[17:50] <seb128> and rejected bugs don't give you useful informations either
[17:50] <jcastro> plus this way I don't have to be involved in the triaged/confirmed holy-war. :p
[17:50] <seb128> you have no way to know if that was an invalid bug or if upstream just made a call and decided they don't want to do such chagnes
[17:52] <seb128> or rather no automatic way to make the difference ;-)
[18:23] <calc> is there a page that specifically states how to enable apport?
[18:23] <calc> i am getting crash bugs with no backtrace, etc which are a bit useless
[18:23] <calc> so i want to direct them to how to enable apport so they can report it properly
[18:25] <pedro_> calc:  no idea about a page, but there's an stock response with instructions on how to do it: https://wiki.ubuntu.com/Bugs/Responses#head-20ebac8207b4398d32f955193ac904e3c4228dea
[18:25] <calc> ok
[18:35] <bdmurray> pedro_: I thought enabling proposed or something like that had it
[18:36] <pedro_> bdmurray: indeed, https://wiki.ubuntu.com/Testing/EnableProposed ; thanks
[18:36] <pedro_> calc:  ^
[18:37] <shirish> hi guys, can somebody tell me how can I know if a certain library is a dependancy of which apps?
[18:37] <shirish> I know this information can be found out but don't know how
[18:41]  * calc thinks he has over stressed the disk io on his laptop
[18:41] <calc> things are starting to run really slow, heh
[18:42] <stgraber> calc: what about memory usage ? swapping ?
[18:49] <JohnPhys> Can anyone test this behavior:  Open up gedit, type in "MOVI" on the first line, and then anything on subsequent lines.  Save the file.  Gutsy now identifies this as some sort of movie file, and will not open in gedit when the file is double clicked.  The "MOVI" seems to be the critical part, "MOV" does not cause the bug.
[18:51] <qense> JohnPhys: I'm indeed told it's an SGI video
[18:51] <qense> I can confirm this on hardy
[18:51] <qense> for gedit(at least)
[18:51] <qense> and nautilus
[18:51] <qense> I'm told it's a video/x-sgi-movie file, although it's just plain text
[18:52] <snap-l> Sounds like it's using a some magic to figure out the file typ.e
[18:52] <snap-l> magic being the first four bytes of the file
[18:52] <qense> I can still open it with gedit, but when I try to open it with nautilus I get the error message that there is no suitable application installed
[18:52] <JohnPhys> Exactly
[18:53] <qense> however, both recognize it as an SGI video
[18:53] <JohnPhys> my friend encountered this when trying to open a file where he was listing his "MOVING OPTIONS" :)
[18:53] <JohnPhys> lowercase letters don't cause the bug either
[18:53] <qense> is it already reported?
[18:53] <JohnPhys> what package should this be filed against?
[18:53] <pedro_> can you test the following:
[18:54] <JohnPhys> I can't find it, but I'm not really sure what to search for
[18:54] <qense> mime-types?
[18:54] <qense> maybe shared-mime-info
[18:54] <pedro_> echo "MOVI" > test
[18:54] <pedro_> file test
[18:54] <pedro_> what's the output of that?
[18:55] <snap-l> test.txt: Silicon Graphics movie file \
[18:55] <snap-l> Under Feisty
[18:55] <pedro_> :-)
[18:55] <qense> it's now confirmed under feisty, gutsy and ahrdy
[18:55] <JohnPhys> test: Silicon Graphics movie file <--- Under gutsy
[18:55] <qense> /home/qense/test: Silicon Graphics movie file
[18:55] <qense>  
[18:55] <qense> on hardy
[18:56] <qense> according to the nautiljus properties dialog it's video/x-sgi-movie
[18:56] <pedro_> anybody has a sgi movie to look at those headers?
[18:56] <pedro_> maybe not a bug and tha'ts how the headers of those file types are
[18:57] <snap-l> I think it should be filed under the 'file' command
[18:57] <snap-l> With the directive that the magic file needs to be clarified
[18:57] <JohnPhys> still, it should be a bug, because "MOVING OPTIONS" should not trigger as an sgi movie
[18:57] <snap-l> :q
[18:57] <snap-l> (sorry... )
[18:57] <qense> are mime types statical or 'assigned' dynamically eg detected when you ask for it
[18:57] <qense> ?
[18:58] <JohnPhys> a search for "mime types sgi" in launchpad doesn't bring up anything
[18:58] <snap-l> Some clues for mimetypes appear to come from file (and /usr/share/file/magic.mgc)
[18:59] <snap-l> I tried one with "KICK", and it doesn't appear to have any issues
[19:00] <snap-l> Also with JFIF
[19:00] <JohnPhys> why are you trying KICK and JFIF?
[19:00] <snap-l> Appears there's something about MOVI
[19:00] <snap-l> Those are four character strings that preceed kickstart files and JPEG images
[19:01] <snap-l> just trying to see if there was a connection
[19:01] <JohnPhys> ah ok
[19:03] <snap-l> Try this... 1234moov
[19:03] <snap-l> Turns it into a quicktime file.
[19:03] <snap-l> Fun things to try are all in /usr/share/file/magic.mime
[19:05] <JohnPhys> wy does ti pick up 1234moov?
[19:08] <JohnPhys> can someone file a bug on this?
[19:08] <snap-l> Because the string pattern tells it to check the 5th position of the file.
[19:08] <JohnPhys> ah, i see
[19:11] <calc> stgraber: wasn't swapping since i have 4gb in my laptop but i was doing several disk intensive things at once which made the system fairly unresponsive
[19:12] <snap-l> The more I look into this, I'm thinking it's a bug against nautilus for not testing more thoroughly.
[19:12] <calc> its probably not a bug in nautilus, maybe in shared-mime-info
[19:12] <snap-l> I think we should tell the friend not to move anymore. :)
[19:12] <calc> depends on where it is getting its mime info from
[19:12] <snap-l> It's getting it from the magic file.
[19:12] <calc> the 1234moov worked fine for me on hardy
[19:12] <calc> i save it as test.txt and it thought it was text
[19:13] <snap-l> OK, maybe that's fixed then, because it showed up as a quicktime file under Feisty.
[19:13] <calc> ah without the .txt extension it thought it is a movie though
[19:14] <snap-l> Yeah.
[19:14] <snap-l> So we need the same for MOVI files
[19:14] <calc> you can't really foolproof mime detect all files
[19:14] <JohnPhys> gutsy thinks the 1234moov is a movie
[19:14] <calc> since the magic in most files is minimal
[19:14] <snap-l> Yeah, without decoding it
[19:15] <JohnPhys> well, if "MOVI" is sent to a file, and it is saved as "test.txt", gusty still thinks it is a movie
[19:15] <snap-l> "This file appears to be a movie, and plays though to completion, but the plot is boring, and the acting sub-par. refusing to play".
[19:15] <calc> MOVI > test.txt shows as text for me on hardy
[19:16] <calc> too bad someone didn't think to setup a iana type thing for internal filetype uid's
[19:17] <calc> then for all non text files you could have a uid at the beginning of the file which when looked up would tell exactly what kind of file it is
[19:17] <calc> so no real detection needed
[19:17] <calc> of course even then if you decided to store the long uid at the beginning of a text file it would show up wrong, but people would know not to do that ;-)
[19:23] <JohnPhys> still, shouldn't it be fixed in gusty, so that the file reads as a text file with the .txt extension?
[20:41] <bdmurray> mvo: bug 230752 has a response to your request for more information
[20:42] <mvo> bdmurray: thanks, checking
[20:43] <bdmurray> Oh hey! I didn't really expect you to be around. ;)
[21:22] <ubilicios> Hey guys the new banshee is giving me probs when I try to download a podcast it gets about 60% done then stops
[21:22] <ubilicios> I try the same podcast on rythymbox and I have no probs
[21:23] <ubilicios> ANyone seen this?
[21:24] <james_w> ubilicios: banshee 1.0?
[21:24] <james_w> from the PPA?
[21:24] <ubilicios> yeah
[21:24] <ubilicios> banshee 1
[21:24] <ubilicios> 1.0
[21:25] <ubilicios> PPA?
[21:25] <james_w> where did you install it from?
[21:25] <ubilicios> from the banshee repo
[21:26] <james_w> the one on launchpad? Or is there one on the banshee site?
[21:26] <ubilicios> banshees site
[21:26] <ubilicios> launchpad has one?
[21:26] <ubilicios> I didn't know
[21:27] <james_w> https://edge.launchpad.net/~banshee-team/+archive
[21:27] <james_w> anyway, I haven't used it for podcasts, so I can't confirm, sorry.
[21:27] <ubilicios> np I will try it on the launchpad
[21:50] <ubilicios> james_w:  Hey I just looked it up I did use the launchpad repo I thought I got it off the banshee site
[21:57] <Mr_Cheeto> Help, i have a bug! When I set my network settings everything works fine, then after say 1 minute it all reverts to some strange unknown settings. I'm using a Realtek 8139 card and i've looked all over the net, there doesn't seem to be any solution in any forums.
[21:58] <Mr_Cheeto> I would like to know if I could get support via phone?
[21:59] <bdmurray> Mr_Cheeto: for phone support - http://www.canonical.com/services/support
[22:01] <Mr_Cheeto> I want to know if somebody can help me 1o1
[22:09] <Cheeto> Can somebody help me 1o1?
[22:10] <greg-g> Cheeto: phone support from companies is here:  http://www.canonical.com/services/support
[22:10] <bdmurray> You might submit a question to http://answers.launchpad.net/ubuntu/
[22:11] <Cheeto> well I can't find a suitable phone service, I need a way to talk instantly *ie IRC or IM* and personally
[22:19] <Cheeto> ok here's the problem, my Kubuntu network settings are fine once i configure them, then about 20 seconds later they revert to some wierd setting and i have to set them back or it just doesn't work, I'm wondering if I'm missing something? how can i pin down my settings so they can't act up?
[22:22] <Cheeto> ......anyone?
[22:23] <bdmurray> this isn't really the best forum for a support issue like that
[22:24] <kenkku> Cheeto: try #kubuntu
[22:26] <CarlFK> https://blueprints.launchpad.net/ubuntu  is that the place to suggest "enable vim's embedded python mode" ?
[22:27] <afflux> CarlFK: I'd file a wishlist bug against vim, iirc blueprints are rather for plans that need some coding/different work
[22:28] <CarlFK> thanks
[22:28] <CarlFK> kinda seemed overkill
[22:28] <afflux> jep
[22:30] <sectech> Has the bugcontrol meeting already taken place?
[22:32] <kenkku> should I assign a bug I'm triaging to myself?
[22:33] <CarlFK> afflux: heh - just found sudo apt-get install vim-python
[22:33] <sectech> kenkku, are you the reporter?
[22:33] <bdmurray> kenkku: no, assignment is an indication that you are working on fixing the bug
[22:33] <afflux> CarlFK: ah okay, nice *g*
[22:34] <sectech> One thing I noticed over the last couple days was that reporters were confirming there own bugs... with information lacking...
[22:34] <kenkku> bdmurray: ok, it just said that in an irc log, although it's from 2007
[22:34] <kenkku> I'll unassign myself and instead subscribe to the bug then
[22:35] <bdmurray> kenkku: You haven't always been able to search for bugs you are subscribed to in Launchpad and that is why the procedure used to be different
[22:36] <bdmurray> sectech: It's perfectly reasonable to point them to Bugs/Status and set it back to New
[22:36] <kenkku> bdmurray: ok, thanks, now it's clear.
[22:36] <james_w> sectech: hi, which bugcontrol meeting do you mean? I don't remember hearing of one.
[22:36] <james_w> sectech: do you mean the QA meeting?
[22:36] <bdmurray> kenkku: where did you find this irc log?  is linked to from somewhere prominent?
[22:37] <kenkku> bdmurray: https://wiki.ubuntu.com/BugSquad/KnowledgeBase the first link, triaging class
[22:37] <bdmurray> that's great
[22:39] <bdmurray> kenkku: thanks, I'll work on fixing it
[22:42] <sectech> QA meeting
[22:42] <sectech> brb
[22:43] <Mr_Cheeto> !pastebin
[22:44] <Mr_Cheeto> sorry, just keeping track of my settings
[22:44] <Mr_Cheeto> !pastebin
[22:50] <LimCore> lol
[22:50] <LimCore> I failed epically.
[22:52] <LimCore> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/240018   <-- will this show up in search, so that people with similar issue can find the solutuion?
[22:53] <james_w> sectech: yes, the QA meeting was a few hours ago.
[22:54] <sectech> damn
[23:11] <jose__> Hello i have a bug with a package, the name is education-mathematics
[23:12] <james_w> jose__: hi, have you filed it in launchpad?
[23:13] <jose__> sorry i didn't, how i do that?
[23:14] <jose__> https://launchpad.net/ubuntu/+source/hello/+bugs
[23:14] <jose__> ??
[23:14] <james_w> go to https://bugs.launchpad.net/ubuntu/+source/debian-edu/+filebug
[23:14] <james_w> once you've finished you can paste the bug number here and we can have a look.
[23:15] <jose__> allright
[23:18] <sectech> james_w,  is there a log of what was discussed in the QA meeting?
[23:18] <james_w> sectech: I don't know if there are minutes, there is a log though, one moment.
[23:19] <james_w> http://irclogs.ubuntu.com/2008/06/18/%23ubuntu-meeting.html
[23:19] <james_w> it was the first meeting today, so it's not hard to find luckily.
[23:28] <jose__> james_w i reported the bug here https://bugs.launchpad.net/ubuntu/+source/debian-edu/+bug/241110
[23:30] <sectech> bdmurray, ping
[23:35] <sectech> Well I don't think the xubuntu ppl like me anymore lol
[23:41] <sectech> meh, all I see is the minutes from the ubuntu meeting
[23:42] <james_w> sectech: starts at 17:59
[23:42] <sectech> Does anyone know if there is a draft of what was agreed upon at UDS? because some of it appears to be already put into play even though it's not official
[23:43] <james_w> on what subject? everything, or something specific?
[23:43] <james_w> hey congratulations btw sectech
[23:44] <sectech> james_w,  A good example is that that "critical" (triage proper) is not the same as "critical" release proper...
[23:44] <james_w> I don't know anything about that one, sorry.
[23:45] <sectech> Example: A bug is critical need in being released for next cycle...  It doesn't match with what we use to triage...
[23:45] <sectech> james_w,  Thanks :)
[23:45] <sectech> about the congrats
[23:46] <james_w> jose__: sorry, I'm in a meeting as well. there's several reports of this, but I don't really know what's going on.
[23:46] <james_w> jose__: I do know the packages are intended for Debian, and they have problems on Ubuntu. For what purpose are you trying to install it?
[23:47] <jose__> i wanted to see the mathematics
[23:47] <jose__> of that
[23:48] <james_w> jose__: you might want to look in to
[23:48] <james_w> Recommends: drgeo, geg, gnuplot, grace, kig, kmplot, kpercentage, kseg, mathwar, maxima, octave, pari-gp, xabacus, xaos, xeukleides, yacas
[23:48] <james_w> Suggests: abakus, drgenius, k3dsurf, kalgebra, kbruch, kgeo, kregexpeditor, magicsquare, qliss3d, scilab, xarith, xeuklides
[23:48] <james_w> those are the packages that are related.
[23:48] <jose__> Now i more interested in how to remove it, but i think this is not the place to ask that
[23:50] <jose__> and thanks anyway for the recommends, i knew a couple of them but not all
[23:52] <bdmurray> sectech: pong
[23:57] <sectech> bdmurray, do you have a wiki setup with what was discussed at UDS? (if you look at my previous comments you see what I am referring to)
[23:59] <bdmurray> sectech: I've read the scrollback and I'm not certain what exactly you are referring to
[23:59] <sectech> I knew about workflow bugs but I was never brought into the issue until a hour ago when cody-sommerville asked me to attend an xubuntu-devel meeting