/srv/irclogs.ubuntu.com/2011/11/08/#ayatana.txt

MacSlowhey there08:03
=== MacSlow is now known as MacSlow|lunch
pindongamorning, 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?12:52
cwillu_at_workpindonga, run compiz from a terminal window and see if it bails out13:14
cwillu_at_work(er, possibly compiz --replace)13:14
pindongait did13:14
pindongaand interesting enough: No composite extension and then segfaulted13:15
pindongawhich is odd, as I have the nvidia proprietary drivers13:15
pindongaand I have dri in glxinfo13:15
cwillu_at_workevidently not :p13:15
pindongathis must be a driver issue I gues13:16
pindongaI had unity3d working on natty13:16
pindonga:/13:16
cwillu_at_workhow did you install nvidia?13:16
pindongausing the restricted drivers app13:16
cwillu_at_workand this is a fresh install?13:16
pindongayes13:16
cwillu_at_work(i.e., I smell a rat :p)13:16
cwillu_at_workwhich version?  the default, or the one with a higher version number?13:17
pindongasince the install wouldn't work right away, I did jockey-text -e xorg:nvidia_current from the terminal13:17
pindongaand that gave me a somewhat 'stable' X13:18
cwillu_at_workI'm guessing that's the main symptom13:18
cwillu_at_worki.e., that it didn't work right away13:18
cwillu_at_workdo you have xorg-edgers enabled or something?13:19
pindongano13:19
pindongaI should try a newer driver probably?13:19
pindongausing x-swat ppa?13:19
pindongaor nvidia_current_updates?13:19
pindongaI really wish I could forgo the nvidia drivers and just use nouveau :(13:20
pindongato have a better 'integrated' experience13:20
pindongabut that doesn't work for me right now either13:20
pindongaat least not with unity3d13:20
cwillu_at_workI'd find out why the drivers didn't install in the first place13:21
pindongawhere should I look for that?13:21
cwillu_at_worka fresh install :p13:21
cwillu_at_workwhatever told you that the install didn't work the first time is what you'd google for/ask about13:22
cwillu_at_workanything else (installing more ppas/random packages, etc) is going to cause as many problems as it solves13:22
pindongawhat happened was that I got a frozen X upon starting the fresh install13:22
pindongawhen I looked that up on google it said it that using the jockey-text line would fix it13:23
pindongawhich it did13:23
cwillu_at_workquick sidebar:13:23
pindongathe 'frozen' bit at least13:23
cwillu_at_workif "looked up on google" meant reading an ubuntuforums result, don't do that13:23
pindongawhat should I do next time?13:23
cwillu_at_workpretend ubuntuforums doesn't exist :p13:24
cwillu_at_workat least until you've exhausted the launchpad links and such13:24
pindongaI could try removing the nvidia drivers, deleting xorg.conf and rebooting; that should try to use the nouveau driver and I can build from there13:25
pindongathat'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" users13:25
cwillu_at_workpretty much, although use jockey to do that13:25
cwillu_at_workit should be able to undo its changes13:25
pindongaand 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_worknvidia'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_work2 monitors shouldn't affect this much, just use nvidia's gui config tool to make the changes and it should work fine13:26
cwillu_at_workhmm13:26
cwillu_at_workit could be that your setup is too large, but if it worked before, that's a bit unlikely13:27
pindongacwillu_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_workjust run jockey, don't do any other changes13:38
cwillu_at_workthen reboot and see if it works13:38
pindongaok, just disabled the driver with jockey13:39
pindongaI'll reboot now and see what happens13:39
pindongatx13:39
=== MacSlow|lunch is now known as MacSlow
pindongacwillu_at_work, ok, back, and I have unity3d now \o/14:10
cwillu_at_workpindonga, \o/14:10
pindongacwillu_at_work, this is suprising to me though: I don't have the proprietary drivers enabled in jockey14:10
pindongabut I still got the nvidia driver14:10
pindongais that correct?14:10
cwillu_at_work?14:10
cwillu_at_worksee, that sounds like you followed some illadvised advise14:10
cwillu_at_workhow do you know you're running nvidia?14:11
pindongalsmod | grep nvidia14:11
cwillu_at_workcheck xorg14:11
cwillu_at_work/var/log/Xorg.0.log14:11
pindongain xorg.conf Driver "nvidia"14:11
pindongathe log file shows the nvidia driver being loaded up14:12
cwillu_at_workare you sure you didn't at some point install the nvidia sh blob?14:12
pindongaLoading /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so14:12
pindongacwillu_at_work, not manually, for sure14:12
pindongaso what I found out is that when running with the nvidia driver, I cannot use Xinerama (which is sort-of expected)14:12
pindongaso I have to use TwinView14:12
pindongabut that's ok I guess14:13
pindongaI also know that when I disabled the driver in jockey, it removed the xorg.conf file14:13
cwillu_at_workjust out of curiosity, what does jockey-text -l say?14:13
pindongahowever, even without that file, the nvidia driver was preferred14:13
cwillu_at_work(pastebin)14:13
cwillu_at_workyeah, nvidia is chosen elsewhere; the xorg.conf is just because nvidia-settings doesn't know how to do thing in any better way14:14
cwillu_at_works/do thing/change settings/, other than the . file in ~14:14
pindongacwillu_at_work, http://pastebin.ubuntu.com/732039/14:14
cwillu_at_workxorg:nvidia_current_updates - NVIDIA accelerated graphics driver (post-release updates) (Proprietary, Disabled, In use)14:15
pindongayeah, interesting14:15
pindongaI'm sure if I go and remove the packages it will use the nouveau driver14:15
cwillu_at_workyou can probably just enable that version in jockey, and things should be sane again14:17
pindongacwillu_at_work, ok, I'll try that..14:18
pindongacwillu_at_work, if I may, another question and I leave you be :)14:18
pindongaunity3d '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
pindongabut I cannot remember where that setting was14:19
cwillu_at_workpindonga, moving windows and suuch?14:21
pindongaalt+tab mainly, but also changing workspaces, moving windows, text rendering14:21
pindongamoving windows is not that bad14:22
pindongafor example, when I change tabs in firefox, it takes some time to switch14:22
cwillu_at_workhard to say off-hand14:24
cwillu_at_workcould be a bunch of things14:24
cwillu_at_worklazy window positioning is broken (on the nvidia and intel hardware I have at least), but that's not what you're seeing14:24
pindongacwillu_at_work, what about the alt+tab behaviour? you know of a setting to make it faster?14:25
pindongathat's my main gripe14:25
cwillu_at_workccsm14:26
cwillu_at_worksame answer as always :p14:26
pindongawhat about the "dash" ? it takes forever between I press 'super' and the dash opens14:28
pindongabtw, not complaining (much) here... just want to know if what I experience is 'normal'14:28
cwillu_at_workthat's a harder problem14:29
cwillu_at_workI believe you can turn off the blur effect, which may help14:29
cwillu_at_workI don't believe it's implemented in the same way as other windows though, (something about fbo vs textures or something?)14:30
pindongaah, 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 faster14:32
pindongaso I guess most of what bothers me might be default settings14:33
pindongaI'll have a deep look at ccsm14:33
pindongathanks for all the help!14:33
Andy80hi all15:50
JoniiHello. Is tis the right place to ask about how to make launcher less likely to accidentally appear16:18
JoniiSay, make it so that you need to press specific keys to have it pop out16:18
davidcalleJonii, I'm not on Unity 3D right now, but have you tried increasing the "Edge Reveal Timeout" in CCSM ?16:26
Joniidavidcalle: ty, I try it17:03
JoniiBy 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 version17:05
htorque_Jonii: if your top panel has a shadow on the desktop, then you are using unity, else unity 2d.17:07
apwis 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 inconsistancy17:08
Joniiapw, I figured it goes in to the next if you're in that same app right now, when initiating alt-tab17:09
JoniiAnd otherwise it just jumps through unless you wait or press down-button17:10
JoniiIs this untrue?17:10
=== chrisccoulson is now known as chrisccoulson_
apwhalf the time it siwtches to the previous application, half the time it seems to switch to the other window int eh same application17:12
apwsomething i am doing makes it chose one of these behaviours, but i am damned if i can figure out what17:12
apwand the inconsitancy is going to make me break some of my hardware shortly17:12
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/i17:13
apwhtorque_, i am talking about the 'quick dab' of alt-tab mode17:13
apwso i am only ever asking for the 'previos thing i was working with'17:13
apwin my common case i have two terminator windows and a chromium window17:14
apwstarting on the chromium window i alt-tab to one of my terminator windows17:14
apwthe next alt-tab with either take me to the otehr terminator or chromium17:14
apwbut i am not sure which it will do17:14
apwmy 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 here17:16
apwok ... i have finally figured out what makes the difference17:19
apwit is how you chose the windows which are your previous and next ones17:19
apwif you are on a third window type and you alt-tab round the ring to terminator, then do the same to chromium17:19
apwthen dab-alt-tab from chrome is ok, then dab-alt-tab will take you to the other terminator window17:20
apwif you alt-tab to the chromium window, and then left-click to select terminator17:20
apwthen dab-alt-tab will switch terminator <-> chromium17:20
apw_that_ cannot be intended can it ?17:20
apwhtorque_, Jonii ^^17:20
nhainesDoes dab-alt-tab mean to tap Alt-Tab without continuing to hold Alt?17:21
=== chrisccoulson_ is now known as chrisccoulson
apwnhaines, yes indeed just that17:26
nhainesapw: thanks.  :)17:27
apwi guess i should just file a bug ?17:31
nhainesapw: if no devs are here that might be a good start.17:43
apwhttps://bugs.launchpad.net/ubuntu/+source/unity/+bug/88768317:52
ubot5Ubuntu bug 887683 in unity (Ubuntu) "alt-tab switcher "next" window inconsitent depending on how you navigate between windows" [Undecided,New]17:52
htorque_apw: confirmed it, though i have no idea what the intended behavior is.17:57
apwhtorque_, thanks :)  yeah i assume one or the other,18:05
thumpermorning20:06
jaytaoko1thumper: hello20:07
thumperhi jaytaoko120:07
=== bregma_ is now known as bregma

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!