i update plasma to 5.11.5 only get a black screen and the white mouse .
* the complete build log and the output of `emerge -pqv '=kde-plasma/plasma-workspace-5.11.5::gentoo'`.
* The complete build log is located at '/var/tmp/portage/kde-plasma/plasma-workspace-5.11.5/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/kde-plasma/plasma-workspace-5.11.5/temp/environment'.
USE="X Xbash-completion a52 aac acl acpi activities alsa amd64 berkdb bindist bluetooth branding bzip2 cairo cdda cdr cjk cli crypt cups cxx dbus declarative dri dts dvd dvdr emboss encode exif fam firefox flac fortran gdbm gif glamor gpm gtk iconv ipv6 jepg jpeg kde kipi kwallet lcms ldap libnotify mad mmx mng modules mp3 mp4 mpeg multilib ncurses nls nptl ogg opengl openmp pam pango pcre pdf phonon plasma png policykit ppds qml qt3support qt5 readline sdl seccomp semantic-desktop spell sse sse2 sse3 sse4 ssl startup-notification svg symlink systemd tcpd tiff truetype udev udisks unicode upower usb vorbis widgets wifi wxwidgets x264 xattr xcb xcomposite xft xml xv xvid zlib" ABI_X86="64" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx via82xx-modem ymfpci" APACHE2_MODULES="authn_core authz_core socache_shmcb unixd actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache cgi cgid dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" CALLIGRA_FEATURES="kexi words flow plan sheets stage tables krita karbon braindump author" COLLECTD_PLUGINS="df interface irq load memory rrdtool swap syslog" CPU_FLAGS_X86="mmx mmxext sse sse2" ELIBC="glibc" GPSD_PROTOCOLS="ashtech aivdm earthmate evermore fv18 garmin garmintxt gpsclock isync itrax mtk3301 nmea ntrip navcom oceanserver oldstyle oncore rtcm104v2 rtcm104v3 sirf skytraq superstar2 timing tsip tripmate tnt ublox ubx" GRUB_PLATFORMS="efi-64" INPUT_DEVICES="synaptics evdev" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LIBREOFFICE_EXTENSIONS="presenter-console presenter-minimizer" OFFICE_IMPLEMENTATION="libreoffice" PHP_TARGETS="php5-6 php7-0" POSTGRES_TARGETS="postgres9_5" PYTHON_SINGLE_TARGET="python3_5" PYTHON_TARGETS="python2_7 python3_5" RUBY_TARGETS="ruby25" USERLAND="GNU" VIDEO_CARDS="intel nvidia" XTABLES_ADDONS="quota2 psd pknock lscan length2 ipv4options ipset ipp2p iface geoip fuzzy condition tee tarpit sysrq steal rawnat logmark ipmark dhcpmac delude chaos account"
how can is slow the patch -p1 often fail and the plasma black screen . By the way the plasma can choice version update and delect very difficult.
Apart from that, the black screen issue is 90% an sddm issue, not Plasma. Try downgrade to 0.15.0.
before i try systemctl disable sddm use startx it is same black screen it maybe be not sddm issue?
Tried that, still not work. Cursor turns red as soon as I move mouse. Screen is black.
Was busy with migration to profile 17, doing emerge -e world when it died at about 1400/1868. Some package not in portage anymore. Guess I should have run Update step first.
So ran updates (twice) and thought it wise to reboot at this point. Bad idea. Now KDE not starting.
Same problems here, on 3 profile 17.0 ~amd64 Installs. One of them can't get even get a DM (sddm or lightdm) up, but can do an emerge -e @system and @world, has networking, etc, with all emerge/portage functions OK.
Seems to be a kde plasma along with no xorg-x11. (No screen found) Tried lots of stuff for two says now. kernel rebuild, all sorts of x11 settings & rebuilding various items even after the @ world rebuild. Nothing works.
The other two installs will so far get sddm up, and run lxde or xfce4 OK. Seems to be an sddm/xorg/kde plasma/qt complex problem that so far defies my understanding. Maybe the last kde updates would like gcc-7.3.0 or another qt update?
What about downgrading kde-plasma/sddm-kcm along with the sddm downgrade mentioned? Really annoying having all three systems having problems.
Really strange is the @world rebuild was flawless.
On my x370 box, I have two Gentoo's. On the one which I could get into with fxce4, I created a new user, and rebooted into kde plasma with sddm. That one created a new set of config files, and is working very good, albeit needed to do my usual custom looks and configuring routines.
From the now working sda11 Gentoo kde GUI I went into the sda6 /home/wrc/.config and removed the four "plasma" config files, and then rebooted (out of the good sda11 Main Gentoo) and into the sda6 Gentoo which now brought up lightdm and I was able to go into kde plasma, Finally!
Needs some configuring work, and likely I'll do a full rebuild on both systems, but it seems this is at least on my systems definitely a plasma related problem. Perhaps old .config files are really outdated. The "new user" on the other sda11 system was pristine, and I also removed the 4 plasma files belonging to the my main sda11 user, and he too can get plasma with sddm, but it isn't "pristine" (a few missing icons, etc. Maybe just do a full qt/kde rebuild and see if that works, or maybe even easier just remove all .config kde files, and reboot. Anyway, I was going nuts for two days.
I deleted the contents of /var/lib/sddm/ and the segfault stopped and sddm started working again.
Had already gone full circle by that time and had the latest sddm and the kde plasma beta installed again.
Desktop was blown up, cleaned out a bunch of desktop related files from ~/.config and a few from ~/.local and got a desktop back.
In case it helps anyone.