/srv/irclogs.ubuntu.com/2008/01/21/#ubuntu-devel.txt

=== doko__ is now known as doko
=== \sh is now known as \sh_away
linos2has anyone see an error like this X Error: BadDevice, invalid or uninitialized input device 16803:03
Hobbseelinos2: please see the /topic03:06
Hobbsee(and if you put that error into google, you'll find the answer, too)03:06
linos2Hobbsee, sorry about that..... thank you03:07
=== bigon` is now known as bigon
=== bigon is now known as bigon`
=== fabbione is now known as thegodfather
=== greeneggsnospam is now known as jsgotangco
monzieHi all06:15
monzieWhat happenned to the libapache-mod-ssl package?06:15
monzieIt was there in 7.04 but is not in 7.1006:15
monzieIf it has been taken out for a reason, can someone please tell me how to install mod-ssl on 7.1006:16
monzie!ubotu apache06:16
ubotuLAMP is an acronym for Linux-Apache-MySQL-PHP. However, the term is often used for setups using alternative but different software, such as Perl or Python instead of PHP, and Postgres instead of MySQL. For help with setting up LAMP on Ubuntu, see  https://help.ubuntu.com/community/ApacheMySQLPHP - See also the Server CD installation process (different in Edgy+)06:16
StevenKmonzie: Use Apache 2, it includes SSL.06:17
Mithrandirmonzie: apache 1 is dead and has been for a while; you should have migrated to Apache 2 by now.06:17
ScottKmonzie: #ubuntu-server is a better place for that kind of question, but StevenK is, as usual, right.06:17
Mithrandirmorning, StevenK06:17
StevenKmorning Mithrandir06:17
monzieStevenK:  i have Apache206:18
StevenKmonzie: Then you don't need libapache-mod-ssl, that's for Apache 106:18
Mithrandirall libapache-* modules are for apache 106:18
StevenKThat too.06:19
monzieok06:19
monzieStevenK, Mithrandir: http://pastebin.ca/867200 ( that's the output of apache2 -l on my sytem)06:19
monzieI cant see SSL there06:19
StevenKThen the module isn't enabled.06:20
StevenKmonzie: Run 'a2enmod ssl'06:20
Mithrandir: tfheen@xoog ~ > ldd =apache2 | grep ssl06:20
Mithrandir        libssl.so.0.9.8 => /usr/lib/libssl.so.0.9.8 (0x00007fb5ae419000)06:20
monzieStevenK: thanks!06:21
StevenKmonzie: No problem.06:21
monzieStevenK: I am sure there was a a reason for not having a "libapache2-mod-ssl" I guess06:21
StevenKYes, because it's included in the Apache 2 package.06:22
monzieok06:22
monzieThanks room!06:22
=== jamesh_ is now known as jamesh
=== bigon` is now known as bigon
warp10Good morning07:00
* Mithrandir idly wonders when ooo-l10n is going to be fixed.07:12
=== carlos_ is now known as carlos
=== stu1 is now known as stub
carlospitti: good morning08:49
pittihey carlos, good morning08:55
carlospitti: I wonder whether you managed to get .deb packages for Hardy language packs08:56
carlosor did you delegate it already ?08:56
thegodfathermorning pitti08:56
pitticarlos: I just got jtv's /msg that they are ready08:58
pitticarlos: I think I'll sit down with Arne today and show him how to build them08:58
carlosok, I thought you had your script executed automatically ;-)08:59
carlospitti: I will need to ask you to remove all lang_country directories again as we did with latest Gutsy lang pack....09:00
pitticarlos: oh, thanks for the warning09:00
carlospitti: btw, full Hardy export took only 15 hours 20 minutes09:03
carlospitti: so we don't need to wait 2-3 days to get one09:03
carlosanymore09:03
pitti\o/09:04
carlospitti: that's using production, no need to use a mirror so we get latest information available in Launchpad09:04
carlospitti: btw, we are going to announce Hardy translations opening today and I wonder whether we could announce also that starting later today or tomorrow we would have language packs updated twice per week09:06
pitticarlos: yes, please do announce it; I'll either sit down with Arne today or do it myself09:07
pitticarlos: but it'll be a few hours/a day, since they take quite some time to build09:08
carlosok, thank you09:08
carlosso we will say in next days09:08
carlos"in next days"09:08
carlospitti: thanks for handling this09:08
Robot101"in the next few days" would be more idiomatic :)09:09
carlosRobot101: thanks ;-)09:09
gesergood morning09:15
geserpitti: Hi, as you merged debhelper in the past have you time to review bug #184545?09:15
ubotuLaunchpad bug 184545 in debhelper "[Merge] debhelper (6.0.2ubuntu1)" [Undecided,New] https://launchpad.net/bugs/18454509:15
pittigeser: I am fine to do it, I just don't know when I'll be able to; can you please subscribe me, so that I'll get a bug mail?09:16
geserpitti: done and thanks09:17
geserpitti: please give-back: haskell-cgi haskell-glut haskell-openal hslogger. Thanks09:37
pittigeser: done09:38
dholbachthekorn, bdmurray: could it be that pylpbugs broke?09:49
dholbachthekorn, bdmurray: http://paste.ubuntu.com/3743/09:50
=== _emgent is now known as emgent
thekorndholbach, hi, will have a look at this during my lunch-break09:58
dholbachthekorn: you ROCK10:04
LucidFoxIs https://wiki.ubuntu.com/No-Mono-by-Default relevant anymore?10:49
ograLucidFox, look at the LP spec page, it should tell you the status10:50
mjg59LucidFox: What do you mean by relevant?10:50
mjg59It's not an approved spec10:50
ogra(if it was even approved to be implemented etc)10:51
mjg59So it's as relevant as it was when it was written (arguably not very)10:51
LucidFoxit says review10:51
LucidFoxThe issue is, someone is asserting that Mono will be removed from the default installation, and points me to that page10:52
ograthats nonsense10:52
LucidFoxI want to repel his argument10:52
ograwe just moved f-spot to be the default photo app10:52
ograwould be silly to drop mono *now* :)10:52
ogramjg59, do you plan to drop by this week in th eoffice ?10:53
mjg59ogra: With luck, on Wednesday10:54
ogracool !10:55
keescookmjg59: saaay... is there a way to access the CPU thermal sensors on the core 2 duo/quad cpus?  (I don't seem to have an ACPI output for it on my desktop)10:55
mjg59keescook: Hm. I think someone wrote a driver to do that.10:56
keescookmjg59: ah, have an pointers to it?  I've been having a bad time googling for such things.  :P10:56
mjg59Yeah, having some trouble finding it10:57
mjg59keescook: http://www.lm-sensors.org/wiki/Devices suggests lm-sensors has one (coretemp)10:58
keescookah!  I thought lm sensors was deprecated in favor of the acpi goo10:59
mjg59If acpi doesn't provide it, deprecation isn't helpful :)10:59
keescookwell, heh, yeah.  :)10:59
mjg59We seem to ship a version of coretemp10:59
mjg59But it doesn't /seem/ to bind for me11:00
mjg59Oh, no, wait11:00
mjg59It just doesn't print anything to dmsg - I've got stuff in /sys/devices/platform11:00
keescookah-ha!11:01
keescookone for each cpu.  :)  hmmm... which actually has the current value...11:01
mjg59temp1_input11:02
Companyit works on my macbook11:05
Companywith lmsensors11:05
keescookmjg59: cool, thanks.  "sensors" reports them all happily. whee11:05
stgrabermoin11:11
monzieHi all11:17
monziehow do i generated Apache certificates in Ubuntu 7.10?11:17
monzieapparently the "apache2-ssl-certificate" packages has been taken out11:18
monzieI am following https://help.ubuntu.com/community/forum/server/apache2/SSL11:18
=== cprov-afk is now known as cprov
thekorn_dholbach: this error is weird, I can't reproduce it,11:55
thekorn_which version of py-lp-bugs are you using, do you have local (uncommited) changes in sponsoring or py-lp-bugs?11:56
dholbachthekorn_:  no, none :-/12:01
=== Igorots is now known as Knightlust
ganeshi installed ubiquity & created a live cd but it is not installing from that cd , help me to resolve my problem12:57
ganeshln-, yeah it a development question12:57
* sistpoty|work is away: coffee break13:02
calcany ubuntustudio people here? i forgot who was nagging me about OOo before13:08
calci have a question for them when/if they show up13:09
zulpitti: can we get xen-3.2 out of new?13:12
pittizul: yes, it's just a matter of finding some time to attack NEW13:13
_MMA_calc: I'm in whatever channel you wanna talk in. :P13:13
zulpitti: great, no problem13:14
TheMusocalc: yes, I am around.13:18
=== superm1_ is now known as superm1
tbfwhat's the rationale behind installing .la files?13:33
tbfthey only cause trouble?13:33
tbfs/trouble?/trouble!/13:34
Chipzztbf: I wouldn't say everyone here is positive about installing .la files (ie some/a lot of people here share your opinion)13:38
tbfChipzz: well, that's why i ask for the rationale13:39
seb128you need those to do static building13:40
slangaseknot if you have .pc files13:40
seb128right13:40
slangasektbf: the sole rationale for installing .la files is that they facilitate static linking using metadata that's available in the same directory as the lib itself, without having to centrally register the information (i.e., with pkg-config)13:41
slangasektbf: IMHO this doesn't outweigh the various disadvantages of installing them; so for the most part I would say there's no "rationale" for installing them in Ubuntu, they're just installed because this is what libtool does by default13:41
Chipzztbf: oe of the problems with .la files is that if you wanted to get rid of them, you would have to do so top-down13:42
tbfseb128: the only guys how need static linking a propritary software vendors....13:42
Chipzz*one13:42
tbfseb128: and most of the time even they cannot make use of it, since the libs they want to link are LGPL13:42
Mithrandirtbf: no, that is wrong.13:42
Mithrandirlike, sash is a perfectly good example of a tool that needs to be statically linked.13:43
tbfMithrandir: ok, one additional case exists: boot imagges13:43
Mithrandirwhy would boot images need to be statically linked?13:43
tbfMithrandir: but for the entire gnome stack for instance it is pointless to link statically13:43
tbfMithrandir: 'cause you can strip unneeded symbols13:43
tbfMithrandir: without dynamic linking you need the entire libc, with static linking you just need space for the code you really use13:44
Mithrandirtbf: I know how static linking works.  I was contradicting your claim that static linking is only useful for proprietary software authors.13:44
tbfhmm... maybe want some libtool switch "no, no f***ing .la file, please"13:47
seb128tbf: stop using libtool if you don't need it?13:47
tbfseb128: were is the camera?13:47
seb128?13:48
tbfseb128: well, from your words i guess this is a hidden camera show13:50
seb128tbf: that's what Keybuk suggested previous time there was a similar discussion on this chan, if you don't want la files you don't need to use libtool there is easier way to get a library built13:51
tbfseb128: libtool does some useful stuff, and the only result of not using it, are many bug reports for your gnome packages13:51
tbf"migrate to libtool please"13:51
tbfseb128: well, but for gnome packages, libtool's la files don't make any sense, as gnome files have that information in their .pc files13:52
tbfs/gnome files/gnome libraries/13:52
seb128tbf: so why not stop building those?13:52
tbfseb128: the pc files?13:53
seb128no the la13:53
tbfseb128: well, stopping to build .la files is exactly what i want13:53
ganeshi installed ubiquity & created a live cd but it is not installing from that cd , help me to resolve my problem13:53
tbfseb128: i want to tell libtool "do not build .la files for this library"13:54
seb128tbf: you might get the "stop using libtool if you don't need it" reply13:54
tbfseb128: libtool knows how to build shared libraries on solaris and with mingw32 for instance...13:55
tbfseb128: also automake works much better with libtool, than without13:55
seb128I don't know enough about libtool to discuss that13:56
Keybuktbf: don't use libtool13:57
Keybukfor gnome packages, pkg-config provides all the answers13:57
Keybuklibtool is unnecessary13:57
tbfKeybuk: the opensolaris guys will disagree, for instance14:00
Keybuktbf: but you just said you don't care about portability14:00
* sistpoty|work is back14:00
tbfKeybuk: how that?14:00
Keybukyou *need* .la files on solaris14:00
Keybukif you delete them, you're declaring that you only care about Linux14:01
tbfnice14:01
Keybuksince you're using knowledge about the Linux dynamic link loader14:01
tbfKeybuk: so how can i rid of them on linux, please?14:01
Keybuktbf: don't use libtool14:01
tbfKeybuk: why do you try to be an idiot?14:01
Keybuktbf: ?  I'm not being an idiot14:02
tbfKeybuk: i never said you are one.14:02
Keybuk<tbf> Keybuk: why do you try to be an idiot?14:02
SpadsKeybuk: why do you *fail* at being an idiot?14:02
tbfKeybuk: trying is different from being14:02
Keybuktbf: http://www.ubuntu.com/community/conduct14:03
Keybuktbf: please read that, carefully14:03
tbfKeybuk: guess you also should read it14:03
ganeshi installed ubiquity & created a live cd but it is not installing from that cd , help me to resolve my problem14:04
Mithrandirtbf: it would help if you stopped coming across as so agressive.14:04
tbfKeybuk: repeating "don't use libtool" really doesn't help, if the person you talk to repeatedly say, that he needs most features of libtool14:04
Mithrandirganesh: you're off-topic for this channel; please take it elsewhere (#ubuntu-installer, possibly)14:04
Keybuktbf: libtool has one feature14:05
Keybukit provides a common interface to shared library generation across all platforms14:05
Keybukyou've said you do not want that feature14:05
Keybukergo you do not want to use libtool14:05
Keybuklibtool does *nothing* else14:05
Keybukif you remove .la files, you are deliberately breaking libtool and attempting to circumvent it14:05
Keybukat which point, why use it at all?14:05
ganeshMithrandir, ok14:05
MithrandirKeybuk: hmm?  Doesn't it track dependencies between static .a libraries and help you link them into a static object?14:06
tbfKeybuk: group pressure?14:06
KeybukMithrandir: only if you use .la files14:06
Keybukas soon as you delete .la files, you can no longer do that14:06
ChipzzKeybuk: your argument is flawed; you do want the common interface, but you do not actually need the .la files for obtaining that goal *on linux*, just on *other platforms*14:06
Keybukat which point, why use libtool at all14:06
Chipzzbut since ubuntu is linux you don't need the .la files14:06
KeybukChipzz: but as Mithrandir points out, you actually *do* need them for that goal14:06
Keybukotherwise you can't do static library linking14:07
ChipzzKeybuk: afaik not on linux; only on other platforms lacking certain features14:07
Mithrandirand then it comes down to whether we actually want to support people linking, say, gtk+ statically.14:07
KeybukChipzz: yes, you do14:07
tbfKeybuk: but why should i care about artifacts for building __static__ libraries, if i want a tool for building __shared__ libraries?14:07
Keybuktbf: gcc is perfectly capable of building shared libraries14:07
tbfKeybuk: and why should i care about dependency tracking information, if i have a more reliable variant?14:07
Mithrandirtbf: libtool know what magic knobs you need to twiddle on different platforms for building shared libraries too.14:07
Keybuktbf: so why use libtool if you have a more reliable variant?14:08
tbfKeybuk: well, and libtool doesn't only do dependency tracking. it also knows which commands to invoke with which arguments14:08
Keybuktbf: so do you, since you know how the the linker works14:08
Keybukand libtool's knowledge depends on it having its control files14:08
Keybukas soon as you take away its control files, libtool's own commands it invokes don't function properly14:09
tbfKeybuk: well, and it takes care about injecting --rpath information, so you can use your shared libs from your source dir...14:09
Keybukit just happens that they function "well enough"14:09
Keybuktbf: that breaks if you remove .la files14:09
tbfKeybuk: so libtool does alot of useful stuff14:09
Keybuktbf: and it cannot do *any* of that, if you remove the .la files14:09
Keybukergo : remove the .la files => why are you using libtool?14:09
MithrandirI'm wondering if we could rip out the dependency tracking bits of libtool and have it use pkg-config for that, while retaining its knowledge on compiler flags to build shared libs.14:10
tbfwell, then we are at the point that libtool most probably is seriously broken....14:10
Keybukas soon as you remove .la files, libtool becomes nothing more than a very large, very complicated shell script that expands to a gcc invocation near-identical to the libtool invocation14:10
Keybuk(on Linux)14:10
tbf....since it regularly uses the wrong .la files14:10
Keybuktbf: it never uses the wrong .la files ;)  what happens is that libtool's generic interface requires you, when you rebuild a library, to rebuild all libraries and programs that depend on it14:11
Keybukit happens that Linux's library implementation doesn't require this14:11
Keybukbut since many library implementations *do* require this, libtool requires it14:11
tbfKeybuk: i do that, i do that14:11
tbfKeybuk: nevertheless it regularly grabs .la files from /usr/lib, instead of whatever-dir i asked it to use14:12
Keybuktbf: next time it does it, please feel free to tar up the image, and grab me on IRC -- I'll happily help debug it for you14:12
ChipzzKeybuk: but, often it's nogt a matter of you wanting or not wanting libtool, it's a matter of *upstream* wanting libtool; so you have no say in it14:12
KeybukChipzz: but we already change upstream by removing .la files14:13
Keybukupstream probably use libtool because automake depends on it for libraries14:13
ChipzzKeybuk: yes, but that's related to what Mithrandir said:14:13
Chipzz15:07 < Mithrandir> tbf: libtool know what magic knobs you need to twiddle on different platforms for building shared libraries too.14:13
Keybukbut we don't need those knobs14:13
ChipzzKeybuk: often, libtool is used for *that* purpose, and the things you say are actuall irrelevant14:14
Keybukit's a trivial matter to replace the ltmain.sh in source packages with something that only has the magic knobs for ubuntu14:14
Keybuk(we replace it most of the time anyway, along with config.guess and config.sub -- we just replace it with the full libtool one)14:14
ChipzzKeybuk: upstream does, for portability to other platforms we don't care about14:14
Keybukthen we could cut libtool out entirely14:14
Keybukautomake would still work, things would get built relying on pkg-config, etc.14:14
MithrandirI'm somewhat wondering what problem you're trying to solve then.14:15
Mithrandirapart from "libtool is a pile of spaghetti and I want tuna for lunch!"14:15
Keybukthere's tuna in libtool14:16
ChipzzKeybuk: the matter of fact is very simple IMO; libtool is often used because of the relative convenience (of not having to figure out 10 gcc switches) of the automake/libtool combo, and for portability; and most often not for the things you mention14:16
Hobbseemmm...tuna14:16
MithrandirKeybuk: there are also bits of metal and brains in libtool.14:16
KeybukChipzz: except those switches rely on the existance of a file that packagers subsequently delete14:16
Keybuklibtool *really* assumes it has a .la file14:16
Keybukand its behaviour without one is quite undefined in many circumstances14:17
MithrandirKeybuk: all of them at varying degrees of radioactivity, of course.14:17
Chipzzbut it still works without?14:17
Keybukno, it really breaks14:17
Keybukit just happens to work on the buildds without14:17
Keybukfor example, when you don't ship a .la file in /usr/lib, a .la file *anywhere else in the path* will trump it14:17
Keybukand you'll end up linking with the wrong libraries14:17
Keybukso builds work on the buildd, since they're fresh14:17
tbfso how do i get back the .la files, after agressively erasing them from /usr/lib?14:17
Chipzzunless I'm grossly mistaken, I have build numerous libs in the past even with the .la files it depended on gone14:17
Keybukbut fail on people's machines14:17
slangasekKeybuk: er, but /usr/lib is normally the last dir in the lib search path anyway?14:18
Mithrandirtbf: reinstall the packages providing them.14:18
slangasekso if you have .la files elsewhere in the path, that's breaking things anyway14:18
ChipzzKeybuk: um yeah, but users shouldn't really be building from source anyway14:18
tbfMithrandir: any magic for doing this automatically?14:18
Keybukslangasek: not at all14:19
aquoi had a look at /var/log/dpkg.log and many lines are printed multiple times? is this a bug?14:19
Keybukthanks to multi-arch weirdness, it's somewhere in the middle (it just happens to be specifically at the end too)14:19
KeybukI've demonstrated the failures many times14:20
Keybukand I've argued repeatedly about this14:20
Keybukand people still ignore me, and still come to me with their problems afterwards14:20
Keybukso meh14:20
Mithrandirtbf: cd /var/lib/dpkg/info; grep -lr la$ *.list | sed s/.list$//| xargs sudo apt-get --reinstall install14:20
Mithrandirtbf: untested, of course.14:20
tbfMithrandir: looks reasonable - thank's alot14:21
slangasekKeybuk: not me, I just concatenate invectives and will libtool to implode14:21
Mithrandirpossibly make that grep pattern \\.la$14:21
KeybukI long ago came to the conclusion that libtool is the wrong solution14:22
tbfMithrandir: already did that ;-)14:22
Keybukand lost the will to care about writing the right solution ;)14:22
slangasekKeybuk: speaking of which, what would you recommend for a pair of libtool "module" .las where one requires symbols from the other, using the current sensible-libltdl behavior of RTLD_LOCAL?14:23
slangasekKeybuk: ... and the module .la doesn't have a name beginning with "lib"? :)14:23
Keybukcan't A needed B?14:23
slangasek(this apparently causes libtool to go stark raving at install time, and try to convert the .la file's path into a -l option)14:24
Keybukfoo_la_LDADD = bar.la14:24
Keybukprog_LIBS = foo.la14:24
Keybukdoesn't that work?14:24
slangasek"prog_LIBS"?  that sounds like it's the wrong answer for a dlopen()ed module?14:25
Keybukoh, dlopen14:25
Keybukthat should still work though?14:25
slangasekanyway, I suspect that doesn't work; from what I see, libtool says "oh, you linked with this thing called bar.la, we're relinking, let's turn that into a -l option and look for -lbar"14:25
slangasekthe best workaround I've found is to provide a libbar.$mumble symlink14:26
slangasek(the naming scheme for the modules is set upstream, well-established and documented)14:26
TheMusoevand: for q quick start, you can find resources for developers on http://live.gnome.org/Accessibility14:31
=== _emgent is now known as emgent
=== DrPepperKid is now known as MacSlow
=== shawarma is now known as soren
slangasekcalc: hoi, what news on ooo-l10n?14:54
evandthanks TheMuso!14:56
calcslangasek: its building... hasn't failed yet so that is good news14:57
calcslangasek: i remembered the fact we change some i18n stuff in ubuntu so i removed that patch and it seems to be working14:58
calcslangasek: so if it does work i will have to examine the patch closer to find what it is breaking14:58
* calc needs a bigger box for OOo compiling14:59
\sh_awayseb128, did you read #184607 and bug #184176? would you like to fix gconf ? :)14:59
ubotuLaunchpad bug 184176 in gnucash "[hardy]Gnucash fails to build with libgconf2-dev 2.21.1-0ubuntu1" [Medium,New] https://launchpad.net/bugs/18417614:59
\sh_awaybug #18460715:00
ubotuLaunchpad bug 184607 in gconf "pkgconfig file says "Requires glib" instead of glib-2.0" [Undecided,New] https://launchpad.net/bugs/18460715:00
=== \sh_away is now known as \sh
calcslangasek: is it safe for me to upload once i get it resolved (hopefully later today) or is there anything it would block thats important?15:01
seb128\sh: no I didn't read it yet looking now15:02
slangasekcalc: er, I presume that once you have it fixed you *should* upload, since the lack of up-to-date l10n packages leaves ooo metapackage uninstallable and makes the hardy out-of-date list quite horrid :)15:02
calcslangasek: yea i was planning on it, but it will load a buildd for a while so wanted to make sure nothing else is pressing in the buildd queue right now15:03
slangasekah, not from my POV15:04
calcok15:05
calci'll get it uploaded today then assuming it finishes build i should be able to resolve the bad patch issue fairly quickly (i hope)15:05
bryce_MacSlow: I didn't find anything in the -intel git log15:05
MacSlowbryce_ ok so we might get a point in the xorg-crowd for fixing that :)15:10
bryce_:-)15:10
bryce_fwiw, xrandr -o 1 still locks up X  :-P15:10
HobbseeMacSlow: fixing what?  :)15:13
MacSlowHobbsee, https://bugs.edge.launchpad.net/ubuntu/+source/compiz/+bug/17577415:14
ubotuLaunchpad bug 175774 in xserver-xorg-video-intel "[hardy] Enabling "Normal" effects produces badly drawn window shadows." [Critical,Confirmed]15:14
=== mathiaz_ is now known as mathiaz
HobbseeMacSlow: nice!15:17
bryce_MacSlow: ok I've built a test deb for these changes15:22
bryce_brb15:23
* calc noticed that his build hasn't actually reached where it failed before15:27
slangasekTheMuso: you may want to merge ubuntu.hardy seed changes into ubuntustudio change; pwlib had an ABI change that ekiga has just been rebuilt for, the seeding of the plugin packages needs to be updated to match15:48
_MMA_slangasek: joejaxx can also handle this. I'll make sure he knows.15:50
slangasek_MMA_: ok, cheers15:51
slangasek_MMA_: picking on TheMuso because I know what timezone he's currently in :)15:51
_MMA_Thanx for the heads up.15:51
_MMA_slangasek: hehe. :P15:52
TheMusoActually, i need to talk to joejaxx about the way he is merging. He is not using bzr merge, which IMO he should be.15:53
slangasekheh15:53
_MMA_Oh ouch.15:53
TheMusoAs it then shows parent commits from the ubuntu seeds.15:53
* slangasek nods15:53
TheMusoslangasek: Picking on me? it seems like other people are more jetlagged than me, and they arrived earlier than I, and didn't have as far to go. :)15:54
_MMA_TheMuso: Well if you feel like kickin' ass and taking names while you're in London rock on. \m/ We should still talk to Joe.15:55
TheMuso_MMA_: Yes, I agree.15:55
TheMusoBut, I won't rule out feeling tired some time this evening.15:57
_MMA_TheMuso: Sure.15:57
slangasekTheMuso: right, "picking on you" because I know you're in my timezone.  and in walking range.15:59
TheMusoYes there is truth in that.15:59
calci found that sleeping pills seem to somewhat help with jetlag16:01
TheMusousually only takes me 1/2 nights, and I'm right.16:01
TheMusoof good sleep.16:01
* Hobbsee finds not travelling the most effective form of jetlag avoidance16:01
calcthough i didn't experience any nighttime kookiness16:01
calcHobbsee: ;P16:02
TheMusoI would rather not use anything to artificially simulate the boy to either feel sleepy or more awake.16:02
TheMusostimulate the body16:02
calchttp://en.wikipedia.org/wiki/Crook_and_Ladder16:03
TheMusoI do have the fact that I sleep deeply on my side.16:03
Hobbseecalc: :)16:04
KeybukRiddell: KDE 4 to have a six-monthly release schedule?16:26
calci obviously still have jetlag as i have a strong desire to go back to the hotel and sleep :-\16:26
calcand all the caffeine doesn't seem to help much16:26
RiddellKeybuk: that's the rough plan16:26
calcRiddell: aligned with Gnome?16:26
RiddellKeybuk: but 4.1 still has some must have features so it could slip if they do16:26
Riddellcalc: goodness no16:27
KeybukRiddell: is there any particular reason, apart from sheer bloody-mindedness, that they didn't pick the same rough dates as GNOME? ;)16:27
calcKeybuk: because KDE != Gnome? ;-)16:27
calcand to cause Ubuntu pain16:27
Keybukit isn't just Ubuntu though16:27
Keybukit causes every distribution pain16:27
TheMusoI've noticed the amount of soft drink that is consumed around here. Its scary.16:27
Riddellwell 4.0 happenes to come out in january so that sets the current schedule16:27
KeybukTheMuso: I'm trying to move everyone onto jelly bellys16:27
TheMusoKeybuk: Oh yeah. Thats even better.16:28
KeybukTheMuso: would you like some?16:28
Riddellcalc: january and july would be a perfectly convenient schedule for us16:28
calcRiddell: maybe they could scedule 4.1 to come out in Sept then to give them extra time ;)16:28
Riddellcalc: that might happen in its own course16:28
RiddellKeybuk: where are you reading this anyway?16:28
TheMusoKeybuk: Thanks for the offer, bt no thanks. I am trying to keep from using artificial/sugar stimulents.16:28
KeybukRiddell: planet ubuntu, of course16:29
calcok its past the failure point for ooo l10n (i think) so that is a good sign :)16:33
TheMusocalc: Do you have a beefy laptop, or are you building this on a fast home box?16:36
calcTheMuso: both, but i am building on my home box16:36
TheMusoright16:36
calcTheMuso: my laptop is core2duo 1.7GHz 4gb ram, my home machine is core2duo 2.8GHz 2GB ram16:37
TheMusoAh ok.16:37
calcTheMuso: i already had ccache primed on my home system so i just used that16:37
TheMusoah16:37
calceven with ccache its taking 5hr+ for the l10n build though16:38
KeybukI built oo.o once16:38
Keybukit took >5hr just for "apt-get build-dep" :)16:38
calcKeybuk: hehe16:38
TheMusoKeybuk: You were obviously somewhere with little/no bandwidth. :p16:38
calcTheMuso: ooo requires a LOT16:38
TheMusocalc: I doubt that not.16:39
calcthough it wouldn't take 5hr at the office to download its build-deps16:39
Keybukcalc: one would hope not16:45
calcis it normal for a system to not allow access for the ~ 3300MB - 4096MB range?16:47
calci have a i945 laptop and wasn't sure if it was a chipset or bios issue, at least when running x86_6416:47
calcin ia32 it probably is a issue due to needing space for pci map16:48
RainCTmvo: ping :)16:48
=== cjwatson_ is now known as cjwatson
mvoRainCT: pong16:53
RainCTmvo: before I upload fusion-icon (to Debian).. is it's priority extra for some reason or did you just forget to change it? :P16:53
mvoRainCT: I think I forgot to change it (I can't remember any particular reason)16:55
crimsunis Ted Gould present at the sprint?16:58
ogra1crimsun, yup16:59
calccrimsun: need him?17:01
crimsuncalc: yes please, concerning cleanup-audio-jumble17:02
calccrimsun: he said his irc client is currently broken but he would try to get online17:03
crimsuncalc: many thanks!17:03
calccrimsun: you might try emailing him until then17:04
=== bigon is now known as bigon`
calcyipee! i got l10n debs being spit out17:09
calcnow i just need to look through the diff to find the offending code17:09
TheMusoheh17:09
TheMusois that for amd64, or i386?17:11
calcits being compiled on amd64 but is indep17:12
calcit looks like my patch didn't do anything17:12
calcso i am going to reapply it, maybe i forgot to regenerate ooo-build afterwards when i did it before17:12
calci don't see how this patch could have done anything to cause it to fail where it did17:13
TheMusoOh fun.17:13
calcbut it is the only patch I made that I know of to the language stuff that isn't in debian which worked out of the box17:13
TheMusoRight.17:14
calcslangasek: so if you didn't see above i have made ooo l10n build but after looking at the patch I left out I am not sure why leaving out the patch helped, so i am going to try rebuilding with using the patch and regenerating the ooo-build build stuff17:18
calcslangasek: i wonder if it worked because of the aotcompile file change17:19
calcslangasek: since iirc language stuff is threaded it could have failed in a weird way due to running out of memory17:20
agd5fare there known issues with hardy and AMD64?  I've gotten a kernel panic with every image I've tried?17:30
calcrunning the full build if this works i will upload (probably in 5hr or so17:31
pochusoren: may I ask you to ACK bug 176007?17:43
ubotuLaunchpad bug 176007 in vinagre "Please sponsor vinagre_0.4 into Hardy" [Wishlist,New] https://launchpad.net/bugs/17600717:43
* seb128 kicks tracker17:47
seb128eating 100% cpu four hours and the applet has no label about it being indexing or anything17:48
* pochu kicks seb128 :)17:48
seb128pochu: heh17:48
seb128what did I do?17:48
pochukick tracker? ;)17:49
seb128its eating all the cpu without a good reason17:49
pochuseb128: tracker-status?17:49
seb128that deservers some good kicking17:49
seb128that hangs17:49
seb128and the applet has no label or count or anything17:49
pochuThat's odd.17:49
pochuDo you mean the progress bar isn't there?17:50
mjg59It means the daemon has stopped responding17:50
pochuHere it works quite well... after I told it not to index ~/dev and ~/tmp17:51
seb128#8  0xb7ddb4d7 in sqlite3InvokeBusyHandler () from /usr/lib/libsqlite3.so.017:51
mjg59seb128: What about the other threads?17:51
seb128mjg59: lack of debug packages I'll try to get debug backtrace17:52
seb128one thread has enough informations to indicate it was indexing INBOX17:53
seb128and there is 2 threads with libsqlite functions17:53
seb128one being stopped on sleep apparently17:53
mjg59Hm17:53
seb128oh17:54
seb128what my be an interesting detail is that my laptop is running on battery at the moment17:54
seb128so it should not start and eat batteries17:54
seb128what might be17:54
mjg59Yeah17:54
=== Kmos_ is now known as Kmos
sorenpochu: Sure thing!17:54
sorenpochu: Done.17:55
pochuseb128: It doesn't do initial index on battery, but that's not the initial index I guess...17:55
pochusoren: thanks :)17:56
mjg59pochu: You can disable both types individually17:56
pochuseb128: You are using evo right? There's this crash in LP, although it doesn't mention libsqlite: bug 18022017:56
ubotuLaunchpad bug 180220 in tracker "trackerd crashed with SIGSEGV" [Undecided,New] https://launchpad.net/bugs/18022017:56
seb128pochu: it should do nothing on battery17:56
_MMA_seb128: I added my xsession-errors to bug 183199. Might give you some idea. Hopefully I can track down more details with crimsun later.17:56
seb128pochu: yes17:56
ubotuLaunchpad bug 183199 in gnome-control-center "System sounds aren't being played in Hardy." [Undecided,New] https://launchpad.net/bugs/18319917:56
pochumjg59: Right. But do we disable both by default? I thought only initial index was deactivated.17:57
mjg59Yes17:57
pochuOk, sorry then.17:58
crimsun_MMA_: (pointer for later:  check capplets/sound/ and libsounds/)17:58
_MMA_k17:59
seb128crimsun, _MMA_: I've no pulse running so it might use aplay18:00
mjg59seb128: No, I don't think that follows18:00
seb128_MMA_: do you have pulsesomething running?18:00
mjg59seb128: Even if I'm on battery, if I save a new file I want it indexed18:01
seb128mjg59: what?18:01
seb128mjg59: depending how much indexing takes18:01
mjg59seb128: Per-file, it should be very little18:01
seb128right18:02
mjg59The hard drive will be spun up anyway18:02
* _MMA_ fires up the Hardy test box.18:02
seb128mjg59: not sure how much indexing a mail takes but you can easily have hundred of mails there18:03
seb128brb18:03
seb128restarting my session18:03
seb128_MMA_: do you have pulseaudio-esound-compat installed?18:07
seb128does installing it and restarting your session makes any difference?18:08
* _MMA_ looks.18:08
_MMA_pulseaudio is running.18:08
_MMA_And we mirrored what Ubuntu had in its seed list sound-wise.18:08
seb128does paplay /usr/share/sounds/login.wav work correctly?18:08
Keybukbryce: err, I've just had my external screen blank18:14
Keybukhow do I get it back?18:14
_MMA_seb128: pulseaudio-esound-compat is installed. paplay /usr/share/sounds/login.wav does yield sound. Playing that same file through gnome-sound-properties does not.18:15
bryce_Keybuk: restart X maybe?18:16
Keybukbryce_: a less drastic solution? :p18:17
bryce_hehe18:17
bryce_Keybuk: there might be an xrandr incantation to bring it back18:17
bryce_Keybuk: any clues in Xorg.0.log?18:18
Keybukno18:18
Keybukat least nothing I understand18:19
agd5fbryce_: you know of any AMD64 issues with hardy?  I've get to find an image that boots.  stuff scrolls by pretty quick, but looks like something about the ioscheduler then I get a panic18:21
bryce_agd5f: hmm, I've not tested on my amd64 system lately18:22
selckinmine hanged somewhere after hd detection without any messages, started working when i used /dev in root= instead of UID18:23
bryce_agd5f: have you tried the 32bit x86 images or just 64bit?18:23
agd5fjust 64 bit, I ran out of blank cds :)18:23
bryce_agd5f: which hardy version(s) have you tested on?18:25
agd5falpha3 and yesterday's snapshot18:25
bryce_ok, that's a -4 kernel18:25
seb128_MMA_: I figured what is wrong18:25
bryce_can you send us a stack trace or dump?  (photo maybe?)18:26
agd5fyeah18:26
agd5fbryce_: I'll file a bug18:26
seb128crimsun, _MMA_: that's an esound bug18:26
bryce_agd5f: cool.  I'm sitting next to tim gardener, and he said he'll take a look18:28
bryce_brb, testing a 965 compiz fix...18:28
BenderUnit22~/clear18:31
_MMA_seb128: Ok. Hopefully crimsun and I can sort it out.18:37
_MMA_seb128: I did get an odd issue when searching for pulseaudio-esound-compat in Synaptic. (not related to the package.) Synaptic completely locked until I killed update manager. I've never seen that before.18:39
seb128_MMA_: the bug is an esound one, I'm going to look at fixing it now18:45
seb128_MMA_: it's using .esd and not .esd-100018:45
_MMA_seb128: Awesome. Thanx. Let me know if I can help.18:45
seb128_MMA_: you are welcome18:45
* _MMA_ sends TheMuso to give Seb a hug. (If Sebastian is in London that is) :P18:46
TheMusolol18:47
_MMA_;)18:47
slangasekpitti: is the gnome-keyring-manager -> seahorse seed change ok for upload?18:49
\shdoko, reping crystalspace ... again the question you mentioned "configure --without-java" in your last upload..but it's commented...18:50
doko\sh: hmm, can't remember ... maybe just do what debian does18:51
\shdoko, k..:)18:51
pittislangasek: yes, it is18:51
slangasekpitti: ok, ubuntu-meta uploaded then18:52
pittiyay18:53
agd5fbryce: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/18488319:32
ubotuLaunchpad bug 184883 in linux "hardy AMD64 kernel panic on boot" [Undecided,New]19:32
agd5fbryce: looks like a bios issue20:48
=== \sh is now known as \sh_away
agd5fI hardcoded the ram voltage and now it seems to boot ok20:48
=== fabbione is now known as thegodfather
crimsun_MMA_: didn't you test the /tmp/.esd symlink I suggested several days ago?22:01
_MMA_crimsun: I did. Lemmie see what I told you.22:03
crimsun_MMA_: did you log out and back in after creating the symlink (I don't see why that would have been necessary)?22:04
_MMA_crimsun: After doing that the sounds didnt play but I got "(gnome-sound-properties:6093): Gnome-WARNING **; error caching sample <-1>!"22:05
pochusoren: btw, and in case you missed it, I attached a debdiff to bug 183169 ;) I've of course tested it with vinagre 0.4, and it solves the issue (for "localhost:1" and for "ñlkjadf~@|#")22:16
ubotuLaunchpad bug 183169 in gtk-vnc "Crash if hostname contains invalid characters" [Medium,Confirmed] https://launchpad.net/bugs/18316922:16
=== azeem_ is now known as azeem
basyAre there any installers for man pages? I need to install man pages for develop with openGL, i have mangl.tar.Z and there are *html and *3gl manuals, any idea how to install that?23:09
basyplz23:10
Seveasbasy, this is not a support channel23:11
basy<Seveas> and which one is for support?23:11
Seveasbasy, #ubuntu23:12
basyi ll try  there sorry23:13
=== illovae is now known as druuna
=== druuna is now known as illovae
Keybuk...we could always just remove openoffice from the seeds and replace it with abiword and gnumeric...23:46
evandseconded23:46
LaserJockgnumeric is pretty darn sweet, at least from my experience of scientific spreadsheet use23:48
mjg59gnumeric is fine. Abiword, less so.23:50
LaserJockI agree23:51
LaserJockalthough I've had Abiword do a little better with some things23:51
LaserJockas far as .doc compatibility23:51
LaserJockmy only personal issue with s/openoffice/abiword+gnumeric/ is having an Impress replacement23:52
Keybukmjg59: the abiword in gutsy/hardy is nice23:52
KeybukI've found it much nicer for writing in23:52
mjg59It's nice, but it's not very /useful/23:52
mjg59At least, for the common case of dealing with .docs23:53
Keybukyeah, the file format stuff maybe not23:53
mjg59(Yes, I know this is a ridiculously hard problem)23:53
Keybukbut openoffice is less useful since it's not INSTALLABLE :)23:53
LaserJockmjg59: have you seen any tests on that? I'd be interested in what abiword fails with regarding dealing with .docs23:54
johanbrIn my limited experience, abiword handles .doc files fine. Although I never receive very complex documents...23:54
mjg59LaserJock: They look different to when I open them in OpenOffice :)23:55
LaserJockmjg59: yes, although in my experience Abiword actually looked closer to Word than OpenOffice did23:55
mjg59Hm. Mine's the opposite23:55
LaserJockbut I only have a limited case23:55
mjg59But, as I said, this is hard23:55
LaserJockI have a book chapter I'm working on, so it's decently complicated but no graphics, just text23:56
LaserJockthe only thing I really saw that Abiword failed at was in using multiple fonts at the same time, abiword just picked one whereas OO.o kept the font list23:57
ScottK2IMO, .doc compatibility is a must.23:57
LaserJockScottK2: yeah, but it's kinda subjective, IMO, which is the problem23:58
LaserJockit'd be nice to have a systematic way of evaluating23:58
ScottK2OOO 2.3 has gotten it to a point where I almost never have a problem.23:59

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