[00:02] pitti: I was told to bug you (don't you feel lucky) - i'm trying to do 'this' https://bugs.edge.launchpad.net/ubuntu/+source/xorg-server/+bug/212073 [00:02] Ubuntu bug 212073 in xorg-server "Touchscreen stops functioning correctly in Xorg if the device is removed/reinserted" [Low,Fix released] [00:02] I see the changes in lshal, but 0 effect on X [00:03] the problem I am trying to fix: when I move my finger to the left, the mouse cursor moves to the right [00:04] I suppose turning the machine upside down won't do it? [00:04] ;-) [00:05] don't laugh - I was considering that [00:05] but then the up/down will have problems [00:11] kirkland: that's fixed it, thanks. I'll upload the change, if you like. [00:13] hrm, it's in bzr. damn. === NCommander is now known as Guest49220 [00:17] argh === Guest49220 is now known as NCommander [00:21] kirkland: blah, it's done already. Who said fixes in ubuntu weren't fast? ;) Thanks! [00:28] hey Hobbsee [00:29] NCommander, i did it, i got an arm system booted in qemu [00:29] score :-) [00:30] NCommander, if i might make a suggestion... could someone DOCUMENT the fact that the default kernel cmdline includes "mem=32M"? [00:30] hey NCommander [00:30] hair was torn out over that [00:30] * NCommander didn't know that [00:30] Hobbsee, how goes it [00:30] NCommander, i got the screenshot i wanted - http://www2.apebox.org/wordpress/wp-content/gallery/00-single/armless.png [00:31] lol [00:31] Xubuntu! [00:31] NCommander: fighting matlab :) [00:31] FTW! [00:31] NCommander, MID was uninstallable this morning due to python transition [00:31] Hobbsee, have you prepared the scarifies in the necessary order? [00:31] directhex, the python transition has/had most of the archive broken :-/ [00:31] * StevenK is kicking python-hildondesktop now [00:32] NCommander: no. I think that might be my problem... [00:32] StevenK, well, i'm not moaning, fixing lp-integration made xubuntu installable :p [00:32] Yay for installable xubuntu [00:32] matlab? :| [00:32] * NCommander just installed Alpha 5 on his new machine :-) [00:32] StevenK, what's wrong with it [00:32] NCommander: Python 2.6 [00:32] NCommander, i wasn't going to push my luck & try a full-on gnome on arm in qemu with 256M [00:33] I mean is it FTBFSing? [00:33] directhex, 256 is the max you can run. GNOME runs slowly, but it does work [00:33] NCommander, at any rate, silverlight on ARM, complete with media support! :p [00:33] nice! [00:34] NCommander: It's uninstallable, I'm looking at fixing it. [00:34] StevenK, would you like some help? [00:35] NCommander, mostly i was documenting the procedure, to allow novell to produce one of those optional licensed binary codec downloads for arm. in case ffmpeg ever loses the required abilities for any reason. [00:54] * TheMuso kinda wished that the python transition happened earlier in the cycle... [00:54] IMO transitions should only be before feature freeze. [00:55] started, certainly. sometimes they can drag on a bit, depending on size [00:55] Major ones anyway. [00:58] But python2.6 was uploaded past FF? [00:58] s/?/. [00:59] It was, but it was spec'ed and approved. [01:00] bam, i have now entered the debian web o' trust [01:01] What's the point of FF if we break everything post it :-/ [01:01] * NCommander is reminded of libbluetooth last cycle, although that was kinda an exception cirmstance. [01:03] NCommander: It wasn't python2.6 that was the issue, it's python-defaults. [01:30] Is there a main sponsor available to look at the one-line patch in bug 336436? [01:30] Launchpad bug 336436 in lsb "/usr/bin/lsb_release:81: DeprecationWarning: the sets module is deprecated" [Undecided,Confirmed] https://launchpad.net/bugs/336436 === asac_ is now known as asac [04:22] okay quick question-- I need to find out what version of oss is installed on someones computer -- is there a quick command to find that? [04:27] apt-cache policy or dpkg -l will both tell you package versions [04:28] i assume you mean either alsa-oss or oss-compat [04:28] oss-compat [04:30] thanks [04:32] np [04:35] he can hear system sounds but they are distorted and he is using oss [04:36] so I fount 4.1 and 4.0 is the installed version and according to their page they fixed a few issues with his sound card [04:36] for jaunty, did alsamixer get replaced? (or, how do I adjust volume levels in a script) [04:37] this one I am afraid is for hardy-- and I think it fixed his issue before just too many people -- too many configurations -- plus my 3 here at the house and 2 linux ones at work and 10 computers at work and 2 servers [04:38] and that does not count the 25 laptops [04:50] CarlFK: no, alsamixer's still there [04:50] this isnt really the place to be asking such support questions though.... [04:54] maco: oh yeah - the oss stuff distracted me === jdong_ is now known as aaaa === aaaa is now known as Guest99615 === Guest99615 is now known as jdong_ [08:08] Good morning [08:09] EtienneG: yes, although there's probably little I can do about it :/ [08:09] jdong_: we should get dbgsyms for -updates/-security [08:10] CarlFK: 212073> let's discuss that in the bug, please subscribe me [08:11] CarlFK: oh, you mean you don't have this particular problem? can you please describe the problem more specifically? does it happen after removal/reinstert, or always, and what's lshal output? [09:06] anyone knows if there is precendence of adding libs to ia32 as an SRU? [09:06] \sh: ^^? [09:13] asac: I would be very cautious in accepting such an SRU - why is it needed? [09:18] slangasek: two things: [09:19] slangasek: i got complain from NSPR/NSS/chrome developer that libnss3-1d needs libsqlite ... but only libnss3-1d is in intrepid ia32 [09:20] slangasek: 2. also they would love to see those in the LTS, as it would allow amd64 users to build chromium === azeem_ is now known as azeem [09:25] its a bit strange that it was added there without sqllite ... in jaunty libnss3-1d explicitly depends on libsqlite3-0 (>= 3.5.9) [09:31] asac: if it were the case that we were shipping nss in hardy ia32-libs already and it was broken, that would be a good reason for an SRU. I don't think we should add more libs to ia32-libs in hardy simply because they'd be nice to have. [09:37] doko: what do you think about writing a mail to ubuntu-devel-announce that explains to the developers that all packages that use python and distutils needs to get the "--install-layout=deb" added? I just did it for command-not-found and unattended-upgrades, but there are much more that need love. its funny, a simple rebuild puts everything in /usr/local now [09:38] slangasek: yes. thats what i thought. intrepid ok, hardy not [09:38] i will provide those in some ppa maybe ... so they can add something more official to their build instructions [09:39] doko: or at least the scripts and i18n stuff (that is build via python-distutils-extra) [09:39] asac: if this is just for building... why not use an i386 chroot? [09:39] slangasek: its also for running ;) [09:39] ok [09:58] james_w: bzr-builddeb --merge seems to be broken in jaunty [09:59] asac: how? [09:59] (still i guess) ... i have debian/ only branches and the top level dir from the tarball ends up in the build tree [09:59] james_w: http://paste.ubuntu.com/125187/ [09:59] (ignore the aclocal.m4 ... that was created in pre-build) [10:00] and what do you expect? [10:00] james_w: i expect the content of NetworkManager.git directory to be in toplevel [10:01] asac: can you do a find for me? [10:01] what are the entire contents of that directory? [10:01] james_w: inside NetworkManager.git? [10:01] ok [10:02] james_w: http://pastebin.com/f26d95ae4 [10:02] let me get a tar tzf of the tarball too [10:02] james_w: http://pastebin.com/f33d9b4d7 [10:03] pitti: in Jockey, there are 'DeprecationWarning: the sets module is deprecated' string all over gui, making mess out of it [10:04] asac: do you still have the Intrepid version pinned? [10:05] PecisDarbs: do you use 0.5-0ubuntu2 ? [10:05] james_w: ii bzr-builddeb 2.1~0ubuntu1 bzr plugin for Debian package management [10:05] PecisDarbs: I did some python 2.6 fixes there [10:05] PecisDarbs: over the gui? do you have a screenshot? [10:06] lsb_release output perhaps? [10:06] (bug 336436, about to sponsor now) [10:06] Launchpad bug 336436 in lsb "/usr/bin/lsb_release:81: DeprecationWarning: the sets module is deprecated" [Low,Confirmed] https://launchpad.net/bugs/336436 [10:07] pitti: 0.5-0buntu1 or 2 [10:07] pitti: screenshot comming, one min [10:07] PecisDarbs: well, the 'or' matters :) ubuntu2 has the 2.6 fixes === DrKranz is now known as DktrKranz [10:07] pitti: ubuntu2 [10:08] james_w: maybe builddeb expects the top level directory name now to be of a certain format? [10:09] asac: no [10:10] strange [10:11] asac: can you let me have your branch and tarball? [10:11] pitti: http://imagebin.ca/9L_dWXk.html [10:11] it was working fine for me on Saturday, so I'd like to look at what you are using [10:11] PecisDarbs: that's 404 [10:12] james_w: sure: http://people.ubuntu.com/~asac/tmp/network-manager_0.7.1~rc2+1git7f1c86e3.orig.tar.gz [10:12] wait, I will copy&paste :) [10:12] pitti: http://imagebin.ca/view/9L_dWXk.html [10:12] james_w: bzr branch lp:~network-manager/network-manager/ubuntu.0.7.1 [10:13] PecisDarbs: right, that's the bug cjwatson mentioned [10:13] 0.7.1, eh? does it actually save a default static ip yet, rather than ignoring you & re-creating a default dhcp link? [10:14] ok, nice to know that you are informed already :) [10:14] pitti,PecisDarbs: fix just uploaded [10:15] pitti: why is jockey displaying lsb_release's stderr in its UI though? [10:15] asac: wfm, "bzr plugins -v | grep builddeb -A2" please? [10:15] cjwatson: thanks man :) [10:15] pitti: and it might make sense to only call it once ... [10:15] cjwatson: stderr> just fixed in bzr [10:16] heh, ok [10:16] cjwatson: once> that's what I did initially, but on other platforms "lsb_release -sir" is not predictable wrt. line breaking/spacing [10:16] cjwatson: longer-term I just want to move this to a build-time check [10:17] james_w: http://pastebin.com/f6d45ce69 [10:17] line breaking/spacing> I don't get it. I just meant to call it once up-front and then you could still substitute it into a string and line-wrap that as normal [10:18] cjwatson: but if it uses space instead of newline as separator, where do I break if there is more than one space? [10:18] asac: it is odd that it is dist-packages [10:18] of course that's slightly pathological (if the distro name has a space in it) [10:18] unless that change was made a little while ago [10:19] james_w: i think before weekend doko did pythong 2.6 transition [10:19] asac: yeah, but this was built almost 2 weeks ago. I guess it's not a problem, I just didn't expect it [10:19] pitti: the UI shown in the screenshot above only uses "Ubuntu" [10:20] pitti: so you could use -si called just once for those, and call -sr separately if you need the release version number [10:20] cjwatson: yes, I could do that [10:20] pitti: I didn't mean "just once, absolutely, for the whole program" - I meant "collapse multiple identical calls into one" [10:20] asac: I don't understand though, I do a "bzr bd --export-only" and it creates the layout you desire [10:21] let me check [10:21] james_w: not for me :( [10:21] james_w: ls ../builds/network-manager-0.7.1~rc2+1git7f1c86e3/ [10:21] debian NetworkManager.git [10:22] I can see that [10:22] I just need you to do a bit more digging, as I can't reproduce it [10:22] cjwatson: it's quite an intrusive change, though (changing all occurrences of using the variables to a function call which lazily calls lsb_release if it wasn't used yet), so I don't want to change it right now [10:22] james_w: i am here - and since i am kind of stuck because of that i will be here ;) [10:23] asac: can you branch to a fresh area [10:23] put the tarball in the parent dir [10:23] james_w: my builddeb conf is: [BUILDDEB] [10:23] build-dir = ../builds/ [10:23] result-dir = ../results/ [10:23] cjwatson: (it doesn't call "lsb_release -sr" multiple times ATM either) [10:23] oops [10:23] damn paste ;) [10:23] and run "bzr bd --export-only" and pastebin the output? [10:23] james_w: yes let me check [10:24] james_w: http://paste.ubuntu.com/125199/ [10:25] james_w: oh fresh area [10:25] sorry [10:26] james_w: http://paste.ubuntu.com/125200/ [10:28] hmm [10:28] james_w: i branched from the local branch. i can try the remote branch too if that can make any difference [10:30] it shouldn't [10:30] asac: do you have any aliases for "tar"? [10:30] do you have a ~/.bazaar/builddeb.conf? [10:31] mvo: https://lists.ubuntu.com/archives/ubuntu-devel/2009-February/027528.html [10:32] james_w: yes. i pasted the builddeb a few lines above [10:32] ah [10:32] (just build-dir = ... and result-dir = ..:) [10:32] do you have a .bzr-builddeb in this branch? [10:32] james_w: no alias for tar [10:32] james_w: if i have it, its committed [10:32] let me check [10:32] the one I have is merge = True in default.conf [10:32] james_w: yes, but you should hav eit too [10:32] do you have anything else? [10:32] right [10:32] no [10:32] no local.conf? [10:33] local.conf? [10:33] in .bzr-builddeb? no [10:33] .bzr-builddeb/local.conf [10:33] ok [10:33] note: i just did a clean branch ;) [10:33] true :-) [10:33] james_w: is there kind of "verbose" mode? [10:34] asac: you can look in ~/.bzr.log [10:34] doko: fair enough, I was just thinking that ubuntu-devel-announce might be a good place too, especially since a rebuild without changes may now move stuff into /usr/local [10:34] mvo: it does work for simple packages, python-support, python-central and cdbs are patched to move these files around [10:35] james_w: http://pastebin.com/f6966bbbc thats what i get on --export-only run [10:35] james_w: line 22. [10:35] what do you run there? [10:35] mvo: do you see any additional, or grave update failures? [10:36] doko: I just updated command-not-found and unattended-upgrades (they use debhelper) and I suspect gdebi needs a update too [10:37] webkitgtk python is broken ;) [10:37] doko: maybe more, I need to check my devel tree. most of my python stuff does not use cdbs :/ [10:37] mvo: btw, why does update-manager install into /usr/lib/pythonX.Y? Is this used by any other package? [10:37] doko: but you know better whats doing on in python land, so its up to you where to announce [10:38] mvo: it's a feature not to use cdbs [10:38] asac: tempdir = tempfile.mkdtemp(prefix='builddeb-', dir=build_dir) [10:38] subprocess.call(['tar','-C',tempdir,'-xf',tarball]) [10:38] doko: it installs stuff with nomove for improved stability (if that is what you mean) [10:38] doko: just like python-apt [10:38] doko: its one of the things that should be as robust as possible [10:39] doko: oh, you mean computer-janitor [10:39] mvo: well, using a private libdir would be even more stable (if you don't have dependencies on update-manager) [10:39] doko: that is fallout from the merge with liw, let me check [10:40] james_w: ok, that would give NetworkManager.git inside of builddeb-XXXX i guess [10:40] doko, mvo: packagekit-backend-apt depends on update-manager [10:40] doko: the computerjanitor stuff is meant to be used by other packages so it needs to be public, but its in the wrong place [10:40] ahh [10:40] mvo, in the wrong place? [10:42] liw: I see stuff in site-packages here on my system from computerjanitor that should be in dist-packages, but let me rebuild to actually verify that [10:42] james_w: are you running latest jaunty? [10:42] mvo, ah [10:44] doko: a quick question: for the use of py_libdir_sh the (loop) variable should be named python, right? [10:44] asac: no, not updated over the weekend? [10:44] james_w: do you have python 2.6 as default? [10:45] asac: nope [10:45] geser: no, the value that you pass should either be pythonX.Y or X.Y [10:45] doko, what should I do to improve my python packages which use cdbs? [10:45] james_w: i would think thats the reason then ;) [10:45] james_w: any trick how i can bzr to use 2.5? [10:46] doko: I've "Package bitbake version 1.8.12-1 has an unmet dep: [10:46] james_w: so yeah ;) [10:46] Depends: python2.4-pysqlite2 [10:46] james_w: python 2.6 booooo [10:46] glatzor: I don't know which packages you do maintain, and I won't look at those suggesting improvements ;) what exactly do you want to know? [10:46] doko: bad paste :( [10:46] james_w: python2.5 /usr/bin/bzr bd --export-only works! [10:47] geser: nothing should depend on pysqlite2 anymore [10:47] doko, you mentioned that not using cdbs would be feauture. so what does it wrong? [10:48] glatzor: I won't start a cdbs discussion. some like it, some not. [10:49] doko: I've "for py in $(PYVERS); do ..." in a rules file, so I use "$(py_libdir_sh)" instead of the hardcoded site-packages. I'm no makefile expert so I don't know from looking at the python.mk if it will work with the variable being named "py". [10:50] asac: thanks, I'm trying to update now [10:51] * asac alias python python2.5 [10:51] ;) [10:51] geser: $ grep 'Call as' /usr/share/python/python.mk [10:51] doko, liw: it looks like I was just confused by the fact that 2.6 stuff goes into dist-packages and 2.5 goes into site-packages. so update-manager should now be ok and install into the right locations [10:51] mvo: yes, I didn't want to change existing locations [10:52] sure [10:53] james_w: let me know when its fixed ... i repointed my python link to 2.5 now [10:53] could we do anything to make builds fails that have the lcoation not updated on the buildds? or add some sort of check to fail if stuff ends up in /usr/local at the end of the build? [10:53] I mean, packages that have no "--install-layout=deb" but get rebuild [10:54] (e.g. because the maintianer overlooked the required change or because of control.in vs control file confusion etc) [10:54] mvo: I think that already happends, in pkgbinarymangler (pkgsanitychecks) [10:55] mvo: these should fail, yes. [10:55] pitti: aha, great. [10:55] mvo: but I found most of my packages FTBFS much earlier, because of wrong *.install files [10:55] but we only check for /usr/local/lib/pythonX.Y, so maybe I just add a check for /usr/local [10:56] pitti: yeah, me too. unattended-upgrades does not have one, so having this additional check is certainly good [10:56] doko: sounds good, e.g. for stuff that is just a python-script with a private dir [10:57] * mvo leaves for lunch [11:02] mr_pouit: I see that there are quite a few xfce4-related sync requests; do these have a FFe somewhere? [11:08] doko: how's python 2.6 going? the extra python has caused a bit of a jump in CD size. :) [11:09] doko: should I expect that to clear up soon, or should I offload some more langpacks in the meantime? [11:09] slangasek: isn't this called collateral damage? ;) [11:09] heh === seb128_ is now known as seb128 [11:10] slangasek: we have one extra python version so extra use is expected no? [11:10] seb128: yes - but it's not supposed to stay that way for release, is it? [11:10] well, the gnome bindings were only built for 2.5 before alpha-5, so python-gnome-*, gtksourceview and deskbar-applet did increase in size [11:11] I'm not aware of other packages going up in size after alpha-5 [11:11] the main difference was that python2.6 wasn't on the CD before, and is now [11:12] slangasek: well we don't plan to drop python 2.5 do we? [11:12] ouch, 1MB compressed larger ... [11:12] seb128: I would assume that we plan to only have one version of python on the CD [11:13] why would you want more than one version of ANYTHING on the cd? [11:14] slangasek: ahh, the static lib is in python2.6. will fix this [11:15] doko: but that's still two versions of python on the CD, which is mainly what I was asking about... [11:15] slangasek: which packages depend on 2.5 on the CD? [11:16] dunno, checking [11:17] if vim is on the CD then vim at least [11:17] looking at vim ... [11:18] doko: hmm - evolution [11:18] vim isn't on the CD, only vim-tiny [11:18] slangasek, seb128 : this should be fixed with the next upload. seb128, do you plan one? [11:19] james_w: may you have a look to bug 336067 later? it's broken since the update to python 2.6 [11:19] Launchpad bug 336067 in python-httplib2 "python-httplib2 needs a patch for Python2.6 support" [Undecided,New] https://launchpad.net/bugs/336067 [11:19] doko: yes, new GNOME versions due today [11:19] pedro_: sure, please assign it to me [11:19] james_w: will do, thanks you :-) [11:19] seb128: if you upload a new evo, can you include the screen size patches, or do they need more work/discussion? [11:20] pitti: I can try, there is just a zillion of those in a tarballs which is going to take a while to review, not to mention that I hate those "add scrollbars everywhere" changes, but shrug [11:21] seb128: yeah, they are ugly; I only sponsor fixes which are reported/discussed upstream, though [11:21] seb128: still, ugly is better than broken on netbooks [11:21] right [11:21] if they don't add frame one normal desktop case [11:21] which some of those changes do [11:21] one -> on [11:23] grrrr at kubuntu [11:23] we are getting a zillion of ""gnome-appearance-properties crashed with SIGSEGV in QGtkStyle::drawControl()" [11:23] gtk-qt-engine is really a crappy crashing thing [11:27] since it exists :) [11:27] seb128: I'd drop it if gtk had a sane default style [11:28] it would have been nice to have python.mk available well before the transition so that I can actually build a source package containing the needed fixes for me to be able to upgrade past the transition [11:29] I think I will add an apport hook to refuse any crasher if that thing is installed and display a warning "you installed that crappy kubuntu hack uninstall it if you want stability" [11:34] * pitti arghs at pidgin ftbfs (libtoolish); Keybuk, seb128, you don't happen to know what http://people.ubuntu.com/~pitti/tmp/pidgin_2.5.4-2ubuntu2_i386.build wants to tell me? [11:34] pitti: run autoreconf [11:35] seb128: right, I could update the 70autoconf.patch, but it built correctly just 7 days ago.. [11:35] pitti: it will not ftbfs on the buildds, the issue is that it runs automake locally [11:35] oh, I see [11:35] pitti: that's a timestamp issue I never bother trying to fix it correctly, it only fails if automake is installed [11:36] tkamppeter, do you happen to know about Brother QL-550 label printer support? [11:40] seb128: weird, pidgin b-deps on automake through intltool [11:42] liw, I know about a third-party driver which is linked from the appropriate printer and driver pages on OpenPrinting, but I did not test it. [11:42] tkamppeter, ok, thanks [11:42] pitti: dunno but some autotools don't get installed and run on the buildd but do locally [11:43] ah, apparently I had automake1.9 installed [11:51] if a main sponsor has some time: bug #336601 [11:51] Launchpad bug 336601 in dput "Modules in use deprecated by python 2.6" [Undecided,New] https://launchpad.net/bugs/336601 [11:59] slangasek, on http://ports.ubuntu.com/ubuntu-ports/dists/jaunty/main/installer-armel/alpha-5/images/ixp4xx/netboot/ there is some discrepancy between the file creation dates [12:00] vmlinuz has a stap from 27th while the other two are from 25th [12:00] *stamp [12:00] ta pitti [12:00] i think something went wrong here [12:01] ogra_: well, I see the same in te 20081029ubuntu21 dir it was copied from... [12:02] weird [12:02] http://ports.ubuntu.com/ubuntu-ports/dists/jaunty/main/installer-armel/20081029ubuntu22/images/ixp4xx/netboot/ has the same dates on all files [12:02] ogra_: so I'm not sure what went wrong, but it went wrong somewhere upstream from the copying I did [12:04] ogra_, did i mention "woo, i got an arm qemu system booting"? [12:04] geser: will you forward bug 336601 to Debian as well? It should work with python 2.5, too [12:04] Launchpad bug 336601 in dput "Modules in use deprecated by python 2.6" [Undecided,New] https://launchpad.net/bugs/336601 [12:05] directhex, no, you didnt, congrats :) [12:06] ogra_, think you could be a sweetheart & document the "mem=32M" bit in the default cmdline? i kept having oom issues until i actually read the kernel config & spotted that [12:06] hmm, i wasnt aware of that and all my docs say -m 256 and append "mem=256M" [12:07] (see https://wiki.ubuntu.com/ARM/RootfsFromScratch ) [12:08] still... http://www2.apebox.org/wordpress/wp-content/gallery/00-single/armless.png [12:08] e [12:10] directhex, i dont build the kernels (our kernel team does) but i'll talk to them to drop that default with the next upload [12:10] ogra_, it'd make it easier for qemu, since you can just use the -m flag [12:10] hey guys, is the python upgrade in jaunty mostly over? [12:11] directhex, yeah, understood ... i didnt even notice since as i said i ude append everywhere anyway [12:11] *use [12:11] ogra_, d-i is sad with only 32M ^_^ [12:12] depends :) [12:12] ahasenack: I would say we're still somewhere towards the middle of the end [12:12] * ogra_ just made it work with the NSLU2 port on 30M [12:12] sladen: cool, thanks [12:12] pitti: sure, will do so now [12:13] geser: thanks; will sponsor in a minute [12:16] doko: python-pqueue is in main because it's seeded (ubuntu.jaunty/development); do you want to remove it from the seed or shall I? [12:16] (once it's out of the seed, there'd be no need for a bug report, it would just get picked up via component-mismatches...) [12:17] slangasek: please do [12:20] Could someone upload my debdiff (with the version and suite target corrected) out of LP: #222532 to intrepid-proposed, please? === ogra_ is now known as ogra [12:30] doko: how do you debug issues similar to bug #332799? [12:30] Launchpad bug 332799 in gnome-desktop "gnome-about crashed with SIGSEGV in PyGC_Collect()" [Medium,New] https://launchpad.net/bugs/332799 [12:33] seb128: try to run it with python-dbg, I suspect it's a missing Py_INCREF somwhere ... see /usr/share/doc/python2.6/SpecialBuilds.txt.gz [12:33] doko: ok thanks [12:36] ogra@osiris:/var/build/versatile$ grep physical /var/log/Xorg.0.log [12:36] [ 4.131326] (II) intel(0): Setting screen physical size to 261 x 163 [12:36] ogra@osiris:/var/build/versatile$ xdpyinfo |grep dimensions [12:36] dimensions: 1280x800 pixels (339x212 millimeters) [12:36] * ogra doesnt get whats sets this [12:36] seb128, does gnome influence my dpi settings in any way to set screen dimensions ? [12:36] ogra: screen dimensions? [12:36] yeah [12:37] ogra: the screen dimension is a physical thing [12:37] xorg detects my display right at 261 x 163 mm [12:37] it doesn't change when tweaking software [12:37] but in my desktop is end up with settings for 339x212 millimeters [12:37] and i cant find out what resets that [12:38] you probably forces the dpi? [12:38] and the resolution? [12:38] well, my gnome capplet has 100dpi in the entry box [12:38] i cant remember ever having set that though [12:38] (it used to be 96) [12:39] ok so that's the xorg detected value [12:39] dunno about the physical screen but that should not be revelant [12:39] you have the dpi value from xorg and the resolution you set [12:39] well, 1280x800 on 261 x 163 would be 124dpi [12:39] which is what should matter for what you get on screen [12:39] and 261 x 163 is the right value (i used a ruler :) ) [12:39] slangasek: the python2.6 package gets 1.4MB smaller (compressed) [12:40] doko: ok :-) [12:40] ogra: dunno then, try a non GNOME session and see if you get the same issue [12:40] will do, good suggestion :) [12:41] oh, unsetting the dpi value in gconf-editor suddenly gets me huge fonts :) so i apparently have touched it before [12:42] hrm, and calling the capplet forces it to 96 ... [12:42] weird [12:42] * ogra tries an xterm session [12:44] seb128, hmm, seems gnoe actually sets it [12:44] in the xterm session i have matching values [12:44] ogra: do you have a .config/monitor.xml? [12:45] yes [12:45] ogra: can you move it somewhere else and try restarting your session and see if that's still an issue? [12:45] yep [12:47] seb128, ok, removing it *and* unsetting the gconf key gets me the right kes [12:47] *key [12:48] ok good [12:48] so know you need to figure what you do to get a buggy config ;-) [12:48] seb128, its a bit tricky, if you once touched the advanced font settings before in a former release or with the monitors.xml in place it will enforce 96dpi [12:48] I guess using the xrandr capplet once to get a config.xml and restarting the session is enough to get the issue [12:49] hum, it should not write the gconf key if you don't change the dpi value [12:49] i seemingly had used the advanced font settings before [12:49] I think there is a bug about the config forcing 96 dpi [12:54] jelmer: your debian/copyright on bzr-fastimport omits exporters/svn-archive.c and exporters/svn-fast-export.c [12:55] slangasek: Hi [12:55] slangasek, Thanks, I'll fix that; fwiw those files are not part of the binary package [12:55] wow [12:55] * ogra wasnt aware how crisp his display can be [12:55] slangasek, I thought bzr-fastimport was rejected though, because it wasn't processed before the FF? [12:55] jelmer: ok - I was going to accept it anyway, that's why it was a throw-away comment on IRC instead of a mail ;) [12:56] jelmer: it's being revisited following a discussion with motu-release the other day [12:58] slangasek, ah, cool === fargiola` is now known as fargiolas [13:11] hmm, what the heck starts notify-osd [13:11] dbus [13:11] that's a dbus service [13:11] hmm [13:11] * ogra would like to get it to not popup *under* the panel [13:12] * NCommander wonders if he was the only one who thought the disappearing update manager icon was a bug, and not a feature. [13:12] so i can actually read the notifications :) [13:12] there is a bug open about that [13:12] it seems to depend of the start order [13:12] restart notify-osd [13:14] * ogra did that and waits for a notification now [13:14] you can use notify-send txt [13:15] i just uninstalled libnotify-bin yesterday in a cleanup spree :) [13:15] slangasek, bug #336180 acked [13:15] Launchpad bug 336180 in gtk2-engines-xfce "Please sync gtk2-engines-xfce 2.6.0-1 (universe) from Debian experimental (main)" [Wishlist,Confirmed] https://launchpad.net/bugs/336180 [13:16] hmm, i got a mail, but no notification [13:16] cody-somerville: there's a bunch of others related to xfce 4.6 - are they acked collectively, or do you want me to subscribe you to each for review? [13:16] slangasek, acked collectively [13:16] cody-somerville: ok, thanks [13:16] slangasek, no problem. [13:17] aha, it pops up in front now (with notify-send) but not on the edge of the screen anymore [13:19] but no mail notification at all === kyselejsyrecek is now known as kyselejsyrecek_p === kyselejsyrecek_p is now known as kyselejsyrecek [13:50] shutil.move completely changed semantics in python2.6, fantastic [13:51] james_w, yay for python? [13:51] indeed [13:52] james_w, given recently published numbers (was it by jdong? i think it was jdong) i'm gonna have to stop jokingly suggesting ironpython as a replacement, tho [13:53] so it was actually fixing a bug: http://bugs.python.org/issue1577 [13:53] "I'd rather not do this. It might cause disasters for code that expects [13:53] the old semantics. If you want a way to do the "mv" semantics, propose [13:53] a new API. [13:53] " [13:55] james_w: which package was broken? [13:55] bzr-builddeb [14:09] doko, http://pastebin.com/d1864c445 [14:09] doko, based on discussion with mvo on #ubuntu-testing, pasted the above link to you :) [14:11] Keybuk, seems we have a prob with ltspfs in jaunty, to me it looks like the rules dont fire the scripts anymore (bug 335767) did anything change in recent udev that could cause that ? [14:11] Launchpad bug 335767 in ltsp "Jaunty Alpha 5: Usb stick (flash drive) does not pop up on the Gnome desktop" [Undecided,New] https://launchpad.net/bugs/335767 [14:15] nags, mvo: it's a bug in ropemacs, the substvars are wrong (s/Python/python). see the warnings in the build log. apparently nobody checked the binary before upload/sync request [14:21] ogra: lots of things changed [14:21] doko, ok [14:22] Keybuk, well, i would assume the rules should still fire if a matching device is plugged in, probably the script arguments arent right anymore, could you tale a look ? i attached the currently used runes to the bug [14:22] ogra: no, I don't have LTSP here [14:22] start debugging using udevadm monitor -e to see what's firing and what environment are available [14:23] use udevadm test to make sure your rules are being run correctly [14:23] use udevd --debug to really get in depth [14:23] err s/runes/rules indeed [14:23] Keybuk, ok, i'll add that to the bug to get info out of the user [14:24] (i dont run ltsp myself anymore either) [14:24] actually I quite like runes [14:24] we should rename it upstream to /etc/udev/runes.d [14:25] hehe [14:28] yippie, i got working notifications again, seb128 thank for the pointer, adding a wrapper script that makes notify-osd sleep for 5 secs seems to help [14:28] *thanks even [14:28] you're welcome [14:37] james_w, gah that's probably what started causing crashes in mythbuntu-common (shtuil.move stuff changing) === The_Company is now known as Company [15:16] ops === davidm_ is now known as davidm === fargiol`` is now known as fargiolas === ssweeny_ is now known as ssweeny [16:17] Mithrandir, StevenK: mind taking a look at bug #331973 (and eventually taking over handling this ffe?) [16:17] Launchpad bug 331973 in telepathy-idle "Ship telepathy-idle 0.1.3" [Wishlist,New] https://launchpad.net/bugs/331973 [16:25] seb128: I've also got a universe FFe for you: bug #334813. mind taking a look? [16:25] Launchpad bug 334813 in evolution-rss "installing evolution-rss removes evolution" [Undecided,New] https://launchpad.net/bugs/334813 [16:25] sistpoty|work: granted [16:25] thanks seb128 [16:25] you're welcome [16:28] Riddell: and one universe FFe for you at well (i.e., at least one, I'm just going through the list): bug #334121... mind taking a look there? [16:28] Launchpad bug 334121 in plasma-widget-translatoid "Update to 0.6" [Wishlist,New] https://launchpad.net/bugs/334121 [16:32] would a core-dev help me by updating mobile-broadband-provider-info? Current version (20081015) lacks one of the major danish providers and support questions for this are frequently popping up. #motu told me to go hunt for a core-dev. Bug 317860 [16:32] Launchpad bug 317860 in mobile-broadband-provider-info "Request to upgrade to latest SVN" [Undecided,Confirmed] https://launchpad.net/bugs/317860 [16:35] Riddell: FFe's at bug #334690 and bug #335031 also look KDE related, mind taking a look at these as well? [16:35] Launchpad bug 334690 in kblogger-kde4 "Update kblogger to 1.0 alpha 3" [Wishlist,New] https://launchpad.net/bugs/334690 [16:35] Launchpad bug 335031 in filelight "New upstream release filelight 1.9~beta for kde4" [Wishlist,New] https://launchpad.net/bugs/335031 [17:06] asac, bug #279365 please review it [17:06] Launchpad bug 279365 in ubufox "Hungarian locale update for Intrepid ubufox" [Undecided,New] https://launchpad.net/bugs/279365 === DktrKranz2 is now known as DktrKranz [17:12] Keybuk: is there anything we can do to make AppArmor start faster? sounds like it's eating 1 second at boot? [17:14] kees: I haven't looked at it [17:14] it looks like it's the parser though [17:14] Keybuk: hrm, yeah. too bad -- that's the part that got speed-ups between 2.1 and 2.3 (i.e. we have the fast version already) [17:15] Keybuk: also, yay http -> https for merges. :) [17:15] could it be done in the background alongside something else? [17:16] Keybuk: possibly -- though it needs to be started ahead of any processes it's going to confine. [17:16] Keybuk: we've already run into issues with that for dhcp client. [17:16] sianis-devel: done [17:16] Keybuk: do you have any bootcharts handy that shows it? [17:18] kees: http://people.ubuntu.com/~scott/boot-performance/mini9_jaunty-20090218-7.png [17:19] Keybuk: we could run it in parallel to the fsck [17:19] that's the sleep just above it? [17:20] I want to get rid of that sleep too ;) [17:20] does it have to be complete before anything in particular happens? [17:21] Keybuk: basically, before any daemons it confines start up [17:21] dhcp client is already protected to wait for AA to start up [17:21] is that sleep from the fsck script or from procps? I can't quite read that [17:23] fsck [17:23] hmm [17:23] doesn't that give you a deadlock? [17:23] udev waits for ifup which waits for dhclient which waits for apparmor which waits for udev ? [17:24] can what it parses not be precompiled? [17:24] Keybuk: I don't think it deadlocks -- we can check with jdstrand [17:24] udev calls ifup, remember [17:24] Keybuk: precompiled -- possibly, but it'd need features from AppArmor [17:25] right, but isn't dhclient spawned (i.e. not waited on)? [17:25] can't remember [17:25] and aa doesn't wait for udev [17:25] it just reads files, parses them and shoves them into kernel space [17:25] its parser does seem very expensive [17:25] what is it? XML? [17:26] Keybuk, kees: udev calls idup as a daemon [17:26] no, it's just reading the /etc/apparmor.d/* files, and making a kernel-space DFA out of them, AFAIU [17:26] ifup [17:26] Keybuk: it will not deadlock [17:26] so, err [17:27] if things udev calls depend on apparmor [17:27] why do you call it after udev? [17:27] do you need /usr mounted? [17:27] we don't need /usr (parser is in /sbin) [17:27] I'm happy to relocate aa [17:27] Keybuk: basically, I thought adding an intelligent ifup-pre.d script would be easier to get in and be less expensive than moving apparmor [17:27] I've just not be entirely certain where to put it [17:28] how often do the things it parses change? [17:28] kees: all we should need it securityfs mounted and /sbin/apparmor_parser [17:28] Keybuk: rarely [17:28] jdstrand: right [17:28] Keybuk: very seldom [17:29] Keybuk: have the boot changes made it into the stock image yet? [17:30] could you put it in the initramfs and run it while we're trying to find the root filesystem ? [17:30] calc: there are a lot of changes, some of them have, some of them are still pending [17:30] Keybuk: ok [17:30] Keybuk: we'd need to check where the securityfs is mounted from, but yeah, probably. [17:30] * calc wonders how fast his laptop will boot with all the changes, it can do 100MB/s to disk :) [17:30] Keybuk: I may have missed something-- is the dhclient pre up script causing a problem/slowdown? [17:30] Keybuk: it'd need to copy the entire contents of /etc/apparmor* into the initramfs [17:30] calc: do you have an SSD? [17:31] jdstrand: no, just aa itself. [17:31] Keybuk: no, a 7200rpm hdd [17:31] I see [17:31] jdstrand: it's taking 1 second for itself. [17:31] calc: then you are doomed for a slow boot forever [17:31] jdstrand: but could be run in parallel somewhere [17:31] Keybuk: lol :) [17:31] Keybuk: i was getting ~ 20s boots with my old laptop before i got this new one [17:31] of course that was 20s to gdm [17:31] calc: 20s to a full, logged-in desktop? [17:31] FAIL [17:31] :p [17:31] heh [17:33] unless the seeks eat too much time it should be close to as fast as the netbook, my cpu is 50% faster and hdd is > 100% faster than my old laptop [17:33] at least for sequential reads [17:33] anybody know of software/strategies for scraping points off a graph image? [17:33] ugh wrong channel [17:34] calc: boot is all about how fast your disk is [17:34] and your seek time is SLOW [17:35] Keybuk: true but doesn't readahead fix that? or is it not being used anymore? [17:35] readahead partially fixes it [17:35] but our gathering has been pretty poor for it in the past [17:36] ok [17:36] so it appears to be quite pessimal compared to sreadahead [17:36] Keybuk: in the bootchart you gave, where is the root fs mount happening? [17:36] kees: before where "rc" starts [17:37] ie. run alongside the udevd that's there [17:37] okay, gotcha [17:37] though that part is probably too CPU contended :-/ [17:37] would be worth testing though [17:37] my /etc/apparmor* is well over 320K... [17:38] a relatively stock install is about 260k [17:38] is there really no way to compile that down to something smaller and easier to read? [17:38] there is no existing way that I know of. [17:39] (this is one down-side to "dynamic label" MAC) [17:39] we might be able to write a parser that only includes files that are included (which could avoid some of the stuff in /abstractions) [17:40] I doubt that would save much [17:40] lol glad I'm not the only one with oversized apparmor.d :) [17:41] jdstrand: yeah. [17:41] Keybuk: is bloating the initrd really worth it? [17:43] kees: what if you loaded profiles on demand? or at least, load most profiles after login? [17:43] Keybuk, looking at the end of http://launchpadlibrarian.net/23302773/udevadm_test_dev_sdb.txt it seems udev actually calls "ltspfs_entry add sdb" as it should, do you know if anything wrt environment handling in udev changed ? the script expects to find LOCALDEV=True in the global environment to actually do something [17:44] Im not sure if this is the place to ask, but does anyone have experience with distcc/pump? I have it semi working and feeling its now working correctly [17:44] *not [17:44] jdstrand: hm, as part of the target process's init script? [17:44] kees: possibly [17:45] kees: just OTOH we could have a really lean apparmor initscript that just mounts securityfs [17:45] kees: no idea without testing [17:45] jdstrand: I think we could just move it earlier and have it run in parallel during the fsck bit [17:45] kees: I'll probably try it at some point [17:45] kees: but given the security issues, I've generally just left it alone [17:45] slangasek: If you have a moment to put your archive-admin had back on to finish the clamav backport to Dapper, I've uploaded all the source backports and the input for syncbugbot is at https://bugs.launchpad.net/dapper-backports/+bug/335724/comments/2 [17:45] Ubuntu bug 335724 in dapper-backports "Please backport clamav 0.94.dfsg.2-1ubuntu0.1 from Intrepid to Dapper (source)" [Wishlist,Fix released] [17:46] ogra: does udevadm monitor show that LOCALDEV is in the environment? [17:46] ogra: your test does not appear to include it [17:46] oh, good question [17:46] * ogra looks [17:46] jdstrand, Keybuk: how about this: two part init: one starts at like S01 and backgrounds itself, then the S37 just blocks until the S01 component is finished? we already have the logic for it in the dhclient scripts [17:47] kees: possibly, though I'm wary that the CPU is fairly bound up until that point [17:47] Keybuk, hmm, i dont even see PATH [17:47] such things can actually make things slower [17:47] ogra: PATH is inherited by udev [17:47] (http://launchpadlibrarian.net/23299761/udevadm_monitor-e.txt) [17:47] kees: so S01 mounts securityfs? [17:48] jdstrand: S01 would do everything S37 does now. S37 would just block until apparmor_parser was finished [17:48] Keybuk: there's a ton of CPU time available during the fsck phase [17:48] Keybuk, so did that change recently ? it seems it only stopped working recently [17:48] Keybuk: like right after procps [17:48] oh I see-- that wouldn't help the boot time would it? or am I missing something? [17:49] kees: note that the fsck ends well before the sleep [17:49] jdstrand: it should help boot time because the CPU load would happen earlier [17:49] in fact the fsck takes virtually no time [17:49] so you should consider that sleep to be a bug that will be fixed ;) [17:49] Keybuk: oh. :) heh [17:49] ogra: did what change recently? [17:49] (the same user did an ltsp test at the beginning of the jaunty cycle and didnt report issues, ltspfs didnt change apart from teh install target for the rules) [17:49] Keybuk, the environment handling [17:49] Keybuk: well, even when it's only AA loading, it's only at 50% cpu [17:49] Keybuk: so it seems like moving it earlier could help [17:49] kees: you mean "using an entire core" ? :) [17:50] ogra: I could read the changelog for you [17:50] ogra: but I'm not going to :) [17:50] Keybuk: d'oh, is that a dual core? heh [17:50] :P [17:50] kees: I think it pretends to be [17:50] not sure [17:50] there's enough "exactly 50%" stuff there [17:50] $ grep sleep /etc/init.d/* | wc -l [17:50] 63 [17:50] *cry* [17:51] kees: you, since it is dynamic labeling, what would be most cool is for apparmor to not actually load the profile until the protected binary is called [17:51] s/you/you know/ [17:51] jdstrand: yeah, have the kernel call out for it. [17:51] kees: exactly [17:52] . o O { binfmt module ? } [17:52] no [17:52] evil [17:52] BAD [17:52] BAD [17:53] BAD [17:53] :) [17:53] it would need to be lighter than that: i.e. user space tells AA what to call out for, then when one of those executes, user space loads the DFA. [17:54] seems like a lot of engineering for this "problem". [17:54] Keybuk: out of morbid curiosity, which sleep is that in your bootchart? [17:55] I don't know [17:55] I haven't found it yet [17:55] that's why it's still there ;) [17:55] it's an insidious hiding sleep [17:55] I don't quite understand why the script only appears as "sh" either [17:56] hmm, i cant seem to find anything environment related [17:56] or why logsave runs for so much longer afterwards [17:58] Keybuk: well, I assume it's related to the trickiness pitti created for the usplash-integration-and-skipable-ness. [17:58] though there aren't any long sleeps in there. [17:58] that's my guess [17:58] but as I said, I can't quite find it yet [17:58] * kees nods [17:59] it vexes me === fader is now known as fader|lunch [17:59] Keybuk: hm? [17:59] Keybuk: scripts in /lib/init/ perhaps? (they are sourced) [18:00] pitti: the longest sleep in there is the 0.5 in the progress loop. [18:00] doesn't seem likely. *scratch head* [18:01] udev? :P [18:01] nm [18:03] Keybuk: seems crazy but, could stuff like "exec 9<&0 (btw, someone has just asked me why rsync runs by default at boot on Jaunty) [18:05] RainCT: it doesn't [18:05] * kees holds onto his hat while apt-get dist-upgrade runs [18:06] rsyncd ? [18:07] Keybuk, hmm, but each of these not run scripts still spawns a subshell to check for the default value [18:08] not that it would be much time, but it still costs some [18:08] ogra: ? [18:08] rsync [18:09] rsync is installed on every ubuntu system, on boot it spawns a /bin/sh, sources /etc/default/rsync and exits [18:10] Keybuk, so these actions take time [18:10] nanoseconds likely, but they do [18:11] correct [18:12] so its not a totally unreasonable question why we do include these off-by-default scripts [18:13] its one useless fs access at least to read the defaults [18:15] ogra: I don't get why rsync isn't separated into a client and server... [18:15] I mean the rsync command is very useful IMO [18:15] but rsyncd has less of an average user usecase [18:16] yeah, especially since you can use a daemon like mode through ssh [18:19] right. That's my #1 usecase for rsync. [18:19] #2 would be for long local copies where its progress indication is helpful [18:37] mpt: Btw, on a dual head setup notify-osd doesn't show up on the same screen as gnome-panel. Should I file a bug about it? [18:38] RainCT, any new bubble should appear on whichever display the mouse pointer is on at the time. If that's not happening (or if that's a horrible design for someone reason), please do report a bug. [18:40] mpt: Oh. Just tried moving the cursor around and it's always on the same screen. (And yesterday it was on the other one.. :P). [18:40] (I'm on Intrepid, though, not sure if that makes any difference..) [18:40] ok, that's a bug then :-) [18:40] I don't think that makes a difference, that's core notify-osd behavior [18:44] anyone here with a huawei 3g stick that uses the "normal" option driver? [18:45] asac: I used to use one :P. What's the "normal" option driver? [18:45] RainCT: the not normal option driver is "hso" ;) [18:45] RainCT: if you dont have it anymore it doesnt matter ;) [18:46] I don't see anything like that in nm-applet === thekorn_ is now known as thekorn [18:48] mpt: Alright, filed bug #336848 [18:48] Launchpad bug 336848 in notify-osd "Notifications show up on the wrong screen" [Wishlist,New] https://launchpad.net/bugs/336848 [18:48] thanks [18:49] Keybuk: it is the usplash sleep -- it's just showing up as a single process when it's multiple sleeps. (I see the same from the dhclient sleep 0.1) [18:49] Keybuk: my boot chart is silly slow [18:49] hmm, interesting [18:50] why is it even sleeping [18:50] fsck has no progress to report [18:50] Keybuk: from looking at the loop, I think it leads with a sleep instead of ending with a sleep. [18:51] but it's got 0.5 granularity, so dropping it to 0.1 would probably make the bulk of it go away [18:51] my bootchart is ALL io bound. [18:51] it seems like readahead-list isn't backgrounded? [18:52] could it just not sleep at all? [18:52] kees: readahead isn't backgrounded deliberately [18:52] ah, cool. [18:52] Keybuk: check with pitti, the scripts are pretty sensitive there [18:59] apw: ogasawara ping [18:59] any of you guys (or anyone else from kernel debug team) here? [19:00] BUGabundo, ? [19:00] so that vbgunz can find help with his SATA disk prob on resume? [19:00] hi apw... meet vbgunz [19:00] vbgunz: please describe your prob [19:00] do you have a LP bug too? [19:00] is it a kernel problem? === fader|lunch is now known as fader [19:00] hello everyone. Been on Jaunty for a while and everything is great. honest. just great. *but* no matter what I try, I can never suspend to ram or disk whether S1 or S3 in bios, BIOS or OS wakeup. everything comes back from resume after about 1 minute *but* the sata disk is dead :( [19:00] if so do it over on #ubuntu-kernel [19:01] and how do you know the disk is dead? [19:02] apw: I cannot read or write to it, and somewhere in the terminal I always get a I/O denied to /dev/sda which is my sata disk [19:02] (using a multimeter ? :) ) [19:02] heeheheeh [19:02] heh [19:02] ogra: just can't "shock" it to life... [19:02] are you able to run dmesg? [19:02] specifically if you run dmesg before you suspend [19:03] so its caches first [19:03] BUGabundo, cold water might ... [19:03] I cannot run any sudo commands at all what-so-ever ... e.g., sudo mount -a ... that disk is dead when I resume :( [19:03] yep, you would need the command to be already loaded [19:03] well, after about 1 minute after resuming everything appears on screen the way I left it [19:03] it sleeps in seconds. wakes up after about a minute. cannot do anything [19:03] so run dmesg, suspend, resume, run dmesg [19:04] and see if that at lest lets you see the kernel logs from the suspend/\resume [19:04] apw: do you think a serial link could help debug it too? [19:04] if they can see the dmesg output we'd be ok [19:04] I tried the 2.26.29 kernel from ppa. I read the resume/suspend was solved in that version *but* no matter what. I get the same results :/ [19:06] apw. even if I could see the anything, I wouldn't know what to do with it... I thought I would be slick the other day but no matter, so much reading and writing is supposed to happen on my sata that I cannot do anything... I tried creating a file on MS and the file protocol died [19:06] you got a digital camera? [19:06] photos is a common way to get the information to us [19:07] heh, believe it or not, sent it in for repair :/ [19:07] always the way [19:07] well you can give us a feel for whats in there if it comes out [19:07] I tried asking this in the ubuntu channel and google but It might be a bit advanced of a question. Is there a way from the kernel arguments on start up to make a live session automatically use restricted drivers over the OSS ones? [19:07] I've got 2 sonys, both died at the same time. worse ever :/ [19:07] anything relating to the disk [19:08] well. I have other disk... Cant I just reroute these messages or logs to my IDE drives? I think they come back *but* I am not absolutely sure... I cannot do anything from the desktop about it :( [19:12] vbgunz: $dmesg > /mountpoint/otherdisk/log.txt ? [19:13] or $ pastebinit -i /var/log/kernel.o.log [19:14] so can you switch to VT-1 ? [19:14] something else to try [19:14] sounds like BUGabundo can talk you thought it all :) [19:14] me ? noo lol [19:15] then get a bug filed with all the info [19:15] agaainst the linux package [19:15] we do need that dmesg output i recon [19:16] * BUGabundo vbgunz you can always zero absolute the machine and dump the contents of the memory while in resume eeheh [19:16] man anything to get a better log [19:17] I dont want to break anything. everything is fantastic. godforbid I suspend though. nightmare :( [19:19] damn. I thought I saw a command in here. dmesg, sleep, resume, dmesg or something [19:20] ok can someone provide the command to keep my logs or dmegs going to my MS *after* resume? [19:20] I'll try it now just to bork it all *but* hopefully I can save a log [19:27] cjwatson: absolutely brilliant blog post, thanks so much for that [19:28] * highvoltage fires up liferea [19:33] slangasek: why would my sync requests need a FFe? It updates xfce* from 4.6rc1 to 4.6, which is bugfix-only, and thus doesn't require a FFe (and this was described in the sync requests...). [19:36] the second dmesg was never written. My bios though was using S1. I have better luck with S3 ... atleast I get back to a dead desktop :) [19:36] am going to try it again... [19:37] bye [19:37] let me know how it goes [19:40] hi [19:41] hello [19:46] yeah! I got the second dmesg [19:46] in it are the I/O errors I was talking about [19:46] do you guys want the one *before* and *after* or just after? [19:47] http://dpaste.com/4775/ [19:47] thats after [19:49] IntuitiveNipple: I managed to save a dmesg after a failed resume, can you check it out http://dpaste.com/4775/ ? [19:51] vbgunz: That's better! Add it to the bug report [19:51] ok [19:52] I think the hell starts at line 1283 [19:52] sda is my sata disk that keeps dying on resume [19:53] vbgunz: Let's switch this conversation to #ubuntu-bugs [19:53] ok there [19:57] mr_pouit: hmm, I don't see any mention in bug #336180 that this was bugfix only... anyway, approved by cody-somerville, so all done now :) [19:57] Launchpad bug 336180 in gtk2-engines-xfce "Please sync gtk2-engines-xfce 2.6.0-1 (universe) from Debian experimental (main)" [Wishlist,Fix released] https://launchpad.net/bugs/336180 [19:57] "This is the final release (jaunty ships the rc1 for the moment). There's no Ubuntu delta." [19:58] I don't know lots of upstream developers that add new features between a RC and the final release. ;) [19:58] slangasek: Did you see my earlier ping about clamav? [19:58] ScottK: yep, was just grabbing it now [19:58] slangasek: Great. Thanks. === beuno_ is now known as beuno [20:02] mr_pouit: Oh, you're so trusting! :-) [20:03] maxb: I'm subscribed to svn commits, so, kind of :P [20:04] ah, fair enough. If you can truthfully state "I have verified the changes between rc1 and final are bugfix-only in nature" then you should definitely do so in the bug - then there's no ambiguity regarding the need for a FFe [20:07] So... I have a perplexing problem. Recently, in Jaunty, one of my partitions (and only one, out of three ext3 partitions on the disk) has suddenly started getting the wrong uuid in /dev/disk/by-uuid/ - it's not even the right format - rather than being a true UUID, it's just 16 hex digits. Any prods towards where I should be debugging? [20:08] btw, blkid is still reporting the true uuid [20:28] zul_: fyi, I'm planning to request a FFe for samba 3.3.1 and handle the merge on it [20:29] (there's a bit of cruft I want to get pulled out of the Ubuntu delta...) [20:29] slangasek: what cruft? [20:29] zul_: changes to every one of the .po files; plus some winbind changes that are obsolete because they were done in Debian in a different way (but the patch still applies) [20:30] slangasek: sounds good to me === zul_ is now known as zul [20:38] fellas. the pci=nomsi solution worked. I could actually resume from a suspend... I am just curious. is this a good idea or what? I feel it could be hackish or not wise. would like any input on solving the real problem if one exists [20:39] im excited. I need to try suspending one more time. brb hopefully without rebooting [20:40] no way. this is just great :D [20:41] pitti: followed up to the email [20:41] wow. my second resume. its working for me :) [20:42] pitti: looks like OOo schedule is going to slip yet again, so i'm glad we stick with the version released at feature freeze :) [20:42] pitti: the first rc looks like it will be released march 19 and possibly 6 or more rc's will be needed (like with 3.0) [20:49] 6 or more RC's? O_o [21:05] calc: ping === savvas_ is now known as savvas [21:10] where might i find someone to help with an lpia build error? [21:10] * kirkland sees no #ubuntu-lpia channel [21:11] kirkland, lpia is just i386 really [21:11] kirkland, whats your build problem? [21:11] kirkland: #ubuntu-mobile, possibly? [21:11] cody-somerville: http://launchpadlibrarian.net/23315733/buildlog_ubuntu-jaunty-lpia.kvm_1%3A84%2Bdfsg-0ubuntu6~ppa1_FAILEDTOBUILD.txt.gz [21:11] Mithrandir: thanks. === savvas_ is now known as savvas [21:13] cody-somerville: nevermind [21:13] cody-somerville: found my problem, sorry to bother [21:14] :) [21:16] Keybuk: around? did you get a chance to read my comments on https://bugs.launchpad.net/bugs/71418 [21:16] Ubuntu bug 71418 in sysvinit "/etc/init.d/(halt|reboot) disables WoL" [Low,Confirmed] [21:19] cjwatson: thanks for saying something about expiring bugs on planet today. that has really annoyed me as the list of minor bugs i have reported over the years has constantly been chomped at by karma hunters... === savvas_ is now known as savvas [22:06] james_w: hi - do you have a workaround/patch for bug 336686? [22:06] Launchpad bug 336686 in bzr-builddeb "merge mode doesn't work under python2.6" [Critical,In progress] https://launchpad.net/bugs/336686 [22:06] mathiaz: in a branch [22:06] I'm trying to prepare an upload now [22:06] james_w: great - mysql-dfsg-5.1 will be happy again after that :) [22:06] if can tell you what to edit if you need it to work right now [22:07] though I will need to get an FFe for this upload, perhaps I should upload the fix for that directly [22:07] james_w: that would be helpful [22:07] james_w: I've --export-only and then debuild -S [22:07] good idea :-) [22:08] james_w: hm - expect the dsc file is not there [22:09] james_w: oh - nevermind [22:27] LaserJock,alex-weej: glad you liked it [22:28] cjwatson: you nicely articulated exactly what I've been thinking [22:28] made my day [22:31] * ScottK gives a big +1 for cjwatson's blog post too. [22:31] Definitely much more diplomatic than I'd have managed too. [22:33] * ogra wants a t-shirt "Bugs are not like fruit" :) [22:34] * directhex hands ogra an apple with some bugs in it [22:34] :P === thekorn_ is now known as thekorn [23:03] yeah. after walking away and leaving the system suspended in ram for 30+ minutes. I turn it on and all is well *but* I am not prompted for a password :( [23:03] should I just make a script that'll lock up the system *then* suspend? === mneptok_ is now known as mneptok === ubott2 is now known as ubottu === jpds_ is now known as jpds === _steron is now known as steron === jpds is now known as Guest18936 [23:32] So, EOL for Dapper on the desktop, June 1 or June 30? [23:32] Is there anything authoritative in writing anywhere? [23:33] https://wiki.ubuntu.com/DapperReleaseSchedule <-- looks like June 1st, but I can neither confirm, not deny. [23:33] s/not/nor/ === steron745 is now known as steron [23:34] Nafallo: yeah, that's far from really clear on it [23:34] the support cycle is generally measured from the actual release date. I haven't heard otherwise from anyone regarding dapper. [23:34] That would imply it's June 1 though [23:35] slangasek: nowhere (that I've found) really spells out how support will continue for servers for the remaining two years [23:35] Presumably a subset of packages will still receive security support [23:36] yes, that's the intent; I don't know the details of what will or won't be included in the server security support [23:36] nijaba: is that your department? [23:36] I'm just looking for something vaguely authoritative to point my management at [23:39] Caesar: check this script: https://launchpad.net/ubuntu-maintenance-check [23:39] slangasek: https://code.launchpad.net/ubuntu-maintenance-check will tell you which packages are maintained for how long on any given system. Seeds have been reorganized so that we can tell. [23:41] nijaba: the historical dapper seeds have been reorganized? [23:41] Caesar: http://www.ubuntu.com/products/whatisubuntu/serveredition/benefits/lifecycle should be considered authoritative by your management [23:41] slangasek: yep [23:42] ok, great [23:42] slangasek: that's what I started with, then moved up to current [23:42] slangasek: I am glad Colin helped though :-) [23:43] :-) === jussio1 is now known as jussi01 [23:45] nijaba: there are exactly zero precise dates at that URL [23:45] So I have to operate on the assumption that it's the release date + n months [23:45] Which is fine [23:45] Caesar: oh, you want precise dates. then your assumption is right [23:46] That URL also doesn't clarify what goes on in the 3-5 year life of an LTS [23:46] Caesar: but you are right, I think we should start an EOL announcement page [23:46] \o/ [23:46] slangasek: that would be more in your field, but I'd gladly start something [23:46] nijaba: Are past-EOL packages going to be moved to old-releases? [23:47] scottk: that'd be mad crazy difficult [23:47] how'd that work? [23:47] (so I really hope not) [23:47] nijaba: I'd be happy if you could get it started. Previously the EOL announcements have all followed the same pattern, so there wasn't much need to draft [23:48] slangasek: what I thought was more of a summary page with release and EOL dates [23:48] elmo: I have no idea, but leaving them in place leaves an odd catagory of packages that hasn't previously existed. [23:49] Generally not supported means community supported. [23:49] nijaba: hrm, ok [23:49] As a community dev, am I still expected to care about these packages? [23:49] slangasek: hi, I just commented out about skrooge in NEW. [23:49] slangasek: what did you have in mind? [23:49] ScottK: I think those packages are EOL [23:49] If not, that makes clamav backports for Dapper much easier after June. [23:49] not community-supported [23:49] slangasek: also as promissed I fixed kdesudo packaging properly and fixed the seeds so that the dvd depends on kdesudo and not kdesudo-kde4... [23:50] It seems odd to have them there, but not there so to speak. [23:50] they're there, but the just have no support whatsoever, as far as I can tell [23:50] *they [23:51] nijaba: I assumed you were talking about how to properly communicate the dapper EOL when it's announced. I don't know that a wiki page to track what's EOLed should be necessary, shouldn't it be enough for the website to state the release dates + the support length? (don't we have this already?) [23:51] Tonio_: ok, thanks :) [23:52] slangasek: I just thought that it might be clearer if, instead of the algorythm to compute the date, we actually write them down so that people don't have to be guessing [23:53] +1 [23:54] slangasek: but I'll start a draft of the dapper desktop EOL, as it might need more details than the usual one [23:54] anyway -> really bed time for me now