Forums

Skip to content

Advanced search
  • Quick links
    • Unanswered topics
    • Active topics
    • Search
  • FAQ
  • Login
  • Register
  • Board index Assistance Desktop Environments
  • Search

Problems installing sway / wayland

Problems with GUI applications? Questions about X, KDE, Gnome, Fluxbox, etc.? Come on in. NOTE: For multimedia, go up one forum
Post Reply
Advanced search
15 posts • Page 1 of 1
Author
Message
Senpai
n00b
n00b
Posts: 5
Joined: Thu Feb 24, 2022 12:23 am

Problems installing sway / wayland

  • Quote

Post by Senpai » Thu Feb 24, 2022 12:32 am

Hello!

Disclaimer; although I'm not new to Linux, and I've been using Arch for a long time now, this is my first time in Gentoo, and I've decided to up my game, so for the first time I'm trying to set an ideal developer environment, and hopefully learning some while doing so. For that reason, I've decided to go with no-multilib minimal setup and to install and configure everything that I need, so hopefully, by the end of the process, I'd learned how my environment works, while also having the best possible slim and performant environment for me to play in.
That mostly involves me googling a lot of stuff, and learning as I go, but for this particular issue - I could find no obvious answers. I'm sure I'm missing something obvious, but please be gentle with me.


Background
I'm having issues setting up sway and wayland. I've setup up, DBus, elogind, my bashrc profile to export XDG_RUNTIME_DIR, but even still I'm having the same issue, and it doesn't seem to lead me anywhere useful.
The machine is a lenovo laptop, and is using an AMD APU - Ideapad 5 - 15ARE05.

Error message

Code: Select all

00:00:00.020 [ERROR] [wlr] [libseat] [libseat/backend/logind.c:653] Could not get primary session for user: No data available
00:00:00.020 [ERROR] [wlr] [libseat] [libseat/libseat.c:58] Backend 'logind' failed to open seat: No data available
00:00:00.020 [ERROR] [wlr] [backend/session/session.c:84] Unable to create seat: No data available
00:00:00.020 [ERROR] [wlr] [backend/session/session.c:249] Failed to load session backend
00:00:00.020 [ERROR] [wlr] [backend/backend.c:86] Failed to start a session
00:00:00.020 [ERROR] [wlr] [backend/backend.c:352] Failed to start a DRM session
00:00:00.020 [ERROR] [sway/server.c:56] Unable to create backend
User Groups

Code: Select all

wheel audio video input users seat


Installed packages

Code: Select all

app-admin/sudo
app-containers/docker
app-containers/docker-cli
app-misc/screenfetch
app-shells/zsh
dev-libs/wayland
dev-vcs/git
gui-wm/sway
net-misc/dhcpcd
net-misc/ntp
net-wireless/iw
net-wireless/wpa_supplicant
sys-apps/dbus
sys-apps/mlocate
sys-apps/pciutils
sys-auth/elogind
sys-auth/polkit
sys-boot/efibootmgr
sys-boot/grub
sys-fs/cryptsetup
sys-fs/dosfstools
sys-fs/lvm2
sys-kernel/dracut
sys-kernel/genkernel
sys-kernel/gentoo-sources
sys-kernel/linux-firmware
sys-process/htop
x11-terms/alacritty
RC Services

Code: Select all

               binfmt | boot                                   
             bootmisc | boot                                   
              cgroups |                                 sysinit
                devfs |                                 sysinit
                dmesg |                                 sysinit
               docker |      default                           
                 fsck | boot                                   
             hostname | boot                                   
              hwclock | boot                                   
              keymaps | boot                                   
            killprocs |                        shutdown        
    kmod-static-nodes |                                 sysinit
                local |      default nonetwork                 
           localmount | boot                                   
                  lvm | boot default                           
              modules | boot                                   
             mount-ro |                        shutdown        
                 mtab | boot                                   
             netmount |      default                           
               procfs | boot                                   
                 root | boot                                   
         save-keymaps | boot                                   
    save-termencoding | boot                                   
            savecache |                        shutdown        
                seatd |      default                           
        stmpfiles-dev |                                 sysinit
      stmpfiles-setup | boot                                   
                 swap | boot                                   
               sysctl | boot                                   
                sysfs |                                 sysinit
         termencoding | boot                                   
                 udev |                                 sysinit
         udev-trigger |                                 sysinit
              urandom | boot                                   
