Plasma 5 beta

[mparillo]

I tried to try it out using the 14.10 plasma 5 iso in Virtualbox but it didn't work.

When you say "didn't work", was it something like this: https://bugs.launchpad.net/ubuntu/+s...s/+bug/1362631
Or it did not boot at all?

[claydoh]

The dd command? Like in this tut?
It states that:

Yeah, actually. It is one of a few ways to make a working install disk that works, unless they have fixed things with the usb-creator found in 14.04. I did give more than one option for the student.....

[Fintan]

I finally got the usb to work with todays daily and usb-creator from 14.10. Looks nice but really sluggish.

[oshunluvr]

dd is only a disk destroyer when you use it wrong. There's no error checking of what you're typing in so it is on you to be correct, and as I've always said: Computers are dumb. If you tell them to do something wrong, they will - and at a very high rate of speed.

[DejanN]

No DiskDestroyer or USB here. Good ol' live DVD.
15. October daily build FINALLY works for me.
Tried it live and liked it so much that I installed it.
Once I got rid of the “Snow White” theme - I really love it; so much that I wont go back, bugs or no bugs.
Great work.

[Fintan]

I just upgraded my 14.04 to 14.10 with no issues.

I then wanted to go plasma5 with:

sudo apt-add-repository ppa:kubuntu-ppa/next
sudo apt update
sudo apt install kubuntu-plasma5-desktop
sudo apt full-upgrade
sudo reboot

Rebooting got me to a message:

saned disabled: edit /etc/default/saned

then nothing. The booting just stopped.

I shut the machine off and then booted again. got passed the saned message to a blannk black screen. Then Standstill.

I went through this process a few times with low latency kernel and non low latency kernel. Either the boot stopped at the saned message of a black screen.

Any ideas?

Bthw my /etc/default/saned shows:

# Defaults for the saned initscript, from sane-utils

# Set to yes to start saned
RUN=no

# Set to the user saned should run as
RUN_AS_USER=saned

[Worzel]

I used the same upgrade sequence as you and installed with no problem. Saned shows exactly as yours - possibly the problem is prior to the saned call.
Sorry can't be more helpful.

[mrboese]

I also upgraded and ran into a new problem: LightDM starts while SDDM is starting, resulting in .... stuff.
I had to remove lightdm and now it seems to work fine so far.

[Fintan]

apt remove lightdm?

Edit: Ook, did that now I get a nice white screen

[claydoh]

make sure sddm is installed first, but the correct package to remove lightdm is lightdm-kde-greeter.

i would try manually starting sddm :
switch to a different terminal via ctrl-alt-f1 or similar
sudo service lightdm stop (just in case)
sudo service sddm stop
sudo service sddm start

Note any errors
You can get to a desktop either using the command
startkde
or
startx

I had this problem myself earlier but it was due to a self-mangled sddm config file, I believe.

[Fintan]

Thanks claydoh
remove lightdm is lightdm-kde-greeter

gives: not installed

install sddm gives: latest version

any of these:
sudo service lightdm stop (just in case)
sudo service sddm stop
sudo service sddm start
give: no such instance.

startkde give: not installed please install....kde-desktop (or similar)

startx gives me a bunhc of errors

hmmm...

[claydoh]

The bunch of errors might be the key

Sent from my Verizon HTC Droid DNA Android smartphone running ViperRom Kit Kat, using Tapatalk, like all that really matters

[Fintan]

Ok. I'll have another look

[Fintan]

Ok. I went back to recovery mode and tried:
startkde
this gave: ....install kde-workspace-bin

I then tried startx and got:
.....errors from xkbcomp are not fatal to xserver
xnit: connection to xserver lost

then

........task sh:1379 blocked for more than 120 seconds

I have no clue what all this really means

[claydoh]

No don't go to recovery mode, switch to a different terminal by ctrl-alt-f1 (or f2,3,4, etc), log in that way with your user account, and type in "startx" if "startkde" won't work.

You can reinstall lightdm-kde-greeter or some other login manager such as lxdm, and still get into Plasma 5, and switching between the login managers is pretty easy

sudo dpkg-reconfigure sddm

or substitute

lightdm

or any other one you may have installed.

I am guessing that you did not get the prompt to switch the login manager during your plasma 5 upgrade, or it didn't work fully or correctly.
You may want to just try running the dpkg-reconfigure command to see which one is selected.