what would be interesting here concerning unity8 (no compiz), will be whether it has h tearing. Atm xmir brings it back, even worse if I kill off compiz & unity. As far as unity7/compiz/xmir - if tearing isn't eliminated then it's just one big step back.
Originally Posted by ventrical On Lubuntu, mir is running unimpeded with only one cursor on a fresh, daily, saucy desktop-i386. hmmmm .. nope .. I don't think so because xorg is comming up in system monitor. unity here, dual cursors. on a terminal window the highest users are Xorg compiz chrome unity-system-co top ... With dual cursors and other symptoms I'm pretty sure it's running xMir.
Originally Posted by ventrical On Lubuntu, mir is running unimpeded with only one cursor on a fresh, daily, saucy desktop-i386. Code: ventrical@ventrical-P4M266A-8237:~$ ps afx | grep unity-system-compositor 2619 pts/0 S+ 0:00 \_ grep --color=auto unity-system-compositor ventrical@ventrical-P4M266A-8237:~$ ps aux | grep unity-system-compositor 1000 2634 0.0 0.0 5664 816 pts/0 S+ 17:54 0:00 grep --color=auto unity-system-compositor edit hmmmm .. nope .. I don't think so because xorg is comming up in system monitor. "\_ grep -color=auto unity-system-compositor" is just grep returning a result on itself (that's why I mentioned you should add a |grep -v grep so as not to get confused by meaningless result
ventrical@ventrical-P4M266A-8237:~$ ps afx | grep unity-system-compositor 2619 pts/0 S+ 0:00 \_ grep --color=auto unity-system-compositor ventrical@ventrical-P4M266A-8237:~$ ps aux | grep unity-system-compositor 1000 2634 0.0 0.0 5664 816 pts/0 S+ 17:54 0:00 grep --color=auto unity-system-compositor
I have itemized my progress today in an earlier post. Just to re-cap, I now have Saucy+mir running Unity, Xubuntu, Lubuntu, Gnome Shell & Kubuntu desktops (not all at once). Taking into account the usual issues of running a development branch just past Alpha stage on a developmental display manager, I would say that things are working well. There are problems logging out and in and with Restart. But shutdown is snappy. Dare I try Cinnamon? It is in the software centre. Well, I am also on btrfs. So, if something breaks it is easy enough to do a roll back. Something for tomorrow, may be. Regards.
It is a machine. It is more stupid than we are. It will not stop us from doing stupid things. Ubuntu user #33,200. Linux user #530,530
Originally Posted by grahammechanical I have itemized my progress today in an earlier post. Just to re-cap, I now have Saucy+mir running Unity, Xubuntu, Lubuntu, Gnome Shell & Kubuntu desktops (not all at once). Taking into account the usual issues of running a development branch just past Alpha stage on a developmental display manager, I would say that things are working well. There are problems logging out and in and with Restart. But shutdown is snappy. Dare I try Cinnamon? It is in the software centre. Well, I am also on btrfs. So, if something breaks it is easy enough to do a roll back. Something for tomorrow, may be. Regards. A few neg i've noticed other than the obvious with slow typing/cursor & the aforementioned h tearing - Here after login plymouthhd tends to max 1 core for no good reason, killing it off shows no ill effects (maybe erroneous reporting, maybe not. Shutdown/restarts are good, logouts remain awful, around 10 sec's (current bug on some hardware
Originally Posted by mc4man "\_ grep -color=auto unity-system-compositor" is just grep returning a result on itself (that's why I mentioned you should add a |grep -v grep so as not to get confused by meaningless result I did add that and it did nothing. Thanks for your observations. I'll have to try some other systems around here. Iv'e only been successful on one machine so far with ATi graphics.
Originally Posted by ventrical I did add that and it did nothing. If you ran ps afx | grep unity-system-compositor |grep -v grep & got nothing then it's the proper result if unity-system-compositor is not running Ex. I'm back on 13.04, no mir, no nothing - :~$ ps afx | grep unity-system-compositor |grep -v grep doug@doug-XPS-M1330:~$ :~$ ps afx | grep unity-system-compositor 2659 pts/0 S+ 0:00 \_ grep --color=auto unity-system-compositor doug@doug-XPS-M1330:~$
Originally Posted by mc4man If you ran ps afx | grep unity-system-compositor |grep -v grep & got nothing then it's the proper result if unity-system-compositor is not running Ex. I'm back on 13.04, no mir, no nothing - Yes . I see .. thanks. Obviously mir is not running on this fresh Lubuntu install on a machine that runs Ubuntu saucy (Unity) just fine under mir. Thanks again.. back to the drawing board edit* ahhh.. I highly suspect that my KVM switcher is not supported.
Last edited by ventrical; July 2nd, 2013 at 01:12 AM.
Originally Posted by mc4man "\_ grep -color=auto unity-system-compositor" is just grep returning a result on itself (that's why I mentioned you should add a |grep -v grep so as not to get confused by meaningless result Here we go another round... Did not we have this sorted in first thread about Mir... ?
Last edited by zika; July 2nd, 2013 at 08:55 AM.
Mir running (or is it xmir) O.K. however the only screen resolution (x)mir will do on this 15.5" TV external monitor is it's max resolution of 1920x1080 which although sharp is pretty small for my eyes. Dual cursors are a bit confusing but usable. systems settings displays won't set resolution, and xrandr isn't successful either although it does call the screen XMIR-1 instead of normal VGA1. So after checking things out for obvious bugs I boot 13.10.0-1 normal xwindows at 1360x768 which is a comfortable read. I've got a 1440x900 external monitor to try - it's drying out after getting splashed with houseplant water.
View Tag Cloud
Ubuntu Forums Code of Conduct