Created attachment 7720 [details] .tgz of /root/drakx on i586 host gx280 HTTP installed 2016-04-27 rpm -qi task-plasma5-minimal "...Description : ...its purpose is to contain minimal dependencies for running a minimal Plasma 5 desktop environment." To reproduce: 1.Install minimal 2.ensure Xorg is functional by opening an IceWM session via startx 3.urpmi task-plasma5-minimal 4.startx /usr/bin/startkde Actual results: 1-xmessage window and mouse pointer open on otherwise empty background: "Could not start D-Bus. Can you call qdbus?" 2-ps -A shows dbus-launch and dbus-daemon processes running Expected results: 1-working Plasma session (taskbar, apps menu starter, etc.)
@ neoclust Sorry, started assigning again.... is there anyone you'd like me to put in the CC for Plasma5/Kf5 bugs?
Assignee: bugsquad => mageiaCC: (none) => marja11
Not tried this way, but minimal install with X plus thereafter urpmi --no-recommends task-plasma5-minimal gave after a reboot a sddm up and Plasma5 desktop started from there OK...
CC: (none) => jyri2000
I've got this bug upgrading from mageia 5 to 6
CC: (none) => saveurlinux
Created attachment 7780 [details] drakbug_report
I could start kde plasma 5 after the followings changes on: '/usr/bin/startkde' 21c21,22 < bindir=`echo "$0" | sed -n 's,^\(/.*\)/[^/][^/]*$,\1,p'` --- > #bindir=`echo "$0" | sed -n 's,^\(/.*\)/[^/][^/]*$,\1,p'` > bindir=/usr/lib/qt5/bin 23c24 < qbindir=`qtpaths --binaries-dir` --- > qbindir=`/usr/lib/qt5/bin/qtpaths --binaries-dir` 205c206 < scriptpath=`qtpaths --paths ConfigLocation | tr ':' '\n' | sed 's,$,/plasma-workspace,g'` --- > scriptpath=`/usr/lib/qt5/bin/qtpaths --paths ConfigLocation | tr ':' '\n' | sed 's,$,/plasma-workspace,g'` maybe it could help fixing the bug
With 4 weeks past, I did: 1.urpmi.update -a 2.urpme task-plasma5-minimal 3.urpmi --auto-select 4.reboot 5.urpmi task-x11 6.startx (opened IceWM) & exit session 7.urpmi task-plasma5-minimal 8.startx /usr/bin/startkde This produced same failure as described in comment 0.
After adding no-recommends to urpmi.cfg, I repeated the steps in comment 6, except for #4, on first boot after a fresh minimal mga5 installation. #6 exited with server error because there was no video driver installed, so I repeated #6 after doing urpmi x11-driver-video-ati. That too exited, as IceWM also had not been installed. After adding plymouth to skip.list I tried urpmi icewm, but that doesn't work. So I proceeded with urpmi task-plasma5-minimal, which doesn't require plymouth, and saw installed 277 new packages. Startx produces the same error as in comment 0.
Assignee: mageia => kde
After another --auto-select on comment 0 system, "Could not start D-Bus. Can you call qdbus?" is still happening instead of Plasma.
After another --auto-select on comment 0 system, "Could not start D-Bus. Can you call qdbus?" is still happening instead of Plasma. Same occurs if attempting session open from sddm. Konsole will run started from an IceWM session. When I run systemsettings5 from Konsole, the window contains only one icon: search; and keyboard is missing from input devices. No luck trying to extract any specifically x-session info from journalctl, always "-- No entries --". ~/.xsession-errors doesn't exist. Xorg.0.log offers no clues.
Today's update from "Cauldron" to 6 finally enabled a Plasma 5 session to start (but with no apparent way to configure panel).
Upgrade from KDE4 on 5 to Plasma on 6 on x86_64 host fi965 has now Plasma able to start, but repeated black screening makes it unusable, as explained in the mailing list here: https://ml.mageia.org/l/arc/dev/2017-07/msg00225.html
Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information. Closing as OLD.
Status: NEW => RESOLVEDCC: (none) => ouaurelienResolution: (none) => OLD