[05:52] <pwnguin> strange question: what's the "right" way to bring a newer kernel into a feisty install?
[05:52] <RAOF> Build from kernel.org sources, and use make-kpkg?
[05:53] <pwnguin> what about ubuntu specific patches?
[05:53] <pwnguin> or at least, patches ubuntu picked up that linus hasnt
[05:54] <RAOF> Well, you could get the kernel source package from launchpad, I suppose
[05:54] <pwnguin> from the kernel team
[05:54] <pwnguin> but im not sure how that works with restricted drivers.
[05:55] <RAOF> Well, I think make-kpkg should work.
[05:55] <RAOF> Heh, it doesn't, although you could use the module-assistant package
[05:55] <pwnguin> someone suggested installing the gutsy kernel, and that didnt go so well
[05:55] <pwnguin> im not entirely sure why, but it scares me a bit
[05:56] <RAOF> I hope that wasn't you in the forums I recommended against installing the gutsy kernel to :)
[05:56] <pwnguin> i rarely post in the forums
[05:56] <RAOF> Good, good :)
[05:56] <pwnguin> besides, i know what im doing most the time
[05:58] <pwnguin> i tried grabbing the kernel from launchpad like you said last nigth, but dependencies were being troublesome, so i figured id just add gutsy to sources.list for a second
[05:58] <pwnguin> install the kernel, then ditch the source
[05:58] <pwnguin> worked surprisingly well, but the kernel locked up around acpi or something
[05:59] <pwnguin> could be related to not being able to find a /dev/disk/by-uuid/ =/
[06:12] <crimsun> likely unrelated.
[06:15] <pwnguin> well, loading acpi modules and not being able to find the root partition somehow would be related
[06:16] <crimsun> that's highly unlikely.
[06:16] <pwnguin> i would imagine so
[06:17] <pwnguin> unfortunately i dont have a serial port on that laptop
[06:17] <crimsun> by the time it rolls around to trying to find /dev/disk/by-uuid, it needs to have gotten the initramfs and pivotroot to get /
[06:18] <crimsun> if you get acpi errors, you'll get their unfortunate results long before it gets far enough in initramfs
[06:18] <pwnguin> i need to figure out which partition it can't find first obviously
[06:23] <pwnguin> well it was definately /dev/sda1, but that was windows. plenty of interesting BUG:s in dmesg. maybe i should go about repartitioning for a test partition
[10:44] <_4strO> yop yop
[04:31] <afflux_> my cryptsetup is working, but kindof buggy. It wait's a long time after I give the password and then says "Rendezvous with udev timed out for 'temporary-cryptsetup-4589'; stat failed: No such file or directory". After that it maps the volume directly, but this is far too long for booting ;)
[04:31] <afflux_> s/wait's/waits/
[04:34] <afflux_> (it waits about three minutes)
[04:57] <edgy> Hi, when I run: sudo debootstrap --variant=buildd  gutsy /var/chroot/ http://archive.ubuntu.com/ubuntu/, I got
[04:57] <edgy> W: Failure trying to run: chroot /var/chroot mount -t proc proc /proc
[04:57] <edgy> am I doing something wrong?
[04:59] <edgy> debootstrap = 0.3.3.3ubuntu4
[05:00] <Hobbsee> i think it's known about
[05:00] <Hobbsee> others were getting it earlier
[05:00] <edgy> $ sudo chroot /var/chroot/
[05:00] <edgy> chroot: cannot run command `/bin/bash': No such file or directory
[05:00] <afflux_> 4
[05:00] <afflux_> oh, sry
[05:01] <edgy> so how come people here manage to install gusty in chroot?
[05:02] <edgy> Hobbsee: have you manage to install gutsy in chroot yourself?
[05:03] <Hobbsee> so, yes
[05:05] <edgy> Hobbsee: is using pbuilder better than this normal way of chroot? I have never tried pbuilder before
[05:05] <Hobbsee> depends what you want to do with it
[05:07] <edgy> Hobbsee: I want to try a gutsy system while it's in development
[05:10] <edgy> Also, I have core 2 duo system, isn't this a 64-bit system? which kernel is best installed?
[05:10] <edgy> amd64?
[05:13] <Toma-> flip a coin and decide
[05:13] <Hobbsee> you could stick it on another partition, too
[05:13] <Hobbsee> you usually want -generic regardless
[05:13] <Hobbsee> iirc
[05:29] <edgy> Hobbsee: i installed generic but the libs installed are 32-bits this is why I wonder!
[05:42] <julo> hi
[05:43] <julo> GNOME's keyring seems to be broken in gutsy. Is it a known bug ?
[05:45] <Hobbsee> julo: have you checked in the bugtracker for it?
[05:50] <julo> Hobbsee: yes, but I don't see anything that looks like my bug
[05:50] <julo> Hobbsee: I just find it strange that nobody noticed it, given that the keyring is used about everywhere in GNOME...
[05:51] <Hobbsee> no idea how many people are actually running gutsy yet, either
[05:51] <Hobbsee> but it'd be a bit strange
[05:52] <crdlb> julo, in what way is it broken?
[05:54] <julo> crdlb: every time I try to open a network server, it tells me that there is no default session, and that I should specify a password for the session. Then, the next time I open a network server, I get the same dialog. And when I restart my GNOME session, all my passwords are lost.
[05:54] <julo> crdlb: it seems that it simply can't create keyring sessions.
[05:55] <crdlb> hmm I'm running gnome 2.19 on my gentoo box
[05:55] <crdlb> and seeing the same problem
[05:55] <julo> crdlb: so I guess it's a bug in GNOME, not in Ubunut.
[05:56] <crdlb> at this point, it's kind of normal :)
[05:56] <Toma-> Id love to see the samba interface actually become useable
[05:57] <julo> crdlb: is there a bug report about it, or should I report one ?
[05:57] <crdlb> I haven't checked to be honest
[05:57] <crdlb> you should probably file it in launchpad
[05:58] <Hobbsee> if it's in gnome, you should file it in the gnome bugzilla
[05:58] <Hobbsee> not ubuntu, as they wont fix it.  they'll just refile it
[05:58] <julo> crdlb: I think it's better to report it in bugzilla.gnome.org.
[05:58] <crdlb> nm then :)
[05:58] <julo> crdlb: and that's what I'm gona do.
[06:09] <edgy> Hobbsee: W: Failure trying to run: chroot /var/cache/pbuilder/build/23153/. mount -t proc proc /proc
[06:09] <edgy> pbuilder: debootstrap failed
[06:10] <edgy> Hobbsee: so pbuilder fails for me too, what shall i do?
[06:10] <Hobbsee> wait
[06:10] <Hobbsee> until it's fixe
[06:10] <Hobbsee> d
[06:10] <Hobbsee> is usually the best strategy
[06:10] <Hobbsee> and file a bug, if there's not already one
[06:11] <Hobbsee> seems odd that there's not an error before that, though
[06:11] <Toma-> you did use sudo in there right?
[06:12] <Toma-> and you need to bind proc... "sudo mount -t proc -o bind oldproc newproc"
[06:19] <edgy> Toma-: yes I did used sudo pbuilder create but I didn't sudo mount -t proc, let me try it
[06:20] <Toma-> -o bind
[06:20] <edgy> Toma-: what shall put in place of oldproc and newproc?
[06:21] <Toma->  /proc /path/to/chroot/proc
[06:23] <edgy> Toma-: I am following this: https://wiki.ubuntu.com/PbuilderHowto and it never mentioned where is the chroot is and I am just executing the first command of sudo pbuilder create
[06:29] <edgy> Toma-: am I asking a stupid question?
[06:30] <Toma-> edgy: looks like pbuilder is indeed broken. you can fix it if you like? :D
[06:30] <edgy> Toma-: i prefer to let the developers fix it so it would be a training session for them. I won't be available to help all the time ;)
[06:31] <Toma-> edgy: failing that, you could install gutsy with qemu to a virtual harddrive, mount it in ubuntu, then transfer the files to a folder, then chroot into it?
[06:32] <edgy> Toma-: how can I install it using qemu? it has no iso yet
[06:32] <Toma-> or simply keep it in a virtual drive and mount -o loop into it + chroot into that, leaving you with a stable snapshot
[06:32] <Toma-> edgy: feisty minimal then update
[06:33] <edgy> Toma-: thanks for the idea
[06:33] <Toma-> no problem
[06:33] <Toma-> Personally, i prefer the whole virtual harddrive thing, as its so easy to maintain
[06:35] <edgy> Toma-: can I mount -o loop an image installed via qemu? I am getting this: mount: you must specify the filesystem type
[06:35] <Toma-> no, make a harddrive/filesystem first then install into that, then mount it. dont use a qemu drive
[06:36] <Toma-> sudo dd if=/dev/zero of=gutsy.ext2 bs=1M count=2147 (for a 2GB drive)
[06:36] <Toma-> count = size in MB's
[06:37] <Toma-> then sudo mkfs.ext3 gutsy.ext3
[06:37] <Toma-> err
[06:37] <Toma-> 2
[06:37] <Toma-> you get the idea
[06:40] <edgy> Toma-: ok. thx
[06:40] <Toma-> no problem
[07:55] <fdoving> i have this issue with the latest gutsy kernel, my trackpoint stops working.
[07:56] <fdoving> anyone else experiencing that?
[07:57] <easytiger> anyone get vmware server 1.0.3 to work on ubuntu 7.10?
[08:39] <Chetwin> Hi all.  I was just read that shuttleworth is pulling out all non-free additions in gutsy.  No more auto installs for wireless drivers and video?
[08:39] <pwnguin> Chetwin: i havent seen this; perhaps he means a seperate distro?
[08:40] <pwnguin> Chetwin: url?
[08:40] <Chetwin> http://www.builderau.com.au/news/soa/Ubuntu-s-Gibbon-gets-free/0,339028227,339274828,00.htm
[08:40] <Chetwin> This worries me
[08:41] <pwnguin> i think the intention is to create an official distro, like kubuntu
[08:41] <Chetwin> Although, the nvidia-glx package that installs in feisty is a crap chute
[08:41] <pwnguin> i dont think it will directly impact Ubuntu
[08:41] <Chetwin> Locks up my system after a few hours
[08:41] <pwnguin> Chetwin: which nvidia card?
[08:41] <Chetwin> Well the auto notification and installation of my ipw3945 wireless drivers was a nice little gift when it first popped up
[08:42] <Chetwin> 7300 Go
[08:42] <Chetwin> It's not eleigible for legacy drivers
[08:42] <pwnguin> try nvidia-glx-new
[08:42] <pwnguin> nvidia's habit of dropping support is unfortunate for users currently
[08:42] <Chetwin> Bah, I just installed the binary from the nvidia site with --no-precomiled-interface option
[08:42] <pwnguin> well, as long as it works better for you
[08:42] <Chetwin> It seems to be fine, but time will tell
[08:43] <pwnguin> the nvidia-glx-new should carry some security fixes etc
[08:43] <Chetwin> I'm not very confident.  Hopeful is a better explination
[08:43] <pwnguin> Chetwin: try reading his actual email
[08:43] <Chetwin> It was strange because it would only happen when I was listening to music, made no sense
[08:43] <pwnguin> http://lwn.net/Articles/230229/
[08:43] <pwnguin> oh
[08:43] <pwnguin> you meant nvidia
[08:44] <shatrat> Chetwin, were you listening to music using a player with an openGL visualization pretty thingy?
[08:44] <Chetwin> Nope
[08:44] <Chetwin> banshee
[08:44] <Chetwin> Or rythmbox
[08:44] <Chetwin> Or totem
[08:44] <Chetwin> Doesn't matter
[08:44] <Chetwin> It just makes the HD race then lock up
[08:44] <shatrat> I blame sunspots
[08:44] <pwnguin> you sure it's nvidia causing this?
[08:45] <Chetwin> I switched back to the nv driver and had no problems
[08:45] <Chetwin> But I need 3d for my games
[08:45] <Chetwin> Odd to say about linux, but times are-a-changin *thank God*
[08:46] <cps1966> sure is better than vista ultimate
[08:46] <Chetwin> Sick
[08:46] <Chetwin> cps1966: I think I just threw up in my mouth
[08:47] <cps1966> well i had to try it on my old dually
[08:47] <cps1966> it'll never see this box
[08:47] <Chetwin> I admit, I fell victim to the vista hype for about 6 hours
[08:47] <pwnguin> if its any consolation the nvidia vista drivers suck too
[08:48] <Chetwin> Then I took my pill'buntu and was back in the game
[08:49] <Chetwin> If it's an consolation, Microsoft is still trying to pic lawsuits on other people for no reason lol
[08:49] <Chetwin> any*
[08:49] <cps1966> they are connered
[08:50] <cps1966> all m$ should be in jail
[08:50] <Chetwin> I don't think they have any room to point fingers.  We'd all be better off if they would just take a huge steaming dump inside all computers before they're shipped so we could smell it ahead of time
[08:51] <Chetwin> It would help the general public avoid all of the issues presented
[08:51] <cps1966> reboot to new kernel
[08:51] <Chetwin> *sarcasm* I'm very upset that I don't have to pay 30-90 bucks an hour for phone support on a product I paid 200+ for in the first place
[09:10] <Peaker> If I fix some packages on gutsy to work with each other, will package patches (to debian/* files) be accepted by Ubuntu?
[09:11] <Peaker> scipy isn't installable in gutsy - and I am trying to fix that
[09:25] <andreas23> hello
[09:26] <pwnguin> Peaker: ask in #ubuntu-motu; they'll tell you how to make sure it happens ^_^
[10:32] <Peaker> any estimates on the chances of beryl being enabled by default in gutsy? :)
[10:34] <crdlb> beryl, no
[10:34] <crdlb> compcomm, very possibly
[10:37] <Peaker> ah it was unforked, I forgot
[10:57] <cps1966> whats the name after gutsy
[11:00] <gnomefreak> cps1966: let us get gutsy done first
[11:00] <cps1966> well i want to know
[11:01] <gnomefreak> cps1966: it wont be picked until gutsy is about done
[11:01] <cps1966> i thought all were planned out to z
[11:02] <gnomefreak> no
[11:02] <gnomefreak> cps1966: mark picks them at end of each cycle
[11:02] <cps1966> hefty hog next
[11:03] <cps1966> if it has OO as office package
[11:04] <cps1966> OO should be an option
[11:05] <gnomefreak> cps1966: please talk about gutsy+1 somewhere else its offtopic for in here.
[11:08] <cps1966> oh gee i was just asking
[11:33] <sid> How is Gutsy.. is it functional.. ie gnome works etc?
[11:33] <cps1966> kde works
[11:34] <sid> cps1966: Does gutsty break often? ie, the system won't start every other week after an upgrade? Or is it "unstable" like debian sid is "unstable"?
[11:35] <cps1966> its not there yet
[11:35] <sid> Will an upgrade from edgy work.. or is it best to do a fresh format from a daily snapshot?
[11:35] <gnomefreak> sid: its not even been released to the public for testing
[11:36] <sid> gnomefreak: I know.
[11:36] <gnomefreak> there is no working ISO
[11:36] <cps1966> well i did upgrade only one glitch
[11:36] <sid> o, there are no dailys
[11:36] <gnomefreak> sid: so to ask does it break. yes it breaks
[11:36] <Pumpernickel> It'll break extremely often for awhile, still.
[11:40] <cps1966> gutsy is a safer bet
[11:41] <Pumpernickel> cps1966: errr... gutsy?
[11:41] <gnomefreak> cps1966: nothing is safe about gutsy
[11:41] <cps1966> ah its safe for me
[11:41] <crdlb> safer than what?
[11:41] <gnomefreak> what works for you doesnt mean it will work for everyone
[11:41] <cps1966> sid
[11:42] <gnomefreak> sid is much safer
[11:42] <cps1966> you can have it
[11:42] <gnomefreak> cps1966: i do i also have 2 gutsys 2 feistys a dapper + a bunch of chroots
[11:43] <sid> What is best to use, aptitude, apt-get, update-manager?
[11:43] <sid> I'm assuming update-manager.
[11:43] <Pumpernickel> Update-manager, usually.
[11:43] <crdlb> does update-manager work this early?
[11:43] <gnomefreak> sid: either way you will more than likely see breakage since the poppler merge is still kind of going on
[11:44] <gnomefreak> crdlb: yes and no. it will try to upgrade you but will more than likely fail unless michael has changed things for gutsy
[11:44] <sid> gnomefreak: I know, I expect breakage, I'll deal with the broken deps etc as they come.
[11:44] <gnomefreak> sid: do it using apt-get
[11:45] <sid> Need to get 347MB of archives.
[11:45] <sid> After unpacking 87.6MB of additional disk space will be used.
[11:45] <sid> gutsy is 87 megs larger than feisty. that's a lot
[11:45] <sid> (I have stock install)
[11:45] <gnomefreak> sid: that depends what you have installed
[11:46] <sid> only defaults
[11:46] <gnomefreak> that is not a accurate estimate
[11:46] <gnomefreak> if you have any other repo other than main than you are no longer default
[11:46] <gnomefreak> example feisty-updates repos
[12:15] <sid> so far no errors, everything is going smoothly.
[12:26] <RxDx> how can i chance my Feisty to get Gutsy unstable atualizations?
[12:27] <sid> RxDx: What is your goal?
[12:27] <RxDx> i want a very up to date system
[12:27] <gnomefreak> RxDx: stack with feisty for now
[12:27] <sid> RxDx: Edgy is a very up to date system. Gutsy is unstable and will likely break your system(often)
[12:27] <gnomefreak> sid: -edgy +feisty
[12:27] <sid> RxDx: And if you fix it, it will break again as updates flood into the repositories.
[12:27] <RxDx> ok.. thanks
[12:27] <RxDx> edgy is bugged.. feisty rullez ;)
[12:28] <sid> er
[12:28] <sid> s/Edgy/Feisty/
[12:28] <sid> RxDx: Is there a package Gutsy has that Feisty doesn't?
[12:28] <RxDx> i dont think.. but if theres i want to have it
[12:29] <gnomefreak> sid: not yet maybe 1 if you are lucky
[12:29] <tritium> RxDx: not necessarily.  There are some regressions.
[12:29] <RxDx> ahh.. thanks
[12:29] <gnomefreak> oh yeah the slow as crap gcc is in gutsy ;)
[12:29] <tritium> e.g., atherois AR5212 support in edgy works, but in feisty doesn't work on all hardware