[Ubuntu-x-swat] [Bug 918791] Re: qemu-kvm dies when using vmvga driver and unity in the guest

@ullix could you please give the precise full qemu command line which is failing, and a url to a boot cd I can use for the guest? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-vmware in Ubuntu. https://bugs.launchpad.net/bug

[Ubuntu-x-swat] [Bug 1270452] Re: Lenovo T440 Touchpad needs custom config

It would help to detail exactly which aspect you consider unusable. (I think you have a menu of options :) For me it was the fact that palmdetect was not working. Therefore I currently use this in .config/upstart/touchpad.conf: description "Configure the Hellpad" author "Serge H

Re: [Ubuntu-x-swat] [Bug 660273] Re: 10de:0a75 [Sony VAIO VPCF11KFX] Xorg freeze

Quoting Graham Ranger (660...@bugs.launchpad.net): > For what it's worth, I was having similar problems, and had almost > concluded it was time to change an admittedly old computer (9-10 years). > I had decided it was the graphics card overheating. As a last ditch > attempt, I took the card out and

Re: [Ubuntu-x-swat] [Bug 660273] Re: 10de:0a75 Xorg freeze

No, this issue is fixed, thanks. status: fixreleased ** Changed in: xserver-xorg-video-nouveau (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bu

[Ubuntu-x-swat] [Bug 726099] Re: libvirtd assert failure: *** glibc detected *** /usr/sbin/libvirtd: realloc(): invalid next size: 0x00007f289004d5e0 ***

** Changed in: libvirt (Ubuntu) Status: In Progress => Confirmed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libpciaccess in Ubuntu. https://bugs.launchpad.net/bugs/726099 Title: libvirtd assert failure: *** glibc detected *** /usr/

[Ubuntu-x-swat] [Bug 1045845] Re: 12.10 guest crash on login when using 12.04 qemu-kvm with cirrus driver

Given comment #16, marking this invalid for qemu-kvm. ** No longer affects: qemu-kvm (Ubuntu) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1045845 Title: 12.10 guest crash on login whe

[Ubuntu-x-swat] [Bug 1056381] Re: [FFe: spice] error on x startup

Changelogs for the relevant packages (spice, spice-protocol, and xserver-xorg-video-qxl) from current quantal versions to the proposed new versions. ** Attachment added: "p" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-qxl/+bug/1056381/+attachment/3368270/+files/p -- You rece

Re: [Ubuntu-x-swat] [Bug 1056381] Re: error on x startup

Quoting Timo Aaltonen (tjaal...@ubuntu.com): > I've added spice and spice-protocol to this bug for tracking the > updates. Should we just move forward or do you think we need an FFe? I've asked on #ubuntu-release yesterday - FFE is not needed for qxl, and the feeling seemed to be that it's not nee

[Ubuntu-x-swat] [Bug 1056381] Re: error on x startup

spice, spice-protocol and qxl with proposed patches packages are built in ppa:serge-hallyn/virt. They seem to build and work fine. I think the lightdm screen is messed up (not sure, things are moved around) but once I login it is correct. -- You received this bug notification because you are a

[Ubuntu-x-swat] [Bug 1056381] Re: error on x startup

.13 and so didn't test compilation of -qxl 0.1.0 with that. I only knew that it failed. ** Changed in: xserver-xorg-video-qxl (Ubuntu) Assignee: Serge Hallyn (serge-hallyn) => (unassigned) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribe

[Ubuntu-x-swat] [Bug 1056381] Re: error on x startup

Ok, for a full fix allowing me to log into unity, we need: 1. spice-protocol and spice updated to 0.12 from debian and upstream respectively. Both quite simple 2. The upstream git commits up to and including 37c97620da959d9214abfc760835aa3031d54daa pushed onto the xserver-xorg- video-qxl package

[Ubuntu-x-swat] [Bug 1056381] Re: error on x startup

commit 4a43bd436c58dae72f91905657a36158efc68907 (src/qxl_driver: use the new dixScreenSpecificPrivatesSize) fixes that particular bug. However login still fails with just that one (I immediately am dumped back at the login prompt). Trying to cherrypick more commits to see if they help. -- You r

[Ubuntu-x-swat] [Bug 1056381] Re: error on x startup

** Changed in: xserver-xorg-video-qxl (Ubuntu) Assignee: (unassigned) => Serge Hallyn (serge-hallyn) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-qxl in Ubuntu. https://bugs.launchpad.net/bugs/1056381 Title: er

[Ubuntu-x-swat] [Bug 1056381] Re: error on x startup

looks like upstream may be fixed. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-qxl in Ubuntu. https://bugs.launchpad.net/bugs/1056381 Title: error on x startup To manage notifications about this bug go to: https://bugs.l

[Ubuntu-x-swat] [Bug 1056381] Re: error on x startup

The failing assert is a new one which was not present in precise: assert (!screen_specific_private[type]); The type passed in is PRIVATE_PIXMAP, and: static const Bool screen_specific_private[PRIVATE_LAST] = { [PRIVATE_SCREEN] = FALSE, [PRIVATE_CLIENT] = FALSE, [PRIVATE_WINDOW] =

[Ubuntu-x-swat] [Bug 1056381] Re: error on x startup

(marking confirmed as it has been seen by both stgraber and myself) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-qxl in Ubuntu. https://bugs.launchpad.net/bugs/1056381 Title: error on x startup To manage notifications ab

[Ubuntu-x-swat] [Bug 1056381] Re: error on x startup

Here is the gdb output from apport-retrace: GNU gdb (GDB) 7.5-ubuntu Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the exten

[Ubuntu-x-swat] [Bug 1056381] [NEW] error on x startup

Public bug reported: When installing a new quantal VM from the desktop iso, (or when selecting 'Try ubuntu' from that iso), when x starts up it crashes and the X low resolution failsafe dialog comes up. ** Affects: xserver-xorg-video-qxl (Ubuntu) Importance: High Status: Confirmed

[Ubuntu-x-swat] [Bug 1045845] Re: 12.10 guest crash on login when using 12.04 qemu-kvm with cirrus driver

** Attachment added: "Another stack trace" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1045845/+attachment/3298730/+files/gdbout2 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net

[Ubuntu-x-swat] [Bug 1045845] Re: 12.10 guest crash on login when using 12.04 qemu-kvm with cirrus driver

Hi Bryce, is what I pasted above sufficient to be helpful? ** Changed in: xorg-server (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1045845

[Ubuntu-x-swat] [Bug 1045845] Re: 12.10 guest crash on login when using 12.04 qemu-kvm with cirrus driver

root@serge-virtual-machine:~# apport-retrace --gdb --sandbox system --cache=yyy _usr_bin_Xorg.0.crash Installing extra package xserver-xorg-core to get ExecutablePath GNU gdb (GDB) 7.5-ubuntu Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later

[Ubuntu-x-swat] [Bug 1045845] Re: 12.10 guest crash on login when using 12.04 qemu-kvm with cirrus driver

NATURALLY once -dbgsym is installed this becomes much harder to reproduce, implying this is a timing related bug. Unfortunately unpacking a previous /var/run/_usr_bin_Xorg.0.crash file and running 'sudo gdb /usr/bin/X CoreDump' doesn't give any sort of backtrace. -- You received this bug notific

[Ubuntu-x-swat] [Bug 1045845] Re: 12.10 guest crash on login when using 12.04 qemu-kvm with cirrus driver

(by 'doesn't give any sort of backtrace' of course I mean that it has none of the needed debug symbols for the related libraries) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1045845 Titl

[Ubuntu-x-swat] [Bug 1045845] Re: 12.10 guest crash on login when using 12.04 qemu-kvm with cirrus driver

The colord crash happens every time I log in over vnc, even when I start dwm instead of unity. The xorg crash only happens with unity. Just installed -dbgsym in the hopes of getting a backrace. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xo

[Ubuntu-x-swat] [Bug 1045845] Re: 12.10 guest crash on login when using 12.04 qemu-kvm with cirrus driver

Here is a tarball with a few crashfiles from /var/run. I'm pretty sure the compiz one is unrelated (that it happened when I logged in over SDL instead of over VNC) The others are two pairs of crash files from two attempts to log in over vnc. ** Attachment added: "crashes.tgz" https://bugs.la

[Ubuntu-x-swat] [Bug 1045845] Re: 12.10 guest crash on login when using 12.04 qemu-kvm with cirrus driver

I can reproduce this with vnc, but not with SDL. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1045845 Title: 12.10 guest crash on login when using 12.04 qemu-kvm with cirrus driver T

[Ubuntu-x-swat] [Bug 1045845] Re: 12.10 guest crash on login when using 12.04 qemu-kvm with cirrus driver

** Changed in: qemu-kvm (Ubuntu) Assignee: (unassigned) => Serge Hallyn (serge-hallyn) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1045845 Title: 12.10 guest crash on login w

[Ubuntu-x-swat] [Bug 1045845] Re: 12.10 guest crash on login when using 12.04 qemu-kvm with cirrus driver

** Changed in: qemu-kvm (Ubuntu) Importance: Low => Medium -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1045845 Title: 12.10 guest crash on login when using 12.04 qemu-kvm with cirru

[Ubuntu-x-swat] [Bug 1045845] Re: 12.10 guest crash on login when using 12.04 qemu-kvm with cirrus driver

Haven't tested this, but will mark it confirmed. Hopefully we can just fix bug 1040033! ** Changed in: qemu-kvm (Ubuntu) Status: New => Confirmed ** Changed in: qemu-kvm (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu-X,

[Ubuntu-x-swat] [Bug 918791] Re: qemu-kvm dies when using vmvga driver and unity in the guest

the oneiric-proposed fix was deleted by a security update. As noone has verified it since march, I will wait until someone asks for it before re-uploading. (simple debdiff from the cached .dsc's for 6.2 and 6.3) -- You received this bug notification because you are a member of Ubuntu-X, which i

[Ubuntu-x-swat] [Bug 918791] Re: qemu-kvm dies when using vmvga driver and unity in the guest

@houstonbofh which release is your host? Please show the result of 'virsh dumpxml MACHINEID | grep machine' -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-vmware in Ubuntu. https://bugs.launchpad.net/bugs/918791 Title: qe

[Ubuntu-x-swat] [Bug 964830] Re: system keeps coming saying it needs to enter low graphics mode

*** This bug is a duplicate of bug 969489 *** https://bugs.launchpad.net/bugs/969489 ** This bug has been marked a duplicate of bug 969489 lightdm tries (and fails) to start too early? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidi

[Ubuntu-x-swat] [Bug 913314] Re: Corrupted display with Spice

Munzir, also, to help keep the symptoms straight, would you mind opening a new bug against xserver-xorg-video-qxl for the resolution issues? (You can point back to comments 18 and 19 in this bug for the log files). -- You received this bug notification because you are a member of Ubuntu-X, whi

[Ubuntu-x-swat] [Bug 913314] Re: Corrupted display with Spice

Munzir, tjaalton pointed out that there is a new qxl xorg server in debian. Would you be able to test that to see if it fixes your existing bugs? If it does, then we can try to get it into precise. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to

[Ubuntu-x-swat] [Bug 964830] Re: system keeps coming saying it needs to enter low graphics mode

-- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/964830 Title: system keeps coming saying it needs to enter low graphics mode To manage notifications about this bug go to: https

[Ubuntu-x-swat] [Bug 964830] [NEW] system keeps coming saying it needs to enter low graphics mode

Public bug reported: But when I switch to a console and say 'start lightdm', I can log into full-res unity 3d just fine. (I can't interact with the dialog asking me whether I want to reconfigure x, becuase the mouse doesn't work there) ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: nvidia

[Ubuntu-x-swat] [Bug 918791] Re: qemu-kvm dies when using vmvga driver and unity in the guest

@Martin, No - I"m still not sure about its responsibilities, so I don't know whether it's deemed a bug that it is using negative values, but certainly (virtualized) hardware shouldn't crash due to it, so that's where we're fixing it. So I'll mark the -vmware package part of the bug invalid. Than

[Ubuntu-x-swat] [Bug 918791] Re: qemu-kvm dies when using vmvga driver and unity in the guest

** Also affects: qemu-kvm (Ubuntu Oneiric) Importance: Undecided Status: New ** Also affects: xserver-xorg-video-vmware (Ubuntu Oneiric) Importance: Undecided Status: New ** Description changed: + = + SRU Justification: + 1.

[Ubuntu-x-swat] [Bug 918791] Re: qemu-kvm dies when using vmvga driver and unity in the guest

@Jamie, yes libvirt supports spice. You do have to set the video section accordingly. Here is an example xml file that works for me: spice 524288 524288 1 hvm destroy restart restart /usr/bin/kvm-spice

[Ubuntu-x-swat] [Bug 918791] Re: qemu-kvm dies when using vmvga driver and unity in the guest

This patch probably isn't the right place in the stack to catch this, but it seems to work for me. With this patch, qemu doesn't crash for me. ** Patch added: "qemu-vmware.debdiff" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-vmware/+bug/918791/+attachment/2798995/+files/qemu-

[Ubuntu-x-swat] [Bug 918791] Re: qemu-kvm dies when using vmvga driver and unity in the guest

@Jamie, > Also, unfortunately unity-2d does not run with with cirrus driver under > 11.04, so > the security and SRU teams are unable to properly test updates in GUI > applications > under unity when using the current 12.04 qemu-kvm Note that I can run unity-2d and unity-3d using spice, i.e. k

[Ubuntu-x-swat] [Bug 918791] Re: qemu-kvm dies when using vmvga driver and unity in the guest

** Also affects: xserver-xorg-video-vmware (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-vmware in Ubuntu. https://bugs.launchpad.net/bugs/918791 Title: qemu-kvm dies wh

[Ubuntu-x-swat] [Bug 913314] Re: Corrupted display with Spice

@Munzir thanks for the info. Can you give us a recipe for reproducing some of the errors? Are you still using a kde guest? Do the errors come up at random, or when you do specific things with the mouse? -- You received this bug notification because you are a member of Ubuntu-X, which is subs

[Ubuntu-x-swat] [Bug 913314] Re: Corrupted display with Spice

I don't have the ability to push it myself, but will ping the x folks and see what can be done to get the fix in. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-qxl in Ubuntu. https://bugs.launchpad.net/bugs/913314 Title: C

[Ubuntu-x-swat] [Bug 913314] Re: Corrupted display with Spice

** Changed in: spice (Ubuntu) Status: New => Invalid ** Changed in: qemu-kvm-spice (Ubuntu) Status: New => Invalid ** Bug watch added: Debian Bug tracker #655318 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655318 ** Also affects: xserver-xorg-video-qxl (Debian) via http:

[Ubuntu-x-swat] [Bug 913311] Re: X crashes repeatedly (qxl/spice)

*** This bug is a duplicate of bug 913314 *** https://bugs.launchpad.net/bugs/913314 Turns out to be fixed by the same patch as bug 913314, so i'll mark this as a duplicate of that. ** This bug has been marked a duplicate of bug 913314 Corrupted display with Spice -- You received this bu

[Ubuntu-x-swat] [Bug 913314] Re: Corrupted display with Spice

THis patch, cherry-picked from upstream, appears to fix both this bug and 913311! ** Patch added: "translate-the-access-region.patch" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-qxl/+bug/913314/+attachment/2665651/+files/translate-the-access-region.patch -- You received this

[Ubuntu-x-swat] [Bug 913314] Re: Corrupted display with Spice

Here is a debdiff for adding the dbg package. ** Patch added: "xserver-xorg-video-qxl-add-dbg.debdiff" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-qxl/+bug/913314/+attachment/2665644/+files/xserver-xorg-video-qxl-add-dbg.debdiff -- You received this bug notification because

[Ubuntu-x-swat] [Bug 913314] Re: Corrupted display with Spice

Line 300 below is where it fails 295 /*-- all but last block: aligned reads and affect 32 bits of (a,b,c) */ 296 while (length > 12) 297 { 298 a += k[0]; 299 b += k[1]; 300 c += k[2]; 301 mix(a,b,c); 302 length -= 12;

[Ubuntu-x-swat] [Bug 913314] Re: Corrupted display with Spice

Fixed the -dbg package. Here is a new gdb session log pin-pointing where (but not, to my untrained eye, why) the segfault happens. ** Attachment added: "gdb-Xorg.txt" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-qxl/+bug/913314/+attachment/2665615/+files/gdb-Xorg.txt -- You

[Ubuntu-x-swat] [Bug 913314] Re: Corrupted display with Spice

(I do see now that the detail info comes from xserver-common-dbg, none from xserver-xorg-video-qxl-dbg - hopefully after a restart tomorrow there will be more info) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-qxl in Ubuntu.

[Ubuntu-x-swat] [Bug 913314] Re: Corrupted display with Spice

I created a xserver-xorg-video-qxl-dbg package and reproduced as per https://wiki.ubuntu.com/X/Backtracing#Backtrace_with_gdb. The following backtrace has a bit more info. ** Attachment added: "gdb-Xorg.txt" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-qxl/+bug/913314/+attachm

[Ubuntu-x-swat] [Bug 913314] Re: Corrupted display with Spice

Reproduced. ** Changed in: xserver-xorg-video-qxl (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-qxl in Ubuntu. https://bugs.launchpad.net/bugs/913314 Title: Corrupted display with

[Ubuntu-x-swat] [Bug 913311] Re: X crashes repeatedly (qxl/spice)

** Changed in: xserver-xorg-video-qxl (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-qxl in Ubuntu. https://bugs.launchpad.net/bugs/913311 Title: X crashes repeatedly (qxl/spice) T

[Ubuntu-x-swat] [Bug 913314] Re: Corrupted display with Spice

Thanks, Dave. Is this also (lik3 913311) using unity-2d? ** Changed in: xserver-xorg-video-qxl (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-qxl in Ubuntu. https://bugs.launchpad.ne

[Ubuntu-x-swat] [Bug 902237] Re: kvm-spice cannot boot KDE - qxl display driver segfaults

** Summary changed: - kvm-spice is very slow to boot + kvm-spice cannot boot KDE - qxl display driver segfaults -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-qxl in Ubuntu. https://bugs.launchpad.net/bugs/902237 Title: kv

[Ubuntu-x-swat] [Bug 902237] Re: kvm-spice is very slow to boot

kvm comes from the qemu-kvm package, which comes from the qemu-kvm source tree (git://git.kernel.org/pub/scm/virt/kvm/qemu-kvm.git). This enables kvm by default. The qemu-kvm-spice package is provided by the qemu-linaro source package, which is based on the qemu source tree (git://git.qemu.org/qe

[Ubuntu-x-swat] [Bug 902237] Re: kvm-spice is very slow to boot

** Also affects: xserver-xorg-video-qxl (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-qxl in Ubuntu. https://bugs.launchpad.net/bugs/902237 Title: kvm-spice is very slow

Re: [Ubuntu-x-swat] [Bug 817632] Re: terminal frequently gets corrupted

I can't test guest logins right now, since gnome/unity logins appear to have been killed by my last update. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/817632 Title: termin

[Ubuntu-x-swat] [Bug 817632] Re: terminal frequently gets corrupted

If you like, though that seems a little aggressive. I couldn't reproduce lately due to lack of access to the affect system. I got access to it again today, and yes the terminal still does it. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvid

Re: [Ubuntu-x-swat] [Bug 817632] Re: terminal frequently gets corrupted

Quoting Bryce Harrington (817...@bugs.launchpad.net): > Huh, that's very odd. When did this first start occurring? > > If you upgraded to oneiric recently, did it occur in previous ubuntu > installations? No it didn't happen in natty. It is similar to what used to happen years ago on an old thi

[Ubuntu-x-swat] [Bug 817632] Re: terminal frequently gets corrupted

-- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/817632 Title: terminal frequently gets corrupted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/

[Ubuntu-x-swat] [Bug 817632] [NEW] terminal frequently gets corrupted

Public bug reported: My gnome-terminal frequently does not getupdated. For instance, I'll type a command or an irc comment, but the terminal won't update until I hit ctrl-l (which sometimes does not work) or switch to another viewport and back. ProblemType: Bug DistroRelease: Ubuntu 11.10 Packag

[Ubuntu-x-swat] [Bug 726099] Re: libvirtd assert failure: *** glibc detected *** /usr/sbin/libvirtd: realloc(): invalid next size: 0x00007f289004d5e0 ***

Can anyone who has installed the proposed packages please comment to let us know how long they've been using it? We'd like an idea of wether (a) noone is using it or (b) people using it are just not seeing the issue any more. many thanks. -- You received this bug notification because you are a

[Ubuntu-x-swat] [Bug 726099] Re: libvirtd assert failure: *** glibc detected *** /usr/sbin/libvirtd: realloc(): invalid next size: 0x00007f289004d5e0 ***

** Attachment added: "libvirt-pci-32bit-debs.tgz" https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/726099/+attachment/1988492/+files/libvirt-pci-32bit-debs.tgz -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libpciaccess in Ubuntu. http

[Ubuntu-x-swat] [Bug 726099] Re: libvirtd assert failure: *** glibc detected *** /usr/sbin/libvirtd: realloc(): invalid next size: 0x00007f289004d5e0 ***

Hi, could everyone please install the amd64 packages in comment #11 and shout if it happens again with these packages? many thanks. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libpciaccess in Ubuntu. https://bugs.launchpad.net/bugs/726099

[Ubuntu-x-swat] [Bug 726099] Re: libvirtd assert failure: *** glibc detected *** /usr/sbin/libvirtd: realloc(): invalid next size: 0x00007f289004d5e0 ***

** Attachment added: "Package with more conservative locking" https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/726099/+attachment/1987596/+files/libvirt-pci-debs.tgz -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libpciaccess in Ubuntu

[Ubuntu-x-swat] [Bug 726099] Re: libvirtd assert failure: *** glibc detected *** /usr/sbin/libvirtd: realloc(): invalid next size: 0x00007f289004d5e0 ***

** Changed in: libvirt (Ubuntu) Status: Incomplete => In Progress -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libpciaccess in Ubuntu. https://bugs.launchpad.net/bugs/726099 Title: libvirtd assert failure: *** glibc detected *** /usr

[Ubuntu-x-swat] [Bug 746064] Re: libvirtd crashed with SIGSEGV in realloc()

*** This bug is a duplicate of bug 726099 *** https://bugs.launchpad.net/bugs/726099 ** Visibility changed to: Public ** This bug has been marked a duplicate of bug 726099 libvirtd assert failure: *** glibc detected *** /usr/sbin/libvirtd: realloc(): invalid next size: 0x7f289004d5e0

[Ubuntu-x-swat] [Bug 750645] Re: libvirtd crashed with SIGABRT in __kernel_vsyscall()

*** This bug is a duplicate of bug 726099 *** https://bugs.launchpad.net/bugs/726099 ** This bug is no longer a duplicate of bug 746064 libvirtd crashed with SIGSEGV in realloc() ** This bug has been marked a duplicate of bug 726099 libvirtd assert failure: *** glibc detected *** /usr/sb

[Ubuntu-x-swat] [Bug 750645] Re: libvirtd crashed with SIGABRT in __kernel_vsyscall()

*** This bug is a duplicate of bug 746064 *** https://bugs.launchpad.net/bugs/746064 ** This bug has been marked a duplicate of private bug 746064 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libpciaccess in Ubuntu. https://bugs.launchpad

[Ubuntu-x-swat] [Bug 750645] Re: libvirtd crashed with SIGABRT in __kernel_vsyscall()

Could you attach the output of 'sudo lspci -v'? If it happens again - or if you have not yet rebooted since that happened - could you attach /var/log/boot.log? Thanks, still trying to reproduce. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to l

[Ubuntu-x-swat] [Bug 750645] Re: libvirtd crashed with SIGABRT in __kernel_vsyscall()

Thanks for taking the time to report this bug and helping to make Ubuntu better. Hm, once again libpciaccess shows up in the stack trace. Did you do anything in particular before the crash happened? Can you trigger this kind of crash with just 'restart libvirt-bin', or is it only, unpredictably,

[Ubuntu-x-swat] [Bug 726099] Re: libvirtd assert failure: *** glibc detected *** /usr/sbin/libvirtd: realloc(): invalid next size: 0x00007f289004d5e0 ***

Two of the duplicates are from lucid, have the same eglibc signature as this one (bad old size in realloc), but those don't show where that was called. This bug (the original) and the other dup from natty both show libpcialloc to be the one which called realloc when it failed. ** Also affects: eg

[Ubuntu-x-swat] [Bug 655446] Re: Xorg won't start

Yay, latest nvidia driver in natty is working for me on my Sony vaio F11. ** Changed in: nvidia-graphics-drivers (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in ubuntu

[Ubuntu-x-swat] [Bug 655446] Re: Xorg won't start

The last time I tried, which I think was after natty alpha-1, I still had this problem. Unfortunately that laptop is currently serving wireless for the whole house and family, so it may take a few days before I can find a good time to test. I'll leave the bug state 'incomplete' until I can confir

[Ubuntu-x-swat] [Bug 660273] Re: Xorg freeze

-- Xorg freeze https://bugs.launchpad.net/bugs/660273 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@li

[Ubuntu-x-swat] [Bug 660273] Re: Xorg freeze

** Attachment added: "The Xorg.0.log.old file from the hang" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/660273/+attachment/1691841/+files/Xorg.0.log.old -- Xorg freeze https://bugs.launchpad.net/bugs/660273 You received this bug notification because you are a member of Ubuntu-X, whi

[Ubuntu-x-swat] [Bug 660273] [NEW] Xorg freeze

Public bug reported: Binary package hint: xorg Laptop (using nouveau drivers and compiz) was humming along nicely, then froze - I could move the mouse but keyboard and mouse clicks were ignored, and cpu usage must have been high as the fan got very loud. The Xorg.0.old logfile (about to be attac

[Ubuntu-x-swat] [Bug 655446] Re: Xorg won't start

RAOF on #ubuntu-desktop pointed me to http://www.nvnews.net/vbulletin/showthread.php?t=155218 . Falling back to the 256.53-0ubuntu3 nvidia-common package fixes the issue. So the 260 nvidia driver appears broken for my vaio F11 laptop. -- Xorg won't start https://bugs.launchpad.net/bugs/655446

[Ubuntu-x-swat] [Bug 655446] Re: Xorg won't start

** Attachment added: "BootDmesg.txt" https://bugs.launchpad.net/bugs/655446/+attachment/1674328/+files/BootDmesg.txt ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/655446/+attachment/1674329/+files/CurrentDmesg.txt ** Attachment added: "Dependencies.txt" http

[Ubuntu-x-swat] [Bug 655446] [NEW] Xorg won't start

Public bug reported: Binary package hint: xorg I updated my maverick laptop this afternoon. Now after boot is mostly completed, I get a blank screen. I can't get to any terminals either (without booting an older kernel, where I get dropped straight into a console instead of getting X). All I

[Ubuntu-x-swat] [Bug 641320] Re: Touchpad is not working since last kernel update in maverick

This is an Xorg.log from the working kernel which I'm booted in now. ** Attachment added: "Xorg.0.log" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/641320/+attachment/1598356/+files/Xorg.0.log -- Touchpad is not working since last kernel update in maverick https://bugs.launchpad.net/b

[Ubuntu-x-swat] [Bug 641320] Re: Touchpad is not working since last kernel update in maverick

** Attachment added: ".proc.driver.nvidia.cards.0.txt" https://bugs.launchpad.net/bugs/641320/+attachment/1598306/+files/.proc.driver.nvidia.cards.0.txt ** Attachment added: ".proc.driver.nvidia.registry.txt" https://bugs.launchpad.net/bugs/641320/+attachment/1598307/+files/.proc.driver.n

[Ubuntu-x-swat] [Bug 641320] [NEW] Touchpad is not working since last kernel update in maverick

Public bug reported: Binary package hint: xorg I called it an xorg bug, but it's probably purely a kernel bug. When I boot the previous kernel, touchpad works. When I boot the one which was installed with last night's maverick update, I can't move the mouse or click with the touchpad. Proble

[Ubuntu-x-swat] [Bug 553647] Re: xserver crash (repeatable, triggered by drawing circle/ellipse e.g. in xfig)

Seconded. I ended up using xfig under vnc which did work, but is a bit more cumbersome. Otherwise (with a nvidia geforce 310m) xserver crashes. -- xserver crash (repeatable, triggered by drawing circle/ellipse e.g. in xfig) https://bugs.launchpad.net/bugs/553647 You received this bug notificati