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