[12:50] <AnRkey> keram thanks it's working
[12:52] <DanaG> Hmm, trying to run WinXP with the VESA Bochs under KVM:  I get exception 14.
[01:57] <AnRkey> how do i get gutsy tribe 3 to go into x when it boots?
[01:57] <AnRkey> i have to startx when i login at the moment
[02:11] <XiXaQ> hey, the Windowlist in a vertcal panel shows windows horisontally! That's great, I've been longing for that for ages. However, to me it seems abit buggy?
[02:15] <jmg> hi all, i just upgraded to gutsy and didnt get compiz
[02:15] <jmg> how can i enable it?
[02:15] <crdlb> jmg, system>preferences>appearance>desktop effects
[02:17] <jmg> crdlb: says its enabled (button is down)
[02:18] <jmg> how can i debug whats happening? grep compiz in /var/log reveals nothing
[02:18] <jmg> oh
[02:18] <jmg> hehe
[02:18] <DanaG> Try .xsession-errors instead.
[02:48] <AnRkey> does anyone else's installation not go into gdm when it boots?
[02:49] <AnRkey> I can't get mine to go into gdm when it boots, can anyone help?
[02:52] <AnRkey> i have to use startx to go into x
[02:53] <calc> AnRkey: is gdm installed?
[02:54] <calc> AnRkey: if so what does 'sudo /etc/init.d/gdm start' do for you?
[02:54] <calc> gar
[02:57] <calc> AnRkey: is gdm installed?
[02:58] <AnRkey> calc, yeah fine
[02:58] <calc> AnRkey: if so what does 'sudo /etc/init.d/gdm start' do for you?
[02:58] <AnRkey> i am using it now
[02:58] <calc> oh so gdm works now, ok, thats good :)
[02:58] <AnRkey> i login and use startx to get into gdm
[02:58] <calc> startx doesn't go into gdm
[02:58] <calc> gdm is in place of needing to use startx
[02:59] <calc> if gdm is working it comes up at boot time
[02:59] <calc> startx just starts X
[02:59] <calc> so quit out of X and then run 'sudo /etc/init.d/gdm start' to see what it does
[03:00] <calc> if that causes gdm to start then something is wrong with /etc/rcX.d/ symlink (probably)
[03:00] <DanaG> Odd, when I made /var a separate partition, it seemed to break some things.
[03:00] <calc> if it does start dpkg-reconfigure -plow gdm might ask you if you want to use it (not really sure though)
[03:01] <AnRkey> calc, it does work but it won't start during boot time
[03:02] <AnRkey> sudo /etc/init.d/gdm start gives me this * Not starting GNOME Display Manager (gdm); it is not the default display manager.
[03:03] <calc> AnRkey: ah well then that is the problem
[03:04] <calc> AnRkey: i think sudo 'dpkg-reconfigure -plow gdm' will fix that for you
[03:04] <calc> its not starting because
[03:04] <calc> DEFAULT_DISPLAY_MANAGER_FILE=/etc/X11/default-display-manager
[03:04] <calc> is not gdm
[03:04] <calc> which i think reconfigure will let you set it to that
[03:05] <Pici> Is that a softlink to gdm?
[03:05] <AnRkey> cat /etc/X11/default-display-manager shows this
[03:05] <AnRkey> /usr/bin/gdm
[03:05] <calc> whoa
[03:05] <AnRkey> so donno now
[03:06] <calc> hmm
[03:06] <calc> AnRkey: i see the issue
[03:06] <AnRkey> echo $DEFAULT_DISPLAY_MANAGER_FILE comes up empty
[03:06] <calc> AnRkey: change the file so say /usr/sbin/gdm
[03:06] <calc> s/so/to/
[03:07] <calc> gdm is in /usr/sbin not /usr/bin
[03:07] <calc> which is what the init script checks to see if it should start
[03:08] <AnRkey> ok gonna reboot brb
[03:08] <AnRkey> thanks calc
[03:08] <AnRkey> is this a bug in gutsy's installer then?
[03:08] <AnRkey> how do i follow up on it?
[03:08] <AnRkey> rebooting quick
[03:12] <AnRkey> calc, thanks that worked perfectly. I am a bit bummed that I did not check the path to gdm myself. Thanks again though.
[03:12] <AnRkey> be back later, gonna get a bit of sleep
[03:12] <AnRkey> gotta be up in a few hours
[03:30] <voidmage> strange
[03:30] <voidmage> for some reason firefox likes to take up 98% cpu when i lauch it
[03:30] <voidmage> and it won't ever actually work
[03:31] <voidmage> brb x restart
[03:37] <techII> is "update-manager -d" supposed to work on 64 bit systems yet?
[03:39] <voidmage> Is anybody else having trouble with compiz at the moment?
[03:40] <voidmage> when I start compiz it crashes X
[03:44] <voidmage> well yeah
[03:44] <voidmage> compiz likes to crash X now
[03:44] <voidmage> started as soon as I added Option "AddARGBGLXVisuals" "True" to xorg.conf
[04:01] <DanaG> FOr me, compiz FREEZES Xorg.
[04:09] <voidmage> Can anyone help me diagnose why certain apps, including mythtv and compiz cause X to crash?
[04:12] <voidmage> Backtrace:
[04:12] <voidmage> 0: /usr/bin/X(xf86SigHandler+0x81) [0x80c8631] 
[04:12] <voidmage> 1: [0xffffe420] 
[04:12] <voidmage> Fatal server error:
[04:12] <voidmage> Caught signal 11.  Server aborting
[04:12] <voidmage> is all that xorg.log gives me
[04:13] <voidmage> I'm not really sure where to begin.
[04:15] <voidmage> I have nothing to go by except that thing in xorg.log and the fact that when it crashes, X basically just restarts without warning
[04:21] <voidmage> sorry about that, X keeps crashing
[04:21] <voidmage> if anyone said something in between the time I was gone and now, can you repeat it?
[04:21] <jmg> guys i have the gnome-settings-daemon bug
[04:23] <voidmage> see if removing compiz fixes it
[04:23] <voidmage> might crash again
[04:23] <voidmage> brb if that happens
[04:47] <jmg> compiz.real  Warn: Bind Pixmap to Texture failure
[04:49] <yellow_chicken> which alsa will gutsy gibbon use?
[05:04] <voidmage> I can't rebuild the nvidia kernel modules now
[05:05] <voidmage> ERROR: Unable to determine the NVIDIA kernel module filename.
[05:34] <voidmage> anyone know what's up with the latest nvidia drivers and: ERROR: Unable to determine the NVIDIA kernel module filename. ?
[05:52] <voidmage> anyone know what's up with the latest nvidia drivers and: ERROR: Unable to determine the NVIDIA kernel module filename. ?
[06:00] <taxman> I thought I saw a page on how to rsync to the latest tribe3. Am I dreaming?
[06:01] <taxman> rsynch a tribe2 iso that is
[06:03] <taxman> ahh, I guess jigdo can do similarly
[06:08] <jmg> my system doesnt have xgl is it required for compiz xtill?
[06:08] <voidmage> is something with the nvidia drivers broken?
[06:08] <voidmage> i get anyone know what's up with the latest nvidia drivers and: ERROR: Unable to determine the NVIDIA kernel module filename. ?
[06:10] <voidmage> anyone know what's up with the latest nvidia drivers and: ERROR: Unable to determine the NVIDIA kernel module filename. ?
[06:22] <voidmage> anyone know what's up with the latest nvidia drivers and: ERROR: Unable to determine the NVIDIA kernel module filename. ?
[06:25] <jmg> ok compiz is working now but it has the wrong resolution, any fix?
[06:26] <jmg> !fixresolution
[06:26] <ubotu> Sorry, I don't know anything about fixresolution - try searching on http://bots.ubuntulinux.nl/factoids.cgi
[06:26] <jmg> !fixres
[06:26] <ubotu> The X Window System is the part of your system that's responsible for graphical output. To restart your X, type  sudo /etc/init.d/?dm restart  in a console - To fix screen resolution or other X problems: http://help.ubuntu.com/community/FixVideoResolutionHowto
[06:27] <voidmage> Anyone know anything about ERROR: Unable to determine the NVIDIA kernel module filename. ?
[06:35] <jmg> :(
[06:52] <voidmage> Anyone know anything about ERROR: Unable to determine the NVIDIA kernel module filename. ?
[06:56] <xtknight> voidmage, i see your question 6 times on one page.  apparently nobody knows.
[06:57] <voidmage> good, that means someone's there
[06:57] <voidmage> :P
[06:57] <xtknight> lol
[06:57] <xtknight> have you tried removing/reinstalling linux-restricted-modules and nvidia-glx-new?
[06:57] <voidmage> xtknight: probably would help to say that i'm using nvidia.com's drivers because nvidia-glx-new doesn't support the 8600
[06:58] <xtknight> ah
[06:58] <voidmage> and that the error comes from the installer
[06:58] <xtknight> i think i know what the problem is
[06:58] <xtknight> but you're not going to like the solution
[06:58] <voidmage> happened today starting after some updates were put out
[06:58] <xtknight> basically you have to type "sudo modprobe -i nvidia" at every bootup
[06:58] <voidmage> anyways, what's that?
[06:58] <xtknight> and then it works
[06:58] <xtknight> for the official nvidia.com drivers
[06:58] <xtknight> -i makes it ignore the install script, no bad consequences (probably just a few missing sanity checks)
[06:59] <voidmage> i don't have the nvidia modules installed though?
[06:59] <xtknight> oh, you don't?
[06:59] <voidmage> no, that error's coming from the installer
[06:59] <xtknight> you mean the installer doesnt finish?
[06:59] <xtknight> hmm
[06:59] <voidmage> yeah
[06:59] <xtknight> not sure i only tried it on Feisty myself
[07:00] <voidmage> really wish they'd package 100.14.11 in nvidia-glx-new
[07:00] <voidmage> because of course, my card is the only unsupported one right now
[07:00] <xtknight> besides, there's also a file in /etc/modprobe.d/lrm-video that also interferes with installing nvidia.com drivers
[07:00] <xtknight> in/at
[07:00] <voidmage> yeah i actually just saw that when i tried to modprobe nvidia
[07:00] <xtknight> commenting this out works for some people:  #   install nvidia /sbin/lrm-video nvidia $CMDLINE_OPTS
[07:00] <xtknight> didnt do anything for me
[07:01] <xtknight> i had to use modprobe -i after i got it installed.  doesnt even sound like youre at that point yet
[07:01] <xtknight> and you have the linux-headers right?
[07:01] <voidmage> yeah
[07:01] <voidmage> oh wait, have to kill x
[07:01] <voidmage> doesn't like that i'm installing it while X is running
[07:01] <xtknight> gdm stop
[07:01] <xtknight> err... sudo /etc/init.d/gdm stop
[07:02] <voidmage> brb then
[07:04] <voidmage> nope
[07:04] <voidmage> didn't do anything
[07:05] <voidmage> first off, weird that it would suddenly break
[07:05] <xtknight> what did you do differently this time?
[07:05] <voidmage> i commented out that line in lrm-video
[07:05] <xtknight> oh
[07:05] <xtknight> didnt do anything here either
[07:05] <voidmage> anyways, still confused why it would break like that
[07:05] <xtknight> there's an --expert mode
[07:06] <voidmage> tried that one already
[07:06] <voidmage> didn't do anything
[07:06] <xtknight> tried building it yourself?
[07:06] <xtknight> like extract the sh into a folder and compile
[07:06] <voidmage> haven't tried that yet
[07:06] <xtknight> might give you more verbose output, at least
[07:06] <xtknight> there's nothing in NVIDIA installer.log?
[07:06] <voidmage> just that line
[07:06] <xtknight> that is more verbose
[07:06] <xtknight> ok try the switch that lets you extract it and compile it
[07:07] <voidmage> make: *** [print-module-filename]  error 1
[07:07] <xtknight> hmm
[07:08] <xtknight> http://www.nvnews.net/vbulletin/showthread.php?t=79902
[07:08] <voidmage> oh, i think i got it.
[07:08] <voidmage> looks like ccache fails a sanity check
[07:09] <voidmage> oh wow.
[07:09] <voidmage> i think that worked
[07:10] <voidmage> i'll try this now
[07:10] <voidmage> brb again
[07:15] <voidmage> alright, that worked.
[07:16] <voidmage> one other thing, to fix the lrm-video issue what worked was installing linux-restricted-modules-common
[07:18] <xtknight> hmm
[07:18] <xtknight> what worked in the end?
[07:18] <xtknight> compiling it on your own?
[07:19] <voidmage> CC=gcc sudo NVIDIA-driver-100.14.11.sh
[07:19] <voidmage> figured out ccache was failing a sanity check
[07:20] <voidmage> well, compiz works nw
[07:20] <voidmage> now
[07:20] <voidmage> i like the packaging, esp. how it's in main
[07:20] <voidmage> :P
[07:56] <opopanax> shoulda been gibbous gibbon
[07:57] <opopanax> so what's this i read about configless X?
[07:57] <opopanax> is that planned to be part of gutsy?
[08:02] <scotth_> opopanax: http://www.x.org/wiki/Releases/7.2
[08:03] <scotth_> gutsy seems to have 7.2
[08:03] <scotth_> try moving your xorg.conf out of the way and see what happens
[08:03] <opopanax> yeah
[08:03] <opopanax> have to upgrade first
[08:04] <opopanax> I've got beryl installed; compiz is just a drop-in replacement, right?
[08:04] <scotth_> kindof
[08:04] <opopanax> i know they're not exactly alike...
[08:04] <scotth_> well they are
[08:04] <scotth_> beryl is compiz+bunch of extra plugins
[08:04] <opopanax> beryl was a fork of compiz, I thought.  did they re-merge?
[08:04] <scotth_> yeah they did
[08:05] <opopanax> gatcha
[08:05] <scotth_> short story is gutsy has compiz fusion which is the merge of the two
[08:05] <opopanax> oic.
[08:05] <opopanax> so, beryl as implemented in feisty is dep.?
[08:05] <stdin> umm, Ubuntu Gutsy dose
[08:05] <opopanax> deprecated
[08:05] <opopanax> rather
[08:05] <scotth_> was beryl ever in feisty?
[08:05] <voidmage> !info beryl feisty
[08:05] <ubotu> beryl: Compositing window manager, decorator and theme support - Beryl. In component universe, is optional. Version 0.2.1.dfsg+git20070318-0ubuntu2 (feisty), package size 2 kB, installed size 44 kB
[08:06] <opopanax> that would be the case
[08:06] <stdin> beryl was not installed by default
[08:06] <opopanax> no
[08:06] <voidmage> compiz will be in gutsy from what i hear
[08:06] <voidmage> default, even
[08:06] <opopanax> yep[
[08:06] <scotth_> thought you had to use outside repos to get it in feisty
[08:06] <opopanax> which means my laptop will cease to work.
[08:06] <opopanax> heh
[08:06] <voidmage> if beryl doesn't work it SHOULD fall back to metacity
[08:06] <voidmage> emphasis on should
[08:06] <voidmage> :P
[08:06] <scotth_> I think it will fall back gracefully
[08:06] <stdin> scotth_: not actually, it was merged into the repos
[08:07] <voidmage> lolstabilityhumor
[08:07] <stdin> -fusion is nice though :)
[08:07] <opopanax> i think i have the wrong update-manager...  can I just go ahead and manually change my repos to gutsy and do a dist-upgrade?
[08:07] <scotth_> yeah, I definately agree... fusion is sweetness
[08:07] <stdin> adds a lot of functionality to the bling of beryl
[08:08] <scotth_> wrong update-manager?
[08:08] <scotth_> gksudo update-manager -c -d
[08:08] <opopanax> hmmmm
[08:08] <opopanax> the gutsy page needs to be updated then
[08:08] <opopanax> doesn't like -c
[08:09] <scotth_> that was just off the top of my head
[08:09] <scotth_> manpage?
[08:09] <opopanax> sorry
[08:09] <opopanax> .......says i'm up to date.
[08:09] <scotth_> no manpage
[08:09] <opopanax> heh.  i'll do some pokin see what I can find
[08:09] <opopanax> info page prolly
[08:10] <scotth_> ahh, no -c
[08:10] <scotth_> http://www.ubuntu.com/testing/tribe3
[08:10] <opopanax> page says I need update-manager from feisty-proposed...
[08:11] <voidmage> opopanax: a dist-upgrade would probably work, but make sure to remove all third-party and local packages first
[08:11] <voidmage> and make sure to run a dist-upgrade until it doesn't report any upgrades
[08:11] <voidmage> then make sure (k)ubuntu-desktop and ubuntu-minimal are installed
[08:11] <Hobbsee> and ubuntu-standard
[08:11] <scotth_> I ussually upgrade apt and dpkg first
[08:12] <Hobbsee> scotth_: you shouldnt need to.
[08:12] <scotth_> old debian advice
[08:12] <opopanax> makes sense, though...  like in gentoo, always update the toolchain, then portage, then the toolchain again.
[08:12] <scotth_> Hobbsee: old habit, has yet to get me into trouble
[08:12] <opopanax> then the rest of it.
[08:12] <Hobbsee> it *should* just dist-upgrade cleanly - or fairly cleanly
[08:13] <Hobbsee> in fact, if you do it with a dist-upgrade, and report teh bugs, that'd be very useful
[08:13] <opopanax> ran ~x86 in gentoo for 2 years, should be fine.
[08:13] <opopanax> but, then again, not a debian guy, so I could get hung up
[08:13] <Hobbsee> actually, kubuntu upgrader will likely fall over
[08:13] <opopanax> ok, changing repos.
[08:13] <Hobbsee> there are still some conflicts in kdepim, iirc.  i should really fix them.
[08:14] <Hobbsee> (where you can use dpkg -i --force-overwrite as a workaround)
[08:14] <opopanax> so, i can change feisty to gutsy, feisty-backports to gutsy-backports, so on and so forth, and I should be "fine"?
[08:14] <Hobbsee> stf
[08:15] <Hobbsee> opopanax: gutsy-backports doesnt exist
[08:15] <Hobbsee> and you should be mostly fine.
[08:15] <opopanax> keep feisty-backports, then?
[08:15] <stdin> takes a bit of work sometimes, but that's alpha :)
[08:15] <Hobbsee> please file bugs for those overwriting packages, though, if they havent been filed already
[08:15] <Hobbsee> opopanax: no, remove it completely
[08:16] <opopanax> gutsy-commercial lives?
[08:16] <Hobbsee> i dont think so, it'll 404 if it doesnt
[08:16] <opopanax> kcool
[08:17] <voidmage> gutsy-backports exists, but it's empty
[08:17] <voidmage> gutsy-commercial isn't open yet
[08:18] <voidmage> my current sources.list, for reference: gutsy, gutsy-proposed, gutsy-updates, gutsy-security, gutsy-backports, medibuntu-gutsy, and skype
[08:18] <opopanax> gutsy-proposed?
[08:18] <opopanax> k, cool.
[08:18] <opopanax> thanks
[08:18] <voidmage> commended out includes gutsy-commercial, wine, and ivtv
[08:19] <stdin> I like to have all the official repos in sources.list and anything else in another file in sources.list.d/
[08:19] <stdin> helps me keep track
[08:20] <opopanax> g-com 404'd like you said.
[08:20] <opopanax> all else succeeded.
[08:20] <Hobbsee> voidmage: skype may fall over.  no idea about the state of medibuntu
[08:21] <voidmage> i've had luck with skype
[08:21] <voidmage> well for now at least
[08:21] <voidmage> the repo is "debian stable"
[08:21] <voidmage> not sure how long that will last though
[08:23] <opopanax> thanks for the groovy assistance-like help.
[08:23] <opopanax> and stuff
[08:23] <opopanax> see how it goes, and i'll report back.
[08:24] <opopanax> pretty standard hardware
[08:26] <xtknight> hmm so gutsy has commercial now huh?
[08:26] <xtknight> lol never mind
[08:30] <AnAnt> Hello, I got a problem in gutsy
[08:31] <AnAnt> when I pass vga=788, I can't work on virtual console
[08:32] <AnAnt> I am using a 15.4" laptop
[08:50] <shirish> guys is somebody or anybody having issues with starting ubuntu, gtk+ refusing to start?
[08:52] <databuddy> shirish: just do ctrl+alt+bkspace
[08:52] <databuddy> then relog in and its fixed here
[08:54] <databuddy> gah - fonts are tiny in gkrellm - the dpi bug is hitting me all ovah ! ;p
[08:54] <databuddy> any way to change default font size for gtk apps like gkrellm?
[08:55] <DanaG> Is the DPI setting correct?
[08:56] <DanaG> Oh wait, do you mean GTK1?
[08:56] <DanaG> If so, I don't know the answer to that one.
[08:58] <databuddy> DanaG: dpi doesnt do anything in general
[08:58] <DanaG> The new appearance panel no longer applies changes on the fly.
[08:59] <DanaG> Now you have to log out and back in.  It's a major regression, in my opinion.
[08:59] <shirish> databuddy: I did the crtl+alt+backspace but it doesn't solve the issues
[09:00] <databuddy> shirish: sorry, perhaps i dont understand exactly
[09:00] <databuddy> for me gnome would seem to load - but nothing would load ust would have blank desktop
[09:00] <shirish> databuddy: I have uploaded the xsession-errors file http://rapidshare.com/files/45499269/.xsession-errors.html
[09:00] <databuddy> i would do that and relog in and i was good - sometimes twice
[09:00] <shirish> databuddy: yup, know that one, but this is a recurring issue, the good thing is I have also xubuntu-desktop installed so i can use stuff
[09:04] <databuddy> well 'solved' my dpi problem - just gotta restart X in between
[09:05] <shirish> DanaG: can you take a look at http://rapidshare.com/files/45499269/.xsession-errors.html
[09:05] <databuddy> shirish: dunno the impacts of having both full desktops in - tho you dont typically need the whole thing to use everything - i use k3b in gnome all the time - in fact for linux its the only burning program i use
[09:05] <shirish> databuddy: I like to use both desktops, i have few clients/friends who use xubuntu while some which have ubuntu
[09:06] <shirish> hence the two desktops requirement
[09:07] <databuddy> ya
[09:07] <databuddy> i dont see anything in that errors log that sticks out - but im no pro sorry
[09:08] <DanaG> For text files, use pastebin.
[09:08] <DanaG> I've lately found myself having to kill XOrg 3 or 4 times before a login worked.
[09:09] <DanaG> I've read somewhere that the "Desktop Effects" panel is what breaks things, so try disabling it there and manually starting compiz at each session, for safety.
[09:11] <shirish> DanaG: ok cool
[09:12] <shirish> ubotu paste
[09:12] <ubotu> pastebin is a service to post large texts so you don't flood the channel. The Ubuntu pastebin is at http://paste.ubuntu-nl.org (make sure you give us the URL for your paste - see also the #ubuntu channel topic)
[09:13] <databuddy> so DanaG how does one get beryl in gutsy anyway?
[09:15] <shirish> DanaG: http://paste.ubuntu-nl.org/31633/
[09:23] <shirish> DanaG: sorry for logging out, my system had got hanged
[09:23] <DanaG> Beryl has been superseded by compiz-fusion.
[09:24] <DanaG> But you can still install the old Feisty debs of Beryl.
[09:24] <DanaG> Just be aware that with everything after 0.1.9999, transparent cube breaks some animations.
[09:25] <DanaG> Restarting to Ubuntu now -- I was in Windows.
[09:25] <shirish> DanaG: ok cool, lemme know when you're in
[09:25] <shirish> DanaG: also have you played with tracker, the search engine?
[09:38] <AnAnt> Hello, I got a problem in gutsy
[09:38] <AnAnt> when I pass vga=788, I can't work on virtual console
[09:38] <AnAnt> I am using a 15.4" laptop
[09:48] <DanaG> Argh, ntfs-3g doesn't offer a fallback to read-only!
[09:56] <shirish> DanaG: welcome back :)
[09:56] <DanaG> Oh, that reminds me: there are some updates I haven't installed.
[09:57] <DanaG> I always read any changelogs before installing updates, just to see what's new.
[10:00] <shirish> DanaG: how do you read changelogs before installing updates?
[10:01] <DanaG> Oh, you use update-manager.
[10:01] <shirish> ah, I know what you mean, I use aptitude hence forgot
[10:09] <opopanax> finally done downloading, now installing packages.
[10:12] <opopanax> the best part of xorg 7.x is the modular architecture.  Makes things a lot easier to update; I remember that from gentoo.
[10:12] <opopanax> is debian proper still on xfree86?
[10:13] <pwnguin> i dont think so
[10:13] <pwnguin> but you can be on xorg and not xorg 7.x
[10:18] <opopanax> pwnguin, um, yeah.
[10:19] <opopanax> is dapper lts on xorg <7
[10:24] <opop> yep
[10:36] <Ind[y] > Where is the dhclient init script? I want to add a flag to dhclient.
[10:37] <opop> ok, dist-upgrade borked.
[10:37] <opop> on unzoo
[10:38] <opop> hmmm
[10:38] <opop> doing an update first
[10:38] <Ind[y] > (I mean, I want to find where is the script that launches dhclient.)
[10:42] <opop> indy:  should be a boot service, but only launched if called for in /etc/network/interfaces
[10:42] <opop> right?
[10:44] <Ind[y] > opop: Actually, I get tons of messages at boot, from NetworkManager (at the TTYs), and I want to disable these messages. I suppose dhclient prints them, so I want to find the script that launches it, and add the -q flag to dhclient.
[10:48] <opop> try ifup
[10:48] <opop> that might contain it.
[10:48] <opop> sorry, not super-familiar with the debian boot process yet.
[10:49] <Ind[y] > opop: ok. thanks.
[10:49] <opop> what's dhcdbd?
[10:50] <Ind[y] > Actually I found dhclient's configuration file. Can I add a flag to dhclient from there?
[10:50] <opop> man dhclient
[10:50] <opop> or dhclient.conf
[10:52] <opop> oh, the new sudo dialog is kinda nice
[10:52] <opop> there's no script-name in /etc/ containing the name dhclient, if that helps.
[10:54] <Ind[y] > opop: I found /etc/dhcp3/dhclient.conf but I don't know how to tell it to add a flag to dhclient, every time it starts.
[10:55] <opop> are you sure you want to?
[10:57] <opop> -q is just quiet, right?
[10:57] <Ind[y] > Yes
[10:57] <Ind[y] > But how can I add this flag (I don't start dhclient manually)?
[10:57] <opop> i would think a lot of output from dhclient would be bug-related, wouldn't you?
[10:58] <opop> something you'd want to resolve, not muzzle.
[10:58] <opop> you'd have to find the script that's calling it.
[10:58] <Ind[y] > opop: Actually, -q quiets the non-bug-related messages.
[10:58] <Ind[y] > Only the info ones.
[10:59] <Ind[y] > opop: I know, that's what I am saying from the begining :P
[10:59] <opop> ifup is in binary, so you really can't edit that.
[10:59] <opop> getcha
[10:59] <Ind[y] > Sorry?
[10:59] <opop> gotcha
[10:59] <Ind[y] > (I bet you found it)
[10:59] <opop> /etc/init.d/networking doesn't call it directly.
[10:59] <opop> no, didn't find it.
[10:59] <Ind[y] > :P
[11:00] <Ind[y] > opop: I suppose that someone here knows it. There are many developers here, after all.
[11:01] <opop> yah.
[11:01] <opop> sorry i couldn't help.  pretty sure ifup calls it, though.
[11:01] <Ind[y] > opop: OK, never mind. Thanks a lot, though :-)
[11:14] <opop> bad image index on synaptic and eog, any ideas?
[11:20] <opop> ok, great, just a bad file.  it's gone now.
[11:21] <opop> https://bugs.launchpad.net/ubuntu/+source/apport/+bug/125260
[11:21] <ubotu> Launchpad bug 125260 in apport "Dist upgrade in up-to-date Gutsy reports errors" [Undecided,Invalid] 
[11:24] <opop> rebooting into gutsy.  wish me luck.  (removing xorg.conf just for kicks, see what happens.)
[11:39] <opopanax> ok, everything seems to be ok, but my beryl install is borked.
[11:39] <opopanax> compiz isn't starting
[11:40] <opopanax> emerald isn't doing it's thing properly.
[11:40] <opopanax> as far as window decorations.
[11:40] <opopanax> hmmm.
[11:57] <Sebastian> Why does my screen suddenly turn greenish/blueish instead of black when X starts before GDM shows itself?
[12:00] <askand> Am im the only one that cant use iconthemes from gnomelook in gutsy?
[12:28] <blackdiamond_> Hi guys! Sorry if my english language is not really correct. But I'll try to do my best. I use ubuntu 7.04. On a partition on my pc I would like to test Gutsy. I try to do that, but in the new partition, internet connection doesn't work. There is no way to connect the modem. My modem is D-Link. It can be a problem of kernel? What can I do? I would like to get involved in testing Gutsy Gibbon. Thanks
[12:29] <jussi01> blackdiamond_: I suggest you wait for a while before using gutsy. there are still a lot of broken things and it isnt ready for peole who dont know exactly what they are doing
[12:30] <askand> Am im the only one that cant use iconthemes from gnomelook in gutsy?
[12:31] <blackdiamond_> @Jussi01. The problem is that i always use to report bugs etc..I don't have problem to test this sort of things.. The only problem is that there is no way to connect to internet. thanks
[12:32] <blackdiamond_> but i don't know what is the real problem
[12:35] <jussi01> blackdiamond_: ok, how did you connect the modem in 7.04?
[12:40] <blackdiamond_> @Jussi01. From terminal pppoeconf
[12:41] <blackdiamond_> system -->network --> ethernet etc.. and it works
[12:50] <jussi01> blackdiamond_: excellent :)
[12:51] <blackdiamond_> do you think that is the new kernel of GUtsy that do not support my modem?
[02:52] <ekso> hey,  on gutsy tribe 3, where do i find the restricted drivers module?
[02:55] <xstasi> anyone knows what are the feisty-proposed repos?
[03:01] <Hobbsee> ekso: restricted-manager?  you have to install it
[03:01] <Hobbsee> ekso: it's a bug, it's subsequently been fixed.
[03:01] <Hobbsee> xstasi: feisty --> #ubuntu
[03:01] <xstasi> well noone knows about that on #ubuntu
[03:01] <xstasi> :)
[03:02] <ekso> Hobbsee: it's installed on synaptic, but I can't find it anywhere (neither the command to run it on a terminal)
[03:02] <Hobbsee> xstasi: copy the feisty-updates line of your sources list, adn adapt it to be feisty proposed.
[03:02] <xstasi> yeah, i didn't ask how to use them
[03:02] <xstasi> i asked what are they
[03:02] <xstasi> :P
[03:02] <Hobbsee> ekso: are you talking about linux-*-modules, or restricted-manager?
[03:03] <Hobbsee> xstasi: oh, i misread
[03:03] <Hobbsee> !sru | xstasi
[03:03] <ubotu> xstasi: Stable Release Update information is at http://wiki.ubuntu.com/StableReleaseUpdates for main and restricted, while https://wiki.ubuntu.com/MOTU/SRU is for universe and multiverse.
[03:03] <Hobbsee> !proposed
[03:03] <ubotu> Sorry, I don't know anything about proposed - try searching on http://bots.ubuntulinux.nl/factoids.cgi
[03:03] <xstasi> mh.. sru uh?
[03:03] <xstasi> :D
[03:03] <Hobbsee> xstasi: see the sru stuff - the proposed updates to a stable release go to -proposed
[03:03] <xstasi> Hobbsee, IIRC, you are a MOTU..
[03:03] <Hobbsee> xstasi: and a core dev, yes.
[03:03] <xstasi> i'm downloading gutsy right now
[03:03] <xstasi> so i haven't tried it yet
[03:04] <Hobbsee> cool :)
[03:04] <Hobbsee> you wont need feisty-proposed then
[03:04] <xstasi> Upgrading from Feisty
[03:04] <xstasi> If you upgrade from feisty, please make sure that you have update-manager 0.59.23 from feisty-proposed installed. Then run "update-manager -d".
[03:04] <xstasi> that's why i wondered
[03:04] <xstasi> :)
[03:04] <Hobbsee> ah right
[03:04] <xstasi> anyway
[03:04] <Hobbsee> it's the test repository, basically
[03:04] <xstasi> i had an idea, maybe you already did it..
[03:04] <xstasi> how about using the new debian-installer for the alternate?
[03:04] <xstasi> the one in gtkfb
[03:05] <xstasi> it would be really cool..
[03:05] <Hobbsee> i didnt do it
[03:05] <Hobbsee> cjwatson would know, i'd be surprised if we didnt already.
[03:05] <xstasi> i'd like to avoi
[03:05] <Hobbsee> depends when it came out, etc
[03:05] <xstasi> i'd like to avoid wasting both bandwidth and cds
[03:05] <xstasi> to burn an iso
[03:06] <xstasi> that's why i ask you instead of trying by myself
[03:06] <xstasi> :p
[03:06] <Hobbsee> fair enough
[03:07] <Hobbsee> if you have a look at the changelog, it should tell you.
[03:07] <ekso> is there a way to run the restricted-modules GUI from the terminal?
[03:07] <mendred> hullo Hobbsee..long time no see
[03:07] <Hobbsee> hi mendred
[03:08] <xstasi> ekso, sudo restricted-manager, i guess
[03:08] <Hobbsee> ekso: sure, type restriced-modules
[03:08] <Hobbsee> er, what xstasi said
[03:08] <Hobbsee> that's waht i *meant* to type
[03:09] <ekso> nope... restricted-manager not found
[03:09] <ekso> and lrm-manager exists, but doesn't open anything :?
[03:10] <xstasi> dpkg -L restricted-manager | grep bin/
[03:10] <xstasi> try this :P
[03:10] <ekso> AF
[03:10] <ekso> thanks!! :D
[03:11] <Hobbsee> ekso: can you pastebin the output of 'apt-cache policy restricted-manager'?
[03:11] <Hobbsee> oh, you found it
[03:11] <ekso> yes, it wasn't installed. i thought it was (LINUX-restrict-modules-* was)
[03:12] <Hobbsee> ah, so i was right in my suspicion
[03:12] <xstasi> Hobbsee, anyway
[03:12] <xstasi> where should i check for that d-i thing again?
[03:13] <Hobbsee> changelogs.ubuntu.com
[03:21] <xstasi> Hobbsee, how many strange named files..
[03:22] <xstasi> :P
[03:22] <xstasi> is there useful info?
[03:23] <xstasi> anyway, update-manager -d says nothing.. is the wiki info correct?
[03:23] <xstasi> because i'm about to sed -e "s/feisty/gutsy/g" on sources.list
[03:23] <xstasi> :P
[03:24] <igorgue> Does anybody have a working vmware server?
[03:34] <xsacha> updated from adept_updater today and now my mouse seems to double click whenever i press left mouse button
[03:34] <yellow_chicken> beta use alsa 1.0.14rc4 or final release?
[03:35] <yellow_chicken> gutsy beta use alsa 1.0.14rc4 or final release?
[03:37] <yellow_chicken> can someone help, i installed 1.0.14 on ubuntu 7.04.  when i go youtube.com and watch like 3 videos, the sound screws up.  the sound chug a little and screws up
[03:38] <igorgue> it have gutsy and it says 1.0.14
[03:38] <igorgue> no rc4
[03:40] <igorgue> yellow_chicken, it says 1.0.14-1
[03:40] <igorgue> i think is rc1
[03:40] <yellow_chicken> oh no
[03:40] <yellow_chicken> i was using rc4
[03:41] <igorgue> :S
[03:41] <yellow_chicken> but i just switch to final release. but sound still screw up
[03:41] <igorgue> btw, I can see youtube all day and no sound problems
[03:43] <yellow_chicken> well, for me this machine, plays sound.  then at some point, it just keep on playing the same note over and over again. and tottally crashes, and a reboot is needed to fix
[03:43] <yellow_chicken> it
[03:53] <xstasi> Hobbsee, can i pm?
[03:56] <Hobbsee> xstasi: you can, but i'm not really here at the moment.
[03:57] <Hobbsee> !backports | xstasi
[03:57] <ubotu> xstasi: If new updated Ubuntu packages are built for an application, then they go into Ubuntu Backports. See https://help.ubuntu.com/community/UbuntuBackports - See also !packaging
[03:57] <xstasi> thx
[04:17] <xstasi> !help
[04:17] <ubotu> I am ubotu, all-knowing infobot. You can browse my brain at http://bots.ubuntulinux.nl - Usage info: http://wiki.ubuntu.com/UbuntuBots
[04:47] <PriceChild> hmm the new xchat loads old logs when you start up
[04:55] <elkbuntu> PriceChild, oh? as in, in the scrollback?
[04:55] <PriceChild> Yeah
[04:55] <elkbuntu> sweeeeeet!
[04:55] <PriceChild> Haha :)
[04:56] <PriceChild> do I get a prize for telling you about it?
[04:56] <elkbuntu> PriceChild, a hug if we ever meet again
[04:56] <PriceChild> wooo
[04:56] <PriceChild> and then you can see my question in -ops in the scrollback when you reboot :)
[05:00] <elkbuntwo> ohmigawd. it really does!
[05:01] <PriceChild> haha I wasn't lying :D
[05:01] <PriceChild> I wish xchat had an easy way to change the amount of scrollback you have though...
[05:01] <PriceChild> I think it means editing a file or two before compiling
[05:02] <elkbuntwo> btw, you were saying yesterday you disliked the new tree view?
[05:02] <elkbuntwo> i cant see any difference other than the little lines
[05:15] <sn0> PriceChild it does?
[05:15] <sn0> settings > prefernces > interface > text input > scrollback lines
[05:17] <elkbuntwo> zomg, PriceChild, we also finally get a gnome where we can drag and drop our panel tabs into order!
[05:33] <sn0> does anyone else notice a blue/green screen appearing, for about half a second, before GDM kicks in? on latest updates
[05:34] <elkbuntu> sn0, yes. they've merged the new debian gdm in, and it wasnt trivial so there'll be a few quirks like that
[05:34] <sn0> ohh righty, reminded me of the default background on windows 95/98 :o
[05:34] <elkbuntu> hehe, it's actually from the debian-moreblue theme iirc
[05:34] <sn0> :>
[05:35] <elkbuntu> the gdm greeter was debian-moreblue for a short while
[05:37] <sn0> i haven't seen it
[05:42] <webjames> sn0 i had that
[05:42] <webjames> then an error about debian-moreblue, then it went to a different login screen
[05:43] <sn0> bug 118657
[05:43] <ubotu> Launchpad bug 118657 in gdm "default background colour is blue in gutsy" [Low,Confirmed]  https://launchpad.net/bugs/118657
[05:43] <PriceChild> sn0, wooo thanks for that
[05:43] <PriceChild> elkbuntu, yeah... I don't like the little lines :P
[05:43] <sn0> yw PriceChild :-) it drove me mad too
[05:44] <webjames> little lines?
[05:44] <sn0> ctrl+l lines?
[05:44] <sn0> first time i seen those i thought there was a spider on my screen
[05:45] <sn0> ctrl+l = clear lol
[05:45] <webjames> i haven't got any lines?
[05:52] <sn0> webjames im settings > preferences > interface > text box > there is a 'show marker line'
[05:52] <sn0> ahh too late ;] 
[06:41] <opopanax> interesting....  the flashplugin-nonfree dpkg-reconfigure script deletes /usr/lib/flashplugin-nonfree prior to attempting to unpack flash into it.
[06:43] <opopanax> ...but only when re-configuring...
[06:44] <opopanax> worked fine with a --reinstall
[06:53] <opopanax> k, how to get compiz working properly......removed beryl and attendant packages
[06:53] <opopanax> have to do it after baseball.  go mariners!
[07:37] <masterloki> http://www.newegg.com/Product/Productcompare.aspx?Submit=ENE&N=2010380048%201069609639%201305520548%20106790703%201067918816&bop=And&CompareItemList=N82E16814141057%2CN82E16814136008%2CN82E16814141038%2CN82E16814141038R%2CN82E16814141057R
[07:38] <databuddy> masterloki: ok looking ^^
[07:42] <masterloki> ok
[07:43] <databuddy> http://www.newegg.com/Product/Product.aspx?Item=N82E16814141038R
[07:43] <databuddy> thats the one i'm voting for
[07:43] <databuddy> but double check its got the adaptor for the monitor
[07:43] <databuddy> i think i have an extra one lying around anyway tho
[07:45] <databuddy> yeah i got an extra dvi-i to vga i'm sure of it
[07:46] <masterloki> databuddy are you talk about the dvi to avg adaptor
[07:47] <databuddy> avg?
[07:47] <databuddy> no.
[07:47] <databuddy> dvi to vga
[07:47] <databuddy> o yeah
[07:47] <databuddy> yes.
[07:48] <masterloki> I have one so if it does not have one I can use mines
[07:49] <databuddy> yeah
[07:49] <databuddy> that particular package comes with only the vid card - nothing else with it - thats basically what oem means on those
[07:50] <masterloki> ok
[07:50] <databuddy> so no disks or anything - but it works out of the box with win and *nix - and can dl the drivers easily enough
[07:50] <databuddy> and look at the features at the bottom - has uuberloads
[07:51] <masterloki> ? uuberloads
[07:52] <databuddy> lots and lots and lots :P
[07:54] <masterloki> ok
[07:54] <masterloki> :)
[07:54] <masterloki> ummm good
[09:20] <soothsayer> Does systemtap work on Gutsy without having to compiling kernels?
[09:23] <crimsun> it does.
[09:23] <xstasi> so
[09:23] <crimsun> You need to install the debug image and systemtap packages and create a symlink by hand,
[09:23] <xstasi> is there a recommended way to upgrade?
[09:23] <xstasi> i'd sed -e "s/feisty/gutsy/g" on sources.list and then apt-get up{date,grade}
[09:24] <soothsayer> crimsun: Alright thanks. The debug image wasn't available on Feisty right?
[09:24] <xstasi> but i've seen stuff involving a so called update manager
[09:24] <soothsayer> crimsun: (The particular debug image needed for full functionality in systemtap)
[09:24] <crimsun> soothsayer: it is.
[09:25] <xstasi> !upgrade
[09:25] <ubotu> For upgrading, see the instructions at https://help.ubuntu.com/community/UpgradeNotes
[09:25] <boris55> is there any reason that the mysql versions for ubuntu is so far behind other distros exxpecailly from the repsos?
[09:25] <xstasi> mh
[09:25] <xstasi> not what i was looking for
[09:26] <crimsun> xstasi: dist-upgrade after update, not upgrade.
[09:26] <xstasi> mh
[09:26] <xstasi> so that's the best way?
[09:26] <crimsun> xstasi: it's one way.
[09:26] <xstasi> mh kay
[09:26] <xstasi> :D
[09:26] <xstasi> because the wiki said to issue update-manager -d
[09:26] <xstasi> which is similar to dist-upgrade
[09:26] <xstasi> but the list of upgradables was empty.. :)
[09:26] <xstasi> i assume i'll have to do that way
[09:27] <crimsun> boris55: what are you talking about?
[09:27] <crimsun>   Candidate: 5.0.45-1
[09:27] <crimsun> http://mysql.org/downloads/mysql/5.0.html#downloads
[09:27] <crimsun> they're identical for the most recent stable release.
[09:28] <boris55> from the apt application.
[09:29] <crimsun> what about it?
[09:29] <crimsun> it's definitely the latest.
[09:29] <crimsun> http://pastebin.ca/637304
[09:29] <boris55> ok, I'll check again.
[09:30] <boris55> thanks.  I see it.
[09:51] <ryanakca> [!!]  Install the base system          Debootstrap Error          Failed to determine the codename for the release.    <Continue>              (Ubuntu Server 7.10.. yesterday's build... amd64)
[09:52] <ryanakca> Is there any way to manually pass the codename/version to debootstrap?
[11:05] <napsy_> why does evolution suck in latest updates?
[11:09] <AnRkey> napsy_, what is it doing?
[11:09] <napsy_> when I got new mail it starts to consume 100% cpu
[11:11] <AnRkey> hmm
[11:11] <AnRkey> it is beta so...
[11:11] <AnRkey> report it :D
[11:11] <napsy_> ok
[11:11] <AnRkey> evo normally gives me a nut ache when i use it with the exchange plugin
[11:12] <AnRkey> i seem to be alone with my dislike for the app
[11:13] <AnRkey> ok outa here
[11:13] <AnRkey> bf2 time
[11:27] <DanaG> WTF happened to CCSM?  The animations properties page is now horridly confusing!
[11:28] <DanaG> I mean, what is "4"?  Or "7"?
[11:28] <DanaG> For animation type.
[11:30] <DanaG> I mean, imagine if all the buttons in your car were labeled only with numbers, and there was nothing anywhere to indicate what those numbers meant?
[11:37] <geser> DanaG: I see this too after the last compiz update
[11:38] <geser> I guess the number specifies the type of animation but I don't have the mapping between number and animation
[12:01] <DanaG> I wish they'd bring back the checkboxes (wow, what a concept!) from Beryl's settings manager.