[06:07] <hot_wheelz> Hi,
[06:07] <hot_wheelz> If mythexport is part of Myhbuntu by default then how come when I brows to http://localhost/mythexport I'm greeted by page not found?
[06:09] <rhpot1991> hot_wheelz: did you install it?
[06:15] <hot_wheelz> rhport1991 i was told it was default
[06:17] <rhpot1991> hot_wheelz: its not, install it
[06:20] <hot_wheelz> by runnnig sudo apt-get update
[06:20] <hot_wheelz> sudo apt-get install mythexport atomicparsley
[06:20] <hot_wheelz> right
[06:22] <hot_wheelz> or just sudo apt-get install mythexport atomicparsley if i am up to date with all other updates?
[06:32] <hot_wheelz> rhport1991 please confirm
[06:44] <hot_wheelz> rhport1991 sorted
[06:44] <mycosys> confirmed hot_wheels
[06:45] <mycosys> or even simpler - sudo aptitude install mythexport should do it
[06:46] <mycosys> sorry for the misinformation it was mart of mythbuntu =- dont recall installing it and i have it but i am on jaunty still
[06:51] <hot_wheelz> np mycosys all taken care of now :-)
[06:54] <hot_wheelz> have a good1 guys :-)
[07:00] <mycosys> u2
[17:31] <adub_> kinda curious is there startup sound with mythbuntu
[17:31] <adub_> wondering if my sound is working on my systme
[18:50] <tgm4883`> adub_, nope
[18:50] <tgm4883`> no startup sound
[18:56] <adub_> tgm4883 do you have an nvidia card or is anyone in here using hdmi sound ??
[18:59] <tgm4883`> adub_, I do have an nvidia card
[18:59] <tgm4883`> but i'm not using hdmi sound
[20:14] <adub_> can anyone in here that is running mythbuntu 10.10 please explain what they did in order to get sound working via hdmi
[21:28] <mrand> adub_: you *might* (or might not) need updated alsa drivers.  https://wiki.ubuntu.com/Audio/InstallingLinuxAlsaDriverModules
[21:28] <Zinn> [wiki.ubuntu.com] Audio/InstallingLinuxAlsaDriverModules - Ubuntu Wiki


