@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. -- plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events() https://bugs.launchpad.net/bugs/543484 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
