Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
[Solved]Virtualbox Gentoo, Start X No screens found and more
View unanswered posts
View posts from last 24 hours

Goto page 1, 2, 3, 4  Next  
Reply to topic    Gentoo Forums Forum Index Desktop Environments
View previous topic :: View next topic  
Author Message
Hironatashima
Apprentice
Apprentice


Joined: 28 Apr 2005
Posts: 212

PostPosted: Tue Mar 13, 2018 1:52 pm    Post subject: [Solved]Virtualbox Gentoo, Start X No screens found and more Reply with quote

So I've been fighting with X window for a week or more trying to get it to run. I built into the Make.conf the use flags for it, I've compiled the kernel for it to work with Virtualbox. Emerged Virtualbox AND the virtual box guest addons, etc. etc. etc., I followed the handbook for it too. The gentoo environment is running beautifully... minus X window. Everything is set as far as I can figure.... I'm trying to run it with Gnome, since I've never used Gnome much before, mostly I just use KDE, but this is a severe headache and a half. So to the point, here's my pastebins of what I figure yall need to help me out:

Xorg.0.log https://paste.pound-python.org/show/BIcte5WQU75kW993oJ1o/

xorg.conf https://paste.pound-python.org/show/4o3AaoMdRKeYbLAxi82y/

make.conf https://paste.pound-python.org/show/8VnRZgTurlEA2EXNadgS/

If there's any other pastebin you guys need, let me know, and I'll throw it up here with the quickness. I've looked at a number of other issues that I thought were similar, but none of their fixes helped me out at all.

Thanks in advance for the help!


Last edited by Hironatashima on Tue Mar 20, 2018 5:03 pm; edited 3 times in total
Back to top
View user's profile Send private message
Maxxx
Guru
Guru


Joined: 12 Jan 2016
Posts: 503
Location: Italia

PostPosted: Tue Mar 13, 2018 2:19 pm    Post subject: Reply with quote

I had same problem...

Try to put "modesetting" instead of "vboxvideo" in your xorg.conf - Section "Device":

Code:
...
   Identifier  "Card0"
   Driver      "modesetting"
   BusID       "PCI:0:2:0"
EndSection
...

Furthermore in make.conf, in "VIDEO_CARDS=", i have "vboxvideo", not "virtualbox"
Back to top
View user's profile Send private message
Hironatashima
Apprentice
Apprentice


Joined: 28 Apr 2005
Posts: 212

PostPosted: Tue Mar 13, 2018 2:31 pm    Post subject: Reply with quote

Thanks for the response Maxxx,

I've made the suggested changes, and the results have not changed too drastically. Shall I try the X -configure option? I've heard that command no longer works effectively... Here's the pastebins at any rate:

Xorg.0.log - https://paste.pound-python.org/show/wGhycVH562LTy69wNImD/

xorg.conf - https://paste.pound-python.org/show/iilTQRfHZmM6eOryLsiF/

make.conf - https://paste.pound-python.org/show/mupwK4O4k3WNEHOv1KIg/
Back to top
View user's profile Send private message
Maxxx
Guru
Guru


Joined: 12 Jan 2016
Posts: 503
Location: Italia

PostPosted: Tue Mar 13, 2018 2:36 pm    Post subject: Reply with quote

Could you post the output of:

Code:
lspci | grep -i VGA
Back to top
View user's profile Send private message
guitou
Guru
Guru


Joined: 02 Oct 2003
Posts: 362
Location: France

PostPosted: Tue Mar 13, 2018 2:42 pm    Post subject: Reply with quote

Hello.

Check the first error (the dbus one), try and fix it (starting dbus service for example?..)
Then regarding second error, whether using vboxdriver or modsetting, it must be installed to be available (emerge x11-drivers/xf86-video-vboxvideo)

++
Gi)
Back to top
View user's profile Send private message
Hironatashima
Apprentice
Apprentice


Joined: 28 Apr 2005
Posts: 212

PostPosted: Tue Mar 13, 2018 2:42 pm    Post subject: Reply with quote

Code:
00:02.0 VGA compatible controller: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter
Back to top
View user's profile Send private message
Hironatashima
Apprentice
Apprentice


Joined: 28 Apr 2005
Posts: 212

PostPosted: Tue Mar 13, 2018 2:49 pm    Post subject: Reply with quote

guitou,

Thank you for chiming in and helping also.

The first error I haven't yet cracked yet.

The second: I tried to emerge the vbox driver, said something about unmasking, fixed that, and emerged again, and it got to the end, but stopped because it'd create a 'collision' with /usr/lib64/xorg/modules/drivers/vboxvideo_drv.so

I think there's some progress happening, but... not quite sure where, yet.
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 41320
Location: 56N 3W

PostPosted: Tue Mar 13, 2018 2:53 pm    Post subject: Reply with quote

Hironatashima,

Code:
[  2328.829] (EE) dbus-core: error connecting to system bus: org.freedesktop.DBus.Error.FileNotFound (Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory)
Means that you need to start dbus.
Add it to the default runlevel so you don't forget.

Code:
[  2328.838] (II) Loading /usr/lib64/xorg/modules/drivers/vboxvideo_drv.so
[  2328.838] (II) Module vboxvideo: vendor="Oracle Corporation"
[  2328.838]    compiled for 1.19.5, module version = 1.0.1
[  2328.838]    Module class: X.Org Video Driver
says that you have the right Xorg video driver available.

You don't need an xorg.conf to get Xorg to start. You will get USA settings by default.
Try renaming xorg.conf, so its not found and go with the automatics until Xorg starts.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
guitou
Guru
Guru


Joined: 02 Oct 2003
Posts: 362
Location: France

PostPosted: Tue Mar 13, 2018 3:01 pm    Post subject: Reply with quote

Thanks neddy: always a better knowledge and a so much better way to tell :)
And to Hiro: as a general rule, when encountering errors, it is better to address first error first (often happen to some errors to be due to previous ones / besides, these 2 don't seem to depend on one another though)

++
Gi)
Back to top
View user's profile Send private message
Hironatashima
Apprentice
Apprentice


