** Changed in: deja-dup
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1251628
Title:
Warn user if they've manually added remote URLs to
** Changed in: deja-dup
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1254291
Title:
Cant re-add rubbish bin to exclusions after removing
To manage
There is now a button to reset the folder preferences - should be in
46.0
** Changed in: deja-dup
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1254291
The preferences dialog now clearly indicates location rows that can’t be
backed up (inside the flatpak, or a remote URL). Will be released with
46.0
** Changed in: deja-dup
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Cleaning up old tickets - this string is from gvfs.
It has been translated in French since this ticket was filed:
https://gitlab.gnome.org/GNOME/gvfs/-/blob/43e5a1e3/po/fr.po#L2284
** Changed in: deja-dup
Status: Confirmed => Invalid
** Changed in: deja-dup (Ubuntu)
Status:
I think this is a report against Deja Dup - that string is an error
message we give if 'duplicity --version' doesn't actually give us a
parsable version string.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Interesting… that usually means that duplicity crashed on us or had some
other odd error when we asked it for its version.
But when you do it on the terminal, it’s fine…
Are you using the standard Ubuntu distro version of deja Dup (vs flatpak
or snap releases?)
--
You received this bug
Hmm, that's odd. That means... maybe there's a problem decrypting some
of your metadata, but you do have an unencrypted version of that
metadata in duplicity cache folders...?
But if you can restore stuff, that likely means you can decrypt the
latest actual data...
If you run "DEJA_DUP_DEBUG=1
Scarlett,
I must confess, I had forgotten about this report (it is now well over a
year since I posted it), with no real response.
At some time since then both bugs went away, I presumably when I
upgraded to 23.04 or 23.10, but I don't actually remember. At the time
I probably lived with the
** Changed in: deja-dup (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1933717
Title:
Backup messages in wrong language
To manage notifications
** Changed in: deja-dup (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1778638
Title:
duplicity stuck in splice() call on Bionic
To manage
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011355
** Bug watch added: Debian Bug tracker #1011355
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011355
** Also affects: deja-dup (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011355
Importance: Unknown
Looks like Debian stable is using 42.7 right now - should I file a bug
on the Debian side to track that too?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973816
Title:
Deja Dup's Google support
OK, I've made a little wiki page about this issue for distro maintainers
(no real new information, but it does have links to patches at the
bottom). The patches should cover all affected versions that Ubuntu
supports (40.7, 42.8, and 42.9).
https://wiki.gnome.org/Apps/DejaDup/GoogleAuthChange2022
Public bug reported:
Hello! I'm the maintainer of Deja Dup. I was recently made aware that
Google is removing an oauth workflow that Deja Dup uses, in September.
Here's their blog post about it:
https://developers.googleblog.com/2022/02/making-oauth-flows-safer.html
Here's the upstream bug
I'm not able to boot with the workaround provided in the final release
Jammy 22.04 or latest daily Ubuntu Jammy 22.04 ISO using VMWare
Technology Preview "Professional Version e.x.p (19431034)."
I've edited the grub config in the Ubuntu installer to include the
mentioned acpi=force option, but it
Deja Dup could maybe be smarter in the specific case of SMB mounts and
only try to mount the root folder...
If you switch your settings from:
Network Location: smb://1.2.3.4/backup/UbuntuBackup
Folder: MyMachineBackup
to:
Network Location: smb://1.2.3.4/backup
Folder:
I think that /tmp filename is a file that duplicity proceeds to throw
away. It copies files there, tries to unpack them, then cleans up after
itself (regardless of success). So that error message would be a lot
more useful if it indicated what the actual source file it had copied
from the storage
Public bug reported:
after update several weeks ago onboard wifi wont work.
trying to use a usb wifi adapter but not working as well.
the wifi router is fine it works with phones and tv.
and i dont know about lenux and dos commands.
** Affects: linux (Ubuntu)
Importance: Undecided
I tested this out against the python test cases in the Vitis-AI repo:
https://github.com/Xilinx/Vitis-AI/blob/v1.3.2/setup/mpsoc/VART/README.md
* resnet50_mt_py
* inception_v1_mt_py
Both were successful. I consider this bug fixed.
Packages tested:
vitis-ai-dnndk/focal-proposed,now
I tested this and it worked!
- Made an initial backup, not saving password.
- Backed up again, changing the password.
With the old version, I got an error at "verify the backup" step. But
the backup files did end up being written with the wrong password.
With the new version, it did not accept
It escaped my attention at the time, but Ubuntu 18.04 released with both
a version of duplicity that shows the new incremental-backups-also-have-
this-issue behavior (see my comment 22) and a release of deja-dup that
wasn't yet fixed to avoid it.
Which means that deja-dup in Ubuntu 18.04 is still
Hi Łukasz - Still see the amd64 packages here:
https://packages.ubuntu.com/search?suite=hirsute=amd64=names=xrt
Can these be removed as well?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1943564
*** This bug is a duplicate of bug 1933717 ***
https://bugs.launchpad.net/bugs/1933717
Hello and thank you for the report! Oddly enough, this is an Ubuntu
translation issue, where some German ended up sneaking into the English
translation. It’s fixed for the next release, but I guess they
** Changed in: linux (Ubuntu Eoan)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847340
Title:
ext4 journal recovery fails w/ data=journal + journal_checksum
** Summary changed:
- linux
+ bionic linux Ubuntu-4.15.0-155.162 fails to boot on Azure Standard_D48_v3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940564
Title:
bionic linux
Hello
I've upgrade to Ubuntu 21.04, the the issue still exists.
Kernel version: Linux 5.11.0-25-generic #27-Ubuntu SMP Fri Jul 9 23:06:29 UTC
2021 x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
As part of the installation, the XRT package should create the vendor-
specific /etc/OpenCL/vendor/xilinx.icd file. The contents of the file
should be:
libxilinxopencl.so
This provides support for the Installable Client Driver (ICD) model as
described here:
Interesting. Jesse, that might be due to
https://gitlab.com/duplicity/duplicity/-/merge_requests/31 which
rejiggered how `--exclude-if-present` checks files in order to avoid a
fatal error that occurred in some edge cases. That change was released
in 0.8.17.
Maybe we would need a smarter fix to
does this behavior persist using the 5.11.0-26.28 in proposed? And can
you confirm you didn't see this problem on 5.11.0-24? Thanks - Terry
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938221
Thanks for bringing this up @dann. This needs to be corrected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1935855
Title:
dbgsym contains no debug symbols
To manage notifications about this
*** This bug is a duplicate of bug 1934187 ***
https://bugs.launchpad.net/bugs/1934187
** This bug has been marked a duplicate of bug 1934187
lxd exec fails
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This looks to be an Ubuntu translation error. The current package of
language-pack-gnome-en-base has some German phrases in its en_GB
translations for deja-dup!
Looks like they were fixed in May in the Ubuntu translation sources:
informed on when this patch set will come into which kernel series,
which we've agreed to do. The intent of this bug is to block
application of the patch set until we get confirmation of Mellanox's
awareness.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Terry Rudd (terrykrudd
*** This bug is a duplicate of bug 1930733 ***
https://bugs.launchpad.net/bugs/1930733
** This bug is no longer a duplicate of bug 1930976
5.8.0-55 kernel issue with RTX 3080 on Nvidia drivers
** This bug has been marked a duplicate of bug 1930733
Kernel oops with the 460.80 and 465.27
*** This bug is a duplicate of bug 1930733 ***
https://bugs.launchpad.net/bugs/1930733
** This bug has been marked a duplicate of bug 1930733
Kernel oops with the 460.80 and 465.27 drivers when using DP, but not with
HDMI
--
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 1930733 ***
https://bugs.launchpad.net/bugs/1930733
** This bug is no longer a duplicate of bug 1930976
5.8.0-55 kernel issue with RTX 3080 on Nvidia drivers
** This bug has been marked a duplicate of bug 1930733
Kernel oops with the 460.80 and 465.27
*** This bug is a duplicate of bug 1930976 ***
https://bugs.launchpad.net/bugs/1930976
** This bug has been marked a duplicate of bug 1930976
5.8.0-55 kernel issue with RTX 3080 on Nvidia drivers
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
.
Terry
** Summary changed:
- After kernel upgrade to 5.8.0.58 my system would no longer boot.
+ After kernel upgrade to 5.8.0.55 my system would no longer boot.
** This bug has been marked a duplicate of bug 1930976
5.8.0-55 kernel issue with RTX 3080 on Nvidia drivers
--
You received this bug
I'm a little confused because I was under the impression that ml2/ovn
doesn't actually use RPC workers for anything. What is happening that
RPC requests end up calling into ml2/ovn code?
If it's needed, it's needed, but I don't like unconditionally setting up
connections for non-API workers
Discussed with Canonical team and decided we will not pursue this
update.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928714
Title:
Vitis AI 1.3.2 Release tag updated
To manage notifications
Public bug reported:
Vitis AI 1.3.2. was recently updated with a few minor bug fixes. While I
don't believe they affect the operation of any of our designs that will
be released with our initial Ubuntu image for ZU10x boards, I think it's
important to release with a consistent version that
Public bug reported:
During the course of the installation the installer crashed.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15.10
ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-43-generic x86_64
NonfreeKernelModules: zfs zunicode
Thanks eric-. I believe this came in via upstream stable commit
for the -49 kernel and has since been reverted. Will watch to see if
the same is true for others who've hit this issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Can you please try the 5.8.0-51 kernel from the -proposed PPA and let us
know if this issue resolves with the newer kernel?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1924624
Title:
after
This looks like a transient error, some issue with python3 on your
install?
But regardless, more recent releases of Ubuntu have deja-dup depend
directly on duplicity and gvfs-backends
** Project changed: deja-dup => deja-dup (Ubuntu)
** Changed in: deja-dup (Ubuntu)
Status: New => Fix
This issue also exists in 21.04 beta. Same solution works. It didn't
show up until today.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876282
Title:
libc++1 is kept back after upgrade to focal
Hi Mukesh,
4.4.0-83 is a very old kernel. Have you tried the latest proposed
kernel for 16.04, which is 4.4.0-203.235?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915699
Title:
Bluetooth
Sorry you were hit by this issue! But good news is that a fix is
available. It was caused by an interaction between Deja Dup and
duplicity when a single quote was followed by a space.
This was fixed upstream in duplicity 0.8.17 (and worked around in deja-
dup 42.5). Both those fixes are in Ubuntu
** Changed in: deja-dup (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/1915161
Title:
deja dup won't restore a folder where name contains apostrophe and
Public bug reported:
Just doing a release upgrade...
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: grub-efi-amd64-signed 1.142.10+2.04-1ubuntu26.8
ProcVersionSignature: Ubuntu 4.15.0-134.138-generic 4.15.18
Uname: Linux 4.15.0-134-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.14
Steve, I am adding this to our workflow to address
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912708
Title:
CONFIG_RANDOMIZE_BASE on ppc64el
To manage notifications about this bug go to:
Eric,
there has been a new signed shim since that bug was filed. Have you or
anyone retested with it?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1841202
Title:
during install kernel console
It seems that in at least 1 case, this condition arises with linux-
modules-extra installed so my suggestion above may not help
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1911352
Title:
Black
If anyone affected by this bug can still reproduce it in their
environments, I would like them to try installing linux-modules-extra
and rebooting to see if the issue clears. You will need to do this with
your 5.4 kernel.
Thanks in advance,
Terry
--
You received this bug notification because
Thank you Tamas. You are likely aware we don't plan to support 5.8.*
in 21.04 user space but we've very interested to make sure this issue is
not present in 20.10 (groovy). Have you tested with that user space?
Also, have you tried the 5.10 kernel in -proposed for 21.04? If you see
the same or
Yes Tamas. In other words, I believe you are confirming the only think
changing back and forth is the kernel version you are running. Thank you
for that.
--
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 1909005 ***
https://bugs.launchpad.net/bugs/1909005
** This bug has been marked a duplicate of bug 1909005
Ubuntu does not resume (wake up) from suspend
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Are you running the 5.8.0-33 kernel in the same 21.04 user space?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912188
Title:
Load growing continously
To manage notifications about this bug go
@Italo, have you had time to test Kai-Heng's suggestion?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1909017
Title:
bug when suspending the system does not wake up and freezes on black
screen
Andrew, we plan to address this in the Focal 5.8 hwe kernel and we're
going to be building a test kernel. We would really appreciate you
testing it since you have a reliable reproducer.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Daniel,
This isn't actually a kernel bug. I will watch these for a few days but
will mark them invalid if the 18.04 dual boot install worked. I just
don't want to erase information for 16.04 until the installer team has
some time to consider this.
--
You received this bug notification because
*** This bug is a duplicate of bug 1901904 ***
https://bugs.launchpad.net/bugs/1901904
** This bug has been marked a duplicate of bug 1901904
[SRU] virtualbox 6.1.10-dfsg-1~ubuntu1.20.04.1 ADT test failure with
linux-hwe-5.8 5.8.0-25.26~20.04.1
--
You received this bug notification
*** This bug is a duplicate of bug 1901904 ***
https://bugs.launchpad.net/bugs/1901904
** This bug has been marked a duplicate of bug 1901904
[SRU] virtualbox 6.1.10-dfsg-1~ubuntu1.20.04.1 ADT test failure with
linux-hwe-5.8 5.8.0-25.26~20.04.1
--
You received this bug notification
Thanks Jack,
I will go ahead then and mark this invalid
** Changed in: linux (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/1910588
Title:
rsync backup
** Changed in: linux (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/1910806
Title:
System hang - kernel 5.8.0-36
To manage notifications about this bug
Hi Jack.
I discussed this with other kernel engineers this morning and we also
felt this was looking more like a FW or hardware issue. I am anxious to
hear your results. Thanks for the detailed response.
Terry
--
You received this bug notification because you are a member of Ubuntu
Bugs
Jack, I just saw your message in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910806
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1910588
Title:
rsync backup hang
To manage notifications
Have you tested with 5.8.0-36?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1910588
Title:
rsync backup hang
To manage notifications about this bug go to:
Ben, can you tell us if it was 5.8.0-34 kernel or later?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1911352
Title:
Black screen on boot after 20.04 upgraded to kernel 5.8
To manage
Zhang, can you please include more detail and logs?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1910483
Title:
dkms and initramfs-tools dependent issue
To manage notifications about this bug go
Rohit or anyone affected by this bug, can you please see comment #3?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1909496
Title:
[i915] Blinking unlock screen
To manage notifications about this
There are a few bugs that seem related to this one. The Canonical
kernel team will be investigating this further. Thanks for the work on
this lotuspsychje.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
thanks Amir, I believe you were on vacation so really appreciate it
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1904848
Title:
Ubuntu 18.04- call trace in kernel buffer when unloading ib_ipoib
Robin, do you mind filing a new bug? Will be easier for me to dig into
what's not working for you, rather than adding on to this 2013 issue.
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Shuah Khan reported in IRC that she starting having problems with 4.14
only of the stable kernel after her upgrade to 20.04. 4.4 and 4.9 work
just fine. She followed up with 4.19, 5.4 and 5.9 kernel, with no
issue.
She suspects the issue is related to compress/decompress
I think the English word used is Utilities
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873238
Title:
Deja-dup icon is missing only runs from terminal
To manage notifications about this bug go
Oh that’s interesting yes. I’ll have to see how to get the quota info
from gvfs and apply it to our calculations. Thank you for the report!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906304
I ended up just adding this to my crontab to pull an updated copy once a
month.
# Update the pci id file
20 120 * * /usr/sbin/update-pciids
The easy solution might be to add a cron file to do something similar. A
cleaner solution would be to include it into it a dedicated package.
--
This is resolved now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1764896
Title:
System will not display using displayport from AMD GPU
To manage notifications about this bug go to:
Oh and I should have mentioned workarounds:
- give everyone execute permission on the offending folder
- install the snap version of duplicity
- install the snap (or flatpak) version of deja-dup
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
(Any one of those should work by itself)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905170
Title:
Impossible to create a full backup due to permission error on
/home/lost+found folder
To
This is a bug in a possible interaction between Deja Dup >= 42.1 and
Duplicity < 0.8.16.
Which means as of this writing it definitely affects 20.10, and may
affect 21.04 if Duplicity doesn't get bumped before release.
This was fixed in Duplicity by the following patch:
Were you using the snap package? There was a bug briefly in duplicity
that would have caused this error, but it is fixed now. Do you still see
this?
I don’t believe the bug was ever present in Ubuntu 20.04 itself.
** Changed in: deja-dup (Ubuntu)
Status: New => Incomplete
--
You
Amir and Heinz-werner, it would be helpful to get some test results on
this functionality in the Ubuntu 5.8 kernel in 20.10. Thanks in
advance.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894977
** Summary changed:
- vclib from ubuntu_k8s_unit_tests fail on Eoan 5.3 GCP / F-5.4-GCP
+ vclib from ubuntu_k8s_unit_tests fail on Focal-5.4-GCP
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1855809
** Changed in: linux-gcp (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1855808
Title:
cmd from ubuntu_k8s_unit_tests failed with Eoan-5.3 GCP
To manage
** Changed in: deja-dup (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1027514
Title:
Restore dialog becomes too huge when restoring too many files
To
** Changed in: deja-dup (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/953194
Title:
deja-dup attempts to backup "lost+found"
To manage
Latest versions show a notification that will bring the dialog open as
needed. (Or starting the app from the application launcher will also
show it.)
** Changed in: deja-dup (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
That UI has been redesigned and is a lot better now.
** Changed in: deja-dup (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1281675
Title:
The scheduling
Nikita, your issue actually looks a lot like something fixed in duplicity
0.8.16:
https://gitlab.com/duplicity/duplicity/-/commit/f6809e8a4e09b70138a0902434d8c88d3c4c8ccb
Try installing the snap version of deja-dup or duplicity, both of which
have the fix for this.
--
You received this bug
Yeah an sru should be fine — no dramatic changes in there, but plenty of
nice fixes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901340
Title:
Backup doesn't automatically start when drive is
Ah, OK. Maybe the previous problem with the snap was because the old
session monitor was still active? Odd.
But glad it worked now!
So yeah, looks like the fixes in 42.3 work for your case, and it's
possible the patches around encrypted & removable drives from 42.3 and
42.4 should be backported
Version 42.3 did fix an error with scheduled backups to encrypted
drives! I suspect that might be what you're hitting? Can you try the
snap and see if that fixes things? Might want to make a manual backup
first just to confirm everything is working.
snap install deja-dup --classic
sudo apt remove
500 http://us.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
100 /var/lib/dpkg/status
I also experienced the issue in the latest default kernel for Ubuntu, so
I downloaded one of the later stable ones:
Linux terry-pc 5.9.1-050901-generic #202010170731 SMP Sat Oct 17
07:42:59 UTC
This issue also exists in 20.10. The fix works as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876282
Title:
libc++1 is kept back after upgrade to focal
To manage notifications about this
HI Asavah,
I took your suggestion and modified it slightly.
sudo -s
do-release-upgrade -d (expected to fail)
cd /var/cache/apt/archives
dpkg --force-depends --force-breaks -i libnss-nis_3.1-0ubuntu4_amd64.deb
do-release-upgrade -d
It did allow the libnss-nis package to install. Afterwards,
Tested after 20.10 release. No improvement.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1899272
Title:
upgrade to 20.10 beta from 20.04 fails immediate configuration
To manage notifications
Public bug reported:
This problem shows up when using any update method (update-manager -d,
do-release-upgrade -d). The captured data shows an immediate-configure
error.
--
Fetched 0 B in 0s (0 B/s)
1 - 100 of 9681 matches
Mail list logo
