[12:07] <ajmitch> Keybuk: sorry, I can't unsubsribe -archive from that bug, description has been changed now anyway
[12:10] <ogra> is there any lsof equivalent in python ?
[12:10] <tsdgeos> hi
[12:10] <tsdgeos> who packages poppler for ubuntu?
[12:11] <LaserJock> mdke: I'd talk to mvo
[12:11] <LaserJock> tsdgeos: check the Lauchpad page
[12:12] <slomo> tsdgeos: i made the last changes
[12:12] <tsdgeos> slomo: someone told me you have zlib usage enabled
[12:12] <Keybuk> ajmitch: it's probably easier to just ask mdz directly than file a bug
[12:13] <slomo> tsdgeos: yes... there already is a bug about it upstream that it breaks under certain conditions
[12:14] <tsdgeos> upstream lol
[12:14] <slomo> tsdgeos: if this is fixed soon i'll leave it, otherwise disable it again
[12:14] <tsdgeos> so it now our fault that you enable things that should not be enabled?
[12:14] <tsdgeos> we already know its broken
[12:14] <slomo> tsdgeos: https://bugs.freedesktop.org/show_bug.cgi?id=7798
[12:14] <tsdgeos> that's because it's disabled
[12:14] <Ubugtu> Freedesktop bug 7798 in general "Crash in StreamPredictor::getChar" [Normal,New]
[12:14] <tsdgeos> don't need to show me my bugs ;-)
[12:15] <slomo> tsdgeos: why is there no warning or something written somewhere else about it that it must not be enabled? if it is meant to be disabled i'll disable it again, no problem :)
[12:15] <tsdgeos> probably because we suck as a project
[12:16] <tsdgeos> https://bugs.freedesktop.org/show_bug.cgi?id=3948
[12:16] <Ubugtu> Freedesktop bug 3948 in general "Pdf fails when using zlib based decoder instead of xpdf one" [Normal,New]
[12:17] <tsdgeos> is older and is the bug i opened to convice the others to disable it
[12:17] <tsdgeos> hey Ubugtu is nice, how many bugzillas does he know?
[12:18] <tsdgeos> slomo: what also happens is that Jeff wrote the zlib based code and noone else knows much about it and he is not much around lately so it's diffcult to touch the code
[12:18] <ajmitch> mdz: ping (cdbs UVF)
[12:18] <slomo> tsdgeos: ok, so what's the reason why nobody changes it to be disabled? :) i'll disable it now for the ubuntu package again
[12:19] <tsdgeos> slomo: it is disabled
[12:19] <tsdgeos> no?
[12:20] <tsdgeos> well, you mean disabled completely?
[12:21] <slomo> tsdgeos: that or at least add some warning to the configure flag or have a warning in the README
[12:21] <tsdgeos> yeah
[12:21] <tsdgeos> you're right, i'll add a coment to the configure --help
[12:22] <slomo> tsdgeos: thanks :)
[12:23] <tsdgeos>   --disable-zlib          Don't build against zlib. This is the default value
[12:23] <tsdgeos>                           as the zlib code is know to fail in some cases.
[12:23] <tsdgeos> better?
[12:24] <slomo> yes
[12:24] <tsdgeos> oki
[12:25] <tsdgeos> don't you love open source?
[12:29] <tsdgeos> bye
[01:07] <Keybuk> I can't help but wonder ...
[01:08] <Keybuk> what happens if you pass a file descriptor (using SCM_RIGHTS) to a process that wasn't expecting one
[01:08] <Keybuk> is that a way of preventing a file from being deleted?
[01:29] <zul> hey
[01:29] <ajmitch> hello zul
[01:36] <zul> hey ajmitch
[01:39] <imbrandon> 'ello everyone
[01:40] <bddebian> Howdy
[01:51] <lamont> mdz: I could drop resolvconf down to suggests if you want...
[01:51] <madduck> lamont: out of curiosity, why did you list it as recommends in the first place?
[01:52] <lamont> madduck: "standard reason"
[01:53] <madduck> lamont: which is? i am sorry, but i really don't know.
[01:53] <lamont> ("it seemed like a good idea at the time", or more specifically, someone convinced me it was a good idea)
[01:53] <madduck> :)
[01:53] <lamont> but then, at the time, nothing installed even recommends automatically....
[01:53] <madduck> uh. revise! :)
[01:54] <lamont> so it was one of those "whatever, if it'll shut you up" kind of thought processes... hence the lack of care about changing it back to suggests
[01:54] <madduck> makes perfect sense. glad that mdz pointed it out.
[02:11] <bddebian> bluefoxicy: You around?
[02:13] <bluefoxicy> hi
[02:14] <bluefoxicy> did I do something useful while I wasn't paying attention?
[02:14] <bddebian> bluefoxicy: Hi.  Do you have any additional input on Bug #466 ?  I'm not quite sure what to do with it
[02:14] <Ubugtu> Malone bug 466 in snort "Snort 2.3 Inline Support" [Wishlist,Needs info]  https://launchpad.net/bugs/466
[02:14] <bluefoxicy> bddebian:  Additional input:  Snort 2.6 is out.  Snort 2.4 was also out.  Why are we so far behind?  :)
[02:15] <bluefoxicy> bddebian:  besides that I'm fairly sure --enable-inline still requires a library we don't have.
[02:15] <bluefoxicy> bddebian:  do you know what version of snort is in latest debian unstable?
[02:16] <crimsun> http://packages.qa.debian.org/s/snort.html
[02:17] <bluefoxicy> 2.3.3
[02:17] <bluefoxicy> same here.
[02:17] <bluefoxicy> I would not worry too much about inline until somebody decides to care about snort again.
[02:18] <bluefoxicy> At this point I would say that most people who care enough about it are going to wind up building their own anyway, since version 2.3 is deprecated and I think 2.4 is also deprecated.
[02:21] <bluefoxicy> actually, I'm going to file a bug on that :|
[02:22] <mdz> lamont: I do want
[02:22] <mdz> lamont: I don't think it should be installed with postfix by default
[02:30] <infinity> lamont: "nothing installed recommends by default at the time"?  Bah.  We, the dselect users, collectively spit at thee.
[02:31] <Fujitsu> Hahhaa/
[02:31] <bddebian> bluefoxicy: So is it OK if I reject 466?
[02:33] <Keybuk> infinity: what, you and elmo?
[02:33] <infinity> Keybuk: And kamion.
[02:33] <infinity> Keybuk: And iwj.
[02:33] <bluefoxicy> bddebian:  can you defer it for later?
[02:33] <bddebian> infinity: Hehe
[02:33] <infinity> Keybuk: And that may be the entire dselect community. :)
[02:33] <bluefoxicy> bddebian:  or is it all or nothing
[02:33] <bddebian> bluefoxicy: I can leave it but if 2.3 is dead why bother?
[02:34] <bluefoxicy> bddebian: I could change the description to 2.6 later, or you could kill it and I can open a new bug if we ever get 2.6
[02:34] <bddebian> bluefoxicy: Why don't you package 2.6? ;-)
[02:34] <bluefoxicy> bddebian: honestly?  Too lazy to figure out what files to split into what packages.
[02:35] <bluefoxicy> (i.e. too busy playing Solar Jetman on my freshly modded NES)
[02:35] <bluefoxicy> bddebian:  I'll take a crack at it maybe but I don't want to wind up being the new maintainer.
[02:36] <Kaleo> mjg59: /etc/acpi/suspend.d/05-acpi-lock.sh does not check if the lock is triggered; see bug 31935 and patch proposed
[02:36] <Ubugtu> Malone bug 31935 in acpi-support "ThinkPad, Fn-F4 leads to double unsuspend" [Medium,Confirmed]  https://launchpad.net/bugs/31935
[02:40] <bddebian> bluefoxicy: Do you have an upstream source for snort?
[02:42] <bluefoxicy> bddebian: somewhere on snort.org?  Or what do you mean upstream source?  just the source code right/
[02:42] <bluefoxicy> http://snort.org/dl/
[02:42] <bddebian> Yeah, just found that but I was just reading the Debian about re-distribution issues with 2.4
[02:45] <bluefoxicy> bddebian:  oh?  I thought the code was gpl
[02:46] <bluefoxicy> the rules are non-distributable but that doesn't matter, 1) there's release-time GPL rules; 2) a registered feed can be used with oinkmaster legally, but the user has to get it himself.
[02:46] <bddebian> Aye, that's what the submitter says
[02:46] <bluefoxicy> there was some FUD that there were "no GPL rules" and that "oinkmaster no longer works" at one place.
[02:50] <bddebian> bluefoxicy: Are rules distributed in the current package?
[02:51] <Keybuk> memo-to-self ... printf ("%d" % getpid ()) ... does NOT work in C
[02:52] <bluefoxicy> bddebian:  it seems we have snort-rules-default, which snort depends on (which I think it shouldn't because rules can come straight from oinkmaster anyway... and they will destroy the files installed by snort-rules-default)
[02:53] <bddebian> Hmm, I don't know if I want to "break" any more packages in Universe :)
[02:53] <bluefoxicy> Keybuk:  you need a comma, not a %.  :)  *not helpful, but friendly*
[02:53] <bluefoxicy> bddebian:  srd is just the gpl rules
[02:54] <bddebian> bluefoxicy: Ah
[02:55] <bluefoxicy> and they get released at every snort release so the version is the same as snort
[02:55] <bluefoxicy> and then there was Hobbsee
[02:55] <bddebian> bluefoxicy: The debian maintainer claims that the number of rules would drop from 3100 to like 30
[02:56] <bddebian> Heya Hobbsee
[02:56] <Hobbsee> hi bddebian
[02:57] <bluefoxicy> bddebian:  I claim we don't care because 1) the current ruleset is outdated, and outdated IDS/antivirus rulesets are USELESS (this is reactive security, it's useless by default); 2) Oinkmaster works, and snort is in general an alert system and not a protection (inline is a protection), so the user has to "know what he's doing"
[02:58] <bluefoxicy> lemme make sure oinkmaster has 2.6 stuff
[03:00] <bluefoxicy> -CURRENT seems to be 2.6 yes.
[03:08] <TheMuso> c
[03:09] <TheMuso> c
[03:09] <TheMuso> crap
[03:09] <Hobbsee> Keybuk: w.r.t eric, the only change that we may need to keep is that it replaces eric3, which doesnt exist on ubuntu anyway.  what changes thinking about?
[03:10] <Keybuk> dunno, didn't look
[03:10] <Keybuk> the tool just tells me that there were changes, and you didn't say in the bug that it was ok to override them
[03:10] <Hobbsee> Keybuk: right.  well i confirmed it, so i'm not sure why you're asking for another confirmation :P
[03:10] <Hobbsee> thanks for the syncs, btw
[03:10] <Hobbsee> gnomefreak didnt, i'll bug him
[03:12] <Keybuk> you just confirmed that the non-ubuntu-dev member wasn't trying to h4x0r us ;)
[03:12] <Hobbsee> Keybuk: heh.  true
[03:12] <Hobbsee> Keybuk: i think we're all getting lazy with the numbers of syncs being requested.
[03:12] <Hobbsee> Keybuk: how do you know that i'm not trying to h4x0r us?  you've never met me.
[03:12] <Hobbsee> in person, at least :P
[03:12] <crimsun> (you're in ubuntu-dev, that's moot)
[03:13] <Hobbsee> crimsun: they still havent met me to find out if i'm an axe murderer or out to kill everything off.  maybe i can just talk my way thru getting -dev rights.
[03:14] <ajmitch> Hobbsee: enough of us have met you to sign your key, at least
[03:14] <Hobbsee> point.
[03:14] <ajmitch> and the same could apply to any of us
[03:14] <Hobbsee> also true
[03:14] <ajmitch> fo all we know, I could be trying to bring down the archive via cdbs, for example
[03:14] <Hobbsee> true
[03:14] <Keybuk> cdbs manages that all on its own
[03:14] <Hobbsee> then we discuss levels of paranoia, and sensible ones.
[03:14] <Hobbsee> haha
[03:15] <Keybuk> Hobbsee: it's all about trust levels ... you hung around enough doing good works that you were passed for general upload access to universe by the Technical Board
[03:15] <Keybuk> obviously you could have just been good so you could be bad once you got access
[03:15] <Keybuk> but we didn't think so
[03:15] <zul> Hobbsee: and here i am thinking that you are an axe murderer
[03:16] <Hobbsee> Keybuk: that's true.
[03:16] <ajmitch> plus we know where you live
[03:16] <Hobbsee> zul: you may well be right.
[03:16] <zul> Hobbsee: you sure you arent lizzie borden
[03:16] <Keybuk> there's something very strange about an actor from the original Stargate movie turning up in the series playing something else
[03:17] <zul> Hobbsee: google lizzie borden
[03:21] <Hobbsee> zul: and you're in luck - i couldnt carry my axe with my textbooks/laptop/etc home last night.  so you'll get a few days where i cant axe murder you
[03:21] <Hobbsee> hum.  i lost my .ssh key.
[03:24] <zul> Hobbsee: you have to find me first..
[03:24] <Hobbsee> zul: point.
[03:24] <zul> and i dont give out my address to no stinking axe murderers
[03:25] <Hobbsee> hah
[03:30] <Hobbsee> yay, debtags/adept stuff didnt get fixed.
[04:19] <jdub> hrm
[04:20] <jdub> apparently, i'm not getting any love out of the ng-ified madwifi in -6
[05:11] <foo> err, I am getting this; The following packages have unmet dependencies: mplayer-nogui: Depends: libggi2 (>= 1:2.0.5) but it is not installable .. broken packages. I am on ubuntu, any ideas? This sounds like an RPM issue. I left that scene ...
[05:13] <rodarvus> foo, #ubuntu
[05:14] <rodarvus> hi Hobbsee :)
[05:14] <foo> rodarvus: Uh, I asked in there. No one knows.
[05:14] <Hobbsee> rodarvus: you didnt manage to break my X!  shame on you!
[05:14] <ajmitch> hello rodarvus
[05:14] <Hobbsee> foo: edgy/dapper?
[05:14] <rodarvus> hey ajmitch
[05:14] <foo> Hobbsee: Dapper, 6.06
[05:15] <foo> Thanks
[05:15] <Hobbsee> foo: can you paste your /etc/apt/sources.list to pastebin please?
[05:15] <foo> Hobbsee: http://paste.ubuntu-nl.org/20729
[05:16] <Hobbsee> thanks
[05:16] <foo> thank you
[05:16] <Hobbsee> foo: line 22 and 23 - you're missing a "universe" before each multiverse
[05:16] <Hobbsee> fix that, update sources list, no more problem, i expect
[05:17] <Hobbsee> foo: yep, there's your problem.
[05:18] <Hobbsee> installs fine
[05:18] <foo> Ah, thank you. I was questioning my switch from debian to ubuntu, but this PEBKAC.
[05:18] <Hobbsee> foo: yeah.  there seem to be a *lot* of PEBKAC errors w.r.t sources lists now.  they redid the page on sources lists so it couldnt just be copy and pasted anymore.
[05:19] <foo> Hobbsee: lame
[05:19] <bluefoxicy> ubuntu-desktop wants to be removed if python-support is removed; promote python-support to main or fix whatever... hm.  o.o
[05:19] <Hobbsee> sarah@sarah:~$ show python-support | grep main
[05:19] <Hobbsee> Filename: pool/main/p/python-support/python-support_0.4.1_all.deb
[05:19] <Hobbsee> Filename: pool/main/p/python-support/python-support_0.3.8_all.deb
[05:19] <Hobbsee> bluefoxicy: ^
[05:20] <Hobbsee> bluefoxicy: it's already there mate
[05:21] <bluefoxicy> Hobbsee:  cool, mine must be outdated.
[05:23] <bluefoxicy> Sarah Connor IS a psychopathic bitch
[05:23] <bluefoxicy> she's the woman from the Terminator series
[05:23] <Hobbsee> ah right
[05:24] <bluefoxicy> in the first movie she's attacked by a robot from the future; in the second, she's in a psycho ward for believing she got attacked by a robot from the future, and has trained herself to tear the shit out of any more robots from the future she meets.
[05:30] <Hobbsee> right
[05:50] <desrt> bluefoxicy; sounds like terminator
 Sarah Connor IS a psychopathic bitch\nshe's the woman from the Terminator series