Joined: 28 Apr 2005
Posts: 212

PostPosted: Tue Mar 13, 2018 3:09 pm    Post subject: Reply with quote

NeddySeagoon,

You are indeed a guru.

That said, some headway was made with your advice. I had no idea that I had to manually add DBUS to default. I renamed the xorg.conf like you said, it started, and terminated with a screen flicker... that was it... Here's the log output:

Code:

[    93.894]
X.Org X Server 1.19.5
Release Date: 2017-10-12
[    93.894] X Protocol Version 11, Revision 0
[    93.895] Build Operating System: Linux 4.9.76-gentoo-r1 x86_64 Gentoo
[    93.895] Current Operating System: Linux HiroTux 4.9.76-gentoo-r1 #1 SMP Mon Mar 12 07:04:47 EDT 2018 x86_64
[    93.895] Kernel command line: BOOT_IMAGE=/kernel-genkernel-x86_64-4.9.76-gentoo-r1 root=UUID=fff20e25-2423-49bf-929a-2db1226b9215 ro
[    93.895] Build Date: 12 March 2018  03:02:55PM
[    93.895] 
[    93.895] Current version of pixman: 0.34.0
[    93.895]    Before reporting problems, check http://wiki.x.org
   to make sure that you have the latest version.
[    93.895] Markers: (--) probed, (**) from config file, (==) default setting,
   (++) from command line, (!!) notice, (II) informational,
   (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[    93.897] (==) Log file: "/var/log/Xorg.0.log", Time: Mon Mar 12 15:59:38 2018
[    93.899] (==) Using config directory: "/etc/X11/xorg.conf.d"
[    93.899] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[    93.900] (==) No Layout section.  Using the first Screen section.
[    93.900] (==) No screen section available. Using defaults.
[    93.900] (**) |-->Screen "Default Screen Section" (0)
[    93.900] (**) |   |-->Monitor "<default monitor>"
[    93.901] (==) No monitor specified for screen "Default Screen Section".
   Using a default monitor configuration.
[    93.901] (==) Automatically adding devices
[    93.901] (==) Automatically enabling devices
[    93.901] (==) Automatically adding GPU devices
[    93.901] (==) Max clients allowed: 256, resource mask: 0x1fffff
[    93.904] (WW) The directory "/usr/share/fonts/TTF/" does not exist.
[    93.904]    Entry deleted from font path.
[    93.904] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[    93.904]    Entry deleted from font path.
[    93.904] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
[    93.904]    Entry deleted from font path.
[    93.904] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[    93.904]    Entry deleted from font path.
[    93.904]    (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[    93.905] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[    93.905]    Entry deleted from font path.
[    93.905]    (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[    93.905] (==) FontPath set to:
   /usr/share/fonts/misc/
[    93.905] (==) ModulePath set to "/usr/lib64/xorg/modules"
[    93.905] (II) The server relies on udev to provide the list of input devices.
   If no devices become available, reconfigure udev or disable AutoAddDevices.
[    93.905] (II) Loader magic: 0x55584458fd20
[    93.905] (II) Module ABI versions:
[    93.905]    X.Org ANSI C Emulation: 0.4
[    93.905]    X.Org Video Driver: 23.0
[    93.905]    X.Org XInput driver : 24.1
[    93.905]    X.Org Server Extension : 10.0
[    93.907] (++) using VT number 1

[    93.907] (--) controlling tty is VT number 1, auto-enabling KeepTty
[    93.951] (EE) systemd-logind: failed to get session: Launch helper exited with unknown return code 1
[    93.953] (II) xfree86: Adding drm device (/dev/dri/card0)
[    93.959] (--) PCI:*(0:0:2:0) 80ee:beef:0000:0000 rev 0, Mem @ 0xe0000000/16777216, BIOS @ 0x????????/131072
[    93.959] (II) LoadModule: "glx"
[    93.960] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so
[    93.971] (II) Module glx: vendor="X.Org Foundation"
[    93.971]    compiled for 1.19.5, module version = 1.0.0
[    93.971]    ABI class: X.Org Server Extension, version 10.0
[    93.971] (==) Matched vboxvideo as autoconfigured driver 0
[    93.971] (==) Matched vboxvideo as autoconfigured driver 1
[    93.971] (==) Matched modesetting as autoconfigured driver 2
[    93.971] (==) Matched fbdev as autoconfigured driver 3
[    93.971] (==) Matched vesa as autoconfigured driver 4
[    93.971] (==) Assigned the driver to the xf86ConfigLayout
[    93.971] (II) LoadModule: "vboxvideo"
[    93.973] (II) Loading /usr/lib64/xorg/modules/drivers/vboxvideo_drv.so
[    93.974] (II) Module vboxvideo: vendor="Oracle Corporation"
[    93.974]    compiled for 1.19.5, module version = 1.0.1
[    93.974]    Module class: X.Org Video Driver
[    93.974]    ABI class: X.Org Video Driver, version 23.0
[    93.974] (**) Load address of symbol "VBOXVIDEO" is 0x7f8fd4357380
[    93.974] (II) LoadModule: "modesetting"
[    93.974] (II) Loading /usr/lib64/xorg/modules/drivers/modesetting_drv.so
[    93.974] (II) Module modesetting: vendor="X.Org Foundation"
[    93.974]    compiled for 1.19.5, module version = 1.19.5
[    93.974]    Module class: X.Org Video Driver
[    93.974]    ABI class: X.Org Video Driver, version 23.0
[    93.974] (II) LoadModule: "fbdev"
[    93.976] (WW) Warning, couldn't open module fbdev
[    93.976] (II) UnloadModule: "fbdev"
[    93.976] (II) Unloading fbdev
[    93.976] (EE) Failed to load module "fbdev" (module does not exist, 0)
[    93.976] (II) LoadModule: "vesa"
[    93.976] (WW) Warning, couldn't open module vesa
[    93.976] (II) UnloadModule: "vesa"
[    93.976] (II) Unloading vesa
[    93.976] (EE) Failed to load module "vesa" (module does not exist, 0)
[    93.976] (II) VBoxVideo: guest driver for VirtualBox: vbox
[    93.976] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[    93.976] (II) vboxvideo: kernel driver found, not loading.
[    93.977] (II) vboxvideo: kernel driver found, not loading.
[    93.977] (II) modeset(0): using drv /dev/dri/card0
[    93.977] (II) modeset(0): Creating default Display subsection in Screen section
   "Default Screen Section" for depth/fbbpp 24/32
[    93.977] (==) modeset(0): Depth 24, (==) framebuffer bpp 32
[    93.977] (==) modeset(0): RGB weight 888
[    93.977] (==) modeset(0): Default visual is TrueColor
[    93.977] (II) Loading sub module "glamoregl"
[    93.977] (II) LoadModule: "glamoregl"
[    93.977] (II) Loading /usr/lib64/xorg/modules/libglamoregl.so
[    94.002] (II) Module glamoregl: vendor="X.Org Foundation"
[    94.002]    compiled for 1.19.5, module version = 1.0.0
[    94.002]    ABI class: X.Org ANSI C Emulation, version 0.4
[    94.002] (II) glamor: OpenGL accelerated X.org driver based.
[    95.452] (II) glamor: EGL version 1.4 (DRI2):
[    95.452] EGL_MESA_drm_image required.
[    95.458] (EE) modeset(0): glamor initialization failed
[    95.458] (II) modeset(0): ShadowFB: preferred NO, enabled NO
[    95.463] (II) modeset(0): Output VGA-1 has no monitor section
[    95.466] (II) modeset(0): EDID for output VGA-1
[    95.466] (II) modeset(0): Manufacturer: VBX  Model: 0  Serial#: 63964088
[    95.466] (II) modeset(0): Year: 1990  Week: 1
[    95.466] (II) modeset(0): EDID Version: 1.3
[    95.466] (II) modeset(0): Digital Display Input
[    95.466] (II) modeset(0): Indeterminate output size
[    95.466] (II) modeset(0): Gamma: 2.20
[    95.466] (II) modeset(0): DPMS capabilities: StandBy Suspend Off
[    95.466] (II) modeset(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4
[    95.466] (II) modeset(0): Default color space is primary color space
[    95.466] (II) modeset(0): First detailed timing is preferred mode
[    95.466] (II) modeset(0): redX: 0.640 redY: 0.330   greenX: 0.300 greenY: 0.600
[    95.466] (II) modeset(0): blueX: 0.150 blueY: 0.060   whiteX: 0.312 whiteY: 0.329
[    95.467] (II) modeset(0): Manufacturer's mask: 0
[    95.467] (II) modeset(0): Supported detailed timing:
[    95.467] (II) modeset(0): clock: 56.4 MHz   Image Size:  0 x 0 mm
[    95.467] (II) modeset(0): h_active: 952  h_sync: 954  h_sync_end 956 h_blank_end 958 h_border: 0
[    95.467] (II) modeset(0): v_active: 976  v_sync: 976  v_sync_end 1010 v_blanking: 982 v_border: 0
[    95.467] (II) modeset(0): Ranges: V min: 0 V max: 200 Hz, H min: 0 H max: 200 kHz, PixClock max 1005 MHz
[    95.467] (II) modeset(0): Monitor name: VBOX monitor
[    95.467] (II) modeset(0): EDID (in hex):
[    95.467] (II) modeset(0):    00ffffffffffff0058580000b803d003
[    95.467] (II) modeset(0):    0100010380000078eeee91a3544c9926
[    95.467] (II) modeset(0):    0f505400000001010101010101010101
[    95.467] (II) modeset(0):    0101010101010c16b80630d006300202
[    95.467] (II) modeset(0):    0202000000000000000000fd0000c800
[    95.467] (II) modeset(0):    c864000a202020202020000000fc0056
[    95.467] (II) modeset(0):    424f58206d6f6e69746f720a00000010
[    95.467] (II) modeset(0):    000a20202020202020202020202000b9
[    95.467] (II) modeset(0): Printing probed modes for output VGA-1
[    95.467] (II) modeset(0): Modeline "952x976"x59.9   76.25  952 1008 1104 1256  976 979 989 1013 -hsync +vsync (60.7 kHz P)
[    95.467] (II) modeset(0): Modeline "2560x1600"x60.0  348.50  2560 2752 3032 3504  1600 1603 1609 1658 -hsync +vsync (99.5 kHz e)
[    95.467] (II) modeset(0): Modeline "2560x1600"x60.0  268.50  2560 2608 2640 2720  1600 1603 1609 1646 +hsync -vsync (98.7 kHz e)
[    95.467] (II) modeset(0): Modeline "1920x1440"x60.0  234.00  1920 2048 2256 2600  1440 1441 1444 1500 -hsync +vsync (90.0 kHz e)
[    95.467] (II) modeset(0): Modeline "1856x1392"x60.0  218.25  1856 1952 2176 2528  1392 1393 1396 1439 -hsync +vsync (86.3 kHz e)
[    95.467] (II) modeset(0): Modeline "1792x1344"x60.0  204.75  1792 1920 2120 2448  1344 1345 1348 1394 -hsync +vsync (83.6 kHz e)
[    95.467] (II) modeset(0): Modeline "2048x1152"x60.0  162.00  2048 2074 2154 2250  1152 1153 1156 1200 +hsync +vsync (72.0 kHz e)
[    95.467] (II) modeset(0): Modeline "1920x1200"x59.9  193.25  1920 2056 2256 2592  1200 1203 1209 1245 -hsync +vsync (74.6 kHz e)
[    95.467] (II) modeset(0): Modeline "1920x1200"x60.0  154.00  1920 1968 2000 2080  1200 1203 1209 1235 +hsync -vsync (74.0 kHz e)
[    95.467] (II) modeset(0): Modeline "1920x1080"x60.0  148.50  1920 2008 2052 2200  1080 1084 1089 1125 -hsync -vsync (67.5 kHz e)
[    95.467] (II) modeset(0): Modeline "1600x1200"x60.0  162.00  1600 1664 1856 2160  1200 1201 1204 1250 +hsync +vsync (75.0 kHz e)
[    95.467] (II) modeset(0): Modeline "1680x1050"x60.0  146.25  1680 1784 1960 2240  1050 1053 1059 1089 -hsync +vsync (65.3 kHz e)
[    95.468] (II) modeset(0): Modeline "1680x1050"x59.9  119.00  1680 1728 1760 1840  1050 1053 1059 1080 +hsync -vsync (64.7 kHz e)
[    95.468] (II) modeset(0): Modeline "1400x1050"x60.0  121.75  1400 1488 1632 1864  1050 1053 1057 1089 -hsync +vsync (65.3 kHz e)
[    95.468] (II) modeset(0): Modeline "1400x1050"x59.9  101.00  1400 1448 1480 1560  1050 1053 1057 1080 +hsync -vsync (64.7 kHz e)
[    95.468] (II) modeset(0): Modeline "1600x900"x60.0  108.00  1600 1624 1704 1800  900 901 904 1000 +hsync +vsync (60.0 kHz e)
[    95.468] (II) modeset(0): Modeline "1280x1024"x60.0  108.00  1280 1328 1440 1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[    95.468] (II) modeset(0): Modeline "1440x900"x59.9  106.50  1440 1520 1672 1904  900 903 909 934 -hsync +vsync (55.9 kHz e)
[    95.468] (II) modeset(0): Modeline "1440x900"x59.9   88.75  1440 1488 1520 1600  900 903 909 926 +hsync -vsync (55.5 kHz e)
[    95.468] (II) modeset(0): Modeline "1280x960"x60.0  108.00  1280 1376 1488 1800  960 961 964 1000 +hsync +vsync (60.0 kHz e)
[    95.468] (II) modeset(0): Modeline "1366x768"x59.8   85.50  1366 1436 1579 1792  768 771 774 798 +hsync +vsync (47.7 kHz e)
[    95.468] (II) modeset(0): Modeline "1366x768"x60.0   72.00  1366 1380 1436 1500  768 769 772 800 +hsync +vsync (48.0 kHz e)
[    95.468] (II) modeset(0): Modeline "1360x768"x60.0   85.50  1360 1424 1536 1792  768 771 777 795 +hsync +vsync (47.7 kHz e)
[    95.468] (II) modeset(0): Modeline "1280x800"x59.8   83.50  1280 1352 1480 1680  800 803 809 831 -hsync +vsync (49.7 kHz e)
[    95.468] (II) modeset(0): Modeline "1280x800"x59.9   71.00  1280 1328 1360 1440  800 803 809 823 +hsync -vsync (49.3 kHz e)
[    95.468] (II) modeset(0): Modeline "1280x768"x59.9   79.50  1280 1344 1472 1664  768 771 778 798 -hsync +vsync (47.8 kHz e)
[    95.468] (II) modeset(0): Modeline "1280x768"x60.0   68.25  1280 1328 1360 1440  768 771 778 790 +hsync -vsync (47.4 kHz e)
[    95.468] (II) modeset(0): Modeline "1280x720"x60.0   74.25  1280 1390 1430 1650  720 725 730 750 +hsync +vsync (45.0 kHz e)
[    95.468] (II) modeset(0): Modeline "1024x768"x60.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz e)
[    95.468] (II) modeset(0): Modeline "800x600"x60.3   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz e)
[    95.468] (II) modeset(0): Modeline "800x600"x56.2   36.00  800 824 896 1024  600 601 603 625 +hsync +vsync (35.2 kHz e)
[    95.468] (II) modeset(0): Modeline "848x480"x60.0   33.75  848 864 976 1088  480 486 494 517 +hsync +vsync (31.0 kHz e)
[    95.468] (II) modeset(0): Modeline "640x480"x59.9   25.18  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz e)
[    95.468] (II) modeset(0): Output VGA-1 connected
[    95.468] (II) modeset(0): Using exact sizes for initial modes
[    95.468] (II) modeset(0): Output VGA-1 using initial mode 952x976 +0+0
[    95.468] (==) modeset(0): Using gamma correction (1.0, 1.0, 1.0)
[    95.468] (==) modeset(0): DPI set to (96, 96)
[    95.468] (II) Loading sub module "fb"
[    95.468] (II) LoadModule: "fb"
[    95.468] (II) Loading /usr/lib64/xorg/modules/libfb.so
[    95.471] (II) Module fb: vendor="X.Org Foundation"
[    95.471]    compiled for 1.19.5, module version = 1.0.0
[    95.471]    ABI class: X.Org ANSI C Emulation, version 0.4
[    95.471] (==) Depth 24 pixmap format is 32 bpp
[    95.473] (==) modeset(0): Backing store enabled
[    95.473] (==) modeset(0): Silken mouse enabled
[    95.473] (II) modeset(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[    95.475] (==) modeset(0): DPMS enabled
[    95.475] (--) RandR disabled
[    95.477] (II) AIGLX: Screen 0 is not DRI2 capable
[    95.477] (EE) AIGLX: reverting to software rendering
[    95.486] (II) IGLX: enabled GLX_MESA_copy_sub_buffer
[    95.487] (II) IGLX: Loaded and initialized swrast
[    95.487] (II) GLX: Initialized DRISWRAST GL provider for screen 0
[    95.487] (II) modeset(0): Damage tracking initialized
[    95.487] (II) modeset(0): Setting screen physical size to 251 x 258
[    95.716] (II) config/udev: Adding input device Power Button (/dev/input/event0)
[    95.716] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[    95.716] (II) LoadModule: "libinput"
[    95.716] (II) Loading /usr/lib64/xorg/modules/input/libinput_drv.so
[    95.745] (II) Module libinput: vendor="X.Org Foundation"
[    95.745]    compiled for 1.19.5, module version = 0.25.1
[    95.745]    Module class: X.Org XInput Driver
[    95.745]    ABI class: X.Org XInput driver, version 24.1
[    95.745] (II) Using input driver 'libinput' for 'Power Button'
[    95.745] (**) Power Button: always reports core events
[    95.745] (**) Option "Device" "/dev/input/event0"
[    95.746] (**) Option "_source" "server/udev"
[    95.746] (II) event0  - (II) Power Button: (II) is tagged by udev as: Keyboard
[    95.746] (II) event0  - (II) Power Button: (II) device is a keyboard
[    95.746] (II) event0  - (II) Power Button: (II) device removed
[    95.746] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input0/event0"
[    95.746] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[    95.747] (II) event0  - (II) Power Button: (II) is tagged by udev as: Keyboard
[    95.747] (II) event0  - (II) Power Button: (II) device is a keyboard
[    95.747] (II) config/udev: Adding input device Sleep Button (/dev/input/event1)
[    95.747] (**) Sleep Button: Applying InputClass "libinput keyboard catchall"
[    95.747] (II) Using input driver 'libinput' for 'Sleep Button'
[    95.747] (**) Sleep Button: always reports core events
[    95.747] (**) Option "Device" "/dev/input/event1"
[    95.747] (**) Option "_source" "server/udev"
[    95.749] (II) event1  - (II) Sleep Button: (II) is tagged by udev as: Keyboard
[    95.749] (II) event1  - (II) Sleep Button: (II) device is a keyboard
[    95.749] (II) event1  - (II) Sleep Button: (II) device removed
[    95.749] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSLPBN:00/input/input1/event1"
[    95.749] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 7)
[    95.749] (II) event1  - (II) Sleep Button: (II) is tagged by udev as: Keyboard
[    95.749] (II) event1  - (II) Sleep Button: (II) device is a keyboard
[    95.749] (II) config/udev: Adding input device Video Bus (/dev/input/event5)
[    95.749] (**) Video Bus: Applying InputClass "libinput keyboard catchall"
[    95.749] (II) Using input driver 'libinput' for 'Video Bus'
[    95.749] (**) Video Bus: always reports core events
[    95.749] (**) Option "Device" "/dev/input/event5"
[    95.749] (**) Option "_source" "server/udev"
[    95.750] (II) event5  - (II) Video Bus: (II) is tagged by udev as: Keyboard
[    95.750] (II) event5  - (II) Video Bus: (II) device is a keyboard
[    95.750] (II) event5  - (II) Video Bus: (II) device removed
[    95.750] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/LNXVIDEO:00/input/input6/event5"
[    95.750] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 8)
[    95.750] (II) event5  - (II) Video Bus: (II) is tagged by udev as: Keyboard
[    95.750] (II) event5  - (II) Video Bus: (II) device is a keyboard
[    95.751] (II) config/udev: Adding input device VirtualBox mouse integration (/dev/input/event6)
[    95.751] (**) VirtualBox mouse integration: Applying InputClass "libinput pointer catchall"
[    95.751] (II) Using input driver 'libinput' for 'VirtualBox mouse integration'
[    95.751] (**) VirtualBox mouse integration: always reports core events
[    95.751] (**) Option "Device" "/dev/input/event6"
[    95.751] (**) Option "_source" "server/udev"
[    95.751] (II) event6  - (II) VirtualBox mouse integration: (II) is tagged by udev as: Mouse
[    95.751] (II) event6  - (II) VirtualBox mouse integration: (II) device is a pointer
[    95.751] (II) event6  - (II) VirtualBox mouse integration: (II) device removed
[    95.751] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:04.0/input/input7/event6"
[    95.752] (II) XINPUT: Adding extended input device "VirtualBox mouse integration" (type: MOUSE, id 9)
[    95.752] (**) Option "AccelerationScheme" "none"
[    95.752] (**) VirtualBox mouse integration: (accel) selected scheme none/0
[    95.752] (**) VirtualBox mouse integration: (accel) acceleration factor: 2.000
[    95.752] (**) VirtualBox mouse integration: (accel) acceleration threshold: 4
[    95.752] (II) event6  - (II) VirtualBox mouse integration: (II) is tagged by udev as: Mouse
[    95.752] (II) event6  - (II) VirtualBox mouse integration: (II) device is a pointer
[    95.752] (II) config/udev: Adding input device VirtualBox USB Tablet (/dev/input/event4)
[    95.752] (**) VirtualBox USB Tablet: Applying InputClass "libinput pointer catchall"
[    95.752] (II) Using input driver 'libinput' for 'VirtualBox USB Tablet'
[    95.752] (**) VirtualBox USB Tablet: always reports core events
[    95.752] (**) Option "Device" "/dev/input/event4"
[    95.752] (**) Option "_source" "server/udev"
[    95.809] (II) event4  - (II) VirtualBox USB Tablet: (II) is tagged by udev as: Mouse
[    95.809] (II) event4  - (II) VirtualBox USB Tablet: (II) device is a pointer
[    95.809] (II) event4  - (II) VirtualBox USB Tablet: (II) device removed
[    95.809] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:06.0/usb2/2-1/2-1:1.0/0003:80EE:0021.0001/input/input5/event4"
[    95.809] (II) XINPUT: Adding extended input device "VirtualBox USB Tablet" (type: MOUSE, id 10)
[    95.809] (**) Option "AccelerationScheme" "none"
[    95.809] (**) VirtualBox USB Tablet: (accel) selected scheme none/0
[    95.809] (**) VirtualBox USB Tablet: (accel) acceleration factor: 2.000
[    95.809] (**) VirtualBox USB Tablet: (accel) acceleration threshold: 4
[    95.864] (II) event4  - (II) VirtualBox USB Tablet: (II) is tagged by udev as: Mouse
[    95.864] (II) event4  - (II) VirtualBox USB Tablet: (II) device is a pointer
[    95.864] (II) config/udev: Adding input device VirtualBox USB Tablet (/dev/input/mouse1)
[    95.864] (II) No input driver specified, ignoring this device.
[    95.864] (II) This device may have been added with another device file.
[    95.865] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event2)
[    95.865] (**) AT Translated Set 2 keyboard: Applying InputClass "libinput keyboard catchall"
[    95.865] (II) Using input driver 'libinput' for 'AT Translated Set 2 keyboard'
[    95.865] (**) AT Translated Set 2 keyboard: always reports core events
[    95.865] (**) Option "Device" "/dev/input/event2"
[    95.865] (**) Option "_source" "server/udev"
[    95.865] (II) event2  - (II) AT Translated Set 2 keyboard: (II) is tagged by udev as: Keyboard
[    95.865] (II) event2  - (II) AT Translated Set 2 keyboard: (II) device is a keyboard
[    95.865] (II) event2  - (II) AT Translated Set 2 keyboard: (II) device removed
[    95.865] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input2/event2"
[    95.865] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 11)
[    95.867] (II) event2  - (II) AT Translated Set 2 keyboard: (II) is tagged by udev as: Keyboard
[    95.867] (II) event2  - (II) AT Translated Set 2 keyboard: (II) device is a keyboard
[    95.867] (II) config/udev: Adding input device ImExPS/2 Generic Explorer Mouse (/dev/input/event3)
[    95.867] (**) ImExPS/2 Generic Explorer Mouse: Applying InputClass "libinput pointer catchall"
[    95.867] (II) Using input driver 'libinput' for 'ImExPS/2 Generic Explorer Mouse'
[    95.867] (**) ImExPS/2 Generic Explorer Mouse: always reports core events
[    95.867] (**) Option "Device" "/dev/input/event3"
[    95.867] (**) Option "_source" "server/udev"
[    95.867] (II) event3  - (II) ImExPS/2 Generic Explorer Mouse: (II) is tagged by udev as: Mouse
[    95.867] (II) event3  - (II) ImExPS/2 Generic Explorer Mouse: (II) device is a pointer
[    95.867] (II) event3  - (II) ImExPS/2 Generic Explorer Mouse: (II) device removed
[    95.867] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input4/event3"
[    95.867] (II) XINPUT: Adding extended input device "ImExPS/2 Generic Explorer Mouse" (type: MOUSE, id 12)
[    95.867] (**) Option "AccelerationScheme" "none"
[    95.867] (**) ImExPS/2 Generic Explorer Mouse: (accel) selected scheme none/0
[    95.867] (**) ImExPS/2 Generic Explorer Mouse: (accel) acceleration factor: 2.000
[    95.868] (**) ImExPS/2 Generic Explorer Mouse: (accel) acceleration threshold: 4
[    95.868] (II) event3  - (II) ImExPS/2 Generic Explorer Mouse: (II) is tagged by udev as: Mouse
[    95.868] (II) event3  - (II) ImExPS/2 Generic Explorer Mouse: (II) device is a pointer
[    95.868] (II) config/udev: Adding input device ImExPS/2 Generic Explorer Mouse (/dev/input/mouse0)
[    95.868] (II) No input driver specified, ignoring this device.
[    95.868] (II) This device may have been added with another device file.
[    95.869] (II) config/udev: Adding input device PC Speaker (/dev/input/event7)
[    95.869] (II) No input driver specified, ignoring this device.
[    95.869] (II) This device may have been added with another device file.
[    95.895] (II) event0  - (II) Power Button: (II) device removed
[    95.895] (II) event1  - (II) Sleep Button: (II) device removed
[    95.895] (II) event5  - (II) Video Bus: (II) device removed
[    95.895] (II) event6  - (II) VirtualBox mouse integration: (II) device removed
[    95.895] (II) event4  - (II) VirtualBox USB Tablet: (II) device removed
[    95.897] (II) event2  - (II) AT Translated Set 2 keyboard: (II) device removed
[    95.897] (II) event3  - (II) ImExPS/2 Generic Explorer Mouse: (II) device removed
[    95.898] (II) UnloadModule: "libinput"
[    95.898] (II) UnloadModule: "libinput"
[    95.898] (II) UnloadModule: "libinput"
[    95.898] (II) UnloadModule: "libinput"
[    95.898] (II) UnloadModule: "libinput"
[    95.898] (II) UnloadModule: "libinput"
[    95.898] (II) UnloadModule: "libinput"
[    95.906] (II) Server terminated successfully (0). Closing log file.


