[00:07] hm, should openldap2.3 be removed from the archive to avoid confusion? [00:26] alex-weej, so, here i am ... what do you want to discuss ? [00:31] (i think michael r. head explained the filtering very well already ... and youself pointed out the broken threading on the webpage ... so i dont actually see any point on going on to discuss it, but i'm available if you want to) === mcasadevall_ is now known as NCommander [04:12] pitti: poor you with rm --one-file-system.... I had the same problem a few months ago zapping a temp home dir, not knowing ~/.gvfs mounted a samba share I viewed [04:17] jdong: yeah, I'm a bit leary of the .gvfs stuff [04:21] LaserJock: particularly since I was unaware of the .gvfs automounting behavior.... boy that should really get some release note red warnings! [04:25] jdong: yeah, I almost did some stupid stuff because of it === beuno_ is now known as beuno [06:41] nxvl: dude. include a payload with your pings. :) [06:44] cjwatson: feeling better? :) [06:45] Good morning [06:49] Morning pitti [06:51] cjwatson: yes, sorry i just ping you and then realiza that you were sleep [06:51] cjwatson: i didn't take the tz in account, so i just left there [06:51] :D [06:54] Chipzz: not really [06:54] I wouldn't be up before 7 if I were feeling well [07:53] I'm stumped [08:08] tkamppeter_: ping [08:08] * thorwil waves to sabdfl [08:09] hey thorwil [08:10] sabdfl, i'm wondering whether you got my mails? [08:39] moin [08:42] hi, I installed the glfrx-control to tweak my ATI card via the control panel. But settings I set in here, where are they stored ? [08:57] cjwatson: did you file a bug on LP about that bug when doing a manual install with encrypted LVM ? [08:58] cjwatson: It complains of unsafe swap space :( (it's in the encrypted LVM so shouldn't) [09:23] bryce: could you have a look at bug #251059 when you're up? [09:23] Launchpad bug 251059 in xorg "Intrepid: Monitors with incorrect EDID have no display and no safe mode" [Undecided,New] https://launchpad.net/bugs/251059 [09:40] ah, a new ATI driver came out [09:41] it says it introduces product support for Ubuntu 8.04 production support... [09:41] im not sure what that means [09:41] and it supports new cards [10:08] cjwatson: so, I've had some time to look at your auto tools problem [10:10] hey Keybuk! [10:11] Keybuk: I've some libtool2 issues [10:11] good morning Keybuk [10:12] seb128: what are your issues? [10:13] Keybuk: sec, getting the details again, I fought with that yesterday [10:17] asac: ah, sorry, my fault; I didn't copy epy to -updates yet [10:20] Keybuk: in fact that's gtk which seems to do something stupid, I'm wondering why that works when using libtool1.5, http://people.ubuntu.com/~seb128/configure.in has "deplibs_check_method=`(./libtool --config; echo 'eval echo $deplibs_check_method')" or there is no "libtool" in the gtk source so the ./libtool call fails [10:20] yeah, that won't work until after libtool has run ? [10:21] it may be that the different versions generate the script at different times, of course [10:21] well, that doesn't work when relibtoolizing using libtool2 [10:21] but that works when using libtool1.5 [10:21] I'm trying to figure why now [10:21] AlexCONRAD: I'll add that driver ASAP [10:22] tseliot: FYI, when I install the restricted drivers, I don't have antialiasing in flash. But when I install the ATI drivers (from their web site), I do have antialiasing enabled, after a reboot, I have nothing to do. [10:23] enabled in *flash* [10:23] I'm still trying to figure out what's the difference bewteen the settings you set in "amdcccle" and the onces you set using aticonfig [10:24] and the ones* [10:24] pitti: all fine then - nothing to be sorry ;) (especially now that it turned out to be a none issue) [10:25] asac: btw, what about nspr and nss? AFAIR there was something still not 100% clear? [10:26] pitti: sorry, have to run to doctor ... will be back in 30 minutes or so. [10:26] tseliot: nevertheless, I still have "SGI" set as the "client glx vendor string" via glxinfo [10:26] seb128: this exact case is covered in the libtool doc [10:26] asac: no problem; good luck! [10:27] seb128: if you simply delete that line, everything works [10:27] $deplibs_check_method is available to any configure code after LT_INIT / AC_PROG_LIBTOOL [10:27] Keybuk: ok, thanks [10:28] that was working when using libtool 1.5 because something copied "libtool" in the build directory apparently [10:28] yes [10:28] which is not the case in the current version and expose the bug [10:29] libtool was generated at the point inside configure where AC_PROG_LIBTOOL happened [10:29] and all the variables were lost to configure [10:29] it's now generated by config.status [10:29] hey seb128! [10:29] which means the variables are all available, and can even be changed by other configure bits [10:29] hello NCommander, sorry I've been busy working on the new GNOME updates and didn't reply to your mail yet [10:30] seb128, it's fine. Anything I can do to help with those updates? [10:30] Keybuk: ok [10:30] NCommander: help is always welcome ;-) But the remaining updates are mostly non trivial ones [10:30] THat's fine [10:31] I've packaged a few non-trival apps before [10:31] About the only thing I haven't done in that respect is a kernel module [10:31] gcalctool should be trivial, and is needing an update to meet the SRU policy :) [10:31] NCommander: want to have a look at updating evince to 2.23? it'll require a main inclusion report for libspectre which is used now to display .ps in the new version [10:31] that might be a good target [10:31] pitti: huats did both stable and unstable one yesterday [10:31] ah [10:32] not yet uploaded then, it seems [10:32] pitti: bug #250766 [10:32] Launchpad bug 250766 in gcalctool "Please sponsor gcalctool 5.23.5 into intrepid" [Undecided,New] https://launchpad.net/bugs/250766 [10:32] cool [10:32] pitti: no, I've been too busy to do sponsoring yesterday, thanks for sponsoring the hardy update btw ;-) [10:32] de rien [10:33] new GNOME is quite a challenge this week [10:33] gnome-keyring has a new lib, seahorse has been splitted and the tarball drop all the addons for gedit, epiphany-browser etc which are in a new source [10:33] seb128, SUre, no problem [10:33] gnome-desktop changed soname (not updated yet due to CD build) [10:34] evolution-data-server has sonames changes too and they switch to on disk sqlite storage for mail indexes [10:34] the new gnome-session dbus code should land soon [10:34] epiphany-browser has a webkit backend only now [10:34] etc etc ;-) [10:35] NCommander: cool, let me know if you have any question on the update, or feel free to ask here or on the #ubuntu-desktop channel [10:37] pitti: where is the MIR guide again? There is a zillion MainInclusionReport* pages in the wiki and I never remember how to find the guide one in the list [10:37] seb128: https://wiki.ubuntu.com/UbuntuMainInclusionRequirements [10:38] thanks [10:38] seb128: https://wiki.ubuntu.com/MainInclusionProcess is the policy [10:38] NCommander: ^ to read if you didn't yet [10:38] since it links to both the Requirements and the template, it's a better page to bookmark, I think [10:38] right [10:39] seb128, yup, I saw that [10:39] pitti: on --one-file-system [10:39] you know that if you bind-mount from the same filesystem, that doesn't work, right? :) [10:40] Keybuk: I know, yes [10:40] * NCommander doesn't get the autoreconf patch ... [10:40] it's not perfect, but helps a lot already [10:41] NCommander: ? [10:41] In evience, the old version has an autoreconf patch, but it doesn't appear to be necessary [10:41] * liw wants "rm --keep-the-important-stuff", but settles for kvm running a bunch of virtual machines for experimentation [10:41] NCommander: oh, if you have interest in C++ the g*mm bindings also need to be updated and maybe somebody looking after the bugs [10:41] (evience is still building though the new version, so it may not have exploded (yet)) [10:42] NCommander: autoconf update is required due to the lpi changes, they add launchpad-integration to the configure.in [10:42] Oh [10:42] Thanks, I didn't catch a new file was added [10:42] NCommander: and the other autotools are required because the hildon patch change the Makefile.am [10:43] Why not just add it properly it, and then call the autotools scripts to rebuild on the fly? [10:43] I always found patching configure directly will make updates harder [10:43] NCommander: "add it properly"? that's what 01_launchpad.patch does [10:43] NCommander: we just run autoreconf in a patch rather than a build time [10:43] Ok, I can understand that [10:44] that's something which might be discussed and different people have different opinion [10:44] there is pro and con for both way [10:44] I perfer calling autoreconf to do it, but if you perfer I do it as a patch [10:44] you are my mentor thus I shall follow your lead :-) [10:44] well that's what we do for desktop packages [10:45] and at least the result is constant [10:45] which is not the case when you call whatever automake version is installed at build time [10:45] Makes sense [10:45] I'm running cdbs-edit-patch now [10:46] to update the patch just remove the previous version, it'll not apply cleanly anyway [10:47] cdbs-edit-patch 99_autoreconf [10:47] Yeah, I know [10:47] ;-) [10:47] * NCommander has working with autohell before [10:47] autoreconf -v -f && rm -rf autom4te.cache [10:47] ok, good [10:47] seb128: + -i [10:48] Keybuk: usually -f works for me but right [10:48] at least autoreconf works [10:49] It always ticks me off on packages which it breaks miserably on because of missing aclocal macros [10:49] seb128: without -i, it'll fail to update one half of libtool if ltmain.sh already exists in that directory [10:49] it's a bug imo, colin found it yesterday [10:50] * NCommander rm's the patch and redoes it with +i [10:50] AlexCONRAD: antialiasing can be set through amdcccle and - if I'm not wrong - is not stored in the xorg.conf (AMD uses its own configuration file). When you install the driver from either EnvyNG or Jockey amdcccle is not used. I don't know what happens when you use aticonfig. [10:50] Keybuk: ok [10:50] tseliot: I'm doing some tests right now... [10:51] ok, now its building [10:51] tseliot: OpenGL screensavers seem to be affected by the amdcccle (from the ati drivers) [10:52] Keybuk: btw if a program has C and C++ sources, should AC_PROG_CC and AC_PROG_CXX be used or is CXX enough? [10:52] Keybuk: that's for gnome-system-monitor [10:52] seb128, I've used both, but you could probably get away with AC_PROG_CXX [10:52] seb128: both [10:52] you need CC for the C sources, CXX for the C++ sources [10:52] ok, that's what I did yesterday but I was not sure, building using CXX only seems to be working too [10:53] you'd even need to use CC if g++ could compile C code, since it needs to be set in CC [10:53] oh, it might *work* [10:53] the check for a C compiler is pretty much required by everything [10:53] but it might stop working one day ;) [10:53] AlexCONRAD: just FYI AMD's configuration file is /etc/ati/amdpcsb [10:53] tseliot: I see that things are stored in /etc/ati/amdpcsb [10:53] tseliot: :) [10:54] Keybuk: alright, thanks ;-) [10:54] seb128, ok, its building now [10:54] seb128, (this machine for some reason takes forever to run autotools, but builds very quickly) [10:54] tseliot: Im having a hardtime to figure out which or amdcccle or aticonfig (xorg.conf) takes over [10:55] NCommander: ok [10:55] mvo: hello :-) [10:56] tseliot: also, what does "sudo dpkg-reconfigure -phigh xserver-xorg" does really ? [10:56] mvo: I'd likte to patch a command-not-found bug, could you tell me where are the current ubuntu sources for that package? (as in bzr tree, not apt-source sources) [10:57] mvo: I think I finally understand the cause of all the locale issues that pop up since c-n-f was introduced and I know how to fix that [10:57] AlexCONRAD: don't do it unless you really need it. It reconfigure your xorg.conf without asking questions. [10:59] NCommander: some other desktop updates if you are looking for other things to do after this one: gucharmap (the new version adds python binding and might have changed the soname), glibmm and gtkmm if you have interest in C++ bindings [10:59] seb128, I assume you want me to add the libspectre support to this package instead of just having it use the existing gs code [10:59] NCommander: what tarball did you get? [10:59] 2.23.5 [10:59] WHich was the latest on the ftp.gnome.org site [10:59] NCommander: the upstream NEWS mentionned that they dropped the gs support [10:59] but yes, we want to use libspectre now [10:59] The README says optional [11:00] tseliot: well, things are pretty clear now: aticonfig --fsaa=on/off and all antialiasing options are no longer available in the latest ATI drivers [11:00] ATM, its FTBFS because it can't find the launchpad support library [11:00] undefined reference to `launchpad_integration_add_ui' [11:00] tseliot: sounds like you can only do it through amdcccle [11:00] NCommander: did you apply 01_launchpad before doing the autoreconf? [11:00] I thought I did [11:01] NCommander: 01_launchpad should add launchpad-integration to the configure.in and the autoreconf should apply that to the configure [11:01] NCommander: maybe look if the configure lists it correctly? [11:01] zyga: hello! nice to see you :) the current bzr tree is at http://bazaar.launchpad.net/~ubuntu-core-dev/command-not-found/ubuntu [11:01] I don't see it in configure ... [11:01] Argh, if I had to bet, cdbs-edit-patch unapplied it when I ran edit-patch [11:02] it should apply in order [11:02] ie, cdbs-edit-patch 99_autoreconf apply 01_launchpad normally [11:02] I'm checking now to see what went wrong [11:02] No, it did end up in the right place [11:03] mvo: thanks, I'll work on a fix and give you a branch back when I'm finished! [11:05] NCommander: maybe they restructured the code and the launchpad-integration pkg-config check should be moved somewhere else in the configure.in [11:05] I'm checking now [11:05] This is personally why I don't like autoreconf in patches [11:05] I find its easier just to patch configure.ac, and then let autoreconf run at build time [11:06] well, autoreconf at build time would not have produced a better result [11:06] but right, you wouldn't have to update the patch again and again ;-) [11:06] well, you just have to run autoconf in this case [11:06] yeah [11:06] which is quick enough usually [11:07] Neat, libtool is now tossing a nice warning about AC_CONFIG_MARCO_DIR which it didn't before [11:07] zyga: excellent, thanks a lot [11:08] NCommander: right, I noticed that too, not sure if really makes a difference to use that though [11:08] seb128, I usually ignore autotool warnings cause then tend to be a tad paranoid [11:08] I was pondering sending upstream patches for that on the packages I updated yesterday [11:08] Most upstreams don't touch the configure script once its done [11:09] We still have quite a few packages that build with 1.4 version of said tools [11:10] * NCommander also works now on clearing the lintian warnings [11:11] seb128, since your an archive admin, can you help me resolve an issue with my package which got rejected? [11:14] re [11:14] hum, got disconnected [11:14] yeah, most upstream tend to copy configure from an another project, do some changes to get it working and don't touch it when that's not really required [11:15] seb128_, yeah, well as an added bonus, this doesn't properly list a build-dep on ghostscript, it just FTBFS looking for -lgs ... [11:15] I'm suprised it built on the buildds [11:17] well, gs is optional no? it probably built not using this option [11:18] /usr/bin/ld: cannot find -lgs [11:18] It seems it isn't [11:20] It needs ghostscript if you want postscript viewing enabled [11:22] seb128,_ anyway, I was hoping you could resolve a license ambiginity with regards to the copyright file, which lead to codeblocks being rejected [11:22] NCommander: there is no lgs mention in the evince source and the 2.22 configure is using the gs command to check if gs is available [11:23] I have the command available, but I didn't have the development library headers installed [11:23] ok [11:23] I just added the dependency on libgs-dev; its already a core package [11:23] NCommander: I've read the codeblocks rejection [11:24] ok, cool [11:24] I also think having postscript rendering isa good thing [11:24] THe archive admin says the package is LGPL [11:24] But that's only true for the SDK [11:24] Riddell: ^ [11:24] NCommander: Riddell is the archive admin who rejected the upload [11:24] YEah [11:25] I emailed him asking how I should clarify copyright [11:25] I assume I need to add LGPL for the files under that specifically [11:25] (in the copyright) [11:25] right, if you have sources under the LGPL the LGPL licence text should be distributed in the tarball and the debian/copyright should list those [11:26] the COPYING file only has the GPL3 [11:26] right, you need to add A COPYING.LGPL for example then [11:26] or COPYING.LIB [11:26] which has the LGPL text [11:26] Can I simply add it as a patch, or do I actually need to repack the upstream? [11:26] I know some archive admin want it in the upstream tarball [11:27] otherwise the tarball is not re-distribuable [11:27] I was under the impression if something was shipping as GPL3, the collective work was GPL3, expect for the files that are LGPL, which can be used under the LGPL by themselves if they are removed from the package [11:27] * NCommander recalls his time as a FSF Savannah admin === seb128_ is now known as seb128 [11:28] not sure about that [11:28] cjwatson or pitti might know better [11:28] Yeah [11:28] but if you have LGPL sources you should have the LGPL text in the tarball [11:28] The LGPL says that it can be replaced with the GPL [11:28] So by having the later, you can meet the requires of the former [11:28] it is, but it's a separate issue. if the code is under a licence, the licence text should be included so we know the full terms of the licence [11:29] Does that alone warrent repacking the source to add a COPYING.LGPL file, or should it simply be added via a patch (and in the copyright file of course) [11:30] NCommander: addding license documents via a patch is always wrong IMHO [11:30] it's upstream who would need to add the file since they're the ones licencing it [11:30] either you don't need it at all(because of some GPL implies LGPL situation), or it needs to be in the orig.tar.gz [11:30] I'll ask upstream to add the file (I already had to file a bug with them over a rendering bug in wxWidgets) [11:31] I assume if I want it to go them, I need to repack the source, right? [11:33] NCommander: yes [11:33] ok [11:33] That makes sense [11:33] NCommander: or get upstream to fix the issue and roll a new version ;-) [11:34] NCommander: I expect my e-mails to you are in your spam box, gmail doesn't like my server sometimes [11:34] code::blocks already stinks when it comes stable releases [11:34] seb128, http://paste.ubuntu.com/29569/ - evidence seems to hate me :-P [11:34] * NCommander looks up the extension he needs to add to the mime file [11:35] I'm not convinced that's authorized [11:35] hmm if i make a new package with some changes (libqt4-sql-psql) since the default one does not support postgres 8.3 that ships with ubuntu, how can i make it not want to download a "updated" package from the standard repo? [11:35] I found the fix on their bugzilla [11:35] * NCommander adds the patch [11:36] do i need to bump the version somehow? [11:36] NCommander: good, don't forget to add those to debian/evince.mime too [11:37] no, its a typo in the desktop file thats causing that [11:38] NCommander: application/x-cb7 seems to be new and should be added to debian/evince.mime no? [11:38] I'm checking [11:38] yeah [11:38] Its new [11:38] But I can't figure out what extension is x-cb-7 [11:39] According to the source, its some sorta comic book format [11:40] NCommander: http://bugzilla.gnome.org/show_bug.cgi?id=532312 indicates cb7 [11:40] Gnome bug 532312 in general "Comic Book compresses with 7zip (aka .cb7)" [Enhancement,Resolved: fixed] [11:40] thanks :-) [11:42] ok, new mime type in place, autoreconf patch updated again, now to see if it will build [11:48] seb128, internet trouble? [11:48] NCommander: no, restarting session to try updates sometimes [11:49] I should configure an IRC proxy or something [11:53] * NCommander edits the changelog [11:56] ok, it's lunch time, see you in a bit [11:56] I should be more or less done by then seb128 ;-) [11:56] NCommander: I'm away for lunch, I'll read the backlog when I'm back [11:56] ok, cool [11:56] it must be late for you, there is no hurry for the update, feel free to continue tomorrow [12:00] late or early [12:00] anyway lunch time, bbl [12:14] seb128, its all built, but it has a bunch of lintian warnings like debian-copyright-line-too-long, but no errors [12:26] seb128, uploaded to PPA sonicmctails on LP [12:30] mvo: is there any sane way to make bug repots from python that will identify ubuntu version? [12:31] mvo: (so that the "report this bug" URL will point to correct ubuntu release, not the generic package [12:31] mvo: I was thinking about optionally reading /etc/issue [12:31] zyga: lsb_release? [12:31] or using lsb [12:31] right [12:32] /etc/issue is commonly customised by users so you can't rely on it. [12:32] lsb_release looks as a sane way to do that [12:32] now just for a simple way to tie that to launchpad [12:33] thanks I think calling subprocess.call("lsb-release", "-a") is enough for bug maintainer to re-assign the bug as needed [12:36] I was under the impression (and correct me if I'm wrong) that the current Ubuntu bug workflow was to assign bugs to the 'generic' package and not to the release specific version. Unless of course you're talking about reworking that workflow. [12:36] I wasn't aware of that [12:36] I was just looking for a way to get default bug reports more meaningful than before [12:36] see https://bugs.edge.launchpad.net/ubuntu/+source/pidgin vs https://bugs.edge.launchpad.net/ubuntu/hardy/+source/pidgin [12:53] that was exciting...I just installed the latest intrepid daily desktop [12:54] mdz: and it actually worked? [12:54] pitti: almost [12:55] lots of problems [13:03] mdz: out of interest: did you get read errors from the cd? (I got that with testing the last two daily images from faumachine... just curious if that's a faumachine bug or a bug in the live cd) [13:05] sistpoty|work: no [13:05] ok, thanks === RainCT is now known as RainCT_ [13:28] mvo should I add something to debian/control when I want to use lsb_release? [13:28] (like lsb-release package) [13:29] zyga: yes, a depends on the lsb-release package [13:29] ok, done [13:32] lamont: do you have any clue about this FTBFS on hppa? http://launchpadlibrarian.net/16253078/buildlog_ubuntu-intrepid-hppa.gnustep-base_1.16.1-2ubuntu1_FAILEDTOBUILD.txt.gz [13:33] "iz feature" :-< [13:33] gah! [13:34] I wouldn't worry too much about it [13:34] once hppa catches back up (is it??) I expect that infinity will throw everything that failed back against the wall to see what sticks [13:35] that looks like one of the standard "that threads bug" (it isn't actually, but it is...) failure modes [13:35] mvo: http://suxx.pl/~zyga/command-not-found--locale-issues-fix/ [13:35] ok, I'll leave it alone for now, thanks [13:36] mvo: I didn't test it with python 2.4 though [13:36] zyga: thanks, I will merge and review now [13:36] mvo: I did one more change that is not in the changelog [13:37] I replaced /usr/bin/env python with /usr/bin/python -S [13:37] -S omits import site that often got to crash reports [13:37] hmm, doesn't work with 2.4 [13:38] if that's a problem I can work around it but I think it needed 2.5 before (try/except/finally) [13:38] NCommander: ok cool, I'll have a look in a bit and comment here or by mail [13:38] seb128, cool [14:26] geez, intrepid daily doesnt even survive unpacking the kernel in my vbox [14:27] ogra: Is it perhaps running compcache? [14:27] ion_, nah, just the alternate CD, no fancy stuff [14:28] th eodd part is that the oops scrolls indeed out of sight [14:28] we should really do something that it doesnt get bigger thn a standard terminal at some point ... or put the intresting stuff at the bottom [14:28] BenC, ^^^ [14:29] ogra, perhaps can you set up a "serial" console easily on a VM, and then capture using minicom or similar? [14:30] hmm, thats way more work than i planned to get an intrepid VM quickly :) [14:31] ogra: what are you using? kvm? or s.th. else? [14:32] virtualbox on hardy [14:32] and the current daily alternate [14:32] * sistpoty|work tries hardy kvm atm with the current daily desktop *g* [14:32] uuuh, desktop is like gambling i bet :) [14:32] pitti, hi === tkamppeter_ is now known as tkamppeter [14:33] i just need a working env. for ltsp stuff (going to the ltsp hackfest today) [14:33] tkamppeter: could you please update system-config-printer to a recent snapshot? I need it for the jockey printer bits [14:33] pitti, OK [14:33] sistpoty|work, i had just read some bugmail that indicated the current daily desktop has a few bugs in ubiquity [14:33] it seems you need to run some autoconf stuff in order to produce an orig.tar.gz from git? [14:33] tkamppeter: ^ [14:33] tkamppeter: ok, thank you! [14:33] (The Intrepid version is hopelessly outdated ...) [14:34] but if you make it to the desktop, you are in better shape than virtualbox right now [14:34] sistpoty|work, as in bugs preventing install due to errors [14:34] but it would be really helpful (not right now but in general) to have oppses printed out in reverse order ... usually only the first lines re the intresting ones and they always scroll off the visible area [14:34] superm1: I kind of made it to the desktop :) [14:35] pitti, yes. You must do (in the main directory): [14:35] ./bootstrap [14:35] rm -rf autom4te.cache [14:36] Then you must create a tarball with --exclude=.git [14:36] hmm, not even the CD selftest will run ... [14:36] must be a serious kernel issue (or isolinux) === azeem_ is now known as azeem [14:36] ogra, well i dont know that i entirely agree. perhaps having a kernel parameter to "allow" then to be printed in reverse order would be better [14:37] especially in the case of entirely reproducible oopsses [14:37] superm1, that would be fine too, but its a thing that bothered me often already [14:38] if your keyboard doesnt work after the crash there is simply no easy way to reach the wanted info [14:39] and things like vprintk or show_fault_oops dont really tell me something ... [14:40] geez ... dropping quiet from teh bootopts gets me funny colored squares on the screen [14:43] ogra: there's ways to scroll back to the oops [14:44] not in my vm it seems [14:44] what was the command to disable tickless ? noticks=on ? [14:45] i saw somethng about ticks in the last round [14:45] dynticks=off [14:45] thanks [14:45] oops [14:45] ogra: no, it's nohz or nohz=1 [14:45] heh, ok [14:45] NCommander: ok, I'm looking at your evince update, first note: you did use the upstream tarball and a diff.gz, that's wrong ;-) you need to rename the tarball evince_2.23.5.orig.tar.gz so it's used and the debian changes are stored in a diff.gz [14:46] NCommander: the ppa upload didn't build on lpia, seems that the hildon patch needs some changes [14:46] argh [14:46] The former was just stupid error [14:46] (I went away after uploading to my ppa, I didn't even check to see if I made a native version of not) [14:46] As for the second, look closer at the lpia log [14:46] but dynticks=off seems to change something as well ... now it hangs without any oops [14:46] Its one of the dependencies failing to configure [14:47] NCommander: looking [14:47] seb128, it fails before it even tried to build [14:48] NCommander: otherwise you added .debhelper.log files in the debian directory, those should probably not be in the source [14:48] NCommander: hum, no [14:48] ah, nohz gets me the same result ... hangs at ACPI: XSDT .... [14:49] er, your right [14:49] NCommander: the log I'm reading has lot of undefined reference to gtk function which indicates a -lgtk-x11-2.0 is missing somewhere [14:49] WTF was I on ... [14:49] Yeah [14:49] I see that [14:49] I've got an lpia chroot [14:49] I'll see if I can run that down [14:50] you should be able to use --enable-hildon on i386 too [14:50] I did have an orig tarball, I just had an - instead of a _ [14:50] * ogra grins ... nohz=1 and acpi=off gets me "BUG: Unable to handle kernel <1>" [14:50] just change the rules [14:50]