Kubuntu 15.04 "sddm-greeter' crashes on start up.

[PJJ]

I have installed 15.04 at least three times with various methods now with identical results:
"sddm-greeter' crashes.

The issue must have something to do with 'plasma' because it is mentioned in the error message. Is this a common bug (as it appears from Net postings) or what can be done to fix the problem.

I am back on my ancient Toshiba A45. Running 14.10 without any problems.

None of the 'fixes' I found resolved this issue.

Does anyone have a solution for this problem, please?

[ronw]

I don't have a solution, but you are more likely to get help if you post the actual error message, and list the fixes you tried that didn't work.

[PJJ]

I tried that before. No replies either. Here are some error samples:

sddm-greeter PID: 493 Signal: Segmentation fault (11)

and:

We are sorry, sddm-greeter closed unexpectedly.

Details:

executable: sddm-greeter PID: 937 Signal: Segmentation fault (11) Tie: 06/25/15 19:28:25.

My previous thread is here:
https://www.kubuntuforums.net/showth...d-unexpectedly

solutions offered by Google search are not working.

[PJJ]

By the way, this issue has somehow something to do with Plasma.
And 'micro-code'. there is a fix for this problem for another Linux flavor.
They fixed it by updating micro-code.

[vinnywright]

never had this problem ,,,,but,,,,,, you can try a "ctrl+alt+F6" at the login screen to get a TTY and login their then do a "sudo apt-get update && sudo apt-get dist-upgrade" to make sure you are all up to date package wise .

is this crash happening after trying to login or as soon as you get to the login screen ?

micro-code is usualy for possessors like

[FONT=monospace]vinny@vinny-Bonobo-Extreme:~$ apt search microcode  [/FONT][FONT=monospace]Sorting... Done
Full Text Search... Done
[COLOR=#18B218]amd64-microcode[/COLOR]/vivid 2.20141028.1 amd64
  Processor microcode firmware for AMD CPUs

[COLOR=#18B218]intel-microcode[/COLOR]/vivid,now 3.20150121.1 amd64 [installed]
  Processor microcode firmware for Intel CPUs

[/FONT]

have a look at /var/log/sddm.log and see if you can gleen anything from it ,,,,,,look for lines that start with (EE) ,,,,,,,,,you WILL see a lot of lines that start with (WW) mostly can be ignored .

you say in you other thread

By the way, 12.04 starts up with the identical error.

but that is impossible because 12.04 dose not use "sddm" !

what is the hardware you are running on ,,,,,,,,,,,,probably of most interest would be the graphics chip ,,,,,,but do give it all.

VINNY

[PJJ]

Oh, it is indeed here.
Well, it looks like I am as usual answering my own question. Not sure yet. So I wait with the bragging till I can confirm success.

This is a common issue with 15.04. I am not the only one suffering from it. So, someone in this excellent forum should have known about it.

According to my research there are several fixes. Fglx (?) and or sddm update. Neither seems to fix the problem permanently.

The workaround to start sddm is:
alt+F2 at sddm crash
login
systemctl start sddm

Or download a version compiled after March 2015. Shouldn't the official version contained in kubuntu repositories be up to date?

Next:
sudo apt-get distupgrade

( I don't think it will work).

Finally, the ultimate insult:

Switch to Ubuntu.
It is supposed to work just fine.
No darn conflict between sddm and kde or such.

Shouldn't Kubuntu developers take care of a conflict built into a OS?

I have not tested either one of the suggested fixes. But I will do so shortly.
And crow about it if it works.

By the way, updating micro-code did not work. I tried that.
I did however not use the official Kubuntu micro-code file for my processor.

[vinnywright]

did we miss my post?

VINNY

[oshunluvr]

did we miss my post?

VINNY

lol +1

[PJJ]

did we miss my post?

VINNY

No, I did not. But I posted my post BEFORE your post.

Thank you for the detailed reply. I will give each and every suggestion a try - as soon as I have reinstalled 15.04. I removed it because it was an update from 14.10. Now I will make a clean installation from USB drive. But need to work out first how to do that. My antedeluvian Toshiba does not have that option. Struggling with PLOP to make it happen.


The "12.04' reference is a typo.

I cannot be the graphics card because I managed several times to get the update 15.04 working. And I used it for hours without any problems.

The error occurs right after startup and before the login screen.

I could log in (alt+F2) and then proceed from there. Once the simple command 'sddm start' got me to the login screen and to a fucntioning 15.04.

[PJJ]

lol +1

See my reply to Vinny.

[vinnywright]

No, I did not. But I posted my post BEFORE your post.

the time stamp on the post sead 6 minutes AFTER ,,,,,,,,,,,,,,,,,

VINNY

[oshunluvr]

the time stamp on the post sead 6 minutes AFTER ,,,,,,,,,,,,,,,,,

VINNY

Well, the time you hit POST doesn't mean you've seen the previous posts yet because the page doesn't update when you're typing...Just sayin'

You kids play nice now

[vinnywright]

Well, the time you hit POST doesn't mean you've seen the previous posts yet because the page doesn't update when you're typing...Just sayin'

You kids play nice now

LOL ,,,but of course you are correct,,,,,,,,,,,,,,,,,,it happens to me a lot .
I will start to answer something and before I can finish typing someone else will have chimed in ,,,,,,,,but it takes me a long time to post with my spelling issues and all

BUT if you ,,,,,, preview post ,,,,,,,you can see if someone else has posted ,,,,,,,,,,if you look for it that is ,,,,,,just sayin' ,,,,,,,,lol

VINNY

[PJJ]

Here is the latest about the ongoing drama.
I had to upgrade from 12.10 to 15.04 because I could not get a USB boot working (with PLOP).

Logged into 15.04 without problems. Stayed on it for hours. Wifi went out. Restarted: Same old problem. Sddm crashed.

Tried: systemctl start sddm.
Resulted in this:

Adding cookie to /var/run/sddm/: 1
/usr/bin/xauth: timeout locking (?) var/run/sddm1
DAEMON messages:
display server startin
running /usr/bin/X :1 -auth/var/run/sddm/:1 - nolisten tcp-background none- noset vt?
display server stopped
running "/usr/share/sddm/scripts/Xstop"

End error messages. Hangs on terminal screen.

I also checked the log as suggested. Lots of messages with three recurring. Unfortunately I cannot give them here because the text is stored in 15.04. Not accessible.

There is nothing wrong with PLasma or anything else. I worked long enough in 15.04 without any issues before the wifi went out.

Will now try the other solution that worked for me once: ctrl + alt+F1:
sudo /etc/init.d/sddm start

will get back.

[vinnywright]

. Unfortunately I cannot give them here because the text is stored in 15.04. Not accessible.

you can access it with a live cd/usb

VINNY