that said, this concerns me:

Code:

...
[    93.951] (EE) systemd-logind: failed to get session: Launch helper exited with unknown return code 1
...


as I've been trying to use systemd for gnome.

This.... uuuuh, dunno why it's looking for VESA... any advice? not sure what Glamor is referring to.... and well, I don't have the slightest idea on why AIGLX is generating an error, nor how to fix it.

Code:

...
[    93.976] (EE) Failed to load module "vesa" (module does not exist, 0)
...
[    95.458] (EE) modeset(0): glamor initialization failed
...
[    95.477] (II) AIGLX: Screen 0 is not DRI2 capable
[    95.477] (EE) AIGLX: reverting to software rendering
...


Once again, you guys have been a big help. This is the most progress I've had yet. If I'd known about that tidbit with DBUS, I'd have been farther along a week ago.
Back to top
View user's profile Send private message
Hironatashima
Apprentice
Apprentice


Joined: 28 Apr 2005
Posts: 212

PostPosted: Tue Mar 13, 2018 3:40 pm    Post subject: Reply with quote

Further Troubleshooting update for you wonderful gurus out there!

So I had to change my grub2 config to allow for Systemd, and found a nice walkthrough for that here:

https://wiki.gentoo.org/wiki/Systemd#Bootloader

and combined it with the initial install handbook for gentoo to rebuild my grub in accordance with Systemd.