[01:42] <Nattgew> when and why is a bug assigned to someone?
[01:43] <jjesse> when someone takes a bug?
[01:43] <jjesse> an example i am going to work on a bug so i asign it to me
[01:47] <Nattgew> work on it like fix it or triage it
[01:48] <greg-g> fix it
[01:48] <jjesse> both
[01:48] <greg-g> if you are just triaging a bug, do NOT assign it to yourself (or another triager)
[01:48] <greg-g> no
[01:48] <greg-g> no
[01:48] <greg-g> that signifies that someone is working on fixing the problem
[01:48]  * greg-g apologizes for the repeated no
[01:49] <jjesse> np
[01:49] <Nattgew> so if someone randomly assigns a bug to me...?
[01:49] <greg-g> Nattgew: and you didn't say you were gonig to fix it, then feel free to remove the assignment
[01:49] <greg-g> which bug?
[01:50] <Nattgew> https://bugs.launchpad.net/ubuntu/+source/xsensors/+bug/183330
[01:50] <ubotu> Launchpad bug 183330 in xsensors "xsensors lacks support for coretemp module" [Undecided,New]
[01:50] <greg-g> jjesse: you are from Michigan yes?  I'm not sure if we have met, I'm Greg, the current team whip for Michigan
[01:50] <Nattgew> no, i'm not from michigan, but I've been there
[01:51] <Nattgew> oh, nvm, misread that
[01:52] <greg-g> Nattgew: I do believe there was talk of that being how we did things before, but now we aren't assigning triagers to bugs, just to reduce the confusion regarding who is really working on a fix for the bug
[01:52] <Nattgew> okay thanks
[01:52] <greg-g> yep, no prob
[03:04] <juaniv_a> hi i'm new in this lands
[03:05] <juaniv_a> i have recently signed to launchpad and the code of conduct
[03:05] <juaniv_a> i have recently applied for ubuntu-bugs team too
[03:06] <catterly> juaniv_a: hello and welcome!
[03:06] <juaniv_a> thanks
[03:07] <techno_freak> welcome juaniv_a
[03:07] <juaniv_a> I'm 20 years old and I'm from Argentina
[03:07] <juaniv_a> I've been using ubuntu for a year
[03:08] <juaniv_a> and I've been thinking that it would be nice if i can cooperate to make ubuntu better
[03:08] <juaniv_a> so that's why I'm here
[03:14] <catterly> juaniv_a: that is a pretty good reason, decided it was time to give back to the project?
[03:14] <catterly> that is why I came here as well, just yesterday or the other day, to help triage bugs for the upcoming release
[03:16] <JohnPhys> It's why I started running hardy on a spare partition
[03:17] <juaniv_a> yes it was to time to give back :)
[03:18] <juaniv_a> i read about the bug team
[03:18] <juaniv_a> but i don't understand quite well what do I have to do
[03:19] <catterly> well, basically you can follow this and #ubuntu-bugs-announce, which announces new bugs as they happen
[03:19] <catterly> from there you can mark bugs as duplicate, confirm them, and comment asking users for more information when necessary
[03:20] <catterly> all as appropriate
[03:20] <catterly> there is probably a wiki page somewhere...hmm...
[03:21] <yuriy> in /topic
[03:22] <catterly> oh, yes :]
[03:23] <juaniv_a> ok i'm reading :)
[03:27] <catterly> the HelpingWithBugs page seems to be an excellent resource!
[03:29] <techno_freak>  catterly https://wiki.ubuntu.com/Bugs/HowToTriage is your friend
[03:30] <juaniv_a> thank you
[03:39] <juaniv_a> where are you from?
[03:41] <yuriy> juaniv_a: US here. you should see about an Argentina local community team
[03:42] <yuriy> juaniv_a: https://wiki.ubuntu.com/ArgentinaTeam
[03:43] <juaniv_a> thank you, I am in the argentina team mailing list
[03:43] <yuriy> great :)
[04:07] <snerfu> I am new to submitting bus on launchpad, how do I make my bug non private?
[04:08] <snerfu> It has this lock icon up in the top right corner.
[04:08] <techno_freak> snerfu, bugs are non private by default
[04:09] <savvas> snerfu: there's a 'set privacy' on the left menu :)
[04:09] <snerfu> ah, ok thanks.
[04:10] <snerfu> There we go, non private. sweet.
[04:10] <savvas> be careful though, sometimes private bugs contain personal info
[04:11] <snerfu> I looked through all the logs included in it, I don't think it does. But I don't really have much personal info on there.  Hopefully enough to contact me if they need  more information.
[04:12] <savvas> I meant if you were doing anything bank-related or editing passwords and such :)
[04:12] <snerfu> Ahh, I got ya. Thanks for the tip.
[04:13] <snerfu> This was a minor glitch in soundconverter.
[04:43] <juaniv_a> I have a problem here
[04:44] <juaniv_a> rhythmbox doesn't make my tag changes
[04:44] <juaniv_a> for example i change artist tag
[04:44] <juaniv_a> and then it comes back as it was
[04:44] <juaniv_a> before
[05:23] <techno_freak> phew! my share for the bug bug is done :)
[05:23] <techno_freak> bug hug*
[05:29]  * yuriy hugs techno_freak
[05:30]  * techno_freak hugs yuriy
[05:30]  * yuriy hasn't done anything yet
[05:30] <techno_freak> yuriy, there are lot of edgy dapper bugs in them, i managed to clear some, you have more left
[05:31] <techno_freak> and before secretlondon arrives, we need a dupe-hunter ;)
[07:02] <techno_freak> ah here comes the dupe-hunter ;)
[07:03] <secretlondon> ;)
[07:51] <jussi01> Is ubiquity bug day still going on?
[07:53] <techno_freak> juaniv_a, think it just started ;)
[07:53] <techno_freak> err.. jussi01 ^^
[07:54] <jussi01> techno_freak: ok, great :D
[07:56] <jussi01> Hmmm, Ive no Idea where to start on this, but it would be great if we can get some work done on: https://bugs.edge.launchpad.net/ubuntu/+source/ubiquity/+bug/95886
[07:56] <ubotu> Launchpad bug 95886 in ubiquity "Wrong keyboard layout after installation (US instead of FI)" [Low,Confirmed]
[09:00] <gggggig> hi
[09:01] <gggggig> A game (fretsonfire) freezes my 2.6.24-12 kernel
[09:02] <gggggig> I tried to run it from ssh but it doesn't work, any ideas how to debug it?
[09:02] <secretlondon> gggggig, have you submitted a bug?
[09:02] <gggggig> secretlondon: no
[09:02] <secretlondon> gggggig, please submit a bug first
[09:03] <gggggig> secretlondon: I'd like to collect some data before.. do you know where to find some interestng log?
[09:04] <secretlondon> gggggig, if it actually freezes yours system then debugging system crash on the wiki
[09:05] <gggggig> secretlondon: do you have a link?
[09:05] <secretlondon> i can find one
[09:06]  * secretlondon has poor internet so it'll take a few seconds
[09:07] <secretlondon> gggggig, https://wiki.ubuntu.com/DebuggingSystemCrash
[09:07] <gggggig> secretlondon: ok, thanks
[09:09] <secretlondon> gggggig, also if its a game you may find stuff in ~.xsession-errors
[09:32] <secretlondon> https://wiki.ubuntu.com/UbuntuBugDay/20080325
[09:43] <gggggig> https://bugs.launchpad.net/ubuntu/+bug/206437
[09:43] <ubotu> Launchpad bug 206437 in ubuntu "kernel 2.6.24-12-generic freezes with nvidia" [Undecided,New]
[09:44] <gggggig> I tried DebuggingSystemCrash but I don't get any useful error
[09:44] <gggggig> .xsession-error has nothing releated to this bug
[09:45] <techno_freak> gggggig, xsession-errors will have errors related to X-session crashes
[09:45] <techno_freak> gggggig, the bug you show is a kernel bug
[09:45] <secretlondon> techno_freak, he said it was a crash with a game
[09:45] <secretlondon> techno_freak, sdl games tend to output a lot of xsession-errors
[09:46] <techno_freak> secretlondon, he is referring "kernel 2.6.24-12-generic freezes with nvidia"
[09:46] <gggggig> it could be an nvidia bug..
[09:46] <secretlondon> techno_freak, I know, but he originally told me it was a bug with fretsonfire, which is why I suggested xsession errors
[09:46] <gggggig> but in the but I got something in the dmesg
[09:46] <techno_freak> secretlondon, i agree to what you told :)
[09:47] <secretlondon> fretsonfire has loads of unloved bugs
[09:47] <techno_freak> secretlondon, may be he is generalizing all bugs to xsession-errors ;)
[09:47]  * secretlondon is now working through them
[09:47] <techno_freak> hmm
[09:48] <secretlondon> xsession-errors is useful for debugging games issues in my experience
[09:48] <gggggig> I played some day ago with Glest and I had no problem
[09:48] <gggggig> maybe is something related to f1 f2,.. keys
[09:48] <gggggig> even if I'm using metacity
[09:49] <secretlondon> I don't know, my laptop freezes every so often and I can't pin it down. could be hardware/software/anything
[09:49] <secretlondon> very annoying bugs
[09:56] <gggggig> see you later
[09:59] <secretlondon> bye
[10:53] <rgrig> james_w, thanks for the pointer to edos. it turns out we did the same thing :(. the output is a little bit different but that may be because of _our_ bugs :)
[10:54] <james_w> rgrig: no problem, did you take the same approach?
[10:55] <rgrig> james_w, yeah, there are only small differences (such as that we reuse minisat, while they reimplement it form the minisat paper)
[10:55] <james_w> ah, interesting that you came to the same solution.
[10:56] <rgrig> a little disappointing that we are one year late, though :)
[11:02] <james_w> can someone on hardy open rhythmbox and got to the Jamendo tab and see if they get any tracks please?
[11:05] <seb128> james_w: I get some text explaining what jamendo is
[11:05] <james_w> seb128: and does that disappear and show a track list?
[11:06] <seb128> james_w: do you get https://bugs.launchpad.net/bugs/203428?
[11:06] <ubotu> Launchpad bug 203428 in rhythmbox "jamendo no loading catalogue" [Medium,Invalid]
[11:06] <james_w> it appears as though Jamendo have changed the format of the dbdump file that rhythmbox uses to get the track information, so it shows no tracks.
[11:07] <james_w> it's different to that bug, but I think it's the same cause.
[11:07] <pedro_> morning
[11:07] <seb128> the bug states that's what jamendo sends is buggy though
[11:07] <seb128> hey hey pedro_
[11:08] <pedro_> bonjour seb128
[11:22] <secretlondon> hi pedro_
[11:22] <secretlondon> pedro_, do you have the perms to update the /topic with today's hug day?
[11:23] <pedro_> secretlondon: hello, no sadly i don't :-(
[11:23] <secretlondon> I've updated the wiki
[11:39] <salty-horse> hi. is anyone upgrading from gutsy->hardy any time soon? I'd like to reproduce a problem with date&time configuration migration
[11:44] <heno> salty-horse: please ask liw in #ubuntu-testing. He's starting on a series of upgrade tests now
[11:45] <salty-horse> great. thanks!
[12:28] <dako3256> test
[12:28] <ogra_cmpc> failed
[12:34] <Iulian> Hey
[12:39] <hammera> Hello! My name is Attila Hammer. My hardy beta installation is good, except the final restart. the installer not restart my computer.
[12:39] <hammera> Possible because I launch ubiquity with terminal?
[13:15] <urc_jim> morning all
[13:16] <catterly> good morning!
[14:12]  * heno waves to simira
[14:13] <heno> *** HUG DAY TIP ***: Here is a good place to find exiting bugs for duplicate candidates: http://people.ubuntu.com/~brian/reports/gt5comments/ubiquity.html
[14:13] <heno> and http://people.ubuntu.com/~brian/reports/gt5subscribers/ubiquity.html also
[14:14] <Iulian> Awesome
[14:16] <pascal80> How should translation related bugs be handled?
[14:16] <pascal80> E.g. bug #206524
[14:16] <ubotu> Launchpad bug 206524 in ubuntu "Upgrade to 8.04 window has incoherent messages" [Undecided,New] https://launchpad.net/bugs/206524
[14:19] <pedro_> pascal80: that's french right? you may want to assign it to the language-pack-fr then
[14:21] <Iulian> Hi pedro_
[14:21] <pedro_> hey Iulian, how are you today?
[14:22] <Iulian> I'm doing fine, thanks. What about you?
[14:23] <pascal80> pedro_: Yes that's French, I subscribed ubuntu-l10n-fr
[14:23] <pascal80> pedro_: Was this the right thing to do?
[14:23] <pedro_> Iulian: pretty good also, enjoying the day ;-)
[14:24] <seb128> reassigning to language-pack-gnome-fr too
[14:24] <pedro_> pascal80: yes, language-pack-fr would work
[14:24] <pedro_> ah yes what seb128 said too
[14:30] <pedro_> sourcercito: does it works now?
[14:30] <sourcercito> pedro_, i'm actually waiting until some page with a problematic image loads
[14:31] <sourcercito> you know, me and my great ISP
[14:31] <sourcercito> :P
[14:31] <pedro_> lol
[14:32] <sourcercito> yup, seems to work just fine here :P
[14:35] <pedro_> cool
[14:58] <afflux> morning
[14:58] <bicyclist> Good morning.
[14:58] <bicyclist> does anyone else have those weird pink shadows in compiz when running Hardy Heron ?
[14:59] <afflux> bicyclist: I don't. Do you have a screenshot?
[15:00] <bicyclist> Well yes.
[15:00] <Iulian> That bug is already reported to LP, let me search it.
[15:01] <bicyclist> I am just wondering is it a thing that will be fixed in by the bugsquad or do we have to wait for a reaction of NVidia ?
[15:02] <Iulian> See bug 186382
[15:02] <ubotu> Launchpad bug 186382 in linux-restricted-modules-2.6.24 "[nvidia 169.xx] gtk window decorator somtimes draws decoration ugly or not at all" [Low,Confirmed] https://launchpad.net/bugs/186382
[15:02] <Iulian> Is it the same bug that you have?
[15:09] <sourcercito> secretlondon, could you please free the lock at 5-a-day repo
[15:10] <sourcercito> entering to ~/.5-a-day-data and executing "bzr break-lock" will do the trick
[15:11] <james_w> sourcercito, secretlondon: bzr break-lock remote-url is probably what you want.
[15:12] <sourcercito> sure, that would work too :D, if you can remember the url ;)
[15:12] <james_w> bzr break-lock<EMAIL_ADDRESS>[15:13] <bicyclis1> But it is the bug that marcelo reports. OTher than the pink shadows all my windows are just fine !
[15:13] <juaniv_a> hi
[15:16] <juaniv_a> what do I have to do if I assign a bug to myself?
[15:16] <bicyclis1> juaniv_a I assume... fix it ?
[15:17] <juaniv_a> I supposed
[15:17] <juaniv_a> mmm so it's nobody :P
[15:17] <juaniv_a> i don't know how to fix it
[15:17] <juaniv_a> i'm new sorry for my questions :P
[15:18] <sourcercito> juaniv_a, hi there
[15:18] <qense> hello
[15:18] <bicyclis1> Hey, no offense meant
[15:18] <bicyclis1> besides fixing it can also mean finding out who can help with the code.
[15:19] <bicyclis1> Or if there is a workaround to be documented.
[15:19] <sourcercito> if you can't solve the bug yourself, you could ask any relevant information there is to it, so when all the information is provided the source of the problem can be easily identified
[15:20] <bicyclis1> Has anyone any idea why camorama states it cannot open /dev/video0 yet Camera Monitor informs me that the cam has been activated  Everything works fine with cheese.
[15:21] <afflux> bicyclis1: camorama -D
[15:21] <qense> happy hug day btw
[15:21] <afflux> uh, hugday o.o
[15:22] <afflux> it's holidays for me, so I forgot the date :)
[15:24] <afflux> bicyclis1: depending on the debug output, it could be a duplicate of bug 201030
[15:24] <ubotu> Launchpad bug 201030 in camorama "[7.10] Could not connect to video device (/dev/video0)" [Medium,New] https://launchpad.net/bugs/201030
[15:28] <qense> BUg 206031 indicates that there could be a problem with the CD upgrading. But does anyone know what things could help solving this?
[15:28] <ubotu> Launchpad bug 206031 in console-tools "package console-tools 1:0.2.3dbs-65ubuntu5 failed to install/upgrade: " [Undecided,Confirmed] https://launchpad.net/bugs/206031
[15:39] <bicyclis1> Yupp, ubotu, that is the bug i have, have provided my information as requested in the bug report
[15:41] <afflux> bicyclis1: ubotu is a bot :)
[15:42] <bicyclis1> Grin, i once studied ai so i am still polite to any "artificial intelligence" ;)
[15:42] <afflux> hehe
[15:42] <afflux> bicyclis1: what webcam are you using?
[15:42] <bicyclis1> Well, you never know when they rule the world ;)
[15:43] <bicyclis1> The Webcam built in to my Sony Vaio VGN-FZ31J. Sony Motion Eye webcam, which needs the ricoh drivers.
[15:43] <afflux> what's the device name reported by camorama -D?
[15:43] <bicyclis1> One good point about Hardy Heron already. In Gutsy i had to compile them myself, hardy detected the cam.
[15:43] <afflux> or maybe you can even attach your "camorama -D"
[15:44] <bicyclis1> it is video0 which is recognized by skype and cheese but not camorama
[15:45] <bicyclis1> I adde camorama -D output to the bug report
[15:46] <afflux> thank you very much
[15:47] <bicyclis1> The pleasure is on my side. Love to make a very good ubuntu release even better ;)
[15:47] <pedro_> uh uh have the same camera on my sony vaio
[15:48] <afflux> pedro_: same?
[15:48] <pedro_> not it's broken sadly :-/
[15:48] <pedro_> too much travel i guess...
[15:48] <qense> Does anyone know more about the CD upgrades to help with bug 206031?
[15:48] <ubotu> Launchpad bug 206031 in console-tools "package console-tools 1:0.2.3dbs-65ubuntu5 failed to install/upgrade: " [Undecided,Confirmed] https://launchpad.net/bugs/206031
[15:49] <afflux> bicyclis1: looking at the debug output it seems quite different
[15:49] <pedro_> qense: liw is doing some upgrade testing you can ask him at #ubuntu-testing
[15:50] <qense> ok, thx
[15:50] <afflux> bicyclis1: I think you should report a new bug against "camorama" with "'could not set window info' on Sony Motion Eye", and attach the output and you description, (eg. versions etc.)
[15:50] <afflux> bicyclis1: sorry for the confusion :)
[15:51] <bicyclis1> Ok, no problem will open a new bug !
[15:56] <bicyclis1> afflux: New bug has been reported ;)
[15:57] <afflux> bicyclis1: perfect
[15:57] <bicyclis1> Now continuing the hunt for new ones :)
[15:59] <afflux> bicyclis1: does the cam show up in lsusb?
[16:00] <bicyclis1> Yes:Bus 006 Device 002: ID 05ca:183b Ricoh Co., Ltd
[16:00] <bicyclis1> And it works with motion, cheese and skype.
[16:00] <afflux> bicyclis1: can you attach lsusb -v as a seperate file?
[16:01] <bicyclis1> Sure:
[16:04] <afflux> bicyclis1: I'm going to have a coffee now, I'll mark your bug when I get back
[16:04] <bicyclis1> Ok, attachment is being provided.
[16:38] <Nattgew> if i have a program crashing, and apport isn't coming up, is there any way to make apport handle the crash?
[16:43] <bddebian> Boo
[16:45] <afflux> morning brian
[16:46] <afflux> * bddebian
[16:46] <pochu> Nattgew: double-click the crash in nautilus in /var/crash/
[16:46] <bddebian> Hello afflux
[16:47] <Iulian> Heheh
[16:47] <Iulian> Hi there bddebian :)
[16:48] <afflux> is the 5-a-day branchs unlocked again?
[16:49] <Nattgew> ah pochu thanks but if it doesn't leave anything in /var/crash?
[16:50] <pochu> oh, it should AFAIK
[16:50] <pochu> ls /var/crash/
[16:50] <pochu> language-pack-en.0.crash  _usr_bin_terminator.1000.crash
[16:51] <Nattgew> yeah i did find something in there but it's gksu and i'm looking for evolution
[16:51] <bddebian> Hello Iulian
[17:08] <bicyclist> afflux: Information concerning camorama has been added.
[17:08] <afflux> bicyclist: ah right
[17:10] <afflux> bicyclist: marked the bug as triaged
[17:10] <bicyclist> Good, it is not very important to me but another bug probably fixed ;)
[17:11] <afflux> hm?
[17:12] <bicyclist> A bug found is often a bug fixed ..
[18:11] <CarlFK> how do I report a bug against  https://launchpad.net/ubuntu/hardy/i386/linux-restricted-modules-2.6.24-12-386/<IP_ADDRESS>-12.31
[18:11] <CarlFK> the bug is the %d in [54691.507105] wifi%d: unable to attach hardware: 'Hardware didn't respond as expected' (HAL status 3)
[18:12] <CarlFK> just the cosmettics of the %d, not that it doesn't work.
[18:12] <bicyclist> Hmm, just found that there exists a new version of envy named envyng. Will try to install it now and see if i can fix de shadow bugs in gnome with that install.
[18:20] <bicyclist> Hmm, ok. Envy NG will not fix the pink shadow bug .. :(
[18:36] <secretlondon> james_w been out
[18:36] <secretlondon> no idea why it was locked
[18:37] <james_w> secretlondon: it may have crashed during a commit at some point.
[18:37] <secretlondon> bzr: ERROR: Not a branch<EMAIL_ADDRESS>[18:37] <james_w> I hope you had a good day though.
[18:37] <secretlondon> been applying for jobs
[18:37] <secretlondon> I'm more productive out of the flat
[18:38] <james_w> Ah, sorry, I edited wrong "bzr break-lock<EMAIL_ADDRESS>[18:38] <james_w> extra "E" before.
[18:38] <james_w> any good ones today?
[18:40] <secretlondon> james_w, well it's hopefully done something
[18:41] <secretlondon> I think the 5 a day applet needs rewriting if one person can break it
[18:41] <secretlondon> james_w I may have a job, I find out on thurs
[18:42] <james_w> cool, good luck!
[18:50] <bicyclist> Could the energy control applet be broken ? It doesn't show a single line above 0 %
[18:53] <greg-g> anybody having problems submitting to 5-a-day? http://www.paste2.org/p/17423
[18:53] <secretlondon> I unlocked it, apparently I'd crashed it or something..
[18:53] <secretlondon> been out for 6 hours
[18:54] <greg-g> everybody is getting that error?
[18:54] <greg-g> hmmm
[18:54] <secretlondon> I dunno
[18:55] <greg-g> others apparently are committing fine (looking at the launchpad page)
[18:56] <james_w> greg-g: try 'cd ~/.5-a-day-data/ && bzr update && bzr ci -m "update"'
[18:56] <greg-g> ci -m ?
[18:56] <greg-g> just curious what is it
[18:57] <thekorn> alias for 'commit'
[18:57] <greg-g> ah
[18:59] <greg-g> no errors, we'll see what the codebrowse says
[19:02] <greg-g> and verified, thanks james_w / thekorn
[19:02] <james_w> no problem
[19:44] <qense> is bug 203262 a high or medium?
[19:44] <ubotu> Launchpad bug 203262 in hwtest "hwtest fails preconfigure" [Undecided,Confirmed] https://launchpad.net/bugs/203262
[19:44] <qense> I think high since it prevents a lot of people from upgrading but I am not sure since high is a very high importance
[19:53] <qense> I'm marking it as high now
[19:55] <bicyclist> hmm getting cd bzr: ERROR: extra argument to command checkout: /home/uwe/.5-a-day-data
[19:55] <bicyclist> bzr failed with error code 768
[19:55] <bicyclist> from add-5-a-day
[19:56] <shaya> sort of wondering why the vmsplice() security hole hasn't been fixed in gutsy?
[19:57] <james_w> bicyclist: do you have the most recent version?
[19:58] <bicyclist> i think so, installed it today.
[19:58] <bicyclist> my launchpad user is my email adress, right ?
[19:58] <james_w> bicyclist: your ~/.bzr.log should have some more information.
[19:59] <james_w> bicyclist: no, mine is james-w
[19:59] <secretlondon> no its you launchpad name
[19:59] <james_w> if you log in to launchpad and click on your name in the top right you will be taken to your home page
[19:59] <secretlondon> so mine is secretlondon, and not my real name
[19:59] <secretlondon> after ~
[19:59] <james_w> the bit after "~" is your username
[20:00] <bicyclist> hmm ok, mine is Uwe Hauck. Does taht mean the thing has a problem with the space ?
[20:00] <qense> does the username can have spaces?
[20:01] <bicyclist> Well mine has !
[20:01] <greg-g> what is in the location bar of your browser?
[20:01] <bicyclist> ah ok, mixed Display name with name..    I need to re-do those diffs, as mentioned in the last comment. Will do so now.
[21:55] <blueyed> bug 195691
[21:55] <ubotu> Launchpad bug 195691 in dspam "[dspam] [CVE-2007-6418] programming error leading to information disclosure" [Medium,Fix released] https://launchpad.net/bugs/195691
[22:01] <josephpiche> I believe bug 3868 should be marked as a duplicate of bug 7560, but since these are low number bugs, I want to get someone else's opinion
[22:01] <ubotu> Launchpad bug 3868 in nautilus "Emptying trash should really empty trash" [Medium,Confirmed] https://launchpad.net/bugs/3868
[22:01] <ubotu> Launchpad bug 7560 in nautilus "Wastebasket fails with read only directories" [Unknown,Confirmed] https://launchpad.net/bugs/7560
[22:05] <keescook> blueyed: we've been using "In Progress" to mean there are patches ready for sponsoring.
[22:06] <keescook> blueyed: so when I run through the queue and there is a bug marked "In Progress", I flip it back to "Triaged" if it's ready
[22:06] <keescook> er, not ready
[22:06] <blueyed> keescook: really? for security related bugs?
[22:06] <blueyed> so, when the patch is ready I should mark it "in progress"? sounds strange..
[22:07] <keescook> blueyed: yeah.  we needed a way to map to "actual problem" (confirmed), "fix known" (triaged), "needs sponsorship" (in progress), "has been uploaded" (fix committed), and "published in the archive" (fix released)
[22:08]  * DOOM_NX gn all! - Battery Empty
[22:15]  * calc uses In Progress on OOo bugs to mean i need to fix it for the next upload if at all possible, heh
[22:16] <keescook> yeah, the status usage for security is a bit odd
[22:19] <seb128> keescook: "has been uploaded" (fix committed), do you guys really use that?
[22:21] <seb128> I guess it makes sense for security uploads to make sure they have been built and published everywhere
[22:27] <keescook> seb128: yeah, we need it due to the dak/soyuz split
[22:38] <grovers> hello - I have a patched package, I'm just trying to figure out the process to get it into the next upload
[22:39] <secretlondon> you need to make a debdiff
[22:41] <grovers> so, following the packaging guide from here on out? I ask just because the bug fixing article doesn't point anywhere after making the new package
[22:43] <secretlondon> it's probably on the motu miki pages somewhere
[22:43] <secretlondon> I'm not sure from there
[22:44] <grovers> i've got it, thanks, found another good wiki page
[23:06] <blueyed> keescook: /me refreshed/fixed the diffs for bug 195691 and set the status to in progress (unassigning myself).
[23:06] <ubotu> Launchpad bug 195691 in dspam "[dspam] [CVE-2007-6418] programming error leading to information disclosure" [Medium,In progress] https://launchpad.net/bugs/195691
[23:07] <keescook> blueyed: great! thanks.  I will probably get to them tomorrow.  I'm currently building/testing the ruby1.8 updates


[01:00] <Keybuk> kees: random thought of the day
[01:00] <Keybuk> swap-on-RAID1 is insane, right? :p
[01:01] <kees> insane? no, it's a good idea.
[01:01] <Keybuk> really, why?
[01:01] <kees> because if you lose a drive you don't eat your system?
[01:01] <Keybuk> doesn't md have a performance penalty though?
[01:02] <kees> people using raid1 generally either have a raid1 swap partition or put swap in a file in the raid'd root fs
[01:02] <kees> *shrug*
[01:02] <kees> if you're swapping that much, who cares?  :)
[01:02] <Keybuk> lol
[01:02] <Keybuk> a fair point
[01:03] <kees> what's insane is swap over network block device.  but then lots of things are insane about LTSP.  ;)
[01:03] <Keybuk> I'm being creative
[01:03] <Keybuk> I'm setting this machine up so that its 1TB drive is divided into three RAID-1s
[01:03] <Keybuk> a 256MB for /boot, a 2GB for swap and the rest for LVM
[01:03] <Keybuk> but no second drive ;)
[01:03] <kees> for testing, I assume?
[01:04] <Keybuk> that and future proofing
[01:04] <kees> if you don't intend to ever hibernate, just but your swap in the LVM
[01:04] <kees> s/but/put
[01:04] <Keybuk> it's a file server, so I might want to put a second disk in later and actually do RAID-1
[01:04] <Keybuk> thus it's most logical to set it up as LVM-on-MD rather than just plain LVM
[01:04] <kees> aaah, you're doing a degraded raid1?
[01:04] <Keybuk> is it degraded?
[01:05] <kees> if you only have 1 drive it is.  :P
[01:05] <Keybuk> why?
[01:05] <kees> uhm... because... there's... no mirror?  :P
[01:05] <Keybuk> RAID-1 can be anything from 1..n drives
[01:05] <Keybuk> it just happens that most people use 2 :p
[01:06] <kees> well, I've never tried mdadm --grow -n 2  on a -n 1 array before
[01:07] <Keybuk> it works
[01:07] <kees> hah  -n: Setting a value of 1 is prob‐
[01:07] <kees>               ably  a mistake and so requires that --force be specified first.
[01:07] <kees> cool, yeah, that'll fly.  I've never used it myself.
[01:07] <Keybuk> I actually saw it on someone else's system
[01:08] <kees> anyway, in that case, use 2 MDs, one for boot, one for LVM
[01:08] <Keybuk> and though "damn, that's a _good_ default setup"
[01:08] <kees> just make swap another lv within the LVM
[01:08] <infinity> Keybuk: swap-on-raid is not only sane, but really the only way to go for the magical five-nines.
[01:08] <kees> I tend to buy drives in pairs, so I can add/remove protected md arrays as pvs to my VGs
[01:09] <Keybuk> kees: why swap-on-LV instead of swap-on-MD ?
[01:09] <infinity> Keybuk: If your have non-raid swap, when a drive dies, your kernel panics.
[01:09] <kees> Keybuk: because then it's easier to move around
[01:09] <Keybuk> kees: but impossible to resume from?
[01:09] <Keybuk> (in fact, why is it impossible to hibernate to/from it?)
[01:09] <kees> well, you said file-server.
[01:10] <kees> I said "if you never hibernate..." earlier somewhere
[01:10] <infinity> Keybuk: Impossible to restore from an MD/LV swap because the kernel goes looking for hibernate signatures on swap partitions long before we load any MD/LV drivers.
[01:10] <kees> it is possible, but you have to specify the allocation map
[01:10] <Keybuk> if we did MD and LVM by default
[01:10] <infinity> Keybuk: This isn't an unsurmountable problem.
[01:10] <Keybuk> would you do swap-on-MD or swap-on-LV ?
[01:11] <Keybuk> infinity: I didn't think the kernel looked at all these days?  we resume by hand in initramfs
[01:11] <Keybuk> or is it the actual going down bit?
[01:11] <infinity> (Likewise, hibernating to a swap file is just as doable, we just... Don't)
[01:11] <kees> I would do swap-on-MD to handle the easy suspend/hibernate case.
[01:11] <Robot101> I usually have boot on raid1, then the rest of space on LV on raidN, including swap, but then I don't hibernate such multi-disk servers
[01:11] <kees> Robot101: yeah, that's my case for all the desktop machines in my house
[01:12]  * kees needs to find a cheap laptop with 2 harddrives.  :)
[01:12] <Robot101> and by boot, I usually just take 10GB for / and anything like /var or /home that gets big goes onto the LV
[01:13] <Keybuk> Robot101: you have / rather than /boot ?
[01:13] <infinity> Keybuk: Oh, indeed, we do go looking ourselves these days.  So it's more a question of load order and such.
[01:13] <infinity> Keybuk: No reason we couldn't support resuming from crazy MD/LV setups, as well as from swapfiles read from a readonly root.
[01:13] <infinity> Keybuk: Just would take a bit of code and thought.
[01:13] <Keybuk> infinity: I'm not entirely sure it would require code anymore :p
[01:14] <Keybuk> it might just require a busy loop
[01:14] <Keybuk> or, better yet, a rethink of initramfs so that "mountroot" and "resume" aren't totally separate ways to go
[01:14] <infinity> Keybuk: At the very least, we need a way for resume= to be slightly smarter than just "a partition identifier".
[01:15] <infinity> (For the "suspend to swapfile" option, especially)
[01:15] <infinity> And swap files tend to be the more elegant solution for a lot of interesting use-cases.
[01:16] <infinity> (No one tell Microsoft I said that, though...)
[01:17] <Keybuk> agree
[01:17] <Keybuk> but then I'd say the same for root= ;)
[01:20] <infinity> Keybuk: Well, given the amount of crazy logic we can stuff in initramfs, I suppose there's no reason root= couldn't be a pointer to a file on $random_filesystem.
[01:20] <infinity> Keybuk: Not sure how often I'd use that feature, but if we write the code for resume-from-swapfile, we kinda get root-on-file for free.
[01:20] <infinity> (ish)
[01:20] <Keybuk> you should be able to say root= some magic string that defines a unionfs of two loop-mounted filesystems on a partition named by uuid
[01:20] <Keybuk> then we wouldn't need to special case things like the live cd and wubi
[01:21] <infinity> Voobee!
[01:21] <infinity> Is it wrong that the only thing I took home from that presentation was the pronounciation?
[01:24] <calc> so the platform meeting will be tomorrow at 5pm?
[01:24] <calc> er 2200 UTC
[01:25] <TheMuso> calc: If there is anything worth discussing. Your question is the first mention of it I've seen outside of what Colin said.
[01:25] <Keybuk> I hate d-i
[01:25] <Keybuk> "Failed to determine the codename for the release."
[01:25] <nxvl> Keybuk: why?
[01:25] <Keybuk> W. T. F.
[01:25] <nxvl> heh
[01:25] <nxvl> sometimes bugs happend
[01:25] <calc> TheMuso: ok
[01:27] <Keybuk> nxvl: this is the hardy release!
[01:27] <nxvl> on a hardy instalation you mean?
[01:27] <nxvl> i thought it was on intrepid tests
[01:27] <nxvl> :S
[01:29] <Keybuk> yeah hardy server i386
[01:32] <Keybuk> it's probably my error
[01:40] <Keybuk> in fact, I really can't see why
[01:41] <Keybuk> others have reported it
[01:41] <Keybuk> and cjwatson told them to follow the docs :-/
[01:41] <Keybuk> which is what I thought I'd done
[01:42] <Keybuk> evand: any ideas?
[01:49]  * Keybuk cheats
[01:49] <Keybuk> when in doubt, live edit the installer code to work around the issue
[02:04] <nxvl> popey: ping
[02:05] <Robot101> Keybuk: yeah I just take 10GB for /. once you split mail, home and service data out of /, the actual amount of space you need for the actual software on a server is very small
[02:06] <persia> (unless it's a game server)
[02:07] <Robot101> well, obviously anything you expect to be large you can allocate out of the LVs
[02:07] <Robot101> like make a spacious /srv or something
[02:07] <Keybuk> I just have / 1TB so I don't have to worry about it ;)
[02:14] <Robot101> Keybuk: well, this pattern is flexible for varying workloads - hosting VMs whose root FSes are LVs anyway
[02:15] <Robot101> Keybuk: and changing the RAID stuff around, adding more disks etc, growing with LVM is always easier
[02:15] <Robot101> Keybuk: also I like the way I can shuffle the disks, or take any one of them, and boot the system still
[02:39] <ogasawara> bryce: sorry for the delay, I've posted a comment to bug 213191
[02:39] <bryce> ogasawara: thanks
[03:26] <MachinTrucChose> Hi. Can someone tell me why using Install New Language to install french-language support in Kubuntu downloads the Thunderbird package? Why would a language pack require you to download a mail client?
[03:27] <wgrant> Erk, something went wrong in a dependency resolver somewhere.
[03:28] <wgrant> language-support-fr pulls in thunderbird-locale-fr, which shouldn't need thunderbird unless language-support-fr isn't installed, which it is about to be.
[03:29] <MachinTrucChose> well, it downloaded the full thunderbird-<IP_ADDRESS> etc, took forever too :)
[03:29] <MachinTrucChose> I guess the locale had the main program listed as a dependency?
[03:30] <wgrant> thunderbird-locale-fr has a 'thunderbird | language-support-fr' dependency.
[03:30] <calc> cody-somerville: ping
[03:30] <wgrant> So the fact that you're installing language-support-fr should satisfy it.
[03:30] <calc> cody-somerville: not sure if you saw my response about the xubuntu OOo bug
[03:30] <wgrant> But it apparently decides it needs thunderbird too.
[03:30] <cody-somerville> calc, link?
[03:30] <MachinTrucChose> I see, thanks for the info
[03:30] <calc> i forgot the bug number already
[03:31] <calc> you responded to it a few hours ago its the one about openoffice.org-gtk needing to be installed under xubuntu
[03:31] <cody-somerville> Yes
[03:31] <cody-somerville> That isn't a Xubuntu-meta bug
[03:31] <calc> i reassigned it to xubuntu-meta since xubuntu needs to seed that if it wants it
[03:31] <calc> its not something wrong with OOo
[03:31] <cody-somerville> That isn't the bug
[03:31] <calc> oh?
[03:31] <cody-somerville> He was installing from add/remove
[03:31] <cody-somerville> You should read the bug description not just the bug title ;]
[03:32]  * cody-somerville goes back to watching House. :)
[03:32] <calc> ah he manually installed OOo
[03:32] <calc> ok its not a bug at all then
[03:32] <calc> i just marked it invalid
[03:33] <cody-somerville> I wouldn't be so quick to dismiss it.
[03:33] <cody-somerville> You should really mark it as a bug of the add/remove app
[03:33] <cody-somerville> and mark it wishlist
[03:34] <calc> the add/remove app autoinstalls things you don't request it to, that aren't depends?
[03:35] <persia> It doesn't (although it will support Recommends: as well at some point)
[03:35] <calc> i was under the impression it was just a slightly prettier package manager that lists per applications folder
[03:35] <calc> so it would probably need some kind of ugly hack to support installing packages based on the flavor of *buntu
[03:35] <cody-somerville> calc, It wouln't be the flavour of ubuntu
[03:35] <cody-somerville> It would be based on the desktop environment
[03:36] <calc> true, it is just normally they are linked :)
[03:36] <persia> That's even harder to determine than the flavour.
[03:36] <cody-somerville> persia, Lets let the add/remove folks figure it out
[03:36] <cody-somerville> s/lot/worry
[03:36] <cody-somerville> erm
[03:36]  * calc thinks the user should just install what they want
[03:36] <cody-somerville> It isn't clear
[03:36] <persia> cody-somerville: Erm.  I've been looking at that code.
[03:37] <cody-somerville> The user shouldn't have to install open office writer and then some other package to make it look integrated.
[03:37] <persia> What's the bug number?
[03:41]  * calc already deleted the email :-\
[03:43] <cody-somerville> One second.
[03:45] <cody-somerville> https://bugs.edge.launchpad.net/ubuntu/+source/xubuntu-meta/+bug/236265
[03:45] <cody-somerville> calc, It is not a bug in xubuntu-meta and not a bug in "xubuntu in general"
[03:46] <persia> It's an issue with the data contained in app-install-data.  Where that data comes from is different.
[03:47] <persia> It's not a bug in xubuntu-meta, as it's not installed by default, so it oughtn't be seeded.
[03:47] <persia> It may be a bug in OO.o, but only in the syntax of some of the .desktop files.
[03:47]  * cody-somerville nods.
[03:47] <cody-somerville> persia, My thoughts exactly.
[03:47] <persia> Also, there likely ought to be a gtk-app-install, for xubuntu, as otherwise the gnome hints will apply.
[03:47] <cody-somerville> I filed it against app-install-data-ubuntu since calc keeps removing it from OpenOffice
[03:48] <persia> cody-somerville: I'm still looking, but I'm very much leaning towards the problem being a lack of a specialised app-install for Xubuntu, rather than an issue with OO.o.
[03:48] <persia> Anyway, without such an app, it's *really* hard for calc to fix it.
[03:49] <persia> Ah, no, it's not a bug in OO.o at all.
[03:49] <persia> The OO.o install hints are hardcoded in app-install-data, because there are so many ,desktop entries.
[03:49] <cody-somerville> ah.
[03:50] <persia> So, there are two bugs: the lack of a gtk-app-install, and a minor patch to menu-data-additional in app-install-data once there is such a program.
[03:50] <persia> Generating gtk-app-install ought be fairly easy, given gnome-app-install as an example.
[03:51] <persia> Once that's in place, opening a bug against app-install-data to provide the right hints ought be fine (or they can be overridden in gtk-app-install, depending on the complexity of each task)
[03:52] <persia> Bug 236265 is likely best set WontFix, unless Xubuntu plans to seek openoffice.org-gtk
[03:52] <persia> s/seek/seed/
[03:53] <persia> cody-somerville: Does that give you a roadmap, or do you need more information?
[03:54] <ion_> Plain rebuild was enough for vim to get linked to libperl5.10.
[04:02] <Hobbsee_> Afternoon all
[04:02] <ajmitch> greetings
[04:02] <ion_> Howdy
[04:02] <wgrant> Evening.
[04:02] <Hobbsee_> wgrant: no, it's not evening.
[04:02] <ion_> Yes, it is.
[04:02] <wgrant> It's close enough.
[04:04] <calc> sorry for bouncing the bug around so much, but i'm glad someone who knew how it works saw it :)
[04:04]  * calc hugs persia
[04:05] <ajmitch> wgrant: yet certain people in your timezone probably just woke up
[04:05] <Hobbsee_> sigh, chroot problems.
[04:06] <wgrant> ajmitch: Perhaps so.
[04:06] <persia> calc: Mind you, I'm not happy about the fact that OO.o assumes it will be seeded.  Around half our derivatives don't, and it can be confusing when optimising for Ubuntu :)
[04:57] <calc> persia: well the other option is to just force people to install everything, but then people complain it takes too much space, etc
[04:57] <calc> because if you ask enough people they want all the features in OOo
[04:58] <calc> but that is really large and definitely wouldn't fit on an install cd
[04:58] <persia> calc: For those people who want OOo, I agree.
[04:58] <persia> On the other hand, for mythbuntu or Ubuntu Studio, I'm less sure it makes sense.
[04:59] <calc> it shouldn't be getting installed on ubuntu studio at all, there is a bug in the lang packs stuff though
[04:59] <persia> I think it's a hard problem, and that it will take a while to find something that works.
[04:59] <calc> but for users that want to install it on ubuntu studio they would currently have to know what to install for what they want of it
[04:59] <persia> calc: Right, which is the hard problem.  app-install-data only provides a single hint, as OOo doesn't expose one cleanly.
[05:00] <calc> eg you could install openoffice.org metapackage and it would recommend (depends on the package manager) ooo-kde and ooo-gnome, etc
[05:00] <persia> As a result, it's tricky to later install OOo-kde or OOo-gtk, rather than OOo-gnome.
[05:00] <calc> is there a way to expose a hint without forcing it to be installed eg a depends?
[05:00] <persia> That gets into the parts of Add/Remove I don't know so well :)
[05:00] <calc> if so i can modify OOo packaging to give hints, if there is a clear way to do this
[05:00] <calc> ok
[05:00] <persia> It has to do with special tags in the .desktop files.
[05:01] <calc> well to use gtk/gnome/kde integration wouldn't be specific to a desktop file at least aiui
[05:01] <persia> You might ask mvo later, if you have time.  On the other hand, right now it only really affects Xubuntu, and a hack in gtk-app-install might be good enough.
[05:01] <calc> ok
[05:02] <persia> calc: Well, it's the .desktop file for the app installer vs. the .desktop file for the application itself.  In many cases, these are the same.  It may not be possible to have these be the same for OOo.
[05:03] <calc> oh ok
[05:06] <persia> calc: If you want to dig, compare /usr/share/app-install/desktop/ooo-meta.desktop as an example of such a hint
[06:25] <pitti> Good morning
[06:27] <ajmitch> hi pitti
[06:43] <pitti> Keybuk: oh, no Vcs-Bzr: for upstart? you do keep it in bzr, I take it? I'd like to fix the Pre-Depends: for sysvutils -> sysvinit-utils; or do you want to do that yourself?
[07:14] <dholbach> good morning
[07:25] <\sh> hey dholbach
[07:28] <dholbach> hi \sh
[08:11] <\sh> hmmm.wtf? temp removal of sysvutils during dist-upgrade...which breaks the upgrade path...was it a wish? :)
[08:21] <pitti> \sh: I think we need to fix upstart's Pre-Depends: on sysvutils; see my ping to Keybuk earlier on
[08:21] <\sh> pitti, no backlog...but if it's known everything is fine :)
[08:57] <Hobbsee> Keybuk: ping?  :)
[08:57] <Hobbsee> Keybuk: wait. you're techboard.  unping.
[08:59] <Hobbsee> ah, darn, and htere was no CC quorum.
[10:12] <PecisDarbs> hi people, could it be that AppArmor on 8.04 forbids to write to /sys with sudo command?
[10:12] <pitti> PecisDarbs: not by default
[10:12] <arthur-> munckfish: I'll be fine thanks. I don't know yet, I haven't contributed to Ubuntu for a while now
[10:12] <PecisDarbs> damn then
[10:12] <pitti> PecisDarbs: look at the output of 'dmesg' to see the AppArmor erros
[10:12] <PecisDarbs> ok
[10:15] <munckfish> arthur-: hi, glad to hear it, so you're primarily a debian guy?
[10:16] <arthur-> munckfish: definitely yes
[10:18] <munckfish> arthur-: ok cool. Well I'm happy to be responsible for these sorts of packages in Ubuntu it would be good if we could work together to make sure there's no wasted effort between the two projects
[10:19] <arthur-> munckfish: sure, do you like git ?
[10:21] <munckfish> arthur-: I love git. But I'm still at Git kindergarten really :D
[10:26] <arthur-> munckfish: cool, we'll talk about all that later ;-)
[10:30] <munckfish> arthur-: ok grab me whenever
[10:39] <mohbana> hi
[10:40] <pitti> tseliot: do you know what DEST_MODULE_LOCATION in dkms.conf is for? it seems to be ignored, and all .kos actually land in /lib/modules/`uname -r`/updates/dkms/ ?
[10:41] <mohbana> hi i've got a question about fonts in unbutu
[10:45] <tseliot> pitti: let me quote the man page "Currently,  DKMS  searches
[10:45] <tseliot>        for  these  original  modules  with  first  preference going to modules
[10:45] <tseliot>        located in /lib/modules/<kernelversion>/updates/ followed by $DEST_MOD‐
[10:45] <tseliot>        ULE_LOCATION  (as  specified in dkms.conf ).  If one cannot be found in
[10:45] <tseliot>        either location, a find will be used to locate one for that kernel.  If
[10:45] <tseliot>        none  are  found,  then  during a later uninstall, your kernel will not
[10:45] <tseliot>        have that module replaced."
[10:46] <tseliot>  If more than one is found, then the first one  located  (by  preference
[10:46] <tseliot>        indicated  above)  will  be considered the "original_module".
[10:48] <tseliot> pitti: the one in updates is what will be loaded
[10:49] <mohbana> anyone here/
[10:49] <pitti> tseliot: ah, so it is not actually the path for the kmod to be installed, but the older kmod to be *replaced*
[10:50] <tseliot> pitti: yes, exactly. In this way DKMS knows where's the original
[10:50] <tseliot> and can make a backup
[10:50] <pitti> tseliot: aah; that might explain something; thanks!
[10:51] <tseliot> pitt: I know that the fact that it's called "DEST" might suggest that it refers to the destination of the new module ;)
[10:52] <pitti> right, that's what confused me; the man page section about this parameter isn't very helpful
[10:52] <tseliot> pitti: I'll be your human man page :-P
[10:52]  * pitti updates his dkms.conf autogeneration script for that
[10:53] <mohbana> what exactly does ubuntu do to it's fonts  to make them look so good?
[10:55] <mohbana> i am getting totally ignored
[10:57] <mvo> pitti: have you seen #237276 ? I haven't investigated yet what the problem is exactly, I'm curious if you have seen it before?
[10:58] <pitti> mvo: I can only guess that it is due to upstart's Pre-Depends:
[10:59] <pitti> mvo: I pinged Keybuk about it (need to coordinate with him for bzr0
[11:00] <PecisDarbs> hi people, where I can find patches for Ubuntu kernel? in debian directory of source?
[11:00] <pitti> PecisDarbs: http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-hardy.git;a=summary
[11:05] <mvo> pitti: ok, I milestoned it for alpha-1
[11:05] <pitti> mvo: assigned to me, thanks
[11:05] <mohbana> i take it David Turner himself is maintaining freetype on the ubuntu repos?
[11:05] <mohbana> :)
[11:05]  * mvo hugs pitti
[11:12] <Ademan> hey would i be ill-advised to use xorgconfig.py ?
[11:14] <Ademan> /usr/share/python-support/guidance-backends/xorgconfig.py   to be specific
[11:15] <tseliot> Ademan: it's Guidance. What are you trying to do with it?
[11:15] <Ademan> tseliot: not have to write my own code to parse xorg.conf
[11:15] <Ademan> what do you mean it's guidance? i see it being used by displayconfig-gtk
[11:16] <Riddell> seb128: how many gnome point releases are usually done?
[11:16] <tseliot> Ademan: that file is part of Guidance i.e. a backend. I don't think it's maintained any longer.
[11:17] <Riddell> Ademan: displayconfig-gtk is a gtk frontend to kde-guidance's displayconfig
[11:17] <pitti> Ademan: it's shipped in guidance-backends, and used by other packages as well
[11:17] <pitti> Ademan: it works, but the API is not very convenient nor robust
[11:18] <Riddell> Ademan: these days you should probably be using xrandr rather than reading xorg.conf
[11:18] <Ademan> pitti: hrm, well, considering i'd rather not get friendly with flex and bison right now... i think i'll use it
[11:18] <Ademan> Riddell: not for display actually, for input
[11:18] <pitti> Ademan: oh, yeah, it's miles ahead of writing your own :)
[11:18] <Ademan> gonna see if i can't cook up something convenient for lots-o-button-mice
[11:31] <seb128> Riddell: you mean during the unstable cycle? or stable updates?
[11:32] <Ademan> well thanks guys, later
[11:36] <Riddell> seb128: stable
[11:38] <seb128> Riddell: 3
[11:38] <seb128> until .3 rather
[11:38] <Riddell> seb128: right, and those are monthly?
[11:39]  * pitti fixes SpecTemplate to have a standard header again (UbuntuSpec:, contributors, affected packages, etc.)
[11:40] <seb128> that's not a fixed monthly schedule but roughly yet
[11:40] <seb128> yes
[11:40] <seb128> 2.22.1 to 2.22.2 was 6 weeks
[11:41] <Riddell> mm, interesting, thanks seb128
[11:41] <seb128> they avoid having new stable and unstable in the same weeks so there is some flexibility
[11:41] <seb128> you are welcome
[12:35] <Keybuk> pitti: fix to what?
[12:46] <pitti> Keybuk: sysvutils to sysvinit-utils
[12:51] <Keybuk> pitti: did you get any explanation from Debian why they renamed the package?
[12:51] <pitti> Keybuk: they didn't rename it within Debian; it has always been called like this in D
[12:51]  * pitti goes to reproduce the bug in vmware, and test fixes
[12:52] <Keybuk> pitti: they renamed it when they took the patch to separate it from us though
[12:52] <Keybuk> we split it out first
[12:52] <pitti> right
[12:53] <Keybuk> I never understood why they didn't use our name?
[12:53] <pitti> neither have I
[12:53] <pitti> just cosmetical reasons, I guess
[12:53] <Keybuk> "Not Named Here" :)
[12:54] <bullgard4> "detlef@MD97600:~/gnome$ apt-get source apport" obtains 191kB but complains: "gpg: Signatur am Sa 17 Mai 2008 14:07:51 CEST mit DSA Schlüssel, ID 5E0577F2, erfolgt; gpg: Unterschrift kann nicht geprüft werden: Öffentlicher Schlüssel nicht gefunden." How can I make gpg to find the public key?
[12:54] <pitti> ugh, apt-get source verifies signatures?
[12:54] <Keybuk> pitti: what's the right way to do a XS-VCS-Bzr ?
[12:55] <pitti> Keybuk: Vcs-Bzr: https://code.launchpad.net/~ubuntu-core-dev/upstart/ubuntu
[12:55] <pitti> or so
[12:55] <pitti> Keybuk: no XS- any more
[12:55] <pitti> Keybuk: http://bazaar. works as well (that's the code browser)
[12:55] <pitti> bzr get works with either
[12:57] <Keybuk> hmm
[12:57] <Keybuk> weirdly, the header is in bzr
[12:57] <Keybuk> but doesn't show up in the source package
[12:58] <pitti> Keybuk: I don't see it in the apt-get source'd upstart
[12:59] <Keybuk> no, that's what I mean
[13:00] <Keybuk> pitti: bug# for the sysvutils issue?
[13:00] <pitti> Keybuk: bug 237276
[13:01] <pitti> Keybuk: my vmware is still upgrading (ugh, 130 MB to download)
[13:03] <Keybuk> ok, done
[13:04] <pitti> Keybuk: cheers
[13:05] <Keybuk> hopefully the bzr header should show up now
[13:05] <Keybuk> OOI, how do you manage it?
[13:05] <Keybuk> do you apt-get source the package, then checkout the debian directory wiping what's there?
[13:05] <pitti> Keybuk: just debuild -S it and check the .dsc
[13:06] <siretart> FYI, bzr-builddeb 0.95 is able to do this: `bzr bd -S https://code.launchpad.net/~ubuntu-core-dev/upstart/ubuntu`
[13:06] <Keybuk> no, I mean, how do you handle debian-in-bzr ?
[13:06] <pitti> Keybuk: usually debcheckout -a, and then unpack the orig.tar.gz, yes
[13:06] <Keybuk> ah, and you put debian one-level-down ?
[13:07] <pitti> learning bzr-builddeb is a long-standing TODO item of mine...
[13:07] <siretart> Keybuk: just add the --merge option. done.
[13:07] <pitti> Keybuk: right, I have .bzr/ in the top level dir
[13:07] <Keybuk> my current recipe is:
[13:07] <Keybuk>   apt-get source upstart
[13:07] <Keybuk>   cd upstart-0.3.9
[13:07] <pitti> Keybuk: erm, s/right,/no/
[13:07] <Keybuk>   bzr checkout ~/co/upstart/debian
[13:07] <pitti> (common practice on alioth)
[13:08] <Keybuk> (for no readily apparent reason, if you checkout, it puts the .bzr into an existing working copy :p)
[13:09] <Keybuk> I'd rather just put the whole source in, but bzr doesn't like that much
[13:10] <siretart> in what way?
[13:10] <Keybuk> siretart: it thinks it doesn't have to care about timestamps
[13:10] <Keybuk> first time I tried it, it upset automake
[13:10] <siretart> interesting
[13:11] <Keybuk> I've proposed that bzr applies the same timestamp to all files modified by any operation
[13:11] <Keybuk> ie. after checkout, the entire tree would have the same timestamp
[13:11] <Keybuk> and after an update, only the changed files would have a new timestamp (and the same as each other)
[13:14] <Keybuk> ?!
[13:14] <Keybuk> now dpkg-buildpackage is randomly exiting on me
[13:44] <Keybuk> tkamppeter_: interesting, on a completely fresh Hardy install, I just ran hp-setup and my printer appears to work
[13:44] <Keybuk> it must be something left behind by it working on gutsy and before that's breaking it on hardy?
[13:45] <sistpoty|work> bryce: can you also make x11-common available in your people dir? (iirc dexconf is in there, at least not in the both .debs that are in your dir)
[13:46] <sistpoty|work> bryce: oh, and maybe you shouldn't publish the signed .changes file right next to the source package (that way everyone can upload that to ubuntu proper)
[13:54] <Keybuk> tkamppeter_: hah! it works right up to the point I try and print from another machine
[13:58] <siretart> sistpoty|work: ha, just upload it! :-)
[13:59] <sistpoty|work> tststs ;)
[14:32]  * Keybuk considers adding -Werror to package flags
[14:32] <Keybuk> it'd be kinda nice to not even allow the buildds to accept warnings
[14:34] <soren> For sufficiently mind-numbing interpretations of "nice", yes.
[14:34] <persia> This ought be selectable, as the number of new FTBFS cases in universe may be large
[14:35]  * soren thinks "large" is an understatement
[14:36] <soren> Keybuk: You wouldn't happen to have any idea about the scale of the percentage of packages that would ftbfs with -Werror, would you?
[14:36] <seb128> soren: too many
[14:37] <soren> I'm guessing  at least 90%.
[14:37] <seb128> not that bad
[14:37] <persia> Well, maybe 80%.  Lots of code isn't actually C.
[14:37] <soren> No?
[14:37] <seb128> rather 10% I would say
[14:37] <soren> Because they don't actually have warning, or because they'd override -Werror?
[14:37] <seb128> but maybe I'm biaised and GNOME is much better than the rest of the world ;-)
[14:37] <persia> That's still 1500 packages that need fixing: about the total size of maintained universe.
[14:38]  * ogra is on the 10% side
[14:38] <Keybuk> soren: I was just thinking of doing it for one package
[14:38] <seb128> soren: because they don't have warnings, I think many GNOME component have -Werror set when building from svn, they just turn it off for tarballs
[14:39] <soren> Keybuk: Oh. :)
[14:39] <persia> One package is a good idea :)
[14:39] <persia> (Maybe even 10 or so)
[14:40] <soren> seb128: I just picked two completely random gnome packages. Both have warnings (gnome-panel and libgnomeui).
[14:41] <seb128> soren: weird, the libgnomeui build on my disk has no warning
[14:41] <soren> http://launchpadlibrarian.net/13285398/buildlog_ubuntu-hardy-i386.libgnomeui_<IP_ADDRESS>-0ubuntu1_FULLYBUILT.txt.gz
[14:42] <soren> Not a lot, though.
[14:42] <seb128> weird
[15:03] <pitti> calc: hm, no SRU bug in the OO.o changelog
[15:03] <pitti> calc: where is it tracked?
[15:03] <Hobbsee> on very small fragments of post-it notes
[15:04] <Hobbsee> hence the lack of numbers
[15:06] <pitti> Keybuk: hm, seems amd64 didn't like your PIC changes in upstart
[15:07] <Keybuk> pitti: indeed
[15:07] <Keybuk> I saw that
[15:07] <Keybuk> I'll let kees cry about that when he wakes up ;)
[15:07] <Keybuk> since it works fine on my amd64 here
[15:16] <\sh> asac, bug #131793 -> why invalid when there is no real solution for gutsy users? :)
[15:19] <norsetto> is it just me or there is somethign wrong with libglib2.0-data?
[15:21] <asac> \sh: i did a batch closing a bunch of crashers that had no dupes and appeared to not be reproducible anymore
[15:21] <asac> \sh: you can reopen it if oyu provide a backtrace
[15:21] <asac> is it just gutsy?
[15:21] <\sh> asac, hardies ff3 crashing too...
[15:21] <\sh> just tested
[15:22] <asac> => update bug ... attach backtrace, reopen, confirm :)
[15:23] <\sh> asac, you want apport stuff or just plain gdb bt full?
[15:24] <ogra> its probably because spiegel wants you to buy the paper version :)
[15:24] <\sh> ogra, lol
[15:24] <ogra> secret intrigue between ff and spiegel ;)
[15:26] <asac> \sh: the comment suggests that the apport retrace was invalid. so getting a backtrace locally with dbgsym installed should work
[15:26] <seb128> norsetto: it's just you?
[15:26] <\sh> asac, just trying to make it crash again running in gdb
[15:26] <seb128> norsetto: but let say that your comment is not really descriptive about your issue
[15:26] <pitti> soren: hm; if I accept the new u-vm-builder now, that'll reset the 7 days testing period of the current -proposed one
[15:26] <pitti> soren: any chance you could collect some test results on the current one, so that it can move to -updates first?
[15:26] <soren> pitti: That's ok.
[15:27] <pitti> soren: otherwise testing will get messy
[15:27] <soren> No.
[15:27] <norsetto> seb128: dunno, in intrepid something seems to be dragging in 2.16.3-2 which doesn't exists
[15:27] <soren> I don't want the one in -proposed to land in -updates.
[15:27] <soren> I deliberatly didn't wait.
[15:27] <seb128> norsetto: --verbose?
[15:27] <norsetto> seb128: thats as much as I can say now
[15:27] <soren> pitti: It causes a quite severe regression.
[15:28] <pitti> soren: ok; any chance you could reupload with using -v then, to cover the previous changelog in the source.changes, too?
[15:28] <asac> \sh: remember to install dbgsym for cairo and gtk and such things too
[15:28] <pitti> soren: ok, understood
[15:28] <soren> pitti: Oh, so it has the entries from 0.2 and 0.3? Sure, that makes sense.
[15:28] <\sh> asac, you have a list? ,)
[15:28] <pitti> soren: thanks
[15:29] <seb128> norsetto: seems that the binary went to universe for some reason
[15:29] <soren> pitti: What about 0.1? It was a -security upload, so I'm not sure how to treat that.
[15:29] <pitti> soren: that's fine; just the previous -propsoed upload and your new one
[15:29] <pitti> i. e. -v...0.1
[15:29] <asac> \sh: good start is https://wiki.ubuntu.com/MozillaTeam/Bugs under crashes
[15:29] <soren> pitti: Great. Gimme a few minutes.
[15:29] <seb128> norsetto: oh, it's simply to universe, that's not new, but now recommends are installed and libglib2.0-0 recommends it
[15:29] <\sh> asac, well...if I really have 5 lines with something like #1  0xb72931f2 in ?? () from /usr/lib/xulrunner-1.9b5/libxul.so and one libc line..
[15:29] <seb128> norsetto: where does it create an issue?
[15:30] <\sh> for the bt full ...
[15:30] <norsetto> seb128: yes, but why 2.16.3-2?
[15:30] <asac> \sh: maybe gdb doesnt find the xulrunner dbgsymbols?
[15:30] <asac> maybe LD_LIBRARY_PATH tweak helps?
[15:30] <seb128> norsetto: what do you do to get this version mentionned?
[15:30] <\sh> asac, yes...because I need to install them...but I don't want to install the other crap...do you agree, that it could be xulrunner directly?
[15:31] <asac> \sh: hard to say
[15:31] <\sh> asac, ok...working the way down...:)
[15:31] <asac> if here are other libs in the trace try them too
[15:31] <asac> cool
[15:32] <\sh> asac, libc and xulrunner only...
[15:33] <Keybuk> pitti: so I was thinking
[15:33] <Keybuk> how do we make it so you can plug USB storage devices into a server?
[15:34] <norsetto> seb128: I'm just building a package in a pbuilder chroot, if I login and do "apt-get install libglib2.0-0" it also tryes to install that version
[15:34]  * ogra hears pmount scratch on its coffin
[15:34] <seb128> norsetto: what architecture?
[15:34] <norsetto> seb128: amd64
[15:35] <seb128> norsetto: apt-cache policy libglib2.0-0?
[15:35] <pitti> Keybuk: you mean with automount?
[15:35] <norsetto> seb128: Candidate: 2.16.3-2
[15:35] <seb128> norsetto: your mirrror seems to be broken
[15:35] <pitti> ogra: rather something that looks like gnome-mount -vbt
[15:36] <seb128> norsetto: current is 2.17.0-1
[15:36] <norsetto> seb128: well, its archive.ubuntu.com
[15:36] <seb128> norsetto: you ran apt-get update?
[15:37] <norsetto> seb128: yes, since about 3 hours
[15:37] <\sh> norsetto, there are at least three servers behind a.u.c. could be that one is not updated properly yet
[15:37] <norsetto> \sh: since 3 hours? Then there is something wrong with one of the 3
[15:37] <\sh> norsetto, nslookup archive.ubuntu.com and check them manually
[15:38] <\sh> norsetto, yes..we had that when hardy was released...could be that it comes back ;)
[15:38] <norsetto> \sh: seems to be <IP_ADDRESS>
[15:38] <seb128> norsetto: using archive.ubuntu.com the current version on amd64 intrepid is 2.17.0-1 on my installation
[15:39] <norsetto> seb128: which of the 3 are you pointed too?
[15:39] <seb128> norsetto: dunno
[15:40] <Keybuk> pitti: well, with New World Order stuff
[15:40] <Keybuk> I can plug it in on a desktop, and it gets mounted
[15:40] <Keybuk> but same doesn't apply when I plug it in on a server
[15:40] <pitti> Keybuk: right; no ConsoleKit schema on servers, etc.
[15:40] <Keybuk> nor user policy agent to actually do the mounting?
[15:41] <pitti> I'm not sure about how automounting semantics should be on a server TBH
[15:41] <pitti> or whether it's generally desired on a server in the first place
[15:41] <Keybuk> me neither
[15:41] <Keybuk> it's desired in some cases
[15:41] <Keybuk> e.g. media server
[15:41] <pitti> should it be read/writable for everyone? just for root?
[15:41] <soren> Keybuk: In that case the "media" part of it should manage it. Like mythtv or whatever.
[15:42] <Keybuk> soren: but there's no common component for them to depend on
[15:42] <Keybuk> the "media" bit shouldn't NIH the same bit as "desktop" or "storage", etc.
[15:42] <soren> Didn't hal grow these capabilites at some point?
[15:42] <Keybuk> my case is that I have a nice squat file server which has some USB ports on the front
[15:42] <\sh> asac, bug updated :) with the infos
[15:43] <Keybuk> it'd be quite froody if I could plug a USB key, and have that automatically shared ;)
[15:43] <ogra> soren, needs a mounter binary
[15:43] <Keybuk> soren: I'm not sure I recall how it's split between HAL, gnome-mount, Nautilus and gnome-volume-manager
[15:43] <ogra> soren, in case of the desktop its gnome-mount ... for server you need something else which doesnt exist
[15:44] <pitti> soren: hal can do the mounting, etc, and knows when devices appear
[15:44] <soren> Hm... I guess that for "real" filesystems (ones with uid's and stuff) they could just get mounted. There's no ownership settings to worry about since they're specified by the file system.
[15:44] <pitti> soren: but you need something to "connect" the "new device" and "plz mount it for me with those options"
[15:44] <pitti> soren: unix fses> right
[15:45] <Keybuk> really? see I'd say unix fses are the bad ones because you can't squash the permissions
[15:46] <Mithrandir> soren: though, that requires you to have the same UIDs around the place.
[15:46] <soren> Mithrandir: Sure.
[15:46] <soren> Mithrandir: The point is that there's nothing you can (currently) do about that anyway. You either mount it or don't.
[15:46] <soren> There's no need to decide who gets to own it, what the permissions should be, etc.
[15:47] <norsetto> seb128: ok, got the problem, pbuilder update is failing because of sysvutils
[15:47] <soren> I think I still have a patch somewhere against linux 2.4 that actually adds some kind of squashing capabilities here.
[15:47] <Mithrandir> Keybuk: squashing is easy-peasy, just use fuse to mount it.
[15:47] <pitti> Keybuk: which is pretty much what I want if I use my home server which just has an USB hard disk :)
[15:47] <seb128> norsetto: ah, that explains
[15:48] <Mithrandir> soren: sounds easy enough to do.
[15:48] <soren> You could provide a mappings file to mount that would translate UID's and GID's in the vfs layer.
[15:48] <pitti> soren: however, what to do with vfat, ntfs, udf?
[15:48] <asac> \sh: can you ttest the -proposed package too please?
[15:48] <asac> e.g. 3.0rc1 (you have 3.0b5)
[15:49] <asac> (sorry thought you were running proposed)
[15:49] <\sh> na...I don't run proposed....:)
[15:49] <soren> pitti: I don't think ubuntu server should do anything by default with those.
[15:49] <norsetto> pitti: was the sysvutils problem solved? Apparently pbuilder update still fails because of it
[15:50] <soren> I understand the media server use case, though.
[15:50] <asac> \sh: for me it doesnt crash here on RC1
[15:50] <pitti> norsetto: updated upstart was just uploaded about two hours ago, but still FTBFSed on amd64; it might be solved nowish for i386
[15:50] <asac> so maybe its fixed
[15:50] <asac> either test or lets wait till you get that to confirm
[15:50] <norsetto> pitti: ahh ok!
[15:50] <asac> before reporting upstream
[15:50] <\sh> asac, preparing for -proposed :)
[15:50] <asac> great
[15:52] <soren> brb
[15:55] <\sh> asac, right..it doesn't crash anymore with proposed version
[15:56] <asac> cool
[15:56] <\sh> asac, do you actually have an updated gutsy version available to test?
[15:57] <asac> \sh: updated ? you mean in -backports? prod jdong about that. he usually did the backports
[15:57] <asac> havent heard from him for this update yet.
[15:57] <\sh> asac, na...ff2 :)
[15:58] <asac> you mean <IP_ADDRESS>pre?
[15:58] <\sh> dunno what's latest in gutsy...but I can ask the guy who can test it ;)
[15:59] <asac> \sh: ask him. we update on each and every upstream security release
[15:59] <asac> current version should be <IP_ADDRESS> if i am not mistaken
[15:59] <asac> thanks
[15:59] <tkamppeter> Keybuk, what is your printer problem? I have seen something which you told about your printer.
[16:00] <asac> \sh: ok added firefox-3.0 target as fixcommitted and kept firefox target at confirmed for now. usually i would put it back to incomplete when asking to test latest :)
[16:01] <asac> doing that now ;)
[16:01] <\sh> asac, well, people don't use -proposed in production environments ;) they are not as crazy as I am ;)
[16:01] <asac> \sh: yeah. thats why its fixcommitted not released
[16:02] <\sh> asac, I wonder if someone fixed it in rc1 if there is somewhere a upstream bug report...
[16:04] <asac> \sh: most likely
[16:04] <asac> we have hundreds of crashers. maybe there are even dupes in LP that have the right upstream bug
[16:05] <Keybuk> tkamppeter: HP LJ 1018 barely working
[16:05] <\sh> just found an old one from 2004 in bugz*.mz.o ;)
[16:05] <Keybuk> nine times out of ten, it just doesn't print
[16:05] <Keybuk> with the error that the printer isn't connectde
[16:05] <asac> \sh: launchpad search for "crash print" that are either open or fixed upstream yielded bug 217032
[16:06] <asac> \sh: that one is fixed upstream, so maybe a good dupe for this ;)
[16:06] <\sh> asac, na still open ;)
[16:06] <\sh> and marked as crit ;)
[16:06] <asac> \sh: he?
[16:06] <asac> its fixed upstream
[16:07] <asac> mozilla bug 429071
[16:07] <calc> pitti: writing the bug report now, i had forgotten to do it when i got back from vacation
[16:07] <soren> pitti: Ok, in the media server case... What would be the minimal e.g. mythtv would have to do to make it so that USB storage is automagically mounted and owned by it?
[16:08] <calc> pitti: i think i have it targeted properly
[16:08] <pitti> calc: could you upload a new diff.gz/dsc with the bugs referenced?
[16:08] <pitti> calc: thanks
[16:08] <asac> \sh: mozilla bug 429678 is similar. but both appear to be fixed in cairo. not sure if that is our bug
[16:08] <tkamppeter> Keybuk, you are aware of the needed firmware?
[16:08] <Keybuk> tkamppeter: yes
[16:08] <pitti> soren: issue the dbus call to hal
[16:08] <Keybuk> this time round, I've just run "hp-setup" to set it up, and that downloaded things
[16:08] <calc> pitti: its a "Update OpenOffice.org to 2.4.1" bug
[16:08] <tkamppeter> Setting it up with hp-setup loads the firmware from the internet
[16:09] <calc> pitti: we are at rc1 already in proposed
[16:09] <pitti> calc: oh, I see; it doesn't actually address existing ones in LP?
[16:09] <pitti> calc: ok; we just need to have a bug to track it then
[16:09] <soren> pitti: In that case, it doesn't seem at all unreasonable to require the media server solution to handle this, does it?
[16:09] <calc> pitti: it probably does, but i would have to verify which bugs it fixes, not sure if LP has bugs for all of the bugs it fixes though
[16:09] <calc> pitti: i made a master bug that i will be documenting what all it fixes and reference the bugs it fixes that are already in LP from it
[16:10] <pitti> soren: I'm not entirely sure; what happens if two processes want to mount it?
[16:10] <tkamppeter> Setting it up with s-c-p does not install the firmware, but should work if something else has set up the firmware before.
[16:10] <soren> pitti: You tell me :)
[16:10] <\sh> asac, hmmm...we use selfmade cairo right? so I didn't updated cairo
[16:10] <calc> pitti: when i uploaded the first couple to proposed i was behind on bugmail so some of the bugs it fixes have already been fixed in older (2.4.1) uploads that weren't referenced in the changelog at the time
[16:10] <pitti> soren: well, they would race against each other
[16:11] <Keybuk> tkamppeter: the problem is that it gets detected fine, seems to work
[16:11] <Keybuk> probably even get a test page or two out of it
[16:11] <tkamppeter> Keybuk, when you turn the printer on you see whether it loads the firmware or not, by the blinking orange lights.
[16:11] <Keybuk> then why you try and print something useful, like a web page, nothing happens
[16:11] <\sh> asac, for hardy I just installed the firefox-3.0 packages + xulrunner-1.9 update...
[16:11] <Keybuk> tkamppeter: solid green light
[16:11] <soren> pitti: I guess this is something the hal people must have thought about?
[16:11] <asac> \sh: ok makes sense. the trace doesnt look cairo related anyway
[16:12] <tkamppeter> Keybuk, yes after the turn-on procedure it goes to solid green light.
[16:12] <pitti> soren: well, it's not a technical problem really
[16:12] <Keybuk> tkamppeter: so the firmware bit must be working ok
[16:12] <\sh> asac, https://bugzilla.mozilla.org/show_bug.cgi?id=263229 <- reported 2004 , last mod: 2007 ;)
[16:14] <soren> pitti: Depends on how you look at it. HAL could have had a locking mechanism of some kind that would offer the mount point to a list of subscribers in a specific order.
[16:14] <pitti> Keybuk: can you please propose https://blueprints.edge.launchpad.net/ubuntu/+spec/consolidate-spell-checkers and maybe update the people? I can't propose that one as a goal (I wonder why)
[16:14] <tkamppeter> Keybuk, for your printer are two drivers available, foo2zjs and hpijs, the latter only if you have set up the printer with hp-setup once (due to a closed-source plug-in, downloaded together with the firmware).
[16:14] <tkamppeter> Keybuk, have you tried both drivers?
[16:14] <pitti> soren: on the desktop this is solved by having a central mount agent and only allowing mounts to the foreground console
[16:14] <Keybuk> pitti: you should be able to propose now
[16:15] <pitti> but that concept doesn't work well for servers
[16:15] <Keybuk> tkamppeter: I did try both yeah
[16:15] <Keybuk> same problem
[16:15] <pitti> Keybuk: right, works now; thanks
[16:15] <soren> pitti: What if a another mount-agent came along?
[16:15] <Keybuk> it feels like whatever makes the job gets it wrong somehow, in a way that the printer doesn't accept
[16:15] <soren> pitti: Or could there be only one?
[16:15] <Keybuk> if I fiddle with random things like shrinking the print by 50%, it works
[16:15] <pitti> soren: in principle there can be several, but it wouldn't make sense to have more than one
[16:16] <\sh> oh wow...who said that 16M memory for php5 is enough ? :)
[16:16] <Keybuk> printing two pages to a side also seems to usually work
[16:16] <tkamppeter> Keybuk, can it be that the USB is perhaps not stable?
[16:16] <Keybuk> tkamppeter: "the USB" ?
[16:16] <tkamppeter> Keybuk, I mean that perhaps something needs to be done on the kernel?
[16:17] <Keybuk> tkamppeter: don't both things just use libusb?
[16:17] <tkamppeter> Keybuk, even with libusb it goes through the kernel AFAIK
[16:17] <pitti> seb128: please let me know if you disagree with https://blueprints.edge.launchpad.net/ubuntu/+spec/consolidate-spell-checkers (just assigned to you, since it boils down to sponsoring changes in GNOME packages)
[16:17] <pitti> seb128: I can do it as well if you prefer
[16:17] <Keybuk> tkamppeter: only barely
[16:18] <asac> \sh: is the testcase fixed in that bug? :)
[16:18] <Keybuk> if things were wrong enough that they broke libusb, most USB things wouldn't work
[16:18] <soren> pitti: Right, ok.
[16:18] <seb128> pitti: works for me
[16:18] <Keybuk> since libusb is basically a pass-through out of the port
[16:19] <tkamppeter> Keybuk, you can also try two CUPS backends, the "hp" one of HPLIP, which is based on libusb and the "usb" backend from CUPS which is based on the "usblp" kernel module.
[16:19] <ogra> Keybuk, you have a LJ 1018 ?
[16:19] <ogra> i have te same around, working just fine
[16:20] <ogra> *the
[16:20] <Keybuk> tkamppeter: the USB one with foo2zjs was basically working
[16:20] <tkamppeter> ogra, you have one, too? How well does it work for you?
[16:20] <\sh> asac, you mean this mozlogo on the page? when I click on attachment? well, print preview and print do work in rc1 but gives me two pages in the end ;)
[16:20] <Keybuk> ogra: on hardy, set up automatically or by hp-setup ?
[16:20] <ogra> tkamppeter, i only prited about five times with it but it worked flawless out of the box
[16:20] <Keybuk> tkamppeter: I have a vague recollection I had to downgrade foo2zjs to gutsy's version
[16:20] <ogra> it installed itself after plugging in
[16:20] <\sh> zul, slangasek : can we discuss to inc the mem limit in php.ini for php5-apache2 module from 16 to something like 16*2?
[16:21] <ogra> i havent changed anything manually
[16:21] <ogra> Keybuk, auto ...
[16:21] <pitti> mvo: if the two-dimensional package groups turn out not to work, do you see any chance to have something like an apt hook for marking additional packages for installation, based on the currently installed and available ones?
[16:22] <tkamppeter> Keybuk, if you have to downgrade foo2zjs to the Gutsy version, it smells like a bug in foo2zjs.
[16:22] <Keybuk> ogra: mine usually prints the first page or two after being turned on, then stops
[16:23] <ogra> hmm, i havent printed books yet but the two three page prints i did this year all worked
[16:23] <Keybuk> tkamppeter: that downgrade doesn't help with the hpijs method though
[16:23] <Keybuk> tkamppeter: that simply doesn't work for me ;-/
[16:23] <Keybuk> the only other piece of interestingness is that this is on amd64
[16:23] <Keybuk> I might just try this on my i386 hardy box and see if it works
[16:25] <Keybuk> ogra: are you on i386 or amd64?
[16:25] <ogra> i386
[16:25] <ogra> (my laptop)
[16:26] <Keybuk> interesting
[16:26] <Keybuk> because on my laptop, this is still working on i386
[16:27] <ogra> hmm
[16:27] <Keybuk> tkamppeter: ever heard of amd64-only bugs?
[16:29] <\sh> Keybuk, HP LJ 1020 USB works like a charm on gutsy+hardy amd64 with cups
[16:29] <\sh> Keybuk, even with sharing it with a windows os
[16:32] <mohbana> what exactly does ubuntu do to it's fonts  to make them look so good?
[16:38] <Keybuk> mohbana: ?
[16:38] <Keybuk> mohbana: depends which settings you use
[16:38] <Keybuk> (which reminds me to change the subpixel defaults <g>)
[16:40] <mario_limonciell> kees, yeah there are two diffs on the bug.  one of them is an SRU for hardy (i already subscribed ubuntu-sru and that diff is to hardy proposed).  the other one is a lot more intrusive and is intended for intrepid
[16:40] <mohbana> Keybuk: i am talking about the freetype settings, it's using something other than subpixel
[16:41] <mohbana> i've tried enabling that in fedora but it still doesn't look like ubuntu
[16:41] <jdstrand> pitti: hi!
[16:41] <Keybuk> mohbana: right, I mean are you comparing with fonts set at "Best Shapes", "Best Contrast" or "Subpixel smoothing" ?
[16:41] <mohbana> Keybuk: i just want to know the exact details of what ubuntu does to it's fonts
[16:42] <jdstrand> pitti: sorry about the same version thing with ufw-- I thought this was allowed because of the new *-blacklist having the same versions. Of course, these were pocket copied. I'll know for next time
[16:42] <jdstrand> s/these/those/
[16:43] <Keybuk> mohbana: it depends a lot on which option you select, that's all ;p
[16:43] <Keybuk> mohbana: in simple terms, we turn on all the patented stuff and apply patches to do LCD filtering when subpixel rendering
[16:44] <LaserJock> pitti: could you remove the smstools upload in hardy-proposed? there's another SRU and I'd prefer to have everything in one upload
[16:44] <mohbana> Keybuk: what patches please
[16:46] <Keybuk> mohbana: http://david.freetype.org/lcd/
[16:46] <Keybuk> but read http://david.freetype.org/cleartype-patents.html first
[16:50] <mohbana> wow them patches are really old! does ubuntu still use them?
[16:50] <Keybuk> mohbana: a better question would be "wow them patches are really old! why haven't upstream applied them?"
[16:50] <Keybuk> :p
[16:52] <kees> Keybuk: what exactly exploded with PIE?
[16:53] <Keybuk> kees: http://launchpadlibrarian.net/14987481/buildlog_ubuntu-intrepid-amd64.upstart_0.3.9-4_FAILEDTOBUILD.txt.gz
[16:53] <Keybuk> gcc -shared  .libs/alloc.o .libs/string.o .libs/list.o .libs/hash.o .libs/tree.o .libs/timer.o .libs/signal.o .libs/child.o .libs/io.o .libs/file.o .libs/watch.o .libs/main.o .libs/option.o .libs/command.o .libs/config.o .libs/logging.o .libs/error.o   -Wl,--version-script=./libnih.ver -Wl,-z -Wl,relro -Wl,-z -Wl,now -Wl,-O1 -Wl,-O1 -Wl,-soname -Wl,libnih.so.0 -o .libs/libnih.so.0.0.0
[16:53] <Keybuk> /usr/bin/ld: .libs/alloc.o: relocation R_X86_64_PC32 against symbol `nih_free' can not be used when making a shared object; recompile with -fPIC
[16:53] <Keybuk> /usr/bin/ld: final link failed: Bad value
[16:53] <Keybuk> collect2: ld returned 1 exit status
[16:54] <kees> Keybuk: doin' it wrong.  :P
[16:54] <Keybuk> kees: -v
[16:54] <kees> heheh
[16:54] <kees> I assume either  a) some .o wasn't compiled with -fPIE, or  b) the final link lacked -pie
[16:54] <kees> (the final link -pie tells the compiler which crt to link in)
[16:55] <Keybuk> hmm
[16:55] <Keybuk> libtool called it with -pie
[16:55] <Keybuk> but that got eaten
[16:55] <kees> however... you're making a shared object here.
[16:55] <Keybuk> does it need to be -Wl,-pie ?
[16:55] <kees> no
[16:55] <kees> PIE is a PITA.  :)
[16:55] <Keybuk> ?
[16:56] <kees> (Pain In The reAr)
[16:56] <kees> so, hm, if you're making a shared object, those need to all be -fPIC
[16:57] <Keybuk> hmm
[16:57] <kees> i.e. things going into a .so need -fPIC, things going into an executable need -fPIE (and a -pie at the end)
[16:57] <Keybuk> I don't really want the shared object
[16:57] <Keybuk> I just want the static one
[16:57] <kees> and PIC > PIE, so you can link -pie against PIC or PIE objects.
[16:58] <Keybuk> why does it work here and not on the buildds?
[16:58] <kees> uhm.... that's a good question.
[16:59] <kees> I hadn't really noted that issue until just now.  *head scratch*
[16:59] <kees> it's the same toolchain isn't it?
[16:59] <Keybuk> intrepid vs. hardy maybe?
[17:00] <kees> you're doing compiles in an intrepid chroot, yes?
[17:00] <Keybuk> no
[17:00] <Keybuk> hmm
[17:00] <kees> :P
[17:00] <Keybuk> actually, I think I compiled this on i386
[17:01] <Keybuk> where it apparently works fine
[17:01] <Keybuk> if I do it on amd64, even on hardy, it fails
[17:02]  * kees scratches his head even more
[17:02] <kees> well, clearly one issue is the -fPIE of a shared object.  those should be -fPIC.
[17:03] <Keybuk> I don't understand why the -static is getting lost
[17:03] <Keybuk> hah, I bet setting LDFLAGS is overriding it
[17:04] <zul> \sh: I dont have a problem with it lemme ask around
[17:05] <kees> back in a bit...
[17:06] <Awsoonn> hi all~ I'm new to Ubuntu development, working on potentialy fixing a bug in rhythmbox that ... bugs me
[17:07] <Awsoonn> how can i find out if there are any patches applied to the ubuntu version of rhythmbox that are not applied to upstream?
[17:08] <ogra> read the changelog, patches are listed in the upstream merges usually ... and you can grab the source package and look in debian/patches/
[17:08] <stgraber> Awsoonn: apt-get source rhythmbox, then look at the debian directory and see if there is a patches/ subdirectory
[17:09] <seb128> Awsoonn: there is only a patch to build using xulrunner1.9, a launchpad intregration change and an update to the radios list to use ogg
[17:10] <iwkse> hi all, is this a good place for usplash questions?
[17:10] <Keybuk> seb128: applied a trivial one-line patch to gnome-contol-center
[17:10] <Keybuk> expect bugs from frothing-at-the-mouth loonies
[17:10] <seb128> Keybuk: you are messing with fonts settings again, aren't you? ;-)
[17:10] <ogra> a one line patch with half a novel in the changelog :)
[17:11] <Keybuk> seb128: I've made the change I agreed to wait until the start of a non-LTS release cycle to make ;)
[17:11] <Awsoonn> alright, if I want to fix something, generally speaking, should I work on the upstream truck, or the source I get from apt-get?
[17:11] <seb128> ah ah
[17:11] <seb128> Awsoonn: upstream is better but there is not a lot of difference currently
[17:11] <Keybuk> seb128: it passed the njpatel test a few weeks ago
[17:11] <Keybuk> "Wait! What are you doing! Leave my font settings alone! It took me ages to get those ri....ooh, that's much better!"
[17:12] <njpatel> Keybuk: :-)
[17:12] <njpatel> Keybuk: you changed my life
[17:12] <seb128> Keybuk: btw, congrats, you just won the right the merge gnome-control-center now that you touched it ;-)
[17:12] <seb128> s/the merge/to merge
[17:12] <ogra> hehe
[17:12]  * seb128 runs
[17:12] <Keybuk> seb128: no problem, I'll just delegate it to one my team
[17:13] <Keybuk> seb128: could you merge gnome-control-center, kthxbye
[17:13] <Keybuk> :p
[17:13] <seb128> doh ;-)
[17:18] <Awsoonn> just curious, what do you guys use pro hackers use for a programing environment?
[17:18] <geser> $EDITOR
[17:18] <Awsoonn> like, Vim/grep, or eclipse, Kdevelop, etc
[17:18] <Keybuk> emacs
[17:18] <ogra> vim
[17:18] <Keybuk> though I will gladly bear the first-born of anyone who writes a decent GTK+ IDE
[17:19] <soren> Awsoonn: vim
[17:19] <Awsoonn> what do you think of eclipse and Kdevelop and such IDEs?
[17:20] <Keybuk> Awsoonn: Depends: java, pain ... Depends: kde, pain
[17:21] <ogra> Keybuk, nothing for emacs fans, but i found pida quite intresting for pygtk development in the past
[17:21] <ogra> (it embeds glade and vim)
[17:21] <seb128> an d gedit rocks ;-)
[17:21] <ogra> not sure its still under development though
[17:21] <seb128> and gedit rocks ;-)
[17:21] <ogra> it misses the vim mode yet :)
[17:22] <Keybuk> seb128: gedit, with an integrated debugger and source analyser is starting to be along the right lines
[17:23] <Keybuk> I don't know why, but Anjuta should be perfect
[17:23] <Keybuk> yet it's so far off the mark
[17:23] <ogra> oh, pida added an emacs mode :)
[17:24] <ogra> but doesnt work :/
[17:25] <persia> Keybuk: gedit + Nemiver goes a long way towards that
[17:30] <LaserJock> zul: ping
[17:31] <zul> LaserJock: hi!
[17:36] <Keybuk> though I must admit, saying that, that anjuta 2.4 is a rather nice step in the right direction
[17:36] <Keybuk> I might try using that for a bit and see how long it takes me to want to kill people
[17:42] <Keybuk> so, about 5 minutes then
[17:45] <ogra> heh
[17:45] <persia> Is that a longer or shorter period than the last version?
[17:45] <Keybuk> a bit longre
[17:46] <ogra> more options to configure before you can use it ?
[17:55] <pitti> Keybuk: does anjuta have gvim intregration? :-)
[17:56] <pitti> (seriously, I got so addicted to the "handle complex objects" commands in vim that it would take a lot to convince me to abandon it again)
[18:20] <Keybuk> pitti: probably not ;)
[18:20] <Keybuk> it doesn't have C-x 4 a
[18:20] <Keybuk> which is the single most fantastic emacs feature ever
[18:20] <pitti> what does it do?
[18:20] <pitti> eliza?
[18:20] <Keybuk> adds a changelog entry
[18:20] <ogra> pitti, http://picasaweb.google.co.in/arunchaganty/Anjuta/photo#5206317121142374866
[18:20] <Keybuk> with your name, e-mail, the date, the filename and current function all filled in for you
[18:21] <pitti> nice
[18:21] <pitti> ogra: oooooh!
[18:21] <pitti> Keybuk: see ogra's screenshot, that looks quite vimish
[18:21] <ogra> pitti, SoC :)
[18:22] <ogra> http://arunchaganty.wordpress.com/2008/06/01/vim-communication/#ref-1
[18:22] <Keybuk> heh
[18:22] <Keybuk> if I could find an anjuta add to changelog plugin, I might be happy
[18:23]  * pitti doesn't write upstream changelogs; bzr log -v --log-format 'gnu' > ChangeLog FTW!
[18:24] <Keybuk> I do the exact opposite
[18:24] <Keybuk> I have a bzr-commit shell script that puts the new ChangeLog entries into the commit log
[18:24] <Keybuk> (it occurs to me that it's possible to do that as a plugin to bzr commit)
[18:26] <seb128> pitti: ah, right, 'gnu' which is a non standard thing, I still remember it from the time I tried to do a jockey rebuild upload ;-)
[18:26] <pitti> Keybuk: I do that for debian/changelog (debcommit)
[18:27] <pitti> yay me for consistency :)
[18:27] <pitti> but with the current tools, those are the easiest, I think
[18:27] <ogra> how do you get  --log-format 'gnu' working ?
[18:27] <ogra> my bzr only knows long, line and short as options
[18:27] <seb128> probably by installing something you find on the way
[18:27] <Keybuk> ogra: there's a plugin
[18:27] <ogra> ah
[18:28] <ion_> "              This behavior is identical to how emacs handles ChangeLog
[18:28] <ion_> "              files with the change-log-mode provided by C-x 4 a.
[18:28] <ion_> gnuchlog.vim
[18:30] <ion_> keybuk: ↑
[18:30] <Keybuk> ion_: ref?
[18:31]  * ion_ googles... http://www.vim.org/scripts/script.php?script_id=1631
[18:32] <Keybuk> ion_: so not helpful for Anjuta then? :p
[18:33] <ion_> keybuk: There was a discussion about having vim in anjuta. :-)
[18:34] <Keybuk> ion_: and then why not just use vim? :p
[18:34] <ion_> Well, i do. ;-)
[19:16] <blueyed> Why does virtualbox-ose-modules does not show up in the NEW queue at https://edge.launchpad.net/ubuntu/hardy/+queue? (I've received an ACK 16 minutes ago). And, once if should show up, can an archive admin approve it please (version 24.0.3)?
[19:18] <blueyed> well.. "waiting for approval" should land in NEW, shouldn't it?
[19:19] <persia> blueyed: "waiting for approval" is in unapproved.  It goes to NEW once it gets approved (archive admins have to press two buttons)
[19:20] <persia> blueyed: https://launchpad.net/ubuntu/hardy/+queue?queue_state=1&queue_text=
[19:20] <slangasek> blueyed: what's the difference between 24.0.2 and 24.0.3?
[19:20] <blueyed> persia: thanks, must be blind.. anyway, please approve.
[19:20] <blueyed> slangasek: I've messed up the changelog in .2
[19:21]  * persia is very much not an archive admin
[19:21] <blueyed> (build the new module from the intrepid source package)
[19:21] <blueyed> persia: I know.. wasn't meant to be in the same line/to you.
[19:23] <slangasek> blueyed: mm, well, you don't have to increment the version number in that case when it's a -proposed upload, you can just ask the archive admin to remove the broken package from the unapproved queue
[19:24] <blueyed> slangasek: ah, good to know. thanks. but it should be ok now as .3, isn't it?
[19:24] <slangasek> blueyed: ... and -proposed has -19 now instead of -18; you may want to jump over -18 here and just get a version for -19 pushed into -updates at the same time
[19:25] <slangasek> yes, .3 is ok otherwise
[19:25] <slangasek> and if you think it's important to get a fixed modules package for -18 in, I can approve it as-is
[19:26] <blueyed> slangasek: yes, it's important. a hell lot of users are complaining.. :/ I'll upload .4 for -19 then, too, yes?
[19:26] <ogra> seb128, do you have any idea if there are python-wnck bindings anywhere out in the world ?
[19:26]  * ogra cant imagine they dont exists
[19:26] <slangasek> blueyed: you can only have one version in -proposed at a time
[19:26] <seb128> ogra: python-gnome2-desktop has those
[19:26] <ogra> oh
[19:26] <ogra> i was looking for python-wnck :)
[19:26] <ogra> sill yme
[19:28] <blueyed> slangasek: well.. please go with -18 and hopefully it gets approved shortly.
[19:30] <slangasek> blueyed: this does mean that pushing in a -18 version right now may make a fixed -19 version later due to the timeline; but .0.3 is accepted now
[19:31] <emgent> someone have 05ca:1803 Ricoh Co., Ltd webcam ?
[19:54] <blueyed> slangasek: I suppose virtualbox-ose-modules gets copied then to -security and -updates? So that it makes sense to have a version for -18, if somebody is only using -security, but not -updates, correct?
[19:59] <shonen> does anyone know the minimum libpcap version is for usb capture support?
[20:00] <shonen> never mind, I found it
[20:18] <slangasek> blueyed: mm, I don't know about copying it to -security; I don't know if that works in practice
[20:22] <slangasek> blueyed: normally the packages come in the other direction, and I believe we do have provisions for universe packages published as security updates even though they're not part of Canonical's security support
[20:23] <kees> is there a kernel module we need to push through -security?
[20:24] <kees> we've done this in the past for things like the external apache worker, etc
[20:26] <slangasek> kees: virtualbox-ose-modules, which has been uploaded to -proposed
[20:27] <fyrestrtr> hello -- does the 32bit hardy default kernel not have highmem support?
[20:27] <fyrestrtr> on my 4GB ram laptop usable memory is only 2GB
[20:29] <kees> fyrestrtr: you can either install the -server kernel for PAE mode, or you can run the 64bit kernel.
[20:29] <kees> slangasek: er, so it needs to go through -security instead?
[20:30] <slangasek> well, that would be the ideal
[20:30] <fyrestrtr> will the -server kernel affect negatively on proprietary drivers? I have the nvidia driver set installed.
[20:31] <fyrestrtr> I tried the 64bit kernel before, but I have run into some compatibility issues with things like oracle and enterprisedb.
[20:32] <kees> fyrestrtr: I'm actually not sure about the nvidia bit, I think it's okay.  check in #ubuntu-server perhaps?
[20:33] <tkamppeter> Keybuk, up to now I did not encounter a 64-bit-only bug, but I can imaging that they exist, when it comes to handling of bits and bytes, which is often done in printer drivers.
[20:38] <fyrestrtr> can anyone point me to where I can find out about the differences between the Fedora 9 startup bootsplash and the Ubuntu one? I would like to find a way to integrate the Fedora splash with Ubuntu.
[20:39] <pwnguin> apt-get source usplash
[20:39] <pwnguin> no sudo
[20:40] <fyrestrtr> they are the same thing, yes? Previous Ubuntu releases used to have text in addition to the progress meter. I would like the text option back, like with Fedora 9.
[20:40] <pwnguin> you wanted to know what the differences are
[20:40] <pwnguin> get the source and diff em
[20:40] <pwnguin> not sure where to grab fedora's
[20:41] <pwnguin> but there is text in ubuntu -- if you have a scheduled fsck it displays it
[20:41] <pwnguin> along with instructions on how to cancel
[20:43] <james_w> fyrestrtr: remove "quiet" from the kernel command line in grub to get the messages back.
[20:44] <kees> fyrestrtr: remove "quiet" from your menu.lst
[20:45] <pwnguin> i thought that dumped you out of usplash
[20:45] <kees> pwnguin: no, that's removing "splash"
[20:45] <pwnguin> alrighty
[20:46] <pwnguin> fyrestrtr: and if you want that change to stick, make sure you hit the automagic lines in menu.lst too
[20:46] <kees> or run "sudo update-grub"
[20:47] <pwnguin> will that hit the kernel default options?
[20:47] <pwnguin> (for kernel upgrades etc)
[20:49] <kees> pwnguin: if you change the default lines, it will update the per-image lines, yes.
[20:56] <fyrestrtr> two questions regarding tomcat5.5 -- why is there /etc/tomcat5.5/tomcat5.5 which points to /etc/tomcat5.5 -- leading to interesting but pointless things such as /etc/tomcat5.5/tomcat5.5/tomcat5.5/ and -- where are the shared libraries stored?
[20:57] <Awsoonn> hi all, newb here. I want to do some bub work on Rythmbox and am wondering where the best place is to get the source from and best place to post patches?
[20:57] <Awsoonn> bug work**
[20:58] <mohbana> sorry back with freetype question
[20:58] <mohbana> i just want to know the exact details of what ubuntu does to it's fonts
[21:00] <_MMA_> Awsoonn: Maybe upstream?
[21:01] <Awsoonn> _MMA_: i'm a bit confused really, when would I want to work on the source from apt-get or bzr then?
[21:03] <_MMA_> I would think you would only use bzr if upstream uses it as their vcs.
[21:03] <Awsoonn> and what about apt-get source?
[21:03] <_MMA_> I think the only reason to grab it from apt is if you just want to build it yourself.
[21:04] <Awsoonn> *Nods* and what might I want to do about patches applied to ubuntu's version and not the upstream version? just make sure the patch works in both places?
[21:04] <_MMA_> Awsoonn: http://www.gnome.org/projects/rhythmbox/development.html
[21:06] <Awsoonn> I'm sorry, I'm just currently working on rhythmbox, I'm trying to figure out how the bigger picture works with ubuntu and upstream with projects in general
[21:06] <_MMA_> Im unsure about any "ubuntu-specific" patches. seb128 might be able to comment. I usually prefer to get things in upstream myself.
[21:07] <seb128> _MMA_: usually if you work on changes better to use upstream as a base
[21:07] <Awsoonn> I think I'v pestered seb128 more than enough for one day :)
[21:07] <seb128> ups
[21:07] <seb128> Awsoonn:: usually if you work on changes better to use upstream as a base
[21:07] <seb128> you can get the svn or "bzr get lp:rhythmbox" which gives you a bzr import, nicer to work on
[21:07] <seb128> the bzr import is equivalent to current svn
[21:08] <seb128> once you have a patch attach it to bugzilla.gnome.org
[21:08] <seb128> if you think that's an issue worth fixing on ubuntu look on launchpad
[21:08] <Awsoonn> awesome, that is exactly the kinda of info I was looking for, Thank you.
[21:08] <seb128> https://launchpad.net/ubuntu/+source/rhythmbox/+bugs
[21:08] <seb128> if it's not opened there open a new bug
[21:09] <seb128> otherwise use the currently open one
[21:09] <seb128> add a task pointing to the gnome bugzilla bug
[21:09] <seb128> and attach your patch
[21:09] <seb128> you might want to subscribe the ubuntu-main-sponsors team too
[21:09] <seb128> we are usually able to figure how to apply the patch ;-)
[21:10] <seb128> if you want to do all the work you can apply the patch to the current ubuntu package and attach a debdiff (diff between the current package and the updated version you built) but that's not required
[21:11] <Awsoonn> i'd like to do it so I know how to at least, have a link?
[21:13] <seb128> Awsoonn: https://wiki.ubuntu.com/PackagingGuide/Recipes/Debdiff has a detailled example
[21:52] <ScottK> pitti: Do you plan on continuing to use guidance-backends for jockey?  If so, is there a way I can talk you out of it?
[21:53] <pgraner>  /msg NickServ identify intell
[21:53] <pgraner> d /msg NickServ identify intell
[21:53] <ScottK> pgraner: You'll want to change that password now.
[21:53] <pgraner> yea
[21:54] <tormod> bryce, if you're still in sponsor-mood, can you please look at bug 237266? Kind of follow up from yesterday (and no-brainer).
[21:54] <bryce> tormod, sure, in a few minutes
[22:18] <iwkse> hi all, i'm experiencing a problem with usplash. When i create the theme and i try it on my pc it works great, but in chroot (livecd) testing it with usplash -c it doesn't show it. Booting the iso give black screen. I also tried with the eft-example theme and it's still the same effect on the chroot. usplash -c says usplash: can't get console font: Invalid argument but i get the same also on my pc but it works. Why it wouldn't works in chroot?
[22:25] <DktrKranz> any sponsors for main around to look at bug 226783?
[22:27] <Keybuk> Mithrandir: around?
[22:28] <\sh> Keybuk: the change to upstart didn't fix the sysvutils problem in intrepid it seems
[22:28] <Keybuk> or infinity, or someone of equal crackfulness ;)
[22:28] <tormod> hibernation is broken on many laptops due to bug 226069, can some pm-utils knowledgeable look at it please?
[22:30] <\sh> anyways...no the time anymore to deal with this .... sleep is more valuable
[22:33] <ScottK> \sh: Sleep is for the weak.
[22:50] <impulze> um is there any channel not so heavily crowded as the main one? it seems my question gets scrolled out far too fast ;)
[22:54] <ScottK> impulze: No.  That's it.  You might try the mailing list if you want something slower paced.
[22:55] <impulze> ok
[23:04] <MacSlow> In which package/patch is the logout-dialog hidden?
[23:04] <ogra> MacSlow, gnome-session
[23:05] <MacSlow> in sesssion... well :)
[23:05] <MacSlow> I looked in gdm, gnome-panel, gnome-applets... just no in session
[23:05] <MacSlow> ogra, thx
[23:07] <iwkse> usplash -c wouldn't works in chroot...it's me or you can notice it too?