Closing assumed fixed.
** Changed in: lightdm (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1066883
Title:
[Macmini 5,1] Fatal serv
saucy has seen the end of its life and is no longer receiving any
updates. Marking the saucy task for this ticket as "Won't Fix".
** Changed in: lightdm (Ubuntu Saucy)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Desktop
Packages, which
raring has seen the end of its life and is no longer receiving any
updates. Marking the raring task for this ticket as "Won't Fix".
** Changed in: lightdm (Ubuntu Raring)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Desktop
Packages, whi
quantal has seen the end of its life and is no longer receiving any
updates. Marking the quantal task for this ticket as "Won't Fix".
** Changed in: lightdm (Ubuntu Quantal)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Desktop
Packages,
Parameswaran Sivatharman, as per http://support.apple.com/kb/HT1237 an update
is available for your BIOS (MM51.0077.B10). If you update to this following
https://help.ubuntu.com/community/BiosUpdate , does it change anything? If it
doesn't, could you please both specify what happened, and just p
** Tags added: bios-outdated-b10
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1066883
Title:
[Macmini 5,1] Fatal server error: Can not run in framebuffer mode on
reboot
Status in
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: lightdm (Ubuntu Quantal)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/b
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu Raring)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: lightdm (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1066
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: lightdm (Ubuntu Raring)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bu
** Tags added: needs-upstream-testing regression-potential
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1066883
Title:
[Macmini 5,1] Fatal server error: Can not run in framebuffer m
** Also affects: linux (Ubuntu Raring)
Importance: Undecided
Status: New
** Also affects: lightdm (Ubuntu Raring)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Saucy)
Importance: High
Assignee: Andy Whitcroft (apw)
Status: Confirmed
** Also a
dmesg shows the below output. plymouth is clearly being stopped by
lightdm (not by /etc/init/plymouth-stop.conf), so we're not hitting a
race in the plymouth jobs. But after stopping plymouth, lightdm hits
the problem with the X server and exits.
I think this is clearly a problem with either the
Failure was observed in the second boot
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1066883
Title:
[Macmini 5,1] Fatal server error: Can not run in framebuffer mode on
reboot
Statu
** Attachment added: "dmesg_bad_second_boot"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1066883/+attachment/3401556/+files/dmesg_bad_second_boot
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.lau
** Attachment added: "dmesg_good_first_boot"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1066883/+attachment/3401554/+files/dmesg_good_first_boot
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.lau
@psivaa -- ok cool so that confirms it is most likely an initialisation
race. Could we get dmesg from a good boot (ie without the pack) and the
next bad boot (with the pack), and attach them to this bug please. Do
make sure they are clearly labelled :)
Thanks.
--
You received this bug notifica
** Changed in: xorg (Ubuntu Quantal)
Assignee: (unassigned) => Canonical X.org (canonical-x)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1066883
Title:
[Macmini 5,1] Fatal server
@apw
Rebooted many times (more than 20) after updating the kernel to the latest on a
known (20121001) good image, it worked ok, no failures could be observed.
Removing /var/lib/ureadahead/pack from the known bad image seem to solve
the issue.
When it was made sure the file is removed before the
@psivaa -- when updating the kernel there on 20121001 can you confirm
that multiple boots were good. Also on the latest image (known bad)
does it work for the next boot if you remove /var/lib/ureadahead/pack
before reboot?
--
You received this bug notification because you are a member of Desktop
So here is the list of test runs,
20120724.2 -> worked
20120918.1->worked
20121001 -> worked
20121011 -> FAILED
The kernel was updated to the latest on top of a working 20121001 and it
still worked
--
You received this bug notification because you are a member of Desktop
Packages, which is subs
When tried with 20120724.2 amd+mac quantal desktop, this issue was not
reproducible (with ~10 reboots). Hence looking at bug 1066228 it appears
be a regression that occurred between alpha3 and beta 1.
--
You received this bug notification because you are a member of Desktop
Packages, which is sub
A fresh install with quantal desktop - amd+mac 20121011 also has the
same issue. First boot after the installation went well but the
subsequent ones do not boot in standard graphics mode.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xo
** Summary changed:
- Fatal server error: Can not run in framebuffer mode on reboot
+ [Macmini 5,1] Fatal server error: Can not run in framebuffer mode on reboot
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bug
24 matches
Mail list logo