so that fixed my systemd error, and I'm trudging on to figure out what the actual @$!!@#$ to do with the rest. I lost the Systemd error and added this error:

Code:

...
[    42.445] (WW) Warning, couldn't open module fbdev
[    42.445] (II) UnloadModule: "fbdev"
[    42.445] (II) Unloading fbdev
[    42.445] (EE) Failed to load module "fbdev" (module does not exist, 0)
...


so now I'm pushing ahead and trying to fix:

fbdev
vesa
glamor which seems to be tied to OpenGL
and finally AIGLX.

I might even try just mess with GDM after all this troubleshooting to see if this will even matter.... however, it's bugging me, so I may actually just try to fix it for the sake of fixing it.
Back to top
View user's profile Send private message
Hironatashima
Apprentice
Apprentice


Joined: 28 Apr 2005
Posts: 212

PostPosted: Tue Mar 13, 2018 4:20 pm    Post subject: Reply with quote

Another update, I've done a bit of research, it seems that fbdev and vesa are errors from when X autodetects drivers. Unfortunately, the fix to eliminate those errors is to either a) ignore them, or b) install the packages with those particular drivers/scripts.

Now I'm looking to fix glamor, and the AIGLX of OpenGL. Remaining troubleshooting:

glamor
AIGLX.

I've tried to startx again, the screen blinks, resizes, and then X closes, but no fatal errors anymore.
Back to top
View user's profile Send private message
Hironatashima
Apprentice
Apprentice


