Hi Marko, On Fri, 2011-01-14 at 15:57 +0000, Marko Vojinovic wrote: > On Wednesday 12 January 2011 18:13:58 William Case wrote: > > Compiz > > 1) make it one package > > yum list compiz* > [snip] I have much the same list as you do, but for gnome. I used packagekit and had to pick each component. At least I thought I had to. That was what worked for me in Fedora 12 & 13. > What exactly do you propose to merge here? > > > 2) fix compiz so that 'place' works with Firefox. > > 3) mesa-dri-drivers should be more explicit about what driver to use for > > what. I wasted over an hour before discovering I needed > > mesa-dri-drivers-experimental to run compiz. > > yum list mesa-dri-* > [snip] > Installed Packages > mesa-dri-drivers.i686 > mesa-dri-drivers.x86_64 > Available Packages > mesa-dri-drivers-experimental.i686 > mesa-dri-drivers-experimental.x86_64 > I needed mesa-dri-drivers-experimental.x86_64 to run and didn't download mesa-dri-drivers.i686. Again, using packagekit. Thanks, I will use yum next time. > I don't know what are all the differences in the two approaches. But for > example, IIRC, configuring compiz is done from the gnome preferences when > compiz iz run integrated, while it is done from ccsm when not integrated. And > such differences. The best way to try it out and see what is actually different. > Create a new user with default gnome system, no desktop effects or anything. > Then yum install fusion-icon and start it from the menu. Compiz will > automatically get loaded, and you'll get the fusion-icon in the system tray, > from where you can access ccsm, set up emerald or some other decorator, tweak > some options, and so on. Then compare and contrast that environment to the > usual one where you start compiz from the Gnome "desktop effects" button (or > whatever it is in the preferences). > I have a 'guest' user that I reserve for just such experiments and will give your suggestion a try. > > > Sessions manager. > > 1) It has taken me well over an hour to chase down what some of the more > > obscure programs and names are starting. > > 2) I found a site that gave me a description and suggestions of which > > services I should automatically start on boot or login. Everybody's > > need is different, but release notes or some Fedora Documentation should > > outline the use of session manager and services. > > As far as boot services go, you can use system-config-services. It has a > reasonable GUI, where you can click on every service and read its description > and purpose in the appropriate part of the window. Then decide whether you > need it or not, and start/stop/enable/disable. > > As for the session services that start after you login into Gnome, that's a > completely different question. :-) Perhaps I wasn't clear. I did find a list of descriptions of services that suggested what I might need. I have turned things off accordingly using system-config-services gui. My nitpick was I wanted to be able to create a sparser program or applications startup. It seemed that the default had about 30 applications starting at login and I was sure I didn't need them all. The tool tip in Gnome that went with each program in the start up menu wasn't all that helpful. The obvious programs that you would want had obvious descriptions. The less obvious were less well defined. For example, name "PolicyKit Authentication Agent" description is "PolicyKit Authentication Agent". What does that do? Do I need it at startup? I turned it off to see. Yes I need it -- can't get to root for many applications without it. Or, What does AT SPI D-Bus Bus do? What does the File Context maintainer do? and so an so on. I can and have chased down each one of these items but it is a PIA without either better tool tip descriptions or a reliable list with explanations. Even a readme somewhere would be helpful. While I am at it, I have had to write a couple of 'sleep' scripts to delay the start up of some programs. The startup menu used to have a 'nice' option. I would prefer a 'move up' or 'move down' button on the startup menu so I could set (some) priorities. Perhaps by getting the compiz to run at startup and using gconf rather than ccsm I can eliminate the need for the 'sleep' scripts. > Marko > -- Regards Bill Fedora 14, Gnome 2.32 Evo.2.32, Emacs 23.2.1 -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
