[00:00] RIGHT [00:00] mathiaz: hmmm where can I read about looms? [00:00] oh, heh, I think I was 18 seconds late with the kickseed sync [00:00] * cjwatson blames his local clock [00:01] lol' [00:01] ... which has yet to hit midnight [00:01] let's blame Keybuk [00:02] hahah! [00:04] slangasek: http://www.flamingspork.com/blog/2008/02/22/bzr-loom-a-bzr-plugin-with-quilt-like-functionality/ [00:04] slangasek: https://edge.launchpad.net/bzr-loom/ [00:04] slangasek: looms is quilt for bzr [00:07] yes, I gathered that, I was interested in getting ahold of the details :-) [00:09] hello, does anyone have blender and NetworkManager running on their ubuntu so I can confirm a bug? thanks [00:09] non-ati video card preferred [00:10] Who can change build priorities? [00:11] soren, an archive admin! [00:11] buildd admin, rather [00:12] Thinking about it some more, I'm not sure it'll make any difference. [00:12] https://launchpad.net/~launchpad-buildd-admins/+members [00:17] hm... mount command's manpage should be updated for -t ext4 type [00:31] mathiaz: ah, hrm, if you're going to fire off all the patches in a batch, bug reports would probably be better [00:31] update manager autolaunch, ugh, now i just need to go uninstall it entirely since apparently the notification icon wasn't annoying enough already [00:34] * calc had thought he had somehow hit the button by accident until he read the bug report that this is a new "feature" === pgraner_ is now known as pgraner [00:40] calc, how about xpsp2-style "your pc will reboot in 15 mins for an update"? :) [00:40] directhex: heh that will be when everyone switches to fedora [00:40] directhex: that is one of the reasons I refuse to use XP for anything more than bug testing === Cxoliac is now known as Sevink [00:41] though there is a way to disable it, that is well hidden, it is the most evil pos [00:41] the idea about getting a stock gnome setup though may have more users than originally intended depending on how far these feature changes go [00:42] iirc it was thought it would only be wanted by gnome devs [00:43] * calc just used gconf-editor and disabled the autolaunch [00:43] calc: At least the update icon is unobtrusive [00:44] StevenK: yea the new feature is that update notifier runs on your desktop every 2 days [00:44] Eek [00:44] so really intrusive [00:44] Bad [00:44] yea [00:44] bug 331054, its considered a new 'feature' [00:44] Launchpad bug 331054 in update-notifier "Do not launch in background" [Undecided,Invalid] https://launchpad.net/bugs/331054 [00:45] * calc hopes the DX team doesn't manage to run off all the Ubuntu users [00:46] it won't take too much to reach windows annoyance level which will drive users elsewhere [00:46] That is a shocking feature. [00:46] at least the users who don't know how to fix it on their machines, anyway [00:46] That will get users in more trouble than it will help them IMO [00:46] I won't want to have to keep turning that off when I create a fres install/user. [00:47] fresh [00:48] TheMuso: feel free to bring it up on one of the mailing lists for discussion, apparently it was closed as invalid, since they want it to work that way [00:48] Hrm. [00:48] though it looks like this might be a feature request from sabdfl after looking at the bug report :-\ [00:51] * TheMuso sighs. [00:51] The bug did say auto-updating isn't going to be the default ... [00:51] StevenK: auto updating isn't default, but popping up to show you need to update will be [00:52] Ah [00:52] * StevenK grumbles [00:52] so every 2 days you get this dumb thing launched [00:52] which i don't even use, i only don't remove it since it is depended on by ubuntu-desktop [00:53] does it launch every two days, or only when there are pending updates? [00:54] every 2 days with pending updates, so for people tracking development releases, every 2 days :) [00:55] regardless popping up a large app window is pretty annoying [00:55] i guess they considered the app icon showing up wasn't sufficient annoying so they wanted to make it worse [00:56] iirc it shows up red or something like that when you need to update [00:57] * TheMuso will have to test it, and if it behaves badly with accessibility, will have to turn it off for accessibility use cases. [00:57] things popping up the user didn't explicitly ask for isn't particularly good ui design (imho), it causes confusion [00:57] on the live CD/installs etc. [01:27] slangasek: FF is, or is not in effect yet? [01:28] is [01:28] Damn [01:28] So I need FFe's for all of the stuff I just cleared out of NEW? [01:32] Hi ! There's been an important security update in vsftpd and I was wondering to whom should I raise a flag so that it makes it to the repos as fast as possible ??? Any Idea ? [01:32] slangasek: Just worried that I should be processing NEW and syncs differently [01:37] StevenK: From a motu-release perspective we have considered stuff that got uploaded prior to FF as OK even if it got processed out of new later. [01:38] Right, so NEW is okay, but syncs need closer checking [01:39] Even there I'd say if they were ack'ed and approved, pre-FF it's OK. [01:39] Unless someone is starting a new ghc6 transition or something [01:39] Someone actually asked about updating ghc6 today. [01:39] We all said NO. [01:40] I've only done binary NEW, so ... [01:47] FrankT-Qc: you could try #ubuntu-hardened - other than that, I don't know :) you could also file a bug report and check the box below the report to make it a "security risk" (or something like that) at http://bugs.launchpad.net/ubuntu/+filebug [01:49] savvas : thanks [01:50] slangasek: If we're past FF, then I think a "Hey, stop now" mail would be in order. I havene't seen one yet. [01:50] Indeed [01:50] ScottK: will send it out in a couple of hours, unless you want to beat me to it [01:51] * ScottK has to deal with kids for a few more hours, so probably not. [01:52] The good news is that means I don't have to stay up late tonight to finish something. I can give myself an FFe on the weekend as easily as today. [01:52] :-) [01:53] slangasek: I changed /topic in #ubuntu-motu. It's a start. [01:54] $topic =~ s/open/FF (ish)/; # ? === cjwatson1 is now known as cjwatson [02:27] jcastro: Just read your blog on the tool for opening upstream tasks. [02:27] I guess I don't understand what good a blank upstream task does? [02:31] ScottK: well it would make it clear the bug is an upstream issue versus something that needs fixing just in ubuntu [02:31] I'm rather getting the impression that the new notifier stuff was landed to get in before FF, not because it was ready :-( [02:31] maxb: You sound suprised. [02:32] not surprised :-) [02:32] calc: I guess, it just seems like a lot of effort for little gain unless you are actually going to report the bug upstream and then link it. [02:32] * maxb goes on bug-filing spree [02:32] ScottK: unfortunately the talk I gave at UDS wasn't recorded but basically, people who triage do a good job at linking once they find that it's an upstream bug [02:33] ScottK: so the idea is to get developers opening more open tasks so that triagers can link them [02:33] jcastro: I see. I guess that makes sense. === dmb_ is now known as dmb [02:33] Kind of. [02:34] basically, if developers can grow the pile of possible bugs, it's relatively easy to grind through them and open the bugs upstream [02:34] I see. [02:34] I thought the theory of Triaged was the was when it was ready for developer attention. [02:35] Now I'm confused again. [02:35] it only looks at triaged bugs [02:35] OK. [02:36] I'm caught in a mental catch 22 in that I don't know how you can mark it triaged and not know it needs upstreaming, but I never understand this stuff. [02:36] cool new 5-a-day group :) [02:37] ScottK: ok, so when you are looking at a bug and you know it's upstream, you can mark it as such, and then someone like me will go through the annoying (but relatively easier) task of filing it upstream. [02:38] jcastro: how are the stats tracked with the new group? [02:38] I see. [02:38] that way you do what you do best, and the triagers can do what they do best [02:38] I guess that makes sense. [02:38] jcastro: OK. Thanks. [02:38] that's the /idea/ anyway [02:39] * ScottK just wishes he see more triagers doing more than "-> Incomplete, can you still reproduce this in Jauntu". [02:39] amen [02:40] I'd even much prefer "I tried to reproduce this and couldn't, how did you do it and can you still" [02:40] absolutely === bluesmoke is now known as Amaranth [02:41] I just put my bugs back to what they should be when folk do that to me [02:41] usually with a snarky comment [02:41] :( [02:41] does anyone know why gcj-4.3 on HPPA seems to be MIA? [02:41] LP says it built [02:41] the binaries seem to have vanished into thin air ... [02:42] Yes. Me too, although I'd describe my reponse is these cases more as 'pointed' [02:42] The bug team doesn't test the bugs, they just look at the ones that are Incomplete for more than a month [02:42] We could script that. [02:42] ScottK: It is scripted, the Launchpad Janitor [02:43] Amaranth: That's for after they're incomplete. [02:43] I guess I missed half the conversation [02:43] Do you mean the "Does this still happen in jaunty?" ones? [02:43] Yeah. [02:43] It [02:44] It's a new bug and the first comment is can you reproduce it and set it to incomplete. [02:45] We could trivially replicate this by setting all bugs to incomplete at the last alpha and then marking them invalid if no one complains by release. [02:45] I don't think this would be a good policy, but it would give us most of the same effect. [02:49] as long as all doesn't include triaged bugs ;-) [02:49] it would give us most of the same effect and it would suck even more completely. :-) [02:50] heh [02:50] +1 cjwatson [02:53] cjwatson: quick question, how often are the ports alternate CDs being built? Each milestone, or more often? [02:53] cjwatson: I'm definitely not arguing in favor of it, just trying to point out how mechanical the current 'triage' effort it. [02:54] ScottK: oh, I know [02:54] NCommander: daily [02:54] Oh [02:54] * NCommander is lagging [02:54] I thought today was the 20th ... [02:54] And the last build was yesterday [02:54] :-) [02:55] * NCommander is actually trying to make our ports be shiny this release [03:03] \o/ boost1.35 fixed on sparc. [03:03] Speaking of ports. [03:03] ? [03:03] Akonadi built. [03:04] Score! [03:04] speaking of sparc, can somebody fix its asm/byteorder.h? [03:04] http://launchpadlibrarian.net/22607976/buildlog_ubuntu-jaunty-sparc.glibc_2.9-0ubuntu10_FAILEDTOBUILD.txt.gz [03:04] cjwatson, testbuilding the fix now [03:04] ah good [03:04] (I have to build a kernel, then the fixed glibc) [03:04] I have a potential glibc change pending for the not too distant future anyway [03:04] so maybe we can do those in one upload rather than separately [03:04] cjwatson, powerpc and sparc are looking quite good for this release, and if I can get an itantic, it will look good with ARM :_) [03:04] I need to get it tested from my PPA though, so tomorrow [03:05] cjwatson, test what to where? [03:06] potential fix for bug 313218 [03:06] Launchpad bug 313218 in glibc "IPV6 causes slow internet access" [Critical,Confirmed] https://launchpad.net/bugs/313218 [03:06] it's in 'deb http://ppa.launchpad.net/cjwatson/ppa/ubuntu jaunty main' if anyone wants to try it before I do and potentially hose their system ;-) [03:07] Actually, I can test this [03:07] * NCommander has an IPv6 network ... or did [03:07] that's one of the components of the test [03:07] I have an IPv6 network too [03:07] I haven't reset up the router since I replaced it [03:07] also needs testing from the folks actually afflicted by the bug, though, which is rather more those people who have broken IPv6 connectivity [03:07] oh [03:08] What did you change? [03:08] pulled in a Fedora patch to disable gethostbyname4 for the time being [03:08] O_o? [03:08] That sounds like a necessary bit of code ... [03:08] it's from Jakub Jelinek who knows what he is doing wrt glibc. [03:09] Well, if my point just didn't burn and crash [03:09] if gethostbyname4 isn't there it'll use gethostbyname3 - glibc tends to support older interfaces of things [03:09] glibc's source code scares me [03:09] I feel like its going to come and get me in the middle of the night and rip off my head [03:09] speaking of middle of the night ... [03:10] cjwatson, I was about ot say it was kinda late your time. [03:11] i noticed we were switching to boost 1.35 but 1.37 is also in the archive, should packages migrate to that instead? [03:13] calc: We all need to use the same one. [03:13] Please let's not start another switch right now. [03:14] That and I just got 1.35 patched to work on sparc. [03:14] cjwatson, do you know about anything on java on HPPA? [03:15] NCommander: I don't think such a thing exists. [03:15] :-/ [03:15] IIRC that's what lamont told me. [03:17] * ScottK goes back to trying to understand what the heck he was thinking when we wrote this beautiful code 9 months ago. [03:18] * NCommander watches ScottK's brain liquidify [03:19] It really was a lovely way to solve the problem I was having at the time. [03:19] It may, however, turn out to be just one increment short of extensible enough. [03:21] ScottK, looks like kdebindings on HPPA is fixed [03:21] \o/ [03:21] Its nice to have that fixed. [03:21] Yep. I don't think that's ever built. [03:21] * NCommander is officially the KDE port gurur ;-) [03:21] *guru [03:21] It did in the 3.x series [03:21] No mono bindings in KDE3. [03:22] yay [03:22] We could have solved KDE4 easily enough be not shipping them. [03:22] I'm kinda suprised mono is disabled on HPPA [03:22] It seems to be supported [03:22] it probably wasn't supported back in the distant past [03:23] maybe its worth seeing if we can kick the mono lines from PAS [03:23] * ScottK knows just that he wants the fricking package to build. [03:23] Well, either way ... [03:24] NCommander: Let's get pimlibs built on sparc before another upload first, so it'll have a chance there too. [03:24] That just needs a publisher run followed by a rescore. [03:25] stupid question: is porting a feature to a new architecture (i.e., fixing mono on HPPA) affected by feature freeze? [03:26] NCommander: Was the lack of Mono a design decision or a bug? [03:26] I think the HPPA porting group just never realized mono was ported [03:26] who has HPPA hardware? [03:26] Physical, or access to one? [03:26] Amaranth, lamont :-) [03:27] NCommander: He runs a KDE desktop on there? :) [03:28] dunno [03:28] Its a sticking point with me tha tKDE been broken on HPPA [03:28] (actually, just having a hosed port is :-P) === Skiessi is now known as Guest424255 [04:09] cjwatson: I have managed to get the ia64 kernel down to 10MB, which will appear to just fit inside boot.img. I can't go any smaller without sacrificing functionality. A lot of stuff was disabled and/or built in for the last kernel as it was. [04:11] NCommander: so you made the fix to glibc? I thought the fix had to be done in the kernel. [04:14] TheMuso, no, I made it to the kernel [04:14] NCommander: ah ok [04:15] TheMuso, ah, the sparc kernel just finished [04:15] (like five seconds ago :-) [04:15] timing [04:15] But ... [04:15] I built the wrong kernel [04:15] wait [04:15] Hold on [04:16] * NCommander is an idiot ... [04:17] NCommander: java/hppa vs doko is a long standing frustration of his. [04:18] lamont, I take it is a chicken and the egg problem because to bootstrap OpenJDK, you need a JDK already in place, right? [04:20] NCommander: doko was at least smashing his head against openjdk/hppa, iirc. until he got tired of the threads/kernel/libc/whatever-the-hell-it-really-is bug [04:20] lamont, which seems to have gone away-ish [04:20] the one that has me rapidly approaching the point where I craft the email to ubuntu-devel-announce announcing the retirement of the hppa port from ubuntu [04:21] ish being the operative word [04:21] mostly, we just don't giveback things that we know kill it [04:21] lamont, well, I haven't experienced the fun it caused with Ruby [04:21] because, well, it hurts when we do that [04:21] NCommander: coolness [04:21] * NCommander was one of the people who helped debug ruby on HPPA [04:21] I'd like to drop jaunty's kernel on the porting box and see if it works. [04:21] ^- better. [04:22] (and then run glibc's test suite to see what our breakage level is at) [04:23] NCommander: here's a test for you: pick anything amusingly interesting from _DAPPER_ and build it in a dapper+security chroot on that jaunty kernel - needs to work [04:23] at least until jun 2011 [04:23] I don't have a HPPA box I can install kernels on [04:23] * NCommander has root at an HPPA box at HP, but thats on the other side of the US for me ... [04:25] *sighs* [04:25] * NCommander grabs a handbook on SPARC ASM [04:27] lamont, is there a HPPA virtualization solution? (I've been trying to find an actual HPPA box for some time, but they're damn pricy, even used :-/) [04:28] no solution that I know of [04:28] know where I can get a cheap box? [04:29] * lamont was part of an investigation into virtualizing hppa in about 1992ish, that determined that it would certainly require guest knowledge in lots of places, and then we dropped that [04:30] ok, sparc should be fixed soonish [04:31] * NCommander grumbles and backports more fixes [04:32] lamont, side issue, do you have access to the HPPA build chroots? They're misconfigured to disallow installing unsigned packages. I had a fun build failure in a devirtualized PPA due to that :-/ [04:39] I'm gonna go with "no" to that, even though rules-lawyers might disagree [04:39] lamont, rules-lawyers? [04:40] NCommander: I have root on just about every machine in the data center. and the others I have console on. [04:40] oh, I see [04:41] mostly, I'm just tired enough to not want to even understand the issue, let alone fix it. [04:41] which reminds me... I need to deal with the debian release on the debian/hppa buildd machines [04:43] lamont, this leads me to my next question on why HPPA is so bleck :-/. I do remember when it was a fairly loved architecture in Debian (before NPTL ...) [04:43] and there you go answering your own wquestion [04:43] Oh [04:43] I'm just suprised HP hasn't sponsored work on it [04:44] * lamont goes back to the pain that he knows, with: apt-get remove --purge libvirt-bin [04:45] ouch [04:45] * NCommander just wish PA-RISC boxs didn't command such a high price on ebay [04:48] hppa didn't even get bootstrapped until late 2000 iirc [04:48] join #fedora [04:49] Well, HP seems to be fairly bipolar on it; I see them moving to IA-64, and yet HPPA is quite common from what I see on their server offerings [04:50] NCommander: iirc ia64 was supposed to be the replacement... except that ia64 wasn't that great (aiui) once it actually came out [04:50] Well, ia64's are fairly cheap if your not too picky [04:50] Someone told me at UDS that the ia64's in the data center were ebay specials ... [04:52] NCommander: probably cheap because they aren't very useful, heh [04:53] well, I can find plenty of SPARCStation 20's for less than 200 bucks. Might just snag one for installation testing [04:57] sparcstation 20 won't run ubuntu, iircf [04:57] bah [04:58] So HP-UX supports Java, so pa-risc support is there [04:58] * NCommander takes a look to see if the code to support it is there ... [05:25] hi all, quick q on building packages. What mechanism generates the .changes file once all of the .debs and sources are placed into the parent directory of the source? [05:26] oh, nm. I need caffeine [05:33] It looks like at least libgpod-nogtk-dev and possible other binaries from libgpod have fallen into Universe for some archs (e.g. for i386, but no am64). I was wondering it an archive admin is around who would clean that up? [05:40] good morning [05:43] bryce: wow... my gdm is in explosion loop of death and I can only click "OK" [05:51] does anybody of you have something like this in your gdm log? [05:51] error setting MTRR (base = 0xe0000000, size = 0x08000000, type = 1) Invalid argument (22) [05:51] ddxSigGiveUp: Closing log [05:52] I believe gdm when it tells me that the xkbcomp problems are not fatal [05:52] > Warning: Type "ONE_LEVEL" has 1 levels, but has 2 symbols [05:52] > Ignoring extra symbols [05:54] "error setting MTRR" - that's a hardware matter [05:54] definitely no such error in my logs [05:55] I dist-upgaded and restarted - that's what it looks like now (on my nv amd64) [05:55] my i386 laptop works fine [05:55] and on the amd64 I can't switch to the consoles now [05:55] which sucks [05:56] slangasek, can you retry the livefs build for ubuntu dvd? yesterdays didn't come out, and we were counting on some fix(es) in it. [06:02] https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/331292 [06:02] Ubuntu bug 331292 in gdm "gdmgreeter crashed with SIGSEGV in __libc_start_main()" [Undecided,New] [06:02] superm1: yep, running [06:02] I guess that's my issue [06:03] what happened to bulletproof X? [06:03] :-((( [06:04] hum, maybe it's not [06:04] I wasn't using nvidia [06:05] heh with my video chipsets whenever X really fails it tends to lock everything with it... [06:05] I once had a mismatch between the kernel blob and userland that triggered hardlocks... === slangasek changed the topic of #ubuntu-devel to: Archive: feature-frozen | alpha-4 released | Ubuntu 8.10 released! | Development of Ubuntu (not support, not app development on Ubuntu) | #ubuntu for support and general discussion for dapper-intrepid | #ubuntu-motu for getting involved in development | http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://wiki.ubuntu.com/HelpingWithBugs [06:08] what about http://people.ubuntu.com/~dholbach/new-nm-dialogue.png - do we really mean to have that dialogue? [06:09] and why does gnome-terminal crash on me? [06:09] today is not going to be my day, I just know it [06:11] oh it is definitely one of those weeks where just about everything goes wrong :) [06:11] to pile up on my fun stuff this week I lost both of my Firefox profiles... on the same day... independent systems same bug :) [06:13] ok... xdm instead of gdm works [06:16] dholbach: Apps that try to use notification-daemon with buttons get an error that they think means notification-daemon isn't running and fall back to showing a dialog [06:16] I like how the "You are now running on battery power" dialog has a Cancel button [06:17] Maybe if I click it the computer will automatically attach the power cord again [06:17] I'm not sure those dialogues help with anything [06:17] They don't, it's something no one ever actually saw before because notifications always worked [06:18] dholbach: does 5-a-day-stats get automatically updated by just joining the group now? [06:19] Amaranth: That's apparently supposed to act as a reminder to patch those applications. [06:19] calc: that's the plan - I still have to do some work to do for that [06:19] dholbach: ok [06:19] calc: now that I can log in to GNOME again, I'm one step closer to doing it :) [06:19] dholbach: heh :) [06:20] ok, it's bug 331324 [06:20] Bug 331324 on http://launchpad.net/bugs/331324 is private [06:22] Can any of the archive admins please rescore libdvdread on ia64, hppa and armel? It is stuck at score 3255 for more than 30 hours. [06:25] slytherin: no. Done. [06:25] (you need a buildd admin, not an archive admin) [06:28] Mithrandir: thanks [06:28] slytherin: There is a bit of a line tonight. [06:32] ScottK: though, if people are actively waiting for something to build, I'm happy to rescore it so they don't get blocked. [06:33] Mithrandir: Sure, I just mentioned it in there interests of 'nothing's wronge except everyone uploading tons the day before FF.' [06:33] oh, sure. === tkamppeter_ is now known as tkamppeter [07:13] superm1: still fails to build; langpack conflicts [07:13] looks like it's because of the long build queues [07:40] Does anyone know if mom data is available in xml or csv or somthing? === thekorn_ is now known as thekorn [08:09] Good morning [08:09] Hi [08:12] Good morning pitti [08:14] morning [08:14] pitti: Good morning. [08:16] pitti: do you know why bug 330621 was not retraced yet? [08:16] Bug 330621 on http://launchpad.net/bugs/330621 is private [08:21] pitti: good morning, can I talk with you for a minute? :) [08:48] Meh, X froze again while I was showering [08:48] PecisDarbs: pong [08:49] dholbach: when was it filed? [08:50] pitti: nm, saw your conversation with seb128 about the retracer [08:50] dholbach: "my conversation"? [08:50] it might be stuck again, but I didn't get a warning mail [08:50] * pitti checks [08:52] dholbach: oh, was it amd64? the retracer got stuck apparently [08:52] * pitti restarts it [08:52] seb128: ^ FYI [08:52] pitti: cf #distro [08:52] pitti: stop ignoring me there dude ;-) [08:52] seb128: didn't see anything [08:52] pitti, mine is freezing as well (we seem to share a lot of hardware!). I also have to log in twice to gdm. Is that a known issue? [08:53] beuno: happens to me, sometimes, a few minutes after suspend from hibernate; otherwise it's behaving [08:54] pitti, it has happened to me twice in the past few days, but not related to hibernating or suspending, unfortunetly [08:56] beuno: can you still ssh in? [08:56] beuno: I can, and I tried stracing X, and got a busy loop with [08:56] --- SIGALRM (Alarm clock) @ 0 (0) --- [08:56] sigreturn() = ? (mask now []) [08:56] ioctl(11, 0x40046445, 0xbfb8e4a4) = -1 EINTR (Interrupted system call) [08:57] pitti, ah, I haven't tried. Will do next time. === kagou` is now known as kagou [09:00] <\sh> soren: you have main powers, right? would you like to review bug #331410 (jaunty debdiff) for net-snmp [09:00] Launchpad bug 331410 in net-snmp "CVE-2008-6123: not fixed in latest security releases" [Undecided,In progress] https://launchpad.net/bugs/331410 [09:01] beuno: me too, I'll check if it's the same next time [09:01] beuno: oh, and I just tried stracing X in X; don't do that... [09:01] gives a nice lockup :) [09:02] hahah [09:02] :-D === GuilhermeCunha is now known as guilhermeCunha [09:03] ssh'ing in and kill -9'ing strace recovers, though [09:03] pitti, other than those two things, Jaunty seems much more solid than Intrepid [09:03] tseliot: btw, did GNOME stop respecting .config/monitors.xml a week ago (or so) as well? [09:04] tseliot: that's pretty nasty, I always have to start the session with reconfiguring screens, compiz --replace, killall gnome-panel.. [09:04] beuno: what hardware do you have? [09:04] * pitti -> back in 5 [09:04] pitti: no, did you file a bug report about it? [09:05] pitti, dell xps1330 with GM965 and 3945ABG [09:08] pitti: if you do, I'll be happy to fix that [09:15] tseliot: yes, I did, let me find it [09:16] tseliot: bug 329410 [09:16] Launchpad bug 329410 in gnome-control-center "does not set configured resolutions at GNOME startup any more" [Undecided,New] https://launchpad.net/bugs/329410 [09:16] tseliot: .config/monitors.xml didn't change AFAICS (did it?), so it seems that gnome-settings-daemon or whatever else is responsible for reading and acting on it doesn't work any more? [09:18] pitti: no but there can be different (temporay) configuration files. I'll try to reproduce the problem here and I'll fix it [09:21] tseliot: it just seemed to coincide with the new-style capplet (separate on/off, and so on) [09:21] might be pure coincidence, though [09:21] tseliot: is g-settings-daemon the piece that should read it? [09:22] pitti: yes, through libgnome-desktop. [09:22] ah [09:22] tseliot: so maybe something was ported to drop libgnome? [09:22] pitti: I've done some serious work on it therefore I should be able to figure out where the problem lies [09:22] * debian/control.in: [09:22] - the new version doesn't require libesd, libpulse, libgnomeui [09:22] gnome-settings-daemon (2.25.2-0ubuntu1) jaunty; urgency=low [09:23] I doubt they can be the cause of the problem [09:23] ah, no, that's too old [09:23] it just stopped working a week ago or so [09:24] I have some suspects ;) === guilhermeCunha is now known as GuilhermeCunha- [09:43] ArneGoetje: hardy/intrepid-proposed langpacks accepted [09:51] NCommander: java/hppa> absolutely no idea [09:52] TheMuso: ia64 kernel> thanks, sounds good [09:59] pitti: did a changes in sl-modem-daemon.init patch you suggested, a little bit optimized all alsaload along the way. Patch attached to bug report. [09:59] PecisDarbs: great, thanks [10:00] hello, i'd like to propose some enhancements to the display manager applet, is there anyone that is in charge with it? [10:01] anyone on current KDE? can you tell me where Konqueror stores its cookie file/database? [10:02] majeru: display manager applet? you mean the fast user switcher in the panel, with your name and status? [10:02] no, i mean that one that may change the screen resolution [10:02] majeru: tseliot primarily [10:02] ok, thanks [10:03] majeru: what's the problem? === Nicke_ is now known as Nicke [10:05] there's no problem, i have some usability proposals [10:06] mostly for those people with multiple display setups [10:06] like having profiles accessible from the notification menu [10:07] and sub-menus for each display's resoluton [10:07] majeru: can you file a bug about it and send me a link to it, please? I'll have a look at it later [10:07]