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