I have verified the fixed package, see attached terminal output.
Steps taken:
- check package version
- verify nf_tables is used
- check default chains have not been created yet
- run test case
- check if default chain has been created
After that I upgraded the iptables packages on my neutron
That's a bug in iptables, fixed in iptables upstream, see bug 1898547.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1902270
Title:
iptables-restore fails on groovy
To manage notifications about
I could reproduce the issue by building git v1.8.5 and the issue was
fixed after cherry-picking "iptables-nft: fix basechain policy
configuration"
$ git log
commit 8d985eb4eb7a23fd98b75d71179af40169144cc5 (HEAD -> bug1898547)
Author: Pablo Neira Ayuso
Date: Fri Oct 2 13:44:36 2020 +0200
This issue was fixed in iptables git master commit
dac904bdcd9a18aabafee7275ccf0c2bd53800f3
I guess the actual fix may have been "iptables-nft: fix basechain policy
configuration", commit 0bd7a8eaf3582159490ab355b1217a4e42ed021f
--
You received this bug notification because you are a member of
** Changed in: neutron (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898547
Title:
neutron-linuxbridge-agent fails to start with iptables 1.8.5
To manage
Public bug reported:
Ubuntu Groovy (20.10)
kernel 5.8.0-20-generic
neutron-linuxbridge-agent: 2:17.0.0~git2020091014.215a541bd4-0ubuntu1
iptables: 1.8.5-3ubuntu1 (nf_tables)
iptables-restore points to xtables-nft-multi
After upgrading iptables from 1.8.4 to 1.8.5 and rebooting the neutron
I created a new horizon host on bionic with bionic/ussuri and installed
openstack-dashboard.
openstack-dashboard:
Installed: 3:18.3.2-0ubuntu0.20.04.1~cloud0
apache error log showed many errors about missing policy files
admin panel was visible while logged in as non-admin user
I enabled
I created a new horizon host on focal and installed openstack-dashboard.
openstack-dashboard:
Installed: 3:18.3.2-0ubuntu0.20.04.1
apache error log showed many errors about missing policy files
admin panel was visible while logged in as non-admin user
I enabled focal-proposed and upgraded
Also happens with bionic/ussuri
apt policy python3-django-horizon
python3-django-horizon:
Installed: 3:18.3.2-0ubuntu0.20.04.1~cloud0
Candidate: 3:18.3.2-0ubuntu0.20.04.1~cloud0
Version table:
*** 3:18.3.2-0ubuntu0.20.04.1~cloud0 500
500
Trying to build the focal proposed package, it seems adding the mo files
to SOURCES.txt with sed instead of regenerating SOURCES.txt does the
job.
I changed debian/rules:
#rm -f horizon.egg-info/SOURCES.txt
sed -i 's/\(.*\)po$$/\1po\n\1mo/' horizon.egg-info/SOURCES.txt
Building the package with
James Page submitted a fix upstream:
https://github.com/ceph/ceph-deploy/pull/496
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864993
Title:
platform.linux_distribution has been removed from
This is still an issue with the package from focal-proposed:
3:18.3.2-0ubuntu0.20.04.1
** Summary changed:
- Policy files are missing
+ [Focal] Policy files are missing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
openstack-dashboard:
Installed: 3:18.2.1~git2020041013.754804667-0ubuntu2
sudo ls -la /var/lib/openstack-dashboard/
total 20
drwxr-x--- 4 horizon horizon 4096 Apr 20 09:37 .
drwxr-xr-x 23 rootroot4096 Apr 20 09:36 ..
drwxr-x--- 2 horizon horizon 4096 Apr 17 11:14 secret-key
-rw---
Public bug reported:
After bug 1866187 "dnsmasq needs access to /var/lib/neutron/dhcp" was
fixed we now got a new error:
/var/lib/neutron/dhcp/ is not accessible.
due to: find /var/lib/neutron -type f -exec chmod 0640 "{}" + -o -type d
-exec chmod 0750 "{}" +
Apr 17 10:57:16 network
openstack-dashboard:
Installed: 3:18.2.1~git2020041013.754804667-0ubuntu1
Situation got worse now.
Package does: find /var/lib/openstack-dashboard -type f -exec chmod 0640 "{}" +
-o -type d -exec chmod 0750 "{}" +
which makes all directories under /var/lib/openstack-dashboard/static
With Original package
rabbitmq-server:
Installed: 3.6.10-1
~# rabbitmqadmin --version
rabbitmqadmin %%VSN%%
With upgraded package from proposed
rabbitmq-server:
Installed: 3.6.10-1ubuntu0.1
~# rabbitmqadmin --version
rabbitmqadmin 3.6.10
I use rabbitmq as part of a small openstack test
This issue seems to be caused by the regenerated SOURCES.txt file from:
horizon (3:18.0.1~git2020021409.bb959361b-0ubuntu3) focal;
urgency=medium
* d/rules: Force regeneration of SOURCES.txt to ensure that generated
django{js}.mo files are included in binary packages, resolving issues
Public bug reported:
python3-django-horizon:
Installed: 3:18.2.1~git2020032709.2c4470272-0ubuntu1
After a fresh install of openstack dashboard on focal, apache2 error.log
contains hundreds of error message about missing policy files:
[Tue Apr 14 09:12:34.558183 2020] [wsgi:error] [pid
Public bug reported:
After a fresh install of an openstack cluster in focal, dd 8 April,
horizon does not show details on images and network topology and does
not allow to launch a new instance.
>From cli, using openstack-client, everything works fine.
Apache error log shows many errors, like:
I re-installed the neutron node from scratch, with neutron
2:16.0.0~b3~git2020032420.a0e1b5804e-0ubuntu2
Now neutron-common postinst does chmod 0750 /var/lib/neutron which makes
the dhcp files unreadable:
Mar 27 20:36:15 network dnsmasq[6218]: failed to load names from
Public bug reported:
I installed a fresh test cloud in focal. After creating some networks
and subnets, neutron-dhcp-agent complained:
sudo journalctl -u neutron-dhcp-agent -e
Mar 05 11:43:53 network dnsmasq[13211]: failed to load names from
Public bug reported:
Running ceph-deploy in focal, using python3.8, results in an error
message:
[ceph_deploy][ERROR ] RuntimeError: AttributeError: module 'platform'
has no attribute 'linux_distribution'
It turns out platform.linux_distribution has been removed from python 3.8
(bpo-28167:
Public bug reported:
I installed a fresh openstack test cluster in eoan today (October 3).
Neutron database initialization with the command:
sudo su -s /bin/sh -c "neutron-db-manage
--config-file /etc/neutron/neutron.conf
--config-file /etc/neutron/plugins/ml2/ml2_conf.ini
upgrade head"
I tested on xenial by creating an eoan pbuilder.
With the existing debootstrap package (1.0.78+nmu1ubuntu1.8) this fails with
error message:
Warning: Unknown distribution "eoan". Do you want to continue [y|N]? n
After upgrading to debootstrap from xenial-proposed
(1.0.78+nmu1ubuntu1.9) the eoan
Has OPENSTACK_KEYSTONE_BACKEND been added to REST_API_REQUIRED_SETTINGS?
After an upgrade from queens I did not have the "create role" option
either. Adding OPENSTACK_KEYSTONE_BACKEND to REST_API_REQUIRED_SETTINGS
fixed that.
Both options are properly set in /etc/openstack-
I guess you upgraded from an original neutron 8 config to queens. In
queens external_network_bridge has been deprecated and should not be
used (Using this will result in incorrect port statuses).
What happens if you use "external_network_bridge = "
--
You received this bug notification because
I confirm the issue I reported in comment #7 has been fixed.
After installing openvswitch-common, openvswitch-switch, python-openvswitch
2.9.2-0ubuntu0.18.04.2 the neutron-openvswitch-agent continued working and
after restarting neutron-openvswitch-agent network traffic between running
After installing this upgrade, my openstack neutron services didn't start
anymore.
Neutron log shows:
2018-10-18 08:08:10.573 16703 CRITICAL neutron [-] Unhandled error:
ImportError: No module named compat
...
2018-10-18 08:04:30.302 14895 ERROR neutron File
I installed 2:12.0.1-0ubuntu1 in bionic and was hit by high cpu load on neutron
and computes from neutron-linux-bridge-agent.
Neutron 12.0.1 contains the fix for bug 1745468, which unfortunately caused new
bug 1750777.
The fix for that new bug fixed the high cpu load for me in bionic.
I *think*
apt-cache show bridge-utils | grep -E "Pack|Vers|Confl"
Package: bridge-utils
Version: 1.5-15ubuntu1
Conflicts: ifupdown (<< 0.8.17)
So that conflict applies to ifupdown 0.8.16ubuntu2 in Bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: ureadahead (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/660043
Title:
ureadahead buffer size seems too small
To manage notifications about
Joseph,
with default module parameters for 3.6, meaning emulate_invalid_guest_state=Y,
both 3.6-rc1 and -rc2 are good.
However, with emulate_invalid_guest_state=N, like it is with 3.5 kernels, both
rc1 and rc2 are bad. Also 3.6-rc7 from the mainline ppa is bad with this module
parameter
linux-image-3.5.0-15-generic_3.5.0-15.22~lp1045027v1_amd64.deb works
fine for me too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1045027
Title:
[regression] iPXE kills kvm with KVM: entry
As both the error message and the commit message refer to big real mode I
tried a locally build 3.5.3 kernel with commit KVM: VMX: Fix KVM_SET_SREGS
with big real mode segments reverted.
With an unmodified local build 3.5.3 I could reproduce the original error.
With the local build 3.5.3 with
I am seeing this same error message when I start kvm with an empty disk
attached right when pxe kicks in. With kernel v3.6-rc3 it works fine, with
v3.5.3it still fails.
I found a comment from the upstream developer at
http://www.mail-archive.com/kvm@vger.kernel.org/msg73419.html:
We'll try to
Apparantly the wrong version of the patch went into 3.4-rc5, so there is a
follow up patch now:
drm/i915: Do no set Stencil Cache eviction LRA w/a on gen7+.
See http://lists.freedesktop.org/archives/intel-gfx/2012-May/017391.html
--
You received this bug notification because you are a member
This bug has been fixed in xserver upstream:
commit af88b43f9e604157b74270d609c08bdfa256a792
Author: Peter Hutterer peter.hutte...@who-t.net
Date: Fri Apr 27 16:31:17 2012 +1000
dix: don't emulate scroll events for non-existing axes (#47281)
No, you cannot use the -intel package from 11.10, because it is build
for an older xserver version.
Xorg log says:
[ 1010.456] BUG: triggered 'if (!dev-valuator || dev-valuator-numAxes 2)'
That suggests this is a duplicate of bug 921236. There success is
reported by downgrading
A patch was submitted to intel-gfx yesterday: [Intel-gfx] [PATCH v2] drm/i915:
Set the Stencil Cache eviction policy to non-LRA mode.. I have tested this
patch on top of the precise kernel 3.2.0-24-generic. Googleearth no longer
freezes when zooming in.
The patch is currently on it's way to
** Visibility changed 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/975901
Title:
guest session is not confined by apparmor
To manage notifications about this bug go to:
The name collision is discussed in
https://bugs.launchpad.net/keystone/+bug/910484
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/916773
Title:
package python-keystoneclient (not installed) failed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/916773
Title:
package python-keystoneclient (not installed) failed to
install/upgrade: trying to overwrite '/usr/bin/keystone', which is
also in
Public bug reported:
Trying to install python-keystoneclient fails as /usr/bin/keystone is
also shipped in the keystone package.
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: python-keystoneclient (not installed)
ProcVersionSignature: Ubuntu 3.2.0-8.15-generic 3.2.0
Uname: Linux
Hi Micah,
I have tried several ways to get the package working without --no-as-needed,
but no joy.
To my understanding the problem is:
- the plugins are needed to initialize structures in ebtables/libebtc. They do
this via their magic _init functions, which run when the plugins are loaded, by
The segfault is cause by the as-needed compiler change. This also happened at
SUSE, see https://bugzilla.novell.com/show_bug.cgi?id=567267.
The attached debdiff solves the issue for me. It builds, installs and runs fine
(tested on amd64).
I also added a small change to get a dbgsym package for
I am frequently hit by a different crash (bug 819314), so I cannot say
lightdm is stable yet. However, the specific code leading to the double
kill in this bug seems to have been removed, so I don't think this
specific crash can happen anymore.
--
You received this bug notification because you
Michael,
no, it does not crash every time, but it does happen frequently.
I have run the script, see the attached output. The script completed without
errors.
** Attachment added: lala output
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/812862/+attachment/2240730/+files/lala.out
--
I re-open this bug as apport marks newer crashes duplicate against this bug and
there was no actual fix for this bug yet.
The crash happened for me with version 0.4.3-0ubuntu1 (see bug 809781). I
attached lightdm.log to my bug which shows:
[+27.77s] WARNING: Greeter did not quit, sending kill
** Visibility changed 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/812862
Title:
aptd crashed with SIGSEGV in std::basic_stringchar,
std::char_traitschar, std::allocatorchar
0x0f14d268: 0x60020100: CONSTANT_BUFFER: valid
0x0f14d26c: 0x0f133587:offset: 0x0f133580, length: 512 bytes
0x0f14d270: HEAD 0x7b001804: 3DPRIMITIVE: tri fan sequential
This is almost certain
https://bugs.freedesktop.org/show_bug.cgi?id=38771, fixed in mesa git
master and 7.11
*** This bug is a duplicate of bug 774978 ***
https://bugs.launchpad.net/bugs/774978
[ 5758.687] 4: /usr/bin/X (_CallCallbacks+0x34) [0x432af4]
[ 5758.687] 5: /usr/bin/X (WriteToClient+0x21a) [0x461cca]
[ 5758.687] 6: /usr/lib/xorg/modules/extensions/libdri2.so
(ProcDRI2WaitMSCReply+0x52)
*** This bug is a duplicate of bug 774978 ***
https://bugs.launchpad.net/bugs/774978
[370186.294] 3: /usr/bin/X (_CallCallbacks+0x3e) [0x8074e1e]
[370186.294] 4: /usr/bin/X (WriteToClient+0x267) [0x80a7607]
[370186.294] 5: /usr/lib/xorg/modules/extensions/libdri2.so
*** This bug is a duplicate of bug 774978 ***
https://bugs.launchpad.net/bugs/774978
[47.040] 4: /usr/bin/X (_CallCallbacks+0x34) [0x432af4]
[47.040] 5: /usr/bin/X (WriteToClient+0x21a) [0x461c9a]
[47.040] 6: /usr/lib/xorg/modules/extensions/libdri2.so
(ProcDRI2WaitMSCReply+0x52)
*** This bug is a duplicate of bug 774978 ***
https://bugs.launchpad.net/bugs/774978
[ 8481.477] 3: /usr/bin/X (_CallCallbacks+0x3e) [0x8074e1e]
[ 8481.477] 4: /usr/bin/X (WriteToClient+0x267) [0x80a7607]
[ 8481.477] 5: /usr/lib/xorg/modules/extensions/libdri2.so
Public bug reported:
Binary package hint: unity-2d
When trying to start a unity 2d session, the session crashes and the login
screen appears again.
Running unity-2d-launcher in a recovery session shows a segfault while drawing
the launcher, see the attached backtrace.
The numbers in the
** Attachment added: launcher3.dbg
https://bugs.launchpad.net/bugs/789909/+attachment/2146890/+files/launcher3.dbg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/789909
Title:
unity-2d-launcher
Marcelo, the record extension will still be loaded indeed. However, without
synaptics the extension is not activated.
You can check this by attaching gdb to Xorg (from a second pc) and setting a
breakpoint on RecordAReply. If the breakpoint is hit, record is active.
With synaptics installed (on
I have tracked down the crash a bit further, by adding debug prints when
input buffers are freed.
[ 18735.941] REQUEST: ClientIDX: 6, type: 0x89 data: 0xa len: 8 buffer:
0x7fba90fa8010 name: DRI2
[ 18735.943] Add buffer to FreeInputs, aci: 0x2e7d8c0 buffer: 0x7fba90fa8010
[ 18735.943] REQUEST:
*** This bug is a duplicate of bug 774978 ***
https://bugs.launchpad.net/bugs/774978
** Tags removed: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/776749
Title:
xserver crashed with
I have tried running X under strace, but no success. I couldn't
reproduce the crash, probably because X became too slow. Log file when
calibre was running was 5 GB.
I also tried xtrace and valgrind without luck. xtrace only showed what
calibre was doing. Valgrind shows errors, but only before and
Public bug reported:
Binary package hint: xserver-xorg-video-intel
Xserver frequently crashes when I start calibre and switch between different
ebooks in the ebook list.
This crash is quite reproducible, about 80% of the times I run calibre. The
crash happens both in unity and in classic
** Attachment added: stacktrace
https://bugs.launchpad.net/bugs/776749/+attachment/2110611/+files/calibre_X.stacktrace
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/776749
Title:
xserver
Public bug reported:
Binary package hint: ia32-libs
Running googleearth on amd64 uses software 3D. The 32 bit dri drivers in
ia32-libs cannot be used because they cannot find libdricore and libglsl.
For example ldd /usr/lib32/dri/i965_dri.so shows:
libdricore.so = not found
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/755720
Title:
32 bit dri drivers cannot find libdricore and libglsl
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I noticed the refcount patch was applied in natty and can confirm
logging out has been working fine in natty for the past couple of weeks.
xorg-server (2:1.9.99.902-2ubuntu1) natty; urgency=low
...
* 215_glx_drawable_refcounting.diff:
- Refcount GLXDrawables to avoid use-after-free crashes.
A patch was posted by Chris Wilson today on the dri-devel mailing list
that fixes this crash for me:
glx: Refcnt the GLXDrawable to avoid use after free with multiple
FreeResource
Although there may be more than one resource handles pointing to the
Drawable, we only want to
I have been trying to debug this and think I found the problem:
- The crash is caused when an already freed drawable is used (drawable contents
are invalid)
- The crashing resource always has xid=0. If I prevent DrawableGone calls when
xid=0, the crash does not happen. XID=0 seems strange, as
Public bug reported:
Binary package hint: ureadahead
After upgrading to maverick, I noticed boot time was longer than with lucid,
about 42s in maverick instead of 30s in lucid.
From the bootchart it seemed ureadahead was not properly working. It showed
continuous hdd activity.
From the
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/660043/+attachment/1691231/+files/Dependencies.txt
--
ureadahead buffer size seems too small
https://bugs.launchpad.net/bugs/660043
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: bootchart with maverick version
https://bugs.launchpad.net/ubuntu/+source/ureadahead/+bug/660043/+attachment/1691232/+files/bootchart-orig.png
--
ureadahead buffer size seems too small
https://bugs.launchpad.net/bugs/660043
You received this bug notification because you
** Attachment added: bootchart with 128MB/num_cpus buffer
https://bugs.launchpad.net/ubuntu/+source/ureadahead/+bug/660043/+attachment/1691233/+files/bootchart-128MB.png
--
ureadahead buffer size seems too small
https://bugs.launchpad.net/bugs/660043
You received this bug notification
** Attachment added: bootchart with 8MB fixed buffer
https://bugs.launchpad.net/ubuntu/+source/ureadahead/+bug/660043/+attachment/1691234/+files/bootchart-8MB.png
--
ureadahead buffer size seems too small
https://bugs.launchpad.net/bugs/660043
You received this bug notification because you
CurrentDmesg shows:
[12436.390414] Out of memory: kill process 29463 (mutter) score 157749 or a
child
[12436.390430] Killed process 29463 (mutter) vsz:630996kB, anon-rss:13324kB,
file-rss:16868kB
So mutter was killed because you ran out of memory. It looks like mutter is
using a lot of RAM.
As you are using an intel 945 and the bug happens when you have an
extended desktop with width 2048 and there is the error message (EE)
intel(0): Failed to allocate framebuffer. this seems to be freedesktop
bug 28515 (libdrm) which is fixed in:
commit 726210f87d558d558022f35bc8c839e798a19f0c
Disassembling dixFreePrivates in gdb shows the crash is happening in:
if (items[i].size)
xfree(privates[i].value);
Also, Kubuntu resets/regenerates the Xserver on log-out, where Gnome starts a
new server on log-out.
The regeneration bit in the git commit
The xorg logs for both Manolo and Ride show you are using the old Jaunty kernel
(2.6.28) and drm is not properly working. Please make sure you boot with the
new Karmic kernel (2.6.31) and see if that solves the problem.
If the karmic kernel still has this problem, please attach xorg.0.log and
Log message:
Fatal server error:
Cannot run in framebuffer mode. Please specify busIDsfor all
framebuffer devices
is the same we have seen in Karmic in bug 383407. It was fixed in the
xserver:
xorg-server (2:1.6.1.901-2ubuntu2) karmic; urgency=low
* Add
This was most likely the same problem as bug 454029, which was fixed
with:
xserver-xorg-video-intel (2:2.9.0-1ubuntu2~xup~3) jaunty; urgency=low
* Reinstate 01_gen_pci_ids.diff for jaunty xserver (LP: #454029)
and ship the pci ids file
** Changed in: xserver-xorg-video-intel (Ubuntu)
The screenshot looks like the screenshot in
http://bugs.freedesktop.org/show_bug.cgi?id=24315 comment 2.
Robert, if you can confirm the upstream screenshots match what you are seeing,
it may be worth to add a tracker.
** Bug watch added: freedesktop.org Bugzilla #24315
** Also affects: xserver-xorg-video-intel via
https://bugs.freedesktop.org/show_bug.cgi?id=24315
Importance: Unknown
Status: Unknown
--
graphics corruption occuring with normal use
https://bugs.launchpad.net/bugs/454984
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 455114 ***
https://bugs.launchpad.net/bugs/455114
** This bug has been marked a duplicate of bug 455114
builds uninstallable package 'kvm'
--
kvm is not updated in a jaunty to karmic upgrade
https://bugs.launchpad.net/bugs/454733
You received this bug
*** This bug is a duplicate of bug 454029 ***
https://bugs.launchpad.net/bugs/454029
Fredrik: this issue was fixed today. If you install the latest version of the
intel driver, you should be fine again.
(xserver-xorg-video-intel 2:2.9.0-1ubuntu2~xup~3). See also bug 454029
** This bug has
*** This bug is a duplicate of bug 455114 ***
https://bugs.launchpad.net/bugs/455114
** This bug has been marked a duplicate of bug 455114
builds uninstallable package 'kvm'
--
kvm is not updated in a jaunty to karmic upgrade
https://bugs.launchpad.net/bugs/454733
You received this bug
Public bug reported:
Binary package hint: qemu-kvm
On my karmic test system kvm has been kept back for some time now.
As this seems to be a potential problem for jaunty to karmic upgrades, I tested
an upgrade in a pbuilder chroot.
- start jaunty pbuilder
- install kvm
- install
** Attachment added: XsessionErrors.txt
http://launchpadlibrarian.net/33904688/XsessionErrors.txt
--
kvm is not updated in a jaunty to karmic upgrade
https://bugs.launchpad.net/bugs/454733
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
*** This bug is a duplicate of bug 454029 ***
https://bugs.launchpad.net/bugs/454029
** This bug has been marked a duplicate of bug 454029
screen resolution messed up; no longer recognizes monitor type
--
Unknown display, resolution shoud be 1024*600 but only 800*600 allowed. (EEE PC
*** This bug is a duplicate of bug 454029 ***
https://bugs.launchpad.net/bugs/454029
** This bug has been marked a duplicate of bug 454029
screen resolution messed up; no longer recognizes monitor type
--
Screen resolution doesn't go past 800x600,
https://bugs.launchpad.net/bugs/454240
*** This bug is a duplicate of bug 454029 ***
https://bugs.launchpad.net/bugs/454029
** This bug has been marked a duplicate of bug 454029
screen resolution messed up; no longer recognizes monitor type
--
xserver-xorg-video-intel version 2.9.0 for jaunty in PPA broken on eeepc
From Xorg.0.log:
(II) Scanning /usr/share/xserver-xorg/pci directory for additional PCI ID's
supported by the drivers
(II) No matches found for this device in /usr/share/xserver-xorg/pci
The update is missing the list of pci ids for intel. Xserver 1.6.3 in jaunty
still needs those pci ids.
Public bug reported:
Binary package hint: qemu-kvm
On my karmic test system kvm has been kept back for some time now.
As this seems to be a potential problem for jaunty to karmic upgrades, I tested
an upgrade in a pbuilder chroot.
- start jaunty pbuilder
- install kvm
- install
** Attachment added: XsessionErrors.txt
http://launchpadlibrarian.net/33904688/XsessionErrors.txt
--
kvm is not updated in a jaunty to karmic upgrade
https://bugs.launchpad.net/bugs/454733
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Erik, you are using an old kernel, which had problems to load drm correctly (as
shown in XorgLogOld.txt).
Can you please install the latest kernel (2.6.31-14-generic) and test if you
can still reproduce the problem?
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: New =
Thanks for confirming, Jeremy. I will close the bug then.
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Incomplete = Fix Released
--
[GM45] X Crashes Every Time I Close Zsnes
https://bugs.launchpad.net/bugs/433310
You received this bug notification because you are a member of
Closing the bug, as the problem was solved by a reinstall for both John
and Kieran.
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Confirmed = Fix Released
--
[i965GM] Desktop effects could not be enabled
https://bugs.launchpad.net/bugs/410258
You received this bug notification
The partial stacktrace in Xorg log shows 3:
/usr/lib/dri/i965_dri.so(intelDestroyContext+0x10a)
A crash in intelDestroyContext on GM965 was recently fixed in mesa
(7.6.0~git20090817.7c422387-0ubuntu7) and now in mesa 7.6.0
Jeremy, could you please test if you still have this problem?
--
[GM45]
It seems you are all using the intel driver from the xorg-edgers ppa.
In this driver support for user mode setting has been dropped. This
means you now have to use a kernel with modesetting (KMS) enabled. The
easiest way to do this is to install the kernel from the same ppa and
reboot using that
The agp issue of bug 430694 was fixed in linux 2.6.31-12.41. David's logs show
he was using an older kernel.
David, could you please test with the latest kernel and see if that solves the
problem?
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: New = Incomplete
--
[i945] 945
Moving to xserver-xorg-video-ati based on info from log files.
** Package changed: xserver-xorg-video-vesa (Ubuntu) = xserver-xorg-
video-ati (Ubuntu)
--
Xserver crash: Logout when Firefox or Empathy is in action
https://bugs.launchpad.net/bugs/446648
You received this bug notification because
Francis: you have got the new xserver-xorg-video-intel package
(2.9.0-1ubuntu1) from karmic, which was uploaded just before you added
the ppa. So the fix is already in Karmic and there is no need anymore to
upload any logs. Therefore I will close this bug.
Most likely this fix solved your mouse
As the freeze is fixed for the original reporter, I will close this bug
now.
The 2.9 Intel driver has been uploaded to Karmic and should become available in
the coming hours (depending on the mirror you are using).
If you find any other issues, please report these as a new bug.
** Changed in:
1 - 100 of 342 matches
Mail list logo
