View previous topic :: View next topic |
Author |
Message |
linuxfluesterer Tux's lil' helper
Joined: 06 Jan 2016 Posts: 130 Location: Germany
|
Posted: Wed Jun 13, 2018 10:46 am Post subject: [UNSOLVED] XFCE with systemd |
|
|
Hallo people.
I'm a beginner with Gentoo (less than a week). I have achieved to install Gentoo on a laptop.
Due to the slow performance first I only installed the [25] default/linux/amd64/17.0/systemd (stable) * profile.
Now I wanted to install the XFCE4 desktop.
For this I installed Code: | xfce-base/xfce4-meta,
x11-terms/xfce4-terminal | and more,
following this url:https://wiki.gentoo.org/wiki/Xfce
Now, after installing, I login as root in a tty terminal and then enter
I just receive a black screen, then I receive some messages of Xorg and Xserver shut down successfully,
but no XFCE desktop appears. Instead I'm back on text terminal (tty).
I should mention (again), that I do not use openrc (xinit), my profile is selected for use with systemd.
So, simply, what is the easiest way to get XFCE run on a systemd gentoo system?
Thank you in advance.
-Linuxfluesterer
Last edited by linuxfluesterer on Wed Jul 11, 2018 9:48 am; edited 1 time in total |
|
Back to top |
|
|
guitou Guru
Joined: 02 Oct 2003 Posts: 534 Location: France
|
Posted: Wed Jun 13, 2018 11:43 am Post subject: |
|
|
Hello.
Your X log file (/var/log/Xorg.0.log) might be a good starting point to help diagnose the issue.
++
Gi) |
|
Back to top |
|
|
dermatty n00b
Joined: 13 Jun 2018 Posts: 1
|
Posted: Wed Jun 13, 2018 11:48 am Post subject: |
|
|
use only standard user for startx, not root! with root, startx will fail! |
|
Back to top |
|
|
linuxfluesterer Tux's lil' helper
Joined: 06 Jan 2016 Posts: 130 Location: Germany
|
Posted: Wed Jun 13, 2018 12:10 pm Post subject: |
|
|
dermatty wrote: | use only standard user for startx, not root! with root, startx will fail! |
There is no difference, as standard user to root...
-Linuxfluesterer |
|
Back to top |
|
|
linuxfluesterer Tux's lil' helper
Joined: 06 Jan 2016 Posts: 130 Location: Germany
|
Posted: Wed Jun 13, 2018 12:18 pm Post subject: |
|
|
guitou wrote: | Hello.
Your X log file (/var/log/Xorg.0.log) might be a good starting point to help diagnose the issue.
++
Gi) |
Code: | [ 5998.351]
X.Org X Server 1.19.5
Release Date: 2017-10-12
[ 5998.359] X Protocol Version 11, Revision 0
[ 5998.361] Build Operating System: Linux 4.5.2-aufs-r1 x86_64 Gentoo
[ 5998.364] Current Operating System: Linux localhost 4.17.0-gentoo #1 SMP Sat Jun 9 20:51:46 -00 2018 x86_64
[ 5998.364] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.17.0-gentoo root=/dev/sda4 ro
[ 5998.368] Build Date: 10 June 2018 12:50:20AM
[ 5998.371]
[ 5998.373] Current version of pixman: 0.34.0
[ 5998.377] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 5998.377] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 5998.385] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Jun 13 13:08:49 2018
[ 5998.388] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 5998.390] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 5998.390] (==) No Layout section. Using the first Screen section.
[ 5998.390] (==) No screen section available. Using defaults.
[ 5998.390] (**) |-->Screen "Default Screen Section" (0)
[ 5998.390] (**) | |-->Monitor "<default monitor>"
[ 5998.390] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 5998.390] (==) Automatically adding devices
[ 5998.390] (==) Automatically enabling devices
[ 5998.390] (==) Automatically adding GPU devices
[ 5998.390] (==) Max clients allowed: 256, resource mask: 0x1fffff
[ 5998.390] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/OTF/,
/usr/share/fonts/Type1/,
/usr/share/fonts/100dpi/,
/usr/share/fonts/75dpi/
[ 5998.390] (==) ModulePath set to "/usr/lib64/xorg/modules"
[ 5998.390] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 5998.390] (II) Loader magic: 0x56465303fd00
[ 5998.390] (II) Module ABI versions:
[ 5998.390] X.Org ANSI C Emulation: 0.4
[ 5998.390] X.Org Video Driver: 23.0
[ 5998.390] X.Org XInput driver : 24.1
[ 5998.390] X.Org Server Extension : 10.0
[ 5998.391] (++) using VT number 2
[ 5998.391] (--) controlling tty is VT number 2, auto-enabling KeepTty
[ 5998.393] (II) systemd-logind: took control of session /org/freedesktop/login1/session/_32
[ 5998.394] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 5998.395] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 10 paused 0
[ 5998.400] (--) PCI:*(0:0:2:0) 8086:2a42:17aa:20e5 rev 7, Mem @ 0xf4400000/4194304, 0xd0000000/268435456, I/O @ 0x00001800/8, BIOS @ 0x????????/131072
[ 5998.400] (--) PCI: (0:0:2:1) 8086:2a43:17aa:20e5 rev 7, Mem @ 0xf4200000/1048576
[ 5998.400] (II) LoadModule: "glx"
[ 5998.401] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so
[ 5998.402] (II) Module glx: vendor="X.Org Foundation"
[ 5998.402] compiled for 1.19.5, module version = 1.0.0
[ 5998.402] ABI class: X.Org Server Extension, version 10.0
[ 5998.402] (==) Matched intel as autoconfigured driver 0
[ 5998.402] (==) Matched intel as autoconfigured driver 1
[ 5998.402] (==) Matched modesetting as autoconfigured driver 2
[ 5998.402] (==) Matched fbdev as autoconfigured driver 3
[ 5998.402] (==) Matched vesa as autoconfigured driver 4
[ 5998.402] (==) Assigned the driver to the xf86ConfigLayout
[ 5998.402] (II) LoadModule: "intel"
[ 5998.403] (II) Loading /usr/lib64/xorg/modules/drivers/intel_drv.so
[ 5998.403] (II) Module intel: vendor="X.Org Foundation"
[ 5998.403] compiled for 1.19.5, module version = 2.99.917
[ 5998.403] Module class: X.Org Video Driver
[ 5998.403] ABI class: X.Org Video Driver, version 23.0
[ 5998.403] (II) LoadModule: "modesetting"
[ 5998.403] (II) Loading /usr/lib64/xorg/modules/drivers/modesetting_drv.so
[ 5998.403] (II) Module modesetting: vendor="X.Org Foundation"
[ 5998.403] compiled for 1.19.5, module version = 1.19.5
[ 5998.403] Module class: X.Org Video Driver
[ 5998.403] ABI class: X.Org Video Driver, version 23.0
[ 5998.403] (II) LoadModule: "fbdev"
[ 5998.403] (II) Loading /usr/lib64/xorg/modules/drivers/fbdev_drv.so
[ 5998.403] (II) Module fbdev: vendor="X.Org Foundation"
[ 5998.403] compiled for 1.19.5, module version = 0.4.4
[ 5998.403] Module class: X.Org Video Driver
[ 5998.403] ABI class: X.Org Video Driver, version 23.0
[ 5998.403] (II) LoadModule: "vesa"
[ 5998.404] (II) Loading /usr/lib64/xorg/modules/drivers/vesa_drv.so
[ 5998.404] (II) Module vesa: vendor="X.Org Foundation"
[ 5998.404] compiled for 1.19.5, module version = 2.4.0
[ 5998.404] Module class: X.Org Video Driver
[ 5998.404] ABI class: X.Org Video Driver, version 23.0
[ 5998.404] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets:
i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G,
915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM,
Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33,
GM45, 4 Series, G45/G43, Q45/Q43, G41, B43
[ 5998.404] (II) intel: Driver for Intel(R) HD Graphics
[ 5998.404] (II) intel: Driver for Intel(R) Iris(TM) Graphics
[ 5998.404] (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics
[ 5998.404] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[ 5998.404] (II) FBDEV: driver for framebuffer: fbdev
[ 5998.404] (II) VESA: driver for VESA chipsets: vesa
[ 5998.405] (II) intel(0): Using Kernel Mode Setting driver: i915, version 1.6.0 20180308
[ 5998.418] (WW) Falling back to old probe method for modesetting
[ 5998.418] (WW) Falling back to old probe method for fbdev
[ 5998.418] (II) Loading sub module "fbdevhw"
[ 5998.418] (II) LoadModule: "fbdevhw"
[ 5998.418] (II) Loading /usr/lib64/xorg/modules/libfbdevhw.so
[ 5998.418] (II) Module fbdevhw: vendor="X.Org Foundation"
[ 5998.418] compiled for 1.19.5, module version = 0.0.2
[ 5998.418] ABI class: X.Org Video Driver, version 23.0
[ 5998.419] (--) intel(0): Integrated Graphics Chipset: Intel(R) GM45
[ 5998.419] (--) intel(0): CPU: x86-64, sse2, sse3, ssse3; using a maximum of 2 threads
[ 5998.419] (II) intel(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 5998.419] (==) intel(0): Depth 24, (--) framebuffer bpp 32
[ 5998.419] (==) intel(0): RGB weight 888
[ 5998.419] (==) intel(0): Default visual is TrueColor
[ 5998.419] (II) intel(0): Output LVDS1 has no monitor section
[ 5998.419] (**) intel(0): Found backlight control interface intel_backlight (type 'raw') for output LVDS1
[ 5998.419] (II) intel(0): Enabled output LVDS1
[ 5998.419] (II) intel(0): Output VGA1 has no monitor section
[ 5998.419] (II) intel(0): Enabled output VGA1
[ 5998.420] (II) intel(0): Output HDMI1 has no monitor section
[ 5998.420] (II) intel(0): Enabled output HDMI1
[ 5998.420] (II) intel(0): Output DP1 has no monitor section
[ 5998.420] (II) intel(0): Enabled output DP1
[ 5998.420] (II) intel(0): Output DP2 has no monitor section
[ 5998.420] (II) intel(0): Enabled output DP2
[ 5998.420] (--) intel(0): Using a maximum size of 256x256 for hardware cursors
[ 5998.420] (II) intel(0): Output VIRTUAL1 has no monitor section
[ 5998.420] (II) intel(0): Enabled output VIRTUAL1
[ 5998.420] (--) intel(0): Output LVDS1 using initial mode 1280x800 on pipe 0
[ 5998.420] (==) intel(0): TearFree disabled
[ 5998.420] (==) intel(0): Using gamma correction (1.0, 1.0, 1.0)
[ 5998.420] (==) intel(0): DPI set to (96, 96)
[ 5998.420] (II) Loading sub module "dri3"
[ 5998.420] (II) LoadModule: "dri3"
[ 5998.420] (II) Module "dri3" already built-in
[ 5998.420] (II) Loading sub module "dri2"
[ 5998.421] (II) LoadModule: "dri2"
[ 5998.421] (II) Module "dri2" already built-in
[ 5998.421] (II) Loading sub module "present"
[ 5998.421] (II) LoadModule: "present"
[ 5998.421] (II) Module "present" already built-in
[ 5998.421] (II) UnloadModule: "modesetting"
[ 5998.421] (II) Unloading modesetting
[ 5998.421] (II) UnloadModule: "fbdev"
[ 5998.421] (II) Unloading fbdev
[ 5998.421] (II) UnloadSubModule: "fbdevhw"
[ 5998.421] (II) Unloading fbdevhw
[ 5998.421] (II) UnloadModule: "vesa"
[ 5998.421] (II) Unloading vesa
[ 5998.421] (==) Depth 24 pixmap format is 32 bpp
[ 5998.421] (II) intel(0): SNA initialized with Eaglelake (gen4.5) backend
[ 5998.421] (==) intel(0): Backing store enabled
[ 5998.421] (==) intel(0): Silken mouse enabled
[ 5998.421] (II) intel(0): HW Cursor enabled
[ 5998.421] (II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[ 5998.422] (==) intel(0): DPMS enabled
[ 5998.422] (==) intel(0): Display hotplug detection enabled
[ 5998.422] (II) intel(0): [DRI2] Setup complete
[ 5998.422] (II) intel(0): [DRI2] DRI driver: i965
[ 5998.422] (II) intel(0): [DRI2] VDPAU driver: va_gl
[ 5998.422] (II) intel(0): direct rendering: DRI2 enabled
[ 5998.422] (II) intel(0): hardware support for Present enabled
[ 5998.422] (--) RandR disabled
[ 5998.436] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
[ 5998.436] (II) AIGLX: enabled GLX_ARB_create_context
[ 5998.436] (II) AIGLX: enabled GLX_ARB_create_context_profile
[ 5998.436] (II) AIGLX: enabled GLX_EXT_create_context_es{,2}_profile
[ 5998.436] (II) AIGLX: enabled GLX_INTEL_swap_event
[ 5998.436] (II) AIGLX: enabled GLX_SGI_swap_control
[ 5998.436] (II) AIGLX: enabled GLX_EXT_framebuffer_sRGB
[ 5998.436] (II) AIGLX: enabled GLX_ARB_fbconfig_float
[ 5998.436] (II) AIGLX: enabled GLX_EXT_fbconfig_packed_float
[ 5998.436] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
[ 5998.436] (II) AIGLX: Loaded and initialized i965
[ 5998.436] (II) GLX: Initialized DRI2 GL provider for screen 0
[ 5998.442] (II) intel(0): switch to mode 1280x800@60.0 on LVDS1 using pipe 0, position (0, 0), rotation normal, reflection none
[ 5998.445] (II) intel(0): Setting screen physical size to 338 x 211
[ 5998.573] (II) config/udev: Adding input device Power Button (/dev/input/event2)
[ 5998.573] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[ 5998.573] (**) Power Button: Applying InputClass "system-keyboard"
[ 5998.573] (II) LoadModule: "libinput"
[ 5998.573] (II) Loading /usr/lib64/xorg/modules/input/libinput_drv.so
[ 5998.574] (II) Module libinput: vendor="X.Org Foundation"
[ 5998.574] compiled for 1.19.5, module version = 0.27.1
[ 5998.574] Module class: X.Org XInput Driver
[ 5998.574] ABI class: X.Org XInput driver, version 24.1
[ 5998.574] (II) Using input driver 'libinput' for 'Power Button'
[ 5998.575] (II) systemd-logind: got fd for /dev/input/event2 13:66 fd 23 paused 0
[ 5998.575] (**) Power Button: always reports core events
[ 5998.575] (**) Option "Device" "/dev/input/event2"
[ 5998.575] (**) Option "_source" "server/udev"
[ 5998.576] (II) event2 - Power Button: is tagged by udev as: Keyboard
[ 5998.576] (II) event2 - Power Button: device is a keyboard
[ 5998.576] (II) event2 - Power Button: device removed
[ 5998.576] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2/event2"
[ 5998.576] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[ 5998.576] (**) Option "xkb_model" "pc105"
[ 5998.576] (**) Option "xkb_layout" "de"
[ 5998.576] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
[ 5998.608] (II) event2 - Power Button: is tagged by udev as: Keyboard
[ 5998.608] (II) event2 - Power Button: device is a keyboard
[ 5998.609] (II) config/udev: Adding input device Video Bus (/dev/input/event3)
[ 5998.609] (**) Video Bus: Applying InputClass "libinput keyboard catchall"
[ 5998.609] (**) Video Bus: Applying InputClass "system-keyboard"
[ 5998.609] (II) Using input driver 'libinput' for 'Video Bus'
[ 5998.610] (II) systemd-logind: got fd for /dev/input/event3 13:67 fd 26 paused 0
[ 5998.610] (**) Video Bus: always reports core events
[ 5998.610] (**) Option "Device" "/dev/input/event3"
[ 5998.610] (**) Option "_source" "server/udev"
[ 5998.611] (II) event3 - Video Bus: is tagged by udev as: Keyboard
[ 5998.611] (II) event3 - Video Bus: device is a keyboard
[ 5998.611] (II) event3 - Video Bus: device removed
[ 5998.611] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input3/event3"
[ 5998.611] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 7)
[ 5998.611] (**) Option "xkb_model" "pc105"
[ 5998.611] (**) Option "xkb_layout" "de"
[ 5998.611] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
[ 5998.612] (II) event3 - Video Bus: is tagged by udev as: Keyboard
[ 5998.612] (II) event3 - Video Bus: device is a keyboard
[ 5998.613] (II) config/udev: Adding input device Lid Switch (/dev/input/event0)
[ 5998.613] (II) No input driver specified, ignoring this device.
[ 5998.613] (II) This device may have been added with another device file.
[ 5998.613] (II) config/udev: Adding input device Sleep Button (/dev/input/event1)
[ 5998.613] (**) Sleep Button: Applying InputClass "libinput keyboard catchall"
[ 5998.613] (**) Sleep Button: Applying InputClass "system-keyboard"
[ 5998.613] (II) Using input driver 'libinput' for 'Sleep Button'
[ 5998.614] (II) systemd-logind: got fd for /dev/input/event1 13:65 fd 27 paused 0
[ 5998.614] (**) Sleep Button: always reports core events
[ 5998.615] (**) Option "Device" "/dev/input/event1"
[ 5998.615] (**) Option "_source" "server/udev"
[ 5998.615] (II) event1 - Sleep Button: is tagged by udev as: Keyboard
[ 5998.615] (II) event1 - Sleep Button: device is a keyboard
[ 5998.615] (II) event1 - Sleep Button: device removed
[ 5998.615] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1/event1"
[ 5998.615] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 8)
[ 5998.615] (**) Option "xkb_model" "pc105"
[ 5998.615] (**) Option "xkb_layout" "de"
[ 5998.615] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
[ 5998.616] (II) event1 - Sleep Button: is tagged by udev as: Keyboard
[ 5998.616] (II) event1 - Sleep Button: device is a keyboard
[ 5998.617] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event4)
[ 5998.617] (**) AT Translated Set 2 keyboard: Applying InputClass "libinput keyboard catchall"
[ 5998.618] (**) AT Translated Set 2 keyboard: Applying InputClass "system-keyboard"
[ 5998.618] (II) Using input driver 'libinput' for 'AT Translated Set 2 keyboard'
[ 5998.618] (II) systemd-logind: got fd for /dev/input/event4 13:68 fd 28 paused 0
[ 5998.618] (**) AT Translated Set 2 keyboard: always reports core events
[ 5998.619] (**) Option "Device" "/dev/input/event4"
[ 5998.619] (**) Option "_source" "server/udev"
[ 5998.619] (II) event4 - AT Translated Set 2 keyboard: is tagged by udev as: Keyboard
[ 5998.619] (II) event4 - AT Translated Set 2 keyboard: device is a keyboard
[ 5998.619] (II) event4 - AT Translated Set 2 keyboard: device removed
[ 5998.619] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input4/event4"
[ 5998.619] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 9)
[ 5998.619] (**) Option "xkb_model" "pc105"
[ 5998.619] (**) Option "xkb_layout" "de"
[ 5998.619] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
[ 5998.620] (II) event4 - AT Translated Set 2 keyboard: is tagged by udev as: Keyboard
[ 5998.620] (II) event4 - AT Translated Set 2 keyboard: device is a keyboard
[ 5998.621] (II) config/udev: Adding input device AlpsPS/2 ALPS DualPoint TouchPad (/dev/input/event6)
[ 5998.621] (**) AlpsPS/2 ALPS DualPoint TouchPad: Applying InputClass "libinput touchpad catchall"
[ 5998.621] (II) Using input driver 'libinput' for 'AlpsPS/2 ALPS DualPoint TouchPad'
[ 5998.622] (II) systemd-logind: got fd for /dev/input/event6 13:70 fd 29 paused 0
[ 5998.622] (**) AlpsPS/2 ALPS DualPoint TouchPad: always reports core events
[ 5998.622] (**) Option "Device" "/dev/input/event6"
[ 5998.622] (**) Option "_source" "server/udev"
[ 5998.623] (II) event6 - AlpsPS/2 ALPS DualPoint TouchPad: is tagged by udev as: Touchpad
[ 5998.623] (II) event6 - AlpsPS/2 ALPS DualPoint TouchPad: no resolution or size hints, assuming a size of 69x50mm
[ 5998.623] (II) event6 - AlpsPS/2 ALPS DualPoint TouchPad: device is a touchpad
[ 5998.623] (II) event6 - AlpsPS/2 ALPS DualPoint TouchPad: device removed
[ 5998.623] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input6/event6"
[ 5998.623] (II) XINPUT: Adding extended input device "AlpsPS/2 ALPS DualPoint TouchPad" (type: TOUCHPAD, id 10)
[ 5998.623] (**) Option "AccelerationScheme" "none"
[ 5998.623] (**) AlpsPS/2 ALPS DualPoint TouchPad: (accel) selected scheme none/0
[ 5998.623] (**) AlpsPS/2 ALPS DualPoint TouchPad: (accel) acceleration factor: 2.000
[ 5998.623] (**) AlpsPS/2 ALPS DualPoint TouchPad: (accel) acceleration threshold: 4
[ 5998.624] (II) event6 - AlpsPS/2 ALPS DualPoint TouchPad: is tagged by udev as: Touchpad
[ 5998.624] (II) event6 - AlpsPS/2 ALPS DualPoint TouchPad: no resolution or size hints, assuming a size of 69x50mm
[ 5998.624] (II) event6 - AlpsPS/2 ALPS DualPoint TouchPad: device is a touchpad
[ 5998.625] (II) config/udev: Adding input device AlpsPS/2 ALPS DualPoint TouchPad (/dev/input/mouse1)
[ 5998.625] (II) No input driver specified, ignoring this device.
[ 5998.625] (II) This device may have been added with another device file.
[ 5998.625] (II) config/udev: Adding input device AlpsPS/2 ALPS DualPoint Stick (/dev/input/event5)
[ 5998.625] (**) AlpsPS/2 ALPS DualPoint Stick: Applying InputClass "libinput pointer catchall"
[ 5998.625] (II) Using input driver 'libinput' for 'AlpsPS/2 ALPS DualPoint Stick'
[ 5998.626] (II) systemd-logind: got fd for /dev/input/event5 13:69 fd 30 paused 0
[ 5998.626] (**) AlpsPS/2 ALPS DualPoint Stick: always reports core events
[ 5998.626] (**) Option "Device" "/dev/input/event5"
[ 5998.626] (**) Option "_source" "server/udev"
[ 5998.627] (II) event5 - AlpsPS/2 ALPS DualPoint Stick: is tagged by udev as: Mouse Pointingstick
[ 5998.627] (II) event5 - AlpsPS/2 ALPS DualPoint Stick: trackpoint does not have a specified range, guessing... see https://wayland.freedesktop.org/libinput/doc/1.10.7/trackpoints.html
[ 5998.627] (II) event5 - AlpsPS/2 ALPS DualPoint Stick: trackpoint device set to range 20
[ 5998.627] (II) event5 - AlpsPS/2 ALPS DualPoint Stick: device is a pointer
[ 5998.627] (II) event5 - AlpsPS/2 ALPS DualPoint Stick: device removed
[ 5998.627] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input7/event5"
[ 5998.627] (II) XINPUT: Adding extended input device "AlpsPS/2 ALPS DualPoint Stick" (type: MOUSE, id 11)
[ 5998.627] (**) Option "AccelerationScheme" "none"
[ 5998.628] (**) AlpsPS/2 ALPS DualPoint Stick: (accel) selected scheme none/0
[ 5998.628] (**) AlpsPS/2 ALPS DualPoint Stick: (accel) acceleration factor: 2.000
[ 5998.628] (**) AlpsPS/2 ALPS DualPoint Stick: (accel) acceleration threshold: 4
[ 5998.628] (II) event5 - AlpsPS/2 ALPS DualPoint Stick: is tagged by udev as: Mouse Pointingstick
[ 5998.628] (II) event5 - AlpsPS/2 ALPS DualPoint Stick: trackpoint does not have a specified range, guessing... see https://wayland.freedesktop.org/libinput/doc/1.10.7/trackpoints.html
[ 5998.628] (II) event5 - AlpsPS/2 ALPS DualPoint Stick: trackpoint device set to range 20
[ 5998.628] (II) event5 - AlpsPS/2 ALPS DualPoint Stick: device is a pointer
[ 5998.629] (II) config/udev: Adding input device AlpsPS/2 ALPS DualPoint Stick (/dev/input/mouse0)
[ 5998.629] (II) No input driver specified, ignoring this device.
[ 5998.629] (II) This device may have been added with another device file.
[ 5998.651] (**) Option "fd" "23"
[ 5998.651] (II) event2 - Power Button: device removed
[ 5998.651] (**) Option "fd" "26"
[ 5998.651] (II) event3 - Video Bus: device removed
[ 5998.651] (**) Option "fd" "27"
[ 5998.651] (II) event1 - Sleep Button: device removed
[ 5998.651] (**) Option "fd" "28"
[ 5998.651] (II) event4 - AT Translated Set 2 keyboard: device removed
[ 5998.651] (**) Option "fd" "29"
[ 5998.651] (II) event6 - AlpsPS/2 ALPS DualPoint TouchPad: device removed
[ 5998.652] (**) Option "fd" "30"
[ 5998.652] (II) event5 - AlpsPS/2 ALPS DualPoint Stick: device removed
[ 5998.653] (II) UnloadModule: "libinput"
[ 5998.653] (II) systemd-logind: releasing fd for 13:69
[ 5998.663] (II) UnloadModule: "libinput"
[ 5998.663] (II) systemd-logind: releasing fd for 13:70
[ 5998.673] (II) UnloadModule: "libinput"
[ 5998.673] (II) systemd-logind: releasing fd for 13:68
[ 5998.678] (II) UnloadModule: "libinput"
[ 5998.678] (II) systemd-logind: releasing fd for 13:65
[ 5998.682] (II) UnloadModule: "libinput"
[ 5998.682] (II) systemd-logind: releasing fd for 13:67
[ 5998.694] (II) UnloadModule: "libinput"
[ 5998.694] (II) systemd-logind: releasing fd for 13:66
[ 5998.750] (II) Server terminated successfully (0). Closing log file. |
Hope, this helps. I wonder, why this log file has so many messages.
-Linuxfluesterer |
|
Back to top |
|
|
eccerr0r Watchman
Joined: 01 Jul 2004 Posts: 9824 Location: almost Mile High in the USA
|
Posted: Wed Jun 13, 2018 2:17 pm Post subject: |
|
|
Are you using "startx xfce4" or "startxfce4" ... the latter should work. The former, I'm not quite so sure...
Tu use startx you may need to set XSESSION=xfce4 or something like that ... _________________ Intel Core i7 2700K/Radeon R7 250/24GB DDR3/256GB SSD
What am I supposed watching? |
|
Back to top |
|
|
linuxfluesterer Tux's lil' helper
Joined: 06 Jan 2016 Posts: 130 Location: Germany
|
Posted: Wed Jun 13, 2018 6:53 pm Post subject: |
|
|
eccerr0r wrote: | Are you using "startx xfce4" or "startxfce4" ... the latter should work. The former, I'm not quite so sure...
Tu use startx you may need to set XSESSION=xfce4 or something like that ... |
I tried the this:
and when this did not work, I tried: and after that I also tried
In no case I saw the known XFCE Desktop. Sometimes I see a split screen with 3 gui terminals. So strange!
-Linuxfluesterer |
|
Back to top |
|
|
eccerr0r Watchman
Joined: 01 Jul 2004 Posts: 9824 Location: almost Mile High in the USA
|
Posted: Wed Jun 13, 2018 10:11 pm Post subject: |
|
|
You should be running
"startxfce4"
(One word, NO spaces, ONE x)
I believe running
"XSESSION=xfce4 startx"
should also work -- but I did not try it and not sure. _________________ Intel Core i7 2700K/Radeon R7 250/24GB DDR3/256GB SSD
What am I supposed watching? |
|
Back to top |
|
|
The Doctor Moderator
Joined: 27 Jul 2010 Posts: 2678
|
Posted: Thu Jun 14, 2018 12:39 am Post subject: |
|
|
And in any case you should absolutely NOT be doing it as root.
Running X as root is very dangerous as GUI apps are not secured so the entire system is vulnerable. Besides that, all the GUI tools are designed to be run as a user and expect it. This means that they will fail in unexpected ways when run as root.
The 3 screens you got are the default X environment, twm I believe, that gets bundled with xorg. _________________ First things first, but not necessarily in that order.
Apologies if I take a while to respond. I'm currently working on the dematerialization circuit for my blue box. |
|
Back to top |
|
|
Fitzcarraldo Advocate
Joined: 30 Aug 2008 Posts: 2053 Location: United Kingdom
|
Posted: Thu Jun 14, 2018 9:23 am Post subject: Re: XFCE with systemd |
|
|
linuxfluesterer wrote: | For this I installed Code: | xfce-base/xfce4-meta,
x11-terms/xfce4-terminal | and more,
following this url:https://wiki.gentoo.org/wiki/Xfce
Now, after installing, I login as root in a tty terminal and then enter
I just receive a black screen, then I receive some messages of Xorg and Xserver shut down successfully,
but no XFCE desktop appears. Instead I'm back on text terminal (tty). |
The Gentoo Wiki article you referenced does not tell you to use the command you quoted. It states the following:
Xfce - Gentoo Wiki wrote: | startx
When using startx, create a ~/.xinitrc file with the following contents:
startxfce4
To launch the Xfce4 desktop simply type startxfce4 at the command-line and press enter:
|
Did you create the file ~/.xinitrc with the contents stated in the Wiki article? The Wiki article is giving you two alternatives: either a) create the file ~/.xinitrc containing 'exec startxfce4' and use the command 'startx' from your user account, or b) use the command 'startxfce4' from your user account. _________________ Clevo W230SS: amd64, VIDEO_CARDS="intel modesetting nvidia".
Compal NBLB2: ~amd64, xf86-video-ati. Dual boot Win 7 Pro 64-bit.
OpenRC systemd-utils[udev] elogind KDE on both.
My blog |
|
Back to top |
|
|
linuxfluesterer Tux's lil' helper
Joined: 06 Jan 2016 Posts: 130 Location: Germany
|
Posted: Thu Jun 14, 2018 11:40 am Post subject: |
|
|
The Doctor wrote: | And in any case you should absolutely NOT be doing it as root.
Running X as root is very dangerous as GUI apps are not secured so the entire system is vulnerable. Besides that, all the GUI tools are designed to be run as a user and expect it. This means that they will fail in unexpected ways when run as root.
The 3 screens you got are the default X environment, twm I believe, that gets bundled with xorg. |
Maybe I mistake / misunderstand because I think of a login manager like xdm, sddm or lightdm, which I assume, are not installed on my system. Iunderstand, that after a login as a normal user then the desktop environment will be run as normal user also.
Thanks for clearing.
@ "The doctor" and Fitzcarraldo also: I'll need to test the suggested commands as soon I'll be back on my Gentoo system.
-Linuxfluesterer |
|
Back to top |
|
|
eccerr0r Watchman
Joined: 01 Jul 2004 Posts: 9824 Location: almost Mile High in the USA
|
Posted: Thu Jun 14, 2018 1:34 pm Post subject: |
|
|
Not sure when the devs will chime in but they'll suggest not to hack your .xinitrc unless you really know what you're doing - as it will muck up with the Gentoo scripting, mainly to set up XDG stuff.
Do so at your own risk (though startxfce4 will also set up XDG stuff for you.) _________________ Intel Core i7 2700K/Radeon R7 250/24GB DDR3/256GB SSD
What am I supposed watching? |
|
Back to top |
|
|
linuxfluesterer Tux's lil' helper
Joined: 06 Jan 2016 Posts: 130 Location: Germany
|
Posted: Thu Jun 14, 2018 7:48 pm Post subject: Re: XFCE with systemd |
|
|
Fitzcarraldo wrote: | The Gentoo Wiki article you referenced does not tell you to use the command you quoted. It states the following:
Xfce - Gentoo Wiki wrote: | startx
When using startx, create a ~/.xinitrc file with the following contents:
startxfce4
To launch the Xfce4 desktop simply type startxfce4 at the command-line and press enter:
|
Did you create the file ~/.xinitrc with the contents stated in the Wiki article? The Wiki article is giving you two alternatives: either a) create the file ~/.xinitrc containing 'exec startxfce4' and use the command 'startx' from your user account, or b) use the command 'startxfce4' from your user account. |
I'm at home now and I'm very sorry to say: there is no startxfce4 file on my Gentoo system,the only sequence found on my system is startx . So where is this mysterious file startxfce4? Of course I created a ~/.xinitrc file (as user) with the described content.
-Linuxfluesterer |
|
Back to top |
|
|
eccerr0r Watchman
Joined: 01 Jul 2004 Posts: 9824 Location: almost Mile High in the USA
|
Posted: Thu Jun 14, 2018 8:40 pm Post subject: |
|
|
Did you install xfce4-meta or how did you install xfce4?
/usr/bin/startxfce4 is part of xfce-base/xfce4-session which should have been picked up by xfce4-meta . You can try
equery list xfce4-session
to see if you have it installed. equery is part of app-portage/gentoolkit if you don't have it installed. _________________ Intel Core i7 2700K/Radeon R7 250/24GB DDR3/256GB SSD
What am I supposed watching? |
|
Back to top |
|
|
linuxfluesterer Tux's lil' helper
Joined: 06 Jan 2016 Posts: 130 Location: Germany
|
Posted: Fri Jun 15, 2018 1:19 pm Post subject: |
|
|
eccerr0r wrote: | Did you install xfce4-meta or how did you install xfce4?
/usr/bin/startxfce4 is part of xfce-base/xfce4-session which should have been picked up by xfce4-meta . You can try
equery list xfce4-session
to see if you have it installed. equery is part of app-portage/gentoolkit if you don't have it installed. |
I wonder, I wonder, I thought, I've installed xfce4-meta. But a check with: Code: | emerge -p xfce4-meta | replied: N for not installed.
Ok, so I will install this package with distributed computing = distcc because there are about 300 sub packages belonging to [xfce4-meta[/i]. But I have many problems distcc. For these problems, I have opened a new thread.
Because without distributed computing, my 2009 year old x86_64 Intel(R) Core(TM)2 Duo CPU T5870 @ 2.00GHz with 4 GBytes Ram is compiling very, very slow.
When I have received a suitable answer to my distcc topic I will go on then with installing big packages.
Else, I will think about to use Gentoo on such a slow system.
-Linuxfluesterer |
|
Back to top |
|
|
eccerr0r Watchman
Joined: 01 Jul 2004 Posts: 9824 Location: almost Mile High in the USA
|
Posted: Fri Jun 15, 2018 1:50 pm Post subject: |
|
|
Well, need to expect compilation time!
I still run Gentoo-xfce4 on an Atom box (with 2GB RAM) so I feel your pain... Trying to use my quad core machines as much as possible but the Atom is still stuck compiling on its own frequently. _________________ Intel Core i7 2700K/Radeon R7 250/24GB DDR3/256GB SSD
What am I supposed watching? |
|
Back to top |
|
|
linuxfluesterer Tux's lil' helper
Joined: 06 Jan 2016 Posts: 130 Location: Germany
|
Posted: Fri Jun 15, 2018 1:58 pm Post subject: |
|
|
eccerr0r wrote: | Well, need to expect compilation time!
I still run Gentoo-xfce4 on an Atom box (with 2GB RAM) so I feel your pain... Trying to use my quad core machines as much as possible but the Atom is still stuck compiling on its own frequently. |
Hmmm. you may be right, but what matters is processor speed. I will combine external servers to share their processor power with my client (distcc). And when I compiled my kernel-4.17.0 without distcc, I just needed 30 minutes, when I (meant , distcc works fine) used distcc, then my compilation time melted down to 10 minutes.
But emerging fce4-meta is not behaving like kernel compiling.
So, for me is essential to make distcc run smoothly as it is proposed for.
-Linuxfluesterer |
|
Back to top |
|
|
linuxfluesterer Tux's lil' helper
Joined: 06 Jan 2016 Posts: 130 Location: Germany
|
Posted: Sun Jun 17, 2018 11:02 am Post subject: |
|
|
Hallo friends.
After I was busy to learn about distcc usage in combination with emerge / compiling / make, I tried to install
Code: | emerge --ask --autounmask-write xfce-base/xfce4-meta | which seems to work (install) several (sub) packages fine.
Until there was a package named snappy which could not be installed, because there is a missing part or object or so with name window.h.
So here installation of xfce-base/xfce4-meta stops, because I cannot find any package or else, which could satisfy this window.h file.
I'm not sure, I will go on trying to install xfce4-meta on this at several locations changed Gentoo system (my first at all).
I wonder, why it is not possible to install the XFCE desktop as simple as it is told this desktop is simple, lean and tiny for less strong hardware.
I rather think about to start at the beginning again:
-boot with live Gentoo USB-stick
-completely delete the root partition
-unpack stage3 to the empty partition again
-chroot to the new partition with the unpacked skeleton
-selecting another profile
...
So, here are some questions, which should show me the way how I will have to go on next:
- If I'd choose the default/linux/amd64/13.0/desktop profile, do I already have systemd included?
- if not, can I easily activate systemd.
My intention is such to prepare this slow laptop for a usable desktop, and, if XFCE doesn't work, then I will have to choose Plasma later,
when I will have understood more of generell Gentoo.
Thank you for joining again.
-Linuxfluesterer |
|
Back to top |
|
|
eccerr0r Watchman
Joined: 01 Jul 2004 Posts: 9824 Location: almost Mile High in the USA
|
Posted: Sun Jun 17, 2018 2:17 pm Post subject: |
|
|
As systemd is an explicit choice for Gentoo, if you did not install systemd, likely you do not have it. Most Gentooers are systemd refugees by choice as they want to stay far away from this contraption. That is not to say there are a good number of them using it as well (me included, I have a mixture of systemd and openrc boxes.)
I think a quick way to tell: Run
If it pulls up a list of targets, you're running systemd.
If it gives you an error indicating some dbus problem or if the command isn't found, then you are not. _________________ Intel Core i7 2700K/Radeon R7 250/24GB DDR3/256GB SSD
What am I supposed watching? |
|
Back to top |
|
|
linuxfluesterer Tux's lil' helper
Joined: 06 Jan 2016 Posts: 130 Location: Germany
|
Posted: Sun Jun 17, 2018 5:41 pm Post subject: |
|
|
On my 'strong' computer, I have a Sabayon OS, a Gentoo based binary operating system.
It is using systemd. That is the reason, why I chose systemd for Gentoo installation profile.
But it made problems then to install a simple desktop, XFCE
Because Plasma contains many (sub) packages, I will not install it before I will have made more experiences with Gentoo.
Ok, it's a good idea to check an installation with the systemctl -a command.
I also know, that there is a systemd component, which can be installed with emerge
-Linuxfluesterer |
|
Back to top |
|
|
eccerr0r Watchman
Joined: 01 Jul 2004 Posts: 9824 Location: almost Mile High in the USA
|
Posted: Sun Jun 17, 2018 7:22 pm Post subject: |
|
|
I'm more worried about people who run
# emerge systemd
and then they say they're running systemd... no they are not. A kernel command line needs to be changed to specify systemd as init.
Honestly I've found xfce runs perfectly fine under systemd. Haven't noticed any glitches whatsoever. Granted most of my systemd boxes have gnome3 installed as well, perhaps having gnome3 gets more of the dep issues cleared away.
---
BTW, my poor old Atom box (Netbook, distcc disabled because I don't have any helpers ready for it, single core/HT, 2GB RAM) is now 56 hours into a world update (OpenRC/XFCE4). It still has 70 packages to go. _________________ Intel Core i7 2700K/Radeon R7 250/24GB DDR3/256GB SSD
What am I supposed watching? |
|
Back to top |
|
|
linuxfluesterer Tux's lil' helper
Joined: 06 Jan 2016 Posts: 130 Location: Germany
|
Posted: Sun Jun 24, 2018 11:28 am Post subject: |
|
|
eccerr0r wrote: | I'm more worried about people who run
# emerge systemd
and then they say they're running systemd... no they are not. A kernel command line needs to be changed to specify systemd as init.
Honestly I've found xfce runs perfectly fine under systemd. Haven't noticed any glitches whatsoever. Granted most of my systemd boxes have gnome3 installed as well, perhaps having gnome3 gets more of the dep issues cleared away.
---
BTW, my poor old Atom box (Netbook, distcc disabled because I don't have any helpers ready for it, single core/HT, 2GB RAM) is now 56 hours into a world update (OpenRC/XFCE4). It still has 70 packages to go. |
I'm glad to hear, that XFCE would run perfectly under systemd.
That was my intention. So first I selected the 17.0 systemd stable profile. That systemd is running, I can see, when I run the systemctl command.
But I have problems to install {i]xfce4-meta[/i]
I get error messages like could not find window.h and, not sure, other dependency errors.
So, if I would begin to install Gentoo again (boot with Gentoo USB-Stick, chroot... select profile...)
What is your suggestion to handle a correct xfce desktop under systemd to prevent receiving errors and dependency problems, pls?
Thank you very much.
-Linuxfluesterer |
|
Back to top |
|
|
eccerr0r Watchman
Joined: 01 Jul 2004 Posts: 9824 Location: almost Mile High in the USA
|
Posted: Mon Jun 25, 2018 4:29 am Post subject: |
|
|
Please post which package failed and some context.
Again all my systemd boxes have gnome3 installed and thus had the gnome3/systemd profile set. But it should not be relevant - my xfce/openrc boxes merged fine with a plain desktop profile.... _________________ Intel Core i7 2700K/Radeon R7 250/24GB DDR3/256GB SSD
What am I supposed watching? |
|
Back to top |
|
|
linuxfluesterer Tux's lil' helper
Joined: 06 Jan 2016 Posts: 130 Location: Germany
|
Posted: Tue Jun 26, 2018 11:09 am Post subject: |
|
|
eccerr0r wrote: | Please post which package failed and some context.
Again all my systemd boxes have gnome3 installed and thus had the gnome3/systemd profile set. But it should not be relevant - my xfce/openrc boxes merged fine with a plain desktop profile.... |
I think, it would be easier to begin new installation than to follow (slow) reinstallation of xfce4-terminal.
And as I said, one error I had, was the absence of the following program / app / routine while emerging this xfce4-terminal:
window.h: no file or directory
In Google I found an explanation, that this routine is necessary for the Windows OS (or I'm wrong?). I'm not sure about that.
So, simply could you tell me the steps after installing Gentoo from USB stick after unpacking stage3 and executing chroot.
I mean, begin with your profile, pls, and then,
what did you do to updating Gentoo repos, world repo, whatever necessary to have a clean Gentoo base.
After that, which packages of xfce did you emerge then?
That would be all, I want to know.
Thank you in advance.
-Linuxfluesterer |
|
Back to top |
|
|
eccerr0r Watchman
Joined: 01 Jul 2004 Posts: 9824 Location: almost Mile High in the USA
|
Posted: Tue Jun 26, 2018 7:16 pm Post subject: |
|
|
It takes a lot to make a Gentoo box unrecoverable, but more information is needed to help debug.
Screenshots will be necessary, or post lines from build.log ... The location of build.log should be specified in the merge failure output. Post the exact location of the file too, since that path contains the exact package that's being built and have trouble. _________________ Intel Core i7 2700K/Radeon R7 250/24GB DDR3/256GB SSD
What am I supposed watching? |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|