In Ubuntu 16.10 the kernel configuration seems to have again
# CONFIG_AUFS_XATTR is not set
I'm wondering if this is intentional or by mistake. Observed from linux-
image-4.8.0-21-generic_4.8.0-21.23_amd64.deb.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
This problem only seems to affect Kubuntu upgrades, where the graphical
frontend 'DistUpgradeViewKDE' is used.
If the text mode upgrade is used (e.g. 'do-release-upgrade -d') the
release notes are not shown at all. Also if the GTK graphical frontend
is used (e.g. 'do-release-upgrade -d --frontend=
This might be a duplicate of bug #1509655. If /var/log/dist-
upgrade/main.log ends with a python backtrace pointing to
DistUpgradeViewKDE.py line 339, it is the same problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
Public bug reported:
Upgrading from 15.10 to 16.04 may fail e.g. in corporate environments
where firewall or IDS/IPS equipment enforce strict HTTP protocol usage.
The failure occurs right in the beginning of the upgrade, as the
upgrader fails to retrieve the release announcement that would be show
The reason of the problem is visible in the python backtrace of the bug
description, where line 339 of DistUpgradeViewKDE.py causes a TypeError:
File
"/tmp/ubuntu-release-upgrader-7bai3dvc/DistUpgrade/DistUpgradeViewKDE.py", line
339, in conffile
self.confDialogue.show_difference_bu
For the record, I also suffered from similar symptoms after upgrading to
Saucy, and the reason turned out to be pam_systemd missing from
/etc/pam.d/common-session.
However, in my case the upgrade had succeeded and package libpam-systemd
had been installed. It did not add pam_systemd to common-sess
The KDE bug tracker has the following bug report about a situation which
leads to similar mouse problems as described here. That problem occurs
only if the mouse gestures feature has been turned on.
https://bugs.kde.org/show_bug.cgi?id=224712
There is also a method for recovering from the pro
** Tags added: lucid
--
PyQt4 applications crash at exit
https://bugs.launchpad.net/bugs/561303
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to python-qt4 in ubuntu.
--
kubuntu-bugs mailing list
kubuntu-b...@lists.ubuntu.com
https://lists.ubun
Public bug reported:
Binary package hint: python-qt4
Package python-qt4 (python bindings for qt4) seems to be broken in Lucid
beta 2. Many PyQt4 applications crash at exit, which can be easily
reproduced by running some of the example applications available in
package python-qt4-doc. For example,
Just to add to my comment about e100 driver yesterday, I found
discussion about this problem in the 'Intel Wired Ethernet' project in
SourceForge
(http://sourceforge.net/tracker/?func=detail&aid=2876241&group_id=42302&atid=447449),
and also a fix to the problem in kernel.org git repositories (commi
After upgrading from Ubuntu 9.04 to 9.10 (kernel 2.6.28 to 2.6.31), I
have similar problem with the e100 network driver. It seems that the
firmware used to be within the driver in the older kernels, but is now
available as a separate binary
/lib/firmware/2.6.31-14-generic/e100/d101m_ucode.bin. At b
I started having this problem after upgrading from Intrepid to Jaunty.
At that time I was using the default GNOME desktop.
However, the problem disappeared when I installed the kubuntu-desktop
package and starting using KDE desktop. I'm not able to reproduce the
endless repeat behavior any more wi
I have reported my observations with Jaunty and 'xset r off' to the
upstream bug tracker as
http://bugs.freedesktop.org/show_bug.cgi?id=21454 .
** Bug watch added: freedesktop.org Bugzilla #21454
https://bugs.freedesktop.org/show_bug.cgi?id=21454
--
Keyboard keys get stuck and repeat (Feisty,
I upgraded two machines from Intrepid to Jaunty and started having this
problem of stuck keys. It never occurred before the upgrade, and as the
two machines have very different hardware, I would imagine the problem
is not hardware dependent.
I have two ways of reproducing the problem:
1) In a gno
14 matches
Mail list logo
