[00:25] <leleobhz> someone know why users-admin dont work even using sudo?
[00:26] <maco> leleobhz: because you cant use sudo with policy-kit apps
[00:26] <RAOF> leleobhz: Because it uses policykit now; it should barf on sudo.
[00:26] <maco> you have to just run "users-admin" and then click the unlock button
[00:27] <leleobhz> this worked in first install
[00:27] <maco> it worked back in 7.10
[00:27] <leleobhz> but after a dist-upgrade (from jaunty to jaunty)
[00:27] <maco> not since then
[00:27] <Sergeant_Pony> anyone know where I can find mf2t? I asked in #ubuntu and no help
[00:27] <leleobhz> this button is hidden
[00:27] <leleobhz> this is why im asking
[00:27] <leleobhz> maco: what i can try to make this work again?
[00:27] <maco> the unlock button still exists on users-admin in jaunty
[00:28] <maco> do *not* run "sudo users-admin" or the button will be disabled
[00:28] <leleobhz> dont work
[00:28] <maco> bug 210897
[00:28] <leleobhz> maco: ive runned only with my user, and dont worked
[00:29] <RAOF> "Don't work" isn't a useful problem description.  Does the "unlock" button appear?  Is it sensitive?  What happens if you press it? etc.
[00:29] <leleobhz> so if i run one time users-admin with sudo, i permanentelly damage it?
[00:29] <leleobhz> RAOF: [28/01-22:27:31] < leleobhz> this button is hidden
[00:29] <leleobhz> still hidden if i run with my user
[00:29] <maco> hidden as in not there at all or as in greyed out
[00:29] <leleobhz> grayed out
[00:30] <leleobhz> like i dont have permission to run it
[00:30] <maco> try "sudo -k" then retry it
[00:30] <maco> *without* sudo
[00:30] <leleobhz> no effect
[00:30] <maco> (sudo -k will kill the sudo session)
[00:30] <hggdh> or close the terminal, and open it again
[00:30]  * leleobhz running all commands from my user
[00:31] <maco> hggdh: ive had sudo credentials carry from one terminator to another
[00:31] <leleobhz> maco: understood, but dont worked yet
[00:32] <leleobhz> ill post a screenshot
[00:32] <hggdh> maco, that's bad -- the credentials should be restricted to the pid
[00:32] <hggdh> unless you opened a terminator from another running terminator
[00:32] <hggdh> (or gnome-terminal, for that matter)
[00:32] <maco> hggdh: no, if i use sudo in a terminator, then close it and open another right away, sometimes i dont need to enter my password when i sudo in the new one
[00:33] <maco> dunno if it still happens with jaunty
[00:33] <maco> but on hardy i could do it
[00:33] <hggdh> eeek
[00:33] <maco> yeah i can still do it
[00:33] <hggdh> then it is a safer bet to sudo -k
[00:34] <leleobhz> http://img294.imageshack.us/img294/9452/usersadmingi9.png
[00:34] <leleobhz> here is
[00:34] <maco> open a terminator, sudo -i, enter pw, hit the X. open a new terminator, sudo -i, no need for pw
[00:35] <maco> leleobhz: yeah that looks broken. can you reproduce it with a new user or after a reboot?
[00:35] <leleobhz> maco: this happens here (the hardy issue) :p
[00:35] <hggdh> perhaps group membership
[00:35] <maco> hggdh: what?
[00:35] <leleobhz> my user is the first ive created in ubuntu install
[00:36] <leleobhz> and the users-admin worked before the dist-upgrade
[00:37] <hggdh> perhaps he is not a member of the adm group
[00:37] <leleobhz> uid=1000(leleobhz) gid=1000(leleobhz) groups=4(adm),20(dialout),21(fax),24(cdrom),25(floppy),26(tape),27(sudo),29(audio),44(video),46(plugdev),109(lpadmin),116(admin),121(sambashare),1000(leleobhz),1002(setfon)
[00:37] <leleobhz> i am
[00:38] <maco> hggdh: should i be filing a bug on sudo for letting me do that in terminator?
[00:38] <maco> hggdh: i assumed it was like the 15 minutes gksudo timeout
[00:39] <Tekno> terminator ;P
[00:39] <hggdh> maco I think you should. I am not sure what to open against, though
[00:39] <maco> Tekno: terminator uses vte
[00:40] <Tekno> right
[00:40] <maco> oooo maybe it is terminator
[00:40] <hggdh> terminator seems a good bet
[00:40] <maco> because i cant do it with gnome-terminal
[00:40] <hggdh> even better!
[00:40] <maco> oh wiat yes i can
[00:40] <maco> its vte
[00:40] <leleobhz> some idea guys?
[00:40] <maco> if i sudo -i in gnome-terminal, it doesnt carry over to terminator
[00:41] <maco> it does carry over to later gnome-terminals though
[00:41] <maco> ...i wonder if maybe they're assigned the same pid?
[00:41] <hggdh> leleobhz, I am stumped right now
[00:42] <hggdh> the hell is on my side of the fence it works fine
[00:42] <maco> if i start one, do stuff, and exit it, then start another...since the first was exited, maybe the old pid is assigned to the new process?
[00:43] <hggdh> could happen on an extremely busy system, otherwise the chances are pretty much nill
[00:43] <maco> you mean extremely not-busy?
[00:43] <hggdh> pids are monotonically increasing (until they wrap around)
[00:43] <maco> oh
[00:44] <maco> i thought maybe it was "lowest available" :-/
[00:45] <hggdh> heh. users-admin help page is sorta oldish
[00:45] <hggdh> (c) 2004...
[00:45] <maco> oy
[00:45] <hggdh> oy vey
[00:45] <hggdh> no, revised on 2006
[00:46] <hggdh> sigh. OK. Time for a LP search
[00:46] <maco> 2006 is still a while
[00:46] <leleobhz> well, i ll need restart
[00:47] <leleobhz> its good because my VM goes down too
[00:47] <hggdh> yes. leleobhz, does it happen after a restart?
[00:47] <leleobhz> ill see after i restart my entire system
[00:47] <leleobhz> ill back
[00:47] <hggdh> k
[00:49] <hggdh> maco, when you say it carries over to other gnome-terms, do you close the first gnome-term and open a new one, or you just fire another from the g-t menu?
[00:50] <maco> close it and open a new one
[00:50] <hggdh> eeek eeek eeek
[00:50] <maco> launching from alt+f2 "gnome-terminal"
[00:51] <hggdh> bug 313990
[00:52] <hggdh> I will try it
[00:54] <maco> i dont have g-t in my menu anymore
[00:54] <maco> i launch terminator with super+t since i mapped it in my compiz shortcuts
[00:58] <maco> hggdh: slangasek says it's not a bug. sudo auth is based on user+tty# and when i close the first terminal and open a new one, the same tty# is used
[00:58] <maco> its not pid-based
[01:00] <hggdh> ah, OK
[01:01] <hggdh> makes sense -- the pty gets reused
[01:04] <hggdh> maco, where can I control which actions give sound feedback? Like clicking on a button, etc
[01:05] <maco> i dont know
[01:05] <maco> im still trying to figure out how to test all the available alert sounds in the volume control thing
[01:05] <hggdh> oh, so its volume-control...
[01:05] <maco> if i click "ubuntu" it makes the bongo noise, which i suppose is as an example
[01:06] <maco> no...i havent seen an option for it in there
[01:06] <maco> i havent seen an option anywhere
[01:06] <maco> i would ASSUME somwhere in some audio control app *if* it exists
[01:07] <hggdh> ah thanks. I am going crazy here -- my sound finally started to work again, and I cannot control what sounds and what does not
[01:07] <hggdh> I am almost going back to pulseaudio, so that I will have no sound again :-(
[01:09] <hggdh> anyway. The volume control button on the volume icon does not fire off anything
[01:12] <maco> is it intentional that only 1 slider is available now?
[01:12] <maco> i need to go into alsamixer if i want to change more than one slider
[01:12] <maco> otherwise i *guess* right-click -> preferences, set the volume icon to control slider A. set it. right-click -> preferences, set to control slider B. set B. again for sliders C, D, E, and F
[01:13]  * hggdh has no clue, having been without sound for pretty much one year now. And neither "volume control" nor "preferences" work...
[01:16] <tuxxy__> has anyone got their nvidia card working in Jaunty yet?
[01:16] <tuxxy__> with any driver heh
[01:16] <maco> hggdh: they launch nothing?
[01:17] <x1250> tuxxy__, sure. Try using driver 180 and in xorg.conf: Section "ServerFlags" with Option "IgnoreABI" "True".
[01:18] <tuxxy__> ahhh thats the issue i had thankyou sir, I had the 180 installed but didnt edit the xorg
[01:20] <maco> where can i get an old version of xserver-xorg-input-synaptics?
[01:20] <maco> the current one is really freaking unusable
[01:21] <x1250> maco, from launchpad.net
[01:22] <maco> where though?
[01:23] <hggdh> maco, they launch nuthin
[01:23] <maxb> maco: You could get the intrepid source package and rebuild it in a jaunty environment
[01:24] <hggdh> can't you just downgrade it under synaptic? Or has the older version being deleted?
[01:25] <maco> hggdh: er i was just gonna grab the deb that was in use prior to last week
[01:25] <maxb> Oh, you *can* get it fromlaunchpad if you known where to look
[01:25] <maco> because last week's upload broke things
[01:25] <hggdh> https://launchpad.net/ubuntu/+source/xfree86-driver-synaptics
[01:26] <maxb> https://launchpad.net/ubuntu/+source/xfree86-driver-synaptics/0.15.2-0ubuntu8, choose the right architecture, then the little "Resulting binaries" box on the right hand side, then you get a link to the actual binary package
[01:26] <x1250> maco, jaunty's previous version: http://launchpadlibrarian.net/20438229/xserver-xorg-input-synaptics_0.15.2-0ubuntu8_i386.deb
[01:27] <x1250> hggdh, old versions get deleted :(
[01:27] <hggdh> yes... very fast
[01:27] <maxb> From the archive.... but the librarian seems to hang on to them
[01:28] <x1250> yes, it looks like all versions can be grabbed from librarian
[01:28] <hggdh> but as log as the source packages are there, then it is easy to rebuild locally, and deploy
[01:29] <maco> x1250: thanks
[01:29] <maco> 0.99.3 breaks things really badly
[01:30] <x1250> yes sir it does
[01:31] <tuxxy__> guys I have nvidia driver 180 installed and have added "IgnoreABI" "True" to xorg but no luck I get the same error at boot and have to reconfigur
[01:32] <tuxxy__> so unless I did something wrong I gess it isnt possible
[01:33] <x1250> tuxxy__, try pasting Xorg.0.log (from a failed attempt) in paste.ubuntu.com, and your failed xorg.conf.
[01:35] <tuxxy__> http://paste.ubuntu.com/111087/
[01:36] <tuxxy__> x1250 theres the link it was a standard xorg and I somply added the bottom section for server flags, either way both fail with 180 nvidia drivers
[01:37] <x1250> tuxxy__, is Option "IgnoreABI" "True", with "Option" included :P
[01:37] <x1250> Option "IgnoreABI" "True"
[01:37] <x1250> just copy paste it
[01:38] <tuxxy__> http://paste.ubuntu.com/111088/
[01:38] <tuxxy__> x1250 like that?
[01:38] <shadowhywind> ok guys, heres a very odd problem, my left click on my touchpad, has turned into a "paste" button......
[01:38] <x1250> tuxxy__, also, why are you separating things? Its IgnoreABI and not Ignore ABI, and ServerFlags, not Server Flags
[01:39] <x1250> tuxxy__, right, but you missed the whole ServerFlags section now :P.
[01:39] <tuxxy__> yes ok got it
[01:40] <tuxxy__> http://paste.ubuntu.com/111089/
[01:43] <x1250> tuxxy__, looks ok, but this looks better: http://paste.ubuntu.com/111090/    <----- just some identing, so it looks better
[01:45] <tuxxy__> no luck guys, it says drivers installed but no effects and fan will not stop on card
[01:47] <x1250> tuxxy__, what driver says Xorg.0.log you're using? and what does LIBGL_DEBUG=verbose glxinfo gives you ?
[02:01]  * leleobhz back
[02:02]  * leleobhz back
[02:03] <leleobhz> a strange thing
[02:04] <leleobhz> running users-admin from console free my user line to edit
[02:04] <leleobhz> run from system menu dont unhide notting
[02:04] <leleobhz> can this have some relation with shadow?
[02:41] <hggdh> leleobhz, I am not sure I follow you
[03:42] <pwnguin> whoever said ext didnt fragment should see this
[03:42] <pwnguin> B/dev/sda3: 255368/1181952 files (5.6% non-contiguous), 1769819/2359296 blocks
[03:48] <pwnguin> oops
[03:49] <pwnguin> it seems intrepid tools will tune an ext4 volume, but not mount it =(
[03:54] <Amaranth> pwnguin: it's ext4dev
[03:54] <pwnguin> oh yea
[03:55] <Volkodav> http://desktoplinux.com/news/NS8942465787.html <== that'[s cool
[03:59] <maco> ashp: you had the bug where no outputs are displayed, right?
[03:59] <maco> for audio, i mean
[04:12] <cwillu> pwnguin, nobody should have said ext doesn't fragment.  The fragmentation however is typically minimal, and has very little effect on performance except on very full, very old, or very used-in-exactly-the-right-deliberately-weird-way ext partitions
[04:14] <maco> torrenting without pre-allocating space....while your hard drive is pretty full and it's a large torrent...that'd be "exactly the right weird way"
[04:23] <cwillu> maco, well, that'd be the 'very full' :p
[04:25] <maco> cwillu: well if its a very large torrent that will *result* in very full, thatd also count, i think
[04:38] <pwnguin> oddly, things seem to have worked without touching fstab
[04:52] <emet_> !info mono
[04:52] <emet_> !info mono-mcs
[04:52] <emet_> :\
[04:53] <emet_> !info rocketman
[05:13] <teethdood> is sound broken for someone?
[05:13] <maco> teethdood: no output device in your volume control?
[05:13] <maco> pulseaudio -k && start-pulseaudio-x11
[05:13] <teethdood> maco: no output device yes
[05:16] <teethdood> maco: thanks that works
[05:16] <maco> its a race condition
[05:16] <maco> bug 322374
[06:16] <philip__> is there an option to convert ext3 to ext4? gparted doesn't show it
[06:17] <lucent> philip__: not a complete conversion, no
[06:17] <lucent> ext4 is extents based
[06:17] <lucent> you can use ext3 in a kind of hybrid mode, where it becomes thus unreadable by ext3 driver
[06:17] <lucent> existing files use the existing inode scheme
[06:17] <lucent> newer created files use the extents scheme
[06:18] <lucent> philip__: I caution against using ext4
[06:18] <lucent> there's a data loss bug that bit me twice
[06:18] <lucent> it's not ready yet.
[06:18] <x1250> lucent, you were affected by that bug? ouch.
[06:18] <lucent> yeah
[06:18] <lucent> I have a 1TB volume formatted with ext4dev too
[06:18] <lucent> just kind of praying it never gets bit
[06:19] <x1250> :)
[06:19] <philip__> thanks for the warning
[06:19] <lucent> using root-on-ext4-on-LVM I got bit by the ext4 corruption bug very quickly
[06:19] <lucent> less than a week of regular daily use
[06:20] <lucent> I'm shy to help fix and diagnose such bugs, other simpler tasks I will not wait for others to fix and do the work myself
[06:20] <philip__> so...don't use it even at Jaunty final?
[06:20] <lucent> this ext4 scares the willies out of me
[06:20] <lucent> I would wait for 2.6.31 or 2.6.32
[06:21] <lucent> IMO ext4 is nothing to get excited about, it will not be stable enough for production use before BTRFS gets adopted
[06:21] <lucent> I like the extents capabilities of ext4 for large external (infrequently used and non-mission-critical) volumes
[06:21] <x1250> I'll wait till 9.10 or 10.04, if things goes well
[06:22] <lucent> ha
[06:22] <lucent> more interesting to me are the encrypted home directories
[06:22] <philip__> that's the other thing I wanna ask
[06:22] <lucent> now that encrypted filenames are making their way into the mix, it will get very interesting quickly
[06:23] <philip__> home dir encryption, ready to roll or not?
[06:23] <lucent> ready, if you don't mind it blowing up and having to do some admin work later
[06:24] <lucent> it sure beats the piss out of having the whole block device encrypted, performance-wise
[06:25] <x1250> lucent, but I've read encryption has a rather big impact on performance
[06:25] <lucent> yes, it does x1250
[06:25] <philip__> I've been using mainly truecrypt but it's a pain in the ass sometimes
[06:25] <lucent> moving encryption from block-device based to userspace based means that the kernel can cache things better
[06:26] <lucent> I used block-device (LVM on luks) encryption for at least a year
[06:26] <lucent> it was horridly slow, but unfalteringly secure
[06:26] <emet_> I'm going to do ext4
[06:26] <emet_> I have faith in the kernel hax0rs
[06:27] <lucent> emet_: you have a blindness to my advice
[06:27] <lucent> that is okay
[06:27] <lucent> philip__: home dir encryption in Alpha3 does not encrypt filenames
[06:27] <emet_> :o
[06:28] <philip__> under truecrypt AES128, my external USB drive goes from 13MB/s to 2MB/s transfer rate
[06:28] <lucent> it really doesn't address the issue of hiding one's pornography
[06:28] <emet_> butterfs has awhile to go tho
[06:28] <lucent> USB?
[06:29] <lucent> philip__: if you're encrypting a USB flash drive, I suggest using luks, it's built in support for any Ubuntu Gnome desktop is superb
[06:29] <philip__> one of those pocket  western digital drives
[06:29] <lucent> I can stick my encrypted USB thumbdrive in a LiveCD environment and there's a graphical prompt for the key
[06:29] <lucent> it's bliss
[06:32] <lucent> hey - I need to find answers about a Ruby / TCP/IP programming problem involving libpcap-ruby Pcap::TCPPacket#tcp_data_len != Pcap::TCPPacket#tcp_data.length
[06:32] <lucent> anybody into that stuff?
[06:40] <cwillu> lucent, #ruby? :p
[06:40] <cwillu> lucent, I'd expect one is the buffer size, and the other is the size of the actual data in the buffer, but I don't really know
[06:42] <lucent> cwillu: I'm tryin'
[06:42] <lucent> cwillu: the app I want to make will rip video from flash websites that stream via RTMP protocol
[06:43] <cwillu> lucent, can't you already do that by grabbing the Flash* file from /tmp?
[06:43] <lucent> cwillu: with RTMP streams there's not always a /tmp file
[06:44] <lucent> cwillu: the problem I'm having (even before addressing that RTMP stream) is that packets are failing and being retransmitted
[06:45] <lucent> I need to go back and re-insert packets
[06:45] <lucent> but I don't know how @#%#@@$ big they are
[06:46] <lucent> maybe I'm over thinking this but, how do you take output from pcap and re-assemble TCP packets in-order and replace re-transmitted failure packets
[06:48] <cwillu> rtmp already has the means to request a resend of a dropped packet, no?
[06:48] <cwillu> tcp itself does
[06:49] <lucent> TCP is, so like I get sequence numbers with each packet
[06:49] <lucent> based on TCPPacket#tcp_seq + TCPPacket#tcp_data_len  is the supposed next sequence number
[06:49] <lucent> if the sequence number isn't right, then I'm missing a packet
[06:49] <lucent> if the number is greater, then it's missed
[06:50] <lucent> if it's less, then it's a re-transmit
[06:50] <lucent> I kind of have a system in place that builds a hash lookup of sequence numbers and tells me if they're missing or not
[06:50] <lucent> so ... yeah
[06:51] <lucent> I just need some more interest from people who know what they're doing
[06:52] <cwillu> still not sure why you're not just getting a retransmit then, a dropped packet should get a resend well below the application layer
[06:53] <lucent> cwillu: I'm hooking into pcap though
[06:53] <lucent> it's seeing packets as they come
[06:53] <cwillu> yes, but it should be retransmitted regardless
[06:53] <cwillu> not sure why you need to recheck it
[06:54] <lucent> it is retransmitted, and I'm getting that retransmitted packet :P
[06:54] <lucent> but it's not in order
[06:54] <lucent> 'cause it's retransmitted
[06:54] <cwillu> but...
[06:54] <cwillu> then...
[06:54]  * cwillu 's head explodes
[06:55] <cwillu> rtmp has sequence numbers on the data, why do you need to retransmit it at all?  you have the data, just, use it
[06:55] <cwillu> I'm missing something :)
[06:55] <lucent> I get like A B D E F C G H I
[06:55] <cwillu> you're the receiver, right?
[06:55] <lucent> yep
[06:55] <lucent> I'm just observing traffic on the wire
[06:55] <lucent> I'm not the RTMP client
[09:45] <BUGabundo> guys we were discussing here yesterday data loss
[09:45] <BUGabundo> and tests of disk were asked
[09:45] <BUGabundo> http://paste.ubuntu.com/111181/
[09:45] <BUGabundo> here is my smartctl -a
[10:52] <tbd> hi
[10:53] <tbd> i've installed kde 4.2 on my amd64 jaunty box and i have a "little" problem...
[10:53] <tbd> is wished to know if anyone could help me with it
[10:54] <tbd> i don't get the title bars on the windows and i presume it is a problem with some package, but i don't know if it is so or if it is due to something else
[10:55] <BUGabundo> tdb you need to refresh your window manage
[10:55] <BUGabundo> something like kwin --replace
[10:55] <BUGabundo> for kwin
[10:55] <BUGabundo> or compiz --replace for compiz
[10:56] <tbd> I was not using compiz, then... I'll try the first thing
[10:56] <tbd> thx, BUGabundo
[11:02] <twager> Firefox runs ok yet I cannot do an upgrade as apt telle=s me it cannot find the repos...I cannot ping ubuntu either ny name or ip number any help welcome
[11:12] <tbd> hi again...
[11:12] <tbd> already solved ;)
[11:29] <CoreyOn> Hey, does anyone know if the current daily builds include kde 4.2.0, or is it still too soon for them to be adding that?
[11:44] <cwillu> !info kdebase
[11:44] <cwillu> cor^^^
[11:44] <cwillu> bah, silly CoreyOn
[11:55] <Kano> hi, why is there no new current iso for kubuntu?
[12:12] <BUGabundo> kano no daily?
[12:12] <BUGabundo>  !daily
[12:12] <BUGabundo> Kano: I see it there!
[12:12] <Kano> BUGabundo: nope
[12:13] <Kano> both daily are 2 days old
[12:13] <BUGabundo> http://cdimage.ubuntu.com/kubuntu/daily/current/
[12:13] <Kano> hmm
[12:13] <BUGabundo> yep
[12:13] <BUGabundo> right
[12:13] <BUGabundo> I was seeing alternate
[12:13] <BUGabundo> 29-Jan-2009 05:18
[12:13] <BUGabundo> daily is from 27
[14:19] <philip__> ok I just apt-get smartmontools, but why the heck does it depend on postfix packages?!?
[14:43] <histo> Are we broken rightnow?
[14:43] <histo> ahh well i'm rebooting and finding out i guess.
[15:47] <asraniel> hm.. the new adept (comming from 8.04, never used 8.10) is really bad... any news about kpackagekit replacing it?
[16:08] <BUGabundo1> Friends I would like to invite you all to show up at Tokamak, a KDE summit to discuss the future of Plasma. from day 6 to 9, at Porto (ISEP) Portugal. http://techbase.kde.org/Projects/Plasma/Tokamak2 & http://tuxvermelho.blogspot.com/2009/01/tokamak-ii-no-porto.html
[16:17] <FFForever> any news on a sound fix?
[16:18] <BUGabundo1> FFForever: what prob are you experiencing?
[16:18] <FFForever> after yesterdays round of bug fixes after rebooting i lost sound =\
[16:19] <FFForever> someone else had this problem i advised them 2 wait for a new pulse audio update... but i dunno....
[16:19] <tuxxy__> im still waiting for nvidia issues to be sorted too
[16:19] <FFForever> tuxxy__, what issue?, nvidia works fine 4 me =D
[16:20] <tuxxy__> well no restricted drivers available and when I manually install the 1.80 driver and edit the xorg with ABI ignore it still not work
[16:20] <asraniel> only if you have a new card
[16:20] <tuxxy__> 8600GTS
[16:21] <FFForever> mine words perfectly, tuxxy__ did u use the nvidia-xconfig as root?
[16:21] <tuxxy__> i installed the driver manually 1.80 and run nvidia-xcoinfig yes
[16:21] <tuxxy__> I got the error system is not using driver
[16:21] <FFForever> dunno after i added the ignoreabi it worked for me =p
[16:22] <tuxxy__> with which driver
[16:22] <FFForever> is anyone having a problem using the repo?
[16:22] <FFForever> the 1.80 =P
[16:22] <tuxxy__> damn so you installed 1.80 and added ABI ignore true to xorg
[16:23] <maxb> There is no 1.80 nvidia driver. There is a 180 though :-)
[16:23] <tuxxy__> wonder why it wont work for me maybe cos I am 64-bit
[16:23] <FFForever> i am on 32 =P
[16:23] <FFForever> i don't use x64 even though i could...
[16:23] <tuxxy__> shame :p
[16:23] <FFForever> tuxxy__, does apt-get update work 4 u?
[16:23] <tuxxy__> ok so my question anyone got an nvidia card working on 64-bit Jaunty
[16:23] <FFForever> i cant get updates it won't connect =\
[16:24] <BUGabundo1> nvidia fine for me
[16:24] <BUGabundo1> sound too
[16:24] <tuxxy__> well im not on Jaunt right now
[16:24] <maxb> tuxxy__: Yes, working for me right now
[16:24] <BUGabundo1> I do have the ABI ignore
[16:24] <tuxxy__> BUGabundo1: driver 180 and did you add ABI Ignore to xorg
[16:24] <BUGabundo1> 64bits too
[16:24] <FFForever> it stops @ 54% [Connecting to us.archive.ubuntu.com (91.189.88.31)]
[16:24] <tuxxy__> ok im gonna boot it give it another shit
[16:24] <tuxxy__> oops
[16:24] <tuxxy__> shot
[16:24] <tuxxy__> heh brb
[16:24] <BUGabundo1> tuxxy__: I ddi
[16:25] <BUGabundo1> FFForever: choose another mirror
[16:25] <FFForever> BUGabundo1, how?
[16:25] <charlie-tca> FFForever: Sems slow today
[16:25] <BUGabundo1> AFTER doing an apt-get clean
[16:25] <BUGabundo1> System->Admin->Sources
[16:25] <maxb> waitwaitwait
[16:25] <maxb> You don't want to "apt-get clean"
[16:26] <maxb> Unless you genuinely want to delete all your downloaded .deb files
[16:26] <BUGabundo1> I would recommend
[16:26] <BUGabundo1> so old lists get clean
[16:26] <maxb> BUGabundo1: Are you sure that apt-get clean affects the lists _at all_? I believe it only relates to the packages
[16:26] <BUGabundo1> having several mirrors lists have cause me corruption of packages download in the past
[16:27] <BUGabundo1> ok do it manually then
[16:27] <BUGabundo1> LOLOL
[16:27] <BUGabundo1> sudo rm /var/cache/ something
[16:27]  * BUGabundo1 puts be warning in using sudo rm
[16:27] <BUGabundo1> s/be/big/
[16:27] <tuxxy__> ok guys im in Jaunty, restricted drivers says i have the 180 driver installed and activated yet I cant have effects and my 8600GTS fan is stuck on full speed heh
[16:29] <tuxxy__> heres my xorg http://paste.ubuntu.com/111272/
[16:29] <FFForever> ...
[16:29] <FFForever> run nvidia-xconfig
[16:29] <FFForever> ur not using the nvidia driver....
[16:29] <tuxxy__> VALIDATION ERROR: Data incomplete in file /etc/X11/xorg.conf. Device section "Configured Video Device" must have a Driver line.
[16:30] <FFForever> duh =P
[16:30] <FFForever> add one?
[16:32] <tuxxy__> http://paste.ubuntu.com/111275/ that better?
[16:32] <FFForever> should be =P
[16:32] <FFForever> gimmie 1 min
[16:32] <FFForever> ill post mine =D
[16:33] <tuxxy__> hey thanks FFForever
[16:34] <FFForever> http://paste.ubuntu.com/111278/
[16:34] <FFForever> (i am on a laptop)
[16:34] <tuxxy__> could I just copy paste the xorg from my Ibex installation
[16:34] <FFForever> should work =P
[16:34] <FFForever> but i dunno
[16:35] <tuxxy__> http://paste.ubuntu.com/111280/
[16:35] <maxb> tuxxy__: Prefer not to, the xorg.conf is deliberately edited going intrepid->jaunty by the update-manager
[16:36] <tuxxy__> hmm well Ill give this a shot then try it with just the driver line
[16:36] <tuxxy__> brb
[16:37] <FFForever> Failed to fetch http://mirrors.us.kernel.org/ubuntu/dists/jaunty/main/source/Sources.bz2  Hash Sum mismatch
[16:37] <FFForever> =\
[16:39] <maxb> FFForever: rm /var/lib/apt/lists/mirrors.us.kernel.org_*  and try again
[16:39] <tuxxy__> no luck
[16:39] <FFForever> kk
[16:40] <FFForever> why do uc's waste money on hosting distro repo's?
[16:41] <maxb> tuxxy__: My working xorg.conf http://paste.ubuntu.com/111283/
[16:41] <tuxxy__> http://paste.ubuntu.com/111284/
[16:41] <tuxxy__> I got too much Ill cut some out
[16:42] <tuxxy__> ok one mroe go
[16:43] <FFForever> its archive.channicol.com that is giving me the problems =\
[16:43] <FFForever> that only ubuntu host...
[16:43] <FFForever> Canonical*
[16:44] <teethdood> is the top panel's autohide feature not working for anyone else?
[16:46] <tuxxy__> maxb: I used your exact xorg and received error unable to parse config file
[16:46] <maxb> !
[16:46] <tuxxy__> heh ye
[16:47] <tuxxy__> http://paste.ubuntu.com/111285/
[16:47] <tuxxy__> that what i used
[16:47] <tuxxy__> it did give me less errors than usual though on a positive note heh
[16:53] <tuxxy__> cracked it guys :0
[16:55] <tuxxy__> thanks maxb ;)
[16:55] <maxb> What was the final answer?
[16:57] <tuxxy__> working perfect
[16:57] <tuxxy__> :)
[17:28] <FFForever2> bah..., the new kernel is broken =(
[17:28] <FFForever2> Acpi: aborted because of bad magic numbers, Kernel panic - not syncing vfs unable to mount root fs on unknown wn-block(0,0)
[19:01] <nickrud> is it march yet? No?
[19:01] <Assid> jj in march?
[19:02] <nickrud> no, I'm yearning for jaunty but usually wait for march to test new versions
[20:54] <maco> are there minimal install disks for jaunty yet?
[20:54] <maco> ive got one system that can only be installed using a minimal (net) install disk
[20:57] <Pici> maco: http://archive.ubuntu.com/ubuntu/dists/jaunty/main/installer-i386/current/images/netboot/ seems to exist. But I have no idea if those were ever tested.
[20:57] <maco> meh i'm fine with being a test dummy
[20:57] <maco> that system's not my main one. the one i use for everything is *already* running jaunty ;-)
[20:59] <Pici> maco: Mine too.
[21:00] <Xamusk> how stable is jaunty now?
[21:01] <maco> fairly
[21:01] <maco> i get kernel panics on hibernate
[21:01] <maco> sometimes no keyboard after suspend
[21:01] <ikonia> Xamusk: variable
[21:01] <maco> and there's currently a race condition in pulseaudio that's easily worked around
[21:02] <maco> while the system's running, it seems fairly stable for me
[21:03] <Xamusk> :(
[21:03] <Xamusk> I just got a new box and was checking FS's status to see which would be best now
[21:03] <ikonia> ext3
[21:04] <Xamusk> I currently use reiserfs
[21:04] <maco> ext4 is in and called stable, but make sure you keep backups. and keep the backups on a different fs.
[21:04] <Xamusk> I don't like ext3 much, since I've had corrupted files with it
[21:05] <Xamusk> and also with a wrong powerdown it takes forever to check, not counting that thing that keeps checking after 20 reboots
[21:06] <ikonia> Xamusk: you can control how often it checks after unmounts
[21:06] <lucent> I don't have those problems, Xamusk, I am on laptop hardware which sometimes uncleanly powers off
[21:07] <Xamusk> well, when I lost data with ext3 was a long time ago, but having to configure that stuff manually is a pain, and reiserfs checks much faster after unclean shutdown
[21:08] <mahfiaz> i still keep my /home on ext2 to have undelete
[21:08] <maco> Xamusk: i can tell you why it checks faster
[21:09] <mahfiaz> and two days ago I needed it again, but since I wasn't quick when powering off my machine, I still lost my data
[21:09] <maco> unless im confusing it with xfs, it does writeback checking only
[21:09]  * Assid is ready to give bandwith
[21:09] <Assid> tell me when
[21:09] <maco> so it'll throw away whatever was supposed to be written
[21:09] <maco> and any broken files, in order to get into a consistent state
[21:10] <maco> ext3 tracks what should be written/removed and then does it if it wasnt done before shut down, so you still end up with the changes being committed properly
[21:10]  * maco goes to check that old term paper
[21:11] <maco> ah reiserfs isnt even writeback-only. it's metadata-only.
[21:11] <Xamusk> hmmm
[21:11] <maco>             Since ReiserFS is not always synchronous, journalling cannot always protect against a corrupted file
[21:11] <maco> system if the system is shutdown uncleanly.
[21:11] <maco> xfs is writeback-only. ext3 can be put into writeback-only mode if you like
[21:12] <maco> wait wait
[21:12] <maco> reading more through my paper because this was a while ago...
[21:12] <maco> writeback is just ext3's name for metadata-only journalling
[21:12] <Xamusk> fact is that I've lost data with it, including system files
[21:12] <maco> so this is why i keep old term papers lying around...
[21:16] <Xamusk> :)
[21:30] <lucent> fact, I've lost data with ext4, reiserfs, xfs, fat32, and early revisions of ext3 journalling
[21:31] <lucent> I've never lost data due to an error in stable ext3 operation
[21:31] <lucent> it's air-tight if your RAM is good
[21:31] <lucent> bad ram can lead to corruption very quickly
[21:34] <Xamusk> yeah, I've been there... bad RAM, but no corruption, luckly
[21:38] <bardyr> Hey, i have just upgraded to jaunty and i noticed  the new volume controller, my problem is that now i cant turn of my bass? is there anyway to get all the old options back?
[21:41] <mahfiaz> alsamixer may help you
[21:41] <CarlFK> what is the xorg.conf tweek to get nvidia to work with janty?
[21:41] <mahfiaz>  buf if you find a neater way, let me know
[21:41] <bardyr> CarlFK, get the latest driver
[21:42] <bardyr> it works and it works insanely great
[21:42] <CarlFK> bardyr: Installed: 180.22-0ubuntu2 ?
[21:43] <andersk> Option "IgnoreABI" "True" in the ServerFlags section
[21:43] <bardyr> CarlFK, you need to download and compile the latest driver from nvidia.com
[21:43] <CarlFK> andersk: that's what I think I was looking for
[21:43] <CarlFK> bardyr: no time :)
[21:44] <andersk> Using the driver from nvidia.com is not recommended because it will interfere with the package manager.
[21:44] <x1250> bardyr, try with: alsamixer -c 0
[21:45] <x1250> or install gnome-alsamixer
[21:46] <CarlFK> whats the dpkg thing to build xorg with driver=nvidia?
[21:47] <x1250> with driver nvidia? don't know any.
[21:48] <x1250> dpkg-reconfigure -phigh xserver-xorg will create a default xorg.conf, for driver nv
[21:48] <CarlFK> yeah, it is someting like that
[21:48] <blueyed> CarlFK: just change "nv" to "nvidia" (if you have the latter installed)
[21:48] <CarlFK> my card isn't supported by nv :(
[21:49] <CarlFK> but maybe dpkg-reconfigure -phigh xserver-xorg ... then flip it..
[21:50] <x1250> sure, just add a Driver "nvidia" in section "Device", just under "Configured Video Device"
[21:50] <phixxor> my computer boots from CDR but not from CDRW -- is that a common problem?
[21:54] <lucent> phixxor: yeah
[21:54] <maxb> Really?
[21:54] <lucent> phixxor: cdrw is not bootable on drives manufactured on or before 1997
[21:54] <lucent> also you can't boot from UDF discs usually on equipment made before 2003
[21:55] <lucent> it has to be a fully written and closed ISO session from a blanked CDRW with
[21:55] <lucent> .
[21:58] <phixxor> lucent: ok well this computer came with 98 installed so I think it is new enough but I'm not sure
[21:58] <phixxor> PIII 733mhz
[21:58] <lucent> 98 what installed?
[21:58] <lucent> RAM?
[21:58] <phixxor> heh, no windows
[21:58] <phixxor> that's how old it is
[21:59] <lucent> I thought case modding wasn't popular until at least the PIII 800mhz units were common
[21:59] <lucent> why would you want 98 windows anyways
[21:59] <phixxor> I don't
[21:59] <phixxor> I was just using that as a clue to see how old it was
[21:59] <lucent> what are you talking about?
[21:59] <phixxor> if it came with win 98, it must have been older than 1998
[22:00] <lucent> oh nevermind
[22:00] <phixxor> so could I close the session next time
[22:00] <phixxor> or would it still have trouble
[22:01] <lucent> I stopped using that microsoft garbage after the transition from Microsoft (R) Windows (TM) Windows for Workgroups (TM) 3.11
[22:01] <lucent> open session cdrw discs will *not* boot without specially designed firmware
[22:01] <phixxor> lucent: that is way before I was using computers at all :P
[22:02] <phixxor> so if I specifically close the session, it might have a chance at booting
[22:03] <lucent> phixxor: in layman terms, find an Ubuntu box that is working and has a cd burner, and right click on the ISO image file icon, and go "Write to disc" or some such
[22:03] <lucent> using the Disc burner
[22:03] <lucent> it will work.
[22:03] <lucent> if it doesn't work, it will never work
[22:04] <phixxor> lucent: the iso is on a mac right now
[22:04] <lucent> good luck buddy
[22:04] <phixxor> I think there's an option of closing the session after writing
[22:04] <lucent> I don't know how that mac thing works
[22:04] <phixxor> lucent: thanks
[22:04] <phixxor> I'll try it
[22:07] <phixxor> in fact when I try to boot from it, it throws up the splash screen  (ubuntu live disk)
[22:07] <phixxor> but when I try to start up it waits a while and gives me an i/o error
[22:07] <phixxor> maybe it's a problem with the live cd technology
[22:08] <phixxor> support for older drives
[22:15] <bardyr> phixxor, have you tried a disk check?
[22:15] <bardyr> phixxor, all IO errors i have seen on live cd's have been because the cd was crap
[22:16] <phixxor> bardyr: I can try one; cdrws do tend to have more errors
[22:17] <phixxor> its just that the burning program I used said it verified the disk for accuracy after burning
[22:17] <CarlFK> http://dpaste.com/114461/  Backtrace: 0: /usr/X11R6/bin/X(xorg_backtrace+0x3b) [0x81340eb] 1
[22:19] <bardyr> CarlFK, you need to upgrade to the latest driver if you want to use the nvidia driver
[22:19] <bardyr> ignoreABI is just to unstable to be useful
[22:22] <CarlFK> bardyr: have the url of the i386 ver of NVIDIA-Linux-x86_64-180.22-pkg2.run ?
[22:22] <CarlFK> i accednetly downgraded my box
[22:22] <bardyr> 2sec
[22:22] <bardyr> and you need a newer driver then that
[22:23] <bardyr> ftp://download.nvidia.com/XFree86/Linux-x86/180.27/NVIDIA-Linux-x86-180.27-pkg1.run
[22:23] <CarlFK> thanks
[22:25] <CarlFK> bardyr: what do I need to apt get so it can buid?
[22:25] <bardyr> and that driver runs incredibly good
[22:25] <CarlFK> er, looks like I am setup
[22:25] <bardyr> CarlFK, build-essential
[22:25] <CarlFK> headers is what I am woried about
[22:25] <bardyr> build-essential should handle all that stuff
[22:26] <CarlFK> something did :)
[22:29] <CarlFK> bardyr: still crashing
[22:29] <CarlFK> I think 173 is still intalled
[22:29] <CarlFK> The following packages will be REMOVED:  nvidia-glx-173
[22:30] <CarlFK>  subprocess post-removal script returned error exit status 2 Errors were encountered while processing:  nvidia-glx-173
[22:32] <CarlFK> crap - I ended up with .22
[22:34] <CarlFK> yay.           NVIDIA Accelerated Graphics Driver for Linux-x86 (180.27)
[22:35] <maxb> Does it tell you what's new in .27 anywhere? The nvidia website is still advertizing .22
[22:36] <bardyr> CarlFK, congrats
[22:36] <bardyr> maxb, i think the only difference is that .27 was touched by God
[22:37] <maxb> heh
[22:37] <CarlFK> bardyr: still crashing
[22:37] <maxb> Well, .22 is working for me, so I'll wait for it to land in Jaunty regardless
[22:37] <bardyr> seriously all my gfx errors are gone
[22:37] <bardyr> no more weird compiz
[22:37] <bardyr> CarlFK, what does the log say?
[22:39] <CarlFK> Saw signal 11.  Server aborting.  http://dpaste.com/114472/
[22:42] <bardyr> CarlFK,is that a updated log?
[22:43] <CarlFK> updated ?
[22:43] <bardyr> new
[22:43] <CarlFK> yes
[22:43] <bardyr> (EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not found)
[22:43] <bardyr> uninstall all ubuntu nvidia drivers with --purge
[22:43] <bardyr> and reinstall the official binary one
[22:44] <bardyr> CarlFK, that one is using .22
[22:44] <CarlFK>  --purge ?
[22:45] <CarlFK>  subprocess post-removal script returned error exit status 2  Errors were encountered while processing: nvidia-glx-173
[22:45] <CarlFK> can I just rm /lib/modules/2.6.28-5-generic/kernel/drivers/video/nvidia ?
[22:46] <lucent> as root, you can do damn near anything.
[22:54] <decomp> my mouse and keyboard stop working under kde. work fine on console. any ideas?
[22:54] <decomp> actually dont work under gnome or xfce4 either but was still running kdm
[22:54] <maco_> decomp: join the party
[22:54] <decomp> lol
[22:54] <maco_> oh
[22:54] <maco_> nevermind. mine do work in gnome.
[22:55] <decomp> are you running gdm or kdm?
[22:55] <maco> gdm
[22:55] <decomp> ahhh
[22:55] <decomp> i shall try that then
[22:55] <decomp> tx
[22:55] <decomp> i just love bleeding edge
[22:58] <andersk> I packaged nvidia 180.27 in my PPA, for anyone who wants to try it without confusing their package manager: https://launchpad.net/~anders-kaseorg/+archive/ppa
[22:59] <decomp> gnome and gdm = no dice
[23:01] <CarlFK> ander : The method driver /usr/lib/apt/methods/https could not be found.
[23:01] <CarlFK>  
[23:01] <CarlFK> oh, that isn't the soruces line
[23:02] <CarlFK> andersk: whats the package name?
[23:02] <CarlFK> nvidia-glx-180 ?
[23:03] <andersk> Yes.
[23:03] <CarlFK> i thought there already was a 180?
[23:03] <andersk> Jaunty has 180.22.  My PPA has 180.27.
[23:03] <CarlFK> ah, right
[23:03] <decomp> AH
[23:03] <decomp> i want that then
[23:04] <decomp> ;)
[23:04] <CarlFK> boy I hope this works
[23:04] <andersk> CarlFK: if you have the binary nvidia driver installed from nvidia.com, you probably want to uninstall it before installing an nvidia-glx-180 package.
[23:04] <CarlFK> dpkg: error processing nvidia-glx-173 (--remove):  subprocess post-removal script returned error exit status 2
[23:04] <CarlFK> Errors were encountered while processing:  nvidia-glx-173
[23:04] <CarlFK> I really wish that would go away
[23:05] <decomp> andersk: can you just do dpkg -P on the existing driver?
[23:05] <decomp> i removed all those drivers at one point, i was frustrated lol
[23:05] <CarlFK> gah!(II) NVIDIA GLX Module  180.22  Tue Jan  6 09:58:42 PST 2009
[23:05] <andersk> If you're already using the Ubuntu-packaged nvidia driver, you should just be able to upgrade.  But if you manually installed it from nvidia.com, that screws things up.
[23:06] <decomp> good point
[23:06] <decomp> why is ubuntu the only distro that complains about my BIOS
[23:08] <decomp> ok i already had your repo in as specified above, ive also done several dist-upgrades and upgrades but for some reason i have the 180-22 ver
[23:09] <andersk> Did you do aptitude update or apt-get update after adding the repo?
[23:10] <decomp> yeah its a key issue, nevermind
[23:10] <decomp> ;)
[23:12] <CarlFK> where is it finding .22?
[23:12] <decomp> there we go, downloading now
[23:12] <decomp> my existing driver ver
[23:12] <CarlFK> http://dpaste.com/114483/
[23:13] <CarlFK>  /usr/lib/xorg/modules/extensions//libglx.so ?
[23:16] <andersk> dpkg -l nvidia*180*