Ubuntu

Kubuntu Locking up

Asked by James Anning

Hi,
I just did a fresh install of Kubuntu 14.10 beta 2, KDE 5 plasma (my boot drive is a samsung 840 solid

state drive - not sure if that will matter)

I will be working in Dolphin file explorer browsing a directory when out of the blue, the machine locks

up, the mouse will move but nothing on the mouse or keyboard will work. I have to hit the power button

and reboot. This also happens when in systems settings, there, and Dolphin is where this has happened,

may occur elsewhere - don't know.

When it boots up, the blue "Kubuntu" will come up center screen then one of the issues below will

occur:

1) starting automatic crash report generation: apport

2) starting automatic crash report generation: apport
     restoring resolver state ...

3) starting automatic crash report generation: apport
     restoring resolver state ...
     starting uuid generator uuidd

4) starting automatic crash report generation: apport
     restoring resolver state ...
     starting uuid generator uuidd
  :tc/rc2.d/S0Z sddm: 4: .: can't open /lib/init/init-d-script
                                                        saned disabled edit /etc/defualt/saned

when 1,2 or 3 happen, I have to hit the power button or unplug the PC
when 4 happens, it does boot up. Number 4 may be due to my newly created sddm.conf file containing:

[Autologin]
User=ajub2
Session=plasma.desktop

Please advise, thanks James.

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
actionparsnip (andrew-woodhead666) said : 		#1

Report a bug.

Utopic is not ready and not stable so random crashing is completely expected. If you are happy to put up with crashing and feature holes, up to and even a few weeks after release, but want to submit bugs to resolve issues then by all means use Utopic.

If you want an OS that works then I suggest you wipe Utopic off and do a clean install of Trusty. Trusty is rock solid and is LTS so supported til April 2019. Utopic only has 9 months support once it is released.

It's a beta release. What did you expect!?

Revision history for this message
James Anning (janning197) said : 		#2

Its a beta release at the Release Candidate stage,,,,,I was expecting it to be close to the released product.
Sorry, I guess I'm used to windows, the later betas and RC with that is pretty stable.

AJ

Revision history for this message
actionparsnip (andrew-woodhead666) said : 		#3

Yes it is "pretty stable" but that isn't "stable" is it. You will get issues.

Pre-releases are not for casual users.

Revision history for this message
asher (asher-chayyim) said : 		#4

The solution (until this bug is fixed) is to kill the X process.

do the following while that error message is on the screen:

ctrl+alt+f1 (this will open console/terminal)
(then enter your username and password)
ps aux | grep X (this will show info about the X process)
sudo kill pid (this kills the X process, where pid is the process id of the X process shown by the previous command)

Revision history for this message
actionparsnip (andrew-woodhead666) said : 		#5

Or run:

killall -u $USER

bit easier.

Revision history for this message
asher (asher-chayyim) said : 		#6

Also some people suggested that you create a blank file for the missing one:

sudo touch /lib/init/init-d-script

But that alone hasn't worked for me.

So I also have to kill the X process on every boot (see my other comment above) in order to get to the graphic logon screen.

Can you help with this problem?

Provide an answer of your own, or ask James Anning for more information if necessary.

To post a message you must log in.