[00:04] keybuk: Huh. mountall seems to say that / is mounted and that FHS is mounted and let rc-sysinit begin, even though / is still mounted readonly. Then mountall seems to receive an udev event about the / partition appearing, and proceed to fsck / while rc is trying to get the system started (with everything screaming about not being able to write to /). [00:05] that's odd [00:05] I don't think it does that here [00:06] keybuk: If fsck makes changes to the / partition, i manage to login via getty and then the system reboots suddenly. [00:06] I'll investigate [00:06] do you have the debug log? [00:08] I wonder what's the best way to get one? mount a tmpfs at /mnt before mountall in mountall.conf and redirect the output to a file in there? [00:10] oh [00:10] I see [00:10] it triggers FHS too early [00:10] and it looks like it doesn't clear the needs remount flag either [00:10] will fix tomorrow [00:11] oh [00:11] I've fixed this already [00:11] I just hadn't applied the patch [00:12] :-) [00:36] pitti, you around? [00:37] NCommander: Likely in bed. === rickspencer3 is now known as rickspencer3-afk [01:32] I'm using quilt to add a patch to a package (for SRU), but I notice that an older patch has a one-line offset when applying it, should it be refreshed or should I just leave it alone? [01:34] arand: for SRU, I don't think it's worth bothering with [01:34] slangasek: aknowledged. [01:46] YokoZar: no need to worry [01:50] dtchen, that "15 sec latency" bug I was talking about... https://bugzilla.redhat.com/show_bug.cgi?id=521276 [01:50] bugzilla.redhat.com bug 521276 in gstreamer-plugins-good "Something about jitter buffer makes VoIP over GStreamer useless (delay around 15 sec)" [High,New] [01:50] it's fixed by a gstreamer patch in git: http://cgit.freedesktop.org/gstreamer/gst-plugins-base/commit/?id=058776bcf1ab218b509d19685a0b528d71c65f98 [01:51] johanbr: yep, i saw it earlier, but i'm not in a position to do much about it presently [01:51] alright [01:51] patching and rebuilding the current karmic package makes everything work as expected [01:52] would an lp bug be useful? [01:52] johanbr: absolutely [01:52] alright, just a few minutes [02:02] keybuk: Still around? [04:01] hello! anybody here? i need some advices :) [04:01] !ask | jumpingjack [04:02] jumpingjack: Please don't ask to ask a question, simply ask the question (all on ONE line, so others can read and follow it easily). If anyone knows the answer they will most likely reply. :-) [04:07] Is there way in ubuntu to get the text under mouse cursor everywhere on the desktop? What language or framework i should use? I'm new in linux, so i need a help with starting.. [04:08] i don't need a solution, i need a way to start from [06:44] Good morning [06:45] Keybuk: well, I left my comment in the bug; that was a bit too trigger-happy IMHO [06:45] NCommander: hi [06:46] pitti, I got a question on calibre, you moved a bug onto python-qt4 which is RC, but pyqt doesn't promise a stable ABI,so calibre needs a binNMU to get going again [06:46] (I think, I have yet to test that theory) [06:47] NCommander: but a followup upload was said to not fix it.. [06:47] well, I could never reproduce it myself anyway [06:49] pitti, I want to move the bug back to calibre, its currently blocking pyqt4 into testing (which in turn has KDE blocked). It doesn't seem toi be a pyqt4 issue specifically [06:49] (kdebindings is chugging along just fine) [06:50] well *shrug* sure [06:58] good morning [07:04] morning o/ [07:04] heya didrocks, hi amitk [07:05] hey dholbach :) [07:10] morning dholbach === thomasc is now known as BobbyFerret [08:52] asac: so... firefox installer is in main and on the latest cd images, time to resolve the remaining issues ;) ... I didn't find a firefox icon in the app-install data (+ I think Kubuntu doesn't have the data installed currently), so I suppse the only options we have is getting TB approval or detach the icon from the branding package (i.e. create a seperate package for the icon) [08:55] shtylman is going to come up with a kubuntu-installer-style packag ethat can be shared among ubiquity and k-f-i, so we can free additional CD space :) [09:04] pitti, seb128: what do you think about bug 407817? [09:04] Launchpad bug 407817 in gnome-icon-theme "gnome-icon-theme does not allow alternative start-here icons" [Low,New] https://launchpad.net/bugs/407817 [09:04] bdrung_ worked hard on it === tkamppeter_ is now known as tkamppeter === dholbach_ is now known as dholbach [09:06] sorry, fell out of the internet [09:06] pitti, seb128: what do you think about bug 407817? [09:06] Launchpad bug 407817 in gnome-icon-theme "gnome-icon-theme does not allow alternative start-here icons" [Low,New] https://launchpad.net/bugs/407817 [09:06] bdrung_ worked hard on it [09:08] dholbach, I don't like alternative much and I don't think a distro specific hack is the way to go there [09:09] dholbach, I think the logo icon to use should rather be a gconf key [09:10] bdrung_: ^ what do you think? [09:10] seb128: what do you mean with "distro specific hack"? [09:11] what are you trying to do? allow customization of the gnome-panel menu icon? [09:11] gconf would be a solution, too. [09:11] gconf would work on any distro [09:11] seb128: yes [09:11] and not rely on alternatives which is a debian,ubuntu thing [09:12] it would also allow users to change the icon [09:12] rather than having a system setting you can't change [09:12] that's a good point [09:15] when we have a gconf key for that, you can drop my changes [09:21] seb128: Bug #253416 << maybe gnome-panel checks before displaying the issue, but it still installs a desktop file [09:21] Launchpad bug 253416 in ubuntu "[Xubuntu] yelp can not find ghelp:about-ubuntu" [Low,New] https://launchpad.net/bugs/253416 [09:21] so another menu system will display it… [09:22] I'm too busy today to start a discussion about that [09:22] of course (!) [09:22] I don't think adding something like NotShowIn=XFCE; (or similar) needs a big discussion [09:23] (instead of reaffecting the bug to something else) [09:24] the entry has nothing to do there in fact I think [09:24] it should rather be moved in the documentation [09:24] and gnome-panel should be patched to display it if available [09:27] kirkland, using -s in the debhelper invokations might help [09:36] ogra: i'll try that [09:36] ogra: which ones? [09:52] kirkland, all under the binary-static target i think+ [09:52] s/+// [09:56] ogra: hmm, that didn't work [09:56] dpkg-gencontrol: error: current host architecture 'amd64' does not appear in package's architecture list (i386) [09:56] + [09:56] kirkland, well, just add amd64 to Architecture then [09:56] though -s should work as i understand it [09:57] "It understands that if the control file lists "Architecture: i386" for the package, the package should not be acted on on other architectures. " from the manpage [09:57] ogra: hrm [09:58] just add amd64 to Architecture: ... will just get me some more bugs for the binary i guess [09:59] there is no reason it shouldnt build, i just think the syscall translation layer doesnt work so well on amd64 === johe|work is now known as johe [10:12] doko, hey ! [10:13] doko, "debian/*.shlibs: Update to the version from the branch." ... could that solve my ld-linux3-dev issues with the d-shlibs override ? [10:13] (from your binutils upload [10:13] ) [10:14] ogra: no, I don't think so [10:14] meh, ok [10:14] * ogra had hopes :) === ember_ is now known as ember [10:28] tseliot: do you happen to have some time to test the intrepid-proposed nvidia-common in bug 303825? [10:28] Launchpad bug 303825 in nvidia-common "linux-image-2.6.27-9-generic failed to install/upgrade : run-parts: /etc/kernel/postinst.d/nvidia-common exited with return code 10" [Undecided,Fix committed] https://launchpad.net/bugs/303825 [10:30] pitti: sure [10:33] doko: just a poke about the python2.6 stuff I filed/subscribed you to earlier (the FTBFS is blocking me from updating ia32-libs which in turn is FTBFSing Wine ;) ) [10:35] YokoZar: doko is on vacation or at least travelling right now [10:35] doko: I tried building python2.6 locally and in my PPA, and it failed three times with three different errors :-( (https://edge.launchpad.net/~pitti/+archive/ppa/+build/1207804 and https://edge.launchpad.net/~pitti/+archive/ppa/+build/1207804) [10:35] ahh ok [10:35] well, he did a binutils upload this morning :) [10:35] ok [10:36] I'm sure it's not the first time for doko to do that while on vacation ;-) [10:36] dholbach: I'm back [10:37] doko: ah, hey! had a nice vacation? [10:37] pitti: yes, thanks! [10:37] doko: beach and cocktail? Or the hiking/bike style? :-) [10:37] pitti: there's a promotion request pending for readline6 binaries ... [10:38] doko: well, if we want to start the readline6 transition now, ok; but python2.6 still doesn't build [10:38] pitti: no, just running and beach [10:38] nice [10:38] pitti: it's not a transition, there are two development packages, and the readline6 source already is in main, because of readline-common [10:39] readline6 | 6.0-2ubuntu2 | karmic/universe | source [10:39] pitti: which is wrong, because readline-common is in main [10:39] ah, bug 421035 is incomplete [10:39] Launchpad bug 421035 in readline6 "sync & promotion request (unstable -> main)" [Undecided,Incomplete] https://launchpad.net/bugs/421035 [10:40] * pitti promotes source [10:40] ahh, this was asked while I was away ... [10:40] ok, rest of binaries promoted [10:41] bug updated [10:41] hmm, strange, no diffs anymore in the ui to the previous version [10:42] seb128: retracer> *nnng* bad gateway; WTH is up with LP today? [10:42] * pitti restarts retracers again [10:43] pitti, edge timeout [10:43] seb128: but apport isn't on beta-testers [10:43] my versions script fails on similar errors [10:43] I'm poking in an SRU for glib2.0, noticing that in kk patch 61_* is added, however a 61_* patch already exists in intrepid version, should I simply use 62_* for intreipid alone or should it be changed throughout? [10:44] pitti: about the build failure: I'll see on which archs the buld fails with -fprofile-use, and then disable it on these archs [10:44] i.e. the 61_* patch in intrepid are a completely different patch, with the same number prefix. [10:44] doko: ok, thanks; at least it shouldn't be on depwait any more in 1 hours 15 mins [10:47] arand, the number are just for ordering [10:47] arand, you can use any number you want [10:48] seb128: even though the same patch are going to be added in all releases, consistency in naming may be ignored? [10:49] arand, we don't care [10:49] the patch just need to be applied in a way which works [10:49] the naming, ordering, etc is a detail [10:59] r-base is broken in Ubuntu karmic for all. Doh, could somebody apply the correct fix as described in [10:59] https://bugs.launchpad.net/ubuntu/+source/r-base/+bug/426360 [10:59] Ubuntu bug 426360 in r-base "[PATCH] r-base suppresses ALL error messages forever" [Undecided,New] [10:59] ? It would be embarassing if that goes into karmic gold [11:03] I subscribed the sponsoring team [11:03] spaetz: if you subscribe "ubuntu-universe-sponsors" to bugs like this then they will get reviewed and uploaded when approved [11:06] I've also subscribed Dirk Eddelbuettel, who's the Debian R maintainer but who was also responsible for this Ubuntu-specific change; he doesn't seem to be subscribed to all Ubuntu r-base bugs [11:08] cjwatson: do we plan to include dpkg 1.15.4 in karmic? [11:09] possibly [11:10] I haven't looked over it in detail yet but it's not out of the question [11:17] doko: what do you need it for? the install-info transition? [11:20] cjwatson: yes, that would be convenient [11:21] I'm not going to say yes straight away because the changelog is massive, but I'll look at it [11:39] did we ever come to an agreement if we want merge proposal for ~ubuntu-dev stuff on ubuntu-devel@? [11:39] if we don't want that stuff, I'll just reject those mails now [11:39] is there a way for us to turn that off? [11:45] dholbach: well, they were explicitly turned on, so they can be turned off again [11:50] james_w: bug 414298 ack'ed [11:50] thanks pitti === nixternal is now known as Guest88294 [11:52] if I want to contribute to a package in 9.10, where can I go to download the dev packages? [11:52] *new ubuntu users [11:55] EricInBNE: We aren't accepting new packages for 9.10 anymore. We are concentrating on getting bugs fixed and things working. [11:55] !development | EricInBNE [11:55] james_w: hm? [11:55] ScottK, its for bugfixing an existing package [11:55] EricInBNE: Excellent. [11:56] EricInBNE: What package? [11:56] ScottK, recently changed from fedora to ubuntu. [11:56] dholbach: there was a change made in the Ubuntu teams on LP last year such that code review emails would go to ubuntu-devel@ [11:56] EricInBNE: Interested in becoming an Ubuntu Developer? Get started here: https://wiki.ubuntu.com/UbuntuDevelopment [11:56] dholbach: that change could be undone if desired, but it was an explicit decision to send them there [11:56] EricInBNE: Welcome. [11:56] ScottK, looking to contribute to the Android execution environment. [11:57] james_w: ok... do you know if that was documented somewhere? [11:57] I see. [11:57] not offhand [11:57] dholbach: Do you have suggestions for what channel EricInBNE should be asking about contributing in? [11:57] * ScottK needs to run off for a few hours. [11:57] ScottK, is that in .10? I couldnt find it. mjfrey mentioned he is looking for a few replacement pkgs on his weblog [11:58] EricInBNE: I'm not sure. [11:59] I suspect #ubuntu-mobile would be the place to ask, but I'm not certain. [12:01] yep, that's what I'd say to [12:01] too [12:02] is launchpad the analog to rawhide? or is there another code repo [12:02] check out https://wiki.ubuntu.com/UbuntuDevelopment [12:02] EricInBNE: karmic (the current Ubuntu development version) is the pendant to Fedora rawhide [12:02] cjwatson: superblock having offset of my timezone a known issue? [12:02] it should explain a lot about how the archive works [12:03] asac: bug 423247 [12:03] Launchpad bug 423247 in clock-setup "Superblock last mount times cause fsck to fail" [High,Fix released] https://launchpad.net/bugs/423247 [12:03] (probably) [12:04] ok cool [12:04] will check if update makes this go away [12:04] death to timezones! utc everywhere! [12:04] i guess there is no way to not run fsck now? [12:04] ;) [12:05] asac: update? it was an installer bug [12:05] cjwatson: i get this on a regular install [12:05] so upgrading will make no difference [12:05] cjwatson: second time now [12:05] its an old install [12:05] install of what? [12:05] oh, not my problem then :) [12:05] ubuntu? [12:05] I mean what vintage [12:06] hmm [12:06] feels too similar to be not the same ;) [12:06] there are lots of similar issues [12:07] if it's an old install, could you talk with Keybuk? [12:07] Keybuk: ^^ ... on reboot i have to run fsck, because superblock has my timezone offset [12:08] of course it could be that the old installation broke your hardware clock [12:08] date; hwclock --debug --show [12:08] I got that several times too recently [12:08] cat /etc/default/rcS [12:08] well, grep ^UTC= /etc/default/rcS [12:09] fsck is running ... will run that afterwards [12:10] basically, one possible cause is that the hardware clock has been rendered wrong at some point in the past, and it's only fixed up by NTP once the network comes up [12:11] I got the issue several times on karmic [12:11] cjwatson: hmm. you say the hardware clock was always wrong? or you think just intermediately during karmic? [12:11] ie it's not only a one time problem due to old values [12:12] otherwise we need to do something because loads of users will end up with fsck ;) [12:12] seb128: i got it the second time now. feels like on every reboot where i did an dist-upgrade in between [12:12] if that's the case, the way to fix your computer is to fix the hardware clock: if /etc/default/rcS says UTC=yes, then it should be the time in UTC; if it says UTC=no, it should be the current local time [12:12] seb128: I only fixed the installer bug after alpha 5, a few days ago [12:12] asac: I think the installer bug has been around for ages and ages [12:13] am i right in assuming this only happens if your system clock is in local time? [12:13] hyperair: you mean hardware clock; and I don't think you're right [12:13] cjwatson: so ok. lets assume i had that installer bug. now its broken. the solution cant be to say: "fix your hardware clock" thats good for me, but not for users [12:13] hmm [12:13] well, shouldn't we do something so user upgrading don't get that confusing login to manually run fsck on reboot? [12:13] yes, feel free to suggest something that actually works :-) [12:13] i need to understand why it suddely started to break now [12:13] I agree it's a problem but have no bright ideas [12:14] asac: because Scott took out a workaround [12:14] same as asac [12:14] it always worked till recently [12:14] can't we keep the workaround? [12:14] so something must have changed. and thats where we probably need to fix it [12:14] it introduced other problems ... [12:14] if we don't have better ideas ... [12:14] what was the workaround? [12:14] we need to understand both impacts. fsck on every second reboot is worst you can get [12:14] its close to complete system breakage [12:15] I don't know the details, and cannot participate further in this discussion without them [12:15] hehe [12:15] thats ok ;) [12:15] lets wait [12:16] fsck run takes about 1h anyway ;) [12:17] oh, hurrah, requestsync now correctly doesn't allow me to sponsor my own main requests [12:20] ? [12:21] * maxb has also seen that timezone-fsck issue twice on rebooting an existing system [12:21] keybuk: Around? [12:22] and it's not like it was a fsck normal run in usplasg [12:22] it's a command line prompt which invite you to run commands [12:22] yes, I *know*& [12:22] ie it's broken enough that most normal users will declare the system screwed and reinstall [12:22] yes, I *know* [12:22] you can stop explaining how important it is now. :-) [12:22] directhex: is this a bug or not? I'm not sure from your statement [12:22] ok, let's wait for Keybuk to comment then [12:23] geser, it's an unbug [12:23] well, I have the impression that you argue that we traded an issue for an another one [12:23] geser, i was able to run requestsync for ages to sync packages in main, and didn't need a sponsor as i'm a motu [12:23] but apparently that was a false impression ;-) [12:23] as long as it's on the karmic list I'm fine with it [12:23] seb128: no, I'm arguing that "just put the workaround back" probably isn't the right answer, and we should actually think about it instead ;-) [12:23] let's people who understand what's going on work on it [12:24] * seb128 goes back to desktop land ;-) [12:25] seb128: do I have to comment? [12:25] Keybuk, no [12:25] Keybuk, I trust you to do whatever is required to sort that for karmic ;-) [12:25] Keybuk: i would appreciate if you could explain whats the problem ;) [12:25] better to spend your time working on the bug rather than explaining it again on IRC [12:26] which bug? [12:26] Keybuk: superblock has UTC offset for me on reboot ... requiring fsck [12:26] its an old install [12:26] same here [12:26] asac: every time, or just after this one reboot? [12:26] it doesn't happen every time though [12:26] Keybuk: its the second time in a row now [12:26] Keybuk: https://bugs.launchpad.net/bugs/423247 I'm assuming [12:26] I didn't notice what trigger it yet [12:26] Launchpad bug 423247 in clock-setup "Superblock last mount times cause fsck to fail" [High,Fix released] [12:27] I had the issue several times [12:27] when it next happens, stop at the fsck error [12:27] and grab me [12:27] some of those have been forced reboot after a broken suspend resume [12:27] you'll need to run "grep ^UTC /etc/default/rcS", "date" and "hwclock --debug --show" [12:28] Keybuk: ok. this reboot was forced reboot too [12:28] ie, resume, computer hangs, press the power button several second, turn computer on again, get the issue [12:28] so maybe it only happens then [12:28] yea [12:28] i will try to reproduce once current fsck finishes [12:28] seb128: likewise if you can reproduce, stop at the moment things are inconsistent [12:29] ok [12:29] keybuk: I added another patch, that one removes /forcefsck in a root_hook. http://heh.fi/patches/mountall/ [12:30] ion: could you mail these to me, I don't keep track of IRC logs ;) [12:30] keybuk: The URL has the patches. Is that okay? [12:30] ion: sure, but mail it to me ;) [12:31] Will do [12:31] asac, seb128: the only clock bug that I am aware of was that the first/second reboot after installing, you'd hit the fsck error [12:31] once you've passed it, it's fixed and there are no issues [12:31] if you're hitting the fsck error on an installed system, you have an entirely different but that I am not familiar with [12:32] ok, I've an entirely different bug then [12:33] I got it several times in karmic [12:33] it's possible that you two have entirely different bugs [12:33] Keybuk: colin said the clock-setup bug was around for long time in installer. you know what caused this show up now in karmic? [12:33] and I'm pretty sure each time after broken resume and forced power aoff and on cycles [12:33] "fsck has time inconsistency" is a bit like "human has a runny nose" [12:33] asac might have a cold, where you might have swine flu, etc. [12:33] asac: yes, I know why clock issues are showing up in karmic suddenly [12:33] my superblock time is exactly offset by my timezone [12:34] same here [12:35] asac, seb128: in which direction? negative timezone or double timezone? [12:35] fsck says: "time == UTC", but superblock == "my timezone time" [12:36] asac: don't suppose you can pastebin me the contents of your /etc/adjtime file? [12:36] fsck is currently running. i will get you that right after [12:36] ok [12:36] seb128: what way is the timezone math for you? [12:36] I don't remember, I had the issue several days ago [12:36] $ grep ^UTC /etc/default/rcS [12:36] UTC=no [12:36] if that matters [12:37] I will try to power down the laptop later but not now ;-) [12:37] seb128: your /etc/adjtime file would be helpful [12:37] see that's interesting [12:37] $ cat /etc/adjtime [12:37] 0.193938 1252449040 0.000000 [12:37] 1252449040 [12:37] LOCAL [12:37] the fact that you have UTC=no means that you can't possibly have the same bug as asac [12:41] Keybuk: http://paste.ubuntu.com/267881/ [12:42] no adjtime at all [12:42] re [12:42] ok, that broke again [12:42] I get it every time I shut down the laptop not properly [12:42] I'm on my netbook now [12:43] Keybuk: what info do you need? === MacSlow is now known as MacSlow|postal-o [12:43] now =13: [12:43] superblock = 15:... [12:43] 13:40:20 is now [12:43] Keybuk: http://paste.ubuntu.com/267883/ ... thats --show --debug [12:44] no rcS UTC=no [12:44] date says 13:45:02 [12:45] hwclock says the same [12:45] let me try to reproduce now .... /me hits powerbutton [12:46] oh [12:46] hwclock --debug --utc [12:46] Time read from clock ... 13:46 [12:46] Wed Sep 9 15:46 [12:47] Keybuk: so i was wrong. time == "timezone time" ... superblock time == "timezone time + my timezone offset" ... so yeah double timezone offset [12:47] so hwclock is acting as if UTC=yes was used [12:47] * asac should better know what time it is ;) [12:47] seb128: sorry rewind [12:47] i am now in the "do fsck state" [12:47] keybuk: Whoops, i hadn’t re-exported the patches. The URL contains patches that actually work now. :-P [12:47] me too [12:47] seb128: what is the exact fsck output at the point it fails? [12:48] asac: likewise, what is the exact fsck output right now? [12:48] keybuk: At least rm-forcefsck was broken. [12:48] ups [12:49] Keybuk: "/dev/sda6: Superblock last write time (Wed Sept 9 15:40:20 2009 [12:49] now = ... 13:.... [12:49] seb128: please, I do need the whole thing [12:49] UNEXPECTED INCONSISTENCY [12:49] don't abbreviate it [12:49] the times are quite important [12:49] 15:40:20 [12:49] 13:40:30 [12:49] ok, so your superblock was last written at 15:40:20 [12:50] and your "time now" is 13:40 [12:50] your time now looks correct to me [12:50] yes it is [12:50] hm. what's the quick way to check why a package was promoted to main? [12:50] the 15: is two hours in the futur [12:50] it's 11:50 UTC, 13:50 CET [12:50] directhex: which one? [12:50] seb128: you have UTC=no in /etc/default/rcS ? [12:50] I've UTC=no [12:50] yes [12:50] seb128, libgluezilla [12:50] seb128: your /etc/adjtime file has LOCAL in it? [12:50] directhex: dunno, look for bugs [12:51] Keybuk: yes [12:51] seb128: what does "date" say? [12:51] 13:51:38 [12:51] Keybuk: http://www.flickr.com/photos/asacasa/3903749434/sizes/l/ [12:51] and /etc/localtime is a file not a symlink? [12:52] seb128: hwclock --debug --show ? [12:52] it's a file [12:52] asac: could you provide the same bits of information as seb128 [12:52] hm, i wrote the MIR. i need to see someone over memory issues [12:52] directhex: look at the MIR bug #362854 [12:52] Time read from the hw clock ... 13:52:34 [12:52] Launchpad bug 362854 in gluezilla "include into main" [Undecided,Fix released] https://launchpad.net/bugs/362854 [12:52] seb128: could you pastebin it so it doesn't get lost [12:52] Hw clock time 13:52:34 [12:52] I do need the entire output [12:52] Wed Sep 9 [12:52]