[12:04] is ubuntu in debconf high or critical? [12:07] srbaker: critical in the installer, high in the installed system [12:07] cool [01:00] hi all. [01:02] hrm.. no jdub, eh? === srbaker [~srbaker@blk-224-143-227.eastlink.ca] has left #ubuntu-devel ["Leaving"] === mdz [~mdz@69-167-148-207.vnnyca.adelphia.net] has joined #ubuntu-devel === wartylog [~warthylog@port1845.ds1-khk.adsl.cybercity.dk] has joined #ubuntu-devel === Topic for #ubuntu-devel: Ubuntu development -- general discussion on #ubuntu === Topic (#ubuntu-devel): set by mdz at Mon Sep 20 07:48:40 2004 [01:54] mdz: can we sync gftp with debian? -6 fixes RC bug for both us and them; the fix is in incoming; our bug # is 1806 [01:54] (we have -5 already) [01:54] Mithrandir: just saw that [01:54] yes, fine with me [01:54] please request it [01:55] willdo === sivang [~user1@80.179.82.108.forward.012.net.il] has joined #ubuntu-devel [01:55] night all [01:56] has anyone bumped into _very__very_ slow disk performance under inspiron 8200 laptop? I recently install a daily from about 4 days ago, and it just crewles.. [01:56] Is this more appropriate at #ubuntu ? :) === Mithrandir hopes he got the long addresses right and goes to bed. [01:58] night Mithrandir === lamont introduces his daughter to xlife. this is fun. [02:18] : [02:18] :) [02:18] any urgent bugs? === truk-away [~trukulo@docsis65-46.menta.net] has joined #ubuntu-devel === minghua [~minghua@danube.mems.rice.edu] has joined #ubuntu-devel === minghua [~minghua@danube.mems.rice.edu] has left #ubuntu-devel ["Leaving"] === runo [~runo@CM-lcon1-38-130.cm.vtr.net] has joined #ubuntu-devel === jamesh [~james@203-59-87-199.dyn.iinet.net.au] has joined #ubuntu-devel === jdub [~jdub@home.waugh.id.au] has joined #ubuntu-devel === tseng [~tseng@thegrebs.com] has joined #ubuntu-devel [04:40] justdave: happiness? [04:40] lamont: yep [04:40] what was it? [04:41] I accidently nuked a paren when I added the -f [04:41] ouch [04:41] because my stupid terminal was sending the wrong code for backspace :) [04:41] heh [04:43] guess postfix isn't as picky about that stuff as sendmail (or at least not by default) [04:43] sendmail makes you grant users permission to use -f [04:43] fehj [04:43] which is why I assumed I needed admin support :) [04:43] nc localhost 25 [04:44] yeah. then again, postfix's sendmail is mode 555 [04:44] and just writes a file into /var/spool/postfix/maildrop [04:44] one of these days soon, bugzilla will do smtp by default anyway [04:46] if you do, there's always sendmail -bs for those that can't run on port 25. But that's a gross hack from days gone by [04:47] back in 30 or so [04:47] later === npmccallum [~npmccallu@69-162-252-7.ironoh.adelphia.net] has joined #ubuntu-devel === lamont [~lamont@mix.mmjgroup.com] has joined #ubuntu-devel === lamont [~lamont@mix.mmjgroup.com] has joined #ubuntu-devel === lamont [~lamont@mix.mmjgroup.com] has joined #ubuntu-devel === doko [doko@dsl-084-057-030-252.arcor-ip.net] has joined #ubuntu-devel [06:44] morning guys [06:55] fabbione: morning [06:55] hey dani [06:56] daniels: i start to be a bit worried about Dec conf. [06:56] jane talks about end nov. mid dic [06:56] mark isn't sure... [06:56] personally i don't mind [07:18] oh man [07:18] the gnome-cups-manager test pages are all line-based, not font-based [07:18] ie. can't just s/XIMIAN DESKTOP/UBUNTU/g :) [07:19] ew! [07:20] jdub: btw, if you or anyone else can tell me how to preserve categories for contacts into evo2.0 and back, that'd be the last thing that's keeping me on jpilot... [07:20] lamont: to and from palm? [07:21] yes [07:21] the only use I have for evo is to sync my palm. :-) [07:21] heh [07:22] I _like_ the MUA I use, don't want some stupid gui MUA. :-) [07:22] lamont: so why do you sync with evolution at all? [07:22] atm I don't/ [07:23] but if I could preserve my address book categories, then I could drop jpilot. [07:23] the wifely one is using evo, because I didn't want to make her non-conformist... [07:23] ok, why do you want to sync with eovlution insetad? [07:23] oh [07:23] she discovered this evening that if you drop 5 concurrent events into evo, it segv's trying to print it... ;) [07:24] jdub: I'm _trying_ to be a good warthog/ [07:24] and it would be nice to share calendars in the house. === lamont admits to some usefulness to evo. I just don't want it for my MUA... === lamont looks at the clock, and realizes that he has to get up in about 5.5 hours. sigh. [07:25] daughter wants up at 5, instead of the normal 5:30. [07:25] I hate getting up early. [07:26] anyway, g'night [07:27] night [07:29] jdub: pstoedit? [07:31] mdz: thought about that, but doesn't convert to anything inkscape likes [07:31] but i could screw around with xfig [07:32] WWBJD? [07:33] jdub: there is a pstoedit SVG output plugin [07:33] maybe you could ask Ximian for whatever source format they have for the page [07:33] :) [07:34] it should probably be fixed in gnome cvs anyway [07:34] mdz: where's the svg output plugin? [07:34] http://www.pstoedit.net/plugins [07:34] eww, it's a binary [07:35] yeah [07:35] "Unless you get a key, these drivers will slightly distort the generated output. Colors will be changed and the letter e will be replaced by $." [07:36] oh hey [07:36] are you sure pstoedit doesn't support svg out of the box? [07:36] it looks like it can use the libplot svg output [07:37] pstoedit -f plot-svg xd2-testpage-a4.eps /tmp/test.svg [07:37] Interpreter finished. Return status 0 [07:39] mdz: it just gave me 0 length output\ [07:39] inkscape seems to like it fine [07:39] oh, now it's working [07:39] bong [07:40] ugh, the output is horrible [07:40] it's a little cracked out [07:40] might even be worth doing our own ;) [07:41] for some reason everything is covered by black circles [07:41] s/circles/shapes/ [07:41] if you delete that crap, the good stuff is underneath [07:41] maybe it's some weird printer magic [07:42] all of the objects are there, it's just the colours that are borked [07:43] mine are all misshapen [07:45] inkscape crashed on me [07:46] probably worth making our own :-) [07:46] I liked all the little test patterns they provided though [07:48] mmm === jdub has found a test page generator [07:48] will see if the output sucks or not ;) === pitti [~martin@195.227.105.180] has joined #ubuntu-devel [07:53] Hi guys! [07:53] pitti: good morning [07:53] mdz: Morning. Exhausting weekend... [08:11] http://www.gnome.org/~jdub/random/ubuntu-a4.eps or http://www.gnome.org/~jdub/random/ubuntu-letter.eps [08:11] anyone want to check those out? [08:14] hmm [08:14] that looks pretty good [08:23] jdub: ERROR 404: Not Found. [08:24] that makes ithard to test [08:25] mdz: 1808 what do you want me to do with this one? [08:25] jdub: ^^ [08:25] pitti: does this sound like it could be related to pmount? https://bugzilla.ubuntu.com/show_bug.cgi?id=1715 [08:26] pitti: I can easily fix up my gnome-vfs patch, but I'm wondering why the problem occured just recently. [08:27] fabbione: oh, that reminds me [08:27] fabbione: pipka's laptop only supports the full resolution of the lcd at 16bit [08:28] fabbione: which means the configuration fails :| === fabbione ask again... what should I do with it? [08:29] defaulting to 16 bits or let 24 bits? [08:29] one way or another we will get bug reports [08:29] do you mean in the general case? [08:29] "it doesn't work at 24 bits but only at 16" [08:29] http://www.gnome.org/~jdub/random/ubuntu-a4.eps or http://www.gnome.org/~jdub/random/ubuntu-letter.eps [08:29] "GRAVE BUG: my video card supports 24 bits and you only init at 16" [08:29] ^ try again :) [08:29] fabbione: ;-) [08:29] jamesh: this is indeed the same bug as #1599. [08:30] jdub: yes as a general case... it's either one or another [08:30] fabbione: if there is some way to auto-detect the situation, great [08:30] jamesh: this is not directly a pmount problem, it's a gvfs bug [08:30] fabbione: if not, close it [08:30] fabbione: either way, it's not important for the release (hence severity; enhancement) [08:30] mdz: hhhrrrmmm, it ends up being important [08:30] jamesh: seb recently uploaded a new gvfs, and my patch (which worked fine with the older one) does not play well with the new upstream version [08:30] jdub: what does? [08:30] jamesh: so I disabled it temporarily [08:30] pitti: I can probably get the computer:/// and network:/// patches to only move "connect to server" type entries. That would solve the problem, right? [08:30] mdz: well there is a way, but that will require xresprobe to return me the amount of ram on the video card and according to resolution set the depth [08:30] mdz: when the resolution chosen does not work at 24bit [08:31] jamesh: yes, this would solve both bugs. [08:31] mdz: but do you feel to implement it at this point in time? [08:31] fabbione: no, I really don't [08:31] jamesh: if you know the guts of gvfs well enough, it would be great! [08:31] mdz: i realize we did never discuss this problem before [08:31] mdz: so it's a point, but up to you [08:31] pitti: okay. I'll put together a patch, and we can see if it solves things. [08:31] this is only an issue with older graphics cards which do not have enough RAM, right? [08:31] fabbione: i'd say hoary [08:31] jamesh: I actually thought that I had to write new code to make the devices appear in Disks, but if that code already exists, so much the better [08:31] jamesh: thanks! [08:32] mdz: that's a lot of machines [08:32] mdz: not just older [08:32] pitti: my patch moves all GnomeVFSVolumes that don't have an associated GnomeVFSDisk object to network:/// [08:32] jdub: video cards sold today have more ram than most of my computers [08:32] jamesh: ah, maybe that was the reason why my previous patch just did not work any more [08:32] pitti: I'm not sure why things like the firewire and USB drives don't have a Disk object now though. [08:32] mdz: in ricer machines, sure [08:32] jdub: in something you buy from Dell or HP [08:33] pitti: s/GnomeVFSDisk/GnomeVFSDrive/ [08:33] mdz: it's a significant bug, but something that can probably wait until hoary [08:33] jamesh: upstream version only shows Disks which have an fstab entry [08:33] mdz: yes [08:33] jdub: I don't see that we can do anything intelligent in that situation; we would need to ask a question [08:33] jamesh: my previous patch "faked" such an entry by modifying the function which read fstab; it added the user-entries of mtab [08:33] "what's more important: colours or resolution?" [08:33] pitti: okay then :) [08:34] jamesh: but with the new upstream version, it became unreliable and breaked the trash [08:34] mdz: it's easy to determine from available video ram [08:34] jdub: you can't determine whether the user would prefer a higher resolution with fewer colours, or a lower resolution with more colours [08:35] that's the tradeoff, isn't it? [08:35] not on an lcd :-) [08:35] but it's something you can decide that they can reconfigure later [08:35] (on a crt) [08:36] that's what we do today :-) [08:36] they can't, because their system doesn't work [08:36] why not? [08:37] can the driver not detect that the mode is no good and fall back? [08:37] we don't do that today [08:37] when pipka installed her machine [08:37] it chose the right resolution for the lcd [08:37] and the wrong colour resolution [08:37] were she not a kung-fu master, she would not have got out alive [08:38] ah, ok [08:38] so the LCD was configured correctly, but the card can't drive it [08:38] if you can determine two useful configurations from the video ram [08:38] in the LCD case there is no tradeoff [08:38] you just need to drop the depth [08:38] then on a laptop you can choose the correct one for the lcd [08:39] on a crt you can make up some reason why you'd choose one over the other [08:39] and let the user configure it how they want later [08:39] #1808 is a different case [08:40] I think the emulator just sucks, but I wasn't sure [08:40] no, same case [08:40] it's just not hardware ;) [08:40] oh, you have a copy of microsoft virtual PC? [08:40] that'll come in handy for testing the fix [08:41] i don't, but i know it emulates an s3 [08:41] i think i can get access to a copy [08:41] I don't think the chipset is relevant [08:41] but probably don't need it, the fix is described above :) [08:42] the chipset isn't relevant, it's the 'hardware environment' [08:42] the 'hardware environment' in this case seems like a buggy emulator [08:42] which is a very differetn case from a card which is short on video ram [08:42] the amount of video ram can generally be probed [08:42] dude, it emulates a video card that can't do that [08:42] nothing wrong with the emulator [08:42] I _have_ an S3 card, and it _does_ to 24-bit colour [08:43] s/to/do/ [08:43] jdub: eps: maybe let the user know how many lines around the edges he is supposed to see? [08:43] apart from making a bad choice of hrdware setup [08:43] doko: hrm, that'd be a software issue ;) [08:43] doko: just replacing the poopie eps shipped with gnome-cups-manager [08:45] jdub: no, just print it somewhere on the page, "you should see ... if not, adjust your setup, help at ..." [08:46] fabbione: hmm, there is also a tradeoff with DRI [08:47] my mga card can only run 1600x1200 with DRI disabled due to lack of RAM [08:48] mdz: ok.. should we default to 16 bits? [08:48] fabbione: hell no :-) [08:48] fabbione: just another thing to think about when we decide to look at this issue in the future [08:48] mdz: we need to rewrite all the autodetection code anyway [08:48] and do a hell of a lot of a cleanup [08:49] s3s do do 24-bit, yes === pitti [~martin@195.227.105.180] has joined #ubuntu-devel [08:52] http://www.robertmoir.co.uk/win/vpcfaq/VPCFAQ7-KnownIssueswithVP.html#7.3 [08:52] http://vpc.visualwin.com/ [08:52] ^ mentions ubuntu ;) [08:53] hah, nice [08:55] Colin Barnhorst seems to have tried many different operating systems [08:55] hah, even knoppixmyth is on there [08:56] sick puppy ;) [08:57] but "does it worK? no" [08:59] hah, that page describes linux boot parameters as "cheat codes" [08:59] up-up-up-b-b-a-start-down-- WOOHOO! KERNEL 2.6!!!! [08:59] ^^vv<><>ABAB START [09:00] try to submit an entry for "Small Ubuntu Server", maybe it shows up in the front then ;) === mdz blinks at the PregnantPanda proposed release name [09:03] let's choose that name for the next release which requires new glibc, new gcc, new kernel, new X and new just about everything else [09:04] mdz: i like PokeyPenguin [09:04] that's Hoary, or Hoary+1 ? [09:05] hoary+2 is meant to be PerkyPenguin [09:10] ok bong-sippers [09:10] what do you think about those printer pages [09:10] ? [09:10] otherwise i'm just going to upload the suckers [09:11] ubuntu. [09:14] where are the printer pages? [09:15] ah, missed the 'try again' [09:15] http://www.gnome.org/~jdub/random/ubuntu-a4.eps or http://www.gnome.org/~jdub/random/ubuntu-letter.eps [09:16] jdub: definitely fixes the bug :-) [09:25] heh [09:25] you like? [09:25] fabbione: any idea about 1724? [09:26] pitti: I just bugzilla'd the new gnome-vfs patch. [09:26] jdub: I think it would be nice to have some test patterns and stuff, but for Warty purposes, what you have is more than sufficient [09:26] patterns rather than colours? [09:26] jamesh: thanks! Does it work now? [09:27] jamesh: I will take a look at it (out of curiosity :-) ) [09:27] jdub: text in a few different fonts, stipple pattern, parallel lines, etc. [09:27] mmm [09:27] pitti: it doesn't cause any problems here, and the patch to computer-method.c is a lot simpler [09:27] pitti: which means that it should behave more like upstream [09:28] jdub: I say ship it [09:28] SHIP IT! [09:29] pitti: I've only got a limited number of volume types to test on this box, which is why I'd like to know if it works well in other situations. [09:29] jamesh: still quite a big patch, but it looks as if it _could_ go upstream... [09:29] jamesh: I think there's only one possibility to find that out :-)) [09:29] pitti: it is a replacement for a patch we already have in gnome-vfs, and it is a bit smaller than the one it replaces. [09:30] pitti: the diffs between the two patches are quite small. [09:30] jamesh: shall I build and test the package before you ask mdz to approve it? [09:30] pitti: that would be useful, yes. [09:31] jamesh: do you already have a i386 deb somewhere? [09:31] no. [09:31] jamesh: okay, I build it myself. [09:36] this version of the patch could probably be sent upstream (the last version wasn't as clean) === azeem [~mbanck@socks-out.lrz-muenchen.de] has joined #ubuntu-devel === seb128 [~seb128@ANancy-111-1-3-129.w81-250.abo.wanadoo.fr] has joined #ubuntu-devel [09:50] Morning seb128! [09:50] morning [09:51] yo seb128 [09:51] grrr, 30 hours to fix the dsl connection, apparently dsl people don't work sunday [09:51] seb128: got my mail? [09:51] ouch [09:51] just back from 30 hours internet-less [09:51] my fetchmail/spamassassin/... is working :) [09:52] jamesh: patch works fine for me [09:53] pitti: great. [09:53] jamesh: this bug report was great; so far I thought that the new device would not appear in Nautilus at all [09:54] jamesh: I would have never come to the idea to look in "Network" for it :-) === seb128_ [~seb128@ANancy-111-1-18-15.w81-51.abo.wanadoo.fr] has joined #ubuntu-devel === trukulo [~mzarza@26.Red-81-45-239.pooles.rima-tde.net] has joined #ubuntu-devel [10:02] funny, I'm getting 2 weeks old mails for 3 days (WTF with my @debian) [10:04] jdub: the new hal 0.2.98 does not work with the current g-v-m, so I need to upload a new gvm [10:04] jdub: there is a new upstream version 1.0.2 of g-v-m which just adds some new translations [10:04] :) [10:04] seb128_: read planet.debian.net, there was a problem with mail server [10:04] jdub: may I upgrade g-v-m- while I'm at it? [10:05] pitti: yes thanks [10:06] http://www.extremetech.com/article2/0,1558,1651228,00.asp [10:06] ^ (p)review === elmo_ss [~james@host217-37-231-28.in-addr.btopenworld.com] has joined #ubuntu-devel === pitti [~martin@195.227.105.180] has joined #ubuntu-devel === pitti [~martin@195.227.105.180] has joined #ubuntu-devel === jdthood [~jdthood@aglu.demon.nl] has joined #ubuntu-devel === pitti [~martin@195.227.105.180] has joined #ubuntu-devel [11:30] seb128: the nautilus-cd-burner in warty does not yet use the new locking mechanism of hal to prevent further mounts; is this already upstream? [11:30] yes it's upstream [11:30] but need hal >= 0.2.98 [11:30] so it's not buildable for the moment [11:30] seb128: I just packaged crack-of-the day hal/dbus/gvm [11:30] seb128: now I test CD burning [11:31] ok [11:31] cool [11:31] seb128: I cannot find any trace of lockign in the n-c-b sources [11:31] it's in 2.8.3 [11:31] seb128: ah, so I'm going to package this as well [11:31] seb128: unless you want to do that... === azeem [~mbanck@socks-out.lrz-muenchen.de] has joined #ubuntu-devel [11:32] pitti: that's just a matter of dch -i, New upstream release and update the hal depends [11:32] pitti: so as you want :) [11:32] seb128: okay, since the other stuff is at my hd and not uploaded yet, I would do it [11:32] ok, thanks [11:32] seb128: so the guys can test the complete new stack from my archive without having it to upload first [11:33] yeah [11:33] jdub: [11:34] xfree86 (4.3.0.dfsg.1-6ubuntu22) warty; urgency=low [11:34] * Update 000_stolen_from_HEAD.diff: [11:34] + Include Xv/framebuffer fix for xf86xv.c. [11:34] * Update 030_Xserver_and_driver_region_primitive_fixups.diff: [11:34] + Fix REGION_EQUAL call in nv_driver.c. [11:34] * Update Czech debconf template translations (thanks, Miroslav Kure). [11:34] * Apply fix for Keycodes for PrintScreen and SysRq. (Closes: #1762) [11:34] -- Fabio M. Di Nitto Mon, 27 Sep 2004 07:58:55 +0200 [11:34] seb128: http://ftp.gnome.org/pub/GNOME/desktop/2.8/2.8.0/sources/ just has n-c-b 2.8.0 [11:34] seb128: where do you pull new sources from? [11:35] seb128: ah found it [11:35] seb128: sorry for disturbing [11:35] np [11:40] jdub: ok, changes done for the -fr list [11:47] seb128: hmm, ncb 2.8.3 still does not attempt to umount the CD-RW [11:48] seb128: how easy is it to add an _extra_ unmount option to the context menu? (By now you just have eject) [11:48] no idea [11:48] should ask jamesh about this, he had a look on that [11:50] seb128: I haven't looked at the exact nautilus code, but I could. [11:50] ok [11:50] jamesh,seb128: I think I can add the unmounting to n-c-b [11:51] jamesh: have you replied to my question about pygtk/gnome the other day ? [11:51] jamesh,seb128: but having a separate unmount option for CDs is a good idea nevertheless [11:51] pitti: why do you want to umount in n-c-b ? [11:52] seb128: by now you insert an RW, it is mounted automatically; if you want to burn on it, it is busy [11:52] seb128: however, there is no possibility to unmount it, it is ejected [11:52] you want to add an umount "option" ? [11:52] seb128: so we could pumount -l the device before burning [11:52] yes, but not an option [11:52] just umount it [11:52] seb128: okay, then without -l [11:53] seb128: by now, there is just a "TODO: unmount the device..." in the ncb code [11:53] I can ping an upstream about this === ross [~ross@82-44-126-41.cable.ubr03.croy.blueyonder.co.uk] has joined #ubuntu-devel [11:54] seb128: maybe a good idea; I don't know much about the code [11:54] seb128: I can add the umount there and try if it works [11:54] ok [11:58] seb128: I talked a bit with jdahlin about it. The fix is probably the right thing for Python < 2.3.5 [11:58] pitti: btw, the code for handling unmount/eject context menu item is in real_update_menus_volumes() in src/file-manager/fm-directory-view.c [11:59] pitti: it seems to use the same verb for both eject and unmount [11:59] jamesh: so the decision is taken at a lower level? [11:59] jamesh: that would mean it is nontrivial to add, isn't it? [12:02] pitti: the decision between eject and unmount is in the eject_for_type() function [12:02] pitti: which is set to show an eject option for cdroms, zip and jaz drives, and unmount for others [12:02] jamesh: I saw this once; it does not seem to be designed for just unmounting [12:03] jamesh: well, if its nontrivial to change and cd-burner supports automatic unmounting, it's not such a big deal, I suppose [12:03] pitti: unmount_volume_callback() uses the result of eject_for_type() to decide whether to eject or unmount [12:03] pitti: and the code for setting up the context menu uses eject_for_type() to decide whether to call the item eject or unmount. [12:04] it isn't a case of showing one item and hiding the other [12:04] jamesh: ugly... [12:04] jamesh: at least for having two commmands... [12:04] it is just a single menu item with a different label depending on the drive type. [12:05] pitti: well, other than the case you mentioned, when is a user going to want to unmount a cdrom or zip disk? [12:05] pitti: the correct fix would be to get n-c-b to do the unmount [12:05] jamesh: I would do it if I wanted to repartition my USB stick, ZIP drive or whatever [12:06] jamesh: but if I want to do that, I can as well type umount by hand [12:06] jamesh: I want to fix n-c-b anyway [12:06] pitti: actually, you probably couldn't umount by hand ... [12:06] if the stick has a trash dir [12:06] jamesh: these device locks, I suppose [12:07] jamesh: but that shouln't happen on CD-ROMs, no? [12:07] jamesh: seb128 suggested not to lazily unmount the CD, but do that normally [12:07] pitti: the Gnome vfs umount/eject stuff has a "pre unmount" signal so that apps like nautilus can stop monitoring directories [12:08] since fam/gamin's dnotify watches hold the device open [12:08] jamesh: hmm, so actually n-c-b should call this instead of umounting directly? === Sledge [~steve@80.46.37.1] has joined #ubuntu-devel [12:09] morning... [12:09] morning Sledge [12:10] pitti: yep. Get the GnomeVFSVolume or GnomeVFSDrive object for the cd drive and call its unmount() method. [12:10] jamesh: any idea how I can do that in n-c-b? I only have the device string (/dev/hdc or so) [12:11] pitti: gnome_vfs_volume_monitor_get_volume_for_path() might do it. [12:15] jamesh: do I have to call the pre_umount method myself or does GnomeVFSVolume's umount() method care for that? [12:15] pitti: the gnome_vfs_volume_unmount() routine handles it all for you. [12:15] jamesh: thanks a lot for your help! [12:19] pitti: if inotify existed a few years back, things wouldn't be so complicated ... === Capri [~makolb@mnch-d9ba4117.pool.mediaWays.net] has joined #ubuntu-devel [12:32] does somebody already had problems to boot the warty iso on a powerbook ? [12:34] seb128: define problems [12:34] the powerbook doesn't boot on the CD [12:34] it doesn't see it as a bootable one or something like that [12:34] seb128: hold 'c' as you power on [12:35] ok, not for me, I'm telling that to the guy ;) [12:35] thanks [12:35] sure [12:35] and for shared-mime-info, yes it was 0.15 :) [12:36] right, well, that bug is still occurring then :-/ [12:36] thom: 'c' doesn't work, the guy says it already does that [12:36] debian CDs boot ok [12:36] warty doesn't boot [12:36] s/it/he/ [12:41] seb128: btw, I did a patch for bug 1715 (firewire volume showing up under Network) [12:42]