make.conf

Code: Select all

# These settings were set by the catalyst build script that automatically
# built this stage.
# Please consult /usr/share/portage/config/make.conf.example for a more
# detailed example.
COMMON_FLAGS="-march=native -fomit-frame-pointer -O2 -pipe"
CFLAGS="${COMMON_FLAGS}"
CXXFLAGS="${COMMON_FLAGS}"
FCFLAGS="${COMMON_FLAGS}"
FFLAGS="${COMMON_FLAGS}"
MAKEOPTS="-j4"

# NOTE: This stage was built with the bindist Use flag enabled
PORTDIR="/var/db/repos/gentoo"
DISTDIR="/var/cache/distfiles"
PKGDIR="/var/cache/binpkgs"

VIDEO_CARDS="amdgpu radeonsi"

USE="-X -kde -examples -debug -doc elogind -selinux -systemd -test dbus wayland video_cards_radeon"

# This sets the language of build output to English.
# Please keep this setting intact when reporting bugs.
LC_MESSAGES=C

# Mirrors
GENTOO_MIRRORS="https://mirror.bytemark.co.uk/gentoo/"
ACCEPT_LICENSE="*"
Top
Zucca
Moderator
Moderator
User avatar
Posts: 4691
Joined: Thu Jun 14, 2007 10:31 pm
Location: Rasi, Finland
Contact:
Contact Zucca
Website

  • Quote

Post by Zucca » Thu Feb 24, 2022 11:57 am

Sway, or rather wlroots, tries to communicate with elogind, while you have seatd installed.
I remember I needed to add elogind to boot runlevel to make wayfire (wayland compositor which also uses wlroots) start.

So I'd probably disable seatd completely and then add elogind to boot runlevel.
Also if you didn't meant to have seatd, you could then uninstall it. First check your use flags if something is pulling seatd for some reason.
..: Zucca :..

Code: Select all

init=/sbin/openrc-init
-systemd -logind -elogind seatd
I am NaN! I am a man!
Top
Anon-E-moose
Watchman
Watchman
User avatar
Posts: 6566
Joined: Fri May 23, 2008 7:31 pm
Location: Dallas area

  • Quote

Post by Anon-E-moose » Thu Feb 24, 2022 12:10 pm

Code: Select all

$ equery u seatd
[ Legend : U - final flag setting for installation]
[        : I - package is installed with flag     ]
[ Colors : set, unset                             ]
 * Found these USE flags for sys-auth/seatd-0.6.3:
 U I
 - - builtin : Enable embedded server in libseat 
 - - elogind : Enable session tracking via sys-auth/elogind
 + + server  : Enable standalone seatd server 
 - - systemd : Enable use of systemd-specific libraries and features like socket activation or session tracking
If you are going to have both seatd and *logind, then set the flags properly for seatd.

Edit to add: and since you don't have dbus started, you might add

Code: Select all

dbus-run-session -- /usr/bin/sway
or however you are trying to start sway.
UM780 xtx, 6.18 zen kernel, gcc 15, openrc, wayland
minixforum m1-s1 max -- same software as above but used for ai learning


Zealots are gonna be zealots, just like haters are gonna be haters
Top
Senpai
n00b
n00b
Posts: 5
Joined: Thu Feb 24, 2022 12:23 am

  • Quote

Post by Senpai » Thu Feb 24, 2022 10:47 pm

Hello Guys, thanks for the help.

So I had a look;
Zucca wrote:Sway, or rather wlroots, tries to communicate with elogind, while you have seatd installed.
I remember I needed to add elogind to boot runlevel to make wayfire (wayland compositor which also uses wlroots) start.

