[01:52] <k-milogars> hello
[03:09] <andresmujica> dholbach: ping
[03:10] <andresmujica> hmm his not here..
[03:10] <persia> Try again in about three hours.
[03:10] <andresmujica> anyone knows if the 5-a-day is out of the repos?
[03:10] <persia> It's early there yet.
[03:10] <andresmujica> yepp. you're right that's the other side of the world :)
[03:14] <andresmujica> ohh, nop my mistake it's still there..
[03:20] <jbuncher> is there anyone in here that can help me "Confirm" a bug I reported on launchpad, where intel wireless seems unable to connect to hidden SSID on hardy kernel 2.6.24-23? (2.6.24-22 is fine)
[03:30] <jbuncher> Here is the bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/327431
[03:32] <vocx> jbuncher, how do you produce those formated strings with Problem type, Architecture, etc. in the bug report?
[03:35] <jbuncher> you mean the stuff at the bottom of the bugreport?  I ran "ubuntu-bug -p linux".  I assume the -p stands for "package" and "linux" tells it what package to file it under.  It then goes through apport or something and attaches that info at the end of the bugreport.
[03:35] <jbuncher> I found out about that through https://wiki.ubuntu.com/KernelTeamBugPolicies
[03:38] <jbuncher> vocx:  I don't suppose you have intel wireless and a wireless network you can not broadcast the ssid on with hardy kernel 2.6.24-23 in order to confirm the bug?
[03:39] <vocx> jbuncher, nope sorry.   But do you have a working TV card? Maybe you can help me
[03:39] <jbuncher> vocx:  yes, a PVR 150, but that's running *dapper*, so I don't think it's likely to be of help to anyone at this point :)
[03:40] <vocx> jbuncher, wow, you only use LTS releases?
[03:42] <jbuncher> vocx:  well, I just take a while to upgrade.  I was running gutsy for a long time on my laptop before upgrading to hardy (I use my laptop and desktop for research, so they *have* to work, so I do a lot of testing before undertaking the upgrade).  And as for dapper, that's running on a 700MHz Athlon with 384 MB of ram running myth, and I just dunno if it will be able to handle hardy :)
[03:44] <jbuncher> *loves you always*
[03:44] <vocx> jbuncher, at least install xawtv and tvtime, totem-gstreamer or totem-xine
[03:44] <jbuncher>  god damn
[03:44] <jbuncher> well that was in the wrong window
[03:44] <vocx> ...
[03:44] <vocx> thanks I guess
[03:44] <jbuncher> lol
[03:44] <jbuncher> that was definitely intended for my pidgin window, not xchat
[03:45] <jbuncher> vocx:  You want me to install xawtv and tvtime on my dapper machine with the tv card?
[03:46] <vocx> I know xawtv is probably going disappear soon, but I still think it's good when you can't watch TV with anything else
[03:47] <jbuncher> ah, for if/when I upgrade
[03:47] <jbuncher> I think my plan is to wipe it and install mythbuntu, should be a bit lighter-weight than a full hardy install.
[03:48] <vocx> https://bugs.launchpad.net/ubuntu/+source/tvtime/+bug/275275
[03:48] <jbuncher> that or buy some new (mid-low range) hardware once I don't have a car payment!
[03:49] <vocx> https://bugs.launchpad.net/ubuntu/+source/xawtv/+bug/319049
[03:52] <vocx> jbuncher, This one is probably the most serious, scroll to the bottom, it doesn't matter if you don't have fglrx, just follow my the instructions there https://bugs.launchpad.net/ubuntu/+source/tvtime/+bug/210132
[03:53] <lajjr> hello everyone.
[03:54] <thewrath> hey lajjr
[03:54] <jbuncher> vocx:  does this need to be run on the machine with the tv card?
[03:54] <lajjr> hi thewrath
[03:55] <thewrath> discussed in here is bugs for server and desktop?
[03:55] <vocx> jbuncher, yes
[03:55] <lajjr> good what bugs have come up yet?
[03:56] <lajjr> any eing talked about?
[03:56] <lajjr> eing=being
[03:56] <vocx> lajjr, do you have a working TV card?
[03:57] <lajjr> I have a tv card. and the code so far is only reversed engineered code.
[03:57] <thewrath> lajjr: not seen any yet
[03:58] <thewrath> will hopefully find some bugs soon
[03:58] <thewrath> i just joined the beta/alpha testing, etc
[03:58] <lajjr> yes it works but errors just have isolate them to make a stable package.
[03:58] <vocx> lajjr, mmm... what do you mean? Does it work or not? What chipset?
[03:59] <lajjr> hp ec680
[04:00] <vocx> jbuncher, you mentioned research, do you use latex, texlive? I'm using 8.10, and apparently some hyphenation patterns don't work.
[04:00] <lajjr> well it works with a error on select channel
[04:00] <thewrath> persia: the issue i talked to you about the wpa2 enterprise wireless is an issue USA wide
[04:01] <thewrath> well i sent that to someoen else but i thought i would mentiont hat in here
[04:01] <jbuncher> vocx:  yeah, I use latex and texlive.  I haven't had the chance to test a lot on 8.10 yet.  Do you have a link to a discussion of hte issue?
[04:02] <vocx> lajjr, try bugs #210132 #319049 #275275
[04:02] <persia> thewrath, I really don't know anything about wireless, wireless encryption schemes, or use of wireless in the US, and am really not the best person to address that.  Look for a bug in LP, or maybe someone else already knows about the bug, or maybe there's a workaround.
[04:02] <vocx> jbuncher, this is from debian, http://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg533438.html   let me get another link
[04:03] <thewrath> okay persia i meant to address that to the room
[04:03] <thewrath> i just copied what i sent you earlier
[04:03] <persia> No worries :)
[04:04] <thewrath> so persia  got to the first wiki site?
[04:04] <persia> type "/topic" and use the links there.
[04:04] <thewrath> yewa
[04:05] <thewrath> that is what i was using
[04:05] <thewrath> i just wnated to confirm it
[04:05] <jbuncher> vocx:  I get errors when trying to run tvtime on dapper, but they're not what you're looking for, it can't change the permissions on ~/.tvtime/tvtime.xml
[04:05] <jbuncher> thewrath:  what wireless issue are you talking about?
[04:06] <thewrath> 8.10 not connecting to wpa2 enterprise
[04:06] <thewrath> encrypted wireless networks
[04:07] <jbuncher> thewrath:  for all wireless chipsets?  is the ssid hidden?
[04:07] <thewrath> been told issue with network manager
[04:07] <thewrath> all chipsets and no the ssid is not hidden
[04:08] <jbuncher> thewrath:  ah ok.  I'm having an issue with hidden ssid wpa enterprise and intel chipsets on latest hardy kernel (-23).  -22 is fine so I don't hink this issue is network manager related.  I'm trying to find someone to help confirm the bug.
[04:08] <thewrath> ah
[04:09] <lajjr> vocx: I will look into those bugs to but my code is ripped from the exe for the driver.
[04:09] <thewrath> well jbuncher i am going to go to bed here soon so you going to be on tomorrow morning?
[04:09] <thewrath> i am in USA EST
[04:09] <thewrath> so i will be at work about 9am tomorrow
[04:10] <jbuncher> thewrath:  I should be, I'll try to get on after I take my car in.
[04:10] <thewrath> ah
[04:10] <thewrath> okay
[04:11] <vocx> lajjr, so you are really using a reverse-engineered driver? What's with that?
[04:11] <thewrath> just got my oil changed today then went on a 130 mile round trip ride lol
[04:11] <jbuncher> thewrath:  nice, I need to get a dent worked out that happened over christmas.
[04:13] <lajjr> yeah it works with my card I have. I can get the channel watch for awhile then when I switch it errors. I have to debug it.
[04:15] <vocx> jbuncher, here is a more clear description of the problem with hyphenation https://bugs.launchpad.net/ubuntu/+source/texlive-base/+bug/240823
[04:15] <vocx> jbuncher, you may also try installing texlive-lang-spanish and using \usepackage[english,spanish]{babel}
[04:16] <vocx> jbuncher, at least hyphenations worked in 7.10, since I was using it a month ago, then I fresh installed this 8.10
[04:16] <jbuncher> vocx:  Thanks for the info, though I don't use languages other than english, so I might be spared having to deal with that bug.  Hopefully they fix it soon though.
[04:18] <vocx> jbuncher, it's very simple, you just have to install the language pack, use babel, and it will mark an error saying that it will default to english, no need to write a single word in the foreign language
[04:18] <jbuncher> ah ok
[04:24] <jbuncher> vocx:  On my hardy install, I don't get errors when using babel as you suggested.
[04:24] <jbuncher> vocx:  so it may be relegated to intrepid
[04:25] <vocx> jbuncher, yes, seems like a bug concerning Texlive2008 as described in the bug report
[04:28] <lajjr> is anyone on here an admin from ubuntu bug control??
[04:32]  * lajjr is going to kick some code around.
[06:31] <Laibsch> maxb: I think I understand now.  You are a script guru!
[06:43] <dholbach> good morning
[07:31] <Ryan52> how do you mark  a bug as forwarded to an upstream bug tracker?
[07:33] <Ryan52> meh, /me writes it in a comment
[07:35] <persia> Ryan52, You add a bug task.  Which bug?
[07:36] <Ryan52> bug 330527
[07:37] <Ryan52> oh, lp figured it out for me.
[07:37] <Ryan52> (I think)
[07:38] <persia> You mean the "Remote Bug watches" portlet?
[07:38] <Ryan52> ya.
[07:38] <persia> Unfortunately, that doesn't show up in the "Fixed Elsewhere" search.
[07:39] <persia> So, the way that it's documented to do it is to use the "Also affects Project" button, and assign a bug to the gtsm project.
[07:39] <persia> Then, add your tracker URL to track that task.
[07:39] <Ryan52> I tried that...tho there's no gstm project.
[07:40] <persia> Well, you could register it: just note that it uses sourceforge for code and bugs.
[07:40] <Ryan52> o, ok, thanks.
[07:41] <persia> Personally, I liked the remote bug watches because they were easier, but it's nice to be able to start a new development cycle with a quick search for all the bugs already fixed somewhere else, and pull in the fixes.
[07:42] <Ryan52> okie doke. in this case upstream won't ever fix this bug, so it's fine :D
[07:42] <Ryan52> well, that's my assumption at least, but ya ;)
[07:42] <persia> Doesn't really matter: having the link works both ways.
[07:43] <persia> Because there's both tasks, if someone fixes it in Ubuntu, they are reminded to send the patch to the upstream bug as well.
[07:44] <Ryan52> ah, cool.
[11:43] <Elbrus> As I am in the process of adopting nedit in debian I am trying to figure out bug 309163. But I am no programmer, so what should I do (or learn) to be able to debug. I can not reproduce the bug.
[11:44] <Elbrus> Basically: what should I ask the reporter?
[14:16] <jeromeg> hello
[14:16] <jeromeg> I used to be a member of ubuntu-bugcontrol
[14:16] <jeromeg> but my membership expired a few monthes ago
[14:16] <jeromeg> could someone add me again ?
[14:19] <pedro_> jeromeg: hey, what's your launchpad id?
[14:19] <jeromeg> pedro_: jerome-guelfucci
[14:19] <pedro_> jeromeg: looking, give me a min
[14:19] <jeromeg> thank you !
[14:24] <pedro_> jeromeg: done, enjoy ;-)
[14:24] <jeromeg> pedro_: thanks a lot
[14:24] <pedro_> you're welcome, thanks for helping
[14:25]  * jeromeg will be able to set bugs as triged again :)
[14:25] <jeromeg> *triaged
[14:44] <bddebian> Boo
[14:47] <tuxmaniac> bddebian: mooo
[14:49] <bddebian> :)
[14:59] <thewrath> jbuncher: you there
[14:59] <jbuncher> thewrath:  Yes, but I have to head out for about an hour.
[15:01] <thewrath> oh ok
[15:01] <thewrath> you still having issues?
[15:01] <thewrath> with hidden SSIDs?
[15:01] <jbuncher> thewrath: yes, with intel wireless, wpa enterprise, and 2.6.24-23
[15:02] <jbuncher> I'm going to try to hide the ssid on my home router today to see if the problem exists with wpa personal
[15:58] <jbuncher> thewrath:  Back
[16:00] <BUGabundo> BOO
[16:35] <jbuncher> thewrath: hmm, it seems that I can access hidden ssid wpa-psk networks, but not hidden ssid wpa enterprise networks
[16:38] <jbuncher> is there anyone in here that can help me "Confirm" a bug I reported on launchpad, where intel wireless seems unable to connect to hidden SSID on hardy kernel 2.6.24-23? (2.6.24-22 is fine)
[16:38] <jbuncher> Here is the bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/327431
[19:23] <Laibsch> maxb: I reworked your script a bit, it encompasses all steps now and can work both with local and remote dsc files: http://rafb.net/p/FUuRLK76.html
[19:31] <Laibsch> http://ubuntu.csie.ntu.edu.tw is listed as a mirror in Asia, yet it does not even have a DNS entry.  Who is the person to inform?
[19:37] <Laibsch>  http://apt.nc.hcc.edu.tw seems to have problems, too
[19:40] <jbuncher> is there anyone in here that can help me "Confirm" a bug I reported on launchpad, where intel wireless seems unable to connect to hidden SSID on hardy kernel 2.6.24-23? (2.6.24-22 is fine)
[19:40] <jbuncher> Here is the bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/327431
[19:53] <persia> Laibsch, file a bug, and subscribe ~ubuntu-mirror-admins
[19:55] <Laibsch> OK
[19:55] <Laibsch> most of the Asian mirrors seem to be in a sorry state, actually
[20:46] <huayra> asac if you are there I would like to know if the nm-applet from your PPA is the same version in Jaunty daily
[20:48] <huayra> that way interested bug hunters can test the newest packaged code (2009-02-13)
[20:48] <huayra> and if it's not the same version as in your PPA, we just make people aware of the existence of a nm PPA for Jaunty ;)
[20:50] <huayra> as Dan suggested in the list, it would be cool if we, ubuntu hugers, at least have the option to help test the newest code available in tomorrows hug day
[20:50] <huayra> I'll be hunging around here if anyone has a comment
[21:01] <asac> huayra: what version is on jaunty daily CD?
[21:01] <asac> huayra: we have 0.7.1~  ... in jaunty now
[21:01] <asac> the PPA is not more recent for jaunty
[21:01] <asac> maybe for intrepid
[21:01] <asac> but not more recent for jaunty there
[21:04] <huayra> thanks asac, so if you make an upgrade previous to the hug day on jaunty you will have the most recent code available (13th of February in the PPA)?
[21:35] <asac> huayra: no. the most recent code is already there
[21:35] <asac> PPA has nothing new for jaunty
[21:40] <huayra> ok, got it
[21:41] <huayra> thanks asac
[21:41] <huayra> you are always so helpful :)
[21:54] <asac> welcome
[22:19] <joumetal> I am able to reproduce bug 331264. However startx is working.