Launchpad has imported 5 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=463728.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2008-09-24T09:43:15+00:00 Hans wrote: Description of problem: When the fsck of a network based blockdevice (nbd/iscsi) fails, the netfs initscript will drop the user to a root shell to repair things and then issue "shutdown -r now" upstart seems to try to continue entering the runlevel it was busy with entering despite the reboot command being given. While at the same time (in parallel??) starting a runlevel switch to the new (reboot) runlevel. Most noticeably here is that upstart spews messages like: -process tty1 died, respawning -process prefdm died, respawning (not the exact text but like that) While its busy shutting down services for the reboot. Reply at: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/66002/comments/11 ------------------------------------------------------------------------ On 2008-09-24T14:01:05+00:00 Bill wrote: Hm, looking at a tty, for example: start on stopped rc2 start on stopped rc3 start on stopped rc4 start on started prefdm stop on runlevel 0 stop on runlevel 1 stop on runlevel 6 So, it may start quickly (on the stop of the runlevel) but then stop again (on the start of runlevel 0/1/6) Reply at: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/66002/comments/12 ------------------------------------------------------------------------ On 2008-11-26T03:12:22+00:00 Bug wrote: This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle. Changing version to '10'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Reply at: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/66002/comments/13 ------------------------------------------------------------------------ On 2009-11-18T08:25:19+00:00 Bug wrote: This message is a reminder that Fedora 10 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 10. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '10'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 10's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 10 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Reply at: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/66002/comments/23 ------------------------------------------------------------------------ On 2009-12-18T06:25:49+00:00 Bug wrote: Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. Reply at: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/66002/comments/24 ** Changed in: upstart (Fedora) Importance: Unknown => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/66002 Title: entering 'reboot' at the rescue console brings up gdm Status in upstart package in Ubuntu: Fix Released Status in upstart package in Fedora: Won't Fix Bug description: Situation: Being dropped to a shell because of a fschck. There I say 'reboot' to reboot the machine. Result is that gdm is started instead of the machine being rebooted. System: Freshly installed edgy from daily 13/10/2006. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/66002/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