[05:51] <desrt> you left out "in the third one she's dead of cancer"
[05:52] <crimsun> (thanks for spoiling T3, as I hadn't seen it!)
[05:53] <bddebian> Heh
[05:53] <desrt> you find out about that pretty close to the start
[06:00] <infinity> crimsun: I'm pretty sure that discussing the plot of a movie isn't considered a "spoiler" three years after its release. :P
[06:00] <infinity> crimsun: (Granted that means it probably only ran in Australia a month ago, but for everyone else in the world, there's no excuse)
[06:00] <bddebian> hah
[06:00] <TheMuso> hehe
[06:01] <crimsun> infinity: of course not :)
[06:04] <TheMuso> Hobbsee: I am not much of a movie buff either.
[06:04] <TheMuso> Except for some sci-fi/fanticy stuff.
[06:20] <dooglus> when I run evolution, it complains a lot about "too many open files".
[06:20] <dooglus> is there some way to increase the limit?
[06:20] <dooglus> it's 1024 at the moment
[06:30] <Keybuk> quest upstart% ./client -p 4950 status ping
[06:30] <Keybuk> ping (stop)
[06:30] <Keybuk> currently waiting
[06:30] <Keybuk> quest upstart% ./client -p 4950 start ping
[06:30] <Keybuk> ping (start)
[06:30] <Keybuk> currently starting, process active
[06:30] <Keybuk> quest upstart% ./client -p 4950 status ping
[06:30] <Keybuk> ping (start)
[06:30] <Keybuk> currently running, process active
[06:31] <Keybuk> quest upstart% ./client -p 4950 stop ping
[06:31] <Keybuk> ping (stop)
[06:31] <Keybuk> currently running, process killed
[06:31] <Keybuk> quest upstart% ./client -p 4950 status ping
[06:31] <Keybuk> ping (stop)
[06:31] <Keybuk> currently waiting
[06:31] <Keybuk> \o/
[06:31] <Fujitsu> That looks somewhat like a Symantec Ghost client's status log.
[06:32] <Keybuk> replace "ping" with, say, "apache"
[06:32] <Amaranth> Keybuk: yay
[06:32] <crimsun> I'm thinking that's part of Keybuk's init New World Order.
[06:32] <infinity> Keybuk: But ping is a way cooler service.
[06:32] <Fujitsu> I guess so.
[06:32] <Fujitsu> infinity, of course. Everything needs that service.
[06:32] <Keybuk> infinity: it was the best example of a long-running process that I could think of
[06:32] <Fujitsu> Apache's not important :P
[06:33] <infinity> Keybuk: /usr/bin/yes
[06:33] <Hobbsee> crimsun: oh dear.  scary init New World Order
[06:33] <poningru> ooh
[06:33] <Fujitsu> I like it...
[06:33] <Fujitsu> And replacing cron'll be fun :)
[06:34] <Hobbsee> Fujitsu: yeah, but if he gets unhappy, he might just decide to break everyone's systems cos he can.
[06:34] <Fujitsu> True.
[06:34] <Keybuk> fortunately I'm always happy
[06:34] <poningru> heeh
[06:34] <poningru> nes??
[06:35] <Fujitsu> infinity, you are.,
[06:35] <Hobbsee> Keybuk: dried frog pills? sounds like fun
[06:35] <infinity> poningru: No... "yes" is a binary that just outputs "y\n" forever until killed.  Handy to feed to scripts that want affirmative input.  I've done the above to feed negative input.
[06:35] <Keybuk> infinity: I've done s/y/something else/ before
[06:35] <Keybuk> but not /n/
[06:35] <jdub> it's the happy you have to watch out for
[06:36] <poningru> infinity: ah did not know that
[06:37] <infinity> What I really want is /usr/bin/guess that will semi-randomly output 'y' or 'n' on a whim, or perhaps based on time of day or mood.
[06:37] <Fujitsu> I like it.
[06:37] <Keybuk> /usr/bin/maybe ?
[06:37] <Fujitsu> yes with attitude.
[06:37] <HrdwrBoB> Usage: yes [STRING] ...
[06:38] <infinity> HrdwrBoB: Oh, don't ruin my fun.  I've never read the docs for yes.  Ever.
[06:38] <HrdwrBoB> heh
[06:38] <infinity> HrdwrBoB: Though I suppose we all learn something new every day.
[06:38] <HrdwrBoB> though TBH, it's like find|grep
[06:38] <HrdwrBoB> it's easier/quicker to find|grep
[06:38] <HrdwrBoB> than to mangle the damn find options
[06:38] <poningru> rofl
[06:39] <Fujitsu> Do we, infinity? You sure?
[06:39] <jdub> HrdwrBoB: or be told off by find for getting them the wrong way around...
[06:39] <infinity> Fujitsu: Well, I like to pretend I do, I can't speak for everyone, I guess.
[06:39] <Fujitsu> Haha.
[06:39] <HrdwrBoB> jdub: yeah, because if you can detect something is not ordered correctly, the correct course of action is to tell the user he/she's an idiot
[06:39] <Fujitsu> Of course.
[06:40] <HrdwrBoB> (and then fail)
[06:40] <infinity> It doesn't fail, it just carries on.
[06:40] <jdub> i'm waiting for
[06:40] <jdub> find: warning: WHATCHOOTALKIN'BOUTWILLIS?
[06:40] <Fujitsu> I think we need to modify all CLI applications to simply output RTFM\n when bad syntax is provided.
[06:40] <Hobbsee> haha
[06:40] <Hobbsee> that could be fun
[06:43] <Keybuk> jdub: indeed, I never knew that you'd previously been a woman
[07:15] <bluefoxicy> what
[07:16] <bluefoxicy> infinity:  yes n
[07:18] <bluefoxicy> infinity:  'yes bitch' works too
[07:23] <imbrandon> bluefoxicy: look man we all adults and we all have heard "adult" language but from you IMHO its take to extreemes a bit, can you try to tone it down a notch over all here in -devel ? not trying to start a flame , infact no direct response at all would be ideal but if you fell the need you are welcome to PM me. Just my 0.2c
[07:48] <mneptok> arr!
[08:06] <pitti> Good morning
[08:07] <ajmitch> morning pitti
[08:08] <Hobbsee> hi pitti
[08:08] <pitti> hey ajmitch
[08:08] <pitti> moin Hobbsee
[08:56] <tepsipakki> hi there. Who could rebuild debian-installer for edgy? It would just need to pick up new versions of the udebs
[08:58] <tepsipakki> ..because libnss-dns-udeb is fixed now
[08:58] <Hobbsee> tepsipakki: any core dev should be able to do that
[08:59] <tepsipakki> hobbsee: you ain't one, yet?-)
[08:59] <Hobbsee> tepsipakki: they denied me :P
[08:59] <tepsipakki> hobbsee: damn! :)
[09:00] <Hobbsee> tepsipakki: yeah, darn.  hasnt been *that* much of a problem, cos i've been concentrating on uni, and universe
[09:02] <tepsipakki> It'll come, eventually ;)
[09:04] <tepsipakki> ..membership, that is
[09:11] <Hobbsee> tepsipakki: got membership.  in fact, i get to approve other people's membership :P  core is the issue
[09:13] <tepsipakki> hobbsee: ah yes, I got confused.. by "membership" I meant core :)
[09:13] <tepsipakki> heck, I'm a member as well
[09:14] <Hobbsee> tepsipakki: yes, iirc you had memberhsip at the same time as me
[09:14] <tepsipakki> yes :)
[09:14] <doko> cprov-ZzZ, infinity: does soyuz have difficulties picking up new uploads?
[09:18] <infinity> doko: What are you missing?
[09:20] <doko> infinity: gcc-snapshot
[09:26] <doko> infinity: java-gcj-compat on amd64
[09:29] <infinity> doko: FTBFS.
[09:30] <infinity> doko: gcc-snapshot is just taking a while cause it's a universe package, and way back in the give-back queue.
[09:31] <Keybuk> quest upstart% ./client -p 26881 trigger startup ping (start) starting, process 29326 active
[09:31] <Keybuk> script (start) starting, process none
[09:31] <Keybuk> script (start) running, process 29327 active
[09:31] <Keybuk> startup event triggered
[09:31] <doko> thanks
[09:31] <Keybuk> \o/
[09:31] <Hobbsee> infinity: you're rebuilding an architecture?  :P
[09:31] <doko> Keybuk: got my mail about zope, CC'ed to Fabio?
[09:32] <Keybuk> doko: yeah, but I didn't understand it
[09:32] <Keybuk> you seemed to answer your own question *shrug*
[09:33] <doko> ?
[09:34] <Keybuk> how can you use bzr for Debian and Ubuntu when they freeze at different times ...
[09:34] <Keybuk> ... use two branches
[09:34] <Keybuk> call one "debian" and the other "ubuntu"
[09:35] <doko> Keybuk: right, can we do that using the LP repository? technically: yes, is it wanted?
[09:35] <Keybuk> yes, yes
[09:36] <Keybuk> the LP repository is just a place to mirror it
[09:36] <Keybuk> or store it
[09:39] <doko> ok, thanks
[09:39] <pitti> mvo: ok, so I fixed the Depends: parsing bug after all, since it also breaks caudium
[09:40] <mvo> pitti: ah, nice!
[09:40] <kagou> who do i ask for daily iso builds ?
[09:41] <doko> infinity: gnat-4.1 needs manual intervention, will query you
[09:43] <pitti> TheMuso: ok, pkg-create-dbgsym 0.11 uploaded; as soon as it's in the archive, caudium can be given-back
[09:45] <infinity> doko: Mmkay.
[09:46] <infinity> pitti: And by "given-back", you mean "removed from the archive", right?
[09:47] <pitti> infinity: well, TheMuso just pointed me to http://librarian.launchpad.net/3915685/buildlog_ubuntu-edgy-i386.caudium_2%3A1.4.7-14.1_FAILEDTOBUILD.txt.gz
[09:47] <pitti> infinity: personally I don't care for caudium itself :)
[09:55] <pitti> shawarma: ping
[09:55] <pitti> shawarma: can you please merge asterisk again to pick up the security fix?
[09:59] <tepsipakki> so, could some core-dev rebuild debian-installer for edgy?
[10:11] <infinity> tepsipakki: Kamion tends to prefer to be the only person who uploads d-i, but I suppose I could make an exception, given that he's off...
[10:13] <tepsipakki> infinity: thanks :)
[10:14] <tepsipakki> infinity: I think there's no harm in uploading it.. the current version is broken anyway
[10:16] <infinity> tepsipakki: Yeah, I know.
[10:16] <infinity> tepsipakki: I broke it.  I should know. :)
[10:16] <infinity> tepsipakki: I was counting on Colin doing a d-i upload before he took off on his vacation, but that didn't happen, s'all.  *shrug*
[10:20] <Kaleo> mvo: anacron have a quite old change pending; see bug 36816
[10:20] <Ubugtu> Malone bug 36816 in anacron "Anacron doesn't work with suspend/hibernation" [High,Confirmed]  https://launchpad.net/bugs/36816
[10:21] <Kaleo> -have+has
[10:21] <tepsipakki> infinity: :) I'll look forward to testing it today.. maybe I'll finally reinstall my laptop with edgy, too
[10:29] <mvo> Kaleo: from what I see this needs to be added to acpi-support
[10:30] <mvo> Kaleo: hm, maybe not ...
[10:33] <mdke> mvo: do you have access to fix bugs in dapper-commercial?
[10:39] <TheMuso> I'm wondering if anybody would be able to help me fix up a problem I am having with a universe merge. More specifically, the package fails to build on powerpc, whereas it succeeds on i386.
[10:39] <TheMuso> The build log is http://www.themuso.id.au/ubuntu/xawtv-powerpc-build.log
[10:40] <TheMuso> I recently did a merge for this package, which was uploaded. The package failed to build on ia64 and powerpc, but build alright on the other arches.
[10:40] <TheMuso> There is now an updated merge, and since this problem still persists in the new version, I would like to include a fix to make it build successfully on all arches before I upload the merge.
[10:40] <mvo> mdke: I should have, yes
[10:41] <pitti> TheMuso: hmm, error: 'PAGE_MASK' undeclared could be a difference in l-kernel-headers?
[10:42] <mdke> mvo: the slight problem is that I don't think bug reports are going to the right place. Take "realplayer" for example... it is getting reported on realplayer, but I think that refers to the package in multiverse.  bug 52484 would be a 30 second fix, but I don't think people who can work on dapper-commercial have got bug mail about it
[10:42] <Ubugtu> Malone bug 52484 in realplayer "Realplayer is in Graphics submenu, not Sound & Video." [Untriaged,Confirmed]  https://launchpad.net/bugs/52484
[10:42] <TheMuso> pitti: Not sure. The build chroots showed the same problem when the original merge was uploaded.
[10:42] <TheMuso> I hadn't thought of checking on ppc at the time, as it built on i386, and a MOTU confirmed that as well.
[10:45] <mvo> mdke: I fixed this in my latest upload
[10:45] <mvo> mdke: its not gone accepted yet though
[10:45] <mdke> mvo: cool, good news. what do you think about the issue of reporting bugs on dapper-commercial packages?
[10:46] <mvo> mdke: maybe we could add a tag for those? or create a group? I guess a group is the better choice
[10:46] <mdke> mvo: but do the packages exist for bugs to be filed on distros/ubuntu?
[10:47] <mdke> distros/ubuntu/+source/opera doesn't exist, nor does /realplay
[10:47] <stub> Launchpad is going down in 15 mins for its regular code update. Estimated downtime is under 10 minutes.
[10:48] <mvo> mdke: hm, right
[10:51] <TheMuso> Ok, it seems that powerpc doesn't have/use asm/page.h. For powerpc, it is only a stub, so I need the help of someone who understands the differences between powerpc and i386 framebuffer as well as the headers to work this one out.
[10:53] <mdke> mvo: I guess LP isn't used for dapper commercial?
[10:53] <mdke> s/LP/soyuz
[10:53] <mvo> mdke: correct
[10:54] <mdke> ah
[10:58] <jamesh> infinity: it's as if you've never read a UNIX text book.
[10:59] <jamesh> infinity: gar.  was in scroll back with you talking about arguments to "yes"
[10:59] <jamesh> ignore me
[11:07] <pygi> pitti, poke again :)
[11:07] <pitti> hey pygi
[11:07] <pygi> hey hey pitti
[11:07] <pygi> I would have questions again :)
[11:08] <pygi> why would I get "/usr/include/libburn/0/libburn/" instead of normal "usr/include/libburn/libburn/"?
[11:09] <pitti> pygi: I don't know, broken build system?
[11:09] <pitti> pygi: also, i/libburn0/ might be more appropriate
[11:09] <pitti> pygi: well, usually one API is enough at a time, so /usr/include/libburn/ sounds sufficient as well
[11:09] <pygi> pitti, broken build system yes, I  just don't know which part ^_^
[11:10] <pitti> pygi: some Makefile.am part probably, but I know little about autofoo
[11:11] <pygi> pitti, ahm,oki, will explore
[11:11] <pygi> pitti, you wanna test libburn by burning iso file?:)
[11:11] <pitti> I'll probably do it that way, sure
[11:12] <pygi> you can already do so, if you are willing
[11:12] <pitti> pygi: not right now, but maybe this afternoon? maybe you can mail me a link and some short instructions
[11:12] <pitti> ?
[11:12] <pygi> pitti, sure
[11:14] <pygi> thanks for the help
[11:18] <pygi> pitti, ah, weird me :)
[11:18] <pygi> libincludedir=$(includedir)/libburn/@BURN_MAJOR_VERSION@/libburn
[11:18] <pitti> ah, there you go
[11:18] <pygi> should I add minor version, or there is no need to have two api's at a time?
[11:18] <pitti> pygi: well, as long as the package has a pkgconfig file which matches that path, it doesn't matter so much, but it is still ugly
[11:19] <pygi> pkgconfigdir=$(libdir)/pkgconfig
[11:19] <pitti> pygi: why not simply remove the slash, then packagers have the freedom to support multiple APIs at a time
[11:19] <pygi> you mean leave it at "$(includedir)/libburn"?
[11:20] <pitti> no, libincludedir=$(includedir)/libburn@BURN_MAJOR_VERSION@/libburn
[11:20] <pitti> pygi: ^ if packages are supposed to #include <libburn/foo.h> instead of #include <foo.h>
[11:22] <pygi> right, I'll try and see :)
[11:22] <pitti> well, you have to decide that (or look what packages do which already use libburn)
[11:23] <mvo> bug #56125
[11:23] <Ubugtu> Malone bug 56125 in apt "doesnt look like a cow" [Unknown,Unconfirmed]  https://launchpad.net/bugs/56125
[11:25] <ajmitch> mvo: looks critical
[11:25] <mvo> ajmitch: yeah. I think we need to make it at lesat "important"
[11:26] <pitti> mvo: the proposed one looks really better, though
[12:21] <mvo> I would like to de-brand update-notifiers "ubuntu cd detected". any suggestions for a new (more neutral) string? "Distribution CD detected"? "Packages CD detected" "CD with packages detected"?
[12:26] <seb128> mvo: I don't really like those but I've no better suggestion
[12:27] <seb128> mvo: is one extra string to translate for Debian really an issue?
[12:27] <seb128> mvo: because the CD is not a random distribution one, it's an Ubuntu one ...
[12:27] <mvo> not a big issue for debian, but for any derrived distro
[12:27] <mvo> that is true
[12:27] <seb128> you consider it as a "big issue" for any derrived distro?
[12:28] <mvo> not really a big issue
[12:28] <mvo> more a "nice-to-have"
[12:28] <seb128> ah k
[12:28] <seb128> right
[12:28] <seb128> thinking about it
[12:28] <seb128> but I think it's not easy to not mention that's an Ubuntu CD
[12:45] <madduck> Keybuk: i'd love to know what e.g. initctl does that daemontools does not, or what initctl is in the first place, what the plans are, etc.
[12:45] <madduck> Keybuk: google doesn't really reveal much, so maybe you would update your blog?
[12:46] <Keybuk> initctl is just a control client for upstart
[12:46] <madduck> it looks fancy
[12:46] <Keybuk> upstart is an init replacement somewhere between launchd and init-ng, turning left at smf
[12:47] <madduck> so one more thing we'll be discussing in cambridge. :)
[12:47] <Keybuk> it's written from the point of view of "this is what we NEED" rather than "this is what users think we need to make their machine boot 0.2s faster"
[12:47] <madduck> .oO(do i sense irony?) :^>
[12:48] <Keybuk> the quick summary is that it's an event-based init daemon
[12:48] <Keybuk> tasks and services are started by events
[12:48] <Keybuk> and themselves cause events to occur
[12:48] <madduck> so dependencies are handled?
[12:48] <Keybuk> events include "startup", "writable-filesystem", "default-route up", etc.
[12:49] <madduck> note that i see the point of initscripts-ng not in being a faster bootup, but simply the proper support of dependencies
[12:49] <Keybuk> the problem with tools to reorder the static initscripts is that they don't actually solve any new problems
[12:49] <Keybuk> they just take a bit of problem away from the distribution maintainers
[12:49] <madduck> yeah
[12:49] <madduck> which, in Debian, is a good thing. since we're less about distribution-wide coordination than Ubuntu
[12:50] <Keybuk> they still don't cope with "what happens if the user plugs a USB hard drisk in at *this* point"
[12:51] <madduck> ah, so you'll replace udev on the way? ;)
[12:51] <Keybuk> no reason to replace udev
[12:51] <Keybuk> udev works perfectly
[12:51] <Keybuk> there will be a udev rule to provide a source of events for upstart
[12:51] <pitti> hi Keybuk
[12:52] <madduck> Keybuk: sounds reasonable? and this will be available to Debian too, I assume?
[12:52] <Keybuk> of course
[12:52] <madduck> sweet
[12:54] <Keybuk> I vainly hope that everyone will adopt it <g>
[12:56] <madduck> Keybuk: you'll have to convince me in person. :)
[12:59] <Keybuk> :D
[01:01] <jono> hey
[01:03] <Keybuk> hey Mr O'Bacon!
[01:03] <jono> heya Keybuk :)
[01:03] <Zdra> hi, will glade3 be part of edgy ?
[01:03] <jono> Zdra, I was gonna ask the same question :)
[01:05] <Zdra> everybody speaks about glade3 those days
[01:06] <seb128> Zdra: I've planned to look at it today
[01:07] <seb128> Zdra: I've played with the 2.9n package some days ago
[01:07] <seb128> I'm not sure if it's supposed to be good enough to replace glade-2
[01:07] <seb128> or if it should be a separate package
[01:07] <seb128> opinions on the topic are welcome ;)
[01:09] <Zdra> seb128: is it easy to build the program for testing ?
[01:09] <TheMuso> c
[01:09] <Zdra> buildep are in edgy ?
[01:10] <seb128> Zdra: you know how to build a package?
[01:10] <seb128> Zdra: yep, just take the src package from debian experimental
[01:10] <Zdra> ok
[01:10] <seb128> Zdra: maybe dpkg -i the deb from debian work, I've not tried
[01:10] <seb128> Zdra: rebuilding it works fine on edgy
[01:11] <Zdra> seb128: thanks I'll try that this evening when i'm back at home
[01:11] <seb128> Zdra: np, let we know how it works for you ;)
[01:22] <TheMuso> c
[01:22] <TheMuso> curse it
[01:41] <ogra> pitti, i have a very intresting gnome-vfs effect here
[01:41] <seb128> ogra: "gnome-vfs effect"?
[01:41] <ogra> if i mount /tmp/.ogra2-ltspfs/cdrom (without bind mounting) it gets picked up as /cdrom by nautilus
[01:41] <ogra> seb128, yes
[01:42] <rodarvus> doko, is the removal of libssp0 on latest gcc upgrade expected? (i.e., is it ok for me to proceed with upgrade?)
[01:42] <seb128> the question was to get a description of the "effect" :p
[01:43] <ogra> seb128, i have to moint --bind every other device i mount to fake a disk drive for nautils/gnome-vfs but if i call the mountpoint "cdrom" *anywhere* in the filesystem it gets picked up by nautilus
[01:43] <doko> rodarvus: yes, it's provided by glibc
[01:43] <seb128> ogra: ah, funny ;)
[01:44] <ogra> i spend half of my morning to find out why i always have 2 cdroms if i bind mount it additionally in /media/ogra/cdrom
[01:44] <rodarvus> doko, thanks
[01:45] <ogra> does anyone from the distro team have a usb floppy drive he could bring to the sprint ?
[01:46] <ogra> btw, do we have a hardware list like last time ? would be handy i think
[01:48] <Keybuk> with air travel such as it is as the moment, do you think it's entirely wise for people to bring exotic hardware? :)
[01:50] <ogra> hmm, right
[01:51] <ogra> i forgot about that ...
[01:51] <seb128> Keybuk: many people are not going to flight though
[01:51] <seb128> s/flight/fly
[01:51] <ogra> i think a good third is
[01:51] <seb128> which means most of people are not flying :p
[01:52] <ogra> right :)
[01:53] <infinity> Keybuk: You're expecting people to bring liquid hardware?
[01:53] <ogra> seb128, is there a way to suppress the eject itme in nautilus context menu ?
[01:53] <ogra> *item
[01:53] <seb128> ogra: patch the source package
[01:53] <seb128> ogra: no runtime option no
[01:53] <ogra> hmm, k
[01:54] <Keybuk> infinity: my AMD64 is liquid cooled ;)
[01:54] <Keybuk> and it's luminous green in colour
[01:54] <thom> Keybuk: then you deserve everything you get ;-)
[01:54] <infinity> Just like all that glowing green nitro-- wait...
[01:55] <Keybuk> thom: *shrug* it's about a zillion times quieter than fans
[01:57] <pitti> ogra: g-vfs> that must be special-cased
[01:57] <thom> i more meant the luminous green, but anyway :-)
[02:02] <ogra> pitti, ltspfs on /tmp/.ogra2-ltspfs/cdrom type fuse (rw,nosuid,nodev,user=ogra2)
[02:03] <ogra> pitti, thats the only cdrom i have mounted :)
[02:03] <ogra> but it shows fine in the drivelist and on the desktop
[02:05] <ogra> i wonder if it starts to enumerate them or something ...
[02:05] <ogra> its not unusual that you have 20 active users on a ltsp server
[02:05] <StevenK> Keybuk: My AMD64 is a shuttle based system, and has one fan which is whisper quiet.
[02:06] <thom> StevenK: i don't think you can fit SLI in a shuttle ;-)
[02:07] <StevenK> Yes, I doubt it.
[02:07] <Keybuk> StevenK: how long does it take to compile open office?
[02:07] <StevenK> I've never tried, actually.
[02:08] <Keybuk> it's a fun benchmark
[02:08] <StevenK> I've re-encoded video, if that can give you an idea.
[02:08] <thom> moz or OOo are probably the best benchmarks
[02:10] <Keybuk> didn't actually time any of the re-encodings I was doing on here :-/
[02:10] <Keybuk> it's about 5 minutes an episode I think
[02:10] <Keybuk> maybe a bit more
[02:11] <StevenK> My AMD64 is wimpy, it's 40 minutes to go from .avi to .vob
[02:11] <zul> at least you have one
[02:14] <StevenK> http://en.wikipedia.org/wiki/GeForce_7_Series#GeForce_7950_GX2
[02:14] <StevenK> There we go, SLI in a shuttle. :-P
[02:15] <tseng> StevenK: so you can run glxgears really really fast?
[02:15] <StevenK> At the moment, my AMD64 doesn't have 3D.
[02:15] <StevenK> This will change very soon.
[02:15] <ajmitch> StevenK: you're not missing much
[02:15] <Keybuk> tseng: it's great for blasting monsters into kibbles
[02:34] <tepsipakki> infinity: thanks for the d-i upload, it works like a charm now
[02:34] <\sh> moins
[02:36] <infinity> tepsipakki: Cheers,
[02:39] <tepsipakki> ..only to fail with usplash
[02:39] <tepsipakki> ->lp
[02:41] <infinity> tepsipakki: usplash failing to configure?
[02:41] <tepsipakki> yes
[02:41] <infinity> tepsipakki: No proc/fd/whatever?
[02:41] <tepsipakki> yep
[02:41] <infinity> tepsipakki: I'll give you a shiny nickel to rewrite that line in the postinst to make it work. :)
[02:42] <tepsipakki> hm, haven't seen it yet.. i guess it's ugly?-)
[02:43] <infinity> Not particularly, I'm just not sure why it doesn't work on some arches, and does on others.
[02:43] <infinity> Baffling to me.
[02:43] <infinity> The powerpc buildd doesn't trip on it, amd64 and i386 do.
[02:43] <infinity> Local tests can't reproduce it.
[02:43] <tepsipakki> it's lookin for /dev/fd/62 on my T23
[02:43] <infinity>           IFS="x," read x y garbage < <(echo "$RET")
[02:44] <infinity> (Note that RET="640x480, random junk" at this point)
[02:44] <infinity> End goal is to populate x=640, y=480
[02:44] <Riddell> ogra, mvo: both your hwdb-client bzr archives are out of date compared to the edgy package
[02:50] <tepsipakki> infinity: here xserver-xorg/config/display/modes is preseeded, shouldn't it skip the IFS part if db_get fails?
[02:50] <infinity> tepsipakki: It should, so it's obviously not failing.  Why would it?
[02:50] <infinity> tepsipakki: If it's pre-seeded, I'd expect it to, y'know, have a value.
[02:51] <infinity> (hence, not fail)
[02:51] <tepsipakki> so the input is wrong, no?
[02:53] <infinity> Not sure I'm following you.
[02:53] <infinity> The /dev/fd/62 thins is all becaus of that sketchy redirect.
[02:53] <infinity> Probably just saner to rewrite it to split the string using something other than IFS and read.
[02:53] <tepsipakki> here the preseeded value is "1920x1200, 1600x1200, 1400x1050, 1280x1024, 800x600, 640x480", because of the different monitors around
[02:54] <infinity> Right, which should give you x=1920; y=1200
[02:54] <infinity> Try it on the command line.  It'll work fine.
[02:54] <tepsipakki> but it's wrong on this laptop =)
[02:55] <infinity> (base)adconrad@cthulhu:~$ IFS="x," read x y garbage < <(echo "1920x1200, 1600x1200, 1400x1050, 1280x1024, 800x600, 640x480")
[02:55] <pitti> iwj: do you see any efforts to port the firefox <IP_ADDRESS> vulnerabilities to 1.0.x on that mailing list?
[02:55] <infinity> (base)adconrad@cthulhu:~$ echo $x
[02:55] <infinity> 1920
[02:55] <infinity> (base)adconrad@cthulhu:~$ echo $y
[02:55] <infinity> 1200
[02:55] <tepsipakki> you see, it's simpler to preseed that to the xserver, but upslash should use something more robust maybe?
[02:55] <infinity> tepsipakki: The fact that it's wrong is the fault of your presseed, but that's not what's breaking the postinst.
[02:56] <tepsipakki> why can't it have a template of it's own?
[02:56] <mjg59> Where would it get the information from?
[02:56] <tepsipakki> hmm
[02:57] <tepsipakki> is xserver-xorg configured before?
[02:57] <tepsipakki> before usplash..
[02:57] <mjg59> It's not guaranteed to be
[02:57] <infinity> mjg59: Oh, hey, you're not supposed to be here.
[02:57] <mjg59> Yeah, I don't have time to do the flies today now
[02:57] <infinity> mjg59: Come up with a better way to parse that without the redirect.  It's breaking in the livefs builds, which sucks.
[02:57] <mjg59> Not supposed to be in the lab out of hours
[02:58] <mjg59> Oh man
[02:58] <mjg59> Why don't they have /proc mounted?
[02:58] <infinity> They do.
[02:58] <mjg59> Then why does it break?
[02:58] <iwj> pitti: No, I'm afraid not.
[02:58] <infinity> Might be missing /dev/fd/whatever, I guess.
[02:58] <infinity> I haven't poked into it deeply.
[02:58] <mjg59> I guess in that case it'll just have to be other tools
[02:58] <infinity> But it breaks on debootstrapping any new chroot.
[02:58] <mjg59> X debconf nightmare
[02:59] <mjg59> infinity: Fancy hacking something up with awk?
[03:00] <infinity> Boy, do I ever.
[03:03] <tepsipakki> ok, I'll fix my preseed-templates to preseed values that are actually usable on the target computer :)
[03:03] <sladen> infinity: aren't /dev/fd/* symlinks to /proc/self/fd/* ?
[03:04] <infinity> sladen: Or something like that, yeah.
[03:04] <infinity> sladen: No idea why it's not working in a fresh debootstrap, I haven't had the time to look at it.
[03:04] <infinity> (nor why it works on powerpc, but not i386 and amd64)
[03:05] <\sh> ok...I have a serious problem with our grub package and a smartarray p600 sas controller...grub installs itself onto the /dev/cciss/c0d0 device, but when it should start, it gives us "GRUB Hard Disk Error"....with sles9 grub-0.94 without any cciss raid patches it works
[03:08] <\sh> (dapper that is)
[03:09] <sladen> \sh: if linux doesn't know what it is, the BIOS emulation will probably provide a good enough device to boot off;  what is grub set to boot off?
[03:12] <\sh> sladen: linux knows about the smartarray controller...grub is configured to be installed in MBR (/dev/cciss/c0d0 aka hd0), /boot partition is (/dev/cciss/c0d0p1 aka hd0,0)
[03:12] <\sh> sladen: strange thing is, in our grub package we have cciss_raid patches, but in sles9 they don't have any patches, but this 0.94 version works
[03:15] <sladen> \sh: I don't understand, why would you have patches to grub.  grub (TTBOMK) would just be using the int 13 bios services
[03:15] <sladen> \sh: if grub has any patches, is grub configured to know to be setup up differently such that is uses them?
[03:17] <\sh> sladen: the patches are for (as far as I read) for recognizing the different notation of the partitions ... (/dev/cciss/c\d+d\d+p\d+ instead of /deV/[h,s] d[a-z] \d+
[03:17] <infinity> mjg59: PS, that was wine-induced sarcasm.
[03:22] <infinity> mjg59: What are the rules with abusing stdout in a debconf-using postinst?  Okay, as long as it's all redirected and captured, right?
[03:23] <Russel> hiho, i hope this is the right channel
[03:23] <mjg59> infinity: Should be
[03:24] <Russel> i wanted to suggest, to the package, which provides cp, that it should include the patch which enables cp -g ("grafical" informations about transfer)
[03:26] <Hobbsee> hey, if i revoke my old key, and create a new key, and add it to LP, what happens with regarding uploading packages?
[03:26] <Hobbsee> (key = gpg key)
[03:27] <fabbione> Hobbsee: you want to ask in LP for that.
[03:27] <Hobbsee> fabbione: right.  hello, btw
[03:27] <fabbione> but probably once you revoke the old one, the new one should be recognized
[03:28] <fabbione> i dunno if LP performs checks on key signs and stuff like that
[03:28] <tepsipakki> russel: file a wishlist bug against coreutils on launchpad.net
[03:28] <fabbione> hello :)
[03:30] <Hobbsee> fabbione: yeah, i could get it resigned fairly easily, that's not much of a problem
[03:31] <fabbione> Hobbsee: but do you actually have any reason to revoke the old key?
[03:31] <Russel> tepsipakki: thx
[03:32] <Hobbsee> fabbione: sort of
[03:34] <fabbione> Hobbsee: well if it is an urgent reason i suggest to revoke the old key immediatly (get your upload sponsored) and get the new one signed and uploaded to LP
[03:34] <fabbione> urgent as in compromised or something
[03:35] <Hobbsee> fabbione: it's not really urgent, as in, it's not exactly compromised.
[03:35] <fabbione> did you upload the private key to a key server?
[03:35] <Hobbsee> but it probably shouldnt stay the way it is
[03:35] <Hobbsee> the new one?  i havent even revoked the old one yet
[03:36] <fabbione> did you upload the private key to a key server? <- old key ;)
[03:36] <Hobbsee> dont know :P  i followed the guide on it on the wiki
[03:36] <fabbione> ok :)
[03:39] <Hobbsee> fabbione: so what's the answer then?  :P
[03:41] <fabbione> Hobbsee: if i was you and suspected comprimise, i would revoke my key immediatly
[03:41] <fabbione> and figure out later how to get the new one in
[03:41] <fabbione> remember that uploads with your key gives away root on all people machine installing your packages
[03:41] <Hobbsee> fabbione: it's not suspected comprimise per se.  it's not something that should stay that way though
[03:42] <fabbione> well if you are not more specific, i can't be more specific
[03:42] <rodarvus> Hobbsee, adding a new gpg key to your launchpad account is quite painless
[03:42] <Hobbsee> rodarvus: yes, but does it get recognised with the keyring?
[03:42] <rodarvus> create you new gpg key, upload it to a keyserver, wait about 5-10 minutes for the key to be mirrored
[03:42] <rodarvus> sign the CoC with your new key, upload the signed gpg key to launchpad
[03:43] <Hobbsee> right, okay
[03:43] <rodarvus> Hobbsee, yes, as soon as the new key is uploaded you can start using it
[03:43] <StevenK> rodarvus: Does the key need to be signed, though?
[03:44] <rodarvus> by someone else? no.
[03:44] <StevenK> It usually helps, though.
[03:44] <rodarvus> would be nice, though
[03:44] <rodarvus> (I mean, it won't stop you from uploading)
[03:47] <sladen> Russel: http://launchpad.net/distros/ubuntu/+source/coreutils/+filebug priority "Wishlist"
[03:52] <pitti> hi sbalneav
[03:53] <sbalneav> Hey pitti!!
[03:53] <sbalneav> Gonna finish off on the mounter today, address your points.  We're already testing functionality, so that part's working.  Thanks for the help
[03:53] <infinity> Ugh, we have no WoT requirements for the archive anymore?  This is obvious, if I think about it, but I never thought about it.
[03:53] <StevenK> pitti: Can I ask about the rails security update? Or is rails universe and you don't really look after it.
[03:53] <sbalneav> Morning Hobbsee
[03:54] <Hobbsee> infinity: WoT?
[03:54] <infinity> Now uploading is tied to people (quite likely) weak passwords in LP...
[03:54] <StevenK> Web of Trust
[03:54] <infinity> Hobbsee: Web of Trust.
[03:54] <Hobbsee> infinity: ahh...right...of course
[03:55] <infinity> Yay, paranoia.
[03:55] <Hobbsee> hah. yeah
[03:55] <pitti> hi StevenK
[03:55] <pitti> StevenK: there's a bug about it, but right, it's universe, so I don't feel a particular urge for it
[03:55] <pitti> StevenK: and it's fixed in edgy
[03:56] <StevenK> I could fix it for Dapper.
[03:56] <pitti> StevenK: that would be nice
[03:57] <StevenK> pitti: I'll apply the patch to 1.1.2, but what version should I set it to?
[03:57] <pitti> StevenK: https://wiki.ubuntu.com/SecurityUpdateProcedures has some hints about it
[03:57] <pitti> StevenK: short from: increase by 0.1 ubuntus
[03:58] <tepsipakki> infinity: I see that you uploaded a new usplash but something is keeping it from the buildd?
[03:58] <infinity> tepsipakki: Patience.
[03:59] <infinity> tepsipakki: I uploaded it 30 mins ago, the publisher runs at :03
[03:59] <tepsipakki> =)
[03:59] <infinity> tepsipakki: The source will be in the archive after this publisher run, it'll build around :45, then get published on the next :03.. Ish.
[03:59] <Hobbsee> yay.  launchpad is timing out over my number of packages uploaded.
[04:00] <Hobbsee> maybe that's telling me something :P
[04:00] <infinity> Hobbsee: It's telling you that you're l33t.
[04:00] <tepsipakki> infinity: but.. that means testing it will have to wait for tomorrow :)
[04:00] <infinity> Hobbsee: Or that your LP account has been compromised and someone else is uploading as you. :P
[04:00] <StevenK> pitti: I'd suggest edgy is updated to 1.1.6-1
[04:00] <infinity> tepsipakki: OH NOES! :)
[04:00] <Hobbsee> infinity: or just that soyuz is busted again.
[04:00] <Hobbsee> imbrandon: true that
[04:00] <pitti> StevenK: it is already, I requested a sync some days ago
[04:00] <infinity> Hobbsee: Shh.  soyuz has no bugs, only inconvenient features.
[04:00] <StevenK> pitti: Ah
[04:00] <Hobbsee> infinity: haha, right.
[04:01] <Hobbsee> infinity: inconvenient, undocumented ones?
[04:01] <infinity> Hobbsee: Oh, they're documented, right here in #-devel.
[04:01] <thom> infinity: are you gonna get apache synced for edgy, btw?
[04:01] <Hobbsee> hah
[04:01] <thom> (1.3 i mean)
[04:01] <infinity> thom: Yeahp.  I can do that right now, actually.  Thanks for the reminder.
[04:01] <infinity> Of course, I'll miss this publisher run.  Oh well.
[04:02] <thom> oh well; as long as it done pitti will love us anyway
[04:02] <pitti> hey thom!
[04:08] <infinity> thom: Synced.
[04:08] <infinity> Or, would be if I uploaded the sync..
[04:10] <infinity> Done.
[04:10] <infinity> More wine.
[04:12] <StevenK> pitti: rails 1.1.2-1ubuntu0.1 is building locally.
[04:20] <StevenK> pitti: Create a new bug for the rails debdiff?
[04:21] <pitti> StevenK: let's create a dapper task for the existing one
[04:21] <pitti> StevenK: bug 55811
[04:21] <Ubugtu> Malone bug 55811 in rails "Mandatory security update" [Unknown,Fix released]  https://launchpad.net/bugs/55811
[04:22] <pitti> StevenK: I already created a dapper task
[04:23] <StevenK> Just add a comment with the debdiff?
[04:23] <pitti> StevenK: yes, please
[04:23] <pitti> StevenK: well, you can set dapper task to 'fix committed', too
[04:23] <pitti> I'll apply/upload it afterwards
[04:25] <StevenK> pitti: Both done.
[04:29] <pitti> StevenK: ugh, huge patch; I assume you tested this? :)
[04:29] <pitti> StevenK: thank you, I'll do the rest
[04:30] <StevenK> pitti: I'm just checking if the patch applied
[04:31] <pitti> StevenK: applied fine, package ready for upload
[04:32] <StevenK> pitti: Ah, I'm just unsure if the patch is applied at build time.
[04:32] <StevenK> In fact, I don't think it gets applied.
[04:32] <StevenK> pitti: Lemme dig.
[04:32] <pitti> StevenK: hm, dpatch without patches/00list?
[04:33] <StevenK> I saw that.
[04:33] <StevenK> It seemed a little strange.
[04:33] <pitti> StevenK: heh, debian/rules patch does not do anything...
[04:34] <pitti> haha
[04:34] <pitti> StevenK: the patches must be applied inline, too
[04:34] <StevenK> So we have all of these wonderful patches that don't get applied.
[04:34] <pitti> no, they are already applied
[04:34] <pitti> StevenK: check lsdiff -z package.diff.gz :)
[04:35] <pitti> just for some totally uncomprehensible reason the package does not have a 00list, but instead the maintainer applied them manually
[04:35] <pitti> Go Adam Majer
[04:35] <StevenK> Ewwwwwwwwwwwwwwwww
[04:35] <StevenK> pitti: Nice catch.
[04:36] <StevenK> pitti: Should I apply it and redo
[04:36] <StevenK> ?
[04:36] <pitti> StevenK: don't worry, I know how to patch -p0 :0
[04:36] <pitti> s/0$/)/
[04:36] <StevenK> That's ... sickening
[04:37] <pitti> StevenK: incidentially, the package of my last security update (krb5) is broken in exactly the same way
[04:37] <StevenK> pitti: I'm reminded of a certain Joel Klecker quote.
[04:37] <pitti> StevenK: can you please give this thing a light test? the patch is quite intrusive
[04:38] <pitti> and there's no compiler to catch obvious bugs :)
[04:39] <StevenK> pitti: Rebuilding to actually pick up the patch.
[04:40] <infinity> StevenK: Of which you are one...
[04:41] <pitti> they all suck, believe me :)
[04:41] <StevenK> Heh
[04:41] <StevenK> Given some of the crap I've uploaded, I'm willing to admit I suck.
[04:41] <StevenK> Linda 0.1.*, for starters.
[04:44] <StevenK> pitti: Right, with the patch applied, it builds, installs and I can run the built-in server with a rails app.
[04:44] <pitti> StevenK: cool
[04:45] <StevenK> pitti: Excellent, thanks.
[04:57] <BenC> oh sweetness!!
[04:57] <BenC> someone changed the comment font in lp to a monospace font
[04:58] <pitti> yep, finally no unreadable program output any more
[05:00] <ogra> pitti, do you think the cdrom stuff i see is a bug ? (i'd assume so) else i'll need to handle cdroms differently in the ltspmounter scripts
[05:00] <pitti> ogra: I'm not sure why it is special-cased in gnome-vfs
[05:00] <pitti> however, it shouldn't actually be necessary any more these days
[05:00] <ogra> it really ony seems to take effect if the mountpoint is called cdrom ...
[05:01] <pitti> maybe it's a forgotten workaround from the pre-hal time
[05:02] <ogra> well, theer seem to be also some hardcoded things ... if i mount anything to /media/ogra/floppy, it will get a floppy icon
[05:07] <Keybuk> oh, wow, my computer goes so much faster without a dozen "yes" processes run
[05:15] <Riddell> ogra: http://kubuntu.org/~jriddell/bzr/hwdb/
[05:15] <Riddell> ogra: http://kubuntu.org/~jriddell/hwdb/
[05:44] <aigarius> jordi: hi, I uploaded the po files for sbackup
[05:45] <jordi> aigarius: great!
[05:45] <jordi> I'll process
[05:45] <jordi> wow, you already have translations?
[05:48] <jordi> aigarius: approved. It'll take some minutes to appear
[05:48] <aigarius> thanks!
[05:53] <aigarius> jordi: is it normal that the language show up with no messages at this point? will the messages show up a bit later?
[05:58] <aigarius> oh, I see them now
[06:06] <jordi> aigarius: yes, and ok :)
[06:15] <bddebian> Howdy
[06:17] <jordi> aigarius: btw, I spotted a typo in your screenshot
[06:18] <aigarius> I wish I had a penny everytime I heard that :D
[06:19] <aigarius> maybe it is worth making a translation to en? (from the original Engrish)
[06:23] <jordi> aigarius: no, just fix the original in your next release
[06:23] <jordi> aigarius: "I guess the path you entered does not exists. Do you want to add this wrong path?"
[06:23] <jordi> I would s/I guess/It seems/
[06:23] <aigarius> jordi: yes, I know, but I am thinking big :)
[06:24] <aigarius> thanks, will fix it
[06:26] <jordi> aigarius: en translations are imho a bad idea normally
[06:26] <jordi> en_US/en_GB, etc are ok, but not en
[06:27] <jordi> "Do not backup files bigger then"
[06:27] <jordi> aigarius: ^  s/then/than
[06:27] <aigarius> that is my common mistake :)
[06:28] <jordi> and you should use "Do not backup files bigger then %d Mb" as just one string here
[06:29] <aigarius> there is an entry box in between :(
[06:29] <jordi> ugh
[06:29] <jordi> that's bad
[06:29] <aigarius> I should really read the Gnome HIG sometime :)
[06:39] <sbalneav> pitti: ping
[07:16] <pitti> sbalneav: pong
[10:30] <bluefoxicy> ouch
[10:30] <bluefoxicy> multi-gigabytes of swap in use
[10:37] <HiddenWolf> bluefoxicy: how could you, evolution is such a sweet little email app. :)
[10:37] <bluefoxicy> HiddenWolf:  it was eating over a gig of ram.
[10:37] <bluefoxicy> I closed firefox, thunderbird, and gaim for an extra 300 megs total.  I don't see wtf is eating 500M of memory.
[10:38] <HiddenWolf> top doesn't show?
[10:38] <bluefoxicy> I closed the 5 biggest apps on top o.o
[11:40] <icecrash> moin
[11:49] <lfittl> ogra: ping
[12:04] <cbx33> hi any python dbus gurus here?


