In the original bug report I stated that:
> On Ubuntu 20.04 (development branch), as of today, Additional Drivers
> (software-properties-gtk 0.98.6) reports that the device "Intel
> Corporation: Wireless-AC 9260" is not working, and suggests using a
> manually installed driver (cf. screenshot).
A
Can confirm that Ryan's CMake code in comment #4 works around this issue
in Ubuntu 20.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1805173
Title:
GeographicLib cmake file in wrong place
To man
Thanks for the context! It makes sense.
Can someone with adequate rights please mark this as Won't Fix, to close
the report? Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1810517
Title:
re-
Although the security vulnerability in GhostScript that led to this
restriction on converting to and from PostScript and PDF has been
addressed in version 9.24, this restriction remains in place in at least
Ubuntu and Gentoo, and an attempt to remove it in Gentoo has been
stopped, apparently out of
** Information type changed from Public to Public Security
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1810517
Title:
re-enable GhostScript in ImageMagick
To manage notifications about this bug g
Issue reported upstream and bug watch added
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878109
Title:
Certain features in the Sharing panel fail with D-Bus related messages
when gnome-control-c
** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #999
https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/999
** Also affects: gnome-control-center via
https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/999
Importance: Unknown
Status: Unkn
Here is another user reporting the same GDBus errors when trying to
enable Screen Sharing on Ubuntu Server 20.04, if I understand correctly:
https://askubuntu.com/questions/1238329
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
Public bug reported:
When I run gnome-control-center (1:3.36.1-1ubuntu5) on a remote Ubuntu
20.04 host over ssh -X, trying to enable Screen Sharing (VNC) or Media
Sharing in the Sharing panel (*) fails with the following D-Bus related
messages on the standard error:
--
Description updated to reflect that this issue is not specific to a
particular Intel wireless card. A number of different cards are
concerned.
** Summary changed:
- software-properties-gtk erroneously reports that Intel Wireless-AC 9260
device is not working
+ software-properties-gtk erroneously
Hi Rip,
> Three fingers results in a right-click now for whatever
> reason. I have the appropriate settings enabled in KDE
> (I haven't changed them).
>
> Middle click works sometimes after restarting the device
> via xinput, but this is very rare.
If your three-finger taps are inconsistent (some
** Attachment added: "xinput --list"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1877798/+attachment/5369254/+files/xinput--list.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
** Attachment added: "xinput --list-props 13"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1877798/+attachment/5369255/+files/xinput--list-props13.txt
** Description changed:
I'm trying to switch from the "fingers" click-method to the "areas"
click-method, be
Public bug reported:
I'm trying to switch from the "fingers" click-method to the "areas"
click-method, because tapping with three fingers is awkward and I find
that my three-fingers taps are rarely registered as such.
* "fingers": single-finger tap for a click, two-finger tap for a right
click,
Indeed! Thank you for pointing that out. I also found
https://gitlab.gnome.org/GNOME/gnome-screenshot/-/issues/82 and linked
issues and merge requests, for additional context.
So the option to include/remove-border is removed from the upstream GUI
and so are the border effects. The CLI isn't updat
It appears to be an upstream issue, as the only Ubuntu patches in gnome-
screenshot 3.36.0 are related to:
* Unity support
* Disabling the possibility of taking a screenshot of a window or an area by
right-clicking on gnome-screenshot's desktop icon, because this feature doesn't
work in Wayland
** Attachment added: "With --remove-border"
https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1864539/+attachment/5367066/+files/remove-border.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
I can confirm this bug. I have updated the bug report with more precise
information, and I'm adding additional screenshots to demonstrate the
issue.
Additionally, I've noted that:
* There is no difference between --include-border and --remove-border:
the window border is included in the screensho
** Attachment added: "With --include-border and --border-effect=none"
https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1864539/+attachment/5367064/+files/include-border-and-no-border-effect.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Attachment added: "With --include-border and --border-effect=shadow"
https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1864539/+attachment/5367065/+files/include-border-and-shadow-border-effect.png
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Description changed:
- Screenshot tool inserts corrupt border area.
+ When taking a window screenshot with gnome-screenshot in 19.10 and
+ 20.04, a 20 to 25 pixel wide area of transparent padding (alpha) is
+ added around the screenshot.
- This also applies to Ubuntu 20.04 daily build.
+ See
** Summary changed:
- screenshot tool inserts corrupt border area
+ gnome-screenshot adds unnecessary transparent padding around window
screenshots
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/18645
*** This bug is a duplicate of bug 1872258 ***
https://bugs.launchpad.net/bugs/1872258
Jonathan:
Actually that sounds like a question for the update-manager developers,
so I've asked it there and subscribed you to it:
https://answers.launchpad.net/ubuntu/+source/update-
manager/+question/6902
Hi Jonathan and Dan:
> I don't think either apt nor snap auto-updates will handle this.
I don't think so either, and nor will manual snap updates ("snap
refresh" command).
My assumption is that deb-to-snap and snap-to-deb transitions are
limited to development releases. It would be very surprisi
Fixed by update-manager version 1:20.04.6 in bug 1872958
** Package changed: gnome-software (Ubuntu) => update-manager (Ubuntu)
** Changed in: update-manager (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
> Updates installed snap-store snap and uninstalled ubuntu-software
This is normal behavior, unless you have manually installed the "gnome-
software" package. The Ubuntu Software application on 20.04 is now
provided by the "snap-store" snap instead of the "gnome-software"
package. More info in htt
Hi Jonathan and Dan:
> I am not sure what you mean. There is no "snap-store" deb on my
> 20.04 system, nor does "apt search snap-store" yield any results.
It's a snap application, which you'll see in the output of the "snap
list" command if it is installed. It provides the Ubuntu Software
applica
With the replacement of gnome-software by snap-store in 20.04, this bug
is no longer apparent. Only users who manually (re-)install gnome-
software will see it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
Just ran update-manager and can confirm that the fix works perfectly.
The gnome-{calculator,logs,characters} snaps were removed, leaving their
deb equivalents. The snap-store was installed, and the gnome-software
deb was removed.
Thanks a lot!
--
You received this bug notification because you ar
Thanks a lot for the work Marcus, and Iain for reviewing, Gunnar for
translating! I look forward to try that out.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868409
Title:
[FFe] gnome-{calculator
Please disregard my previous comment. Looking at the code, I realize
that the maintainer packaged the upstream gnome-software "3.36.0" tag,
not the "gnome-3-36" branch, which makes a lot more sense indeed.
So even though the fix is made upstream, it is NOT YET released, and
therefore not packaged
The fix was made upstream on Mar 24 [1], released as part of gnome-
software 3.36 on Apr 3 [2], which was packaged for Ubuntu today Apr 6
[3]. I'd say it's just a matter of hours before it's available in the
repository :)
[1]
https://gitlab.gnome.org/GNOME/gnome-software/-/commit/bb7f58f5f8838185
** Bug watch added: gitlab.gnome.org/GNOME/nautilus/issues #117
https://gitlab.gnome.org/GNOME/nautilus/issues/117
** Also affects: nautilus via
https://gitlab.gnome.org/GNOME/nautilus/issues/117
Importance: Unknown
Status: Unknown
--
You received this bug notification because yo
Thanks for the insight Brian. I indeed rarely use the graphical update
manager. I'm starting to suspect I should manually install the snap-
store and uninstall the gnome-{calculator,logs,characters} snaps to get
in sync with the development release.
** Also affects: gnome-logs (Ubuntu)
Importan
The bug is fixed in gedit-plugins 3.36.1, and therefore in Ubuntu 20.04
Focal Fossa which has 3.36.2 at the moment. Previous releases are not
affected by this bug.
** Changed in: gedit-plugins (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you
This bug is still present because the change that Matthias did was
unintentionally undone the following week. So it was not shipped as it
should have been, as part of gnome-software 3.35.91, which is the
current version in Ubuntu. I have signaled this issue upstream.
--
You received this bug noti
Public bug reported:
I'm trialing the development release of Ubuntu 20.04, installed in
December and kept up-to-date by regularly running apt full-upgrade.
I understand from [1] that 20.04 will ship
gnome-{calculator,logs,characters} as APT packages rather than snap
apps, and gnome-software as a
A fix has been committed upstream and is now part of the new release for
gedit-plugins, 3.36.1. How does it work for it to enter Ubuntu, does it
need to enter Debian first?
(@Reinhard you can also edit keys using the command-line gsettings tool,
e.g. "gsettings reset org.gnome.gedit.plugins active
Merge request submitted by an upstream developer
** Changed in: gedit-plugins (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1866565
Title:
Enabling th
** Attachment removed: "Dependencies.txt"
https://bugs.launchpad.net/gedit-plugins/+bug/1866565/+attachment/5334708/+files/Dependencies.txt
** Attachment removed: "Disassembly.txt"
https://bugs.launchpad.net/gedit-plugins/+bug/1866565/+attachment/5334709/+files/Disassembly.txt
** Attachme
** Attachment added: "lsmod.txt"
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1859308/+attachment/5319316/+files/lsmod.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/185930
** Attachment added: "*9260*.txt"
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1859308/+attachment/5319318/+files/%2A9260%2A.txt
** Description changed:
On Ubuntu 20.04 (development branch), as of today, Additional Drivers
(software-properties-gtk 0.98.6) reports tha
In case it is relevant, note that I am starting the kernel with the
option "pci=nommconf" to work around an issue with my PCIe SSD.
** Attachment added: "dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1859308/+attachment/5319314/+files/dmesg.txt
--
You received
** Attachment added: "lshw.txt"
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1859308/+attachment/5319315/+files/lshw.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1859308
** Attachment added: "lspci -v.txt"
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1859308/+attachment/5319317/+files/lspci%20-v.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
Public bug reported:
On Ubuntu 20.04 (development branch), as of today, Additional Drivers
(software-properties-gtk 0.98.6) reports that the device "Intel
Corporation: Wireless-AC 9260" is not working, and suggests using a
manually installed driver (cf. screenshot).
However the device is working
*** This bug is a duplicate of bug 1832087 ***
https://bugs.launchpad.net/bugs/1832087
** This bug has been marked a duplicate of bug 1832087
Intel WIRELESS-AC 9260 (2526:0010) Wi-Fi doesn't work on kernel > 5.0.0-16
--
You received this bug notification because you are a member of Ubuntu
I can also report the same behavior, on a Clevo laptop running Ubuntu
20.04 (development version), kernel 5.3.0-24. Clevo does not currently
provide BIOS updates for this model, and it is unlikely that they ever
will.
The error is as reported by the OP, and repeats several times per second
on the
Ah, OK, thanks. No news since 2018-08 then - I was hoping the GNOME
GitLab would have something new :(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1685754
Title:
gnome-terminal unduly forces umask
Does anyone know where this bug is being tracked upstream now? GNOME has
migrated from Bugzilla to GitLab, and I haven't been able to find the
GitLab version of the Bugzilla bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
Fair point.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1648676
Title:
package ttf-mscorefonts-installer 3.4+nmu1ubuntu2 failed to
install/upgrade: package is in a very bad inconsistent state; y
Sounds right. I just assumed that there wasn't any users of releases <
Trusty any more, as all those releases are EOL. But actually there may
still be, indeed.
Bug should stay Confirmed until Trusty itself is EOL.
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
I set it to incomplete because the original reporter (or anyone else
affected by this problem) hasn't replied to my comment #2 requesting
more information (or hasn't brought up any additional information that
might help understanding the bug's cause).
This is standard practice (AFAIK) and sets old
Still affects xorg-lts-trusty for the users of releases < Trusty LTS,
but all of those releases e.g. Precise LTS are EOL now.
There is therefore no point in fixing this package, it won't be
installed by anybody any more.
--
You received this bug notification because you are a member of Ubuntu
Bu
** Changed in: msttcorefonts (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1648676
Title:
package ttf-mscorefonts-installer 3.4+nmu1ubuntu2 failed to
** Description changed:
[Symptoms]
When installing or updating the package ttf-mscorefonts-installer in
Ubuntu 16.04 or 16.10, an error message appears in a GUI window,
indicating "failure to download extra data files" (the fonts themselves)
"after package installation" (the package i
@Greg:
> 500 Bad redirection (path)
> which I have not seen listed here before - is this a new issue?
Possibly. I have not seen this error before either, in relation to this
bug. Just to be sure, can you please make sure that there aren't any
font-related partial downloads in /var/lib/update-noti
Awesome, thanks for weighting in Kenneth.
I've set the status to "Invalid" (not a bug) for deja-dup since the bug
was in duplicity.
** No longer affects: deja-dup
** Changed in: deja-dup (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member
*** This bug is a duplicate of bug 989750 ***
https://bugs.launchpad.net/bugs/989750
** This bug has been marked a duplicate of bug 989750
repeatedly asks for encryption password when backing up, even though
"remember password" is ticked
--
You received this bug notification because you
@Joseph: When Vej wrote "the first backup", I think he meant "a full
backup" (as opposed to an incremental backup), not the actual first
backup of your documents.
You can force a full backup by backing up to a new location, e.g. a
different folder on the server/disk that you are backing up to. Don
Added this bug to the Duplicity project, as it looks more like a bug in
Duplicity than a bug in Déjà-Dup, judging from the currently available
log files.
Also it's worth noticing that the GPG error reported by Joseph Hedgcorth
in comment 24 is not the same as the GPG error reported by Mathias Bink
Status changed to "Confirmed" because some users are still affected, on
recent Ubuntu releases.
We still don't have enough information for triaging though. Everyone
affected, please provide the full log when replicating the problem, not
just the GPG error:
$ DEJA_DUP_DEBUG=1 deja-dup --backup > d
** Changed in: deja-dup (Ubuntu)
Status: Expired => Confirmed
** Tags removed: amd64 oneiric running-unity
** Tags added: xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/989750
Title:
r
@aaronfranke:
The fix has been published long ago and nobody has this issue any more.
Please read this bug's updated description for all the information, and
please report details here if you see something the description doesn't
mention.
--
You received this bug notification because you are a
** Changed in: deja-dup (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1685294
Title:
Deja-dup won't run backup in Xubuntu 17.04
To manage notifications abo
I'm converting this bug report to a question, as it doesn't appear to be
a bug in Déjà-Dup (upstream or package), but a support request after an
installation failure.
Please comment and/or convert the question back to a bug if more help is
needed and/or more information can be provided and/or it t
Public bug reported:
Please remove pepperflashplugin-nonfree from Ubuntu, starting from the
upcoming Ubuntu 17.10 "Artful Aardvark".
pepperflashplugin-nonfree is the only (packaged) way for Debian users to
install the PPAPI Flash plugin, but adobe-flashplugin from Canonical's
partner repository i
I am setting this old bug to expire, seeing how it concerns ancient
releases of Ubuntu with antediluvian versions of Flash and Firefox.
To install and keep the Flash plugin up-to-date, one can nowadays use
the flashplugin-installer package in the multiverse repository (NPAPI
version) or the adobe-
** Changed in: adobe-flashplugin (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: flashplugin-nonfree (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
** Changed in: adobe-flashplugin (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: flashplugin-nonfree (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.launc
I am setting this old bug to expire, seeing how it concerns ancient
releases and how Flash plugin support has improved since it was
reported.
The Flash plugin can be installed and kept up-to-date via the
flashplugin-installer package in the multiverse repository (NPAPI
version) or via the adobe-fl
Much has changed regarding the Flash plugin and its support by Adobe and
Canonical since this bug was reported. Things are better and simpler.
This bug is unlikely to still be occurring, and if it were it certainly
wouldn't warrant a Critical status.
The Flash plugin can be installed and kept up-t
** Changed in: adobe-flashplugin (Ubuntu)
Assignee: Manpreet (manpreetkunnath) => (unassigned)
** Changed in: adobe-isv
Status: Confirmed => Incomplete
** Changed in: adobe-flashplugin (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification because you ar
Hi Victor, you're just missing a Python module ("no module named
gi.repository"). This has been encountered before, e.g. bug 1641423. No
reason why it is sometimes missing has been found yet.
The module is provided by the python-gi package, which should have been
installed as a dependency of the d
** Summary changed:
- Back up failed with message: Failed to execute child process "duplicity" (No
such file or directory)
+ Backup fails with message: 'Failed to execute child process "duplicity" (No
such file or directory)' or 'No module named gi.repository': missing
deja-dup-backend-gvfs, du
@mohan:
Have you tried doing what APT suggests: reinstalling deja-dup, which is
apparently "in a very bad inconsistent state" (possibly because
something failed during your system update on 2017-04-11 11:02:02,
although I don't know what did)?
For instance, from the command line:
sudo apt-get
** Changed in: pepperflashplugin-nonfree (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1620103
Title:
Installation fails with realpath error
To manag
@Kristoffer:
Assuming the package apt-transport-https is up-to-date on your computer,
what you're seeing are not errors but probably the warnings mentioned in
the bug's description, second-to-last paragraph.
Please refer to the bug's description, and please report details here if
seeing something
*** This bug is a duplicate of bug 1607535 ***
https://bugs.launchpad.net/bugs/1607535
The warnings reported here, about user _apt and their privileges, are
non-blocking and don't impact the successful download of the additional
data. They have been reported in several other bug reports (e.g.
pepperflashplugin-nonfree now downloads the PPAPI Flash Player Plugin
(i386 and amd64) from Adobe instead of Google, so this issue should no
longer happen. Marking as Fix Released.
Anyway better avoid this package (unless using Debian), better install
adobe-flashplugin (on Ubuntu) instead: https:/
*** This bug is a duplicate of bug 1628247 ***
https://bugs.launchpad.net/bugs/1628247
** Changed in: pepperflashplugin-nonfree (Ubuntu)
Status: Confirmed => Fix Released
** This bug has been marked a duplicate of bug 1628247
yakkety 1.8.2+nmu1ubuntu1 does not install due to changed
*** This bug is a duplicate of bug 1628247 ***
https://bugs.launchpad.net/bugs/1628247
** Changed in: pepperflashplugin-nonfree (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
pepperflashplugin-nonfree now downloads the Flash Player Plugin from
Adobe instead of Google, starting with version 1.8.2+nmu1ubuntu1.1 in
yakkety-proposed (and 1.8.3+nmu1ubuntu1 in zesty). So this issue can no
longer happen. Marking it as Fix Released.
Avoid using this package anyway unless on De
Bug fixed in all supported releases. Thanks Bhavani!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1632870
Title:
Package is broken since Google stopped shipping Flash with Chrome 54
for Linux
To
I'm glad manually removing the partially-downloaded fonts fixed the
issue for you.
A bug about partially-downloaded fonts preventing the rest of the
download is currently being fixed in bug 1657567. However, the error
that is thrown out in that case (Content-Range error) is not the same as
the one
Verified for 1.3ubuntu1.1 on Trusty.
The package installs successfully, downloads a .tar.gz PPAPI Flash
Player Plugin archive from an Adobe URL, and installs the contained
libpepflashplayer.so into /usr/lib/pepperflashplugin-nonfree/.
** Tags added: verification-done-trusty
--
You received this
This issue should not happen any longer, so I'm a bit disconcerted. What
is the version table for your ttf-mscorefonts-installer package?
$ apt-cache policy ttf-mscorefonts-installer
Can you confirm that there are no font-related partial downloads in
/var/lib/update-notifier/package-data-downlo
Thanks for your feedback and the video. Never mind the untranslated
string, this behavior is not normal at all. When I plug my external hard
disk, backup starts and completes successfully.
I'm thinking we could add unique error IDs in the code to find out which
particular error is triggered in you
Uqbar, what is your version of apt-transport-https?
$ apt-cache policy apt-transport-https
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1607535
Title:
ttf-mscorefonts-installer 3.4+nmu1ubuntu2 f
*** This bug is a duplicate of bug 374274 ***
https://bugs.launchpad.net/bugs/374274
This is a much-required feature, so I'm adding duplicate status as
needed.
Ideas and designs have been shared but nobody has started implementing
them: the code base is rather large and takes time getting acq
It's no big deal to exit Déjà-Dup while it runs. As far as I can tell,
whatever backup volumes were already made are kept on the backup
location, and the backup will resume later, or can be resumed manually.
Or at least that's what my previous experience of Déjà-Dup has been.
I don't know if the O
@Olivier:
It's the disk you use as backup location I suppose? Does the error show
up every time you plug it? Does it prevent automatic backups from
happening or do they occur later? Does the error prevent you from
running manual backups too? Does it also show up during manual backups?
@Vej:
Migh
I can't find this message in Déjà-Dup's or duplicity's source code and
.po files at the revisions corresponding to their versions in 16.10. No
idea where it comes from.
Olivier, if you can identify and tell us how to trigger this error, this
might give us a chance to find out where the message com
*** This bug is a duplicate of bug 1607535 ***
https://bugs.launchpad.net/bugs/1607535
@Patrick: I was asking Timofey, who reports being affected by this bug
with apt-transport-https 1.3.4 on Yakkety. That shouldn't be the case,
and any error that makes it look like it is can be solved away by
I'm still not convinced that this is worth a SRU, or qualifies for one.
The provision about "bugs which [...] (1) have an obviously safe patch
and (2) affect an application" in the SRU guidelines applies only to
bugs which have "high potential for improving the user experience", and
I'm just not su
Yes, the suggested packages should not be made dependencies or
recommended packages (for Python 2 reasons).
However the OP and comments raise the issue that as of now, on-demand
installation of duplicity (or deja-dup-backend-gvfs) is only triggered
when one opens the deja-dup-preferences GUI and c
Not reproducible every time in my case. Sometimes the folders are listed
twice, sometimes once. In both the include and exclude lists.
This bug and bug 1599662 are probably duplicates indeed.
Also: I cannot reproduce the bug at all on Trusty (deja-dup
30.0-0ubuntu4.1, duplicity 0.6.23-1ubuntu4.1)
@Michael: Sweet, thanks for merging!
@Vej, C de-Avillez: It's nice to nominate this bug for Xenial and
Yakkety, but I'm not sure it's really worth fixing in these series, or
that it fits the SRU requirements (I would personally go with Won't Fix
for the published releases).
--
You received this
@Bhavani: thanks a lot! If it's easily doable to SRU in Trusty, why not?
That would unbreak the package for the rest of Trusty's life. But
Trusty's version of the package is 1.3 vs. Xenial/Yakkety/Zesty's 1.8.x,
so the difference in versions may make it more difficult to SRU in
Trusty. In which cas
I wish I was knowledgeable enough to fix less trivial bugs. In the
meantime, here are two branches. Michael, which one would you like I
request a merge of?
https://code.launchpad.net/~nathanael-naeri/deja-dup/fix-1657092-a
Changes the word "Files" to "the file manager". The more accurate "a
compa
1 - 100 of 173 matches
Mail list logo
