Just a bit of extra info -- it's possible that this has been mentioned
before.
I am using Acer C710-2834 with Chrome OS installed via s9ryd script.
In my case there are two (2) distinct behaviors.
1. Happens when the Chromebook is Running on Battery power.
The message plymouthd:
I ended up at this bug because I saw the message in the title while running
http://goo.gl/s9ryd per
http://chromeos-cr48.blogspot.com/2013/05/chrubuntu-one-script-to-rule-them-all_31.html
I found a work-around at http://ubuntuforums.org/showthread.php?t=2162179 : use
http://goo.gl/kpzxn
I have the same bug on 12.04 alternate 32bit.
followed by error: unexpectedly disconnected from boot status daemon
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1082742
Title:
plymouthd:
In my case (clean 13.04 on internal drive) the exynos5.conf file is
present but I still get the error.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1082742
Title:
plymouthd: ply-terminal.c: 611
Just for the sake of it, I got this problem and it had nothing to do with
plymouth. It was caused by a 13.04 update which removed /etc/X11/xorg.conf.d
along with exynos5.conf. I just had to do this:
- get into ChromeOS shell (Ctrl-Alt-[←])
- log in as chronos, then sudo su -
- make some
OBS.: I got exynos5.conf file from this script:
https://gist.github.com/vvuk/4986933
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1082742
Title:
plymouthd: ply-terminal.c: 611 ply_terminal_open:
After apt-get remove gdm lightdm, I get by default to the command line, and
there startx crashes the kernel.
From /var/log/syslog, it looks like a problem in exynos_user_fb_create:
Apr 14 10:37:25 nap kernel: [ 12.657138] Unable to handle kernel paging
request at virtual address 0040a000
Apr
I too see this bug and X fails to display with my user account, but I
find it interesting that the Guest account works just fine. I can
browse the web in firefox all day with it. So I thought the issue may
be account related. Any ideas are welcome - I'll keep poking around.
--
You received
I am tired of telling each user how to work around a problem.
Frustratingly, you didn't mention the workaround in this bug, and
Googling found your G+ post which says cd /etc/init; for p in
plymouth*;do echo manual ${p}.override;done which doesn't quite
work.
For those stuck, the answer is
For the edification of the reporters I can confirm this doesn't just
happen on Chromebook but on an Efika MX running kernel 3.7, using the
imx-drm staging driver. Xorg seems to crash a hell of a lot too, but I
can't tell if it's related. Using xserver-xorg-video-modesetting or
-fbdev makes no
Is that with your PPA xorg video driver installed? Can you reproduce
that success without? We should look at the differences between our
configs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1082742
W dniu 26.11.2012 09:40, jaduncan pisze:
Is that with your PPA xorg video driver installed?
Yes
Can you reproduce that success without?
Can try later.
We should look at the differences between our configs.
I hope one day to have two devices for such work. One for all the
hacking and
I hope one day to have two devices for such work. One for all the
hacking and second running only packaged work.
Well, in this case you could always just have two USB sticks/SD cards to
boot off. If your base rootfs is small enough to send or you've got
notes on how you set it up I'll even try
when I remove the plymouth entries entirely from /etc/init (not neat,
I know) I get the same blank screen and lock but without the plymouth
error message. Any ideas on how to check if it's a framebuffer issue?
I can confirm this too, also disabling DRI in xorg.conf doesn't work
either.
--
You
I think this is actually an X hang bug - when I remove the plymouth
entries entirely from /etc/init (not neat, I know) I get the same blank
screen and lock but without the plymouth error message. Any ideas on how
to check if it's a framebuffer issue?
--
You received this bug notification because
On my system (without /etc/init/plymouth*.conf files) I have slim (x
login manager) started just fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1082742
Title:
plymouthd: ply-terminal.c: 611
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: plymouth (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1082742
Title:
17 matches
Mail list logo
