Difference between pages "Xfce" and "User talk:Lo0na"

From Funtoo
(Difference between pages)
Jump to: navigation, search
(Created a section on how to add a user to the power group)
 
(thanks for the help :): new section)
 
Line 1: Line 1:
== About Xfce ==
+
Looking into the issue you described...
  
''Xfce is a lightweight desktop environment for UNIX-like operating systems. It aims to be fast and low on system resources, while still being visually appealing and user friendly.
+
OK, based on my initial research into this issue, and I could be wrong... I am leaning towards calling this a quirk in how the new "spam diff" works, which is a new feature in 1.17 or 1.18 of mediawiki. When it is showing you all those lines that it wants to remove, it is on the spam protection page, right? So it is not actually erasing stuff. It just looks like it wants to erase stuff. But this may be a quirk in my spam code with the new mediawiki feature.
  
''Xfce embodies the traditional UNIX philosophy of modularity and re-usability. It consists of a number of components that provide the full functionality one can expect of a modern desktop environment. They are packaged separately and you can pick among the available packages to create the optimal personal working environment.
+
So quick summary - I think the wiki is safe, unless you actually *see* the wiki erase lots of content like the spam protection page is making you think it wants to do. I think I just need to fix the output of the spam protection page.
  
''Another priority of Xfce is adhereance to standards, specifically those defined at [http://freedesktop.org/ freedesktop.org]. <ref>http://www.xfce.org/about/</ref>
+
If you actually see data being destroyed, let me know. But even then, the wiki has history. So don't be afraid of editing and don't be scared by the spam protection warning at this time.
  
== Installation ==
+
UPDATE: I have added some URLs to the whitelist so the installation tutorial isn't set up to trigger the spam filter out of the gates. You should now be able to save changes to this page.
  
Before emerging Xfce you need to:
+
UPDATE: OK, the strange thing is that you should not have been able to make any changes to the Installation Tutorial on the wiki like you did, since this page had links in it that triggered the spam filter. Did you do anything special to get by the spam filter? I will look at the code and make sure it is applying to you.
  
* Check that you have enabled the USE flags necessary for a XFCE desktop environment. [[Funtoo_Linux_First_Steps#Changing_profile|Set your profile to "xfce" via mix-ins]], as follows:
+
Reply: Ah, ok, that makes perfect sense re: you editing sections and not the whole document. You may want to try switching your UI to English and seeing if that makes things work correctly when the spam protection filter does trigger. Yes, the spam protection filter seems to check against the entire contents of the new page (or if editing just a section, the section). So any existing links in the page or section will trigger the spam filter. This is explained in the English spam filter message but I don't have a German variant :)
  
<console>
+
== thanks for the help :) ==
# ##i## eselect profile add funtoo/1.0/linux-gnu/mix-ins/xfce
+
</console>
+
  
* Verify that you have [[Funtoo_Linux_First_Steps#X.Org|X.Org Server]] configured properly.
+
Hi Lo0na, I certainly would appreciate editing help with the Wiki. English is our official language -- we made a decision early on that it is easier to target one language rather than many, since most people know English to some degree anyway. Translated articles tend to get out-of-date. But I would love to have you help with the wiki in any way you can, including editing or adding new good content to the wiki.
  
We are now ready to install Xfce. Install the meta-package, which pulls in all of the components you need for a minimal Xfce installation:
+
I don't know if you use wireless on Linux or not, but I think we could use some information in our networking guide about setting up <tt>wicd</tt>. I feel we are a bit light on the wireless side of things. New users often pop on to freenode to ask wireless setup questions. Maybe all they need are a few pointers. <tt>wicd</tt> seems to be the preferred thing to use because it is so reliable.
 
+
<console>
+
# ##i##emerge xfce4-meta
+
</console>
+
 
+
== Running Xfce ==
+
 
+
There are several different ways to start Xfce:
+
 
+
* Editing the <tt>.xinitrc</tt> file in your user's home directory and using <tt>startx</tt> from a text console.
+
* Using a display manager (e.g. SLiM, GDM, and KDM).
+
* Configuring your shell profile to automatically start Xfce upon a successful login.
+
 
+
=== .xinitrc ===
+
 
+
The most common way to start the environment is to configure <tt>~/.xinitrc</tt> to launch an Xfce session. The proper way to launch Xfce from the terminal is by using <tt>startxfce4</tt> combined with <tt>ck-launch-session</tt>.
+
 
+
<console>
+
$ ##i##echo "exec startxfce4 --with-ck-launch" > ~/.xinitrc
+
</console>
+
 
+
Note that <tt>--with-ck-launch</tt> (from ConsoleKit) is required by Xfce for important tasks such as shutting down, suspending, and automatically mounting removable storage media. Some applications will not work properly without it. Therefore we need to add ConsoleKit to the <tt>default</tt> runlevel, executing the following command as root:
+
 
+
<console>
+
# ##i##rc-update add consolekit default
+
</console>
+
 
+
Finally, to start the graphical environment, run <tt>startx</tt> from a login shell:
+
<console>
+
$ ##i##startx
+
</console>
+
 
+
== Display Manager ==
+
 
+
A display manager is a program that manages sessions and acts as a login screen. Here's a short list of a few of the display managers available in Funtoo:
+
 
+
* XDM (<tt>x11-apps/xdm</tt>): X.Org's standard display manager.
+
 
+
* LightDM (<tt>x11-misc/lightdm</tt>): A lightweight, but highly configurable display manager.
+
 
+
* SLiM (<tt>x11-misc/slim</tt>): Simple Login Manager -- a lightweight display manager. Not very configurable.
+
 
+
Any of these would make a fine choice. After you've chosen which display manager to use, install it:
+
 
+
<console>
+
# ##i##emerge lightdm
+
</console>
+
 
+
All that's left to do now is to add the name of the display manager to <tt>/etc/conf.d/xdm</tt>, add the <tt>xdm</tt> service to the <tt>default</tt> runlevel, and start the service:
+
 
+
<pre>
+
DISPLAYMANAGER="lightdm"
+
</pre>
+
 
+
<console>
+
# ##i##rc-update add xdm default
+
# ##i##/etc/init.d/xdm start
+
</console>
+
 
+
==Power Group==
+
 
+
If you wish to be able to shutdown/reboot/suspend/hibernate using xfce4-logout-session then you will need to add yourself or the user to the power group by:
+
 
+
<console>
+
# ##i##gpasswd -a <username> power
+
</console>
+
 
+
If the group does not exist then execute the following and try again:
+
 
+
<console>
+
# ##i##groupadd power
+
</console>
+
 
+
Now you need to add the following to /usr/share/polkit-1/actions/org.freedesktop.upower.policy:
+
 
+
<console>
+
<?xml version="1.0" encoding="UTF-8"?>
+
<!DOCTYPE policyconfig PUBLIC
+
"-//freedesktop//DTD PolicyKit Policy Configuration 1.0//EN"
+
"http://www.freedesktop.org/standards/PolicyKit/1.0/policyconfig.dtd">
+
<policyconfig>
+
  <vendor>The UPower Project</vendor>
+
  <vendor_url>http://upower.freedesktop.org/</vendor_url>
+
  <icon_name>system-suspend</icon_name>
+
 
+
  <action id="org.freedesktop.upower.suspend">
+
    <description>Suspend the system</description>
+
    <description xml:lang="fr">Mettre le système en veille</description>
+
    <description xml:lang="it">Sospende il sistema</description>
+
    <description xml:lang="pl">Wstrzymanie systemu</description>
+
    <description xml:lang="sv">Försätt systemet i vänteläge</description>
+
    <message>Authentication is required to suspend the system</message>
+
    <message xml:lang="fr">Vous devez vous identifier pour mettre le système en veille</message>
+
    <message xml:lang="it">È richiesto autenticarsi per sospendere il sistema</message>
+
    <message xml:lang="pl">Wymagane jest uwierzytelnienie, aby wstrzymać system</message>
+
    <message xml:lang="sv">Autentisering krävs för att försätta systemet i vänteläge</message>
+
    <defaults>
+
      <allow_any>yes</allow_any>
+
      <allow_inactive>no</allow_inactive>
+
      <allow_active>yes</allow_active>
+
    </defaults>
+
  </action>
+
 
+
  <action id="org.freedesktop.upower.hibernate">
+
    <description>Hibernate the system</description>
+
    <description xml:lang="fr">Mettre le système en hibernation</description>
+
    <description xml:lang="it">Iberna il sistema</description>
+
    <description xml:lang="pl">Hibernacja systemu</description>
+
    <description xml:lang="sv">Försätt systemet i viloläge</description>
+
    <message>Authentication is required to hibernate the system</message>
+
    <message xml:lang="fr">Vous devez vous identifier pour mettre le système en hibernation</message>
+
    <message xml:lang="it">È richiesto autenticarsi per ibernare il sistema</message>
+
    <message xml:lang="pl">Wymagane jest uwierzytelnienie, aby zahibernować system</message>
+
    <message xml:lang="sv">Autentisering krävs för att försätta systemet i viloläge</message>
+
    <defaults>
+
      <allow_any>yes</allow_any>
+
      <allow_inactive>no</allow_inactive>
+
      <allow_active>yes</allow_active>
+
    </defaults>
+
  </action>
+
 
+
</policyconfig>
+
</console>
+
 
+
and also add the following to /usr/share/polkit-1/actions/org.freedesktop.consolekit.policy:
+
 
+
<console>
+
<?xml version="1.0" encoding="UTF-8"?>
+
<!DOCTYPE policyconfig PUBLIC
+
"-//freedesktop//DTD PolicyKit Policy Configuration 1.0//EN"
+
"http://www.freedesktop.org/standards/PolicyKit/1.0/policyconfig.dtd">
+
 
+
<!--
+
Policy definitions for ConsoleKit
+
-->
+
 
+
<policyconfig>
+
 
+
  <action id="org.freedesktop.consolekit.system.stop">
+
    <description>Stop the system</description>
+
    <message>System policy prevents stopping the system</message>
+
    <defaults>
+
      <allow_any>yes</allow_any>
+
      <allow_inactive>no</allow_inactive>
+
      <allow_active>yes</allow_active>
+
    </defaults>
+
  </action>
+
 
+
  <action id="org.freedesktop.consolekit.system.stop-multiple-users">
+
    <description>Stop the system when multiple users are logged in</description>
+
    <message>System policy prevents stopping the system when other users are logged in</message>
+
    <defaults>
+
      <allow_any>yes</allow_any>
+
      <allow_inactive>no</allow_inactive>
+
      <allow_active>yes</allow_active>
+
    </defaults>
+
  </action>
+
 
+
  <action id="org.freedesktop.consolekit.system.restart">
+
    <description>Restart the system</description>
+
    <message>System policy prevents restarting the system</message>
+
    <defaults>
+
      <allow_any>yes</allow_any>
+
      <allow_inactive>no</allow_inactive>
+
      <allow_active>yes</allow_active>
+
    </defaults>
+
  </action>
+
 
+
  <action id="org.freedesktop.consolekit.system.restart-multiple-users">
+
    <description>Restart the system when multiple users are logged in</description>
+
    <message>System policy prevents restarting the system when other users are logged in</message>
+
    <defaults>
+
      <allow_any>yes</allow_any>
+
      <allow_inactive>no</allow_inactive>
+
      <allow_active>yes</allow_active>
+
    </defaults>
+
  </action>
+
 
+
</policyconfig>
+
</console>
+
 
+
[[Category:Desktop]]
+
[[Category:First Steps]]
+
[[Category:Official Documentation]]
+

Latest revision as of 00:02, 10 January 2012

Looking into the issue you described...

OK, based on my initial research into this issue, and I could be wrong... I am leaning towards calling this a quirk in how the new "spam diff" works, which is a new feature in 1.17 or 1.18 of mediawiki. When it is showing you all those lines that it wants to remove, it is on the spam protection page, right? So it is not actually erasing stuff. It just looks like it wants to erase stuff. But this may be a quirk in my spam code with the new mediawiki feature.

So quick summary - I think the wiki is safe, unless you actually *see* the wiki erase lots of content like the spam protection page is making you think it wants to do. I think I just need to fix the output of the spam protection page.

If you actually see data being destroyed, let me know. But even then, the wiki has history. So don't be afraid of editing and don't be scared by the spam protection warning at this time.

UPDATE: I have added some URLs to the whitelist so the installation tutorial isn't set up to trigger the spam filter out of the gates. You should now be able to save changes to this page.

UPDATE: OK, the strange thing is that you should not have been able to make any changes to the Installation Tutorial on the wiki like you did, since this page had links in it that triggered the spam filter. Did you do anything special to get by the spam filter? I will look at the code and make sure it is applying to you.

Reply: Ah, ok, that makes perfect sense re: you editing sections and not the whole document. You may want to try switching your UI to English and seeing if that makes things work correctly when the spam protection filter does trigger. Yes, the spam protection filter seems to check against the entire contents of the new page (or if editing just a section, the section). So any existing links in the page or section will trigger the spam filter. This is explained in the English spam filter message but I don't have a German variant :)

thanks for the help :)

Hi Lo0na, I certainly would appreciate editing help with the Wiki. English is our official language -- we made a decision early on that it is easier to target one language rather than many, since most people know English to some degree anyway. Translated articles tend to get out-of-date. But I would love to have you help with the wiki in any way you can, including editing or adding new good content to the wiki.

I don't know if you use wireless on Linux or not, but I think we could use some information in our networking guide about setting up wicd. I feel we are a bit light on the wireless side of things. New users often pop on to freenode to ask wireless setup questions. Maybe all they need are a few pointers. wicd seems to be the preferred thing to use because it is so reliable.