So I'd probably disable seatd completely and then add elogind to boot runlevel.
Also if you didn't meant to have seatd, you could then uninstall it. First check your use flags if something is pulling seatd for some reason.
It seems that sway itself pulls in seatd for some reason, although I don't see any specific USE flags for sway itself to toggle this behaviour.

Code: Select all

# equery depends seatd
 * These packages depend on seatd:
gui-libs/wlroots-0.15.0-r2 (sys-auth/seatd)
gui-wm/sway-1.7 (sys-auth/seatd)
From random forums online, and the comments here would make me believe that elogind is the preferred approach, and I shouldn't need seatd with that being installed.
Is that correct?

I remember reading online, that I don't have to add elogind to boot runlevel, or have it running as a deamon at all.
Your comment seems to suggest otherwise, so I'll try doing so, see if that fixes my issue.
Anon-E-moose wrote:

Code: Select all

$ equery u seatd
[ Legend : U - final flag setting for installation]
[        : I - package is installed with flag     ]
[ Colors : set, unset                             ]
 * Found these USE flags for sys-auth/seatd-0.6.3:
 U I
 - - builtin : Enable embedded server in libseat 
 - - elogind : Enable session tracking via sys-auth/elogind
 + + server  : Enable standalone seatd server 
 - - systemd : Enable use of systemd-specific libraries and features like socket activation or session tracking
If you are going to have both seatd and *logind, then set the flags properly for seatd.

Edit to add: and since you don't have dbus started, you might add

Code: Select all

dbus-run-session -- /usr/bin/sway
or however you are trying to start sway.
First of all, my bad, I forgot to say that I'm trying to run sway with `dbus-run-session sway`.
As I mentioned above, for some reason I'm having a dependency on sway, so I don't seem to have a choice of having it installed at a time.
It's possible that I'm being a donkey here, as I'm just learning emerge / and USE flags in general, but should I need extra steps to somehow mask seatd to prevent it from being installed with sway?

What is the ideal setup here? Should I get rid of elogind? Or seatd (somehow)?

I must admit, I'm completely out of my element here, although this is a good learning opprtunity for me, I can imagine this being frustrating for you guys. For this I'm so sorry. :/
Top
Anon-E-moose
Watchman
Watchman
User avatar
Posts: 6566
Joined: Fri May 23, 2008 7:31 pm
Location: Dallas area

  • Quote

Post by Anon-E-moose » Thu Feb 24, 2022 11:48 pm

If you build seatd with the elogind use flag, it should work.
UM780 xtx, 6.18 zen kernel, gcc 15, openrc, wayland
minixforum m1-s1 max -- same software as above but used for ai learning


Zealots are gonna be zealots, just like haters are gonna be haters
Top
Senpai
n00b
n00b
Posts: 5
Joined: Thu Feb 24, 2022 12:23 am

  • Quote

Post by Senpai » Fri Feb 25, 2022 12:06 am

Anon-E-moose wrote:If you build seatd with the elogind use flag, it should work.
I'm afraid that it was built with elogind USE flag. It's in my make.conf.
Top
Anon-E-moose
Watchman
Watchman
User avatar
Posts: 6566
Joined: Fri May 23, 2008 7:31 pm
Location: Dallas area

  • Quote

Post by Anon-E-moose » Fri Feb 25, 2022 12:49 am

How are you starting sway, cmd line or display manager?

what does emerge -pv wlroots sway seatd elogind return (-pv just does a pretend)
UM780 xtx, 6.18 zen kernel, gcc 15, openrc, wayland
minixforum m1-s1 max -- same software as above but used for ai learning


Zealots are gonna be zealots, just like haters are gonna be haters
Top
Senpai
n00b
n00b
Posts: 5
Joined: Thu Feb 24, 2022 12:23 am

  • Quote

Post by Senpai » Fri Feb 25, 2022 1:04 am

Anon-E-moose wrote:How are you starting sway, cmd line or display manager?

