Sounds like this rather is about the deja-dup frontend, given that
duplicity itself doesn't have any scheduling capabilities.
** Package changed: duplicity (Ubuntu) => deja-dup (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to dej
Taking a cue from https://bugzilla.redhat.com/show_bug.cgi?id=1166199 I
worked around the issue by adding the following to my
/etc/NetworkManager/NetworkManager.conf
[keyfile]
unmanaged-devices=interface-name:virbr0
Yet I imagine that the real solution is something more general.
** Changed i
** Bug watch added: Red Hat Bugzilla #1166199
https://bugzilla.redhat.com/show_bug.cgi?id=1166199
** Also affects: network-manager (Fedora) via
https://bugzilla.redhat.com/show_bug.cgi?id=1166199
Importance: Unknown
Status: Unknown
--
You received this bug notification because yo
** Package changed: ubuntu => cups (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1397491
Title:
/etc/init.d/cups restart or stop failure
Status in cups package in Ubuntu:
Ne
** Changed in: gnome-disk-utility (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-disk-utility in Ubuntu.
https://bugs.launchpad.net/bugs/1396748
Title:
New upstream release 3.14.0
S
*** This bug is a duplicate of bug 771272 ***
https://bugs.launchpad.net/bugs/771272
Appear to be a known issue in upstream gnome-keyring:
https://bugzilla.gnome.org/show_bug.cgi?id=641082
Marking this report as a duplicate, as it from an Ubuntu point of view
is currently being tracked in bug
It's an explicit behavior of the openssh client to try keys provided by
the ssh agent. If you don't want this behavior you can set the
IdentitiesOnly ssh config option.
I would assume that what is happening here is that you are using the
gnome-keyring as your ssh agent? From what I can see it auto
** Also affects: gnome-keyring (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1302812
Title:
Explicit identity files are bei
Not neccesarily sure that this is a bug, but if something is to change
it's more likely to be in the ubuntu-gnome-desktop package, which is
where the dependency reside.
** Package changed: simple-scan (Ubuntu) => ubuntu-gnome-meta (Ubuntu)
--
You received this bug notification because you are
*** This bug is a duplicate of bug 1282203 ***
https://bugs.launchpad.net/bugs/1282203
** This bug has been marked a duplicate of bug 1282203
gnome-terminal not respecting "Enable menu access keys" setting, inside the
Unity desktop environment.
--
You received this bug notification becau
Yepp, that time line sounds about right to me too.
Given that gnome-terminal 3.6.2-0ubuntu1 is from the 16th of December I
would assume then that the issue is due to some gnome/unity change.
Also, when running gnome-terminal under Xfce the "Enable menu access
keys (such as Alt+F to open the File
** Changed in: gnome-terminal (Ubuntu)
Importance: Undecided => Medium
--
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/1282203
Title:
gnome-terminal not respecting "Enable me
Public bug reported:
Under Edit --> Keyboard Shortcuts.. there is a checkbox for "Enable menu
access keys (such as Alt+F to open the File menu)".
That checkbox appear to have no affect what so ever. No matter whatever
I have it checked or not I still get the same behavior, that menu access
keys a
13 matches
Mail list logo
