[03:35] <geser> keescook: could you sponsor bug #138149? It includes a fix for CVE-2007-1888.
[03:35] <ubotu> Launchpad bug 138149 in sqlite "[Fake sync]  sqlite (2.8.17-2.1build1) from Debian unstable" [Undecided,New]  https://launchpad.net/bugs/138149
[07:53] <cjwatson> aquo: you don't need to install either manually; just use whichever the g++ version you're using depends on
[10:12] <Amaranth> wow i never knew the upgrade tool told you about packages that have moved to universe
[10:12] <Amaranth> that's a nice touch
[11:02] <Kopfgeldjaeger> hi!
[11:36] <stdin> hmm, I need some advice: how would you split a source-package in to more than one binary-package when each binary-package is just compiled differently. ie: the only difference is the libs they are compiled against
[11:37] <stdin> not sure how well I explained it there :p
[11:40] <Fujitsu> stdin: Is this about the Qt[34] /KDE variants bug that I saw earlier?
[11:40] <stdin> it is :)
[11:41] <Fujitsu> I ran away quickly.
[11:42] <Amaranth> stdin: look at totem
[11:43] <Amaranth> stdin: it builds twice, once against xine, once against gstreamer
[11:43] <stdin> hmm, I'll go have a look. thanks
[11:45] <geser> doko: something got wrong with your vectormath package: libvectormath-dev depends on libvectormath1 which doesn't exist
[01:30] <Hobbsee> hmmm.   sabdfl is emailing us all again.  scary.
[01:31] <sabdfl> watching quietly here, too ;-)
[01:31] <sabdfl> how are you, Hobbsee?
[01:32] <Hobbsee> arg!  he's here!
[01:32] <geser> Hi Hobbsee, sabdfl
[01:32] <sabdfl> hey geser, glad to hear it Hobbsee!
[01:32] <Hobbsee> sabdfl: i didnt even kill anyone :P
[01:33] <sabdfl> my kind of gal
[01:33] <pygi> Hobbsee, your not that scary, you just pretend to be =)
[01:33] <zul_> Hobbsee is always scarey
[01:33] <Hobbsee> pygi: oh, i can be scary.
[01:33] <pygi> Hobbsee, nop :)
[01:34] <Hobbsee> sabdfl: it seems to be teh weekend, why are you here?
[01:34] <asisak> Hobbsee: What do you work that eventually involves killing people?
[01:34] <Hobbsee> asisak: killing customers.  not staff.  usually.
[01:34] <jdstrand> mdz: are you seeing odd behavior with your brightness controls and defaults on your laptop?  (I believe we have the same laptop)
[01:34] <Hobbsee> asisak: at a supermarket
[01:35] <Hobbsee> oh yay, cprov is back!
[01:36] <sabdfl> jdstrand: i see that on my X60
[01:36] <jdstrand> I saw #81407, but it is all over the place (people talking about different symptoms, etc)
[01:37] <jdstrand> sabdfl: I have a T42
[01:37] <jdstrand> bug 81407
[01:37] <ubotu> Launchpad bug 81407 in gnome-power-manager "[Feisty]  Thinkpad (all models) LCD brightness control cycles between lowest settings only" [Medium,Confirmed]  https://launchpad.net/bugs/81407
[01:37] <mjg59> I'm working on it
[01:37] <sabdfl> hey mjg59
[01:37] <mjg59> hal is just broken here
[01:37] <jdstrand> mjg59: this is for gutsy?
[01:38] <\sh> nice...I thought my t43 is broken, so I replaced it with a new one *lol*
[01:38] <mjg59> Yes
[01:38] <jdstrand> mjg59: cool
[01:40] <jdstrand> mjg59: another symptom I have is on login it defaults to the lowest brightness.  after a little while things 'settle down' and I can adjust it properly (that is, until g-p-m kicks in, and its reset to the lowest)
[01:40] <jdstrand> mjg59: I'm guessing its all related?
[01:41] <sladen> somewhere I was in the middle of killing thinkpad-keys and replacing it with acpi-support events
[01:41] <jdstrand> mjg59: note that gdm displays the proper brightness
[01:41] <sladen> which should do with the CPU issue and may deal with the brightness weirdness at 100%
[01:42] <mjg59> jdstrand: Pretty much
[01:43] <mjg59> gpm is getting bogus answers from hal because it's not standardised whether stuff sends uints or ints
[01:43] <jdstrand> hey cool, it just went to its lowest brightness as I read your response
[01:43] <jdstrand> mjg59: ah.  is there a bug I can subscribe to?
[01:43] <jdstrand> if its convenient
[01:49] <jdstrand> I ask cause there are a bunch of seemingly related reports, and I don't know which you are actively updating
[01:53] <mjg59> I was mostly ignoring them because a huge number of people have started reporting entirely unrelated issues in the same bugs
[01:53] <mjg59> I'll get it to the point where it should work, then see whether there's still anyone complaining :)
[01:53] <jdstrand> yes-- I saw that too.  Well knowing someone is working on it is ok by me.  Thanks!
[02:15] <Amaranth> mjg59: dude that happens to a lot of the compiz bugs
[02:15] <Amaranth> someone reports a problem and 5 people leave comments with completely different problems
[02:18] <StevenK> Amaranth: I hate that. "Oh, that isn't my problem at all - this is my problem" in a bug report.
[02:19] <lucky_lucas> Hi, every one, I just read that the backlight issue is on the track (happy), I would like to konw what is the state of the compiz/X crash ?
[02:19] <lucky_lucas> I reported a bug but it was somehow unusable
[02:20] <lucky_lucas> bryce seems to be aware and I saw on the xorg maiing list they know that xorg 7.3 crashes with compiz but don't know if any fixes is planned
[02:34] <Amaranth> lucky_lucas: nvidia?
[02:51] <lucky_lucas> Amaranth: both of them
[02:52] <lucky_lucas> I experience a total freeze on my t43p ati firegl with ati 6.7.192 driver and on the  desktop with nvidia driver
[02:52] <Amaranth> oh, the only known problem is the nvidia one, afaik
[02:53] <lucky_lucas> I've read on the xorg mailing list that they are aware of crashes with compiz and x
[02:54] <lucky_lucas> I don't know if it's a "cross driver " issue
[02:56] <lucky_lucas> Therre is something I don't understand in the doc for debbuging xorg, I'm connected through ssh but once I attach gdb to X, it freeze the desktop
[02:56] <lucky_lucas> so I type cont and X goes ok, but I don't have any feedback
[04:05] <Hobbsee> greetings, jono
[04:06] <jono> heya Hobbsee
[04:07] <Hobbsee> bah.
[05:45] <jdstrand> mjg59: I just upgraded the new hal and rebooted.  _very_ preliminary testing shows the screen brightness on my laptop is working fine again
[05:48] <jdstrand> gdm still good, login has no brightness changing, brightness comes back to normal after screen blank
[05:48] <jdstrand> great job!  thanks :)
[05:55] <bSON> hi
[05:56] <bSON> will the dodge effect stay the default for ubuntu gutsy's compiz? it is annoying after a short while, way too much movement IMO
[05:57] <bSON> not the subtleness the default settings should have
[06:59] <bhale> on batter
[07:05] <jdong> is it just me, or is tracker a LOT more disk-intensive than beagle?
[07:13] <geser> I've seen other reporting it too
[07:15] <jdong> it causes like 5x the midnight-thrashing that I'd see with updatedb...
[07:33] <siretart> yes, it really drains notebook batteries like nothing
[07:34] <mekius> hey, after you login with gdm, somehow the X root window is being set to a brown color, what is controlling this?
[07:34] <mekius> before gdm starts up it is using the color i defined in the gdm.conf
[07:34] <mekius> but after the login and before the session starts i see brown
[07:38] <_StefanS_> hi there..
[07:39] <Amaranth> geser, jdong: Are you guys talking about tracker?
[07:39] <_StefanS_> I would appreciate if someone in here could review this comment fra Rizlaw : https://bugs.launchpad.net/ubuntu/+source/kdebase/+bug/103401, it seems to be related some session stuff in gnome.
[07:39] <ubotu> Launchpad bug 103401 in kdebase "Reboot-Restart Button with classic LogOut Dialog (doUbuntuLogout=0) doesn't work" [Undecided,Fix released] 
[07:39] <_StefanS_> it was reported wrong into a KDE related ticket.
[07:42] <Amaranth> _StefanS_: looks like he had a session saved or something
[07:42] <Amaranth> i dunno, i've never used that stuff because it basically never works right
[07:42] <_StefanS_> Amaranth: yes something like it, is it something you could comment on from a ubuntu kind of view ?
[07:42] <_StefanS_> Amaranth: oh. ok
[07:43] <_StefanS_> Amaranth: well it just seems odd to use ctrl+alt+backspace, doesn't it kill the X-server?
[07:43] <jdong> Amaranth: yeah, I'm talking about tracker
[07:43] <jdong> Amaranth: its memory/CPU footprint is impressive, but disk intensity leaves a lot to be desired.
[07:44] <jdong> Amaranth: if I didn't have good quality drives in this thing, I'd be concerned about life reduction.
[07:46] <Amaranth> jdong: oh?
[07:46] <Amaranth> it seems fine here
[07:47] <Amaranth> it stops trying to index if something is writing to the file it's indexing
[07:47] <jdong> Amaranth: hmm I might just have too much (several multi-GB bzr repos) in my home dir then... because it does about 25 minutes of thrashing per night.
[07:47] <Amaranth> per night?
[07:47] <jdong> yes.
[07:47] <jdong> per night
[07:47] <Amaranth> oh, i know why
[07:47] <Amaranth> it ran out of inotify watches
[07:47] <jdong> eep...
[07:48] <Amaranth> so it periodically crawls your filesystem manually
[07:48] <Amaranth> i thought it only did it when it first started
[07:48] <Amaranth> if you, say, triple the allowed inotify watches... :)
[07:49] <Amaranth> hopefully that's not a compile time thing but i have a feeling it is
[07:49] <jdong> what are the downsides of doing that, and how do I go about it?
[07:49] <Amaranth> (kernel compile time)
[07:49] <Amaranth> it's a possible DoS or something
[07:49] <Amaranth> i have no idea how to do that
[07:49] <jdong> ah
[07:49] <jdong> oh well minor issue....
[07:49] <Amaranth> i know rlove pushed really hard to get a high number in there
[07:50] <Amaranth> but didn't succeed, dunno if ubuntu changes it
[08:07] <tonyyarusso> cjwatson, pitti, keybuk: I see that https://blueprints.launchpad.net/ubuntu/+spec/dm-crypt (solution to bug #39326) is still marked as Undefined/Drafting/Unknown, even though the technology has been available upstream for quite a while now.  Why is that, and do you have any estimate of a revised timeline for implementation?
[08:07] <ubotu> Launchpad bug 39326 in debian-installer "installer: dm-crypt support missing" [Wishlist,Confirmed]  https://launchpad.net/bugs/39326
[10:41] <Kopfgeldjaeger> N8
[11:01] <stgraber> Seveas: Can you move ubotu from #ubuntu-iso to #ubuntu-testing ?
[11:03] <Seveas> @part #ubuntu-iso
[11:03] <ubotu> OK
[11:03] <Seveas> @join #ubuntu-testing
[11:03] <Seveas> stgraber, done :)
[11:04] <stgraber> Seveas: thanks