[03:45] <pitti> desrt: I was, but there were two metric tons of rejections and some more problems, so I put that on the backburner; it's accepted upstream now, isn't it?
[03:45] <pitti> Trevinho: ah, that's right
[03:48] <pitti> Trevinho: I uploaded policykit-desktop-privileges_0.14.dsc to fix that, but it'll be stuck in unapproved until after beta-2
[04:46] <desrt> pitti: upstream did a different patch
[05:51] <BigWhale> Good Morning.
[05:55] <didrocks> hey BigWhale!
[06:09] <BigWhale> didrocks, hey. :)
[06:09] <BigWhale> Who do I go to if my go to Ubuntu upload guy is missing? :)
[06:11] <didrocks> BigWhale: patch pilot is working fine nowadays :)
[06:12] <didrocks> BigWhale: like the list was at ~14 items yesterday, directly pinging the patch pilot helps!
[06:12] <BigWhale> patch pilot?
[06:12] <didrocks> BigWhale: https://wiki.ubuntu.com/UbuntuDevelopment/CodeReviews
[06:13] <didrocks> BigWhale: you never noticed all those emails on the ubuntu-devel ML?
[06:13] <BigWhale> I am not really familiar with all the official channels. :/ I was just bugging ken. :>
[06:13] <didrocks> just go on #ubuntu-devel, follow the regular sponsorship process (see above, there are links ;)). If there is someone in /topic with patch pilot, you can in addition directly pings them!
[06:15] <BigWhale> Ok, thanks. :)
[06:16] <didrocks> yw ;)
[06:18] <BigWhale> hmmm... now I'm all confused. I just want Kazam which is now at 1.4.1 in Raring to get bumped to 1.4.2 :>
[06:19] <BigWhale> I'll ask around. :)
[06:50] <jibel> good morning
[06:50] <didrocks> salut jibel, ça va?
[06:50] <jibel> salut didrocks ! Ça va bien et toi ?
[06:52] <didrocks> jibel: ça va bien :)
[07:36] <ogra_> seb128, any objection to make the terminals recommends of u-desktop ?
[07:36] <ogra_> (they are hard deps atm)
[07:36] <seb128> ogra_, none to me
[07:36] <seb128> to->from
[07:36]  * ogra_ does it then
[07:37] <seb128> in practice all non-key-piece-of-infrastructure could be recommends
[07:37] <ogra_> hmm, or i'll better wait until beta is out
[07:37] <seb128> like there is no reason to force apps on users
[07:37] <seb128> well, commit to the seed so it gets in next time somebody refresh the package
[07:38] <ogra_> yep
[07:40] <pitti> hey seb128, bonjour
[07:40] <seb128> pitti, salut, ça va bien ?
[07:40] <pitti> seb128: oui, merci; et toi ?
[07:41] <seb128> pitti, très bien, merci ;-)
[09:11] <darkxst> pitti, hi
[09:12] <pitti> hello darkxst
[09:13] <darkxst> I think we should have a bunch of crash reports against packages with ddebs now
[09:14] <darkxst> bug 1163400
[11:13] <davmor2> hey guys I have an odd issue, all the album art from my u1 music isn't showing up in nautilus, rb or dash.  This is only for local music according to eyed3 the image is imbedded in the mp3 so I am wondering if it is something that nautilus is striping out some how?
[11:23] <davmor2> hey guys I have an odd issue, all the album art from my u1 music isn't showing up in nautilus, rb or dash.  This is only for local music according to eyed3 the image is imbedded in the mp3 so I am wondering if it is something that nautilus is striping out some how?
[11:24] <davmor2> sorry if that is a reapet I wasn't sure if it got through
[11:25] <seb128> it went
[11:25] <seb128> nautilus is not modifying any file so that's not it for sure
[11:26] <seb128> not sure how the artwork is embedded in the file, maybe gstreamer/whatever is handling that is having an issue with it
[11:31] <davmor2> seb128: thanks, eyed3 is listing it like this https://pastebin.canonical.com/88389/  I'm not sure why nautilus isn't showing  it though as far as I know it is in Quantal >  is displaying it just not in the latest raring, this was an install from Tuesdays iso
[11:32] <seb128> where was it displayed before? as thumbnail in nautilus?
[11:32] <seb128> can you open a bug with an example file attached?
[11:36] <davmor2> seb128: in ~/.ubuntuone/Purchased from Ubuntu One/<artist_name>/<album>/  the track.mp3 would show the album art
[11:37] <davmor2> seb128: I don't know if I can add a commercial purchased mp3 to a launchpad bug for legal reasons, I can possibly share one with you directly
[11:38] <seb128> can you test if the same file was showing previews in quantal (or precise)?
[11:38] <davmor2> seb128: I can when I get home
[11:39] <davmor2> seb128: I'm co-working today
[11:39] <seb128> k, let me know how that works
[11:40] <davmor2> seb128: no worries if it shows up in quantal and precise and not in raring I'll open up a bug.
[11:40] <seb128> thanks
[11:40] <seb128> if you open a bug maybe put a link to a temporary u1 link to download the song
[11:41] <seb128> or just share the link in private on IRC
[11:41] <seb128> but first I would need a better description of the issue
[11:41] <seb128> nautilus doesn't display thumbnails of mp3 with a covert art image here
[11:41] <seb128> but I'm not sure it ever did
[11:41] <seb128> the dash/rhythmbox show those though
[11:48] <davmor2> seb128: right I'll add a load of screenshot of what I see in raring in comparison to what I see  in Quantal/Precise too then.  Along with eyed3 info on tracks.
[13:05] <attente> hey seb128
[13:05] <attente> what version of g-c-c will be in S?
[13:05] <seb128> attente, hey
[13:05] <seb128> good question, I don't know yet
[13:05] <seb128> 3.8 if possible
[13:05] <seb128> but they "broke" quite some stuff for us
[13:06] <ogra_> i think its 3.7 now
[13:06] <seb128> like they statically link all their panels
[13:06] <ogra_> (i.e. what will be in the initial toolchain upload)
[13:06] <seb128> which makes harder to have external panels
[13:06] <ogra_> oh. lol
[13:06] <seb128> ogra_, gnome-control-center
[13:06] <seb128> ogra_, you are on #desktop, not  #toolchain ;-)
[13:06]  * ogra_ totally missed what channel he was in and even more missed the dashes
[13:06] <ogra_> yeah
[13:07] <attente> lol
[13:19] <rsacha> hi. can anybody tell me something about how the unity launcher retrieves the bookmark information displayed when right-klicking on the nautilus launcher icon?
[13:19] <didrocks> rsacha: it's from the .desktop file of the application for the static quicklists
[13:20] <didrocks> for nautilus, it's a dynamic one
[13:20] <didrocks> so it's the nautilus process which is exposing its bookmarks
[13:20] <rsacha> didrock: what a pity - i hoped it would fetch it from the .gtk-bookmarks file
[13:21] <seb128> it sort of does
[13:21] <seb128> through nautilus
[13:21] <seb128> nautilus reads that file
[13:21] <rsacha> seb128, i see.
[13:22] <didrocks> in adding to that, it's exposing the default ones, what .gtk-bookmarks wouldn't have
[13:22] <rsacha> background is that we use 12.04 in an ltsp environment and nautilus has to run on the appserver. when it runs on that appserver, no bookmarks are displayed in the nautilus launcher.
[13:23] <rsacha> is there any way to create a workaround for that scenario?
[13:23] <didrocks> I have no knowledge of LTSP, but if you can come with a patch with tests from someone knowing it, that would be great. I think it's a bigger issue with dynamic quicklist and LTSP though
[13:25] <rsacha> didrocks, i guess our setup: launcher=local and nautilus=remote is rather exotic and i wonder if it makes sense to create a patch for that :)
[13:26] <didrocks> rsacha: indeed, it's quite hackish ;) I doubt you will find a reliable workaround though :)
[13:28] <rsacha> didrocks, true. iw onder if it is possible to start a nautilus process locally in "hidden" mode - one that doesn't appear in the launcher and doesn't draw the desktop. that way, the launcher would retrieve the needed information for the remote nautilus from the local nautilus process
[13:29] <didrocks> rsacha: that's possible, if you click on the nautilus icon, you have a local version running?
[13:33] <rsacha> didrocks, no, we created /usr/local/bin/nautilus which is a script that runs "ltsp-remoteapps nautilus". so everytime we run nautilus it is started remotely. the only way to start it locally is to run /usr/bin/nautilus directly
[13:35] <didrocks> rsacha: you probably have issues with bamf matching I guess
[13:38] <rsacha> didrocks, uuh-ooh. bamf, never knew that something like that existed :)
[13:40] <didrocks> rsacha: right, taht's why I think the support isn't there nor really possible :)
[15:42] <desrt> seb128: hey... looks like my suspicion that we would have more breakage caused by my iface-after-init changes uncovered only after the stable release turned out to be true
[15:42] <seb128> desrt, gtkmm and mono?
[15:42] <desrt> seb128: some c++ and c# apps are broken as a result.  there is a workaround in glib that will be part of .1 but maybe you want to pick the changes in the meantime
[15:43] <seb128> desrt, will do, thanks
[15:43] <desrt> both camps agreed to try to have a 'real fix' by next cycle
[15:44] <seb128> you basically broke all the bindings but only pitti noticed and got pygobject fixed? ;-)
[15:44] <pitti> to be fair, desrt pointed out the breakage
[15:44] <pitti> I didn't have to discover by accident
[15:45] <pitti> although the test suite would have told me fairly quickly :)
[15:45] <desrt> seb128: problem is that neither gtkmm nor gtk# follow the unstable cycle
[15:45] <desrt> which is fine.... i expected that there would be people who didn't notice until now
[15:45] <desrt> that's why i made the change the way i did
[15:45] <desrt> easy to backout and/or add exceptions
[15:45] <seb128> right
[15:46] <seb128> that still makes me a bit uneasy
[15:46] <desrt> it ought to
[15:46] <desrt> it makes me uneasy too
[15:46] <desrt> but i'm pretty sure it's the right way
[15:46] <seb128> like are we going to find next that the java bindings have the same issue? ;-)
[15:46] <seb128> (not sure if anyone uses those)
[15:47] <desrt> i've stopped caring about supporting weird uses of glib in a 100% compatible way forever
[15:47] <desrt> it's far more realistic to be compatible for 99% of the apps out there and have good mechanisms for distros to deal with the 1% cases in a sane way
[15:58] <seb128> desrt, do you plan to commit those to https://git.gnome.org/browse/glib/log/?h=glib-2-36 as well?
[15:58] <desrt> oh.  right
[15:59] <desrt> thanks for the obvious reminder :p
[15:59] <seb128> yw ;-)
[15:59] <desrt> in fact, it's questionable that they should be on master at all
[15:59] <desrt> but i guess people running the development release may as well be without crashes for now :)
[15:59] <seb128> yeah, will make binding people happier I think
[15:59] <seb128> let them some time to fix their side
[16:00] <desrt> cherry-picked and pushed
[16:00] <seb128> thanks
[16:02] <apt-get_install> didrocks, there?
[16:03] <didrocks> hey apt-get_install!
[16:03] <didrocks> yep ;)
[16:03] <apt-get_install> hi
[16:03] <apt-get_install> Will I be able to compile and install programs from source on Ubuntu Touch? (didrocks)
[16:04] <didrocks> apt-get_install: sure, it's even already possible :)
[16:04]  * ogra_ wonders why you dont ask in #ubuntu-touch ;)
[16:04] <bhavesh> idk if my question is related to the topic, but I just wanted to know if Ubuntu touch works only for high end phones or even on phones with 1Ghz singe core processor and 512MB RAM?
[16:04] <didrocks> ogra_: we were after the hangout and we told people to come on #ubuntu-desktop for those still having questions
[16:04] <apt-get_install> didrocks: nice, thanks
[16:04] <didrocks> ogra_: it wasn't a touch show related :)
[16:04] <ogra_> didrocks, ah, cool
[16:05] <didrocks> ogra_: do you have the webpages for bhavesh with the low-end device and high-end device? (IIRC, there is one)
[16:05] <apt-get_install> and will Ubuntu Touch be rooted as deafult?
[16:05] <ogra_> you mean the ones that UTouch was ported to yet ?
[16:05] <ogra_> https://wiki.ubuntu.com/Touch/Devices
[16:05] <didrocks> bhavesh: ^
[16:06] <bhavesh> didrocks, ogra_ Thank you. <3
[16:06] <nikth> didrocks, how about an idea to run an image of Ubuntu for mobile on a PC TV stick such as .. Rikomagic ? Will that be possible at all ? worth to try it ? Thanks
[16:06] <didrocks> apt-get_install: yeah, for only touch question, we should migrate to #ubuntu-touch, but it's the kind of questions we don't know yet :)
[16:06] <apt-get_install> oh
[16:06] <ogra_> apt-get_install, the version you install on your own will ... versions on devices preinstalled by manufacturers will likely not (depends on the manufacturer)
[16:06] <apt-get_install> ah
[16:06] <apt-get_install> like android then?
[16:07] <ogra_> well, carriers and manufacturers often require that
[16:07] <apt-get_install> so, you must jailbreak it then
[16:07] <ogra_> but if we have a carrier device there will very likely be an ubuntu image you can install yourself on it
[16:07] <apt-get_install> I rather download and install it by my own
[16:07] <didrocks> nikth: there is a porting guide, if it's running android, it will be really easy (see https://wiki.ubuntu.com/Touch/Porting). For others, can be a little bit harder ;)
[16:08] <nikth> Yea didrocks  , for me (I have a RockChip) is little bit harder , is not so Linux friendly. The SoC is rooted by default but ... we'll see. Thanks for the link !
[16:09] <didrocks> nikth: yw! :-)
[16:36] <didrocks> mterry: I loose faith in humanity understanding sarcasm :)
[16:37] <didrocks> mterry: especially if they listened to the show when I talked about a wine indicator :)
[16:37] <mterry> didrocks, I felt bad for peeps, they seemed to actually be upset
[16:37] <didrocks> indeed, it's all dholbach's fault! Germans, again :-)
[16:37] <mterry> didrocks, you're not in #ubuntu-touch?
[16:37] <didrocks> oh hey ogra_!
[16:37] <didrocks> :)
[16:38]  * didrocks joins one more channel for spam ;)
[16:38] <ogra_> yo
[16:38] <ogra_> didrocks, intresting, sarcasm usually makes me grow faiuth in humanity :)
[16:38] <ogra_> *faith
[16:39] <didrocks> ogra_: well, they didn't get it, that's why I'm loosing faith ;)
[16:39] <ogra_> heh, ok
[16:40] <rvr> didrocks: Loosing faith is cool ;)
[17:18] <seb128> mterry, don't ruin the g+ comments fun :p
[17:18] <mterry> seb128, heh, I felt bad
[17:19] <seb128> mterry, no trolling on social media websites? :-(
[17:20] <ogra_> huh ?
[17:20] <ogra_> i thought thats what G+ is for
[17:20] <ogra_> trolling and cat pictures
[17:22] <didrocks> ogra_: I don't have the same circles than you it seems
[17:22] <didrocks> (for cat pictures ;))
[17:22] <didrocks> cat: pictures: Aucun fichier ou dossier de ce type
[17:22] <didrocks> btw ;)
[17:23] <ogra_> well, there also is that small fraction of people that break their phone backs all the time to take pics of the cracks ...
[17:23]  * ogra_ looks at popey
[17:23]  * popey flutters his eyes at ogra_
[17:24] <ogra_> :)
[17:24] <didrocks> ogra_: oh right, they seem to really perservere in that path :p
[17:24] <ogra_> my nexus4 lives in a phone sock ...  i drop it all the time :)
[17:25]  * Nafallo just put an invisibleShield on his beloved phone.
[17:25] <Nafallo> now I just need to wait 12-24 hours to get to use it again.
[17:25] <ogra_> i had such a rubber condom ... but it makes it look like an iphone
[17:40]  * didrocks waves good evening
[20:43] <GunnarHj> Anybody who can create a Precise task at bug 1161953?
[20:43] <ubot2`> Launchpad bug 1161953 in language-selector (Ubuntu) "gnome-language-selector crashed with TypeError in _expand_pkg_pattern(): not enough arguments for format string" [High,Fix released] https://launchpad.net/bugs/1161953
[20:48] <rsalveti> bryce: I'm looking at the xorg fix for bug 982889
[20:48] <ubot2`> Launchpad bug 982889 in OEM Priority Project precise "X trying to start before plymouth has finished using the drm driver" [Critical,In progress] https://launchpad.net/bugs/982889
[20:48] <rsalveti> drm_device_keep_trying.patch
[20:48] <rsalveti> do you know if this patch is still needed?
[20:48] <rsalveti> it broke all platform devices (not pci), including panda
[20:49] <rsalveti> because the patch is trying to parse the syspath by hand, and just dealing with the pci use case
[20:49] <rsalveti> while before it was grabbing the busid from the drm functions
[20:50] <rsalveti> bryce: the patch: http://paste.ubuntu.com/5677931/
[20:50] <rsalveti> tjaalton: ^
[20:52] <tjaalton> rsalveti: mlankhorst did further changes to it
[20:52] <bryce> yeah the syspath stuff was mlankhorst's change
[20:52] <rsalveti> tjaalton: right, seems the description is not matching the patch
[20:52] <bryce> maybe we should switch to the patchset I sent upstream
[20:52] <rsalveti> bryce: have the link?
[20:52] <bryce> yeah one sec
[20:53] <mlankhorst> rsalveti: judging from the kernel that was the only working case..
[20:53] <mlankhorst> maybe I misread it
[20:54] <rsalveti> nops, we also have platform devices
[20:54] <bryce> http://lists.freedesktop.org/archives/xorg-devel/2013-March/035782.html
[20:54] <rsalveti> such as /sys/devices/platform/omapdrm/drm/card0
[20:54] <rsalveti> mlankhorst: ^
[20:54] <rsalveti> bryce: thanks
[20:54] <mlankhorst> hmz
[20:55] <mlankhorst> I see, I'll try to make it work correctly on pandaboard then
[20:56] <rsalveti> mlankhorst: shouldn't we just use the patches that bryce sent upstream?
[20:56] <mlankhorst> rsalveti: it's a workaround, I'd rather drop the patch entirely
[20:57] <mlankhorst> since his version basically didn t work and only timed out, maybe that's fixed now, but if we could determine busid without requiring master then I think we should...
[20:57] <rsalveti> mlankhorst: problem is that we'd be parsing the string by hand
[20:57] <rsalveti> not that elegant
[20:58] <rsalveti> the busid for panda would be platform:omapdrm:0
[20:58] <mlankhorst> indeed, I'd rather have it as sysfs property...
[20:58] <mlankhorst> which wouldn't be too hard
[20:58] <rsalveti> so we need to grab the driver name and then the card id
[20:58] <mlankhorst> or just fallback if it's not a pci device
[20:58] <mlankhorst> would that be ok?
[20:59] <rsalveti> mlankhorst: yup
[20:59] <rsalveti> mlankhorst: will you work on this patch?
[20:59] <mlankhorst> sure
[20:59] <mlankhorst> can you open a bug report and assign it to me?
[20:59] <rsalveti> there's one already, let me post the details there
[20:59] <mlankhorst> I'm not on my computer, and about to fall asleep :P
[21:00] <rsalveti> sure
[21:06] <rsalveti> mlankhorst: bug 1161981
[21:06] <ubot2`> Launchpad bug 1161981 in xorg-server (Ubuntu) "Boot stalls after Ubuntu Raring desktop ARM (Panda board) install" [High,Confirmed] https://launchpad.net/bugs/1161981
[22:03] <thumper> can someone explain to me why I don't have any Display system settings any more (with raring)?
[22:03] <thumper> also, why don't I have the sync indicator showing?
[22:04] <sarnold> thumper: hrm, I've got a "displays" system settings page on my intel hd4000 raring ...
[22:05] <thumper> sarnold: I went through a phase of having two...
[22:05] <thumper> sarnold: and now I have none...
[22:05] <sarnold> thumper: haha :) nice
[22:05] <bschaefer> thumper, i've had a few of mine 'disappeared' with recent updates...check if you have them installed
[22:05] <thumper> sarnold: the early two was when I was on quantal with a development ppa
[22:05] <thumper> bschaefer: what should be installed?
[22:06] <bschaefer> thumper, hmm check if you have: gnome-control-center
[22:06] <bschaefer> and possibly gnome-backgrounds
[22:06] <thumper> bschaefer: Installed: 1:3.6.3-0ubuntu18
[22:06]  * bschaefer forgot which one was missing
[22:08] <bschaefer> thumper, you've got gnome-backgrounds as well?
[22:10] <thumper> bschaefer: no
[22:12] <koder> hello everybody
[22:12] <bschaefer> thumper, well hopefully that'll give you system display back...but I think that was for appearance...
[22:13] <thumper> ah...
[22:13] <thumper> bschaefer: you are right, I have displays, but no appearance
[22:13] <thumper> bschaefer: any clue about the sync indicator?
[22:14] <bschaefer> thumper, hmm i had a few indicators go away as well try: sudo apt-get install indicator-sync
[22:14] <thumper> gah, session indicator all screwed up again
[22:14] <thumper> after install
[22:14] <thumper> shows all users as ((null))
[22:14] <bschaefer> :(
[22:14] <bschaefer> i've not seen that!
[22:14] <bschaefer> thumper, possibly a compiz --replace ccp
[22:14] <thumper> I get it whenever the system indicator is updated
[22:15] <bschaefer> well I only have guest and my own account, so i
[22:15] <bschaefer> i've never noticed it change to null
[22:15] <thumper> I have a second account where I have personal stuff only open
[22:15] <thumper> so I can use my laptop without thinking of work
[22:15] <thumper> so I have email, but just personal email
[22:15] <thumper> irc, but just personal irc
[22:15] <thumper> etc
[22:16] <bschaefer> o nice, I use to do that with my desktop but i've stopped using it...I should split things up like that as well
[22:16]  * thumper waves at jasoncwarner
[22:16] <jasoncwarner> hey thumper
[22:16] <jasoncwarner> thumper I don't know why you don't have the display settings or indicator. can you file a bug and we'll look into it?
[22:17] <thumper> jasoncwarner: I was wrong, it was appearance I was missing, not displays
[22:17] <thumper> but sure, I can file a bug
[22:17] <thumper> just installing the kernel updates, so will need to reboot after that
[22:18] <jasoncwarner> thumper, yeah, reboot and see if it persists
[22:18] <thumper> jasoncwarner: I just installed gnome-backgrounds which bschaefer seemed to think was needed
[22:18] <thumper> jasoncwarner: but wasn't in the deps, so somehow got removed?
[22:19] <thumper> I'd hope that in making sure I had ubuntu-desktop installed, I'd get all the goodness
[22:20]  * bschaefer had the entire g-c-c go away a week or so ago
[22:20] <bschaefer> but I just needed to re-install somethings...
[22:21] <thumper> should I have a dkms.conf file?
[22:22] <thumper> I get: Error! Could not locate dkms.conf file. after every kernel update
[22:22]  * thumper reboots
[22:24] <thumper> jasoncwarner_: any particular tag I should use for the bugs?
[22:25] <bryce> jasoncwarner, any lockups since changing the semaphores setting?
[22:25] <thumper> jasoncwarner: what should I file the bugs under?
[22:27]  * thumper files three bugs
[22:30] <jasoncwarner_> bryce: no hangouts just yet...fingers crossed!
[22:34] <bryce> good
[22:41] <thumper> jasoncwarner: bugs filed and links in a PM
[22:41]  * thumper saves extra peer reviews for after lunch
[23:07] <RAOF> desrt: Want to pop into #ubuntu-mir for a moment? We'd like to make your life more awesome.


[02:50] <Maynard> Hello all
[02:52] <Maynard> So I have my .iso but choosing the different bootable usb programs has left me REPEATEDLY with grub2(?) not found or casper/linuz/efi not found
[02:53] <Maynard> I am SEMI computer savvy btw.  I am comfortable in terminal usage.  mostly copy/paste though.
[02:59] <Maynard> btw it's 16.04.1 so there is no disk utilities, or the typical answers since it's not gnome. It's xfce or xcfe.... whichever.
[03:00] <Maynard> I was reading unetbootin causes the grub fail and pendrive (I think )was the casper not found one.
[03:02] <OvenWerks> Maynard: I have been using dd if=iso_file of=/dev/sd* (* = whatever the USB stick is)
[03:03] <OvenWerks> Maynard: the computer has to be able to boot from usb sticks of course :) strange I should have to say that as I think they all have for around 10 years, but I do have a machine that requires a DVD
[03:04] <OvenWerks> (dd requires sudo to run probably)
[03:07] <Maynard> no I have built this before on this system.  I do have a black spot right where your answer is.... in terminal just type dd if=iso_file of/dev/sdb or do I use the full sdb1 ?
[03:07] <Maynard> I have sudo
[03:07] <OvenWerks> sdb
[03:08] <Maynard> and no need for the full .iso name?
[03:08] <OvenWerks> Warning, this will make your first partition on the usb stick the size of the iso
[03:08] <OvenWerks> ya the whole iso file name
[03:09] <Maynard> this is where I get lost.....
[03:10] <Maynard> I know in thte future updates will need more space
[03:10] <OvenWerks> After you have installed the iso to your hard drive you may wish to reformat the usb stick if you want to use it for other things.
[03:10] <OvenWerks> That doesn't matter, because the dd will print the size of the new iso
[03:10] <OvenWerks> *the next dd
[03:10] <Maynard> I typically prefer an apt (?) to automatically do this but all have failed so far
[03:11] <Maynard> and dd means what?
[03:11] <OvenWerks> I have not used an upgrade for a long time
[03:11] <Maynard> sorry....
[03:11] <OvenWerks> man dd
[03:11] <OvenWerks>  :)
[03:12] <OvenWerks> dd is a direct raw copy
[03:12] <OvenWerks> I don't remember off hand why it was originally called dd
[03:12] <Maynard> I want to keep the .iso intact and able to update. it's a mere 4Gb but I use it on several comp. to easily make ubuntu for others
[03:13] <OvenWerks> so no problem then
[03:13] <Maynard> so you mean updates will make a new ddd?
[03:13] <Maynard> dd
[03:14] <OvenWerks> no, the iso will be different sizes from release to release. dd doesn't care so long as the total size of the usb stick is less than the iso size
[03:14] <OvenWerks> dd is a raw write to the usb stick without regard for partition tables
[03:15] <OvenWerks> So it effectively makes it's own partition
[03:16] <Maynard> so mine would read " dd if=ubuntustudio-16.04.1-dvd-amd.iso of dev/sdb " exactly as I typed then?
[03:16] <OvenWerks> I think it is amd64 not amd
[03:17] <Maynard> Roger...never understood dd before. So since it's 4Gb and only 2.6 for iso then it'll just keep adding when I update
[03:17] <Maynard> ?
[03:17] <OvenWerks> and I think it should be 16.04.2 by now unless you have an older iso.
[03:17] <Maynard> correct amd64.iso
[03:18] <OvenWerks> dd if=ubuntustudio-16.04.1-dvd-amd64.iso of=/dev/sdb
[03:18] <Maynard> For some reason transmission said 16.04.2 was not suported by tracker
[03:18] <Maynard> exactly as written?
[03:18] <OvenWerks> ok
[03:18] <Maynard> as you wrote
[03:19] <OvenWerks> I think so... assuming the file is right :)
[03:19] <Maynard> I was dbl checking as we were chatting
[03:21] <OvenWerks> it will take a while and does not give any indication of activity
[03:21] <Maynard> unless you mean as long as it's not corrupt or not 100%
[03:21] <Maynard> ok
[03:22] <OvenWerks> Ya once it is finished it tells you blocks in and blocks out. they should be the ssame number.
[03:22] <Maynard> So I'll just leave it and the usual pop-up to restart will come up when its done?
[03:23] <Maynard> OK ok.... I've noticed before the block sizes were different sometimes.
[03:23] <OvenWerks> after that you have to boot with the usb stick in. the dd just writes the stick
[03:23] <Maynard> both sticks are in.
[03:24] <Maynard> I use a 128 as my HD and the 4 as my back up so I don't need to re-download the iso
[03:24] <Maynard> LMAO this thing is a Frankenstein. It's from 2006 but hangs with all but the newer gaming laptops
[03:25] <Maynard> swapped RAM etc etc
[03:26] <Maynard> OK so I would write the dd with both in and then shutdown, then only the 4Gb?
[03:26] <Maynard> stupid question.
[03:27] <Maynard> the iso is on the 128 Gb
[03:27] <OvenWerks> Assuming you wrote the 4 G that is the one you want to boot from
[03:27] <Maynard> I'm just starting from scratch cause of all the problems
[03:27] <OvenWerks> I'm confused
[03:28] <OvenWerks> I would think you are installing to the 128?
[03:28] <Maynard> I'm writing from the 128 to the 4G only to turn around and fresh install onto the 4G as a bootable usb.
[03:28] <Maynard> That better explained lol
[03:29] <Maynard> I will install to the 128 but I want the 4 intact as bootable
[03:29] <OvenWerks> ok, I am not sure if that will work, I think an install is around 8g
[03:31] <Maynard> Correct. the iso will be a bootable and only 2.6 but the installed one on the 128 WILL be 8ish.  As you said.
[03:32] <Maynard> I BARELY made a work around on the 128 so that's why I'm starting the iso from the start cause something happened in the iso to bootable usb part.  Many times with many programs
[03:33] <OvenWerks> I remember trying to install to a 32g usb stick before, but don't remember the details. No swap though.
[03:33] <Maynard> So sounds like the dd will try to install not make a bootable usb of the 2.6 G.  Do I have that right?
[03:34] <OvenWerks> it should make a bootable iso
[03:34] <OvenWerks> should boot the same as a dvd with the same iso on it
[03:35] <OvenWerks> it is the differentce between writing an iso to a device and installing the system to a device.
[03:35] <Maynard> Yeah I did the 32Gb once but every time I mess with swap it crashes everything so now I use the 32 as backup for files.  There is no HDD in here. I need a new PC.
[03:36] <OvenWerks> The iso will run as it's own install, but you have to manually mount a writable partition to save anything. The iso is not persistant
[03:36] <Maynard> Sweet that's what I want. Everything is backed on the 32G and the bootable will be the 4 and then I'll install onto the 128.
[03:37] <Maynard> I told you Frankenstein.
[03:37] <OvenWerks> I have done some odd things in my time...
[03:38] <Maynard> I've never done this in terminal before and it wasn't a persistent, but I could always remember what extras I added and just did it the long way.
[03:39] <Maynard> I read making a persistent one and I hate doing partitions....   Dare I even ask how to use the other 1G on the small one to use as the persistent partition?
[03:43] <Maynard> LOL or do I just do this and let you get to someone else?
[03:45] <Maynard> Cause it WOULD be nice to keep all my extra pkgs there but since I know them if it's complicated I'll just rebuild when I wanna fresh install.
[03:46] <Maynard> Could I do the dd thing then use Gparted to make a 1G partition?
[03:47] <Maynard> Or once I do that in terminal there is no changing the usb with another partition?
[03:56] <Maynard> Did I lose you or are you banging your head on the desk?
[03:57] <Maynard> Just answer the 2 ?s before the head banging one and I'll leave you alone.
[04:06] <Maynard> no?
[04:12] <Maynard> S***bags!  Here's what I get:  dd if=ubuntustudio-16.04.1-dvd-amd64.iso of dev/sdb dd: unrecognized operand ‘of’ Try 'dd --help' for more information.
[04:35] <OvenWerks> Maynard: of=/dev/sdb
[04:35] <OvenWerks> Maynard: you are missing both the = and the /before dev
[04:36] <Maynard> ok
[04:40] <Maynard> no such file now
[04:40] <Maynard> arrrrrrrrgh
[04:45] <Maynard> unetbootin it is...............I HATE it when I cannot figure out what seems a simple thing to do
[14:58] <studio-user823> i installed windows swtich on ubuntu and my system blocked everything, i had to reinstall my OS
[14:59] <studio-user823> anybody knows how could have  been better to uninstall that program and clean my system
[17:32] <djzu> Hi there! I badly need help for running Xpra under Ubuntu Studio. Indeed a simple: apt install xpra; xpra start; xpra attach; will fail (core dumped) on Ubuntu Studio while it is working with Ubuntu or Xubuntu. If not Xfce, who is involved in this crash?
[18:01] <djzu> Hi jbermudes! I badly need help for running Xpra under Ubuntu Studio. Indeed a simple: apt install xpra; xpra start; xpra attach; will fail (core dumped) on Ubuntu Studio while it is working with Ubuntu or Xubuntu. If not Xfce, who is involved in this crash?
[18:06] <OvenWerks> djzu: have you tried ssh -Y?
[18:07] <djzu> @OvenWerks: actually from another machine it is working but not from the local machine
[18:09] <OvenWerks> djzu: it may be better to ask in #xubuntu as they have the same desktop and the ear of some of the xfce devs
[18:09] <OvenWerks> I have only used ssh -Y and VNC myself
[18:10] <djzu> OvenWerks: I tried to replicate installing ubuntu xubuntu and ubuntu-studio on virtual machine and the problem is only on ubuntu studio not xubuntu
[18:22] <OvenWerks> Interesting.
[18:22] <OvenWerks> There is a possibility that it is either xfce settings that differe slightly or more likely that it is a kernel difference
[18:23] <djzu> is the kernel different from xubuntu?
[18:23] <OvenWerks> It is possible to install the generic kernel on top of Studio and run that and see if that makes any difference
[18:24] <OvenWerks> Yes xubuntu uses the standard generic kernel, Studio uses the lowlatency kernel.
[18:24] <djzu> I tried to install the lowlatency kernel on top of regular ubuntu and the problem did not appear
[18:25] <djzu> I'll try to install the lowlatency kernel on xubuntu this time to see if there is an difference
[18:25] <OvenWerks> You also have to make sure the lowlatency kernel is running :)  uname -a will tell you
[18:26] <djzu> yes I made sure of that
[18:26] <OvenWerks> OK
[18:29] <djzu> If not Xfec, if not lowlatency kernel, who can be the culprit?
[18:32] <djzu> OvenWrks: you also said about xfce settings that might differe, can you tell more about that?
[18:33] <OvenWerks> setting->window manager tweaks->compositor  comes to mind
[18:33] <OvenWerks> (though I don't htink we do different)
[18:35] <OvenWerks> also settings->window manager->style->theme may be different
[18:36] <djzu> well running Xpra from fresh Ubuntu inside virtual machine works but throw a warning about a possible bug with 'compiz'.
[18:36] <OvenWerks> I don't use the default theme so I don't know what it should be :) I use Moheli because I resize windows often
[18:37] <djzu> The error is a segmentation fault, do you think a theme can be involved?
[18:37] <OvenWerks> Moheli both has better indication of which window has focus (different title colour) and the frame is wider so it is easier to grab the sides.
[18:37] <OvenWerks> themes are quite invasive
[18:38] <OvenWerks> So yes a theme can do things like that
[18:38] <djzu> interesting
[18:38] <OvenWerks> A theme touches almost everything about the window.
[18:39] <OvenWerks> A theme has code in it
[18:39] <djzu> then the ubuntu studio theme could be involved
[18:39] <OvenWerks> So a gtk2 theme can break a wm running gtk3
[18:40] <djzu> the xpra client is gtk2
[18:40] <OvenWerks> I think most of the DEs (aside from KDE) are already gtk3
[18:41] <OvenWerks> But quite honestly this is getting way outside anything I know about.
[18:44] <djzu> I switched to Moheli theme but the problem is still there
[18:45] <djzu> I'm afraid I'll have to forget about Ubuntu Studio and start from scratch
[18:45] <OvenWerks> you can start from xubuntu and install Studio meta packages to get the same Applications
[18:46] <OvenWerks> Don't install the ubuntustudio-desktop packages though
[18:47] <djzu> yes I know but that's pain since I already have a working setup for music that I'll have to screw and start over
[18:48] <djzu> btw, I just installed ubuntustudio-desktop packages to a fresh Xubuntu in virtual machine and still Xpra was working
[18:49] <OvenWerks> Is it one particular application then?
[18:49] <OvenWerks> Or does it crash when nothing is open too?
[18:52] <djzu>  Xpra is an open-source multi-platform persistent remote display server and client for forwarding applications and desktop screens.  It gives you remote access to individual applications or full desktops. On X11, it is also known as screen for X11: it allows you to run programs, usually on a remote host, direct their display to your local machine, and then to disconnect from these programs and reconnect from the same or another m
[18:53] <djzu> it is about Xorg, X11, Xfvb, Xdummy
[18:54] <djzu> xpra start; xpra attach; will fail. no application involved
[19:21] <OvenWerks> I don't know. Maybe someone else might if when they are around. Most people are close to utc or a couple hours before utc
[19:34] <djzu> Thanks for your input
[19:43] <OvenWerks> np