plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()

for me this happens with nvidia proprietary drivers since last 3-4 days

this happens to me from a clean install of beta1. no nvidia component.

Seems i am also affected, upgraded from 9.10 today and was left with a tty-login and no x at all.
After some trying around and finally »apt-get purging nvidia*« could login to x and everything seemed to work well.
Then I only got that notification about plymouth until now. Will see if something else gets in my way.

Firefox 3.6 works, as well as flash and even sound, so i was really surprised (in a positive way).

Good job - folks at canonical, well done compared to my Karmic-Experience.

My home-box:
Intel Core2Duo 1.8 GHz with nvidia graphics, nothing fancy. Pretty standard install.

Now let's see tomorrow if eclipse works without that nasty 'gdk_native_windows-fix' too, and in case it does I will soon be moving my production box from Karmic, yeehaw!

> upgraded from 9.10 today and was left with a tty-login and no x at all.

That sounds like a bug in your X configuration, not in plymouth - even if plymouth fails to start completely, X should start on its own and you should never be dropped to a console login prompt. (There are bugs with the *free* nouveau driver and plymouth when using multiple displays, but that's not the problem you describe.)

Why do you say that you're affected by this bug in particular? If you are notified of plymouth crashes, please follow the steps to file a bug report; if you think that it's a duplicate of another bug, you can provide that information to us in your report for verification. This bug report that you've followed up to is against an older version of plymouth, and if not actually fixed is probably not going to be reproducible / fixable with the information available, so a fresh bug report with a fresh backtrace is much preferred.

Got this exact crash and message - fully updated as of 29th March - 12pm - ish NZDT

@Steve Langasek

> That sounds like a bug in your X configuration, not in plymouth [...]

I had nvidia proprietary drivers removed/purged first and got the notification in the notification-area afterwards after having logged in to X. Just did not realize that my old nvidia-drivers might have messed up my X-configuration somehow, before I upgraded from karmic. But at the point when I got the notification, I already had fully updated(somithing around 11pm CET 28th of March).

> There are bugs with the *free* nouveau driver and plymouth when using multiple displays [...]

Exactly, but I am not using a multiple-display configuration nor am I having more than one display at the moment. ;-)

> Why do you say that you're affected by this bug in particular?

Because the notification-message said exactly the text that I have given below, and that is exactly what is shown in the issue-description, that's why I reported it here:

plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()

Just ignore the rest of my offtopic writing in the first post (even though I am still pretty impressed with what we have for a beta 1).

If further inverstigation is needed I could try to help and provide some information or log-output as soon as I get to back to my homebox.

Got the bug today after installing 10.04 and running system updates.

Also get an error on the splash screen logging out where it say "Could not write to pipe"

Plymouthd crash upon cold boot - apport crash report should be attached.

Apport has not attached any thing - will supply any other info if requested. Where did apport go?

Please re-test with plymouth 0.8.1-3.

I haven't had this error in recent days.

https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/551952
The linked error happened after opening Gwibber, then this error occurred shortly after.

I got this plymouthd crash at boot-up in Ubuntu Netbook daily build April 2, 2010 and fully updated as of now (12:30pm April 3, 2010 EDT). Lenovo G530 with Intel graphics and components. I'll be looking for an update with hopes that it fixes this crash.

Later...

This crash was reported with an older version of plymouth and does not have a full backtrace attached to it, so if it *does* still occur, there's not enough information here to practically track it down. If you are still seeing *this* crash at boot-up, you should be getting an apport notification; you need to submit a new bug using the information apport provides about the crash.

Don't change this bug status without explanation.

Did an 'apt-get dist-upgrade' the day before yesterday and it seems I am no longer affected - the notification is gone, but now i have several gnome-menue-items under settings twice.

Seems to be fixed and works for me now.

I am now getting it & I am seeing this atleast for the second time.

I saw this yesterday and tried reporting the bug today. However, seeing this bug I said «it is this bug».

Version: 0.8.1-4ubuntu1

This is the version.

System reported bug, title of bug matched in list, ended up here. Sorry for useless comment but maybe the extra info (attached) will help somewhere :-)

i got the bug with dist-upgrade done 24 hours ago.... so the fix is not working....

Clean install of xubuntu 12.04 beta 1 on Lenovo S10e Netbook. Crash occured at the end of update post install.

Also affecting me with clean install of Ubuntu 12.04 beta 1.

same on acer aspire one, Ubuntu 12.04 B1

Same on HP Pavilion dv2250br, on Ubuntu 12.04 Desktop i386 Beta 02!
Crash occured when I was listening to music while I was posting something in Facebook Time Line.

ITX ION-P-E, Ubuntu 12.04 B2

Also affecting me with precise beta 2