what does emerge -pv wlroots sway seatd elogind return (-pv just does a pretend)
'How are you starting sway' - with `dbus-run-session sway`.

The output for `emerge -pv wlroots sway seatd elogind`:

Code: Select all

 * IMPORTANT: 9 config files in '/etc/portage' need updating.

These are the packages that would be merged, in order:

Calculating dependencies   * See the CONFIGURATION FILES and CONFIGURATION FILES UPDATE TOOLS
 * sections of the emerge man page to learn how to update config files.
... done!
[ebuild   R    ] sys-auth/elogind-246.10-r2::gentoo  USE="acl cgroup-hybrid pam policykit -audit -debug -doc (-selinux)" 0 KiB
[ebuild   R    ] sys-auth/seatd-0.6.3:0/1::gentoo  USE="elogind server -builtin -systemd" 0 KiB
[ebuild   R    ] gui-libs/wlroots-0.15.0-r2:0/15::gentoo  USE="-X -vulkan -x11-backend" 0 KiB
[ebuild   R    ] gui-wm/sway-1.7::gentoo  USE="swaybar swaybg swayidle swaylock swaymsg swaynag -X -man -tray -wallpapers" 0 KiB

Total: 4 packages (4 reinstalls), Size of downloads: 0 KiB
Top
Naib
Watchman
Watchman
User avatar
Posts: 6101
Joined: Fri May 21, 2004 9:42 pm
Location: Removed by Neddy
Contact:
Contact Naib
Website

  • Quote

Post by Naib » Fri Feb 25, 2022 2:03 am

as Anon-E-moose how are you starting sway?
you state: dbus-run-session sway which is good but what about the services you have running and the ENV you have setup?


rc-config show --all | grep -E "seatd|elogind"


Code: Select all

cat /usr/local/bin/do_sway

#!/bin/sh

# Session
export XDG_SESSION_TYPE=wayland
export XDG_SESSION_DESKTOP=sway
export XDG_CURRENT_DESKTOP=sway
export XKB_DEFAULT_LAYOUT=gb
#export XKB_DEFAULT_VARIANT=pc104
#export XKB_DEFAULT_OPTIONS

source /usr/local/bin/wayland_enablement.sh

