Same here, kubuntu 14.04 64bits on a Dell Precision 390 with nVidia
Quadro. No wireless cards.
Tried with nouveau nvidia driver and the 313 proprietary driver.
Had BIOS version 2.4.0, upgraded to 2.6.0 (thought I had bricked the
mobo in the process, as kubuntu did not shutdown as part of the bios
The Nilolay's bug was related to bcmwl-kernel-source package, mine's too
but we both had a stopping shutting down with the message "mount:/ is
busy" on a laptop HP presario
First I removed network-manager 'cause of the message "dont get
"www.networkmanager1" while sutting down. It didn't change
i have discovered that my problems doen't releate to this bug, my bug is
releated to bcmwl-kernel-source package
** Tags removed: amd64 trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1181789
Ti
try boot from live flash xubuntu 14.04 trusty beta2 64bit
on AMD Phenom desktop computer
works fine, after will now halt appears message (too fast for reading) and
computer powers off
** Tags added: amd64
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
afecting this
xubuntu 14.04 trusty beta2 64bit
Dell D430 laptop
13.10 works fine
get error mount: / is busy' during shutdown or reboot
and hangs after will how halt or will now reboot
passing reboot=force acpi=force to kernel will not help me at all
** Tags added: trusty
--
You received this bu
Landing this fix in raring was blocked by bug #1199778, which we ran out
of time to resolve before the 13.10 release. My work-in-progress branch
is available at lp:~vorlon/ubuntu/raring/upstart/lp.1199778 in case
anyone else wants to pick this up for 13.04. Otherwise, this bug is
'wontfix'.
** C
I committed the fix to the raring SRU branch so it'll be included in the
next SRU.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1181789
Title:
second call of 'initctl start' leads to fork instead o
** Changed in: upstart
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1181789
Title:
second call of 'initctl start' leads to fork instead of exec ('mount:
I have built upstart_1.9.1-0ubuntu3 for Ubuntu 13.04 Raring.
I do not see the bug with ureadahead anymore.
However once I have seen busy / on shutdown
due to modem-manager and its file in /var/log/upstart
opened for writing.
There are a couple of minor issues with sources
in saucy and their backpr
upstart (1.9-0ubuntu1) saucy; urgency=low
[ Dmitrijs Ledkovs ]
* Use dh_auto_build to run the testsuite, as dh_auto_test stopped
finding autotools test suite.
* Correct typo in upstart postinst (LP: #1195955)
[ James Hunt ]
* New upstream release.
* init/tests/test_conf.c: Remove
** Also affects: upstart
Importance: Undecided
Status: New
** Changed in: upstart
Status: New => Triaged
** Changed in: upstart
Importance: Undecided => Critical
** Changed in: upstart
Status: Triaged => Fix Committed
--
You received this bug notification because you
Fixed in lp:upstart and cherry-picked for the next ubuntu:upstart upload
to saucy, will then cherry-pick back to raring once we're done with the
current SRU.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
** Branch linked: lp:upstart
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1181789
Title:
second call of 'initctl start' leads to fork instead of exec ('mount:
/ is busy' during shutdown)
To mana
** Changed in: upstart (Ubuntu)
Importance: Undecided => Critical
** Changed in: upstart (Ubuntu)
Assignee: (unassigned) => Stéphane Graber (stgraber)
** Also affects: upstart (Ubuntu Raring)
Importance: Undecided
Status: New
** Also affects: upstart (Ubuntu Saucy)
Importanc
The attachment "Don't set proc->script on implicit shell use" seems to
be a patch. If it isn't, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are a member of the
~ubuntu-reviewers, unsubscribe the team.
[This is an automated message performed by a Launchpa
Removing the assignment of proc->script solves this problem for me. If
in future we need to know how the process was started, we should store
that information elsewhere, because implicit and explicit use of the
shell are not exactly equivalent. Patch attached.
This and the patch in bug #1169614 gi
The setting of proc->script was introduced here:
http://bazaar.launchpad.net/~ubuntu-
branches/ubuntu/saucy/upstart/saucy/revision/1182.62.1
At the moment it doesn't seem to be tested anywhere other than in
job_process_run(), so simply reverting the change should fix the
problem, but presumably t
The problem is in init/job_process.c, function job_process_run().
Upstart detects SHELL_CHARS in the exec line, so first time
it launches command with shell and exec wrappings
/bin/sh -e -c exec /bin/sh -c "exit"
and set "script" flag for the job's MAIN_PROCESS.
During the second "initctl start"
** Summary changed:
- upstart fails to track premature exit ('mount: / is busy' during shutdown)
+ second call of 'initctl start' leads to fork instead of exec ('mount: / is
busy' during shutdown)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
19 matches
Mail list logo
