Difference between revisions of "LXQt"

(started entry)
 
(Reminder to install X11 first on clean Funtoo Installs. Re-worded subheadings under 'Starting LXQt')
 
(8 intermediate revisions by one other user not shown)
Line 3: Line 3:
 
LXQt is a lightweight Desktop environment. Some LXDE developers decided to create a Qt based version of their Desktop environment, it's name was lxde-qt. Around the same time some other people were working on a different minimal Qt based DE called razor-qt. When some developers of those projects met they decided to join forces and work together on one project. LXQt was born.
 
LXQt is a lightweight Desktop environment. Some LXDE developers decided to create a Qt based version of their Desktop environment, it's name was lxde-qt. Around the same time some other people were working on a different minimal Qt based DE called razor-qt. When some developers of those projects met they decided to join forces and work together on one project. LXQt was born.
  
== Instalation ==
+
=== Qt5 only system ===
 +
LXQt depends only on Qt5, but polkit-qt has automatically set the qt4 USE flag. In case you are sure that you won't install any Qt4 applications which need polkit-qt you can disable Qt4 there resulting in a leaner System. Otherwise emerging LXQt will not just install qtcore-5 but also qtcore-4. In case your goal is to have a minimal, up to date Qt5 based system edit your /etc/portage/package.use file as follows:
 +
{{file|name=/etc/portage/package.use|lang=|desc=add or alter the polkit-qt line|body=
 +
sys-auth/polkit-qt -qt4
 +
}}
 +
 
 +
== Installation ==
 +
 
 +
=== X Window System ===
 +
For LXQt installations on a clean Funtoo install, first install the [[X Window System]].
 +
 
 +
=== Recommended Funtoo Profiles ===
 +
You should have set the desktop flavor before trying to install LXQt, furthermore we recommend setting the LXQt mix-in. These settings will take care of the USE flags that you otherwise have to set by hand.
 +
 
 +
Just run epro without any arguments to see your current settings.
 +
{{console|body=
 +
###i## epro
 +
 
 +
=== Enabled Profiles: ===
 +
 
 +
        arch: x86-64bit
 +
      build: current
 +
    subarch: generic_64
 +
      flavor: core
 +
    mix-ins: (not set)
 +
 
 +
}}
 +
 
 +
In case you have a output like this. Change it using:
 +
 
 +
{{console|body=
 +
###i## epro flavor desktop
 +
###i## epro mix-in +lxqt
 +
 
 +
=== Enabled Profiles: ===
 +
 
 +
        arch: x86-64bit
 +
      build: current
 +
    subarch: generic_64
 +
      flavor: desktop
 +
    mix-ins: lxqt
 +
 
 +
>>> Added lxqt mix-in.
 +
 
 +
}}
 +
 
 +
Since lxqt-meta depends on policykit we have to add policykit to consolekit:
 +
{{console|body=
 +
###i## echo "sys-auth/consolekit policykit" >> /etc/portage/package.use
 +
}}
 +
 
 +
Now we are ready to install LXQt.
  
 
{{console|body=
 
{{console|body=
###i## eselect profile add funtoo/1.0/linux-gnu/mix-ins/lxqt
 
 
###i## emerge lxqt-meta
 
###i## emerge lxqt-meta
 
}}
 
}}
 +
 +
== Starting LXQt ==
 +
 +
You can either use a display manager to log into your system and start LXQt, or you can log in on a TTY and run {{c|startx}} to start xinit by hand.
 +
 +
=== Without a Display Manager (xinit only) ===
 +
 +
You should edit the file  {{c|~/.xinitrc}} if it already exists, and put {{c|"exec startlxqt"}} in there.
 +
If it doesn't exist you can create it like this:
 +
 +
{{console|body=$##i## echo "exec startlxqt" > ~/.xinitrc}}
 +
 +
You might want to add the commands and options {{c|ck-launch-session dbus-launch --sh-syntax --exit-with-session}} to the {{c|exec}} to start it with ConsoleKit and DBus.
 +
In this case you also need to add ConsoleKit to the default runlevel:
 +
 +
{{console|body=
 +
###i## rc-update add consolekit default
 +
###i## rc
 +
}}
 +
 +
 +
=== With a Display (Login) Manager ===
 +
 +
Please take a look at [[Package:XDM_(Display_Manager)|XDM Display Managers]] for this.

Latest revision as of 13:05, July 1, 2015

About LXQt

LXQt is a lightweight Desktop environment. Some LXDE developers decided to create a Qt based version of their Desktop environment, it's name was lxde-qt. Around the same time some other people were working on a different minimal Qt based DE called razor-qt. When some developers of those projects met they decided to join forces and work together on one project. LXQt was born.

Qt5 only system

LXQt depends only on Qt5, but polkit-qt has automatically set the qt4 USE flag. In case you are sure that you won't install any Qt4 applications which need polkit-qt you can disable Qt4 there resulting in a leaner System. Otherwise emerging LXQt will not just install qtcore-5 but also qtcore-4. In case your goal is to have a minimal, up to date Qt5 based system edit your /etc/portage/package.use file as follows:

/etc/portage/package.use - add or alter the polkit-qt line
sys-auth/polkit-qt -qt4

Installation

X Window System

For LXQt installations on a clean Funtoo install, first install the X Window System.

Recommended Funtoo Profiles

You should have set the desktop flavor before trying to install LXQt, furthermore we recommend setting the LXQt mix-in. These settings will take care of the USE flags that you otherwise have to set by hand.

Just run epro without any arguments to see your current settings.

# epro

=== Enabled Profiles: ===

        arch: x86-64bit
       build: current
     subarch: generic_64
      flavor: core
     mix-ins: (not set)


In case you have a output like this. Change it using:

# epro flavor desktop
# epro mix-in +lxqt

=== Enabled Profiles: ===

        arch: x86-64bit
       build: current
     subarch: generic_64
      flavor: desktop
     mix-ins: lxqt

>>> Added lxqt mix-in.


Since lxqt-meta depends on policykit we have to add policykit to consolekit:

# echo "sys-auth/consolekit policykit" >> /etc/portage/package.use


Now we are ready to install LXQt.

# emerge lxqt-meta


Starting LXQt

You can either use a display manager to log into your system and start LXQt, or you can log in on a TTY and run startx to start xinit by hand.

Without a Display Manager (xinit only)

You should edit the file ~/.xinitrc if it already exists, and put "exec startlxqt" in there. If it doesn't exist you can create it like this:

$ echo "exec startlxqt" > ~/.xinitrc


You might want to add the commands and options ck-launch-session dbus-launch --sh-syntax --exit-with-session to the exec to start it with ConsoleKit and DBus. In this case you also need to add ConsoleKit to the default runlevel:

# rc-update add consolekit default
# rc


With a Display (Login) Manager

Please take a look at XDM Display Managers for this.