billisnicewhat programming language is mainly used in Ubuntu development?00:09
TheMusobillisnice: Python is used a fair bit.00:21
cjwatsonalso quite a bit of C (and too many other languages to list, at varying concentrations), and packaging requires make and shell00:23
cjwatsonflexibility to pick up new languages quickly is more important than raw proficiency in any single language, IMO00:23
hdoncjwatson: yes, thanks, someone else already schooled me about those particular macros ;)00:49
LlamaZorzHey guys,does anybody know when firefox forks for the flash plugin?00:59
slangasekjames_w: debian/squeeze/egenix-mx-base also out of date01:16
slangasekjames_w: in this case, debian/egenix-mx-base also appears to be out of date01:17
=== yofel_ is now known as yofel
* cody-somerville wonders why dbus-daemon would be eating up 30-50% cpu.01:57
fagancody-somerville: it depends on the traffic01:59
faganits either that or its a bug01:59
cody-somervillestrace shows it polling over and over and over and each time it says resource unavailable01:59
cody-somervilleI'm thinking its a bug in gnome-system-monitor since gnome-system-monitor is refusing to exit now01:59
m4tdbus-monitor show anything?02:00
cody-somervilleoh yes02:00
cody-somervillejust as I suspected02:00
fagangnome-system-monitor is a hog anyway02:00
m4thrm which monitors do you have enabled?02:00
cody-somervilleI think its trying to get info about two loop back devices I have mounted02:01
faganAre the devices properly mounted and recognised at the moment?02:01
m4tmaybe i have 'gnome-system-monitor' confused with the system monitor panel applet02:03
faganm4t: system>admin>system monitor02:03
m4tyea. /usr/bin/gnome-system-monitor02:03
cody-somervilleit was actually the cd in my cdrom drive that was the problem02:03
cody-somervilleafter ejecting it, gnome-system-monitor quit and dbus is much quieter now.02:04
* m4t uses htop for that sort of thing02:04
m4tno pretty graphs though02:04
* fagan doesnt use cds anymore02:04
* fagan loves the pretty graphs02:05
faganI cant wait for the UDS :)02:07
chrisccoulsoncody-somerville - i've seen that issue with gnome-system-monitor as well (and there's a bug report for it too)02:09
chrisccoulsonit actually seems like a loop in gvfs somewhere02:10
fagancody-somerville: how do you force an upgrade to lucid?02:10
* fagan got it, good google :)02:13
sconklinI am obviously missing something - how can I change the date in karmic - I need to set it into the past to workaround a bug02:25
sconklinThe admin applet changes it back, even though manual configuration is selected02:26
mustakrakishneed help with PGP key for repo's http://paste.ubuntu.com/316517/02:30
mustakrakishneed help with *GPG key for repo's http://paste.ubuntu.com/316517/02:32
cjwatsonmustakrakish: #ubuntu, please02:33
maxbmustakrakish: That is not a development question, so is offtopic for this channel. Please see the general user support channel, which is #ubuntu .02:34
=== jtimbermo is now known as jtimberman
fagannew_to_linux: hi02:57
new_to_linuxplease help, there is no install button in ubuntu software centre02:58
new_to_linuxi just switched from windows02:58
ScottKnew_to_linux: The best channel for getting questions like that answered in #ubuntu.02:58
new_to_linuxScottK: thanks02:58
=== asac_ is now known as asac
dholbachgood morning07:46
dholbachhi smwn07:47
smwncan I hear a w00p07:50
pittiGood morning07:50
dholbachsmwn: http://photos-c.ak.fbcdn.net/hphotos-ak-snc1/hs202.snc1/6935_251765935091_893075091_8788600_1697850_n.jpg07:50
=== dholbach_ is now known as dholbach
=== dpm_ is now known as dpm
=== tkamppeter_ is now known as tkamppeter
=== highvolt1ge is now known as highvoltage
=== highvolt1ge is now known as highvoltage
=== evand is now known as ev
liwtkamppeter, I got my Brother label printer to work yesterday; what's the best way to get that support included in Ubuntu (on the assumption that I don't want to maintain it myself)? should I file a bug and if so, against which package?11:08
=== akgraner_ is now known as akgraner
tkamppeterliw, how did you get your printer to work? Did you download a driver? Is the driver free software? Is it from Brother11:50
tkamppeterpitti, hi11:51
pittihi tkamppeter11:51
* pitti fiddles with tzdata's 3.0 package format until it works with launchpad again11:52
tkamppeterpitti, it is about the auto-downloadable drivers. Does Ubuntu ship any download keys for any hardware manufacturers, like NVidia or so?11:59
Riddellpitti: amichair is a new member of Team Kubuntu and has been fixing various bugs in Kubuntu apps recently.  he's looking at jockey-kde today and may have some questions to get into the codebase12:00
pittiRiddell: oh, great12:01
pittiamichair: hello :)12:01
pittitkamppeter: no, not right now12:01
amichairpitti: hey there12:01
pittitkamppeter: ideally we wouldn't need to, and just download them on demand; that would require them to be signed by a key that we already trust, though12:02
pittitkamppeter: (well, we need to trust the key either way)12:02
amichairpitti: first thing, I'm just looking through jokey-kde bug reports, and I can't quite distinguish between backend and gui bugs (most of them just say 'crash') - do u have more specific info on something I can start out with?12:04
amichairpitti: second, I notice there are a bunch of sys.exits around - is this normal? is there nothing requiring orderly shutdown in there?12:05
pittiamichair: I'm afraid you have to look at the stack trace; a d-bus error is a backend crash, while most of the rest (sigsegv, etc.) are most probably bugs in python-qt4 or python-kde412:05
pittiamichair: without calling sys.exit(), there are some remaining processes/threads which aren't autocleaned for some reason12:06
amichairpitti: hmmm...12:06
pittiamichair: bug 458662 is similar12:07
ubottuLaunchpad bug 458662 in apport "apport-kde: "Invalid problem report: Package nonexistentarg does not exist" => OK => still "Collecting problem information" dialog" [Low,Fix released] https://launchpad.net/bugs/45866212:07
pittiamichair: (please note that I didn't actually write most of jockey-kde)12:07
amichairpitti: (and I have no previous dev experience with linux, kubuntu, kde, qt or pythong... I think we'll make a great team! :-) )12:08
tkamppeterpitti, the concept is that manufacturers supply the keys and the distros include the keys from manufacturers which they trust.12:08
pittitkamppeter: well, those are two different "trust" here12:08
pittitkamppeter: we can decide which manufacturer we trust to build good packages -- those are the ones which we can offer12:08
pittitkamppeter: but trusting a key is entirely different, it requires identity verification12:09
tkamppeterpitti, this way the distros have to trust the manufacturers and not the LF and only manufacturers and not the LF take responsibility.12:09
liwtkamppeter, http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=555892 has details12:09
ubottuDebian bug 555892 in wnpp "RFP: ptouch-driver -- CUPS/Foomatic driver for Brother P-touch label printers" [Normal,Open]12:09
pittii. e. a trusted path through signatures to their key12:09
pittitkamppeter: so, if the manufacturer's key is signed by someone who we trust, we can just download it on demand; but conversely, if we can't trust the manufacturer's key, then shipping the key by default doesn't increase the confidence in it by any way12:10
pitti(to the contrary, we would make ourselves untrustworthy with key handling)12:10
tkamppeterpitti, so what do I need to tell the manufacturers what they have to do with their keys so that their packages get auto-downloaded? Who must sign their keys so that all distros accept their keys?12:12
directhexare we not autosyncing new packages from squeeze?12:13
ScottKWe are.12:14
ScottKAutosync is not, however, a continuous process12:14
Keybukor, in fact, an automatic process ;)12:14
ScottKIt's done periodically.12:14
ScottKThat too12:15
directhexhow periodic? the packages i'm noticing were all in squeeze when karmic shipped12:15
pittitkamppeter: well, you know how key signing works?12:15
ScottKWell it's run once since then.12:15
pittitkamppeter: either there's a central authority (like the LF) that generates a key and signs driver manufacturer keys, or we have to meet with them directly to sign them12:16
pittitkamppeter: in the first case, all distros would sign the LF key, and the LF woudl sign all the manufacturer keys; in the second case, each distro has to sign each manufacturer key12:16
slangasekdirecthex: it's conceivable that there hasn't been a new package sync run yet, I know I didn't make it that far on archive day on account of spending my time updating the sync blacklist for existing packages instead12:19
slangasekKeybuk: have some time to talk about boot-time hdparm settings?12:19
directhexslangasek, oh, debian syncs still go into binary NEW don't they? let me check12:19
tkamppeterI know about keysigning session where people meet physically and sign the GPG keys of each other, is a physical meeting of a Ubuntu/Canonical representative with one representative of each manufacturer needed for this signing? Or is there a way by internet and phone to do this?12:19
Keybukslangasek: sure12:20
tkamppeterpitti: ^^12:20
slangasekKeybuk: so it's a no-brainer that the current behavior, which may cause multi-second delays at boot time, is wrong; but I think we still need to be setting the configured apm policy at boot time12:21
Keybukslangasek: "still" ?12:21
Keybukwe don't set that right now12:21
Keybukthe hdparm udev rule comes from the days where we had to futz with DMA settings and stuff12:22
slangasekhmm, we do, actually... though perhaps we only set it via /etc/init.d/acpi-support12:22
Keybukobviously since libata, that isn't used12:22
Keybukslangasek: I just grepped through that, couldn't find anything about hdparm12:22
Keybukwing-commander /etc% grep -r hdparm init init.d acpi power pm12:22
Keybukinit.d/bootlogd:# X-Start-Before:    hostname keymap keyboard-setup procps pcmcia hwclock hwclockfirst hdparm hibernate-clean12:22
pittitkamppeter: you can't do it by internet, since the purpose of this is to have physical evidence that the key creator is actually the one he pretends to be ("can't pull yourself out of the swamp")12:22
slangasekKeybuk: /etc/init.d/acpi-support calls /etc/acpi/power.sh calls pm-powersave calls /usr/lib/pm-utils/power.d/95hdparm-apm12:23
tkamppeterliw, you tell in the Debian bug report that you have reported your problems upstream. Did you get any answer from the upstream author?12:23
Keybukslangasek: got you12:23
liwtkamppeter, not yet12:23
pittitkamppeter: phone is better, but not as trustworthy than seeing someone in an office, with a passport, etc.12:23
directhexslangasek, nope, doesn't look that way. remind me to check next time the sync run happens12:23
Keybukslangasek: is that one of our scripts, or an upstream one?12:23
slangasekKeybuk: dunno offhand; can check12:24
Keybukslangasek: you were thinking we should do that by calling out to hdparm on the drive in a udev rule instead?12:24
slangasekKeybuk: now as for the current udev script not doing apm settings... it applies any settings the user has configured in /etc/hdparm.conf, including apm and spindown, and nothing else does this by default12:25
slangasek(granted, that's not where we configure the system default apm settings, so yes, by default that part is a no-op)12:25
tkamppeterpitti: The problem with a key at the LF is that this could imply that the LF would take responsability on the manufacturer's driver packages.12:26
pittitkamppeter: if the manufacturer has a working SSL certificate, they might also put the key and fingerprint on their web page (with https); that might actually work better12:27
pittitkamppeter: as I said, trusting a key and trusting a package are completely independent12:27
slangasekKeybuk: the point I think we want to get to is that there's a single call to hdparm for each drive at the very end of the init sequence for any drives then available, and a udev rule that picks up any drives added after12:27
pittitkamppeter: just because I am convinced that a key that says "Joe Sixpack" really belongs to a physical person "Joe Sixpack" does not mean that I trust any of his actions :)12:28
tkamppeterWorking SSL certificate meas that their site is trusted by some certification authority?12:28
liwtkamppeter, I need to leave now; when you have time, if you can check the Debian bug I referred to for the ptouch-driver package, that would be most helpful, thanks12:28
pittitkamppeter: yes12:28
slangasekthat would mitigate the effects of hdparm on boot performance12:28
pittithe chain has to start somewhere with a physical identity proof12:28
slangasek(and if the udev rule itself is doing things that are inappropriate, we can fix that along the way)12:28
tkamppeterpitti, will that be enough to trust the manufacturer's keys when they come from this site with SSL certificate via https?12:29
Keybukslangasek: it's not the effect of hdparm I care about12:29
Keybukjust the unconditional sync in the existing rule ;)12:29
pittitkamppeter: well, "enough" is a matter of taste, but I think for these purposes yes12:30
Keybukudev doesn'tre12:30
pittitkamppeter: since otherwise people would download them directly from their web site, which involves the same trust (SSL cert)12:30
Keybukudev doesn't really work in a "don't do it during boot but do it later" kind of way12:30
Keybukfrankly even upstart doesn't have a "very end of the init sequence" kinda thing12:30
Keybukwouldn't it be better to do the hdparm calls for each drive from udev12:30
slangasekKeybuk: right; I don't understand why that unconditional sync is there, but the effect is obvious12:30
Keybukincluding setting user settings and apm settings?12:30
Keybukthat way you get a single hdparm call per drive12:31
Keybukwhich is called before the drive is actually used12:31
slangasekKeybuk: well, <cough> users with /usr on a separate partition aren't guaranteed to have the on_ac_power command available when the udev rule runs, so we would still have to re-apply the correct apm setting later12:32
Keybukslangasek: is that the thing in /usr/bin that only looks in /proc and /sys ? :p12:32
Keybukand is only in /usr because someone wrote it in awk12:32
tkamppeterpitti, so what I have to tell the manufacturers is to have an SSL certificate for their site from which the keys and packages should gget downloaded?12:33
slangasekit's also in /usr because it's not related to system recovery12:33
Keybukwould probably be better to fix *that*12:33
Keybuksince we already have the "can't call on_ac_power to decide whether to fsck /usr" thing :p12:33
slangasekyeah, that's a possibility12:33
pittitkamppeter: well, either we need to sign their GPG key, or they must have an officially signed SSL cert and put the key/fingerprint on their website12:33
tkamppeterpitti, are there any requirements on where to place the keys relative to the packages so that the download tools find it?12:34
slangasekok; so if we get on_ac_power in /bin where we can rely on it, then we can use the udev rule for all boot-time settings, and just arrange to make pm-powersave not call hdparm when invoked from init12:34
pittitkamppeter: if the GPG keys have a proper signature, they should just be on the keyserver network12:34
slangasekand then remove that sync if we can confirm it's bogus12:34
pittitkamppeter: if not, then we need to include them (in jockey or whereever)12:34
slangasekKeybuk: ^^ sound right?12:34
Keybukslangasek: yup12:35
slangasekKeybuk: cheers :)12:35
Keybukslangasek: the sync is almost certainly bogus in Ubuntu12:35
KeybukI can imagine why it's there in Debian12:35
Keybuk(udev runs after things are mounted)12:35
KeybukI can't think of any way a udev rule could run on a mounted filesystem ;)12:36
slangasekwhy does udev run after things are mounted in Debian, either?12:36
Keybukslangasek: I haven't looked at Debian in a while, but udev used to run very late12:36
Keybuklike after /usr was mounted12:37
Keybukit wasn't always there though, right?12:37
tkamppeterpitti, what I now need to do is to put together some step-by-step instructions of generating keys, getting them signed or getting them onto an SSL-certified web site, what to provide to the download tools and where, ... Note for that that many manufacturers are not very Linux-aware.12:37
Keybukthe hdparm udev rule is old ;)12:37
Keybukand converted from an even older init script12:37
Keybukslangasek: ah12:38
Keybukbut S03udev just means udevd12:38
slangasekKeybuk: I don't see any record in the udev package of an init script migration12:38
Keybukyou could still have the block device appear later? even though it's already been mounted12:38
Keybukslangasek: I'm only guessing :)12:39
slangasekhrm, how would it /get/ mounted in that case?  static device node?12:39
slangasekS03udev includes udevadm trigger/settle calls12:39
slangaseklet me dig through the hdparm package, to see why this rule /really/ does what it does12:40
Keybukat least we absolutely guarantee that we don't mount things until udev is done with them :p12:40
Keybukslangasek: oh, I think it's always been there12:40
* Keybuk wrote that script12:40
slangasekoh? :)12:40
Keybukand it looks like I just copied that from the old init script12:40
slangasekodd, the changelog says thom wrote it12:40
Keybukthom uploaded it12:41
* Keybuk was on the Launchpad team at the time12:41
Keybuk(technically :p)12:41
Keybukthat was a good UDS12:42
slangasekyeah, this -q -f goes all the way back to warty12:44
Keybukslangasek: hole in the ground, with water in it12:45
yoshi765DAMN UBUNTU12:46
Tm_T!op | yoshi76512:46
ubottuyoshi765: Help! bhale, infinity, Hobbsee, jdub, thom, fooishbar, fabbione, mdz, lamont, or Keybuk12:46
slangasekyoshi765: not an appropriate use of this channel.12:46
Hobbseeclearly going to have a lot to say...12:47
Tm_THobbsee: shame this is one of the few channels I don't have rights ):12:48
Hobbseeheh :)12:48
* Tm_T doesn't like just watch when there's some cleaning to do12:49
=== pedro__ is now known as pedro_
=== debfx_ is now known as debfx
amichairpitti: when selecting to activate a driver in jockey, is there anything done that might take a long time? does it download anything? or it's supposed to be pretty much immediate?13:11
pittiamichair: sorry, was at lunch; yes, it will take a long time, which is why it spawns a progress dialog13:25
pittiit needs to download, unpack, install, etc.13:25
amichairpitti: ok, my test did a quick one so didn't see progress bar, and wondered if I should add one :-)13:26
pittiamichair: there should be one already; it works for me, anyway13:27
amichairpitti: ok, thanks13:29
pittitkamppeter: instead of adding the "LogDebugHistory" to cupsd.conf in a patch, can you please just change the internal default? This will (1) keep the setting for admins who changed it, and (2) avoid a conffile change13:31
pittitkamppeter: also, I think "2000" is a more reasonable limit than "999999" -- the latter would potentially result in a 100 MB log file13:32
=== chuck_ is now known as zul
=== kklimond- is now known as kklimonda
tkamppeterpitti, I would leave the big value, as this makes the logging more or less unlimited. There should not be that many "DEBUG:" messages in the filters. Up to now in user-supplied error_logs in bug reports such an excess never happened.13:42
tkamppeterpitti, it is worse if some lines are missing in a user-supplied error_log.13:42
pittibut if they do, it'd be more or like a DoS of hard disk and bug trackers13:42
pittiwell, but a million lines?13:43
pittiif there's something logging more than 1000 lines about an incident, this is certianly of questionable utility?13:43
tkamppeterA million lines is never reached. 10000 will perhaps happen.13:43
pittiso, let's make it 10000 then?13:44
slangasekKeybuk: hmm, the awk stuff is only used for PMU and APM... could just ignore this :-P13:44
slangasekKeybuk: do you happen to know if non-apci systems shoul also have /sys/class/power_supply/?13:45
Keybukslangasek: they should13:45
Keybukwhether they do yet or not ...13:45
Keybukwhy is gdb skipping the entire body of the function when I do "n"13:46
* Keybuk blames kees13:46
slangasekso I could move that block outside of the "if /sbin/acpi_available" check, and make the awk stuff Somebody Else's Problem13:46
pittitkamppeter: FYI, I'm updating to 1.4.2 to grab the security fix13:47
tkamppeterpitti, I will add a fix to pdftopdf, got it from Otani-san today.13:47
tkamppeterpitti, you have reverted my last commit?13:49
Keybukdoko: around?13:53
sladenpitti: how should I poke apport to stop it reporting particular seahorse-agent crash dumps.  There's a couple of thousand dups to bug #429322 (to the point that it has broken LP) and more stack-trace uploads probably aren't really necessary13:54
ubottuLaunchpad bug 429322 in seahorse-plugins "seahorse-agent assert failure: ERROR:iop-profiles.c:606:IOP_generate_profiles: assertion failed: (obj && (obj->profile_list == NULL) && obj->orb)" [High,Confirmed] https://launchpad.net/bugs/42932213:54
pittislangasek: there is an apport bug pattern for it since Tuesday or so13:54
pittiso it shouldn't even be possible to report further dups13:54
pitti(and yay for the bug which kept apport enabled after stable release :-( )13:55
tkamppeterpitti, pdftopdf fix from Otani-san is committed.13:56
sladenpitti: the dups are still arriving, or so that just the tracer catching up13:56
dokoKeybuk: otp13:56
pittisladen: retracers still have a huge backlog unfortunately13:57
pitti(for the same reason, swamped after final release)13:57
Keybukdoko: when you get back, gcc appears to have deleted the entire body of a function when compiling with -O0 ... how would I debug that ? ;p13:58
maxbjames_w: Hi, are you around today? I was wondering if you could comment on bug 48109714:06
ubottuLaunchpad bug 481097 in udd "subversion 1.6.6dfsg-1 in Debian not imported to branch" [Undecided,New] https://launchpad.net/bugs/48109714:06
dokoKeybuk: hmm, do you have a test case? when did this "optimization" start?14:06
pittitkamppeter: btw, I'm going to do an upload now, but I fully expect that I have to do another one next week or so (new poppler in Debian didn't build yet everywhere, and I need to test it on mips again for the PIE issue)14:13
pittitkamppeter: so, if you have other pending fixes they don't need to wait long14:13
tkamppeterpitti, I have also done the LogDebugHistory fix now.14:13
pittiah, thanks14:13
tkamppeterSimply bzr pull and you have it.14:13
* pitti cancels build and builds again14:13
Keybukdoko: s'ok, was a code error ;)14:20
Keybuksilly upsream14:20
Keybukif (console->fd < 0);14:20
Keybuk  return14:20
=== chuck_ is now known as zul
tkamppeterpitti, can you help me on getting step-by-step instructions together for the manufacturers about generating keys, signing them or putting them on an SSL-certified site, signing the packages, so that users can easily get their drivers auto-downloaded?15:03
=== mbarnett` is now known as mbarnett
=== Keybuk_ is now known as Keybuk
=== dendro-afk is now known as dendrobates
=== chuck_ is now known as zul
theclaweverytime firefox gets updated, the "quick search" entries get replaced/updated15:48
theclawis this behaviour wanted?15:48
dholbachpitti: do you have access to robert_ancell's seahorse fix?16:11
dholbachpitti: there's like 3000 subscribers on the bug already16:12
dholbachmostly due to duplicates16:12
pittitkamppeter: there's plenty of tutorials already; let's sit down next week and write/link something16:47
pittidholbach: it should already be in karmic-proposed16:47
pittidholbach: what do you mean with "access"?16:47
dholbachpitti: the bug is timing out in LP - good to know the fix is on its way :)16:47
pittidholbach: yeah, took me like ten times to get the page, too :-(16:48
pittimail responses FTW16:48
Riddellseb128: where did you upload the fix for bug 462049 to, lubic or -proposed?17:00
ubottuLaunchpad bug 462049 in libindicate "Plasma crashes unexpectedly" [High,Fix committed] https://launchpad.net/bugs/46204917:00
jussi01Riddell: did you notice my comment about the links to kubuntu stuff on summit this morning?17:01
Riddelljussi01: nope, what was that?17:01
seb128Riddell, proposed we pocket copy then17:03
jdonglubic :)17:03
seb128Riddell, why?17:03
jussi01Riddell: just that the links on the summit calendar pages go to non-existant wiki pages when they should go to the corresponding LP pages...17:03
Riddellseb128: I just didn't see it in the queue, but there it is now17:03
jussi01Riddell: click on kubuntu lucid development here for instance: http://summit.ubuntu.com/uds-l/2009-11-16/17:03
Riddelljussi01: I have complained about this but I don't know if I complained to the right person and I probably didn't complain in the right way17:04
jussi01Riddell: ok, Ill go annoy jorge and jono about it17:04
jussi01Riddell: Ill try make sure it happens17:05
Riddellpitti: mind if I accept the SRU for bug 462049 into -proposed?  upstream are getting grumpy about it17:08
ubottuLaunchpad bug 462049 in libindicate "Plasma crashes unexpectedly" [High,Fix committed] https://launchpad.net/bugs/46204917:08
mvodo we have a wiki page that gives a step-by-step instruction how to do/trigger a fsck on the root fs?17:08
* pitti adds "daily SRU round, take III" to his queue17:08
pittiRiddell: will do17:08
pittimvo: wouldn't tune2fs -C 50 /dev/... do?17:09
pittithat's what I usually do for testing17:09
ubottufsck is the FileSystem ChecKer, which runs automatically when you boot if you didn't shutdown cleanly. Type "man fsck" for information on running it manually. The command "sudo shutdown -F -r now" will force a reboot and a filesystem check; "sudo touch /fastboot" will skip a filesystem check at next reboot17:09
jussi01mvo: ^^17:09
mvopitti: this is similar to what I usually do, but I wonder if that is the way that we suggest to our users17:09
pittimvo: well, I'd recommend -C 50; less dangerous to your data :)17:09
pittimvo: oh, isn't it in friendly-recovery:17:10
mvojussi01: thanks17:10
mvopitti: it used to until karmic, now its no longer possible to remount / in ro17:10
jussi01mvo: no probs :) If anyone comes across stuff in factoids that is out of date, please lets us know though.17:11
mvopitti: this has to do with upstart changes, I talked to scott about it before the release and he said its intentional17:11
Keybukmvo: it isn't anything to do with upstart17:12
mvoKeybuk: right, let me re-phrase it "it used to work by chance, now it does no longer" - better ?17:13
Keybuk:) much17:13
tkamppeterpitti, OK, can you schedule a private meeting for that?17:13
pittitkamppeter: no need to be private; I'll add it17:14
mvoKeybuk: hm, shutdown -F is ignored in the upstart code, is there a different magic to force it on restart?17:16
mvoKeybuk: nevermind, I think I found it17:18
* mvo tries touch /forcefsck17:18
=== thekorn_ is now known as thekorn
tkamppeterpitti, with private I meant an informal meeting, without Blueprint.17:25
=== chuck_ is now known as zul
=== maco_ is now known as maco
=== robbiew is now known as robbiew-afk
smoserslangasek, ping.18:50
=== deryck is now known as deryck[lunch]
=== dendrobates is now known as dendro-afk
Ademanwhat should i do to find out about the new gdm/xsplash system?  I haven't run into anything from the simple greeter or xsplash that has any documentation...19:14
Ademanalso while i'm at it... the upstart script for gdm has a seemingly magical variable $CONFIG_FILE, I don't see where that's ever set, is it set by upstart? how?19:14
lamontpitti: around?  your comment on bug 447919 is ref: lucid ,yes?19:45
ubottuLaunchpad bug 447919 in launchpad-buildd "cups testsuite failures don't trigger a build failure" [Undecided,Confirmed] https://launchpad.net/bugs/44791919:45
=== chuck_ is now known as zul
Ademandoes upstart set variables that are used in upstart scripts?  for instance the gdm upstart script uses $CONFIG_FILE which isn't set anywhere in the script that i can see.19:55
StevenKAdeman: I'm guessing that's set by X, but I can't find anything to back that up19:59
=== dendro-afk is now known as dendrobates
Keybukcjwatson, StevenK: Remember that whole Cambridge, Plymouth, Dracut thing?20:21
KeybukI have another one20:21
=== robbiew-afk is now known as robbiew
sebnerKeybuk: wayland \o/20:24
StevenKKeybuk: Haha20:25
chrisccoulsonslangasek - i think i understand whats going on with your g-s-d crash now :)21:33
chrisccoulsonand I think I can see why it regressed from jaunty too21:43
=== dendrobates is now known as dendro-afk
=== dendro-afk is now known as dendrobates
lhasbsubuntu 9.04 server 2.6.2822:19
lhasbsmassive group descriptor corruption :(22:19
lhasbsext-4: group descriptors corrupted22:19
lhasbsVery strange and wierd here.22:19
=== cyphermo1 is now known as cyphermox
slangaseksmoser: pong23:00
slangasekchrisccoulson: oh?  Do tell!23:00
chrisccoulsonslangasek - the section of your xtrace log i quoted in the bug report is all triggered from a single press of Fn+F7. what happens when you press this button is that the screen info is refreshed from the server (because the screen config changed when you connected the monitor). when the screen config changes, a handler in g-s-d autoconfigures the new output. It then acts on the Fn+F7 keypress to reconfigure the output again, wit23:06
chrisccoulsonh screen information which is now out of date23:06
chrisccoulsonit didn't crash in jaunty because g-s-d had no handler for auto-configuring new outputs23:06
chrisccoulsonhow soon after connecting the monitor do you press Fn+F7?23:07
slangasekchrisccoulson: well, ideally within seconds, I don't go to the effort of plugging in a cable I'm not using :)23:07
slangasekbut I haven't noticed the monitor ever being autoconfigured for output, without me pressing Fn+F723:08
=== mbiebl_ is now known as mbiebl
chrisccoulsonwhat i noticed from the xtrace log is that the Fn+F7 keypress arrives before the first RRScreenChangeNotify event, which should arrive when you connect the monitor23:09
chrisccoulsonif you say that you've never seen the monitor being autoconfigured, then that would suggest that the RRScreenChangeNotify event doesn't arrive on it's own, and the xtrace log seems to support this23:10
chrisccoulsonit only arrives after querying the configuration from the server :-/23:10
* slangasek nods23:10
chrisccoulsonand that is what seems to mess it up23:10
chrisccoulsonso there might be a Xorg issue too23:11
slangasekthough the g-s-d behavior seems to be racy per se23:11
chrisccoulsonit does. normally the window of exposure should be small if the RRScreenChangeNotify event is delivered when you connect the monitor, but that doesn't seem to happen in your case23:12
slangasek(or in the case of other users who've reported this bug previously :)23:13
chrisccoulsonis bryce around today?23:13
chrisccoulsonah, he's in #ubuntu-desktop23:14
slangasekright, he doesn't seem to really be around today though23:15
chrisccoulsonslangasek - i'll add the rest of my thoughts to the bug shortly (so I don't forget them), and then try to get some input from bryce when he's around23:20
chrisccoulsonslangasek - in the meantime, it might be good to run it through xtrace again, but watch the output in the console and see if you see the RRScreenChangeNotify event when you connect the monitor, or if it only appears after pressing Fn+F7 (just to confirm that I understand what is happening)23:22
chrisccoulsoni don't know if you can make xtrace filter out specific messages or not23:22
ebroderMsMaco: ping?23:46

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!