That's very difficult for me to guess, legolas... But the mailing list
thread quoted on http://bugzilla.kernel.org/show_bug.cgi?id=9147 seems
to indicate that modifier keys such as Ctrl and Alt were handled the
same way in 2.4 as all keypresses are in 2.6; that is, they weren't
released until a
Yes, there's no indication on kernel.org that the bug has been fixed
either: On http://bugzilla.kernel.org/show_bug.cgi?id=9147 , the status
is listed as ASSIGNED.
Unless we're actually dealing with several different bugs here, the bug
is therefore probably still there.
--
Keyboard keys get
And by the way, if your computer is affected by kernel.org bug #9147,
try pressing Ctrl-Alt-F1 in X. At least on my system, when the bug
occurs, this resets the keyboard driver somehow and refreshes the
screen, instead of bringing up the console, as one would expect.
--
Keyboard keys get stuck
An old mailing list posting regarding the kernels 2.6.0-test1 and -test4
may hold the answer to the problem:
http://lkml.org/lkml/2003/9/15/210
On Mon, Sep 15, 2003 at 08:55:46PM +, xsdg wrote:
What would happen if the kernel received two keypress events, and then one
key-
release event
Also, the person making the complaint is using the i8042 keyboard
controller and getting the same error messages:
Sep 14 20:42:27 cpp kernel: atkbd.c: Unknown key (set 2, scancode 0xb6, on
isa0060/serio0) pressed.
Sep 14 20:42:27 cpp kernel: i8042 history: 19 a2 99 0f 8f 0f 8f 1c 9c 04 84 36
09
Well, I'm using Iceweasel on Windows Vista now and can't remember
experiencing the bug even once, but on Linux it occurs about once a
day... So if the bug did occur in XP, it seems to have been fixed in
Vista. Either that, or it's directly linked to the Firefox logo and
trademark.
--
Ctrl-key
It may be related to differences in the keypress handling in kernel 2.6,
though. Here's someone reporting a similar bug in 2003:
http://lkml.org/lkml/2003/9/14/148
A person named Andries Brouwer replies with the following:
The answers differ for 2.4 and 2.6. For 2.4 each keypress is a keypress,
Ah, I forgot to note here that disabling setup-hotkeys or hotkey-setup
or whatever it was called didn't solve the problem after all. However,
an old mailing list posting from 2003 hints at the keyboard handling in
the kernel 2.6 series being the cause of a remarkably similar problem:
The answers
Not only can I confirm that this device doesn't work in Linux; it
doesn't work in 64-bit Windows 7 either!
If this device ever starts being useful for anything, it'll be when they
release new drivers for it.
--
Linksys By Cisco WUSB600N v2 Doesn't Work
https://bugs.launchpad.net/bugs/408165
You
Great news, though! I was able to obtain the same results as Daan Kets
by using the same distro (64-bit Karmic) and the same driver (64-bit XP
version) and following the steps outlined above. Thank you so much for
this invaluable piece of information! Let's hope other buyers of this
device will
Not so great news, though: After working for a short while initially, it
now quickly fails each time it starts connecting to a network, causing
the network-manager utilities to hang until the OS is rebooted. It could
conceivably start to work again temporarily if the machine were
completely
I always thought what the original poster was experiencing was the
kernel bug over at http://bugzilla.kernel.org/show_bug.cgi?id=9147 ,
which is now being handled over there.
Then again, the keys that are getting stuck seem to vary between
different systems, so who knows.
At any rate, good luck
I've seen the reference to the 2.6.27 kernel, but as far as I can see,
it's not in the APT repository, and unless it can be installed quickly
from a package, it'll take too much time away from the tasks the machine
is actually meant to be used for to test a new kernel. Not to mention
that
I'm having this problem in Kubuntu on a Fujitsu Siemens Amilo laptop
with an ATI chipset and without Compiz Fusion. I'm getting the atkbd.c
error message, but not the USB error message.
[13300.027424] atkbd.c: Unknown key released (translated set 2, code 0xe0 on
isa0060/serio0).
[13300.027430]
lspci:
00:00.0 Host bridge: ATI Technologies Inc RS690 Host Bridge
00:01.0 PCI bridge: ATI Technologies Inc RS690 PCI to PCI Bridge (Internal gfx)
00:04.0 PCI bridge: ATI Technologies Inc Unknown device 7914
00:06.0 PCI bridge: ATI Technologies Inc RS690 PCI to PCI Bridge (PCI Express
Port 2)
Unfortunately, I tried the newest driver today, and the image is still
way too dark. Perhaps I should just get a better (third) webcam...
--
The image is way too dark
https://launchpad.net/bugs/80719
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Public bug reported:
When using the spca5xx driver, the image is way too dark. This cannot be
corrected by using options such as gamma or brightness when loading the
driver. Supposedly a newer version of the drivers corrects the problem,
but this is apparently not the version used in Ubuntu.
**
I've had problems with the controls as well, with an ELECOM branded
camera. Supposedly there are newer drivers available?
--
The video controls (contrast, Brightness, ... ) don't work
https://launchpad.net/bugs/70889
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
The problem's still present in 2.6.38, though the stalls are much
shorter. The longest one I've had until the OOM-killer did its job was
about 12 minutes.
Stephane Carrez suggests changing the I/O scheduler to the deadline
scheduler:
The bug's still there
** Changed in: linux (Ubuntu)
Status: Expired = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/582264
Title:
lucid lynx going into disk activity frenzy,
This patch may be related:
http://osdir.com/ml/scm-fedora-commits/2011-06/msg02243.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/717843
Title:
python2.7 python imaging (PIL) dumps core with
The scheduler change helps a lot (just as the kernel upgrade helped),
but the underlying problem is obviously still there – When the system
runs out of memory, it starts furiously using the disk, even when it
isn't using swap.
Since the original poster submitted the requested information, I'm
Odd... But this thread seems to indicate that TWO fixes might be needed?
http://stackoverflow.com/questions/6080825/python-pil-ycbcr-support
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/717843
I can confirm that it works both for converting RGB images and for
creating new YCbCr images in Oneiric Ocelot.
Wonderful news!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/717843
Title:
Even creating a new YCbCr image or converting an existing one to YCbCr
makes PIL crash due to a buffer overflow, so there's a good chance this
is due to that bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Also mentioned here:
http://stackoverflow.com/questions/6080825/python-pil-ycbcr-support
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/717843
Title:
python2.7 python imaging (PIL) dumps core with
I've been having this problem across several versions of Ubuntu, and
have been affected by the problem both in KDE and Gnome.
One link that has been suggested is that it could be related to some
keycode-related error messages that keep appearing in dmesg :
[quote][4335062.871000] atkbd.c: Use
My reply to https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/237604
might be of interest:
[quote]
I've been having this problem across several versions of Ubuntu, and
have been affected by the problem both in KDE and Gnome.
One link that has been suggested is that it could be related to some
** Changed in: xorg (Ubuntu)
Status: Invalid = Confirmed
--
Ctrl-key stuck in Gnome after continued browsing
https://bugs.launchpad.net/bugs/237604
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
It's been 16 hours without the hotkeys-setup service, and so far the
keyboard has worked perfectly. It looks as if we may have found our
culprit.
--
Ctrl-key stuck in Gnome after continued browsing
https://bugs.launchpad.net/bugs/237604
You received this bug notification because you are a member
16 hours, and it's still working. So it's not entirely unlikely hotkeys-
setup has been causing the keyboard problems all along.
--
Keys get stuck down
https://bugs.launchpad.net/bugs/194214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
If you perform dmesg | grep kbd that is
--
Ctrl+Alt keys stuck
https://bugs.launchpad.net/bugs/185208
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Are you getting errors like this?
[4335062.871000] atkbd.c: Use 'setkeycodes e02a keycode' to make it known.
[4335063.546000] atkbd.c: Unknown key pressed (translated set 2, code 0xaa on
isa0060/serio0).
[4335063.546000] atkbd.c: Use 'setkeycodes e02a keycode' to make it known.
[4335063.607000]
I've had a stuck ctrl key that may be related the hotkeys-setup
service. The following messages appeared in dmesg:
[4335062.871000] atkbd.c: Use 'setkeycodes e02a keycode' to make it known.
[4335063.546000] atkbd.c: Unknown key pressed (translated set 2, code 0xaa on
isa0060/serio0).
Are you by any chance getting error messages like this in dmesg?
[4335062.871000] atkbd.c: Use 'setkeycodes e02a keycode' to make it known.
[4335063.546000] atkbd.c: Unknown key pressed (translated set 2, code 0xaa on
isa0060/serio0).
[4335063.546000] atkbd.c: Use 'setkeycodes e02a keycode' to
But now the bug's returned again. Too bad, because this one seemed to be
a winner.
--
Ctrl-key stuck in Gnome after continued browsing
https://bugs.launchpad.net/bugs/237604
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I see. Unfortunately, the bug just returned, too, so hotkey-setup wasn't
the culprit after all. Switching distros or OSes may be the only
solution so far.
--
Ctrl+Alt keys stuck
https://bugs.launchpad.net/bugs/185208
You received this bug notification because you are a member of Ubuntu
Bugs,
No wait, it's back again. It just took a little longer than usual. The
error messages are back, too.
--
rdesktop ctrl key gets stuck on randomly
https://bugs.launchpad.net/bugs/179846
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Unfortunately, disabling hotkey-setup didn't fix the problem after all.
The bug just took a long time to return this time.
--
Keyboard keys get stuck and repeat (Feisty, Gutsy)
https://bugs.launchpad.net/bugs/124406
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
Binary package hint: pulseaudio
After upgrading from Lucid, the system was unable to reproduce sound.
Even yes /dev/dsp had no effect.
For some strange reason, alsamixer showed all channels to be muted while
KDE's mixer didn't – But that turned out not to be the problem.
Public bug reported:
Binary package hint: kde
Turning off Desktop Effects with Kubuntu Maverick causes 3D applications
such as bzflag or glxgears to display a black square instead of
graphics, and Xorg's CPU usage to jump to 100%.
I'm using the proprietary ATI driver, so it would be great if
In fact, it's worse: The commands have to be run after each reboot to
get sound.
--
No sound after Maverick Meerkat upgrade
https://bugs.launchpad.net/bugs/647539
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
The kernel bug theory seems to hold true, as the problem is much less
severe with kernel 2.6.38. The system is now down to stalling for
seconds at a time instead of hours at a time. An improvement by a factor
of 3600x from one version to the next!
Since the problem appears to be in the process of
Definitely still a problem in kernel 2.6.37-12. Today the machine
stalled twice as I was rsyncing some files from one partition to
another.
The first time it lasted for about an hour, during which it was possible
to type in commands, but it literally took an hour to log in and kill a
few
Public bug reported:
Binary package hint: ibus-qt4
When using IBUS with a QT4 application such as VLC og Konqueror, there's
a significant lag before what's being typed appears on the screen, so
that inputting text in near-realtime is not possible.
This delay doesn't occur when using IBUS with
The delay seems to be introduced by some part of the software involved
with holding the composition string before candidate selection.
This can be verified by entering several letters in quick succession,
causing the output to be delayed, and then immediately pressing the
return key. This will
*** This bug is a duplicate of bug 573434 ***
https://bugs.launchpad.net/bugs/573434
** This bug has been marked a duplicate of bug 573434
korean(hangul) is inputted slowly on kubuntu 10.04
--
IBUS is slow in QT4
https://bugs.launchpad.net/bugs/580989
You received this bug notification
As I said in my (duplicate) bug report, the delay seems to occur when a
string has been entered and is about to be displayed as a compose
string. So while IBUS itself is reasonably fast, the user cannot see
what they are typing in real time.
The bug affects other languages as well – I've seen it
Preedit string actually seems to be the proper term.
--
korean(hangul) is inputted slowly on kubuntu 10.04
https://bugs.launchpad.net/bugs/573434
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
*** This bug is a duplicate of bug 568407 ***
https://bugs.launchpad.net/bugs/568407
** This bug is no longer a duplicate of bug 573434
korean(hangul) is inputted slowly on kubuntu 10.04
** This bug has been marked a duplicate of bug 568407
QLineEdit doesn't update text when changed
*** This bug is a duplicate of bug 568407 ***
https://bugs.launchpad.net/bugs/568407
Peng Huang has investigated the problem, and it has turned out to not
originate in ibus-qt. In fact, it also affects SCIM's Qt module, which
is part of an entirely different software package.
** Package
I had it climb to 21% of available memory, which should be about
831.18MB?
--
ibus-daemon applet leaks memory badly
https://bugs.launchpad.net/bugs/583954
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
The IBUS project uses Google Code and Google Groups and not Launchpad
for project management, though, so it's not guaranteed that they'll see
this bug report unless it's reported there.
They also have an IRC channel on Freenode.
--
ibus-daemon applet leaks memory badly
Possibly... I wouldn't be able to say whether that happens in practice,
though.
--
ibus-daemon applet leaks memory badly
https://bugs.launchpad.net/bugs/583954
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
↑ It would seem that it does, since clicking on ibus (Ubuntu) above
yields a number of bug reports with activity in them. So presumably it
will be noticed, then.
--
ibus-daemon applet leaks memory badly
https://bugs.launchpad.net/bugs/583954
You received this bug notification because you are a
Thank you both! This new version does not seem to leak memory at all;
the memory usage stays fixed at 0.9%.
--
ibus-daemon applet leaks memory badly
https://bugs.launchpad.net/bugs/583954
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have this same bug with the two cryptic error codes being 55 instead
of 48.
krdc has also ceased to work, abruptly disconnecting in the same manner,
so it's reasonable to believe krdc is affected by the same bug.
** Also affects: tsclient
Importance: Undecided
Status: New
** Also
The problem occurred specifically with the server windows.ifi.uio.no
belonging to the University of Oslo, and has been experienced and
described by another user here:
http://dragly.org/2010/08/31/internal-licensing-error/
The solution I used was to delete, recreate and chattr +i the licence
file
To modify my earlier statement somewhat:
The problem with the X Error of failed request: BadAtom (invalid Atom
parameter) and so on and so forth is alleviated by changing protocols
from RDP to RDPv5.
The bug that THEN occurs, and the solution for that, is described in the
above URL (
This issue stil affects me in Maverick Meerkat. uname -a returns the following:
Linux big-iron 2.6.35-23-generic #41-Ubuntu SMP Wed Nov 24 11:55:36 UTC 2010
x86_64 GNU/Linux
The bug can be triggered by periods of relatively high disk activity,
but it also seems to generate its own disk activity,
Also, there was an earlier problem with these exact same symptoms which
was said to be due to a race condition triggered when using a swap file
stored on a LUKS-encrypted partition (this is why I no longer use swap).
I still encrypt my /home partition with LUKS, so that could be related
to the
There's also a thread on the forums pertaining to what seems to be this and
several unrelated problems:
http://ubuntuforums.org/showthread.php?t=1478787
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've upgraded to kernel 2.6.37-12-generic, and the problem seems to be
much harder to trigger, but it was still possible. It seems to be
triggered by low-memory conditions:
1) I used the KDE file manager and navigated to a directory containing a lot of
images, so that it started to create
*** This bug is a duplicate of bug 1235991 ***
https://bugs.launchpad.net/bugs/1235991
** This bug has been marked a duplicate of bug 1235991
Can't “use system keyboard layout” in Saucy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
The setting does seem to work somewhat with Saucy and IBus 1.5.3, though
switching it on and off again multiple times resulted in it temporarily
overriding the system keyboard layout so that it functioned like the
Japanese one, and additionally adding a Japanese keyboard layout to the
list of
Public bug reported:
From time to time, extra keyboard layouts are added to the list of
selectable layouts and input methods, without being added by the user.
One way I triggered this just a moment ago was:
1) Use a European system keyboard layout with some non-ASCII (8-bit) characters.
2)
*** This bug is a duplicate of bug 1247471 ***
https://bugs.launchpad.net/bugs/1247471
** This bug has been marked a duplicate of bug 1247471
IBus candidate window disappears off screen
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
It should be note that the default key combination for activating IBus
has changed from Ctrl+Space to Super (Windows key) + Space. This can
be changed in the settings.
Input methods may also have to be added again. In the list of input
methods in the IBus options, Show all input methods must be
Public bug reported:
When typing near the bottom of the screen, the candidate window for
input methods such as Intelligent Pinyin and Anthy disappears off the
screen, which renders IBus unusable.
** Affects: ibus (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug
** Tags added: 1.5.3 13.10 saucy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1247471
Title:
IBus candidate window disappears off screen
To manage notifications about this bug go to:
I'm afraid the problem still persists. I don't remember a new version of
iBus being released on Ubuntu since the problem first appeaed, either.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1247471
When will YOU fix it? You assigned the bug to yourself.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1247471
Title:
IBus candidate window disappears off screen
To manage notifications about this
** Description changed:
This bug is also reported in:
bug #1269483
bug #1269500
bug #1269669
bug #1286476
It affects users trying to install/upgrade libc6 using dpkg, and in my
case occurred during an upgrade from 13.10 to 14.04.
Similar or related bugs are reported in:
Ramdass Israel: Does the crash happen if you run telinit u?
If so, James Hunt has posted a workaround here:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1269405/comments/30
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This started happening on my system when I tried to upgrade to 14.04.
Installing libc6, either amd64 or i386, it would appear, and either via
do-release-upgrade or dpkg directly, will cause the kernel panic.
not syncing: Attempted to kill init!
** This bug is no longer a duplicate of bug
*** This bug is a duplicate of bug 1269731 ***
https://bugs.launchpad.net/bugs/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, which is subscribed to Ubuntu.
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.
The problem seems to be fixed in Ubuntu 14.04, so I would recommend just
upgrading once it's officially released.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1247471
Title:
IBus candidate window
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 to
*** 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 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 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
Public bug reported:
The bug described in
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1269405 ,
https://bugs.launchpad.net/eglibc/+bug/1269483 ,
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1269500 ,
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1269669 and/or
*** 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
** Description changed:
The bug described in
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1269405 ,
https://bugs.launchpad.net/eglibc/+bug/1269483 ,
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1269500 ,
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1269669
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.
*** 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
** 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
** 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
** 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
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.
*** This bug is a duplicate of bug 1269731 ***
https://bugs.launchpad.net/bugs/1269731
Steve Langasek (vorlon) pointed out in bug #1269731 that the issue may
in fact have been fixed, as I could have been running the old version of
upstart when the error occurs.
Running the telinit u command
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
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
Steve Langasek (vorlon) is now saying that the bug was in fact
introduced after version 13.10, which raises some questions as to why
this bug is triggered during upgrades to 14.04.
There is, therefore, a certain probability that users will be affected
by this when upgrading to 14.04.
--
You
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
*** 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 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 no longer a duplicate of bug 1269731
init crashed with SIGSEGV
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1271440
Title:
Kernel panic when trying to upgrade
To manage
*** 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
1 - 100 of 149 matches
Mail list logo