Joined: 28 Apr 2005
Posts: 212

PostPosted: Tue Mar 13, 2018 4:31 pm    Post subject: Reply with quote

Final update, at least on this matter:

I've determined that my critical error that was blocking my advancement was ultimately DBUS not starting.

All the research that I have done on following errors to this end points to that being the culprit. The errors that I was seeing was caused by autodetection, ultimately.

my proof of concept was adding the following lines to my test user's .xinitrc:

Code:

#!/bin/sh


twm &
xsetroot -solid CornflowerBlue &
xclock -geometry 100x100-1+ &
xterm -geometry 80x50+494+51 &
xterm -geometry 80x20+494-0 &
exec xterm -geometry 80x66+0+0 -name login


One of the handbooks that I found states that this creates an X window session with three terminal windows that pop open and stays until you exit the terminal windows.

Next step is to get GDM up. I may just continue to chronicle my progress on this post, if there are no objections.
Back to top
View user's profile Send private message
Hironatashima
Apprentice
Apprentice


Joined: 28 Apr 2005
Posts: 212

PostPosted: Tue Mar 13, 2018 4:44 pm    Post subject: Reply with quote

Final update for getting Gnome up and running:

The point I was at, was legit the very end of the line..... through systemd:

Code:

systemctl enable --now gdm.service


