[08:03] <MacSlow> hey there
[12:52] <pindonga> morning, I'm having issues getting unity3d to run properly, even though I know my card supports it. Since I reinstalled oneiric I get unity2d even if I ask for the full unity. Is there a log somewhere that says why it's falling back to unity2d?
[13:14] <cwillu_at_work> pindonga, run compiz from a terminal window and see if it bails out
[13:14] <cwillu_at_work> (er, possibly compiz --replace)
[13:14] <pindonga> it did
[13:15] <pindonga> and interesting enough: No composite extension and then segfaulted
[13:15] <pindonga> which is odd, as I have the nvidia proprietary drivers
[13:15] <pindonga> and I have dri in glxinfo
[13:15] <cwillu_at_work> evidently not :p
[13:16] <pindonga> this must be a driver issue I gues
[13:16] <pindonga> I had unity3d working on natty
[13:16] <pindonga> :/
[13:16] <cwillu_at_work> how did you install nvidia?
[13:16] <pindonga> using the restricted drivers app
[13:16] <cwillu_at_work> and this is a fresh install?
[13:16] <pindonga> yes
[13:16] <cwillu_at_work> (i.e., I smell a rat :p)
[13:17] <cwillu_at_work> which version?  the default, or the one with a higher version number?
[13:17] <pindonga> since the install wouldn't work right away, I did jockey-text -e xorg:nvidia_current from the terminal
[13:18] <pindonga> and that gave me a somewhat 'stable' X
[13:18] <cwillu_at_work> I'm guessing that's the main symptom
[13:18] <cwillu_at_work> i.e., that it didn't work right away
[13:19] <cwillu_at_work> do you have xorg-edgers enabled or something?
[13:19] <pindonga> no
[13:19] <pindonga> I should try a newer driver probably?
[13:19] <pindonga> using x-swat ppa?
[13:19] <pindonga> or nvidia_current_updates?
[13:20] <pindonga> I really wish I could forgo the nvidia drivers and just use nouveau :(
[13:20] <pindonga> to have a better 'integrated' experience
[13:20] <pindonga> but that doesn't work for me right now either
[13:20] <pindonga> at least not with unity3d
[13:21] <cwillu_at_work> I'd find out why the drivers didn't install in the first place
[13:21] <pindonga> where should I look for that?
[13:21] <cwillu_at_work> a fresh install :p
[13:22] <cwillu_at_work> whatever told you that the install didn't work the first time is what you'd google for/ask about
[13:22] <cwillu_at_work> anything else (installing more ppas/random packages, etc) is going to cause as many problems as it solves
[13:22] <pindonga> what happened was that I got a frozen X upon starting the fresh install
[13:23] <pindonga> when I looked that up on google it said it that using the jockey-text line would fix it
[13:23] <pindonga> which it did
[13:23] <cwillu_at_work> quick sidebar:
[13:23] <pindonga> the 'frozen' bit at least
[13:23] <cwillu_at_work> if "looked up on google" meant reading an ubuntuforums result, don't do that
[13:23] <pindonga> what should I do next time?
[13:24] <cwillu_at_work> pretend ubuntuforums doesn't exist :p
[13:24] <cwillu_at_work> at least until you've exhausted the launchpad links and such
[13:25] <pindonga> I could try removing the nvidia drivers, deleting xorg.conf and rebooting; that should try to use the nouveau driver and I can build from there
[13:25] <pindonga> that's ok?
[13:25] <cwillu_at_work> (the problem is that you have very low ratio of knowledgeable users to "just do anything to make it seem to work" users
[13:25] <cwillu_at_work> pretty much, although use jockey to do that
[13:25] <cwillu_at_work> it should be able to undo its changes
[13:26] <pindonga> and I will start by making this work on a single screen (most of my pain comes from trying to work with 2 monitors)
[13:26] <cwillu_at_work> nvidia's driver replaces a few other libraries around the system (which is a common cause of trouble with failed installations/removals)
[13:26] <cwillu_at_work> 2 monitors shouldn't affect this much, just use nvidia's gui config tool to make the changes and it should work fine
[13:26] <cwillu_at_work> hmm
[13:27] <cwillu_at_work> it could be that your setup is too large, but if it worked before, that's a bit unlikely
[13:38] <pindonga> cwillu_at_work, so I just run jockey and disable the nvidia driver, I'll also remove xorg.conf and the monitors.xml file.. upon reboot I should be using the nouveau driver by default right?
[13:38] <cwillu_at_work> just run jockey, don't do any other changes
[13:38] <cwillu_at_work> then reboot and see if it works
[13:39] <pindonga> ok, just disabled the driver with jockey
[13:39] <pindonga> I'll reboot now and see what happens
[13:39] <pindonga> tx
[14:10] <pindonga> cwillu_at_work, ok, back, and I have unity3d now \o/
[14:10] <cwillu_at_work> pindonga, \o/
[14:10] <pindonga> cwillu_at_work, this is suprising to me though: I don't have the proprietary drivers enabled in jockey
[14:10] <pindonga> but I still got the nvidia driver
[14:10] <pindonga> is that correct?
[14:10] <cwillu_at_work> ?
[14:10] <cwillu_at_work> see, that sounds like you followed some illadvised advise
[14:11] <cwillu_at_work> how do you know you're running nvidia?
[14:11] <pindonga> lsmod | grep nvidia
[14:11] <cwillu_at_work> check xorg
[14:11] <cwillu_at_work> /var/log/Xorg.0.log
[14:11] <pindonga> in xorg.conf Driver "nvidia"
[14:12] <pindonga> the log file shows the nvidia driver being loaded up
[14:12] <cwillu_at_work> are you sure you didn't at some point install the nvidia sh blob?
[14:12] <pindonga> Loading /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so
[14:12] <pindonga> cwillu_at_work, not manually, for sure
[14:12] <pindonga> so what I found out is that when running with the nvidia driver, I cannot use Xinerama (which is sort-of expected)
[14:12] <pindonga> so I have to use TwinView
[14:13] <pindonga> but that's ok I guess
[14:13] <pindonga> I also know that when I disabled the driver in jockey, it removed the xorg.conf file
[14:13] <cwillu_at_work> just out of curiosity, what does jockey-text -l say?
[14:13] <pindonga> however, even without that file, the nvidia driver was preferred
[14:13] <cwillu_at_work> (pastebin)
[14:14] <cwillu_at_work> yeah, nvidia is chosen elsewhere; the xorg.conf is just because nvidia-settings doesn't know how to do thing in any better way
[14:14] <cwillu_at_work> s/do thing/change settings/, other than the . file in ~
[14:14] <pindonga> cwillu_at_work, http://pastebin.ubuntu.com/732039/
[14:15] <cwillu_at_work> xorg:nvidia_current_updates - NVIDIA accelerated graphics driver (post-release updates) (Proprietary, Disabled, In use)
[14:15] <pindonga> yeah, interesting
[14:15] <pindonga> I'm sure if I go and remove the packages it will use the nouveau driver
[14:17] <cwillu_at_work> you can probably just enable that version in jockey, and things should be sane again
[14:18] <pindonga> cwillu_at_work, ok, I'll try that..
[14:18] <pindonga> cwillu_at_work, if I may, another question and I leave you be :)
[14:19] <pindonga> unity3d 'feels' more sluggish in oneiric than in natty... I guess this may be some defaults that changed? (I know there was a setting somewhere to delay alt+tab for a fraction of a second for example)
[14:19] <pindonga> but I cannot remember where that setting was
[14:21] <cwillu_at_work> pindonga, moving windows and suuch?
[14:21] <pindonga> alt+tab mainly, but also changing workspaces, moving windows, text rendering
[14:22] <pindonga> moving windows is not that bad
[14:22] <pindonga> for example, when I change tabs in firefox, it takes some time to switch
[14:24] <cwillu_at_work> hard to say off-hand
[14:24] <cwillu_at_work> could be a bunch of things
[14:24] <cwillu_at_work> lazy window positioning is broken (on the nvidia and intel hardware I have at least), but that's not what you're seeing
[14:25] <pindonga> cwillu_at_work, what about the alt+tab behaviour? you know of a setting to make it faster?
[14:25] <pindonga> that's my main gripe
[14:26] <cwillu_at_work> ccsm
[14:26] <cwillu_at_work> same answer as always :p
[14:28] <pindonga> what about the "dash" ? it takes forever between I press 'super' and the dash opens
[14:28] <pindonga> btw, not complaining (much) here... just want to know if what I experience is 'normal'
[14:29] <cwillu_at_work> that's a harder problem
[14:29] <cwillu_at_work> I believe you can turn off the blur effect, which may help
[14:30] <cwillu_at_work> I don't believe it's implemented in the same way as other windows though, (something about fbo vs textures or something?)
[14:32] <pindonga> ah, I found something.. at least for the wall switching , the default duration is 0.3 , however if I change that to 0.1 it 'feels' much faster
[14:33] <pindonga> so I guess most of what bothers me might be default settings
[14:33] <pindonga> I'll have a deep look at ccsm
[14:33] <pindonga> thanks for all the help!
[15:50] <Andy80> hi all
[16:18] <Jonii> Hello. Is tis the right place to ask about how to make launcher less likely to accidentally appear
[16:18] <Jonii> Say, make it so that you need to press specific keys to have it pop out
[16:26] <davidcalle> Jonii, I'm not on Unity 3D right now, but have you tried increasing the "Edge Reveal Timeout" in CCSM ?
[17:03] <Jonii> davidcalle: ty, I try it
[17:05] <Jonii> By the way, how do you know if you're using unity 3d or unity 2d? I heard those are indistinguishable, and although my netbook seems to have some sorta graphics device in it, I'm still not certain that it uses 3d version
[17:07] <htorque_> Jonii: if your top panel has a shadow on the desktop, then you are using unity, else unity 2d.
[17:08] <apw> is there a description of the expected semantics of alt-tab in the face of you being 'on' a multi-window app?  about half the time i find alt-tab goes to the next app, and the rest its the other window in the same app.  is this a bug or is there something i am doing to introduce this inconsistancy
[17:09] <Jonii> apw, I figured it goes in to the next if you're in that same app right now, when initiating alt-tab
[17:10] <Jonii> And otherwise it just jumps through unless you wait or press down-button
[17:10] <Jonii> Is this untrue?
[17:12] <apw> half the time it siwtches to the previous application, half the time it seems to switch to the other window int eh same application
[17:12] <apw> something i am doing makes it chose one of these behaviours, but i am damned if i can figure out what
[17:12] <apw> and the inconsitancy is going to make me break some of my hardware shortly
[17:13] <htorque_> apw: how did you get to the multi-window state in the switcher? if i start the multi-window view after initializing the switcher with alt-tab, then it cycles through the windows, when it press alt-tab after starting the switcher with alt-tab-^, then it goes to the next application.
[17:13] <htorque_> it/i
[17:13] <apw> htorque_, i am talking about the 'quick dab' of alt-tab mode
[17:13] <apw> so i am only ever asking for the 'previos thing i was working with'
[17:14] <apw> in my common case i have two terminator windows and a chromium window
[17:14] <apw> starting on the chromium window i alt-tab to one of my terminator windows
[17:14] <apw> the next alt-tab with either take me to the otehr terminator or chromium
[17:14] <apw> but i am not sure which it will do
[17:16] <apw> my hope is to find out what the expected semantics are so i can figure out if they are working or if there is a bug here
[17:19] <apw> ok ... i have finally figured out what makes the difference
[17:19] <apw> it is how you chose the windows which are your previous and next ones
[17:19] <apw> if you are on a third window type and you alt-tab round the ring to terminator, then do the same to chromium
[17:20] <apw> then dab-alt-tab from chrome is ok, then dab-alt-tab will take you to the other terminator window
[17:20] <apw> if you alt-tab to the chromium window, and then left-click to select terminator
[17:20] <apw> then dab-alt-tab will switch terminator <-> chromium
[17:20] <apw> _that_ cannot be intended can it ?
[17:20] <apw> htorque_, Jonii ^^
[17:21] <nhaines> Does dab-alt-tab mean to tap Alt-Tab without continuing to hold Alt?
[17:26] <apw> nhaines, yes indeed just that
[17:27] <nhaines> apw: thanks.  :)
[17:31] <apw> i guess i should just file a bug ?
[17:43] <nhaines> apw: if no devs are here that might be a good start.
[17:52] <apw> https://bugs.launchpad.net/ubuntu/+source/unity/+bug/887683
[17:57] <htorque_> apw: confirmed it, though i have no idea what the intended behavior is.
[18:05] <apw> htorque_, thanks :)  yeah i assume one or the other,
[20:06] <thumper> morning
[20:07] <jaytaoko1> thumper: hello
[20:07] <thumper> hi jaytaoko1