It seems that the change to support this would be minimal, see below.
All file writing during restore seems to be done by
util.py/copyfileobj()
Unless I'm very much mistaken, the following change would do sparse
files, _if_ (and only if) the target object is empty to begin with. If
it isn't, this
** Also affects: duplicity
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576051
Title:
Duplicity cannot handle sparse files efficiently
To manage
** Changed in: duplicity
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/1576051
Title:
Duplicity cannot handle sparse files efficiently
To manage notifications about
Can we get someone to fix this policy violation, please?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1701023
Title:
(on trusty) version 1.9-3ubuntu10.4 regression blocking boot
completion
To
Note: This behavior is in direct violation of the Debian documentation:
https://wiki.debian.org/NetworkConfiguration#Bringing_up_an_interface_without_an_IP_address
Specifies:
Note: If you create the VLAN interface only to put it into a bridge, there is
no need to define the VLAN interface
Public bug reported:
When upgrading from version 1.9-3ubuntu10.1, a previously working
machine can't successfully reboot completely.
ifup is hanging indefinitely, with this process structure (from "pstree
-a 1299"):
ifup,1299 -a
└─run-parts,1501 /etc/network/if-pre-up.d
└─bridge,1502
This is likely the root cause for
https://bugs.launchpad.net/bugs/1642710 (no automatic installation
possible on NVMe-only systems), which is not just wishlist, I think.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On the suggested fix: Why even keep the printf? Why not switch to just print?
I'm not a C expert by any means, but shouldn't
printf("%s", )
be completely equivalent to
print()
With the exception that the second one should be very slightly less overhead?
--
You received this bug notification
*** This bug is a security vulnerability ***
Public security bug reported:
Upstream fix is (apparently):
https://secure.ucc.asn.au/hg/dropbear/rev/b66a483f3dcb
** Affects: dropbear (Ubuntu)
Importance: Undecided
Status: New
** Information type changed from Private Security to
I can confirm that 4.3-7ubuntu1.6 fixes the issue.
While the reproduction steps from the Debian bug report (enable revert-
all-at-newline, run bash, "echo something"+RETURN, CTRL-P, CTRL-U,
CTRL-N, ENTER) reliably crash 4.3-7unbuntu1.5, they don't crash
4.3-7ubuntu1.6
--
You received this bug
So what can be done to get a version with this fix into Trusty?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1422795
Title:
bash crashes often if inputrc contains revert-all-at-newline
To manage
Is there a chance to have this fgix backported to Trusty? It affects
some of our users.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/890784
Title:
Gnome-terminal continues to show outline cursor
Ping.
The test kernel seems to fix this. Could it be pushed to Trusty?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/994931
Title:
Altering use_tempaddr drops all IPv6 addresses
To manage
Any chance this could be fixed in Trusty?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/994931
Title:
Altering use_tempaddr drops all IPv6 addresses
To manage notifications about this bug go to:
** Tags added: patch
** Tags added: patch-accepted-debian
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1422795
Title:
bash crashes often if inputrc contains revert-all-at-newline
To manage
Actually, Markus tested Trusty, not Utopic:
3.16.0-38-generic #52~14.04.1-Ubuntu SMP Fri May 8 09:43:57 UTC 2015 x86_64
14.04.1 is the Trusty version, not Utopic. Therefor adding
verification-needed-utopic back and adding verification-done-trusty.
** Tags removed: verification-done-utopic
I currently don't have two machines anymore, so I can't test. Sorry.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1395717
Title:
synergy: hover doesn't work anymore in Chrome
To manage
Note that the odd origin is due to the way we mirror. The package is the
(unmodified) 4.3-7ubuntu1.5 package as distributed in Ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1422795
Title:
Public bug reported:
Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747341
The Debian bug includes complete reproduction case. Basically:
with .inputrc containing
set revert-all-at-newline On
Go back in the commandline history, edit a command, then submit a different
command (may
Public bug reported:
(Taken from the relevant Debian bug:)
Since Chrome 31, synergy has broken mouse hover if Chrome uses hardware
acceleration.
The upstream bug [1] has a patch to work around the X11 bug that causes
this in comment #65.
Multiple people has confirmed that the patch
Any chance we could get an SRU with the fix in?
As far as I can tell, this isn't really Fix Released, as the fix is not in the
distribution the bug was targeted for (1404 LTS).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Seth: Could you build your test kernel again from the current Trusty kernel
(3.13.0-35.62, if I'm not mistaken)?
I would love to (have someone) test this, but I wouldn't want to go back to
-32.57
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Contrary to my initial thought, it seems this should actually get
assigned to pythondialog.
Running the present-dialog.py quoted above, I can reproduce.
Running this commandline (which should be what python-dialog is
calling), I can't reproduce. Well, I can reproduce the failure, but also
get a
*** This bug is a duplicate of bug 1319941 ***
https://bugs.launchpad.net/bugs/1319941
** This bug has been marked a duplicate of bug 1319941
libreoffice draw / impress crash if user service publishing is disabled in
avahi
--
You received this bug notification because you are a member
So the bug I uploaded the crash report as is
https://bugs.launchpad.net/bugs/1328908
However, Christopher seems to think it is not a duplicate of this bug, while it
is an exact reproduction of the case described here. Without explanation, he
removes the marked as duplicate from the other bug
For the record, I think it is a duplicate and exact reproduction of the
case described in:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1319941
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Could you please at least comment why you think this is not a duplicate
of the bug I linked it to?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1328908
Title:
libreoffice draw / impress crash if
Just as a note: Procedure to reproduce:
Locate the line
#disable-user-service-publishing=no
in /etc/avahi/avahi-daemon.conf and change it to
disable-user-service-publishing=yes
restart the avahi-daemon service (It might read the config file upon
change, but I didn't check)
Try to start Impress
So I was able to reproduce on a freshly installed Ubuntu Trusty, It
seems whoopsie on said machine has trouble uploading the crash data, so
re-attaching the .crash file here.
** Attachment added: .crash file from apport
Christopher M. Penalver: Please read my report:
1) reporting it like you suggested doesn't work. I can't say why except that
this shows up in syslog:
Jun 11 04:54:34 ubuntu whoopsie[1323]: Sent; server replied with: No error
Jun 11 04:54:34 ubuntu whoopsie[1323]: Response code: 503
Jun 11
Anyway, to add some of the information that is requested on the
libreoffice bug mangling page:
$ apt-cache policy libreoffice-impress libreoffice-draw
libreoffice-impress:
Installed: 1:4.2.3~rc3-0ubuntu2
Candidate: 1:4.2.3~rc3-0ubuntu2
Version table:
*** 1:4.2.3~rc3-0ubuntu2 0
*** This bug is a duplicate of bug 1319941 ***
https://bugs.launchpad.net/bugs/1319941
Public bug reported:
Crash report for bug #1319941
ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: libreoffice-core 1:4.2.3~rc3-0ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
For some reason, the upload finally worked. See the bug marked as a
duplicate of this one for the crash report.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1319941
Title:
libreoffice draw /
Would there be a chance to create a -ima flavor of the kernel instead of
enabling it in the stock kernel flavor? This should allow for it to go
into Trusty and into Saucy as a SRU, if I understand correctly, since it
provides a new binary package instead of modifying an existing one (no
regression
This was previously marked incomplete, then expired. However, all the
information that is available is in the bug. Here is a summary again:
dhclient stops trying to renew a lease if a previous renewal failed (due
to server being unavailable).
See #6 for all the logs available. See how the client
The symlink restrictions are solely in the kernel, which people might have to
replace for various reasons. In other words: It might not be a security issue
on plain - unmodified - Ubuntu, but it is still a security issue.
Just sayin'
--
You received this bug notification because you are a
I will see if I can dig up the logs, but this happened a while ago and I only
got around to filing this bug now. Anyway, what happened on dozens of machines
(might have been hundreds):
Machine has a working ethernet connection (to the switch)
The network itself works reliably for the whole time.
Public bug reported:
Present in the Precise version (0.7~beta2ubuntu8) at least:
ifupdown is hardcoded to call dhclient with -1, which causes it to exit on the
first failure.
This can happen in two ways:
1) Failure to bring up the interface if the dhcp server doesn't respond in time
(default
Well, that would cover the first failure mode I described, but we experience
the second one.
I don't see any workaround, apart from removing the -1 from the dhclient
options.
I'm sorry, but this means that a _part_ of my report might be invalid
(though we think we saw that issue), but the other
Can this fix please be made available in Precise? Precise as of today
seems to carry 23.1+1=4ubuntu7, which doesn't incorporate this fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/941790
Title:
According to #13, this was fixed in September 2010, but the fixed
package version (1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu20) is
still not available in Lucid (only somewhere in lucid-proposed). Any
chance to get the fix into lucid?
--
You received this bug notification because you are a
41 matches
Mail list logo