and Gnome started up like a charm. now to make sure everything is good to go!

Topic has been updated to solved!

Thank you all for the input, and help!
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 41320
Location: 56N 3W

PostPosted: Tue Mar 13, 2018 5:05 pm    Post subject: Reply with quote

Hironatashima,

Check your Xorg.0.log one more time.
There are degrees of working. Has the glamour error gone away?

Software rendering works but is very slow. You can also try
Code:
$ glxinfo | head -n 3
name of display: :0
display: :0  screen: 0
direct rendering: Yes
and check that you have direct rendering.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
Hironatashima
Apprentice
Apprentice


Joined: 28 Apr 2005
Posts: 212

PostPosted: Tue Mar 13, 2018 5:09 pm    Post subject: Reply with quote

the lines that are relevant:

Code:

...
   "Default Screen Section" for depth/fbbpp 24/32
[  3664.979] (==) modeset(0): Depth 24, (==) framebuffer bpp 32
[  3664.979] (==) modeset(0): RGB weight 888
[  3664.979] (==) modeset(0): Default visual is TrueColor
[  3664.979] (II) Loading sub module "glamoregl"
[  3664.979] (II) LoadModule: "glamoregl"
[  3664.979] (II) Loading /usr/lib64/xorg/modules/libglamoregl.so
[  3664.984] (II) Module glamoregl: vendor="X.Org Foundation"
[  3664.984]    compiled for 1.19.5, module version = 1.0.0
[  3664.984]    ABI class: X.Org ANSI C Emulation, version 0.4
[  3664.984] (II) glamor: OpenGL accelerated X.org driver based.
[  3665.082] (II) glamor: EGL version 1.4 (DRI2):
[  3665.082] EGL_MESA_drm_image required.
[  3665.082] (EE) modeset(0): glamor initialization failed
...


