[00:44] Hello all! [00:45] Will the BtrFS be supported soon on the/all of Ubuntu's distros, more or less soon!? [00:48] joe_2010, support is on its way into 10.10. [00:49] Ah, I see... Ok, thanks! === DanaG1 is now known as DanaG === andregondim_ is now known as Andre_Gondim [05:39] anyone here a kde user if so running kde 4.5 without hitch? [05:40] 4.5 rc2 [05:42] is there a kubuntu+1? [06:06] anyone usng kde4.5rc2? === DanaG1 is now known as DanaG [07:57] hi, big issue, i dw the 10.10 alpha 2 64bit..it boots up but if you click "try ubuntu" it goes to a freeze with a X mouse pointer or "install ubuntu" and it goes to a freeze post nw time sync [08:10] repeat, i dw the 10.10 alpha 2 64bit..it boots up but if you click "try ubuntu" it goes to a freeze with a X mouse pointer or "install ubuntu" and it goes to a freeze post nw time sync [08:45] hi [08:45] whats up [08:45] pawan here [08:48] i don't have sound with kubuntu maverick ... how can I troubleshoot please? [09:44] Does anyone know if the 10.10 RC's have fixed the Intel I855 Black Screen Issues ? === yofel_ is now known as yofel [11:31] need lucid support anyone there? [11:31] sorry maverick support [11:32] wth, monospace suddenly looks really squashed here o.O [11:32] !anyone [11:32] A large amount of the first questions asked in this channel start with "Does anyone/anybody..." Why not ask your next question (the real one) and find out? [11:33] got maverick alpha2, on booting i dont get ahead of sysn netwok time [11:34] i did f6 when the cd was booking and got the options screen, then selected try ubuntu (live desktop) with options pci=nomsi it goes ahead with the dots blinking but nothing happnens [11:35] yofel: anychance you can help? [11:36] well, don't think so, but did you see if X started on another vt? (8 maybe) how long did you wait? (and wth does nomsi mean?) [11:38] i waiting for about 10 minutes, cd blinking was all very standard and the hdd indicator was on [11:39] pci=nomsi is a kernal boot line that i have to put to boot ubuntu on both jaunty and lucid installations on the computer [11:39] otherwise i never get to the login prompt === MIH1406__ is now known as MIH1406 [12:34] Hi, I pulled the latest unity version, but still away from this screenshot http://dl.dropbox.com/u/217582/Files%20Shared%20from%20GNOME%20Do/unity_dash01-1951205588.jpg ? [12:36] aboSamoor: what are you actually asking ? [12:37] projectM 2.0 has been out for over a year now will 10.10 include it or is there a reason it wasn't bothered with in lucid? [12:37] ikonia, how can i get that version of unity ? [12:37] Euthanatos: maybe no-ones packaged it, it's that simple [12:37] aboSamoor: what version is it ? [12:37] Euthanatos: log a feature request on luanchpad [12:37] ikonia, i do not know [12:37] launchpad even [12:38] aboSamoor: ok....so how you know you have the wrong version ? [12:39] I do not have wrong one, but I am trying to find the one in the screenshot [12:40] aboSamoor: so if you don't have the wrong one....you have the right one, so what's the problem [12:40] ikonia, it does not look like the screenshot [12:40] I'm wondering if it might have something to do with this: "If you would like to use the new Milkdrop 2.0 support, remember to install the Nvidia Cg toolkit, enable USE_CG during compilation, and install the Milkdrop 2.0 presets." - from sourceforge projectM updates page [12:40] aboSamoor: ok, so contact the person who's screen shot it is, and ask them what theme they are using [12:40] Euthanatos: doubtful [12:41] ok thanks === MIH1406__ is now known as MIH1406 === MIH1406_ is now known as MIH1406 [14:14] anyone around to help me with nvidia-current? [14:14] !nvidia [14:14] For Ati/NVidia/Matrox video cards, see https://help.ubuntu.com/community/BinaryDriverHowto | The ATI and nVidia binary drivers may not be currently installable at the moment [14:15] aha^ [14:32] with compiz, changing theme does not change window border [14:33] anyone know where the bug is. or maybe the bug number ;) [14:42] Is it only me or Ambiance theme buttons look like they are missing the texture and task bar buttons are extremely light in Maverick? Is this a theme issue? [16:07] hi. is libept0 save to remove or should i wait until the dependency conflict resolves itself? [16:27] knittl: libept0 should be safe to remove as libept1 should be used now [16:28] yofel: ok great. thx [16:36] i don't have sound with kubuntu maverick ... how can I troubleshoot please? [16:38] under mixer, i see 2 devices: radeon x1200 (hdmi) and internal audio [16:38] both are unmuted [16:38] yet, no sound [16:41] alakhia: You could try lsof /dev/snd/* as root to see if anything has the devices open [16:42] i see 4 entries .... all of them by pulseaudio [16:43] oh ok, I didn't realise KDE used pa [16:44] ok, what next? is the sound going to HDMI? That wouldn't work since I don't have any hdmi device connected [16:44] what does pactl stat say? [16:45] in particular the Default sink [16:45] where would the default args for passing to chromium be stored btw? [16:45] there was a file afaik [16:45] Default Sink: alsa_output.pci-0000_00_14.2.analog-stereo [16:46] alakhia: And what does lspci show as device 00:14 ? [16:46] shadeslayer: /etc/chromium-browser/default [16:46] penguin42: thanks [16:47] 00:14 has 5 sub entries from .0 to .4 [16:47] what's number 2 ? [16:47] 14.2 is Audio device: ATI Technologoes Inc SBx00 Azalia (Intel HDA) [16:48] and what does 14.0 show? [16:48] PCI bridge: ATI Tech Device 7914 [16:48] alakhia: did you try to move 'Internal Audio' to the top of the list in the KDE multimedia settings? [16:49] alakhia: OK, so that's likely the internal audio is the default sink; so at least PA thinks it is using the internal === jeiworth__ is now known as jeiworth [16:50] in multimedia settings, clicking test on internal works [16:50] :) [16:50] i'll move it up and see [16:53] still can't hear audio from firefox youtube [16:53] hm, works here though [16:55] let me try a local audio file [16:55] alakhia: Try opening a shell and doing pasuspender /bin/cat now leave that there, and try and open a new youtube page [16:55] here the hdmi sink was preferred too and I had no sound, I set the default to prefer Internal audio (PA I guess) and now it works [16:59] local audio via vlc doesn't work [17:00] nothing shows up pasuspender either [17:00] hm, didn't try vlc, let's see [17:00] alakhia: ok, close that pasuspender with ctrl-d other wise it will confuse you more [17:00] alakhia: can you check in the vlc audio settings if it's using pulseaudio for output? [17:01] 'Default' should work too (at least it does here) [17:03] vlc shows 'Default' [17:05] hm... can you set internal audio as the preferred output for all phonon catergories maybe? [17:05] alakhia: Can you get the output of pactl list tto a pastebin [17:06] penguin42: I doubt that the problem is on the PA side, esp. since he said that pressint 'Test' works [17:06] *pressing [17:08] yofel: Ah good point, I was wondering about something as simple as what volume it thinks it is [17:13] sorry ... battery died [17:15] booted back up and now kde's audio settings are back where internal audio is 2nd [17:42] anyone else having issues updating packages? update works great but trying to download all fails [17:42] at least the official repos. trying a different mirror [17:43] it was the mirror [17:43] gnomefreak: Yeh I had a problem before; got a complaint about keys (invalid key? or something?) and a package failed to install - but it seems to be OK now [17:44] penguin42: 404 Not Found [IP: 212.219.56.135 80] using the gb.archive.... mirrors [17:44] oh didn't get that [17:44] testing now [17:44] it is very slow [17:44] dropping the gb. from repos worked [17:44] but I also have a download going [17:45] i pinged it and only got 7% loss [17:46] seems to be dowloading the packages fine, slow for sure but is working here [17:47] mine wasnt too much slower than normal [17:47] like I said the speed is expected due to my download but don't have any issues [17:47] i know apt is a problem seems its a depends issue [17:48] hmmm maybe not [17:49] dropping libept0 but it is going to install libept1. but i will test it here [17:49] 17 updates installed without problem [17:49] next is sound issue :( [17:49] sorry gnomefreak can't confirm [17:50] IdleOne: it removed libept0 but installed libept1 [17:50] renaming package was issue [17:50] hmm 7 packages were not installed, yup it wants to remove libept0 [17:51] its good to remove [17:51] removing it. [17:51] will see what happens [17:52] The following packages will be upgraded: [17:52] apt apt-transport-https apt-utils aptitude libept1 python-apt synaptic [17:52] it was replaced by libept1 [17:52] yup [17:52] same package new version [17:52] no errors [17:52] so still good to go [17:54] can anyone confirm bug 455420? [17:54] Launchpad bug 455420 in alsa-driver (Ubuntu) "Sound is muted at log-in" [Undecided,Incomplete] https://launchpad.net/bugs/455420 [17:55] why was there supposed to be a key change [17:56] gpg: key 437D05B5: "Ubuntu Archive Automatic Signing Key " not changed [17:56] there are 2 [17:56] same here [17:57] gnomefreak: I was having the mute at login but it seems to have stopped for the last week or so [17:57] not sure why but I assume if they were unchanged it is because they didn't change [17:57] i still cant get rid of it. clean install and clean upgrade it still happens [17:59] I have been having an issue booting to gui with the past 4-5 kernels. I have to login to text mode then startx [18:00] have't seen that; I still have to change the set gfxmode= [18:00] besides that no issues [18:00] I get a black screen otherwise [18:00] i saw that once or twice but has cleared up. but i wasnt able to get into a TTY at all when it happened [18:00] IdleOne: Which card? [18:01] nVidia Corporation C61 [GeForce 6150SE nForce 430] (rev a2) [18:01] nvidia 6200 here [18:02] Radeon here [18:16] i have sound now ... thanks penguin42 and yofel [18:17] alakhia_: How did you fix it? [18:17] it was having to set the phonon settings in kde [18:17] set analog as the preferred device and now it seems to have taken it [18:18] thanks for all the help both of you [18:18] no problem [18:51] wth.. [18:51] ? [18:52] the screen on my notebook just froze except that I can still move the mouse [18:52] I've seen X crashes like that before and never understood them [18:52] the last thing in .xsession-errors (fetched over ssh) is [18:52] *** NSPlugin Viewer *** ERROR: NPN_InvalidateRect() invoke: Message timeout [18:53] it's difficult to know if that was a symptom or cause though [18:53] well, it did happen after clicking on a picture in firefox, but that has nothing to do with that thing... [18:53] symptom I guess [18:54] oh GREAT [18:54] my stupid 'swap everything in memory out after waking up from suspend' is back on my eeePC -.- [18:55] * gnomefreak guessing you are on 64bit and nspluginwrapper crashed [18:55] not sure why the screen going blank [18:55] but nspluginwrapper crashes don't normally take out the whole of X [18:55] i know [18:57] why the hell is it swapping? http://paste.ubuntu.com/471547/ I have swappiness set to 0 btw.. [18:57] well something is using lots of RAM [18:58] you're 820M into swap so it's not a tiny thing either [18:59] well, I have 1GiB of memory free.. [18:59] and before I suspended I had no swap usage at all [18:59] yofel: Well you do then; you didn't at some point [19:00] hm, running strace on the frozen X give me http://paste.ubuntu.com/471547/ o.O [19:01] that's your free [19:01] eek [19:01] http://paste.ubuntu.com/471551/ [19:03] like 100 lines per second and no output except for that [19:03] well, except if I move the mouse or press something on the keyboard, so it's not completely frozen [19:04] ah, seems like kwin froze solid [19:04] restart_syscall(<... resuming interrupted call ...> [19:07] yofel: If it happens again I would be tempted to gdb attach to X (from a text terminal) and get a backtrace [19:07] well, I still have the freeze open (I'm on my netbook now) [19:07] let's try gdb [19:09] well, that gives me a trace from within nvidia -.- [19:09] ah well, I'll just kill it [19:47] Is there a way to remove that blue indicator with a spready-arms person from the panel? [19:48] doesn't actually have that on either of his machines; so I'll answer yes without knowing any more on the basis that it's gone from mine [20:30] DanaG: what do you need WRT pulse? (from earlier in the week) [20:38] crimsun: Do you generally care about moans in /var/log/user.log if everything is actually apparently working ok? [20:39] penguin42: yes, but they may not be muzzled [20:39] are the moans the sort of asyncq.c or the sort of alsa-util.c? [20:40] crimsun: I've got one of the oldee 'ALSA woke us up to write new data to the device, but there was actually nothing to write!' (alsa-sink.c), followed by a 'Most likely this is a bug in the ALSA driver 'snd_hda_intel' followed by a 'We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.' and then I've got abunch of ratelimit.c 'events suppressed' entries every so often [20:41] penguin42: hmm, anything even slightly correlated to the ratelimit.c warnings? [20:41] stuttering, popping, etc. [20:41] crimsun: No [20:42] still a bug in alsa-driver, regardless :/ [20:42] crimsun: They are pulseaudio[2011]: ratelimit.c: 955 events suppressed ; I've got one at 18:13 (955 events), one at 18:35 with 904, one at 773 at 19:38 and one at 20:23 with 703 events [20:43] I've been listening to ogg's via Exaile and watching some flash videos on and off over that time [20:43] I'd report it still. [20:44] one report for all of that ? [20:45] I'm subscribed to bug 320875 which is pretty ancient [20:45] Launchpad bug 320875 in ALSA driver "pulseaudio produces lots of log messages" [Unknown,New] https://launchpad.net/bugs/320875 [20:46] penguin42: your hda controller and codec have to match the reporter's precisely [20:46] otherwise you really need to file a separate bug report [20:46] ah ok [20:47] what package should I file it against? pa? linux? One of the alsa ones? [20:48] ubuntu-bug alsa-base [20:48] ok [20:48] it's an alsa-driver Feature [20:52] crimsun: Bug 612122 [20:52] Launchpad bug 612122 in alsa-driver (Ubuntu) "ALSA woke us up to write new data to the device, but there was actually nothing to write (and related VIA VT1708S on Intel Corp 5 series/3400 builtin chipset)" [Undecided,New] https://launchpad.net/bugs/612122 [20:53] (At least I assume it's moaning about the hda I'm using and not the hdmi one that isn't used) [20:54] thanks [21:04] This isnt a snipe at anyone but I think the 'controls' in the new volume applet need to be smaller and more refined.. maybe they arent a permanent fixture anyway but I`m just adding my 2p worth. [21:04] duffydack: please file a bug for that, then. [21:05] whats the difference with 10.10 alpha 1, alpha 2 and the daily build found at: http://cdimage.ubuntu.com/daily-live/current/ ? === booboo is now known as coz_ [21:05] how do i upgrade to 10.10 alpha 2 [21:06] vershan: http://www.ubuntu.com/testing/maverick/alpha2 [21:06] vershan, sudo update-manager -d [21:07] yeah ive done that and have alpha 1 [21:07] how do i upgrade to alpha 2 [21:07] vershan, if that didnt do it then something is up...is alpha 2 out already? [21:07] yeah [21:07] vershan, then that should have updated it [21:07] vershan, sudo apt-get update && sudo apt-get dist-upgrade [21:08] !final [21:08] If you installed a Alpha/Beta/RC version of Ubuntu 10.04 (Lucid Lynx) and have been keeping it up to date, then you are already running the latest version of Lucid Lynx. To make sure, type « sudo apt-get update && sudo apt-get dist-upgrade » in a console. [21:08] er.. that needs fixing.. [21:08] jussi: ^ [21:08] whats the difference between alpha 2 and the daily build found at: http://cdimage.ubuntu.com/daily-live/current/ ? [21:08] thanks ill check guys [21:09] stukad: aplha2 is the daily build of July 1st [21:09] and the "current" one got released today? [21:10] yes, the isos are rebuild every day (if possible) [21:10] stukad, that doesnt necessarily mean the daily will work [21:10] so you should use the current iso, but we don't give any guarantee that it works at all [21:10] oh [21:10] ^^ :) [21:11] are you guys on 10.10 atm? [21:11] for the alphaX snapshots we at least try to make sure that it works somewhat [21:11] I could not install from daily 3 days ago - alternate [21:11] stukad: yes [21:11] had to use alpha 2 [21:11] and then update [21:11] frankly I would no install daily ...think of it as the time of experimentation between alphas :) [21:12] how to check which alpha version is in use [21:12] vershan: impossible, they're just snapshots of maverick on a specific date [21:12] ahhhhhhhhh, now i get it [21:13] vershan: so you're only running alpha2 if you installed maverick on July 1st and never installed any updates [21:13] so if i go ahead installing alpha2, would i need to burn/usb + format/reinstall to get the stable version ones it's out, or could i just grab it with dist-upgrade within alpha 2? [21:13] ok [21:13] stukad, from alpha 2 to release you mean? [21:13] yes coz_ [21:14] stukad: just installing updates is fine, though a fresh install might be cleaner (no obsolete libs that were replaced, etc.) [21:14] stukad: No, it wil lupdate most stuff - there are normally a few small differences that get left around [21:14] stukad, my opinion ...play with what you have indljcing updates until release [21:14] including [21:14] stukad: If you've got alpha 1 installed you might want to remove the unclutter package [21:14] and as mentioned ...then download final and reinstall fresh [21:16] well im at 10.4 atm. so i guess i stick with it until the final release of 10.10 [21:16] stukad, sounds like a good idea :) [21:18] stukad: if you want to try maverick in a vm you could use testdrive, that will sync the daily iso and attempt to boot it in kvm [21:20] well im just looking forward to try out TRIM for ssd's in maverick. cba to do it with a testdrive :/ [21:22] oh, that won't work in a vm obviously ^^ - but you should wait at least until beta if it's the first time you're using a devel release [21:33] heh, just booted the live from today and got 'The installer encountered an unrecoverable error', then failsave-x, choosing to run it in low res does nothing - sudo startx from vt gets me into a session, but I get dbus errors when I try to open ubiquity, nice... [23:13] anyone else having problems with f-spot imports? === haz3lnut_ is now known as hazelnut === hazelnut is now known as haz3lnut