Re: [gentoo-user] Can't get the GUI to stay up for more than a minute or so before crashing

[Michael <confabulate@kintzios.com>]

[-- Attachment #1: Type: text/plain, Size: 5497 bytes --]

On Saturday, 22 June 2024 19:13:42 BST Dale wrote:
> Dale wrote:
> > Michael wrote:


> root@Gentoo-1 ~ # xrandr --verbose
> Can't open display
> root@Gentoo-1 ~ #
> 
> 
> That's after I started display-manager but this time, it did nothing. 
> The screen stayed on a console.  I did move the cable to another port
> before booting up. 

The xerver is not running.


> This is the other info except nothing xorg there, just wayland.  See
> below for more on that. 
> 
> 
> root@Gentoo-1 ~ # cat /home/dale/.local/share/sddm/wayland-session.log

I thought you said you were having a problem starting a X session, not 
starting a Wayland session.  What desktop session are you selecting in your 
SDDM?

[snip ...]
> dbus-daemon[2766]: [session uid=1000 pid=2766 pidfd=5] Successfully
> activated service 'org.freedesktop.portal.Documents'
> fuse: device not found, try 'modprobe fuse' first
> error: fuse init failed: Can't mount path /run/user/1000/doc

It can't find the path /run/user/1000/ for your user to be able to set up 
desktop environment variables, user authentication and other desktop related 
files.  Is your fs mounted fully?

[snip ...]
> No backend specified, automatically choosing drm
> kwin_wayland_drm: No suitable DRM devices have been found
[snip ...]

It should have found and listed your video card here ^^^^ and its drivers. 

Can it not detect your card at all?  :-/


> The Wayland connection broke. Did the Wayland compositor die?
> The Wayland connection broke. Did the Wayland compositor die?
> The Wayland connection broke. Did the Wayland compositor die?
> qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
> dbus-daemon[2766]: [session uid=1000 pid=2766 pidfd=5] Activated service
> 'org.freedesktop.impl.portal.desktop.kde' failed: Process
> org.freedesktop.impl.portal.desktop.kde exited with status 1
> 
> (/usr/libexec/xdg-desktop-portal:2787): xdg-desktop-portal-WARNING **:
> 03:20:14.512: Failed to create settings proxy: Error calling
> StartServiceByName for org.freedesktop.impl.portal.desktop.kde: Process
> org.freedesktop.impl.portal.desktop.kde exited with status 1
> 
> (/usr/libexec/xdg-desktop-portal:2787): xdg-desktop-portal-WARNING **:
> 03:20:14.512: No skeleton to export
> kdeinit5: Communication error with launcher. Exiting!
> dbus-daemon[2766]: [session uid=1000 pid=2766 pidfd=5] Activating
> service name='org.freedesktop.impl.portal.desktop.kde' requested by
> ':1.5' (uid=1000 pid=2787 comm="/usr/libexec/xdg-desktop-portal"
> label="kernel")
> Error: could not determine $DISPLAY.
> Error: Can not contact kdeinit5!
> org.kde.startup: "kdeinit5_shutdown" () exited with code 255
> startplasma-wayland: Shutting down...
> startplasmacompositor: Shutting down...
> startplasmacompositor: Done.
> root@Gentoo-1 ~ #
> 
> 
> Since it complains about DRM.  Here's this.
> 
> 
> root@Gentoo-1 ~ # lsmod
> Module                  Size  Used by
> nvidia_drm            102400  0
> nvidia_modeset       1544192  1 nvidia_drm
> nvidia              59744256  1 nvidia_modeset
> root@Gentoo-1 ~ #

I have no experience with Nvidia to know what modules are needed.


> What's that about fuse???

It seems it can't find the fs containing the /run directory and it tries to 
launch fuse to probe & mount block devices.


> To add to this, this is a new video card.  It's a P1000, Nvidia of
> course.  Could it be a bad card that works to a point but then dies?  I
> got a older PCIe V2 card I'm going to try.  That was the card that was
> in during the early stages.  The P1000 was the one that got hung up by
> the post office and arrived days late.  I'm going to test the other
> slower card shortly, got to remember to downgrade nvidia-drivers to
> tho.  ;-)

You may want to walk through the Gentoo wiki for Nvidia to make sure you have 
all necessary drivers installed.  Then you may be more productive if you try 
to solve either Xorg, or Wayland desktop session problems separately.

If the problem is with your hardware, neither desktop session type will work.

 
> On the above wayland info, I recall some having issues with wayland. I
> tried to disable wayland by putting -wayland in make.conf and
> rebuilding.  Since it wanted to rebuild a lot, I removed everything GUI
> related from the world file and then ran --depclean to clean house. 
> Then I emerge everything I removed from the world file again, while I
> napped.  The output above could be old but may still provide a clue.  If
> I could figure out how to go back to KDE V5 instead of the new V6, I
> would, to eliminate a wayland issue if nothing else.  I removed
> everything from /etc/portage/package.keyword file but I think KDE V6 is
> stable now.  The odd part, right now, even sddm isn't coming up. 

kde-plasma/plasma-meta-6.1.0 is still in testing - I sync'ed earlier today:

~ $ eshowkw kde-plasma/plasma-meta
Keywords for kde-plasma/plasma-meta:
              |                               |   u   |  
              | a   a     p s     l r   a     |   n   |  
              | m   r h   p p   i o i s l m m | e u s | r
              | d a m p p c a x a o s 3 p 6 i | a s l | e
              | 6 r 6 p p 6 r 8 6 n c 9 h 8 p | p e o | p
              | 4 m 4 a c 4 c 6 4 g v 0 a k s | i d t | o
--------------+-------------------------------+-------+-------
[I]5.27.11-r1 | + ~ + o o ~ o + o ~ ~ o o o o | 8 o 5 | gentoo
--------------+-------------------------------+-------+-------
     6.1.0    | ~ o o o o o o o o o o o o o o | 8 o 6 | gentoo


[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]