glamor still hates me, it looks like, lol.

glxinfo throws an error:

Code:
Error: Unable to open display


so what do you think?
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 41320
Location: 56N 3W

PostPosted: Tue Mar 13, 2018 5:15 pm    Post subject: Reply with quote

Hironatashima,

At an educated guess, you need to set the egl USE flag in make.conf and rebuild all affected packages.

Check your
Code:
emerge --info
If USE egl is not listed, its worth trying.
Code:
$ equery h egl
 * Searching for USE flag egl ...
[IP-] [  ] dev-qt/qtgui-4.8.7:4
[IP-] [  ] dev-qt/qtgui-5.9.4-r3:5/5.9
[IP-] [  ] dev-qt/qtopengl-4.8.7:4
[IP-] [  ] media-libs/mesa-18.0.0_rc4:0
[IP-] [  ] media-video/mpv-0.27.2:0
[IP-] [  ] x11-apps/mesa-progs-8.3.0:0
notice that mesa will be rebuilt and your error includes
Code:
[  3664.984] (II) glamor: OpenGL accelerated X.org driver based.
[  3665.082] (II) glamor: EGL version 1.4 (DRI2):
[  3665.082] EGL_MESA_drm_image required.

_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
Hironatashima
Apprentice
Apprentice


Joined: 28 Apr 2005
Posts: 212

PostPosted: Tue Mar 13, 2018 5:24 pm    Post subject: Reply with quote

interesting.

Pastebin:

Code:

...
USE="gtk gnome -sysv-utils -qt4 -qt5 -kde dvd alsa cdr dvdr X systemd branding wayland xa gles2 egl jpeg2k raw client python upnp-av youtube networkmanager"
...


