** Branch linked: lp:ubuntu/tuxguitar
** Branch linked: lp:ubuntu/azureus
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to gwt in Ubuntu.
https://bugs.launchpad.net/bugs/740815
Title:
[FFe] Updates to enable us to drop xulrunner from
couchdb + libmozjs is in my PPA now
** Changed in: couchdb (Ubuntu)
Status: In Progress => Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to gwt in Ubuntu.
https://bugs.launchpad.net/bugs/740815
Title:
[FFe] Updates to
Also just affected me on upgrade from karmic to lucid, using mysql. This
just cost me a couple of hours, so I definitely vote in favor of having
this handled properly during upgrade, especially as it affects LTS->LTS
upgrades.
--
You received this bug notification because you are a member of Ubun
This is a legacy behavior in QEMU. There are a number of legitimate use
cases where a user may only have read access to an image and as long as
that image is mounted read-only, everything will work okay.
Virtio and SCSI will expose the read-only attribute to the guest so it
should be very obvious
** Description changed:
Binary package hint: qemu
- $ kvm-img create -f qcow2 disks/t.img 4000M
- Formatting 'disks/t.img', fmt=qcow2, size=4096000 kB
- qemu-img: Error while formatting
+ $ kvm-img create -f qcow2 disks/t.img 4000M
+ Formatting 'disks/t.img', fmt=qcow2, size=4096000
It was apt-get. It hung for a while so I cancelled it with ctrl+c I
think. I'm not sure that triggered the crash.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to beautifulsoup in Ubuntu.
https://bugs.launchpad.net/bugs/740666
Title:
I think what it means that, if the file permission for the disk image in
host OS is read only for the user running qemu, then it is not saying
that clearly. May be qemu should just exit as soon as it sees that image
is read only. I am not sure if in some kind of mode it is possible to
run a VM with
Yeah it was more as confirmation. I'm going to test a patched libgcrypt
(comment #73) next.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libnss-ldap in Ubuntu.
https://bugs.launchpad.net/bugs/423252
Title:
NSS using LDAP+SSL brea
Quoting Phillip Susi (ps...@cfl.rr.com):
> I agree that deviating from upstream should be avoided without good
> cause, but by using this switch, Debian is deviating from upstream. Are
> you aware of a good reason for this?
No, I'm not.
--
You received this bug notification because you are a me
Quoting Phillip Susi (ps...@cfl.rr.com):
> I'll just drop the part about the -Q then, rather than file a new bug
> about the other parts, especially since I already have it linked to the
> debian bug about the rest.
That works :)
> Still the rules trying to match multipath and dmraid and run kpar
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/23/2011 09:18 PM, Phillip Susi wrote:
> Also as I mentioned in bug #737027, the dmraid part of this rule is
> broken due to case mismatch. I don't have a multipath installation to
> check, but I suspect it suffers from the same problem and so th
I'll just drop the part about the -Q then, rather than file a new bug
about the other parts, especially since I already have it linked to the
debian bug about the rest.
Still the rules trying to match multipath and dmraid and run kpartx are
broken. The one for dmraid should not be there at all, a
Thanks for reporting this bug and helping to make Ubuntu better.
This is interesting because the DpkgTerminalLog.gz doesn't give
indication of any such failure. Can you please explain exactly how you
installed this? (Did you use apt-get on the command line, or synaptic,
or software center?)
**
Also as I mentioned in bug #737027, the dmraid part of this rule is
broken due to case mismatch. I don't have a multipath installation to
check, but I suspect it suffers from the same problem and so the rule
isn't run at all anyway.
--
You received this bug notification because you are a member
I agree that deviating from upstream should be avoided without good
cause, but by using this switch, Debian is deviating from upstream. Are
you aware of a good reason for this?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-
** Changed in: multipath-tools (Ubuntu)
Assignee: Serge Hallyn (serge-hallyn) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/644481
Title:
95-kpartx.rul
*** This bug is a duplicate of bug 644481 ***
https://bugs.launchpad.net/bugs/644481
Ah, I see. We didn't SRU because it did not seem to cause any
regression. Is this really preventing it from working for you? If so,
we should SRU bug 644481. I will mark this bug a dup of that one.
Please
** Changed in: samba (Ubuntu)
Assignee: (unassigned) => Clint Byrum (clint-fewbar)
** Changed in: samba (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.laun
@Phillip,
thanks for your input. The point of this bug was to stay closer to what
Debian does. Please feel free to open a bug with Debian and, if they
change their policy, we will follow suit.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscr
This bug was fixed in the package mozvoikko -
1.9.0~svn20101114r3591-0ubuntu3
---
mozvoikko (1.9.0~svn20101114r3591-0ubuntu3) natty; urgency=low
* debian/control: Drop hopelessly outdated Vcs-Bzr, using
lp:ubuntu/mozvoikko now.
* debian/control: Move from xulrunner-dev to fire
I believe this change is incorrect and should be reversed. The -p
switch should not be used at all and kpartx should use its usual rule of
adding 'p' when the previous character is a digit, as this has been the
rule always used on Linux for forming partition names.
--
You received this bug notif
The modprobe was added in Ubuntu, but the dmraid- is also there in
debian. It looks like it has been changed to a lower case -q in Natty,
but I'm still running Maverick.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools i
Taking mozvoikko
** Changed in: mozvoikko (Ubuntu)
Status: Confirmed => In Progress
** Changed in: mozvoikko (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to gwt in Ubu
I also just saw it for the first time when starting chromium, kernel
2.6.35-280generic 64bit.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vsftpd in Ubuntu.
https://bugs.launchpad.net/bugs/590537
Title:
"lo: Disabled Privacy Exten
This bug was fixed in the package gtk-vnc - 0.4.3-0ubuntu3
---
gtk-vnc (0.4.3-0ubuntu3) natty; urgency=low
* Actually update to 0.4.3, the previous version forgot --merge-upstream and
thus the debian diff reverted all upstream changes.
* debian/control: Build against firefox-d
Reopening xulrunner-1.9.2 until it can safely be demoted. Currently this
is still held back by atk1.0 arch skew, which causes a lot of FTBFS on
armel/powerpc. I bumped its build score, but that will take some
retries.
** Changed in: xulrunner-1.9.2 (Ubuntu)
Status: Fix Released => Fix Commi
g-p-e demoted to universe.
** Changed in: gnome-python-extras (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to gwt in Ubuntu.
https://bugs.launchpad.net/bugs/740815
Title:
[FFe] U
** Branch linked: lp:ubuntu/swt-gtk
** Branch linked: lp:ubuntu/gwt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to gwt in Ubuntu.
https://bugs.launchpad.net/bugs/740815
Title:
[FFe] Updates to enable us to drop xulrunner from main
There's nothing keeping xulrunner-1.9.2 in main now
** Changed in: xulrunner-1.9.2 (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: gwt (Ubuntu)
Status: New => Fix Released
** Changed in: gwt (Ubuntu)
Assignee: (unassigned) => Chris Coulson (chrisccoulson)
--
You re
Here you go:
ubuntu@cempedak:/var/log$ ~/getifaddrs
INTERFACE=lo SCRUBBEDINTERFACE=lo ADDR=127.0.0.1
INTERFACE=eth0:metadata SCRUBBEDINTERFACE=eth0 ADDR=169.254.169.254
INTERFACE=eth0 SCRUBBEDINTERFACE=eth0 ADDR=10.55.55.2
INTERFACE=eth0:priv SCRUBBEDINTERFACE=eth0 ADDR=172.19.1.1
INTERFACE=eth0:
This bug was fixed in the package swt-gtk - 3.6.2-0ubuntu1
---
swt-gtk (3.6.2-0ubuntu1) natty; urgency=low
* New upstream release v3.6.2 (LP: #740815)
- mass rename 3.5 => 3.6
* Refresh patches:
- update debian/patches/64/arch64.diff
- update debian/patches/common/01-m
** Also affects: gwt (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to gwt in Ubuntu.
https://bugs.launchpad.net/bugs/740815
Title:
[FFe] Updates to enable us to drop xulrunner from
** Changed in: autofs (Ubuntu)
Importance: Undecided => Medium
** Changed in: autofs (Ubuntu)
Assignee: (unassigned) => Clint Byrum (clint-fewbar)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to autofs in Ubuntu.
https://bugs.l
** Changed in: autofs (Ubuntu)
Importance: Undecided => Medium
** Changed in: autofs (Ubuntu)
Status: New => Confirmed
** Changed in: autofs (Ubuntu)
Assignee: (unassigned) => Clint Byrum (clint-fewbar)
--
You received this bug notification because you are a member of Ubuntu
Serv
Thanks for reporting this bug and helping to make Ubuntu better.
Debian has actually never had this rule. It was added in Ubuntu to
avoid the need for the multipath-tools-boot script.
The '-Q' option has been fixed some time ago. What release are you on?
** Changed in: multipath-tools (Ubuntu)
Hi kwagga,
Is this a recent problem or does it happens since you have been using
Ubuntu 10.10?
If this problem is recent, so I suggest you yo recover your LINUX with
any IMAGE RECOVERY program (dd or CLONEZILLA or anything related) if you
have an image of it...
MORE INFO: I also use Ubuntu 10.10
On Wed, Mar 23, 2011 at 08:35:56PM -, Peter Matulis wrote:
> Building the openldap source with openssl instead of gnutls libraries
> and installing the resulting libldap package works here.
Yes, but that results in combinations of software that are not
redistributable in the archive because th
Hi Andrè,
Thank you for your comment, however, I do not agree that recovering a
whole system image, is a solution, nor a workaround.
In my case, the Windows 7 clients never changed, the ubuntu
machine/SAMBA installation did. The problem is also not isolated to one
or two clients, but all of them,
Building the openldap source with openssl instead of gnutls libraries
and installing the resulting libldap package works here.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libnss-ldap in Ubuntu.
https://bugs.launchpad.net/bugs/423252
Please see the last comment for a WORKAROUND to this issue...
** Changed in: samba (Ubuntu)
Status: Incomplete => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/731
PROBLEM SOLVED:
Problem Solved... I recovered my Windows 7 Ultimate image (with Norton
Ghost 15) to the problematic Windows 7 Ultimate PC and now I can connect
it... Surprisingly I could access it via my Windows 7 Ultimate before
this recovery, but I couldn't in my Linux.. This was probably caused
As I wrote in my initial report:
"The message should at least propose to logout / login to complete the
installation, or the installation post-install scripts should warn / force
this. Ideally this should not be necessary so we have the best user experience."
Right after installation is when I w
In /etc/apparmor.d/abstractions:
Using libvirt-qemu and add /usr/share/seabios/** r, on row 59 (after
/usr/share/vgabios/** r,)
Restart apparmor and virsh!
In /var/log/syslog:
With /usr/share/seabios/** r, in /etc/appamor.d/abstractions/libvirt-
qemu:
Mar 23 19:36:24 node kernel: [13419.727042
On 23 mrt 2011 the next happend:
It is in qemu-kvm: 0.12.5+noroms-0ubuntu7.1
/usr/share/qemu/@bios.bin is symlinked to /usr/share/seabios/bios.bin
Using seabios version 0.6.0-0ubuntu1
Log in /var/log/libvirt/qemu/ give me:
LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/
** Changed in: openvpn (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openvpn in Ubuntu.
https://bugs.launchpad.net/bugs/627973
Title:
Assertion failed at socket.c:629
--
Ubuntu-server-b
It seems, that this is not fixed in 10.04. We need this fixed in LTS.
# dpkg -l |grep squid
ii squid
2.7.STABLE7-1ubuntu12.2 Internet object cache (WWW
proxy cache)
ii squid-common
File in question is /etc/init/smbd.conf.
Original:
<<
description "SMB/CIFS File Server"
author "Steve Langasek "
start on local-filesystems
stop on runlevel [!2345]
respawn
pre-start script
RUN_MODE="daemons"
[ -r /etc/default/samba
Public bug reported:
Binary package hint: samba
The upstart script smb.conf should not only wait for the local-
filesystems event, but also for the network up event (like its done for
the nmbd.conf file which is also part of the samba package).
** Affects: samba (Ubuntu)
Importance: Undecid
48 matches
Mail list logo