still no solution ;-(
--
mountall: could not connect to Plymouth
https://bugs.launchpad.net/bugs/499772
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/ma
same in here, stops booting with the note Mount all: cant connect to
playmouth
so i do have a login line; if i put in my loginname, password, i can do
a "startx"
gnome ist starting fine for 2 mins, after this time it resets me to the
gdm login window.
BUT only if i use 2.6.32-25 kernel, all is f
Same problem here. I can not start the computer anymore. How could I
fix this problem if I cant boot my computer even in text mode?
--
mountall: could not connect to Plymouth
https://bugs.launchpad.net/bugs/499772
You received this bug notification because you are a member of Ubuntu
Bugs, which
Same here!!! Normal boot, but no splash.
--
mountall: could not connect to Plymouth
https://bugs.launchpad.net/bugs/499772
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://
same for me... no noticeable effect, i just get the 'mountall: could not
connect to plymouth' message, and then the computer boots normally...
--
mountall: could not connect to Plymouth
https://bugs.launchpad.net/bugs/499772
You received this bug notification because you are a member of Ubuntu
Bu
I get this message about mountall not connecting to plymouth as well but
it doesnt affect my usage at all. I can still login and run the computer
no problems.
--
mountall: could not connect to Plymouth
https://bugs.launchpad.net/bugs/499772
You received this bug notification because you are a mem
Same is the problem with me too... I am using Lucid 2.6.32-7-generic on x86
machine
The screen output is as follows:
mounting none on /dev no such device fail
mountall could not connect to plymouth
it has happened since last update although 2.6.32.10 is installed but that is
also not being displ
** Tags added: iso-testing
--
mountall: could not connect to Plymouth
https://bugs.launchpad.net/bugs/499772
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.c
hello,
i have the same problem on my asus eeepc 901 - fr, ubuntu lucid -fr since the
last update. i am a newby on ubuntu, tell how i can help you, and how can give
you the log file.
--
mountall: could not connect to Plymouth
https://bugs.launchpad.net/bugs/499772
You received this bug notificat
Sorry, wrong reference, should be bug #502494.
--
mountall: could not connect to Plymouth
https://bugs.launchpad.net/bugs/499772
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
ht
@Christopher:
Please note that this bug has been deemed Invalid, so all your efforts are
probably never going to get noticed by the right people. I suggest you take a
look at bug #502492, which looks similar but more to the point.
--
mountall: could not connect to Plymouth
https://bugs.launchpa
Attaching log file.
** Attachment added: "failsafeX-backup-100103114335.tar"
http://launchpadlibrarian.net/37384297/failsafeX-backup-100103114335.tar
--
mountall: could not connect to Plymouth
https://bugs.launchpad.net/bugs/499772
You received this bug notification because you are a member o
I can confirm the message 'mountall: could not connect to Plymouth' is
the first thing displayed on boot in Lucid. Most of the time it boots
but I had trouble moments ago when the boot just stopped. Ctrl+Alt+F2
brought me to a login screen, but nothing appeared when I typed my
username and I had to
This is not a plymouth bug!
Plymouth is not needed by mountall and with or without plymouth I get the same
error message:
mountall can not connect to plymouth.
This is a libplymouth2 or a mountall issue
In my case it broke the system... I can not start the computer anymore!
--
mountall: could n
Sorry for being unclear but I don't know what happened either. Something
must be wrong, or that message should not have been displayed. If it is
normal not to be able to connect to Plymouth, please remove the message
so it doesn't confuse anyone. As this behavior is new, I thought it was
interestin
Please read http://www.chiark.greenend.org.uk/~sgtatham/bugs.html.
Your report is completely unclear to what has happened on your computer;
I'm left with the distinct impression that your system booted just fine.
In particular I have no idea what the "usual recovery options" are -
since we comple
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/37121616/Dependencies.txt
** Attachment added: "ProcEnviron.txt"
http://launchpadlibrarian.net/37121618/ProcEnviron.txt
--
mountall: could not connect to Plymouth
https://bugs.launchpad.net/bugs/499772
You received this
17 matches
Mail list logo