dbus-run-session  sway $@
I technically start sway via greetd but that is a by and by
#define HelloWorld int
#define Int main()
#define Return printf
#define Print return
#include <stdio>
HelloWorld Int {
Return("Hello, world!\n");
Print 0;
Top
Senpai
n00b
n00b
Posts: 5
Joined: Thu Feb 24, 2022 12:23 am

  • Quote

Post by Senpai » Fri Feb 25, 2022 2:19 am

Naib wrote:as Anon-E-moose how are you starting sway?
you state: dbus-run-session sway which is good but what about the services you have running and the ENV you have setup?


rc-config show --all | grep -E "seatd|elogind"


Code: Select all

cat /usr/local/bin/do_sway
#!/bin/sh

# Session
export XDG_SESSION_TYPE=wayland
export XDG_SESSION_DESKTOP=sway
export XDG_CURRENT_DESKTOP=sway
export XKB_DEFAULT_LAYOUT=gb
#export XKB_DEFAULT_VARIANT=pc104
#export XKB_DEFAULT_OPTIONS

source /usr/local/bin/wayland_enablement.sh

dbus-run-session  sway $@
[/code]

I technically start sway via greetd but that is a by and by
I've followed the wiki, and that mentions setting up XDG_RUNTIME_DIR only (unless I missed something), so that's being exported by my bash_profile

Code: Select all

# /etc/skel/.bash_profile

# This file is sourced by bash for login shells.  The following line
# runs your .bashrc and is recommended by the bash info pages.
if [[ -f ~/.bashrc ]] ; then
	. ~/.bashrc
fi

if test -z "${XDG_RUNTIME_DIR}"; then
	export XDG_RUNTIME_DIR=/tmp/${UID}-runtime-dir
	if ! test -d "${XDG_RUNTIME_DIR}"; then
		mkdir "${XDG_RUNTIME_DIR}"
		chmod 0700 "${XDG_RUNTIME_DIR}"
	fi
fi
As when it comes to rc services that are running, seatd is running, elogind is not, as I've read that it doesn't have to. Nonetheless I've tried running sway while it was running as well - but to no avail.

Code: Select all

Status of init scripts in runlevel "boot"
  binfmt                    [started]
  bootmisc                  [started]
  fsck                      [started]
  hostname                  [started]
  hwclock                   [started]
  keymaps                   [started]
  localmount                [started]
  lvm                       [started]
  modules                   [started]
  mtab                      [started]
  procfs                    [started]
  root                      [started]
  save-keymaps              [started]
  save-termencoding         [started]
  stmpfiles-setup           [started]
  swap                      [started]
  sysctl                    [started]
  termencoding              [started]
  urandom                   [started]
Status of init scripts in runlevel "default"
  docker                    [started]
  local                     [started]
  lvm                       [started]
  netmount                  [started]
  seatd                     [started]
Status of init scripts in runlevel "nonetwork"
  local                     [started]
Status of init scripts in runlevel "shutdown"
  killprocs                 [stopped]
  mount-ro                  [stopped]
  savecache                 [stopped]
Status of init scripts in runlevel "sysinit"
  cgroups                   [started]
  devfs                     [started]
  dmesg                     [started]
  kmod-static-nodes         [started]
  stmpfiles-dev             [started]
  sysfs                     [started]
  udev                      [started]
  udev-trigger              [started]
In terms of the env, the bash_profile seems to work, and it seem to export the XDG_RUNTIME_DIR ENV properly.
Top
Anon-E-moose
Watchman
Watchman
User avatar
Posts: 6566
Joined: Fri May 23, 2008 7:31 pm
Location: Dallas area

  • Quote

Post by Anon-E-moose » Fri Feb 25, 2022 11:24 am

Try with
dbus-run-session -- sway
instead of
dbus-run-session sway

Though not 100% sure if that will make a diff.

Edit to add:

grep video /etc/group
should return group,
if your userid is not there then as run as root with $USER being your username
usermod -G video -a $USER

Code: Select all

 $ grep video /etc/group
video:x:27:root,owner
ETA2: Setting this might help
LIBSEAT_BACKEND=logind
UM780 xtx, 6.18 zen kernel, gcc 15, openrc, wayland
minixforum m1-s1 max -- same software as above but used for ai learning


Zealots are gonna be zealots, just like haters are gonna be haters
Top
Naib
Watchman
Watchman
User avatar
Posts: 6101
Joined: Fri May 21, 2004 9:42 pm
Location: Removed by Neddy
Contact:
Contact Naib
Website

  • Quote

Post by Naib » Fri Feb 25, 2022 3:02 pm

Senpai wrote:
I've followed the wiki, and that mentions setting up XDG_RUNTIME_DIR only (unless I missed something), so that's being exported by my bash_profile

Code: Select all

# /etc/skel/.bash_profile

# This file is sourced by bash for login shells.  The following line
# runs your .bashrc and is recommended by the bash info pages.
if [[ -f ~/.bashrc ]] ; then
	. ~/.bashrc
fi

if test -z "${XDG_RUNTIME_DIR}"; then
	export XDG_RUNTIME_DIR=/tmp/${UID}-runtime-dir
	if ! test -d "${XDG_RUNTIME_DIR}"; then
		mkdir "${XDG_RUNTIME_DIR}"
		chmod 0700 "${XDG_RUNTIME_DIR}"
	fi
fi
.
The problem with the wiki is it is a snapshot of valid information but that does not mean it is the complete picture.

XDG_RUNTIME_DIR is needed but how you set it is different.
1) via such a snippit you have in bash
2) elogind

