One more thing. This specific laptop on which it is happening, I do not
really need for much. I can log in to terminal via Ctrl-Alt-F1 and run
scripts, or otherwise do anything.
I am not in the least stressed out by what is happening, and would love
to help tracking down this bug.
i
--
gdm/x fa
I have this on Kubuntu also. I can't see the bootsplash on startup, only on
shutdown.
However, KDM starts fine and I'm able to boot.
Currently, the problem is just aesthetic.
--
gdm/x fails to start with error "Broken Pipe" at boot in Xubuntu
https://bugs.launchpad.net/bugs/519641
You received t
I've the same problem
--
gdm/x fails to start with error "Broken Pipe" at boot in Xubuntu
https://bugs.launchpad.net/bugs/519641
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
The comment above is wrong. The problem exists and is a real bug (search
for jockey and LIBGL_DRIVERS_PATH) but is unrelated.
--
gdm/x fails to start with error "Broken Pipe" at boot in Xubuntu
https://bugs.launchpad.net/bugs/519641
You received this bug notification because you are a member of U
I would counsel you to echo $LIBGL_DRIVERS_PATH
And see if it set to the
LIBGL_DRIVERS_PATH=/usr/lib/fglrx/dri
while those drivers are uninstalled. This has been happening to me for no
reason i can discern (after deactivating the drivers in jockey, and even
uninstalling fglrx and fglrx-modalias
Its "fixed" in that the current version of Plymouth will dump you to a
text login screen, from which you can switch to a real desktop if you
know the function keystroke for it. The fix for that is milestoned for
beta 2.
--
gdm/x fails to start with error "Broken Pipe" at boot in Xubuntu
https://b
I've got this problem trying to boot using Ubuntu Alpha 3 live cd. If
it's fixed I am waiting for Beta 1 to try.
--
gdm/x fails to start with error "Broken Pipe" at boot in Xubuntu
https://bugs.launchpad.net/bugs/519641
You received this bug notification because you are a member of Ubuntu
Bugs, w
This bug was fixed in the package plymouth - 0.8.0~-13
---
plymouth (0.8.0~-13) lucid; urgency=low
[ Steve Langasek ]
* Don't attach /proc/cmdline to apport reports, this is already in the
standard info that gets collected...
[ Alberto Milone ]
* ubuntu_logo theme:
-
** Changed in: plymouth (Ubuntu)
Milestone: None => ubuntu-10.04-beta-1
** Changed in: plymouth (Ubuntu)
Assignee: (unassigned) => Scott James Remnant (scott)
--
gdm/x fails to start with error "Broken Pipe" at boot in Xubuntu
https://bugs.launchpad.net/bugs/519641
You received this bug
I have this bug with Ubuntu (not xubuntu)
and this is terrible, waiting for fix
--
gdm/x fails to start with error "Broken Pipe" at boot in Xubuntu
https://bugs.launchpad.net/bugs/519641
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
That the behavior changes across reboots doesn't mean that it's a
ureadahead bug, only that the behavior is racy.
Plymouth is known to have a number of race condition bugs currently.
A fix for these is expected to land in lucid within the next day; please
wait for the next upload and retest then.
Seeing this same behavior at boot with Intel graphics and vanilla Ubuntu
Lucid. Is there a separate bug that is not Xubuntu-specific I should be
following?
--
gdm/x fails to start with error "Broken Pipe" at boot in Xubuntu
https://bugs.launchpad.net/bugs/519641
You received this bug notification
Last few reboots gdm starts and i'm able to select my user and type my
password. But when i press enter, gdm restarts and i have to re-enter my
password.
--
gdm/x fails to start with error "Broken Pipe" at boot in Xubuntu
https://bugs.launchpad.net/bugs/519641
You received this bug notification b
** Also affects: ureadahead (Ubuntu)
Importance: Undecided
Status: New
--
gdm/x fails to start with error "Broken Pipe" at boot in Xubuntu
https://bugs.launchpad.net/bugs/519641
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
-
any fix or workaround to this bug ? its annoying , ideas please
--
gdm/x fails to start with error "Broken Pipe" at boot in Xubuntu
https://bugs.launchpad.net/bugs/519641
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs ma
Yes, I can confirm that at the first boot after the install of a new
kernel, I do see gdm without an error. Starting from the second boot,
the error appears again. So +1 that it is related to ureadahead.
--
gdm/x fails to start with error "Broken Pipe" at boot in Xubuntu
https://bugs.launchpad.ne
and the bootchart of the failed boot (next boot)
** Attachment added: "ubuntu-lucid-20100306-5.png"
http://launchpadlibrarian.net/40360395/ubuntu-lucid-20100306-5.png
--
gdm/x fails to start with error "Broken Pipe" at boot in Xubuntu
https://bugs.launchpad.net/bugs/519641
You received this b
I think the problem has to do with ureadahead. if you install something
that changes the boot process, first boot will succeed. Second boot will
fail. Try installing bootchart and reboot.
i attached the bootchart of the successful boot.
** Attachment added: "ubuntu-lucid-20100306-4.png"
http:/
Maybe I should mention, that I do already see a mouse pointer at this
point, when the error appears and gdm doesn't start.
--
gdm/x fails to start with error "Broken Pipe" at boot in Xubuntu
https://bugs.launchpad.net/bugs/519641
You received this bug notification because you are a member of Ubun
Same problem here on a fresh install of Ubuntu Lucid Alpha 3 (all updates
applied), using an ATI card (ATI Technologies Inc RS482 [Radeon Xpress 200M]
[1002:5975] Subsystem: Dell Device [1028:01f5]).
The error I get is:
init: ureadahead-other main process (721) terminated with status 4
init: ur
Steve,
So my assumption that the problem that occurred on the Xubuntu Live CD
(Casper) was not the same issue that I had? It would have made sense to
me that this would have been either the same or a related bug.
On Sun, 2010-02-14 at 19:38 +, Steve Langasek wrote:
> In particular, this is t
In particular, this is the only report of a "broken pipe" error that
I've seen so far.
--
gdm/x fails to start with error "Broken Pipe" at boot in Xubuntu
https://bugs.launchpad.net/bugs/519641
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
There are bugs that appear on each of ATI, Nvidia, and Intel cards.
There is not yet enough information to conclude that they're the same
bug..
--
gdm/x fails to start with error "Broken Pipe" at boot in Xubuntu
https://bugs.launchpad.net/bugs/519641
You received this bug notification because you
Thanks for reporting this bug and any supporting documentation. Since
this bug has enough information provided for a developer to begin work,
I'm going to mark it as confirmed and let them handle it from here.
Having followed many of the conversations on #ubuntu+1, this bug is not
limited to any p
** Package changed: xserver-xorg-video-intel (Ubuntu) => plymouth
(Ubuntu)
--
gdm/x fails to start with error "Broken Pipe" at boot in Xubuntu
https://bugs.launchpad.net/bugs/519641
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubu
After more talking in #ubuntu+1 it was recommended that I remove
Plymouth and see what happens... So I removed plymouth and sure enough,
the system now correctly boots. I'm not sure what the significance is
and if it is Plymouth's interaction with gdm, Xorg or the intel drivers
that is causing this
I'd love to know what the status of this bug is so I can either prepare
to run some traces, etc for the developers and whatnot or if it's even
going to be assigned.
Please let me know what more I need to supply you guys with.
Thanks,
Matt
--
gdm/x fails to start with error "Broken Pipe" at boo
** Package changed: xorg (Ubuntu) => xserver-xorg-video-intel (Ubuntu)
--
gdm/x fails to start with error "Broken Pipe" at boot in Xubuntu
https://bugs.launchpad.net/bugs/519641
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-
After speaking with crimsun in #ubuntu+1 he politely pointed it that it
could be driver issue.. looking at the binary hints some more, I tend to
think he's right since dkms is not present as well as the listing in
"GLXinfo" being absent. This issue may be more correctly filed under
either the kerne
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/38986622/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/38986623/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/38986624/Dependencies.txt
** A
30 matches
Mail list logo
