[00:33] can I get some Intrepid X help here? [00:33] X doesn't start; it complains about not finding the dri2 moduel [00:33] even after I start with a clean xorg.conf [00:34] ...and removed nvidia-glx-96 [00:37] bah [00:37] got /disco'd === lakin__ is now known as lakin [01:59] JontheEchidna: Yes, it complains about dri2; but that's harmless. [01:59] well, X wasn't starting :P [01:59] I ended up doing a fresh install [01:59] yay for /home on separate partitions [02:00] So, that's your problem. X won't start with nvidia-glx-96 or -78, because the driver doesn't work with Xserver 1.5 [02:00] oh [02:00] well it didn't work after I uninstalled the driver and reconfig'd xserver === jtechidna is now known as JontheEchidna [02:13] Man, the nv drivers are blazingly fast [02:14] My sarcasm detector is uncalibrated for IRC. That's sarcasm, right? [02:14] nope [02:15] everything feels more responsivd [02:15] *responsive [02:15] Than the binary driver? I find that hugly surprising. [02:15] Or than vesa? [02:15] than nvidia-glx [02:16] maybe it's the fresh-installness effect [02:16] So, I find that highly surprising. [02:18] What card do you have? [02:20] GeForce 4 MX 440 (64 MB vram) [02:21] Mmm. [02:21] Love that Geforce 2 :) [02:21] yeah... [02:21] I have a VooDoo 2 in the basement [02:21] You could also try !nouveau if you wanted more features and speed out of your 2d. [02:21] Inside a pentium 2 [02:22] Hmm, nouveau might be worth a shot [02:23] but currently I'm upgrading from alpha 3 -> current ;-) [02:23] ...and getting 20 kB/s [02:25] i have a voodoo 5500 upstairs. that thing is huge [02:29] I have 2.6.26 and it won't boot because of the error PCI: Not using MMConfig [02:29] So I have to use 2.6.24 from hardy [05:02] * No1Viking is away: BBL [05:02] !away > No1Viking [05:02] No1Viking, please see my private message [05:38] !away [05:38] You should avoid noisy away messages in a busy channel like #ubuntu, or other Ubuntu channels; it causes excessive scrolling which is unfair to new users. Use the command "/away " to set your client away silently. See also «/msg ubottu Guidelines» === tritium_ is now known as tritium === mendred_ is now known as mendred === crd1b is now known as crdlb [09:50] Is it true that openjdk will be default in Intrepid? [09:52] Yes, it already is so. [09:54] RAOF: Ah, I see, but that is not the same as icedteajava? [09:55] I dunno. Icedtea was only ever meant to be temporary, IIUC. [09:58] Apparently the IcedTea package in Ubuntu and Feodora has been renamed to OpenJDK [09:59] Then I hope they fix the bug stopping people from logging in to the Swedish tax-agency [11:37] i'm having serious issues with the winbind package [11:37] can anyone help? [11:37] it's messed up, and now i can't upgrade or anything [11:38] http://pastebin.ca/1090748 [11:38] i got an error status 2 about it. it is broken at the moment [11:39] quite [11:39] and it's preventing me from doing anything with other packages too [11:40] ie., upgrading [11:40] flash 10 got broken as well since friday's update [11:41] mine doesn't seem to be having too much trouble... [11:41] just a couple issues i noticed from the start after upgrading [11:41] white artifcats on black, and displaying underneath iframes in firefox & seamonkey, instead of over like it used to [11:42] no probs with the package itself though [11:43] any idea how to fix this winbind issue? [11:43] this is on my i386 test puter .. 64bit is bulletproof so far [11:43] i386 here too [11:43] nope [11:43] >.< [12:09] can't even forcefully remove the damned thing [12:39] tanath: It tells you in the error what to do... in the postinst script, remove the ;; and try again [12:39] tanath: wait, no... in the /etc/init.d/winbind script... 'status' section... do that [12:40] tanath: only the one between the lines starting 'status_of_proc' and 'echo "Usage' though [12:41] tanath: then apt-get -f install or whatever (apt-get upgrade again will do it too) and voila, no more issue. [12:43] are you saying update-manager is at fault and winbind is not broken then? [12:44] G_009: No, that script has incorrect syntax, and the package manager can't correct it. [12:44] G_009: That file is part of that package, so in essence, the package is indeed broken. [12:44] i c [12:47] G_009: Of course, editing /etc/init.d/winbind then running update-manager again would also be another alternative way to "fix" the issue, proving that update-manager has nothing to do with it... [12:49] right [12:51] there are some daily updates i wanna check, but if the issue is still there i might give that workaround a go [12:51] effectively, there is a winbind update [12:52] * G_009 crosses fingers [12:52] G_009: I'm entirely up-to-date currently, and the issue still persisted... although I'm not using the main servers, so maybe they haven't propagated yet [12:55] you didnt read the topic before trying to upgrade? [12:55] "new pre-removal script returned error exit status 2" [12:56] gnomefreak: huh? [12:56] G_009: still complaining about line 54? [12:56] fde: intrepid is broken the error you are getting isnt update-manager but a package error [12:57] line 54 again [12:57] and we do NOT recommend users upgrade at this time. should explain it [12:57] gnomefreak: I'm not getting the error, I fixed the issue already... and am trying to advise G_009 on how to fix it too. [12:57] gnomefreak: you're a little late in the convo [12:57] ah ok well whom ever is getting it [12:58] G_009: i cant sit here and watch all day i have 27 other channels to watch [12:58] G_009: See above, remove the first ;; from the status stanza in /etc/init.d/winbind and try again. [12:59] gnomefreak: then you shouldn't chime in with less than useful comments... [13:00] fde: usefull comment == do not upgrade intrepid is broken unuseful comment == upgrade it works for me [13:00] sure.. i'll try later though.. in reality am not really affected by winbind breakage.. cool to know a way around it nonetheless [13:00] gnomefreak: If no one uses the devel branch, it will be released in a more buggy state... anyone should be able to use it provided they aren't in a production environment. [13:00] gnomefreak: No one said "upgrade it works for me" [13:01] fde: no that isnt true testing starting at beta 1 is for users to test alpha is not for users due to the ever changing apps [13:01] fde: it was an example [13:02] i know you are not ill willed, gnomefreak .. but you are still off in your own context right now [13:02] gnomefreak: meh... well I was advising someone of a relatively simple fix for an annoying issue... that he isn't fixing it now proves that maybe he shouldn't be using a devel branch... I have used sid and experimental since 2000 or so, I'm used to breakages [13:02] G_009: your system isnt broken? [13:03] not quite.. just recently flash and this winbind issue.. [13:03] sid is nothing like our devel branch think of it more like experimental in debian [13:03] gnomefreak: No, one package is broken, and I provided a simple fix... so it is his own decision that the system is still not fixed... this tells me he is intimidated by the fix, and thus shouldn't be using unstable systems. [13:03] gnomefreak: uhh... I stated experimental [13:03] fde: no alot are broken just one package that you use is broken [13:04] am not intimidated by the fix.. i just dont wanna do it now.. jeez.. [13:04] fde: i know but sid isnt like our devel branch was my point [13:04] * G_009 passes fde a shoe [13:05] gnomefreak: I have encountered less breakage in Ubuntu's devel branch than in Sid over the years :/ [13:05] if that error happened during upgrade to intrepid from hardy i wouldnt put it off or atleast run sudo dpkg --configure -a [13:05] gnomefreak: that would do _nothing_ [13:05] fde: depends on what you use it for [13:05] fde: yes that would configure all other packages [13:06] that may have not been [13:06] fde: normal every day upgrade no you are right but from hardy to intrepid other packages might not be configured due to failure [13:06] gnomefreak: ugh, you're not getting it, and you're not being helpful at all... the error is as good as fixed, your assistance isn't required. [13:06] dfon your system [13:07] fde: on your system [13:07] fde: his it is not [13:07] gnomefreak: on _all_ systems, considering I told him the fix >:| [13:07] if kernel wasnt configured he wont beable to boot it [13:07] gnomefreak: it's not like it would have removed older kernels though. [13:07] fde: if he shuts it down without dbus kernel or others he might not beable to boot in regual mode [13:08] i didnt just upgrade to 8.10 i've been on it since alpha1.. relax [13:08] hint easie rot run the command and not worry about why it wont boot later [13:08] gnomefreak: lol, you're making a huge issue out of something _really_ simple... stop [13:08] G_009: thats why i said if it was hardy to interpid upgrade [13:08] fde: my comment was to G_009 not meant for you. [13:09] duly noted [13:09] gnomefreak: he has already stated nothing else is wrong with his system. [13:10] G_009: Please do the fix I told you so this can be dropped, thanks.... it'll take like 5 secs... it's at the bottom of the file [13:10] fde: and your point? i was giving him helpful hints but you think i am wrong but i cant say i am since i know my devel cycle seeing as i well am a dev [13:10] gnomefreak: So because I am not a MOTU or Core dev, I can't know it as well as you? [13:11] fde: im not neither either but i package for ubuntu. that isnt my point. once i again i said if you upgraded from hardy to intrepid it should be fixed [13:11] * G_009 sits back to watch cat fight [13:11] not meant for daily updates [13:12] gnomefreak: At times, what you're saying is very valid, but this isn't one of them... it is a simple syntax error in a very basic script... no one has stated they upgraded to intrepid while the issue was applicable. [13:13] gnomefreak: Currently, all you're doing is blowing something out of proportion. [13:13] fde: seing as i didnt see the whole thing due to other things i have to have done this weeke3nd it was a very valid comment since i didnt see him say he was on intrepid for a while [13:14] fde: you can stop anytime you like or i will stop it all together but you midunderstood what i said/meant and it wasnt to you anyway [13:14] gnomefreak: So your ignorance to the topic at hand makes it ok to blow it out of proportion, especially seeing as though when you chimed in, on the same screen - not even requiring a scroll up - was the fix? [13:14] argumentatively i have to add that was not where the convo started either [13:16] fde: im sorry you ffeel me giving him a hint was bad. but you really shouldnt have a problem with him running it since it cant hurt him. and yes you are right maybe he shouldnt be running it but he is [13:16] all is good, though .. am still typing which probably means am still logged in somewhere [13:17] fde: oh and be careful with the words you throw around please [13:17] gnomefreak: I'm saying telling him he shouldn't run intrepid, and giving him advise that wasn't applicable, wasn't necessary. [13:17] i didnt say he shouldnt i said read topic and than gave the portion of the topic i meant [13:18] read topic before upgrade [13:19] but i didnt upgrade.. i did a fresh install.. so i dont know.. maybe you're confusing me with someone else.. too many #rooms.. i know.. [13:19] gnomefreak: the topic provides scare tactics to avoid most from running intrepid... since warty, I have ran only the devel stuff with little issue. I agree many Ubuntu users shouldn't even consider it, but he has and his current issue is easily fixed. [13:19] G_009: like i said since i couldnt/didnt read the full log i wasnt able to see that part and the command is valid either way just less breakage if you didnt upgrade from hardy when this happened [13:20] fde: no it doesnt. you feel comfortable running it but others should be careful if they cant fix it [13:21] it doesnt say dont upgrade it says we recommend that you dont [13:21] gnomefreak: Exactly, but we can't change the fact that he is running it, as is the initial complainer... neither should be if they can't decipher a simple error, but it's not our say really. [13:22] fde: i didnt say he shouldnt run it that was yoru comment but either way go ahead and help him if he wants it [13:22] gnomefreak: I already had before you even stated anything... [13:22] gnomefreak: which in lies my current real issue with you :P [13:22] fde: well i hope he can remember it than [13:23] fde: my issue was he didnt fix it and since he didnt it can cause other packages from being configured [13:23] * gnomefreak didnt ask for a list of what upgrade he is doing [13:23] i havent had updates today [13:23] oh yes i did update-manager === bazhang_ is now known as bazhang [13:24] gnomefreak: then he should live and learn... maybe the resulting breakage will deter him from running devel stuff in the future... which I think you'll agree is probably for the best [13:24] look, i wasnt like "oh my gosh, please help!!" .. i was just commenting on it and fde came along; we were just talking about it.. winbind breakage doesnt affect my 'productivity' whatsoever.. if you were under the impression i was screaming for help on this issue you're pretty much wrong [13:24] gnomefreak: winbind's last 2 upgrades have had the same syntax error in the status stanza [13:24] i do agree maybe he shouldnt but i dont know his knowledge of packages/files filesystems [13:25] you two already assumed i dont know nothing .. so [13:25] G_009: I know, but the person I originally replied to was... you simply wanted clarification, but the issue was relatively simple, and you were unable to decipher it... and indeed guessed an issue that was entirely off base. [13:25] * gnomefreak doesnt use winbind [13:25] G_009: neither of us said that [13:26] gnomefreak: intrepid seems to turn it on by default... it is basically DNS for CIFS... so if you don't encounter windows boxes, you shouldn't need it... [13:26] gnomefreak: in saying that, seeing ugly errors spurted out all over the screen bothers me, so I _have_ to find a fix... it's part of the fun I enjoy with Linux :) [13:26] fde: out of 7 pcs one runs winxp and thats only so i can help friends in the middle of night yelling it broke [13:28] If I ran only stable branches, I'd probably wander back to Windows as Linux would become boring to me. [13:29] as a side note, i didnt encounter winbind issue on 64bit [13:30] G_009: That's pretty strange, are the version numbers the same on both archs? [13:31] gnomefreak: I only help Windows users if they pay me to do so... they're used to such things costing money :) [13:31] yup.. just checked.. same version on both architectures [13:32] Helping Linux users is my primary way of giving back though... [13:32] G_009: cat /etc/init.d/winbind | tail -n10 ... throw that up on paste.ubuntu.com for me please [13:33] from ? [13:33] G_009: the 64bit machine, sorry [13:37] http://pastebin.com/m6b221f4b [13:39] it is the exact same thing on both system too === catweazle_ is now known as catweazle === jtechidna is now known as JontheEchidna [13:44] G_009: Very strange... hmm [13:44] yup [13:45] G_009: For future reference though, state the users nick when replying... I had gone to a different channel awaiting your response... [13:46] G_009: I have no idea though why one system would complain while the other doesn't... makes absolutely no sense [13:46] yah.. the wonders of computerization [14:45] to use intrepid in vmware you'll have to disable the module snd_pcsp with modprobe -r snd_pcsp, but after every reboot, it loads the module again, how can i stop this? [14:47] GSMX: blacklist it [14:48] GSMX: see /etc/modprobe.d/blacklist, iirc. [14:48] thanks === catweazle_ is now known as catweazle [15:08] hey guys. what alpha version is intrepid at? [15:09] 3? [15:10] sounds good, cheers zniavre1 [15:10] closed too fast ... [15:10] hehe ;~) [15:13] Hobbsee: Any idea why that module is being loaded now? It also through me on a normal desktop system... if there is a soundcard detected, it should always take priority over the pc speakers imo... [15:14] yes, it's a bug. [15:15] Hobbsee: hmm, ok... I had already fixed it the first time I was trying to figure out why my music wasn't coming from the speakers... heh... was just really strange === catweazle_ is now known as catweazle [16:19] huh gnome/x ignores my nodeadkeys setting. [16:20] gnome most likely, since xev shows ^ immediatly [16:22] well, gnome-keyboard-properties refuses to set the "default layout", just ignores my clicks. I guess that's the cause. [16:56] humm, setting the "default layout" does not solve this issue. Starting a new plain X (xinit -display :1 -- -ac :1) did have the correct layout set. Any ideas? === catweazle_ is now known as catweazle [17:40] Is NM 0.7 in Intrepid? [17:43] 0.6.6 here [17:44] nm-applet? [17:45] same in fact [17:46] zniavre1: I see, thanks [17:55] uh upgrading ibex since an hour or so, still not readz, just finished nvidia proprie [17:56] now i applz the updates that wants certain packages to be uninstalled 588 new, 11 to be uninstalled [17:56] how to fix my keyboard layout?? [17:56] its english z__ [17:57] i want it to be de_DE [17:57] including GDM [18:37] fde: your winbind edit does not work [18:37] fde: and it's complaining about a ) not the ;; [18:39] G_009: did you manage to get winbind fixed? [18:43] anyone know how to fix the winbind package? i can't do anything until it's fixed === catweazle_ is now known as catweazle [18:58] tanath: rm /etc/init.d/winbind [18:58] that does it? [18:59] sweet [18:59] did it for me :-) [19:00] Hew: that worked. thanks :) [19:00] tanath: no worries, glad I could help [19:02] so here i am running with fully current ibex and got one issue: my keyboard has got keys for volume up and down and mute, after ibex they dont work anymore any ideas? [19:04] cypherdelic: mine stopped working too [19:05] even have a gnome media keys script. still don't work [19:05] i think it's the keyboard layout [19:05] a couple people were complaining earlier about kb layout not working right too [19:05] hm i already fixed mine from us back to de in xorg.conf [19:05] :( [19:06] damn that was my best way to dontrol volume from my couch :D [19:06] haha [19:07] a number of things have stopped working since upgrading :P [19:07] my scroll wheel doesn't work right anymore either [19:07] what else? [19:07] tanath: bad, im a lucker cus emin eworks [19:07] at least the thumb buttons work in Fx [19:08] though not in nautilus/dolphin or anything else anymore [19:08] generic 105-key (intl) PC layout here.. volume keys work (desktop keyboard) [19:08] i just miss keyboard volume buttons [19:08] i can scroll in a few gnome apps when the curser is right over the scroll bar, and sometimes it'll scroll horizontally... [19:08] heh, i miss my scroll wheel more :P [19:08] G_009: how can i fix mine? [19:10] i dont know.. but thats the layout that i got and it works, maybe you should try it [19:11] G i had that selected too so that is not causing problems [19:11] my 'default' is generic 104 [19:11] i have an ms kb, but not one that seems to fit the given ms models. and i can't find out which it is anymore [19:11] can no longer find it on the site [19:13] i don't get why the kb shortcuts don't work though. it detects the keys in the kb shortcut applet, but then doesn't do anything when i press them [19:13] btw, i did rm /etc/init.d/winbind and it worked here too.. easier than "editing" anything [19:13] indeed [19:15] G_009: can i safely execute that command too??? [19:16] sure.. IF you are having the winbind bug [19:16] even if not, you could always reinstall winbind if it were a prob [19:17] G_009: you didnt highlighted anyone, is this related to our keyboard shortcut bugs? [19:17] winbind is not a keyboard issue.. thats something else.. [19:18] G_009: to who were you talking this rm winbind???? [19:18] tanath and i had the same issue.. that fixed it [19:19] G_009: yeah, same here. saw your earlier comment too :) [19:19] that wasnt directed to you, cypherdelic [19:19] cypherdelic: winbind package was broken [19:20] hm so you dont have a idea how we can fix our shortcut probs? i can press that keys in keyboard shutcuts too and they get detected [19:21] tanath: [19:21] not sure [20:19] I wanted to test intrepid in virtualbox, but I always get kernel panic when booting from the cd.. (I downloaded images from the linux tracker) [20:49] My Keyboard Shortcuts still doesnt work since upgraded to Ibex, any ideas? === DreamThi1f is now known as DreamThief [21:12] kane77: that's a known issue [21:12] kane77: let me find the bug report [21:13] kane77: bug 246067 [21:13] Launchpad bug 246067 in linux "Kernel panic during boot in VirtualBox with kernel 2.6.26.3-generic" [High,Confirmed] https://launchpad.net/bugs/246067 [21:40] afflux, thanx.. I was getting desperate and downloaded more than 4 different iso's :D [21:40] hehe [21:40] it's not that fun with 60KB/s :) [21:43] afflux, hmm one advice in the bug page helped to make it boot.. but it's rather sluggish.. [21:44] kane77: yes. It didn't work for me, iirc, but haven't tested that very extensive [21:46] actually it's not running, it freeze :( [21:46] guess I'll wait till it's fixed [22:07] Sry to bother everyone but I'm having Prevu problems and was directed here (although I'm using 8.04 at the moment). I used Apt-get to install it, and when I attempt 'sudo -E prevu-init' I get the following: Failure trying to run: chroot /var/cache/prevu/builds/10290/. mount -t proc proc /proc (then says pbuilder: debootstrap failed). I can give more context if anyone would have a guess [22:21] anyone? [22:27] Hi everybody [22:28] do the ati (fglrx) drivers already work with the new Xserver? [22:49] RAOF: is your ppa the preferred way of getting nouveau? [23:02] My Keyboard Shortcuts still doesnt work since upgraded to Ibex, any ideas? === jtechidna is now known as JontheEchidna