*** This bug is a duplicate of bug 1269731 ***
https://bugs.launchpad.net/bugs/1269731
Any news on this one? I have the same issue, see question
https://answers.launchpad.net/ubuntu/+question/247836
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 1303139 ***
https://bugs.launchpad.net/bugs/1303139
** This bug is no longer a duplicate of bug 1269731
init crashed with SIGSEGV
** This bug has been marked a duplicate of bug 1303139
Kernel panic when dpkg attempts to install libc6
--
You received
*** This bug is a duplicate of bug 1269731 ***
https://bugs.launchpad.net/bugs/1269731
** This bug is no longer a duplicate of bug 1303139
Kernel panic when dpkg attempts to install libc6
** This bug has been marked a duplicate of bug 1269731
init crashed with SIGSEGV
--
You received
*** This bug is a duplicate of bug 1303139 ***
https://bugs.launchpad.net/bugs/1303139
** This bug is no longer a duplicate of bug 1269731
init crashed with SIGSEGV
** This bug has been marked a duplicate of bug 1303139
Kernel panic when dpkg attempts to install libc6
--
You received
*** This bug is a duplicate of bug 1269731 ***
https://bugs.launchpad.net/bugs/1269731
** This bug is no longer a duplicate of bug 1303139
Kernel panic when dpkg attempts to install libc6
** This bug has been marked a duplicate of bug 1269731
init crashed with SIGSEGV
--
You received
*** This bug is a duplicate of bug 1269731 ***
https://bugs.launchpad.net/bugs/1269731
It isn't fixed; this is just a workaround. Programs (especially ones as
vital to system operation as upstart) should never crash when fed
malformed data.
--
You received this bug notification because you
After using the recovery-option in grub you mentioned above nothing
works after reboot.
The gnome-session/GDM is not starting anymore and telinit u still
crashes the machine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[UPDATE]
Solved my gnome-shell-issue from above by creating a symbolic link for
the libwaylande-egl.so.1 :
# ln -s /usr/lib/x86_64-linux-gnu/mesa-egl/libwayland-egl.so.1 /usr/
But telinit u still crashes my machine.
--
You received this bug notification because you are a member of Ubuntu
[UPDATE #2]
Solved my gnome-shell-issue from above by creating a symbolic link for
the libwayland-egl.so.1 :
# ln -s /usr/lib/x86_64-linux-gnu/mesa-egl/libwayland-egl.so.1
/usr/lib/
But telinit u still crashes my machine.
- had some typo in the above article (sorry) because of using twm for
[UPDATE]
Solved my gnome-shell-issue from above by creating a symbolic link for
the libwayland-egl.so.1 :
# ln -s /usr/lib/x86_64-linux-gnu/mesa-egl/libwayland
/usr/lib
But telinit u still crashes the machine!
BTW: The interface of this forum is realy bad.
--
You received this bug
[UPDATE]
Solved my gnome-shell-issue from above by creating a symbolic link for
the libwayland-egl.so.1 :
# ln -s /usr/lib/x86_64-linux-gnu/mesa-egl/libwayland
But telinit u still crashes the machine!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
[UPDATE]
Solved my gnome-shell-issue from above by creating a symbolic link for
the libwayland-egl.so.1 :
# sudo ln -s /usr/lib/x86_64-linux-gnu/mesa-egl/libwayland* /usr/lib
But telinit u still crashes the machine!
BTW: The interface of this forum is realy bad and is IMO unuseable -
it's
get_state.sh is causing a kernel panic here too
** Attachment added: Pic_0115_014.jpg
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1269405/+attachment/3949980/+files/Pic_0115_014.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
*** This bug is a duplicate of bug 1269731 ***
https://bugs.launchpad.net/bugs/1269731
Whilst we investigate this issue, you can still run apt-get / dpkg
without triggering the bug if you do the following:
$ sudo su -
# mkdir /root/bin
# ln -s /bin/true /root/bin/telinit
# chmod 755
*** This bug is a duplicate of bug 1269731 ***
https://bugs.launchpad.net/bugs/1269731
This problem is the same as bug 1269731.
** This bug has been marked a duplicate of bug 1269731
init crashed with SIGSEGV
--
You received this bug notification because you are a member of Ubuntu
Bugs,
*** This bug is a duplicate of bug 1269731 ***
https://bugs.launchpad.net/bugs/1269731
Thank you, James, for the workaround!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1269405
Title:
Kernel
*** This bug is a duplicate of bug 1269731 ***
https://bugs.launchpad.net/bugs/1269731
Fixed -
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1269731/comments/29
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Summary changed:
- Kernel Panic running 'sudo dpkg --configure -a'
+ Kernel Panic when 'telinit u', or (re)installing packages
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1269405
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: eglibc (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/1269405
Title:
Not a glibc issue, and confirmed locally that a glibc upgrade works fine
for me. So, likely a local issue with upstart configs on the affected
machines.
** Changed in: eglibc (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
I cannot recreate this issue on either 32-bit or 64-bit fully-updated
trusty systems. What would be useful is to know if it also affects the
Session Init (upstart running as the user) since that would allow debug
to be collected without the kernel panicking.
To find out, please can those affected
Also, could those affected please:
- attach output produced by sudo initctl list.
- comment if they have added any of their own jobs or modified existing jobs.
- comment if they have any chroots on their system.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Oops, here's the file.
** Attachment added: initctllist.txt
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1269405/+attachment/3949585/+files/initctllist.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Here is the output of get_state.sh when running as a non-root user.
** Attachment added: upstart.state
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1269405/+attachment/3949579/+files/upstart.state
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
There was no crash when running get_state.sh as non-root.
I attached the output of initctl list.
One of my systems (the one I am posting all the output from) has no
chroots, no modified jobs, and one custom job that runs once during
startup. The other system has two chroots, no modified jobs,
Thanks Michael. Did 'start re-exec' work (appear to do nothing) or fail
(crash your desktop session)?
The following isn't a conclusive test, but it will allow us to rule out
whether somehow a system job in unrepresentable when serialised. To
check this, we can copy the system jobs into the
Also, it would be extremely useful to know if this issue is repeatable
every time. If so, please:
1) $ sudo initctl list initctl.list.
2) attach that file to this bug before running 'sudo telinit u' / 'sudo
get_state.sh' to demonstrate the crash is repeatable.
Thanks!
--
You received this
Immediately after I run the get_state.sh command there, KDE krashes and
dumps me back at the KDM login screen. The only output in the file is
the error message from json_pp indicating that the input piped to it
isn't valid JSON.
Yes, the issue is repeatable every time.
--
You received this bug
Hi, this bug also occurs to me.
I also tried the instructions from #15, and issuing get_state.sh causes Unity
to close, bailing out to the login screen.
The resulting upstart.state file is empty.
The output of initctl list is attached.
** Attachment added: initctl.list
Here are some pictures of the kernel panic that happens after dpkg tries
to configure libc6:amd64.
** Attachment added: Picture of kernel panic
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1269405/+attachment/3949657/+files/IMG_20140115_112156800_HDR.jpg
--
You received this bug
Here is the output of initctl list.
** Attachment added: Output of initctl.list
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1269405/+attachment/3949667/+files/initctl.list
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: upstart (Ubuntu)
Importance: Undecided = Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1269405
Title:
Kernel Panic when 'telinit u', or (re)installing packages
To manage
Can we get a workaround or a fix soon, please? I need to be able to use
my laptop.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1269405
Title:
Kernel Panic when 'telinit u', or (re)installing
Workaround:
Choose the recovery mode in GRUB (under Advanced Options for Ubuntu) and
choose 'Fix broken Packages'.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1269405
Title:
Kernel Panic when
34 matches
Mail list logo
