[00:00] <x1250> I guess he should turn off compiz
[00:00] <DanaG> What was his issue?
[00:01] <bluesmoke> compiz-manager checks for software rendering
[00:02] <bluesmoke> He should make sure he isn't using software rendering
[00:02] <bluesmoke> He may have bad permissions on /dev/dri/cari0
[00:03] <bluesmoke> err, /dev/dri/card0
[00:03] <bluesmoke> x1250: the renderer string is more important, btw
[00:04] <bluesmoke> x1250: all open source drivers with or without software rendering will show Tungsten Graphics for the vendor, that's just mesa
[00:04] <bluesmoke> OpenGL renderer string: Mesa DRI Intel(R) 965GM GEM 20080716
[00:04] <bluesmoke> OpenGL renderer string: Software Rasterizer
[00:04] <bluesmoke> The first one is good, the second one is bad
[00:05] <x1250> uhm, I thought I showed Tungsten when hardware acceleration was working. Noted then. Thanks.
[00:05] <bluesmoke> I don't think so, I suppose I could be wrong
[00:06] <bluesmoke> either way the renderer string gives better information
[00:08] <x1250> DanaG, he had slow 3D performance with intel 82945G
[00:20] <Melik> anyone here use Deluge BitTorrent client?
[01:01] <CarlFK> I jsut did an update, and now my box thinks it is 2 timezones away
[01:02] <CarlFK> clock is off by 2.  and I don't see whre to set TZ
[01:02] <CarlFK> found it.  yeah, I thinks I am in LA
[01:02] <CarlFK> yuck
[01:04] <TeknoEee> hello
[01:22] <cwillu> so, my computer's been far too stable lately, I think it's about time to break things with an alpha
[01:23] <hggdh> go for it
[01:32] <TeknoEee> what is best way to file a bug report
[01:39] <hggdh> TeknoEee, see https://help.ubuntu.com/community/ReportingBugs
[01:40] <TeknoEee> okay
[01:40] <TeknoEee> well, I already used launchpad
[01:41] <TeknoEee> https://bugs.launchpad.net/ubuntu/+source/tint2/+bug/319436
[01:51]  * cwillu clicks upgrade
[01:52]  * nickrud crosses fingers for cwillu 
[01:52] <hggdh> TeknoEee, this was why you asked about the best way to report a bug?
[01:53] <cwillu> nickrud, gonna be a couple hours until it's finished downloading anyway :p
[01:53] <nickrud> cwillu, ah, then I'll uncross and go eat :)
[01:59] <maxb> I'm trying Jaunty on an Aspire One. I find that network manager can't see the wireless device with the Jaunty kernel. But it works if I boot the leftover Intrepid kernel. How do I figure out whether the kernel or networkmanager is at fault?
[02:06] <hggdh> maxb, see if the interface is up (ifconfig -a)
[02:09] <hggdh> maxb, then see https://wiki.ubuntu.com/KernelTeam/LinuxWireless; also try https://help.ubuntu.com/community/WifiDocs/WirelessCardsSupported
[02:15] <maxb> I got as far as "iwlist wlan0 scan" showing APs
[02:18] <EagleScreen> will Kubuntu 9.04 use packagekit by default? i can see kpackagekit in jaunty repository
[02:19] <tritium> EagleScreen: what do you mean "by default"?  Ubuntu uses .deb packages by default, and will continue to do so.
[02:21] <EagleScreen> tritium i mean kpackagekit in place of Adept, using packagekit-backend-apt
[02:22] <EagleScreen> and with packagekit installed by default in the system
[02:31] <cwillu> packagekit-backend-apt is in intrepid too
[02:32] <cwillu> EagleScreen, but it's in universe, so it won't be installed by default
[02:32] <EagleScreen> yes it is, but it is not installed be default, synaptic and update-manager are the default applications
[02:33] <cwillu> EagleScreen, it's still in universe in jaunty
[02:33] <cwillu> so it won't be installed by default
[02:33] <EagleScreen> wont installed in Kubuntu?
[02:33] <cwillu> I doubt they'll promote a package to main this late in the game
[02:34] <EagleScreen> as I read here: http://web.mornfall.net/adept.html Kubuntu will use it, but it does not say when, may be in Jaunty?
[02:37] <cwillu> EagleScreen, blueprint on launchpad mentioned intrepid, low priority
[02:37] <cwillu> seeing as packagekit itself is still in universe, I doubt anything further will happen for jaunty
[02:37] <cwillu> maybe 9.10
[02:38] <cwillu> https://bugs.launchpad.net/ubuntu/+bug/304464
[02:40] <EagleScreen> Adept3 is in beta4 stage, and the main developer has announced that he leaves the project, so Adept3 will may not finished never, then will Kubuntu Jaunty continue using a beta of Adept3? isn't it to change to kpackagekit as default package manager?
[02:49] <EagleScreen> incorrect working of kpackagekit/policykit-kde; i think there is a problem with one of them
[02:49] <cwillu> I'm not finding anything but rumours
[02:50] <cwillu> a brief conversation with the kpackage dev, saying he was busy with a new company or something
[02:50] <cwillu> and no blueprints, or activity on the bugs
[02:51] <EagleScreen> kpackagekit call policykit-kde to autenticate for installing packages, but kpackagekit gives you autentication error before you type password in policykit-kde dialog
[02:52] <cwillu> """ Make kdeadmin not depend on kpackage, it's in universe""" just happened last month
[02:52] <cwillu> doesn't feel like they're planning on a switch
[02:53] <cwillu> looks like it could be neat though
[02:54]  * cwillu mutters about ctrl+w in the wrong window...
[02:58] <EagleScreen> ScottK in #kubuntu-devel has told me that the plan it to switch to kpackagekit for kubuntu jaunty
[02:58] <cwillu> okay?
[03:00]  * cwillu hates it when somebody asks a question, you do research on the question, give a tentative answer, and then they accuse you of giving the wrong answer.
[03:00] <liquid> i would hate that too
[03:03]  * legodude__ likes ungrateful jerks
[03:06]  * cwillu huggles EagleScreen 
[03:07] <EagleScreen> what is the meaning of huggles?
[03:50] <cwillu> nickrud, done eating?
[03:52]  * cwillu starts to panic, his machine is applying changes, and nickrud is nowhere to be found!
[03:53] <gourgi1> http://pastebin.com/d22d44e9a      i;m trying to install 'tasque' but it needs to remove some packages   , can someone reproduce it before it as a bug ?
[03:53] <gourgi1> does it needs to remove packages to you too ?
[03:56] <gourgi1> anyone ?
[03:59] <raof> gourgi1: That's the gnome-sharp2 transition.  A bunch of packages just need to be rebuilt.
[04:00] <gourgi1> raof thanks for the info
[04:40]  * nickrud crosses toes as well, hopefully not too late
[04:42] <nickrud> cwillu, is it too late !?! Has your world ended?
[04:42] <cwillu> nickrud, it asked to replace a config file
[04:42] <nickrud> cwillu, do the diff !
[04:42] <cwillu> oooo, now it's downloading firmware :)
[04:42] <cwillu> maybe my broadcom will finally break!
[04:43] <cwillu> it's lasted through fiesty, gutsy and hardy upgrades without breaking :)
[04:43] <nickrud> that's just too good. Whenever I upgrade to a alpha there's been lingering problems.
[04:44] <cwillu> nickrud, you know, it needs to have an 'edit' option though, so often I have things I want from the old, and things from the new (/etc/bash.bashrc comes to mind)
[04:45] <nickrud> cwillu, not sure about update manager, but 'normally' you should be asked if you want the new maintainer's config or your own
[04:45] <cwillu> nickrud, and sometimes I don't want either, I want the maintainers config with the two lines I added
[04:46] <cwillu> as it stands, I have to save the diff and edit it again afterwards, which is annoying
[04:46] <nickrud> it would be nice. try rcs for /etc files, I used it for unstable and it worked nicely for that
[04:46] <nickrud> since I only change a couple things (apache mainly) I just back that up
[04:46] <cwillu> rcs == cvs's predecessor?
[04:48] <cwillu> I already use git + metastore :p
[04:48] <nickrud> cwillu, yes. haha. For the little I need in /etc anything else is overkill. svn for other stuff
[04:48] <cwillu> it'd still be nice if one didn't have to do something after the package manager finished
[04:49]  * cwillu snatches the svn out of nickrud's hands, throws it into the airlock, hits the release button, cringes for a moment, and then braces himself as the exploding svn rocks the ship
[04:49]  * cwillu unwraps a nice fresh git, and hands it to nickrud 
[04:49] <cwillu> my work here is done
[04:50]  * nickrud looks at the git, and screams 'I don't wanna learn nut'in! new!!!'
[04:58] <cwillu> nickrud, it's simple, really
[04:58] <cwillu> git init
[04:58] <nickrud> cwillu, I'm not doubting you - most tools are easy once you spend some time with them <-- note the word time :)
[04:59] <cwillu> git add *
[04:59] <cwillu> git commit -a
[04:59] <cwillu> I stopped trusting svn the second time I had a repository crash
[05:00] <nickrud> cwillu, then there's the admin stuff - at least a basic idea of how the data is stored, best practices to prevent corruption, etc. oooh, never had that happen. But I do have a strong backup regimen
[05:00] <cwillu> matchbox-window-manager is giving me lots of bad file descriptor errors :(
[05:01] <nickrud> cwillu, but one of these days I'll want something out of a git repo. That's the day I'll put in some time. To every purpose, there is a season :)
[05:01] <cwillu> :)
[05:02] <cwillu> me runs dpkg-reconfigure -a
[05:04] <cwillu> nickrud, well, when that day comes, feel free to give me a shout.  I feel it is my duty to get people switched away from crap :p
[05:05] <nickrud> :) I will definitely use your experience as a shortcut
[05:06] <cwillu> anyways, it appears I've got breakage to take care of :p
[05:09] <nickrud> oh the joy :) Have fun
[05:10]  * cwillu runs git revert
[05:23] <cwillu> disappointing, doesn't look like anything serious :(
[06:12] <Alexia_Death> cwillu: bughunting is adicting isnt it:D
[06:35]  * cwillu reboots
[06:36] <cwillu> oooo, wireless isn't broken!
[06:36] <cwillu> almost makes me sad
[06:37] <cwillu> oooo, my laptop's microphone even started working
[06:37] <cwillu> Alexia_Death, yes.  It's addicting, and I'm _not_ getting my fix from this
[06:37]  * cwillu starts shaking uncontrollably
[06:37] <cwillu> must. work around. bugs.
[06:38]  * nickrud points cwillu at BA
[06:38] <cwillu> ba?
[06:38] <nickrud> Bughunters Anonymous
[06:39] <cwillu> and my hotkeys are working
[06:40] <cwillu> and my sound is working
[06:41] <cwillu> hmm, window dragging issues
[06:41]  * cwillu cheers
[07:15] <syockit> biouser: welcome to jaunty!
[07:17] <biouser> indeed, I'm am usually pleasantly surprised after an upgrade.. this is my earliest but we'll see!
[07:18] <biouser> about time to help closer to the edge though I suppose
[07:19] <milos_> what would be the best way to upgrade network manager in hardy to 0.7 version?
[07:22] <biouser> so we get a 3.0+ ekiga?
[07:22] <biouser> milos_ don't know
[07:23] <biouser> milos_ I really enjoyed my upgrade to 8.10 so I've decided to go on to 9.04
[07:24] <syockit> You could enable repository temporarily, install just what you want, and disable it back
[07:24] <syockit> and endure any misconfigurations it might cause
[07:24] <milos_> biouser, the problem is I couldn't install 8.10 ver to that computer, because of some weird hdd bug.
[07:24] <milos_> syockit, what repository
[07:25] <syockit> jaunty
[07:25] <syockit> wait, it's not even on intrepid?
[07:25] <milos_> syockit, nope
[07:25] <milos_> syockit, hardy
[07:26] <milos_> syockit, intrepid can't be installed
[07:26] <syockit> milos_: yeah, anyways, maybe you can try what I said earlier. Assuming the disclaimer that came after that
[07:26] <syockit> milos_: no, just add the repository, install networkmanager, then remove the repository again
[07:27] <milos_> syockit, woudn't that screw everything? did you try that?
[07:27] <syockit> milos_: I don't know. Because I'm on jaunty, and everything's working here.
[07:27] <syockit> milos_: wait, you're on KDE 3 or 4?
[07:28] <milos_> syockit, gnome
[07:28] <syockit> milos_: sorry. I don't know about networkmanager for GNOME. I didn't know they had similar version
[07:29] <milos_> syockit, the thing is, computer isn't mine so I must be carefull to not screw anything
[07:29] <crdlb> syockit: the gnome frontend came first :)
[07:32] <syockit> milos_: The major changes that I can see to its dependencies are wpa-supplicant upgrade, and the introduction of update-notifier-common
[07:32] <crdlb> milos_: there's a network-manager PPA
[07:33] <crdlb> with some form of 0.7 for hardy
[07:33] <milos_> crdlb, where?
[07:33] <crdlb> 110% safer than that other route :)
[07:33] <milos_> crdlb, yeah I know :)
[07:33] <crdlb> https://launchpad.net/~network-manager/+archive
[07:34] <crdlb> make sure you get the hardy version
[07:34] <milos_> crdlb, thnx, this solved problem, sure.
[07:35] <syockit> How did you come here anyway...
[07:41] <biouser> someone psted the +1 in regular ubuntu and I guess the 3 of us joined through that
[07:42] <biouser> fethcing file 428... well, I will see yous guys in the morning....
[07:47] <syockit> biouser: opoo. I thought you've completed already
[07:59] <scizzo-> morning
[09:13] <hateball> Will OOo 3.1 make it into Jaunty?
[09:24] <scizzo-> hateball: find that hard to believe......if not openoffice gets released soon with the 3.1....but you never know
[09:25] <scizzo-> hateball: since they plan the 3.1 release in late march
[09:28] <cwillu> yay, bug #303011 bites me too!
[09:28] <cwillu> 2.6.27 works fine, rebooting into 2.6.28 kills performance (but glx is still accelerated, it's not rendering in software)
[09:30] <cwillu> http://bugs.freedesktop.org/show_bug.cgi?id=16835#c2
[09:30] <cwillu> _that_ pisses me off
[09:30] <cwillu> "The error message was cleaned up, but fixing the performance regression is out of scope for this release cycle"
[09:35] <hateball> scizzo-: when is jaunty freeze?
[09:36] <hateball> I mean.... 8.04 _was_ released with beta software...
[09:36] <hateball> OOo3.1 looks so nice, would be quite neat to see it go in :)
[09:38] <Unksi> hateball: that was because of hardy's long support cycle and that they didn't want to support firefox 2 for that long
[09:38] <Unksi> seeing that mozilla's own support for it ends before hardy's does
[09:39] <hateball> Unksi: Yeah I know... I'm just hoping :|
[09:39] <hateball> Speaking of hope... still hoping for a OOo3 backport to Hardy
[09:40] <cwillu> "    Now that we know that the bit 17 mode isn't just a mistake of older chipsets,
[09:40] <cwillu>     we'll need to work on a clever fix so that we can get the performance of
[09:40] <cwillu>     tiling on these chipsets, but that will require intrusive changes targeted
[09:40] <cwillu>     at the next kernel release, not this one. "
[09:41] <cwillu> what are the odds 2.6.28 will be rolled back? :(
[09:41] <cwillu> hateball, doesn't gooo already have most of the ooo3 goodness?
[09:43] <hateball> cwillu: Hardy doesnt use go-oo tho
[09:43] <cwillu> hateball, doesn't it?
[09:43] <cwillu> quaint that intel is gonna have issues until 2.6.29, due to a system that was intel's idea in the first place
[09:44] <syockit> cwillu: Usually how long does a kernel stay in RC?
[09:45] <hateball> cwillu: hmm, perhaps it does... apt-get show doesnt say so, but in intrepid it does. svg import does however work...
[09:45] <cwillu> syockit, kernel's are released every 3 months or so
[09:46] <cwillu> I'm not holding my breath for it landing in jaunty though, apparently the intel fixes required are to be quite invasive (and haven't been written yet)
[09:47] <cwillu> at best, it might be possible to compile 2.6.28 without gem support
[09:47] <syockit> cwillu: then can forget the rollback?
[09:48] <cwillu> maybe
[09:48] <cwillu> don't know how it affects the rest of the video drivers though
[09:52] <cwillu> hmm
[09:52] <cwillu> gem is disabled on pae
[09:52] <cwillu> pae is enabled on -server
[09:52]  * cwillu installs -server
[09:52] <syockit> cwillu: wait, that bug report says 2.6.26
[09:52] <cwillu> which?
[09:53] <syockit> freedesktop
[09:53] <cwillu> it's from dec2008
[09:53] <syockit> Is it possible it's fixed in 27, and broken again
[09:54] <cwillu> no, gem didn't land until .28
[09:54] <cwillu> he was probably using a dev tree
[09:54] <cwillu> or a simple typo on his part
[09:55] <cwillu> nope, 2.6.26, but it's a user compiled kernel
[09:55] <syockit> cwillu: strange that I'm not feeling any sluggishness on my part. Same graphic controller though
[09:56] <cwillu> syockit, 945?
[09:56] <cwillu> on 2.6.28?
[09:56] <syockit> yup. I'm on jaunty
[09:56] <cwillu> pastebin your xorg.0.log?
[09:56] <cwillu> and you're on compiz, right?
[09:57] <cwillu> (scrolling performance is fine, it's transparency that kills)
[09:57] <BUGabundo> good morning everyone!
[09:57]  * cwillu pokes BUGabundo with bug 303011
[09:58] <syockit> cwillu: Now that you mention it, it does feel slow. Not sluggish though. http://paste.ubuntu.com/107668/
[09:58] <cwillu> syockit, do you have transparency on window move enabled?
[09:59] <syockit> yes
[09:59] <cwillu> syockit, make a big window, and drag it around
[10:00] <cwillu> syockit, granted that if you have a better cpu than mine, it might be merely 'sluggish', in which case, have a top open as well (shouldn't spike the cpu)
[10:00] <syockit> yes, it does feel a bit slow. Didn't compare to previous...
[10:00] <syockit> Have to install glxgears to confirm...
[10:00] <cwillu> reboot into 2.6.27 if you still have it, and check again
[10:00] <cwillu> (whenever, don't feel you have to do it now :p)
[10:01] <cwillu> syockit, hmm
[10:01] <cwillu> you actually have tiling enabled
[10:01] <syockit> I can't do that, dave. My touchscreen driver now depends on 28
[10:02]  * cwillu starts unhooking ominous looking cards from syockit 
[10:03] <syockit> no you won't. I'll turn you into a satellite if you continue that
[10:03] <cwillu> no, you'll turn my friend into a satellite, and then you'll start singing daisy
[10:03] <BUGabundo> cwillu: I have no intel.. but I can take a look!
[10:04] <BUGabundo> I just wished that jaunty, xorg, and nvidia would get their heads strait!
[10:04] <cwillu> BUGabundo, I'm checking a bunch of stuff right now, I'm just in need of commiseration, because there's a chance it simply won't be fixed before 2.6.29, and therefore 9.10
[10:04] <BUGabundo> I have nvidia enabled on xorg and still it won't start with prop driver :(
[10:04] <cwillu> syockit, you don't have the issue, tiling is enabled
[10:05] <cwillu> syockit, could you pastebin me xorg.conf, presuming you have one?
[10:05] <x1250> BUGabundo, are you using IgnoreABI ?
[10:05] <BUGabundo> cwillu: nice godaddy add page on the image link :\\
[10:05] <BUGabundo> x1250: yes!
[10:05] <BUGabundo> let me pastebin my xorg and logs
[10:05] <x1250> BUGabundo, what does Xorg.0.log say?
[10:06] <cwillu> BUGabundo, 'image link'?
[10:06] <Unggnu> hi all
[10:06] <BUGabundo> http://paste.ubuntu.com/107678/
[10:06] <BUGabundo> http://paste.ubuntu.com/107677/
[10:06] <Unggnu> Does the intel driver in Jaunty supports GEM and DRI2?
[10:06] <syockit> http://paste.ubuntu.com/107679/ all defaults dude
[10:06] <BUGabundo> cwillu: "Screenshot with fps marker, under compiz: http://oasis-games.com/~klange/wtf_intel251.png"
[10:07] <cwillu> BUGabundo, sorry, not my image :p
[10:07] <BUGabundo> eehe
[10:07] <cwillu> syockit, odd that you don't have it
[10:07] <BUGabundo> maybe we should edit it, to note that
[10:07] <cwillu> syockit, a couple memory locations are different on the pci line in the log file, but otherwise identical
[10:07] <cwillu> syockit, except that you don't have 3 tiling errors
[10:08] <syockit> and my glxgears ran at about 570 fps
[10:08] <cwillu> I already tried an empty xorg.conf
[10:08] <x1250> BUGabundo, you have two section Device in xorg.conf
[10:08] <BUGabundo> Sauerbraten is nice to play with but even with my nvidia 8400 its quite slow with some smoke and stuff on
[10:08] <x1250> check that
[10:08]  * BUGabundo retries glxgears
[10:09] <BUGabundo> x1250: do I? I have to stop being so tired!
[10:09] <BUGabundo> glxgears Xlib:  extension "GLX" missing on display ":0.0".Error: couldn't get an RGB, Double-buffered visual
[10:09] <x1250> BUGabundo, you're using nv driver :P
[10:09] <BUGabundo> this one is new
[10:09] <x1250> BUGabundo, fix your xorg.conf and restart x
[10:09] <x1250> it may work after that :D
[10:10] <BUGabundo> x1250: http://paste.ubuntu.com/107681/ Fixed thaks
[10:10] <BUGabundo> we really need a tool to parse it, and check for errors
[10:11] <BUGabundo> how is that tool that bryce and alberto were working on ?
[10:11] <syockit> cwillu: I remember tweaking some dri settings. I forgot the name of the app
[10:11] <robin0800> syockit: driconf I think
[10:12] <x1250> BUGabundo, ok, hope that works.
[10:12] <syockit> yeah that. Thanks robin0800
[10:12] <BUGabundo> am I the only one who thinks that the new system-log is prettier but less usable? no more dirs in it!
[10:12] <cwillu> what package is that in?
[10:12] <syockit> in driconf
[10:13]  * cwillu pokes syockit with a stick
[10:13] <cwillu> don't get smart with me ;p
[10:13] <x1250> BUGabundo, I think glxgears does not work with nv driver, which you're using now. I guess that xorg.conf double section device made you use nv instead
[10:13] <syockit> ouch
[10:13] <syockit> You don't have it?
[10:13] <cwillu> installing it now
[10:14]  * cwillu wonders out loud if driconf leaves any log files lying around
[10:14] <cwillu> syockit, can you read off your current settings?
[10:14] <cwillu> (re: driconf)
[10:15] <x1250> cwillu, IIRC it does it does leave a . file
[10:15] <cwillu> or pastebin the file?_:p
[10:15] <cwillu> ~/.drirc
[10:15] <x1250> cwillu, yep thats it
[10:16]  * BUGabundo tries this so much fuss about app: driconf
[10:16] <syockit> cwillu: http://paste.ubuntu.com/107684/ for l33tness
[10:16] <BUGabundo> XDriInfo returned with non-zero exit code.
[10:16] <BUGabundo> $ driconf
[10:16] <BUGabundo> libGL is too old.
[10:16] <BUGabundo> ROFL
[10:17] <cwillu> syockit, not sure how it would be affecting xorg's startup though
[10:17] <robin0800> BUGabundo: driconf is old also
[10:18] <cwillu> thanks
[10:18] <cwillu> just rebooting into the server kernel, and then I'll try that file
[10:19] <BUGabundo> ahh thanks robin0800.... --purging it
[10:21] <cwillu> syockit, -server kernel works
[10:21] <x1250> BUGabundo, driconf did work here when I tested it some weeks ago, maybe nv's driver fault?
[10:22] <syockit> cwillu: that was a quick reboot
[10:22] <BUGabundo> lol
[10:22] <BUGabundo> its every thing fault of both NV and NVIDIA driver
[10:22] <cwillu> syockit, other machine
[10:22] <BUGabundo> lol
[10:22] <cwillu> was already at grub :p
[10:22] <BUGabundo> suspend/hibernate are broke again too...
[10:22] <BUGabundo> heheh
[10:24] <x1250> BUGabundo, did the new xorg.conf work?
[10:25] <BUGabundo> I haven't relogin yet, x1250
[10:25] <cwillu> syockit, could I get you to post your xorg.conf, xorg.0.log and lspci to that bug report, with the statement that yours works?
[10:26] <syockit> Sure, fire it away
[10:26] <cwillu> https://bugs.launchpad.net/ubuntu/+bug/303011
[10:26] <x1250> BUGabundo, ahh, I don't see part/join/quit messages :)
[10:26] <syockit> Cute bot
[10:26] <syockit> Going to subscribe it
[10:27] <cwillu> syockit, do you have libdrm-intel1 installed?
[10:27] <BUGabundo> guys relax a bit and enjoy http://caoepulgas.blogspot.com/2009/01/nine-words-women-use.html
[10:27] <syockit> cwillu: yup
[10:29] <x1250> BUGabundo, haha, true.
[10:30] <cwillu> syockit, what does ls -l /dev/dri say?
[10:30] <syockit> crw-rw----+ 1 root root 226, 0 2009-01-21 07:12 card0
[10:31] <cwillu> wanna break something? :p
[10:31] <cwillu> actually, nevermind
[10:31] <cwillu> that's not it
[10:32] <cwillu> syockit, yours just works for no good reason :p
[10:34] <x1250> I think that should be chmod to 0666
[10:34] <x1250> card0
[10:34] <cwillu> it should, but it doesn't break this
[10:34] <cwillu> syockit, your sluggishness is probably from that
[10:34] <cwillu> maybe
[10:35] <BUGabundo> http://mail.google.com/videochat Gmail voice and video chat is not yet available for Linux. BAHH
[10:35] <x1250> syockit, could you please pastebin: $ LIBGL_DEBUG=verbose glxinfo
[10:36] <rconan> does ubuntu jaunty support multiple GPUs using XRandR?
[10:36] <BUGabundo> x1250: http://paste.ubuntu.com/107692/ I get a coredump
[10:36] <cwillu> rconan, I don't _think_ so
[10:36] <BUGabundo> I guess its NV fault again?
[10:36] <syockit> http://paste.ubuntu.com/107693/
[10:36] <rconan> cwillu, does jaunty have xserver 1.6?
[10:36] <cwillu> rconan, I briefly played with multiple radeon 9250's (had a 6 headed desktop a long time ago)
[10:37] <syockit> x1250: sorry, http://paste.ubuntu.com/107693/
[10:37] <cwillu> yes
[10:37] <BUGabundo> rconan: I think so
[10:37] <BUGabundo> if not, its quite almost there
[10:37] <syockit> rconan: beta i think
[10:37] <rconan> xserver 1.6 is released I believe
[10:37] <rconan> and I _think_ it has XRandR 1.3 in
[10:37] <rconan> which supposedly should support multiple GPUs
[10:38] <rconan> but I'm a little uncertain on all the issues
[10:38] <x1250> syockit, that looks fine to me.
[10:38] <syockit> as you can see, jaunty's got version 1.5.99 for its xserver
[10:38] <bullgard4> Is there a file /etc/default/acpi-support in Jaunty and a file /etc/init.d/acpi-support as well?
[10:39] <syockit> bullgard4: it's here. Maybe came with acpi packages...
[10:39] <rconan> I would imagine then that the plan is to upgrade to 1.6 fairly soon
[10:40] <BUGabundo> !apt-cache policy xorg
[10:40] <bullgard4> syockit: Thank you very much for your information.
[10:42] <syockit> Good, else I'd called upon a Butlerian Jihad
[10:43] <syockit> rconan: I'd say it's pretty much there already
[10:43] <syockit> having .99 version usually means that
[10:44] <cwillu> syockit, I suppose I should stop spamming that bug report
[10:44] <rconan> i just realised it's missed its scheduled release date so 1.6 doesn't actually exist yet
[10:45] <rconan> very much looking forward to XRandR and therefore compiz on my desktop
[10:46] <syockit> !wfm
[10:46] <syockit> Hmm, the message changed slightly, if my memory serves me right
[10:48] <cwillu> syockit, thanks for your help
[10:49] <cwillu> syockit, I think the permissions you posted might be related (alot of people didn't get any intel love at all until they fixed it to 666, specifically _due_ to gem not being enabled when set to 660
[10:52] <x1250> BUGabundo, I guess no dri or glx stuff will work with that driver. (I'm talking about http://paste.ubuntu.com/107692/)
[10:53] <syockit> wow at the blazing 1000fps Belisarivs claims on opensuse
[11:03] <d-b-a> hi i did an update manager -d and its stuck on the last package
[11:04] <d-b-a> any ideas?
[11:04] <d-b-a>  /iproute_20080725-2_i386.deb
[11:05] <d-b-a> is this to be expected / is my mirror b0rked
[11:06] <cwillu> d-b-a, apt-get update and upgrade
[11:06] <d-b-a> do it manually ?
[11:06] <cwillu> you're new to this whole 'alpha' thing, aren't you :p
[11:06] <d-b-a> no
[11:07] <d-b-a> i thought that it was prefered to use update-manager -d
[11:07] <d-b-a> that's why i did that
[11:07] <cwillu> could probably do it through that too
[11:07] <cwillu> check and install
[11:07] <cwillu> same thing basically
[11:07] <d-b-a> ah ?
[11:07] <d-b-a> wait did you tell me to use apt ?
[11:07] <cwillu> update manager's check = apt-get update
[11:07] <d-b-a> rofl
[11:08] <hggdh|away> not for -d
[11:08] <d-b-a> sorrry but ... doesn't debian recommend aptitude over apt-get these days ... just out of interest why apt-get -> your personal perference (yes i know ubuntu is not debian)
[11:08] <d-b-a> cwillu: for -d it checks for the devel version / next right ? -> dist-upgrade
[11:09] <syockit> Because some aptitude problem with dpkg package states makes apt more viable
[11:09] <d-b-a> you can't expect to upgrade
[11:09] <cwillu> d-b-a, if you've already started the upgrade to jaunty, the -d does nothing further:  you're already on the jaunty repos
[11:09] <d-b-a> ah ?  mmm i thought it was tweaked to do some extra stuff
[11:09] <d-b-a> ok ^^
[11:10] <d-b-a> what kernel is jaunty on atm
[11:10] <cwillu> apt-get doesn't do anything fancy, so if something is gonna cause problems, it'll just throw up its hands and leave me to fix things right :p
[11:10] <d-b-a>  and is it frozen
[11:10] <x1250> d-b-a, update-manager does some other things, like disable drivers that are known not to work, add your user to new groups if necessary, use dpkg force option by default, etc. You can do it by hand, but there are some quirks update-manager takes care about, thats why is the recommended method.
[11:10] <cwillu> 2.6.29-4
[11:10] <cwillu> 28, rather
[11:10] <cwillu> x1250, noting that that all happens regardless of the -d
[11:10] <d-b-a> so its not the 29 ?
[11:11] <cwillu> no
[11:11] <x1250> cwillu, yeah I was refering to -d
[11:12] <x1250> d-b-a, yes, aptitude is prefered over apt-get
[11:12] <d-b-a> ok i will read up later thank you ^^
[11:15] <x1250> cwillu, there are somethings update-manager only does when upgrading to a new ubuntu version. There are some quirks it takes care of from hardy -> intrepid, intrepid -> jaunty, etc.
[11:16] <kevku> why is ipv6 missing in 2.6.28-4
[11:16] <maxb> It would be really interesting if the specifics of update-managers's quirks were written down somewhere
[11:17] <mvo> maxb: its in update-managers source :) DistUpgrade/DistUpgradeQuirks.py
[11:17] <maxb> Well... yeah, fine :-)
[11:17] <syockit> How did you know it's called quirks?
[11:17] <mvo> it really depends on each distro release, the set is small (or at least we try keep it small)
[11:18] <maxb> It is common for adaptations for speciifc circumstances to be called quirks
[11:18] <cwillu> x1250, yes, but once you're on jaunty's repos, those happen automatically
[11:18] <cwillu> x1250, don't worry, I've already checked the sourcecode in question :p
[11:18] <maxb> For example, special behaviours needed for particular hardware at suspend|resume time are also called quirks
[11:18] <x1250> cwillu, heh :)
[11:19] <cwillu> x1250, until jaunty is released, it knows its in dev mode
[11:19] <cwillu> /usr/lib/python2.5/site-packages/UpdateManager/Core/MetaRelease.py has the -d logic in question :p
[11:20] <mvo> out of curiosity, are you hunting a specific bug? or is it just interesst in how u-m works ?
[11:21] <cwillu> mvo, thought I'd get your attention ;p
[11:21] <cwillu> no, just poking around
[11:21] <mvo> heh :)
[11:21] <cwillu> haven't had any upgrade bugs this time around :p
[11:21]  * cwillu stills has mvo's name on a post it note on his wall :p
[11:22] <mvo> weeeeh - I hope that is not the wall where the dartboard is located ;)
[11:23] <cwillu> hardly
[11:23] <cwillu> although, it _is_ a corkboard
[11:23]  * cwillu wonders what his landlord would say to a wall peppered with dart holes
[11:26] <cwillu> why would suspend/hibernate not work from the shutdown menu (they do nothing at all), but pm-suspend/hibernate works fine from the terminal?
[11:27] <maxb> IIUC, the first signals gnome-power-manager, the second can trigger the suspend by a variety of different backends
[11:28] <cwillu> gnome-power manager seems to be working otherwise
[11:28] <cwillu> but yep, its suspend menu item does nothing either
[11:29] <cwillu> gnome-power-cmd.sh suspend gives: method return sender=:1.32 -> dest=1.112 reply_serial=2
[11:29] <cwillu> and nothing
[11:30] <cwillu> gconf-editor crashes consistently looking at related keys
[11:35] <syockit> cwillu: just how many things did you manage to break ;)
[11:35] <syockit> otoh, my kubuntu has only minor glitches
[11:36] <cwillu> suspend works, I just have to trigger it from the console :p
[11:38] <kevku> modprobe ipv6
[11:38] <kevku> FATAL: Module ipv6 not found.
[11:38] <kevku> 2.6.28-4-generic #11-Ubuntu
[11:38] <syockit> meanwhile, I'm still banging my head over the qt-gtk thing that causes those ugly radio buttons on firefox
[11:39] <kevku> syockit: use some nice firefox theme or opera.
[11:45] <syockit> kevku: Oh, I forgot opera. Maybe I should consider it again....
[11:45] <syockit> Now why did I stop using it....
[11:45] <kevku> well it uses qt. fits into kde.
[11:48] <syockit> I remember now: (Windows) Firefox->Opera->Google Chrome->(Kubuntu)Midori->Epiphany->Firefox-3->Firefox 3.1 and stuck
[11:49] <syockit> heck, they even have deb repo. Should try it right awayyyy
[11:53] <cwillu> **_(gnome-power-manager:10943): WARNING **: Suspend failed without error message
[12:09] <syockit> oh wow, Opera 10! Presto 2.2! let's go straight to acid3.acidtests.org
[12:10] <syockit> w00t, 100/100!
[12:12] <syockit> kevku: Thanks for reminding me of opera again
[12:50] <Guest55353> hello all
[12:50] <Guest55353> where I can find the ubuntu 9.04 changes?
[12:52] <Guest55353> what are being made by Canonical??? Someone?
[12:56] <Guest55353> Every time that I use TOTEM, it don't remember the position that I want it to open. It is a bug?
[12:58] <Guest55353> hello
[13:06] <Guest55353> so Canonical just wait the Debian's guys make the pakages???
[13:08] <elkbuntu> no.
[13:08] <Guest55353> wow
[13:08] <Guest55353> thaks for the answer
[13:09] <Guest55353> I'm trying to discover what Canonical made or contributed to linux world. Do you know where I can find?
[13:10] <elkbuntu> Guest55353, i have not the time to recite the history of the past 4 years.
[13:12] <Guest55353> someting to improve dpkg? or I don't know, something usefull?
[13:14] <Guest55353> Everyone say that the canonical don't help linux
[13:14] <Guest55353> I want to have something to say for that people
[13:15] <elkbuntu> http://en.wikipedia.org/wiki/Ubuntu
[13:15] <Guest55353> entering....
[13:15] <elkbuntu> Guest55353, remember also that some people dont see non-code contributions as contributions. those people are very wrong.
[13:18] <scizzo-> Guest55353: everything depends on how you look at it
[13:19] <scizzo-> Guest55353: ubuntu helps debian development and debian helps with ubuntu development
[13:20] <scizzo-> Guest55353: also there is information in the topic of this channel that gives you links to places to see changes and development of jaunty......you can also look at www.ubuntu.com/testing for information about what is going on and the releases
[13:35] <shadowhywind> hay all running into a bit of a problem. When i try to login, I only get a failsafe session (unless i killall kdm, and then startx)
[15:15] <BUGabundo1> x1250: FYI its working
[15:15] <BUGabundo1> thanks
[15:15] <BUGabundo1> now I only need to backup everyting and format to ext4 and clean install
[15:16] <x1250> BUGabundo1, good to know
[15:29] <d-b-a> hi   how does one disable the guest user neatly   ?
[15:29] <BUGabundo1> good question
[15:30] <BUGabundo1> I would like to know too..
[15:30] <d-b-a> wtf ? there is no guest entry in /etc/passwd
[15:32] <d-b-a> and dear god no -> recommends on by default sucks i install kde and it wants a mysql server
[15:32] <tritium> d-b-a: that's because it's only a guest session, not an actual account.  You won't find a /home/guest directory either.
[15:32] <d-b-a> tritium: how to disable said user then
[15:32] <d-b-a> this seems insecure to me
[15:33] <BUGabundo1> d-b-a: its quite secure! it can't write anywhere
[15:33] <d-b-a>  not even in /tmp
[15:33] <d-b-a> ?
[15:33] <BUGabundo1> other then the desktop, and the account is cleared after terminated
[15:33] <BUGabundo1> no even /tmp
[15:34] <d-b-a> ok so where in the world is the documentation on this ?
[15:34] <d-b-a> and why not entry in /etc/passwd
[15:34] <d-b-a> no*
[15:34] <tritium> Because it's not a user account.
[15:34] <tritium> It's a guest *session*
[15:34] <BUGabundo1> d-b-a: its just a new X
[15:35] <d-b-a> what ?
[15:35] <d-b-a> so what i'm root ?
[15:35] <tritium> root account is locked by default
[15:36] <BUGabundo1> yep
[15:36] <d-b-a> well what does it run as ?
[15:36] <d-b-a> x runs as root
[15:36] <d-b-a> no..
[15:37] <dholbach> hiya
[15:37] <dholbach> https://wiki.ubuntu.com/UbuntuDeveloperWeek Day 3 to kick off in #ubuntu-classroom in 23 minutes! :-)
[15:37] <BUGabundo1> d-b-a: X runs with users that have permission to launch it, from a console
[15:37] <BUGabundo1> dholbach: what are the themes today?
[15:38] <dholbach> BUGabundo1: great ones - today is going to kick ass
[15:38] <dholbach> just check the link I posted
[15:38] <d-b-a> um...
[15:38] <BUGabundo1> following
[15:38] <d-b-a> problem.
[15:38] <d-b-a> id guest
[15:39] <d-b-a> uid=114(guest) gid=126(guest) groups=126(guest)
[15:39] <d-b-a> it exits
[15:39] <d-b-a> ah i see sorry
[15:39] <d-b-a> its made on the fly
[15:39] <d-b-a> neat.
[15:40] <d-b-a> so to disable just add a user called guest that cannot login right ?
[15:40] <BUGabundo1> okay just found a new bug with gnome-power-manager!
[15:42] <BUGabundo1> setting the bright to 100%, won't use the real 100% bu only 50% using the keyboard I can get it correcly
[15:48] <d-b-a> btw what is the new bug reporting system like how to test this ?
[18:17] <avis> anyone have issues with 32 bit jaunty locking up with a p43 chipset motherboard ?
[18:19] <avis> also, i cannot get output to a ALC888 sound chipset.  i'm not sure, if its because i have two sound controllers on my computer, even when i switch the output to ALC888, no sound from that device.  i realize these types of things are likely common,  i just though i'd ask in the event some of you might know of potential solutions
[18:28] <marijus> anyone got kernel 2.6.29 and kms to work yet?
[18:32] <x1250> marijus, nope, jaunty still has .28
[18:32] <solarion> is parasite going to be in jaunty?
[18:32] <ddeath> I have installed Ubuntu 9.04 on the VirtualBox, so I can't be good tester
[18:33] <ddeath> Is the way to install VirtualBox driver for X Window System?
[18:33] <marijus> i know... will probably also stay on .28
[18:34] <x1250> solarion, if there is request for parasite in launchpad, I doubt it.
[18:34] <solarion> x1250: I don't get the comment
[18:34] <x1250> if there is not, sorry
[18:35] <solarion> ah, that makes more sense
[18:49] <biouser> alright, rebooting into 9.04!
[18:49] <biouser> hopefully I will be back in a minute
[18:50] <mnemo> can someone please run this command on ubuntu and see if it works for you:
[18:50] <mnemo> gksu --desktop /usr/share/applications/software-properties.desktop /usr/bin/software-properties-gtk
[18:50] <mnemo> it's the command for opening the "System::Administration::Software Sources"
[18:50] <pwnguin> anyone know what model laptop mark shuttleworth uses?
[18:51] <pwnguin> im tired of acpi breaking because nobody cares about my model =(
[18:51] <x1250> haha
[18:51] <genii> Probably an eeepc
[18:51] <pwnguin> seriously, someone decided to rewrite the toshiba kernel stuff
[18:52] <pwnguin> but i havent seen shit about it on the ubuntu mailing lists
[18:52] <pwnguin> meanwhile, #ubuntu-laptop might as well be dead =(
[19:26] <biouser> hi, just upgraded to 9.04, I have some problems with my ATI graphics card now.  Can I change from the fglrx (I think that is what I have installed) to the open source drivers (I think that I am set to proprietary now)  thanks
[19:27] <biouser> "no proprietary drivers are in use on this system"
[19:28] <biouser> what is the package that will uninstall fglrx for now and use what ubuntu ships with?
[19:36] <TheInfinity> biouser: just uninstall fglrx package
[19:36] <biouser> okay, will try thanks TheInfinity
[19:37] <TheInfinity> biouser: you can also just modify your xorg.conf file
[19:38] <biouser> right, I might try to go into that.  I don't really care about graphics that much but I was forced into low-resolution mode here.  I will look into it...
[19:38] <biouser> I got this ATI card a few years ago before I knew to go for the most linux-compatible hardware
[20:20] <nunu> hi all, is it possible to mount ext4 partition with jaunty ?
[20:21] <nunu> +s
[20:21] <fosco_> yes
[20:21] <nunu> cool =)
[20:21] <nunu> thx
[20:22] <fosco_>  /dev/sda3 on / type ext4 (rw,relatime,errors=remount-ro)
[20:27] <nippz> sigh
[20:27] <nippz> i dont suppose anyone has a cure for amarok/mysql 5.1 postinst problem by chance?
[20:42] <nippz> actually
[20:42] <nippz> yaknow what would be really nice?
[20:42] <nippz> say i did apt-get install <blah> ; and blah requires a b and c packages
[20:43] <nippz> if apt would use ALL the us mirrors, and prioritize by speeds, and then grab 3-4 packages per `repo` area [universe, main, etc]
[20:44] <mnemo> nippz: I think someone is working on an apt-torrent thing, heh
[20:45] <nippz> apt-torrent? that would be awesome - tho to make it better i would recommend prioritizing repo as first seed
[20:45] <nippz> basically a seed-insertion bit
[20:45] <nippz> mnemo ok i have a workaround for amarok+mysql-server-5.1 error
[20:45]  * genii ponders delta-apt-torrent
[20:46] <nippz> install mysql-server which pulls in latest 5.0 versions.. then download only the amarok package and dpkg -i --force-depends
[20:46] <nippz> no guarentees on stability tho ;P
[20:47] <biouser> ctrl-alt-backspace doesn't work for me now
[20:53] <mysteryc> Hey
[20:53] <mysteryc> Will ubuntu Jaunty Jackalope run the newest Linux kernel?
[20:54] <mnemo> mysteryc: right now there is a 2.6.28 kernel in jaunty and .29 is not released yet
[20:54] <mnemo> .29 will be released before jaunty is but near the jaunty release date kernel changes become very unlikely
[20:54] <mnemo> i dont know for sure, but I _guess_ that jaunty will ship with .28
[20:54] <mysteryc> Oh.
[20:55] <mysteryc> Wel that is pretty good, I've heard the letest update includes better wireless networking :)
[20:55] <biouser> pulse-audio visually monitors the sound I should be getting from the alsa-firefox plug bu tgives no sound until a garble at the end before Connection failed: Connection terminated
[20:55] <biouser> system>preferences>sound does not start
[20:56] <mysteryc> biouser: Shouldn't you be asking in #ubuntu ?
[20:56] <biouser> well this is only now after upgrading to jaunty... maybe there is a better place to post this...
[21:00] <CarlFK> https://help.ubuntu.com/community/ExpressCard  "sudo modprobe pciehp"  works on ibex, not on jaunty.  bug?
[21:00] <CarlFK> FATAL: Module pciehp not found.
[21:00] <apokalyp1> its probably not compiled by default
[21:01] <CarlFK> ah, here we go: [not amd64]
[21:03] <CarlFK> so what's the plan for express cards on a amd64 box?
[21:03] <user___> hi, i get a "package cache file is corrupted _cache->open failed" (upgrade manager). anything i can do to debug and provide a good report. otherwise i'll just restart update manager
[21:11] <biouser> apport and nautilus are both taking about 98% cpu in top
[21:12] <biouser> Could not upload report data to crash database:<urlopen error The write operation timed out>
[21:17] <mnemo> biouser: the fact that apport doesnt work on jaunty right now is a known bug. see this report: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/314212
[21:17] <biouser> thanks mnemo
[21:18] <Technoviking> is it a known problem that the install stops after installing packages, it never finishes the install
[21:22] <biouser> current dist not found in meta-release file <- problem?  running update-manager
[21:23] <cwillu> got the same thing here, give launchpad a check, it's probably known as well
[21:25] <cwillu> #310046
[21:25]  * cwillu pokes ubottu with a stick
[21:25] <cwillu> bug #310046
[21:25]  * cwillu debates poking mvo with a stick
[21:27] <mvo> biouser: no problem
[21:27]  * mvo needs to get rid of that message
[21:28] <cwillu> biouser, what happens when you run gksudo software-properties-gtk from a terminal?
[21:28] <biouser> /usr/lib/python2.5/site-packages/apt/__init__.py:19: FutureWarning: apt API not stable yet  warnings.warn("apt API not stable yet", FutureWarning) ;; reWarning: apt API not stable yet
[21:28] <biouser> but opens
[21:28] <cwillu> k
[21:29] <cwillu> mine dumps with an aptsources.distro.NoDistroTemplateException: Error: could not find a distribution template
[21:29] <mvo> software-propoerties-gtk is currently broken with the latest python-apt upload, I'm parparing a fix as we speak
[21:29] <mvo> should be available in ~1-2h
[21:29] <cwillu> k
[21:29]  * cwillu huggles mvo
[21:29]  * mvo jumps up and down
[21:30] <biouser> nothing is checked in ubuntu software and everything is checked in third party but I guess that is the expected behavior?
[21:30]  * cwillu jumps up and dwn as well, so as to keep the huggle alive
[21:30]  * biouser thanks god for people who contribute since he is still a relative newb
[21:32] <mvo> biouser: its a bug, but hopefull the next python-apt update fixes it
[21:42] <jimi_hendrix> hi i got a bug in the installer
[21:42] <jimi_hendrix> :-(
[21:42] <cwillu> !ask
[21:43] <jimi_hendrix> basically i finish the install options and it starts me over at step five (partitioner)
[21:43] <apokalyp1> har
[21:44] <jimi_hendrix> so any clue?
[21:44] <Technoviking> ack getting loud beeps at boot up, something about udev
[22:04] <Stargazer> I was wondering... what do the topic mean by "break your system" ?
[22:05] <raof> Stargazer: Pretty much anything, with varying degrees of likelyhood.
[22:05] <user___> Stargazer: data failure f.e.
[22:05] <Stargazer> Would it be safer to use in VBox ?
[22:05] <raof> Absolutely.
[22:05] <user___> +1
[22:06] <Stargazer> Ok.
[22:06] <raof> Actual physical harm is very unlikely, but possible (cf: Intel network cards getting bricked by the Intrepid kernel)
[22:06] <dtchen> for people running current jaunty who have not logged out and back in since the latest alsa-utils update, please try `alsamixer' in a Terminal/Konsole/$x-terminal-emulator_of_choice and tell me if you get an alsa-lib error
[22:07] <Stargazer> Raof, my laptop runs epic with Intrepid. it's all intel too.
[22:07] <dtchen> (press Esc or q to exit alsamixer)
[22:07] <apokalyp1> q raises volume
[22:08] <raof> Stargazer: Right.  But during the Intrepid devel cycle, a bug which caused (at least) intel network to be bricked under some not-too-uncommon circumstances was fixed.  This is the sort of problem that is more likely in the dev version.
[22:09] <dtchen> apokalyp1: it shouldn't exit in the repository version with q, correct
[22:09] <dtchen> (i have remapped a bunch of keys)
[22:10] <dtchen> anyhow, anyone getting errors with `alsamixer'?
[22:18] <maxb> Wow... the build-deps of gnome stuff really are quite weight
[22:18] <maxb> *weighty
[22:27] <Amaranth> maxb: I feel the same way when I get build-deps for KDE stuff :P
[22:28] <maxb> It would hurt less if half of it wasn't purely to build the docs
[22:45] <cwillu> Stargazer, but life is so much more fun when you're running alpha software on the bare metal :)
[22:45] <Stargazer> It's also fun to cram a sword through someone, too.
[22:46] <Stargazer> But, i don't have time for that.
[22:48] <cwillu> if something is fun enough, you _make_ the time
[22:52] <linuxman410> has anyone noticed that programs run better in 9.04
[22:52] <Stargazer> I like 8.04 to be honest.
[22:53] <Stargazer> Unless, of course, cross-environment programs run better in 9.04.
[22:53] <linuxman410> i have had less trouble out of 9.04 than i have any of them
[23:04] <jimi_hendrix> i have a problem with the installer...basically i finish the install options and it starts me over at step five (partitioner)
[23:07] <jimi_hendrix> so where can i get help/report this bug?
[23:07] <cwillu> launchpad
[23:16] <cwillu> :/
[23:16] <jimi_hendrix> and no clue how to fix it?
[23:16] <jimi_hendrix> (ubotu have a url)?
[23:16] <cwillu> gpm is sending the hal message to suspend, and complaining that it finished with no error (but didn't do anything), but pm-suspend works fine :/
[23:16] <cwillu> ubottu, is a bot
[23:17] <cwillu> !launchpad
[23:17] <hggdh> jimi_hendrix, see https://help.ubuntu.com/community/ReportingBugs
[23:18] <jimi_hendrix> thanks
[23:18] <jimi_hendrix> and what package is the installer?
[23:19] <hggdh> hum
[23:19] <hggdh> never used it, let me check
[23:20] <linuxman410> i am using old p4 socket 478 1.8 and ati radeon 9200se and 1 gig of ram old machine but runs 9.04 fine
[23:20] <cwillu> hmm, suspend via dbus-send works from the vterm with gdm shutdown
[23:20] <hggdh> jimi_hendrix, ubiquity (graphical)
[23:20] <jimi_hendrix> ok
[23:21] <jimi_hendrix> and should i use the normal ubuntu one or is there a specific jaunty one
[23:23] <jimi_hendrix> hggdh ^^
[23:25] <hggdh> jimi_hendrix, all you need is state this is on Jaunty
[23:25] <hggdh> and what level of Jaunty (Alpha3, daily from yyyy/mm/dd, etc
[23:25] <jimi_hendrix> ok
[23:25] <jimi_hendrix> uhh i dled yesterday i think alpha 3
[23:26] <hggdh> the ISO source file should state it
[23:26] <hggdh> in the name
[23:34] <jimi_hendrix> https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/319817
[23:36] <jimi_hendrix> any input?
[23:42] <cwillu> mvo, just got the python-apt update, software-sources is working again here