Absolutely.
As I've mentioned, I believe bug #1269405, bug #1269483, bug #1269500
are identical to bug #1303139. Bug #1269669 affects a different
package, so it seems like a related problem.
However, if you have reason to believe otherwise, then I'll leave it to
you to mark them in the way you t
That was not what I said at all. I said that *your* bug was not a
duplicate of this one. Please leave it to the developers to determine
what bugs are or ate not duplicates.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
Considering what you said in bug #1303139, I'm reassigning the
"duplicate" bugs as duplicates of that bug, seeing as I have your
assurance that they're a different bug from this one.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
> That's incorrect. This bug did not involve upgrades from 13.10 to
14.04.
Then let's put it this way: bug #1269405, #1269483, #1269500, #1269669
all mention that the bug is triggered when updating libc6 with dpkg,
which is indeed the case with the bug I experienced two days ago.
--
You received
> It's identical in every way to the bugs that's marked as duplicates of this
> ones:
> - The way it's triggered (telinit)
> - The context in which it's triggeredthe symptoms (upgrade from 13.10 to
> 14.04)
That's incorrect. This bug did not involve upgrades from 13.10 to
14.04.
> - The sympto
As for the crash dumps, I don't have them. There seem to be many
attachments posted in the duplicate bugs, but no crash dumps there
either.
Anyway, don't take my word for it. The problem is solved in my
particular case. If the bug is still there when people start upgrading
for real, then they're g
It's identical in every way to the bugs that's marked as duplicates of this
ones:
- The way it's triggered (telinit)
- The context in which it's triggeredthe symptoms (upgrade from 13.10 to 14.04)
- The symptoms (kernel panic because of trying to kill init)
Which is another way of saying it's the
On Sat, Apr 05, 2014 at 09:04:47PM -, David Oftedal wrote:
> Ah! One thing, though:
> Perhaps an updated version of upstart should actually be released for
> version 13.10? Seeing as this bug might affect a lot of people trying to
> upgrade.
The point is that the bug report you're following
Ah! One thing, though:
Perhaps an updated version of upstart should actually be released for version
13.10?
Seeing as this bug might affect a lot of people trying to upgrade.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
I stand corrected! Now that you mention it, upstart would have been
upgraded at some point during the upgrade, and that could very well have
been after the upgrade of libc which caused the kernel panic.
The upgrade was from the previous version, i.e. something like 13.10,
with updates installed.
On Sat, Apr 05, 2014 at 07:09:56PM -, David Oftedal wrote:
> And when I "apt-get show upstart", I get "Version: 1.12.1-0ubuntu1".
> That means that the bug either wasn't fixed in version 1.11-0ubuntu2, or
> there's been a regression after version 1.11-0ubuntu2.
No, it doesn't mean either of th
And when I "apt-get show upstart", I get "Version: 1.12.1-0ubuntu1".
That means that the bug either wasn't fixed in version 1.11-0ubuntu2, or
there's been a regression after version 1.11-0ubuntu2.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
This still happens on my system when trying to upgrade libc6 during the upgrade
to 10.04.
Adding a fake telinit binary to the path was necessary to work around it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
** 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/1269731
Title:
init crashed with SIGSEGV
To manage notifications about this bug go
This bug was fixed in the package upstart - 1.11-0ubuntu2
---
upstart (1.11-0ubuntu2) trusty; urgency=low
[ Steve Langasek ]
* Merge Debian packaging changes from 1.10-2.
[ James Hunt ]
* debian/manpages/upstart-events.7: Remove Job States and Job Lifecycle
sections since
This bug is fixed in upstart 1.11-0ubuntu2 which will be pushed out once
the alpha 2 freeze is over (Thurday).
If you are still affected by this problem (in other words you have not
managed to upgrade to alsa-utils 1.0.27.2-1ubuntu2), you will need to do
*one* of the following:
1) Disable upstart
** Changed in: upstart (Ubuntu)
Status: In Progress => Fix Committed
** Also affects: upstart
Importance: Undecided
Status: New
** Changed in: upstart
Assignee: (unassigned) => James Hunt (jamesodhunt)
** Changed in: upstart
Status: New => Fix Committed
** Changed i
** Branch linked: lp:ubuntu/upstart
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1269731
Title:
init crashed with SIGSEGV
To manage notifications about this bug go to:
https://bugs.launchpad.net/u
** Changed in: upstart (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1269731
Title:
init crashed with SIGSEGV
To manage notifications about this bug
For me, the freeze and this issue was fixed with installing the new
alsa-utils (1.0.27.2-1ubuntu2).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1269731
Title:
init crashed with SIGSEGV
To manage
@TJ - thanks for your analysis, which mirrors our findings. We now have a fix
to Upstart and new tests to ensure this problem stays fixed.
@Luke - thanks too for fixing alsa-utils! :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
** Branch linked: lp:~jamesodhunt/upstart/bug-1269731
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1269731
Title:
init crashed with SIGSEGV
To manage notifications about this bug go to:
https://bu
** Branch linked: lp:ubuntu/alsa-utils
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1269731
Title:
init crashed with SIGSEGV
To manage notifications about this bug go to:
https://bugs.launchpad.ne
This bug was fixed in the package alsa-utils - 1.0.27.2-1ubuntu2
---
alsa-utils (1.0.27.2-1ubuntu2) trusty; urgency=medium
* Forgot to add an env declaration for an environment variable to the
upstart files. (LP: #1269731)
* debian/patches/work_around_ncurses_weirdness.patch:
** Branch linked: lp:ubuntu/trusty-proposed/alsa-utils
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1269731
Title:
init crashed with SIGSEGV
To manage notifications about this bug go to:
https://b
Sorry, I was replying by emaill, and wasn't aware that this was a larger
bug at the time.
** Changed in: alsa-utils (Ubuntu)
Assignee: (unassigned) => Luke Yelavich (themuso)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
My computer inits perfect. My problem is when I try install the new version:
libc6_2.18-0ubuntu5_i386.deb
It generates a kernel panic in the part of "configuration" of the
package.
I report this bug as #1269669
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
This is my KP.
** Attachment added: "kernel panic"
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1269731/+attachment/3950498/+files/SDC14819_recorte.JPG
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
What did you do to reproduce this segfault?
Secondly, the original syntax used with the test command is perfectly
valid in POSIX shell. Its even present in some of the system's important
init scripts. I even just tested this in a script myself.
--
You received this bug notification because you a
** Branch linked: lp:~tj/ubuntu/trusty/alsa-utils/lp1269731
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1269731
Title:
init crashed with SIGSEGV
To manage notifications about this bug go to:
http
** Changed in: alsa-utils (Ubuntu)
Status: In Progress => Triaged
** Changed in: alsa-utils (Ubuntu)
Assignee: TJ (tj) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1269731
Attaching a tar.gz archive that can be extracted to /etc/init/ which
replaces the faulty alsa-utils upstart conf files:
$ tar -tf lp1269731-upstart-alsa-utls.tar.gz
etc/
etc/init/
etc/init/alsa-state.conf
etc/init/alsa-restore.conf
etc/init/alsa-store.conf
To install, download the attachment and
The three alsa config files incorrectly use shell constructions for
testing variables:
WRONG:
if ! test -d $ALSACTLHOME ; then
CORRECT:
if [ ! -d $ALSACTLHOME ]; then
** Also affects: alsa-utils (Ubuntu)
Importance: Undecided
Status: New
** Changed in: alsa-utils (Ubuntu)
I'm in the process of rustling up a patch for alsa-utils, but this
highlights that upstart really needs guard conditions for file->job ==
NULL before trying to dereference it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
Michael's "/etc/init/" showed 4 upstart conf files updated recently;
three on the 14th when this issue began being reported:
$ ls -latr
...
-rw-r--r-- 1 tj tj 480 Jan 9 11:34 nvidia-persistenced.conf
-rw-r--r-- 1 tj tj 483 Jan 14 04:28 alsa-store.conf
-rw-r--r-- 1 tj tj 609 Jan 14 04:28 als
Michael attached the conf files are my request based on my analysis of
the SEGFAULT trace results:
Segfault happened at: 0x7f1191eb98d9: mov 0x20(%rax),%rsi
## Registers.txt shows:
rax0x0 0
rbx0x7f1192f18ed0 139713456475856
rcx0xe 14
rdx
Here is all the initscripts from my system, as requested by TJ in
#ubuntu+1.
** Attachment added: "init.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1269731/+attachment/3950405/+files/init.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Hi Harry - thanks for testing this. The results you are seeing are very
confusing since the changes between 2.18-0ubuntu4 and 2.18-0ubuntu5 are
nominally only relevant for arm and powerpc systems. What could be
different is the version of gcc used to build each of the eglibc and
upstart versions si
I can confirm I have upstart (1.11-0ubuntu1) installed.
And yes eglibc (2.18-0ubuntu5) does result in crash, while v. 2.18-0ubuntu4
does not.
However, this crash happens in my setup, which has Nvidia graphics card (GTX
285) and proprieatary drivers (331) installed.
But, my other installation wit
Here it is - bad quality, but readable
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1269405/comments/29
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1269731
Title:
init crashed with SIGSE
I took a picture of my output too, though it doesn't look any different
from the one without --debug.
** Attachment added: "IMG_0310.JPG"
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1269731/+attachment/3950149/+files/IMG_0310.JPG
--
You received this bug notification because you a
If someone would be prepared to boot their system and force a crash with
Upstart running in debug mode that would be very helpful:
- Temporarily modify grub config in grub menu to:
- remove "quiet"
- remove "splash"
- add "--debug"
- Boot system
- ctrl-alt-f1 and login
- sudo telinit u
I can't speak for him, but I can say that I have tried 2.18-0ubuntu5 and
2.18-0ubuntu2 and I get a KP with both of them with I run "sudo telinit
u".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/126973
Hi Harry - please can you confirm that you are running upstart version
1.11-0ubuntu1 and that running 'sudo telinit u' with:
- eglibc version 2.18-0ubuntu4 does not result in a crash.
- eglibc version 2.18-0ubuntu5 *does* result in a crash.
Thanks very much!
--
You received this bug notificatio
This system freeze (kernel panic) occurs every time the two newest versions of
eglibc (2.18-0ubuntu5 and 2.18-0ubuntu6) are installed, either with synaptic
(GUI) or directly from terminal or from console (tty1).
Downgrading to the eglibc version 2.18-0ubuntu4 does not cause the system
freeze.
-
I have recovered my setup with live-USB and chrooting.
Then with the command:
sudo dpkg --configure a
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1269731
Title:
init crashed with SIGSEGV
To manag
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: upstart (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/1269731
Title:
in
Hi Kai - thank you for reporting this bug. Please see below for simple
instructions on how to work around the issue whilst we investigate it:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1269405/comments/30
** Changed in: upstart (Ubuntu)
Importance: Medium => Critical
** Changed i
related to Bug #1269669
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1269731
Title:
init crashed with SIGSEGV
To manage notifications about this
49 matches
Mail list logo
