Russ, can you please post the values of the following environment
variables in MATE, I'm going to try and implement something and I'm not
sure which one to use (probably the last one). You can use printenv var
or echo $var to find them out. Thanks.
SESSION
GDMSESSION
DESKTOP_SESSION
@Russ Phillips (or anyone using MATE):
Can you confirm that "Caja" is the user-facing name of the file manager
in MATE desktop environment? And by that I mean, its name in the menus.
Thanks.
Cause in Unity DE and Cinnamon DE, I'm quite certain that the user-
facing name of Nautilus and Nemo,
@Russ Phillips:
Don't bother, I checked by myself in the .desktop file.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/1657092
Title:
deja-dup refers to "Files" instead of "Caja"
w Déjà-Dup only officially integrates
with GNOME/Nautilus and Unity/Nautilus as far as I know.
If he's OK with Russ's suggestion then I'll be happy to propose for
merging of course.
** Changed in: deja-dup
Assignee: (unassigned) => Nathanaël Naeri (Naël) (nathanael-naeri)
** Changed
Yes I am marking this Invalid because the issue hasn't manifested itself
since mid-2015. See comment 3 for more details. Fingers crossed that it
doesn't come back.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to sane-backends in Ubuntu.
*** This bug is a duplicate of bug 1002710 ***
https://bugs.launchpad.net/bugs/1002710
** Changed in: unity-2d (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-2d in Ubuntu.
*** This bug is a duplicate of bug 1002710 ***
https://bugs.launchpad.net/bugs/1002710
** Changed in: unity-2d (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-2d in Ubuntu.
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
Added this bug to duplicity, since it is probably better suited for
resolution there than in Déjà-Dup.
Also updated the description.
** Tags removed: amd64 xenial
** Tags added: testcase
** Description changed:
- Deja-dup has never worked for me (last 5 years) always errors.
- No after a new
** Changed in: sane-backends (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to sane-backends in Ubuntu.
https://bugs.launchpad.net/bugs/1442111
Title:
Scanner is correctly identified but
Hi Christopher, thank you for resurrecting this bug report.
The affected machine has since been upgraded to Xenial. It still uses
the same scanner. The current versions of sane-backends and iscan are
barely more recent, so one could suppose the behavior I reported in
2015-05 could still occur.
** Also affects: duplicity
Importance: Undecided
Status: New
** Also affects: duplicity (Ubuntu)
Importance: Undecided
Status: New
** Changed in: duplicity
Status: New => Confirmed
** Changed in: duplicity (Ubuntu)
Status: New => Confirmed
--
You received
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
@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
@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:
*** 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
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
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
** 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,
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
@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
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
** 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 Desktop
Packages, which is subscribed to flashplugin-nonfree
** 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 Desktop
Packages, which is subscribed to flashplugin-nonfree in
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
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
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
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
*** 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
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
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 >
@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.
** 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 Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
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
** Changed in: deja-dup (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/1685294
Title:
Deja-dup won't run backup in Xubuntu 17.04
Status in
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 Desktop
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 Desktop
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 Desktop
Packages, which is subscribed to
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 Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1685754
Title:
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
> 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
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 Desktop
Packages, which is
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]
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
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 Desktop
Packages, which is subscribed to appstream in Ubuntu.
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)
** 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
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
*** 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-
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
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
** 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,
** 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 Desktop
Packages, which is subscribed to
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 Desktop
Packages, which is subscribed to
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:
** 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:
Issue reported upstream and bug watch added
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1878109
Title:
Certain features in the Sharing panel fail with D-Bus related
** 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 Desktop
Packages, which is subscribed to gnome-screenshot in Ubuntu.
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
** 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.
+
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
** 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 Desktop
Packages, which is subscribed to gnome-screenshot in
** 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 Desktop
** 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 Desktop
Packages,
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
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
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
67 matches
Mail list logo
