This should be closed - I solved the problem by going around it, and
can't reproduce it.
** Description changed:
When I do either apt-get update; apt-get upgrade or aptitude upgrade,
the process exits on error without completing fully.
The error is:
72 packages upgraded, 1 newly
Public bug reported:
All-in-one OpenStack LXC setup as described in
https://wiki.ubuntu.com/ServerTeam/Oneiric/OpenStackTestPlan
I was able to successfully spawn multiple instances (in this case 6) in
one reservation - they all started up correctly; however I then tried to
terminate all six in
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/868206
Title:
terminating multiple lxc instances fails with I/O errors
To manage notifications about this bug go to:
** Attachment added: kern.log
https://bugs.launchpad.net/ubuntu/+source/nova/+bug/868206/+attachment/2512134/+files/kern.log
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/868206
** Attachment added: nova-api.log
https://bugs.launchpad.net/ubuntu/+source/nova/+bug/868206/+attachment/2512153/+files/nova-api.log
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
** Attachment added: nova-compute.log
https://bugs.launchpad.net/ubuntu/+source/nova/+bug/868206/+attachment/2512154/+files/nova-compute.log
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
** Attachment added: nova-dhcpbridge.log
https://bugs.launchpad.net/ubuntu/+source/nova/+bug/868206/+attachment/2512155/+files/nova-dhcpbridge.log
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
** Attachment added: nova-manage.log
https://bugs.launchpad.net/ubuntu/+source/nova/+bug/868206/+attachment/2512156/+files/nova-manage.log
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
** Attachment added: nova-objectstore.log
https://bugs.launchpad.net/ubuntu/+source/nova/+bug/868206/+attachment/2512157/+files/nova-objectstore.log
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
** Attachment added: nova-scheduler.log
https://bugs.launchpad.net/ubuntu/+source/nova/+bug/868206/+attachment/2512158/+files/nova-scheduler.log
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
** Changed in: etckeeper (Ubuntu)
Status: New = Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to etckeeper in Ubuntu.
https://bugs.launchpad.net/bugs/800656
Title:
Update Manager can not proceed if there is a lock on
I'm not sure I follow your question - what was not ever done?
-will
On Tue, 2011-10-04 at 18:43 +, Serge Hallyn wrote:
I'm curious why this was not ever done. Was there a glitch when it
was
attempted?
--
You received this bug notification because you are subscribed to the
bug
Thanks for reporting this bug and helping to make Ubuntu better.
I've tested a bit here, and it is waiting on my systems. Could you
check to make sure that the acpid package is installed on your guests?
the pre-stop section tries to cleanly shut down guests with 'virsh
shutdown', but that will
@Will,
marking qemu-common as replacing qemu.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/592010
Title:
hardy2lucid upgrade: qemu-common should replace qemu as well as qemu-
@Geoff,
the only thing I notice in your competions script is that it doesn't
autocomplete names for other connections, so in particular
virsh -c lxc:/// start tab
does not complete with the available lxc containers. Is this something
you've already fixed in your own version?
I've marked
I already reinstalled the test systems with 11.04 so i can't send logs
anymore.
acpid was installed on the VM's and shutdown was confirmed by both the
shutdownlog and visual confirmation of the VM's shutting down. One test
VM was a ubuntu 11.04 desktop install that pop's up the gnome shutdown
** Changed in: postfix (Ubuntu)
Status: Expired = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to postfix in Ubuntu.
https://bugs.launchpad.net/bugs/766833
Title:
package postfix 2.7.0-1ubuntu0.1 failed to
Hello Canonical guys,
I have this problem specially for new and fast machines. Boot is just
too fast. If autofs uses network shares (nis, nis+, ldap), it only can
start autofs after the network is up (upstart bug?). Another solution is
to start immediatelly (for static entries) and, after network
FYI This has been fixed upstream for a while now:
commit c6a6dc1d2d04b1d5aeb6978577f4d08a216f93ed
Author: Justin Clift jcl...@redhat.com
Date: Fri Jul 9 19:21:39 2010 +1000
libvirtd: add man page for libvirtd
--
You received this bug notification because you are a member of Ubuntu
Server
FYI upstream NetCF now has support for Debian style network config:
http://git.fedorahosted.org/git/?p=netcf.git;a=commit;h=5a84c95bea872d31f66be2ed6353734793a83aed
http://berrange.com/posts/2011/09/28/porting-netcf-to-debianubuntu-suse-and-windows/
this would enable the libvirt network APIs to
I maintain a 10.04 LTS based cluster of workstations where each node is subject
to some stress and need to be restarted once in a while. Autofs maps of nfs
shares are communicated via LDAP. Autofs fails to initialize (or even start in
some rare cases) in its default configuration in about 50%
Hi Serge
I'll have to hunt around for the source, I've since left the place
where I wrote that. I do recall updating it, but it may take me a
while to source it.
Geoff
On 5 October 2011 07:32, Serge Hallyn 457...@bugs.launchpad.net wrote:
@Geoff,
the only thing I notice in your competions
Thanks, Daniel. I'll fix the package to install the manpage.
** Changed in: libvirt (Ubuntu)
Assignee: (unassigned) = Serge Hallyn (serge-hallyn)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
Thanks, Daniel, we had noticed this in the last few days. I'm going to
test the packages and hopefully get them into P post haste :)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
FYI, in my case, 11.04, reload autofs is not enough. I need to use
restart autofs
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to autofs in Ubuntu.
https://bugs.launchpad.net/bugs/40189
Title:
autofs needs to be restarted to pick up
Serge,
Not having looked at the file, just dropping a file into
/etc/bash_completion.d is totally fine and is an easy packaging change
without a huge Ubuntu delta. We should send upstream and to Debian, but
I don't think we need to block on it.
--
You received this bug notification because you
** Patch added: Debdiff to fix this
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/522710/+attachment/2512826/+files/libvirt-man.debdiff
** Changed in: libvirt (Ubuntu)
Assignee: Serge Hallyn (serge-hallyn) = (unassigned)
** Changed in: libvirt (Ubuntu)
Status: Confirmed
Public bug reported:
The instances do not stop correctly. An error is triggered and the
instances are not removed from the DB and are still shown as ACTIVE
(even if the KVM processes and the network configuration are deleted
correctly ).
* Package used: nova 2011.3-0ubuntu5 (but the problem is
Thanks for the info, dyna. I'll (unfortunately) mark this bug invalid
as we've lost access to the system. If the bug was not due to the /run
conversion bug, then it should be reported again soon.
(Based on your comment, I wonder whether we should up the timeout to 70
seconds.)
** Changed in:
These packages fix the problem for me. Thanks Jamie!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/865462
Title:
Upgrade to 0.25.4-2ubuntu6.3 introduces
Public bug reported:
The virbr0 interface with a rfc1918 address stays around after removing
libvirt-bin. I also tried reinstalling it and stop libvirt-bin, that
didn't work either. Google found me some virsh incantations and virsh
net-destroy default finally did the trick.
ProblemType: Bug
Quoting Erno Kuusela (e...@iki.fi):
Public bug reported:
The virbr0 interface with a rfc1918 address stays around after removing
libvirt-bin. I also tried reinstalling it and stop libvirt-bin, that
didn't work either. Google found me some virsh incantations and virsh
net-destroy default
Eric,
Thanks for reporting this.
I haven't been able to reproduce this in my test environment. I suspect
a race, I think I know where it is and I've tried writing a few test
cases but haven't been able to catch this.
Can you tell me if you are able to reliably reproduce this every time,
or at
See https://www.redhat.com/archives/libvir-
list/2011-October/msg00104.html and https://www.redhat.com/archives
/libvir-list/2011-October/msg00110.html for the upstream response. The
first message describes the proper fix (switching from chown to acls in
the dac security code). The second
** Tags added: server-o-rs
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/868349
Title:
instances do not stop correctly
To manage notifications about this bug go to:
Yes, this happens every time on my installation.
- If I install Nova from ppa:nova-core/trunk I do not have the problem
(there is no console log fifo/ring).
- If I remove line 221 and line 222 in
/usr/share/pyshared/nova/virt/libvirt/connection.py-ubuntu:
---
def close(self):
Thanks Eric. I've reproduced it on a fresh oneiric install and am
working on it now.
** Changed in: nova (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
** Changed in: nova (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/868349
Title:
instances do not stop correctly
To manage notifications
I really need mysql-server for work. I can't use ubuntu without it. My
approach right now is to install mysql-5.0.
Any leads I can follow?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.1 in Ubuntu.
Public bug reported:
Cobbler enlist needs to either give an optional --dns-name paramter the
gets set to --system-name if null, or automatically assign dns-name to
system name when registering system with the server.
** Affects: cobbler-enlist (Ubuntu)
Importance: High
Status:
Hi Pavel,
2011/10/4 Павел Гуменюк pavel.gumen...@gmail.com:
Hello.
I've been trying to got it work but haven't luck.
I'm using NUT 2.6.0-1 under Windows XP with libusb driver installed
(USB\VID_0D9FPID_0004REV_0001).
I had tryed all options with such config:
PWCOM]
driver =
Public bug reported:
Help screen reads:
--netif is optional; if not specified, all network I/Fs will be registered
all other parameters are required
However, if netif is not specified, only the first interfaces MAC
address is registered
** Affects: cobbler-enlist (Ubuntu)
Importance:
It seems that os.open(..., os.O_NONBLOCK) nevertheless does block, so
self.fd is not replaced. If ConsoleLogger.close() gets called at this
point from another thread, then a double close is attempted. The fix for
this is trivial, although I'm still baffled by how this is possible in
eventlet. I
** Branch linked: lp:~racb/nova/868349
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/868349
Title:
instances do not stop correctly
To manage notifications about this bug go to:
Public bug reported:
I have an Ubuntu LXC host with several containers running internet
services via xinetd.
Sometimes the container services die without any reason and no logfile
entry. First, I thought LXC is not that stable as I hoped, but now I
found the bug inside /etc/init.d/xinetd !
Sorry, forgot to mention: this is on Ubuntu 10.04
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to xinetd in Ubuntu.
https://bugs.launchpad.net/bugs/868538
Title:
/etc/init.d/xinetd kills LXC container's xinetd
To manage
Hi amavis Users!
On 12 September 2011 20:29, Andreas Neustifter
andreas.neustif...@gmail.com wrote:
I discovered a bug that prevents amavisd-release from working on
messages that have an empty X-Envelope-To-Blocked line in the headers.
To avoid duplication I posted details and a patch at
This version of the bash completion file works for me with '-c lxc:///'.
I'd like to think there was a cleaner way of handling this though.
** Attachment added: virsh
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/457163/+attachment/2514275/+files/virsh
** Changed in: bash-completion
My intent is to add this to the libvirt package as soon as I've merged
the newest package into P.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/457163
Title:
virsh lacks bash
yes, I can set a readonly mount. Will have it set in a few. Thank you,
Serge.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/691590
Title:
libvirt should not take ownership of ISO
This bug was fixed in the package puppet - 0.25.4-2ubuntu6.4
---
puppet (0.25.4-2ubuntu6.4) lucid-security; urgency=low
* adjust ssh_authorized_key/parsed.rb: save backup file to filebucket before
dropping privileges. Based on upstream commit:
** Visibility changed to: Public
** Changed in: puppet (Ubuntu Hardy)
Status: Confirmed = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/861182
Title:
Remote
Marking bug as public, since the issue is public now. I have uploaded
untested hardy packages for this and the other CVE that affects hardy to
https://launchpad.net/~ubuntu-security-proposed/+archive/ppa/+packages.
These patches came from upstream and applied cleanly. Since this is in
universe,
Pocket copied puppet to hardy-proposed. Please test and give feedback
here. See https://wiki.ubuntu.com/Testing/EnableProposed for
documentation on how to enable and use -proposed. Thank you in advance!
** Tags removed: security-verification
** Tags added: verification-needed
** Description
To ubuntu-sru: if this passes the verification process, please also
pocket copy to security. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/861182
Title:
Remote directory
** Branch linked: lp:ubuntu/hardy-proposed/puppet
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/861182
Title:
Remote directory traversal, allows write to arbitrary locations
To
I've discovered that a chroot can be escaped by chrooting to any file.
I'm interested on how this plays on attempting to protect /dev/log?
From what I can gather is that chroots should not be used as a security
measure(as they are in this case), but only as a device to run multiple
distributions
Blueprint changed by Dave Walker:
Whiteboard changed:
[lynxman]
Cobbler way of determining distro (by checking directory hierarchy) doesn't
work with mini.iso, do we want to keep it that way or improve distro detection
-- Andreas seems to have got it working.
Work Items for
Blueprint changed by Dave Walker:
Whiteboard changed:
[lynxman]
Cobbler way of determining distro (by checking directory hierarchy) doesn't
work with mini.iso, do we want to keep it that way or improve distro detection
-- Andreas seems to have got it working.
Work Items for
I am also annoyed by that behaviour after every update of the package.
Adam's analysis in comment #7 is right and I think its suggestion should
be implemented.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
You have been subscribed to a public bug:
running on Oneiric, connecting to machines running Natty. On these
machines, the libvirt/qemu versions are as follows:
ii libvirt-bin
0.8.8-1ubuntu6.5
ii libvirt0
Looks like a libvirt issue, reassigning.
** Package changed: virt-manager (Ubuntu) = libvirt (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/868753
Title:
qemu+ssh
** Changed in: ipmitool (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ipmitool in Ubuntu.
https://bugs.launchpad.net/bugs/845068
Title:
ipmitool is not packaged for ARM
To manage
Just upgraded to oneiric, bug persists sigh
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/510587
Title:
Bind/named does not initialize on boot due to missing IPv6 address
** Changed in: eucalyptus/1.6
Status: Fix Committed = Fix Released
** Changed in: eucalyptus
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in Ubuntu.
** Changed in: eucalyptus/1.6
Status: Fix Committed = Fix Released
** Changed in: eucalyptus
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in Ubuntu.
** Changed in: eucalyptus/1.5
Status: Fix Committed = Fix Released
** Changed in: eucalyptus
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in Ubuntu.
** Changed in: eucalyptus/1.6
Status: Fix Committed = Fix Released
** Changed in: eucalyptus
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in Ubuntu.
** Changed in: eucalyptus/1.6
Status: Fix Committed = Fix Released
** Changed in: eucalyptus
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in Ubuntu.
** Changed in: eucalyptus/1.6
Status: Fix Committed = Fix Released
** Changed in: eucalyptus
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in Ubuntu.
** Changed in: eucalyptus/1.6
Status: Fix Committed = Fix Released
** Changed in: eucalyptus
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in Ubuntu.
** Changed in: eucalyptus/1.6
Status: Fix Committed = Fix Released
** Changed in: eucalyptus
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in Ubuntu.
** Changed in: eucalyptus/1.6
Status: Fix Committed = Fix Released
** Changed in: eucalyptus
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in Ubuntu.
The attachment 868349.patch of this bug report has been identified as
being a patch. The ubuntu-reviewers team has been subscribed to the bug
report so that they can review the patch. In the event that this is in
fact not a patch you can resolve this situation by removing the tag
'patch' from
The attachment Debdiff to fix this of this bug report has been
identified as being a patch in the form of a debdiff. The ubuntu-
sponsors team has been subscribed to the bug report so that they can
review and hopefully sponsor the debdiff. In the event that this is in
fact not a patch you can
Thanks Simon and Adam, what you suggest sounds reasonable.
Do you mind raising this as a bug against the debian package? (If you
do, I'll go ahead and do it).
** Changed in: libvirt (Ubuntu)
Status: Confirmed = Triaged
--
You received this bug notification because you are a member of
** Bug watch added: Debian Bug tracker #644457
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644457
** Also affects: libvirt (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644457
Importance: Unknown
Status: Unknown
--
You received this bug notification because
** Changed in: eucalyptus
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in Ubuntu.
https://bugs.launchpad.net/bugs/439410
Title:
Instances from large, fresh EMIs fail to start
** Changed in: eucalyptus
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in Ubuntu.
https://bugs.launchpad.net/bugs/384625
Title:
setting Buckets Path in admin interface is not
** Changed in: eucalyptus
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in Ubuntu.
https://bugs.launchpad.net/bugs/436276
Title:
Part of storage controller setup that should
Public bug reported:
Terminating an instance results in a traceback which appears to be
related to changes introduced in 2011.3-0ubuntu5 debian/patches
/backport-libvirt-console-pipe.patch. It seems nova cannot clean up the
instance console log upon termination. Should note that a seperate
** Attachment added: nova-compute.trace.log
https://bugs.launchpad.net/bugs/868897/+attachment/2516103/+files/nova-compute.trace.log
** Changed in: nova (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Closing the geany task since it's confirmed in #6 to be a Gtk+ bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/851383
Title:
geany crashed when trying to open a second file
To manage
Closing the geany task since it's confirmed in #6 to be a Gtk+ bug.
** Changed in: geany (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/851383
Title:
Hi Romain and thanks for reporting this bug:
You say this:
The problems comes from ALSA itself and not pulseaudio (aplay crackles
too).
aplay usually goes through pulseaudio as well, unless you specify. Did
you try aplay with the following command:
aplay -D plughw:Headset -c 2 -t sine
...and
Same problem here; been battling it for days. Might have randomness
elements to it?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/544469
Title:
iSight webcam on Macbook Pro does not work
To manage
N/A
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/442941
Title:
debconf failed to upgrade from 1.5.27ubuntu1 to 1.5.27ubuntu2: exit
status 128 - Use of uninitialized value $reply in scalar chomp
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mountall (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/578809
Title:
Public bug reported:
I don't really know how to describe this issue, please look at the
attached screen shots.
Gnome works fine on a couple of other computers. But on this one the top
menu is all corrupt and in strange colors.
I also noticed that there is a File menu etc. in the top left
** Attachment added: Screenshot at 2011-10-05 07:50:39.png
https://bugs.launchpad.net/bugs/868111/+attachment/2511432/+files/Screenshot%20at%202011-10-05%2007%3A50%3A39.png
--
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 861548 ***
https://bugs.launchpad.net/bugs/861548
Thank you for taking the time to report this crash and helping to make
Ubuntu better. This particular crash has already been reported and is a
duplicate of bug #861548, so is being marked as such. Please
*** This bug is a duplicate of bug 857738 ***
https://bugs.launchpad.net/bugs/857738
Thank you for taking the time to report this crash and helping to make
Ubuntu better. This particular crash has already been reported and is a
duplicate of bug #857738, so is being marked as such. Please
No. I could not solve the probleme and made a clean install of Kubuntu
11.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/832054
Title:
Could not calculate the upgrade (To Kubuntu 11.04)
To
Today I tested with latest updates but the problem is still present.
compiz:
Installed: 1:0.9.6+bzr20110929-0ubuntu3
Candidate: 1:0.9.6+bzr20110929-0ubuntu3
Version table:
*** 1:0.9.6+bzr20110929-0ubuntu3 0
500 http://archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages
Pada 05/10/11 11:26, Fabrice Coutadeur menulis:
Hi,
Given that we are very near from the release of Oneiric, why is this merge
required? According to the changelog, it doesn't seem to bring anything to
Ubuntu.
I would recommend to wait until the P-Series opens for development to upload
5.9.3 got released today. Maby we still can get this in Oneiric? Would
be nice ofcourse.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/726301
Title:
mission-control-5 crashed with SIGSEGV in
Hi Shang,
It looks like this issue might have been already resolved upstream.
Could you please try following the instructions here:
https://wiki.ubuntu.com/Audio/UpgradingAlsa/DKMS
...and see if it helps?
** Changed in: alsa-driver (Ubuntu)
Status: New = Incomplete
--
You received this
** Summary changed:
- multitouch doesn't work
+ [Acer W500] multitouch doesn't work
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/801988
Title:
[Acer W500] multitouch doesn't work
To manage
I've made the current fix available for natty and oneiric in
ppa:vanvugt/unity:
https://launchpad.net/~vanvugt/+archive/unity
The natty version has been well tested on a Macbook Air. The oneiric
version isn't yet tested.
Please try it and let me know how it goes for you, along with the
** Changed in: evolution
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/611983
Title:
[SRU] Evolution [Open Link In Browser] not working for new eBay email
hyperlinks
1 - 100 of 2342 matches
Mail list logo