I originally was doing what you were doing when I was using lightdm+awesomewm BUT aspects of pipewire caused some issues so I reverted to elogind. So when I then went wayland+sway it was smoother
#define HelloWorld int
#define Int main()
#define Return printf
#define Print return
#include <stdio>
HelloWorld Int {
Return("Hello, world!\n");
Print 0;
Top
CooSee
Veteran
Veteran
User avatar
Posts: 1617
Joined: Sat Nov 20, 2004 10:38 pm
Location: right here !

  • Quote

Post by CooSee » Fri Feb 25, 2022 4:48 pm

you can also just edit /usr/share/wayland-sessions/sway.desktop

cat /usr/share/wayland-sessions/sway.desktop

Code: Select all

[Desktop Entry]
Name=Sway
Comment=An i3-compatible Wayland compositor
Exec=dbus-run-session sway
Type=Application
have you also installed some xdg ebuilds?

here are mine - running only sway here with tinydm and autologin and sway immediately locks the desktop at start and acts like a login-manager :D

Code: Select all

eix -I xdg
[I] dev-scheme/xdgdirs
     Available versions:  (~)2.2^t{xpak} {test}
     Installed versions:  2.2^t{xpak}(02:09:27 PM 02/10/2022)(-test)
     Homepage:            https://www.gnuvola.org/software/xdgdirs/
     Description:         Displays names/values of XDG Basedir variables

[I] sys-apps/xdg-dbus-proxy
     Available versions:  0.1.2{xpak} ~0.1.3
     Installed versions:  0.1.2{xpak}(03:35:18 PM 02/10/2022)
     Homepage:            https://github.com/flatpak/xdg-dbus-proxy
     Description:         Filtering proxy for D-Bus connections

[I] sys-apps/xdg-desktop-portal
     Available versions:  1.12.1{xpak} {geolocation screencast}
     Installed versions:  1.12.1{xpak}(05:10:52 PM 02/10/2022)(-geolocation -screencast)
     Homepage:            https://flatpak.org/ https://github.com/flatpak/xdg-desktop-portal
     Description:         Desktop integration portal

[I] x11-misc/xdg-user-dirs
     Available versions:  0.17{xpak} {gtk}
     Installed versions:  0.17{xpak}(02:11:03 PM 02/10/2022)(-gtk)
     Homepage:            https://www.freedesktop.org/wiki/Software/xdg-user-dirs
     Description:         Tool to help manage 'well known' user directories

[I] x11-misc/xdg-utils
     Available versions:  1.1.3_p20200220-r5^t{xpak} {dbus doc gnome}
     Installed versions:  1.1.3_p20200220-r5^t{xpak}(05:09:30 PM 02/10/2022)(dbus -doc -gnome)
     Homepage:            https://www.freedesktop.org/wiki/Software/xdg-utils/
     Description:         Portland utils for cross-platform/cross-toolkit/cross-desktop interoperability

Found 5 matches
this is my user .profile:

Code: Select all

export MOZ_ENABLE_WAYLAND=1
export XDG_CURRENT_DESKTOP=sway
export XDG_SESSION_TYPE=wayland
export GDK_BACKEND=wayland
export QT_QPA_PLATFORM=wayland
export QT_QPA_PLATFORMTHEME=qt5ct
export QT_WAYLAND_DISABLE_WINDOWDECORATION=1
i also autostart this:

Code: Select all

# Auth with polkit-gnome:
exec /usr/libexec/polkit-gnome-authentication-agent-1
i took most of the config files from endeavour os (community edition) and some from manjaro and use theme colors and icons from:

https://github.com/VijayLalwani/SeaOwl.git

if you want to play with color codes, this will definitely help:

https://www.rapidtables.com/convert/color/index.html

greetings
" Die Realität ist eine Illusion, die durch Mangel an ehrlicher Kommunikation entsteht "
---
" Der Mensch ist von Natur aus neugierig, was am Ende übrig bleibt ist die Gier "
Top
platyhelminth
n00b
n00b
Posts: 16
Joined: Wed Oct 26, 2016 1:02 pm
Location: France

  • Quote

Post by platyhelminth » Fri Jun 27, 2025 3:59 pm

I can confirm all that Senpai said. The Gentoo wiki of sway is a bit outdated (at least for openrc not systemd since I haven't tried) for its default way to launch sway just after login, and even by typing "dbus-run-session sway" . Editing the /usr/share/wayland-sessions/sway.desktop as CooSee said and launching sway with any display manager can work, using greetd like Naib said can also be done with this modification.

I don't know everything about linux, but I tried many things to launch sway from tty or just after login in tty like said in the wiki. The only way I succeeded to launch sway with a modification (similar) of .bashrc like the wiki of sway says :

Code: Select all

if [ -z "$WAYLAND_DISPLAY" ] && [ -n "$XDG_VTNR" ] && [ "$XDG_VTNR" -eq 1 ] ; then
    exec dbus-run-session sway
fi
is to use the display manager qingy ( https://wiki.gentoo.org/wiki/Qingy ) by selecting "console" in the display manager choice. Remember qingy needs modification of /etc/inittab like its wiki of qingy says. I have no idea why it works by changing agetty for qingy.
Top
sMueggli
l33t
l33t
Posts: 627
Joined: Sat Sep 03, 2022 9:22 am

  • Quote

Post by sMueggli » Sat Jun 28, 2025 8:36 am

platyhelminth wrote:I don't know everything about linux, but I tried many things to launch sway from tty or just after login in tty like said in the wiki. The only way I succeeded to launch sway with a modification (similar) of .bashrc like the wiki of sway says :

Code: Select all

if [ -z "$WAYLAND_DISPLAY" ] && [ -n "$XDG_VTNR" ] && [ "$XDG_VTNR" -eq 1 ] ; then
    exec dbus-run-session sway
fi
In my opinion .bashrc is the wrong place because this file is evaluated for every bash session. Better put it into .bash_profile or .bash_login or .profile so that it is evaluated only once.
Top
Post Reply

15 posts • Page 1 of 1

Return to “Desktop Environments”

Jump to
  • Assistance
  • ↳   News & Announcements
  • ↳   Frequently Asked Questions
  • ↳   Installing Gentoo
  • ↳   Multimedia
  • ↳   Desktop Environments
  • ↳   Networking & Security
  • ↳   Kernel & Hardware
  • ↳   Portage & Programming
  • ↳   Gamers & Players
  • ↳   Other Things Gentoo
  • ↳   Unsupported Software
  • Discussion & Documentation
  • ↳   Documentation, Tips & Tricks
  • ↳   Gentoo Chat
  • ↳   Gentoo Forums Feedback
  • ↳   Duplicate Threads
  • International Gentoo Users
  • ↳   中文 (Chinese)
  • ↳   Dutch
  • ↳   Finnish
  • ↳   French
  • ↳   Deutsches Forum (German)
  • ↳   Diskussionsforum
  • ↳   Deutsche Dokumentation
  • ↳   Greek
  • ↳   Forum italiano (Italian)
  • ↳   Forum di discussione italiano
  • ↳   Risorse italiane (documentazione e tools)
  • ↳   Polskie forum (Polish)
  • ↳   Instalacja i sprzęt
  • ↳   Polish OTW
  • ↳   Portuguese
  • ↳   Documentação, Ferramentas e Dicas
  • ↳   Russian
  • ↳   Scandinavian
  • ↳   Spanish
  • ↳   Other Languages
  • Architectures & Platforms
  • ↳   Gentoo on ARM
  • ↳   Gentoo on PPC
  • ↳   Gentoo on Sparc
  • ↳   Gentoo on Alternative Architectures
  • ↳   Gentoo on AMD64
  • ↳   Gentoo for Mac OS X (Portage for Mac OS X)
  • Board index
  • All times are UTC
  • Delete cookies

© 2001–2026 Gentoo Foundation, Inc.

Powered by phpBB® Forum Software © phpBB Limited

Privacy Policy

 

 

magic