=== XorA|gone is now known as XorA
[09:37] <peter__> ubuntu arm desktop use  gnome?
[09:38] <arune> gnome or unity-2d?
[09:40] <peter__> the gnome depend mono?
[09:41] <peter__> Is unity-2d desktop manage system?
[09:49] <lilstevie> peter__: what version of ubuntu
[09:58] <peter__> lilstevie, 10.10
[11:40] <ogra_> rsalveti, added ...
[11:41] <rsalveti> ogra_: awesome, thanks a lot!
[11:41] <ogra_> :)
[11:43] <rsalveti> ogra_: need to grab you a beer later ;-)
[11:43] <ogra_> heh
[11:44] <ogra_> lets first see that we get you through DMB
[11:50] <rsalveti> ogra_: haha, sure :-)
[11:54] <rsalveti> robclark: check with alf__, my cable is with him
[11:54] <rsalveti> robclark: and he need just for tomorrow's session
[11:54] <rsalveti> robclark: so it should be ok for you to take it
[11:54] <robclark> rsalveti: ok, cool
[13:29] <hrw> DMB...
[13:29] <hrw> rsalveti: you attend today's DMB meeting?
[13:29] <rsalveti> hrw: yup, we both need to attend :-)
[13:30] <rsalveti> hrw: it is schedule for 16:15, am I right?
[13:30] <hrw> yes
[13:31] <rsalveti> cool
[13:32] <hrw> notes from cross-toolchain-uses starts looking nicer
[13:46] <rsalveti> robclark|n900: you'll be able to find alf__ at the mem management summit
[13:46] <rsalveti> guess you're also going to be there
[13:46] <rsalveti> hrw: are you updating it directly at etherpad?
[13:47] <rsalveti> hrw: would also be good to check what use cases we should focus on the second session
[13:47] <rsalveti> hrw: are you creating this additional blueprint?
[13:57] <NCommander> lool: https://launchpad.net/mukluk
[14:00] <NCommander> ogra: session time
[14:00] <ogra_> NCommander, hey, you should make a spec for that
[14:00] <ogra_> NCommander, on my way
[14:07] <hrw> rsalveti: I added to whiteboard
[15:20] <rsalveti> hrw: ok, cool
[15:35] <rsalveti> hrw: congrats! :D
[15:36] <hrw> thx
[15:36] <hrw> rsalveti: your turn in <1h
[15:36] <rsalveti> we'll see :-)
[15:43] <hrw> rsalveti is preparing his 'introduce yourself' speech for DMB meeting ;D
[15:43] <rsalveti> hrw: yeah, don't want to spend more time that I have
[15:43] <rsalveti> have to drive a session at 17:05
[15:43] <hrw> ouch
[16:04]  * ogra_ will be in the room in 5min
=== XorA is now known as XorA|gone
=== zumbi_ is now known as zumbi
[20:22] <dcordes> hi
[20:23] <dcordes> Few days ago I tried some natty omap4 image on htcleo machine and had some heavy glitching in unity-2d . I'm wondering if it's worth retrying now that the release is there.
[20:28] <arune> dcordes: works fine on my ac100
[20:28] <arune> with released natty
[20:29] <dcordes> arune: ok. ogra_ already stated pre release version works on ac100
[20:30] <dcordes> arune: are you able to install normal gnome desktop in your natty release image on ac100 ?
[20:30] <dcordes> I need an alternative to unity-* in natty omap4 images
[20:33] <arune> I installed ogras rootfs for maverick and then did dist upgrade to natty
[20:34] <arune> I think I can choose "normal" gnome and also unity-3d at login but did not try any of them after upgrade to natty
[20:36] <dcordes> arune: cool. can you try the gnome ?
[20:38] <arune> dcordes: tomorrow? bed time now ;)
[20:40] <arune> dcordes: remind me
[20:43] <dcordes> arune: tjhanks
[20:49] <rsalveti> dcordes: well, unity-2d always worked fine for the other platforms
[20:49] <rsalveti> so it could be that you're facing some graphics issues in general
[20:49] <dcordes> rsalveti: that's what I'm suspecting
[20:50] <dcordes> rsalveti: I'm looking to create an easy to install rootfs for use on the hd2 in the fashion of maverick images by phh et al
[20:50] <dcordes> rsalveti: and I don't think using maverick again is progress so I'm considering old gnome session
[20:51] <dcordes> rsalveti: ... in natty since I doubt I can fix unity-2d
[20:53] <dcordes> *maverick images by phh et al. for ac100
[20:53] <rsalveti> well, just use rootstock and build the rootfs you need
[20:53] <rsalveti> you can also install unity-2d for maverick, we have a ppa for that
[20:53] <dcordes> I need it vice versa :)
[20:53] <rsalveti> and actually see if it's a user space issue with natty or if it's actually something triggered by Qt
[20:54] <dcordes> unity-2d is qt based ?
[20:54] <dcordes> my framebuffer driver lacks some functions (I also get x error messages) it's really basic. and I never really tried anything qt so the issue might be centered around qt libs
[20:55] <dcordes> as the efl works flawlessly.
[20:59] <rsalveti> dcordes: could be the case
[20:59] <rsalveti> dcordes: yes, it uses Qt
[21:00] <rsalveti> you can try different graphics system
[21:00] <rsalveti> by default it's using raster
[21:00] <rsalveti> so you could also try x11 (native)
[21:00] <rsalveti> or even a simple Qt application to understand what is the isue
[21:00] <rsalveti> *issue
[21:01] <dcordes> rsalveti: raster ?
[21:01] <rsalveti> if you're willing to fix it
[21:01] <dcordes> rsalveti: that's interesting. I thought I were running normal xorg
[21:01] <rsalveti> dcordes: Qt can use different graphics system engines
[21:01] <dcordes> rsalveti: is it some run time setting ?
[21:02] <rsalveti> like raster (sw optimized), native (x11, using xrender calls) and opengl (using gl or gles)
[21:02] <rsalveti> dcordes: yes, you can call any qt application with -graphicssystem foobar
[21:03] <rsalveti> I know unity-2d is setting raster at the code itself, but last time I checked the command line option has a higher priority when setting the engine
[21:03] <rsalveti> so it should work
[21:03] <dcordes> rsalveti: ok so I will just killall unity-2d ... ?
[21:03] <rsalveti> dcordes: well, unity-2d is a combination of different applications
[21:04] <dcordes> eek
[21:04] <rsalveti> launcher, dash, bar, spread
[21:04] <dcordes> right.. I remember the launcher in ps -A
[21:04] <rsalveti> dcordes: what kind of issues did you have?
[21:04] <dcordes> flickering
[21:05] <dcordes> iirc the unity pricesses automatically reappeared after killing
[21:06] <rsalveti> dcordes: yes, you can't easily kill the panel and launcher I believe
[21:06] <rsalveti> you have someone else looking over it to restart it once it's killed
[21:06] <rsalveti> but I noticed that if you start it quickly you should be fine
[21:06] <rsalveti> like running killall -9 unity-2d-places; unity-2d-places &
[21:07] <rsalveti> dcordes: so I'd first recommend you to try the normal gnome interface
[21:07] <rsalveti> if it works, then you can start a normal qt application and see if that also works fine
[21:08] <rsalveti> and then you can start unity-2d pieces by pieces by hand
[21:08] <rsalveti> until you see the problem
[21:08] <rsalveti> and understand where the bug is
[21:11] <dcordes> rsalveti: thanks! that sounds like a nice plan. Also if I fail debugging unity-2d I still can use the gnome image. What must I add to --seed in order to get a full gnome-desktop ?
[21:11] <dcordes> rsalveti: the ubuntu-desktop meta package equivalent
[21:12] <dcordes> rsalveti: iirc I was desperate about not being able to find a gnome meta package in the pre release natty arm image
[21:26] <rsalveti> dcordes: gnome is still there, so once you installed ubuntu-desktop you should have it
[21:26] <rsalveti> for natty it's still just an option you have while login in
[21:29] <dcordes> rsalveti: seems like I was too fast about removing the rootfs ..
[21:29] <rsalveti> yup :-)
[21:29] <dcordes> rsalveti: assuming it wasn't installed I was searching for the package instead of looking for the option
[21:31] <rsalveti> yeah, a lot of people got confused by the unity migration as the default desktop
[22:06] <dcordes> rsalveti: thanks a lot for the advise. I will let you know the outcome about unity-2d-* -graphicssystem x11 thing
[22:08] <rsalveti> dcordes: cool