so I wonder if perhaps I need to recompile Mesa then? I don't recall exclusively building it into my system.
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 41320
Location: 56N 3W

PostPosted: Tue Mar 13, 2018 5:53 pm    Post subject: Reply with quote

Hironatashima,

Try
Code:
emerge -av1 mesa

If the egl USE flag is egl* in green, its been changed since mesa was built and needs to be rebuilt.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
Hironatashima
Apprentice
Apprentice


Joined: 28 Apr 2005
Posts: 212

PostPosted: Tue Mar 13, 2018 5:57 pm    Post subject: Reply with quote

NeddySeagoon,

Thank you again, your advice has been so helpful.

I am in the midst of rebuilding mesa right now, actually. It's a pretty lengthy emerge, that's for sure. It just finished, and I'm going to go ahead and reboot the system to test the results.
Back to top
View user's profile Send private message
Hironatashima
Apprentice
Apprentice


Joined: 28 Apr 2005
Posts: 212

PostPosted: Tue Mar 13, 2018 6:09 pm    Post subject: Reply with quote

Here's the pastebin, currently:

https://paste.pound-python.org/show/KqboU48xUepcyI9oVLqf/

it still fails, and I'm not sure how to fix it. rebuilding MESA did improve the graphics flow of the VBox exponentially, however. but still....
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 41320
Location: 56N 3W

PostPosted: Tue Mar 13, 2018 7:04 pm    Post subject: Reply with quote

Hironatashima,

The preferred list of video drivers, in order is
Code:
[    13.212] (==) Matched vboxvideo as autoconfigured driver 0
[    13.212] (==) Matched vboxvideo as autoconfigured driver 1
[    13.212] (==) Matched modesetting as autoconfigured driver 2
[    13.212] (==) Matched fbdev as autoconfigured driver 3
[    13.212] (==) Matched vesa as autoconfigured driver 4
[    13.213] (==) Assigned the driver to the xf86ConfigLayout

It should be using vboxvideo, rather than modesetting.

All the drivers will be loaded, if they exist. If not the load fails with an (EE) but its not fatal as long as one driver works.
Here, vboxvideo is the one you need.
It loaded
Code:
 [    13.213] (II) LoadModule: "vboxvideo"
[    13.216] (II) Loading /usr/lib64/xorg/modules/drivers/vboxvideo_drv.so
[    13.216] (II) Module vboxvideo: vendor="Oracle Corporation"
[    13.216]    compiled for 1.19.5, module version = 1.0.1
[    13.216]    Module class: X.Org Video Driver
[    13.216]    ABI class: X.Org Video Driver, version 23.0


Code:
[    13.377] EGL_MESA_drm_image required.
[    13.377] (EE) modeset(0): glamor initialization failed

Do you have any other packages that need to be rebuilt for changed USE flags?

Code:
emerge -uDUav @world
will tell.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
Hironatashima
Apprentice
Apprentice


Joined: 28 Apr 2005
Posts: 212

PostPosted: Tue Mar 13, 2018 7:19 pm    Post subject: Reply with quote

NeddySeagoon,

Thanks for seeing this through,

So, the only way I know of to set modesetting is in the xorg.conf file, and I renamed that, so it wouldn't have anything but the default to work with. So how do I force it to use vboxvideo?

second, I'm having some dependency issues with doing any emerges that are affecting @world, right now, that I'm trying to take care of. I've been trying to figure out how to solve the dependency conflict that has net-libs/webkit-gtk locked up. says it has umet requirements with a whole lot of USE flags following it. I guess I have to try them out. What does it mean when a USE flag is in blue? such as displayed here:

(-aqua) -coverage -doc -nsplugin -test
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 41320
Location: 56N 3W

PostPosted: Tue Mar 13, 2018 7:34 pm    Post subject: Reply with quote

Hironatashima,

A USE flag in Red is on, a USE flag in Blue is off
A USE flag in Green, with a * has had its setting changed since the package was built.
That means the new setting does not yet apply to the package.

The brackets ( ) around a USE setting means that the setting is forced in your profile.
That's not to say you can't change it but it requires some extra steps.
You also get to keep all the pieces if it breaks, since USE settings are usually forced for good reasons.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
Hironatashima
Apprentice
Apprentice


Joined: 28 Apr 2005
Posts: 212

PostPosted: Tue Mar 13, 2018 7:39 pm    Post subject: Reply with quote

localhost ~ # emerge -uDUav @world
here's the raw dump from my attempted @world emerge:

Code:

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

Calculating dependencies... done!

!!! The ebuild selected to satisfy "net-libs/webkit-gtk:4[introspection]" has unmet requirements.
- net-libs/webkit-gtk-2.18.6::gentoo USE="X egl geolocation gles2 gnome-keyring gstreamer introspection jit libnotify opengl spell wayland webgl (-aqua) -coverage -doc -nsplugin -test" ABI_X86="(64)"

  The following REQUIRED_USE flag constraints are unsatisfied:
    webgl? ( exactly-one-of ( gles2 opengl ) )

  The above constraints are a subset of the following complete expression:
    geolocation? ( introspection ) gles2? ( egl ) introspection? ( gstreamer ) nsplugin? ( X ) webgl? ( exactly-one-of ( gles2 opengl ) ) !webgl? ( at-most-one-of ( gles2 opengl ) ) webgl? ( gstreamer ) wayland? ( egl ) any-of ( aqua wayland X )

(dependency required by "gnome-extra/sushi-3.24.0::gentoo" [installed])
(dependency required by "gnome-base/nautilus-3.24.2.1::gentoo[previewer]" [installed])
(dependency required by "gnome-extra/gnome-tweak-tool-3.24.1::gentoo" [installed])
(dependency required by "@selected" [set])
(dependency required by "@world" [argument])


I've been trying to mess with this for a few days as well, but everything else was working so it hasn't been my focus just yet. but now it looks like I need to get this problem solved now too.

what are your thoughts?
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Desktop Environments All times are GMT
Goto page 1, 2, 3, 4  Next
Page 1 of 4

 
Jump to:  
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