Page 1 of 2

LXAppearance and LXSession

Posted: 15. Sep 2010, 10:59
by zAchAry
Users of SalixOS Xfce edition might have noticed that LXAppearance does not work for them.
While LXAppearance is not depend on LXSession in order for it to just work it does need LXSession (command: lxsession) to run in the background so changes will appear.

Please add the package labeled as lxsession to the SUGGESTS list of the package labeled as lxappearance.

from: salix.enialis.net/i486/13.1/PACKAGES.TXT

Code: Select all

PACKAGE NAME:  lxappearance-0.4.0-i486-1tm.txz
PACKAGE LOCATION:  ./salix/xap
PACKAGE SIZE (compressed):  45 K
PACKAGE SIZE (uncompressed):  180 K
PACKAGE REQUIRED:  atk,cairo,expat,fontconfig,freetype,glib2,gtk+2,libpng,libX11,libXau,libxcb,libXcomposite,libXcursor,libXdamage,libXdmcp,libXext,libXfixes,libXi,libXinerama,libXrandr,libXrender,pango,pixman,zlib
PACKAGE CONFLICTS:  
PACKAGE SUGGESTS:  
PACKAGE DESCRIPTION:
lxappearance: lxappearance (gtk theme switcher)
lxappearance: 
lxappearance: LXAppearance is the standard theme switcher of LXDE. Users are able to
lxappearance: change the theme, icons, and fonts used by applications easily.
lxappearance: 
lxappearance: 
lxappearance: 
lxappearance: 
lxappearance: 
lxappearance: 
lxappearance: 

Code: Select all

PACKAGE NAME:  lxappearance-0.4.0-i486-1tm.txz
PACKAGE LOCATION:  ./salix/xap
PACKAGE SIZE (compressed):  45 K
PACKAGE SIZE (uncompressed):  180 K
PACKAGE REQUIRED:  atk,cairo,expat,fontconfig,freetype,glib2,gtk+2,libpng,libX11,libXau,libxcb,libXcomposite,libXcursor,libXdamage,libXdmcp,libXext,libXfixes,libXi,libXinerama,libXrandr,libXrender,pango,pixman,zlib
PACKAGE CONFLICTS:  
PACKAGE SUGGESTS:  lxsession
PACKAGE DESCRIPTION:
lxappearance: lxappearance (gtk theme switcher)
lxappearance: 
lxappearance: LXAppearance is the standard theme switcher of LXDE. Users are able to
lxappearance: change the theme, icons, and fonts used by applications easily.
lxappearance: 
lxappearance: 
lxappearance: 
lxappearance: 
lxappearance: 
lxappearance: 
lxappearance: 
edit: Please add a CSS Code to bound and restrict large codes (hight & width)

Re: LXAppearance and LXSession

Posted: 15. Sep 2010, 11:04
by thenktor
AFAIK LXappearance just modifies the .gtkrc-2.0 file. Nothing else is needed.

Re: LXAppearance and LXSession

Posted: 15. Sep 2010, 11:26
by zAchAry
This is what it does but it started to effect the environment after installing and running lxsession.

One thing I really like is modifying different themes for the Root account (I can't do that with xfce4-appearance-settings) by entering

Code: Select all

gksu lxappearance
Please see the screenshot of this bmpanel theme at Box-Look.org
Very neat, can be highly useful if you have no warning that you're using the Root account with any GUI(ed) application and for any reason you haven't noticed that!

But where does lxappearance stores the modifications for Root?

Re: LXAppearance and LXSession

Posted: 15. Sep 2010, 11:30
by thenktor
zAchAry wrote:But where does lxappearance stores the modifications for Root?
in /root/.gtkrc-2.0

Re: LXAppearance and LXSession

Posted: 15. Sep 2010, 11:32
by zAchAry
thenktor wrote: in /root/.gtkrc-2.0
I was searching at / :roll:

Re: LXAppearance and LXSession

Posted: 15. Sep 2010, 12:23
by ray
Change the theme for root? Why would you want to do that?
As long as the theme is stored in /usr/share/themes, it will be automatically be applied to apps you run as root.

Offtopic:
+1 to the issue mentioned by zAchAry, we could use a code tag that has scrollbars.

Cheers,
ray

Re: LXAppearance and LXSession

Posted: 15. Sep 2010, 14:34
by thenktor
ray wrote:Change the theme for root? Why would you want to do that?
As long as the theme is stored in /usr/share/themes, it will be automatically be applied to apps you run as root.
No, it won't in Openbox, LXDE and other window managers.

Re: LXAppearance and LXSession

Posted: 15. Sep 2010, 14:41
by ray
thenktor wrote:
ray wrote:Change the theme for root? Why would you want to do that?
As long as the theme is stored in /usr/share/themes, it will be automatically be applied to apps you run as root.
No, it won't in Openbox, LXDE and other window managers.
Hmm, Do you have any idea why? :?:
I only use Xfce/Gnome and that works for me, so i did think it was pretty much universal.

Cheers,
ray

Re: LXAppearance and LXSession

Posted: 15. Sep 2010, 19:32
by Duncan_Idaho
maybe it has to do with how gnome and xfce manage their sessions, I guess

Re: LXAppearance and LXSession

Posted: 15. Sep 2010, 21:20
by zAchAry
ray wrote:Change the theme for root? Why would you want to do that?
As long as the theme is stored in /usr/share/themes, it will be automatically be applied to apps you run as root.
You're right.
I'm not installing themes to the /usr/share/themes when downloading them from Box-Look.org, Xfce-Look.org,
deviantART.com etc. etc., instead I'm installing to ~/.themes and ~/.icons and when I'm using xfce4-appearance-settings
(with xfsettingsd running at the background) and applying/selecting themes and icons that are located at ~/.themes
and ~/.icons, the applications running as root will be displayed with the most basic icon pack (hicolor, or another similar
name) and the good old Raleigh gtk theme but if I'm selecting a theme that IS located at the directory /usr/share/themes
changes will apply for both, accounts (Root and current, a.k.a "normal").

If you're using LXAppearance you are able to select separate themes for Root (with gksu) and Current which as I wrote
^above is a major benefit which is another form of warning that you're using the Root account with any GUI application,
which, usually, is not safe.

But I still don't understand what thenktor meant by:
thenktor wrote:No, it won't in Openbox, LXDE and other window managers.
Can you make it more clear? If I understand correctly, it's a matter of what_is_called
"session_handler" such as gnome-settings-daemon, xfsettingsd, or lxsession.

Basically, I'm saying exactly what Duncan_Idaho wrote about session managing (if I'm interpreting the post correctly, lol)
But, I'm sure that thenktor already know that, so that's why I'm asking for a clarification.