Unfortunately, it happened again. Editing logind.conf did not help.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1730107
Title:
System sleeps when configured not to do so
To manage notifications
After adding the lines "HandleLidSwitch=ignore" and "IdleAction=ignore" to
/etc/systemd/logind.conf, I'm unable to reproduce the problem on the system.
I don't remember restarting systemd or anything else. Yet, the problem appears
to be gone.
--
You received this bug notification because you
** Also affects: xubuntu-meta (Ubuntu)
Importance: Undecided
Status: New
** Tags added: xubuntu
** Description changed:
The system has been configured not to sleep automatically in
xfce4-power-manager.
Even so, it does sleep.
The following is shown in syslog:
Nov 4
** Summary changed:
- System goes to sleep when configured not to do so
+ System sleeps when configured not to do so
** Description changed:
The system has been configured not to sleep automatically in
xfce4-power-manager.
- Even so, it does go to sleep.
+ Even so, it does sleep.
The
Public bug reported:
The system has been configured not to sleep automatically in
xfce4-power-manager.
Even so, it does go to sleep.
The following is shown in syslog:
Nov 4 21:02:49 hostname NetworkManager[921]: [1509825769.2267]
manager: sleep requested (sleeping: no enabled: yes)
Nov 4
** Attachment added: "Power settings - General tab"
https://bugs.launchpad.net/ubuntu/+source/xfce4-power-manager/+bug/1730107/+attachment/5003750/+files/power-settings-general.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug is not a duplicate of bug #1633737, because it's known to
affect at least three separate applications using Python-Qt4.
While the packages for these applications could be separately fixed,
downgrading or otherwise fixing the Python-Qt4 package would fix the
issue for all the applications
Ah! I forgot you also have to add back the old Xenial repositories.
1. su
2. echo "deb http://archive.ubuntu.com/ubuntu/ xenial universe" >>
/etc/apt/source.list
3. echo "deb http://archive.ubuntu.com/ubuntu/ xenial-updates universe" >>
/etc/apt/source.list
4. apt-get update
5. apt-get install
Sorry, source_s_.list:
1. su
2. echo "deb http://archive.ubuntu.com/ubuntu/ xenial universe" >>
/etc/apt/sources.list
3. echo "deb http://archive.ubuntu.com/ubuntu/ xenial-updates universe" >>
/etc/apt/sources.list
4. apt-get update
5. apt-get install python-qt4=4.11.4+dfsg-1build4
su
apt-get install python-qt4=4.11.4+dfsg-1build4
python-qt4-sql=4.11.4+dfsg-1build4
apt-mark hold python-qt4 python-qt4-sql
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1633819
Title:
Some PyQt4
(The apt-mark hold bit prevents the packages from being upgraded. apt-
mark unhold then presumably allows them to be upgraded again.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1633819
Title:
Thanks, themusicgod1! That seems like a nice fix as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1633725
Title:
Mnemosyne fails to start in Yakkety due to missing QtWebKit
To manage
By the way, that information you posted really helped, hjd. By
downgrading to python-qt4=4.11.4+dfsg-1build4 python-qt4-sql=4.11.4
+dfsg-1build4, I managed to get both Mnemosyne and Anki running again.
Most likely other programs would run as well.
--
You received this bug notification because
Here's a temporary fix I tested with Mnemosyne and Anki:
1. Add the Xenial repositories to /etc/apt/sources.list
deb http://archive.ubuntu.com/ubuntu/ xenial universe
deb http://archive.ubuntu.com/ubuntu/ xenial-updates universe
2. apt-get update
3. Install older version of PyQt4
apt-get
Temporary fix:
1. Add the Xenial repositories to /etc/apt/sources.list
deb http://archive.ubuntu.com/ubuntu/ xenial universe
deb http://archive.ubuntu.com/ubuntu/ xenial-updates universe
2. apt-get update
3. Install older version of PyQt4
apt-get install python-qt4=4.11.4+dfsg-1build4
Temporary fix:
1. Add the Xenial repositories to /etc/apt/sources.list
deb http://archive.ubuntu.com/ubuntu/ xenial universe
deb http://archive.ubuntu.com/ubuntu/ xenial-updates universe
2. apt-get update
3. Install older version of PyQt4
apt-get install python-qt4=4.11.4+dfsg-1build4
Wow, thanks! That seems to explain it. That seems to indicate that all
packages depending on PyQt4 and QtWebKit are broken right now. Quite
vexing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
"Some PyQt4 applications fail to start in Yakkety due to missing QtWebKit"
https://bugs.launchpad.net/ubuntu/+source/python-qt4/+bug/1633819
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1620300
Public bug reported:
https://bugs.launchpad.net/ubuntu/+source/mnemosyne/+bug/1633725
Traceback (innermost last):
File "/usr/bin/mnemosyne", line 155, in
debug_file=options.debug_file)
File "/usr/lib/python2.7/dist-packages/mnemosyne/libmnemosyne/__init__.py",
line 164, in initialise
"Some PyQt4 applications fail to start in Yakkety due to missing QtWebKit"
https://bugs.launchpad.net/ubuntu/+source/python-qt4/+bug/1633819
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1633725
"Some PyQt4 applications fail to start in Yakkety due to missing QtWebKit"
https://bugs.launchpad.net/ubuntu/+source/python-qt4/+bug/1633819
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1633737
See also:
https://bugs.launchpad.net/ubuntu/+source/anki/+bug/1633737 Anki fails to start
in Yakkety due to missing QtWebKit
https://bugs.launchpad.net/ubuntu/+source/spyder/+bug/1620300 Spyder won't start
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
See also:
https://bugs.launchpad.net/ubuntu/+source/mnemosyne/+bug/1633725 Mnemosyne
fails to start in Yakkety due to missing QtWebKit
https://bugs.launchpad.net/ubuntu/+source/spyder/+bug/1620300 Spyder won't start
--
You received this bug notification because you are a member of Ubuntu
Bugs,
See also:
https://bugs.launchpad.net/ubuntu/+source/anki/+bug/1633737 Anki fails to start
in Yakkety due to missing QtWebKit
https://bugs.launchpad.net/ubuntu/+source/mnemosyne/+bug/1633725 Mnemosyne
fails to start in Yakkety due to missing QtWebKit
This seems to be the third bug of this nature
** Also affects: spyder (Ubuntu)
Importance: Undecided
Status: New
** Also affects: mnemosyne (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: mnemosyne (Ubuntu)
** No longer affects: spyder (Ubuntu)
--
You received this bug notification because you are a
** Also affects: anki (Ubuntu)
Importance: Undecided
Status: New
** Also affects: spyder (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: spyder (Ubuntu)
** No longer affects: anki (Ubuntu)
--
You received this bug notification because you are a member of
Public bug reported:
Anki fails to start in Yakkety due to a failure to import QtWebKit.
Traceback (most recent call last):
File "/usr/bin/anki", line 7, in
import aqt
File "/usr/share/anki/aqt/__init__.py", line 12, in
from aqt.qt import *
File "/usr/share/anki/aqt/qt.py", line
This bug doesn't concern Mnemosyne 2.4, though, it concerns the package that's
available from Ubuntu repositories in Ubuntu 16.10.
That package doesn't work when installed on the system.
** Changed in: mnemosyne (Ubuntu)
Status: Fix Committed => New
--
You received this bug notification
Public bug reported:
Mnemosyne fails to start in Yakkety due to a failure to import QtWebKit.
Traceback (innermost last):
File "/usr/bin/mnemosyne", line 155, in
debug_file=options.debug_file)
File "/usr/lib/python2.7/dist-packages/mnemosyne/libmnemosyne/__init__.py",
line 164, in
Also occurs on Ubuntu 15.10 with Plymouth 0.9.0-0ubuntu9.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1433168
Title:
plymouthd takes 4-5 cpu load
To manage notifications about this bug go to:
Also, I seem to have a Radeon card, because when the bug occurs, I also
get the message failed to load driver: r600.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1302270
Title:
[regression] Poor
I just started experiencing this bug on 14.10 today, after updating the system.
I do not seem to have bug #1302264, which this bug was marked as a duplicate of.
It's possible to work around the bug by using chown -R user /dev/dri.
** This bug is no longer a duplicate of bug 1302264
I'm still seeing this bug on 14.10.
There are suggestions floating around the web to the effect that it's
caused by systemd.
One suggested solution is to add the following to /etc/systemd/logind.conf :
HandleLidSwitch=ignore
LidSwitchIgnoreInhibited=no
I've done so, but have not rebooted to see
I'm still seeing this bug on 14.10.
I'm trying the logind.conf workaround.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1222021
Title:
[SRU] xfce4-power-manager does not inhibit systemd from
I have xfce4-power-manager 1.4.1-0ubuntu1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1222021
Title:
[SRU] xfce4-power-manager does not inhibit systemd from handling
buttons and lid events
To
** 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.
Two other users have reported having the bug so far.
** Changed in: upstart (Ubuntu)
Status: Invalid = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1303139
Title:
Kernel panic
Two other users have reported having the bug so far.
** Changed in: upstart
Status: Invalid = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1303139
Title:
Kernel panic when dpkg
*** This bug is a duplicate of bug 1303139 ***
https://bugs.launchpad.net/bugs/1303139
** This bug has been marked a duplicate of bug 1303139
Kernel panic when dpkg attempts to install libc6
--
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
See bug #1286476, bug #1269405 , bug #1269483 , bug #1269500 , and bug
#1269669.
Workaround described in
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1269731/comments/32
.
--
You received this
*** This bug is a duplicate of bug 1303139 ***
https://bugs.launchpad.net/bugs/1303139
The relevant part of the workaround in
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1269731/comments/32
is 1) , which describes how to circumvent the program telinit while
the upgrade is underway.
** Description changed:
This bug was first described in bug #1269405 , bug #1269483 , bug #1269500 ,
and bug #1269669.
It affects users trying to install/upgrade libc6 using dpkg, and in my case
occurred during an upgrade from 13.10 to 14.04.
bug #1271440 describes a similar problem,
** Description changed:
- This bug was first described in bug #1269405 , bug #1269483 , bug #1269500 ,
and bug #1269669. Now bug #1286476 has also been submitted, describing the same
problem.
- It affects users trying to install/upgrade libc6 using dpkg, and in my case
occurred during an
** Description changed:
This bug is also reported in:
- bug #1269405
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.
- A similar bug is reported in:
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
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.
Then I'm marking the bugs as duplicates of this one again, as none of
the libc6 bugs should be marked as duplicates of 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/1303139
Title:
** 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
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
The bug occurs when dpkg tries to install libc6 deb, and this triggers
the telinit command.
As you are adamant that this bug is unrelated to the several bugs that
are already filed which describe this exact problem, I've decided not to
spend any more time on it.
If you wish to investigate the
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
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.
*** 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
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
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
*** 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
*** 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)
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 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:
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
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
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 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,
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
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.
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
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
1 - 100 of 149 matches
Mail list logo
