Oh sorry, it looks like you reverted this in your upload.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1905740
Title:
SRU the current 3.36.5 stable update
To
Most of this looks fine but I'm concerned about this upstream changelog
item:
sharing: Replace vino with gnome-remote-desktop for X11 sessions
It looks like that was done because of a problem with Wayland only.
Changing behaviour for X11 that isn't for the purpose of fixing a bug is
something
Hello Sebastien, or anyone else affected,
Accepted gnome-bluetooth into focal-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
bluetooth/3.34.3-0ubuntu1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
An upload of gnome-shell to bionic-proposed has been rejected from the
upload queue for the following reason: "Fix appears incomplete, and no
progress in a month. Please see
https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1838152/comments/5 and subsequent discussion.".
--
You
An upload of gnome-shell to bionic-proposed has been rejected from the
upload queue for the following reason: "Fix appears incomplete, and no
progress in a month. Please see
https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1838152/comments/5 and subsequent discussion.".
--
You
** Also affects: tracker (Ubuntu Focal)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to tracker in Ubuntu.
https://bugs.launchpad.net/bugs/1896073
Title:
SRU the current 2.3.6 stable
On gnome-shell, we now understand there are complications with API
breakage in microreleases, so we need a plan for reverse dependency
shell extensions to mitigate potential regressions. Discussion at
https://discourse.ubuntu.com/t/scope-of-gnome-mru/18041. I don't think
we can proceed with the
Disco and Eoan are EOL though, and Focal looks like it already has
upstream commit 19e0840 included. So isn't it your proposed Bionic
upload that would be different? Why not look into making that the same
as what is in Focal?
Regardless, I'd like you to please at least consider the possibility
I'm not sure this fix is complete. What about, for example:
https://gitlab.gnome.org/GNOME/gnome-
shell/-/commit/19e084036a1dc3c5da010c3e7a42ce67df317797? As far as I
understand, it is exactly (and only) the fsync() call that we're trying
to move off the main thread, and this commit suggests to me
Hello riu, or anyone else affected,
Accepted gnome-shell-extension-desktop-icons into focal-proposed. The
package will build now and be available at
https://launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-
icons/20.04.0-3~ubuntu20.04.1 in a few hours, and then in the -proposed
An upload of libfprint to focal-proposed has been rejected from the
upload queue for the following reason: "No bug references and/or SRU
information for "New upstream release" and "Lots of various driver
fixes"; incomplete discussion of regression potential in all bugs that
are referenced. Please
Hello Sebastien, or anyone else affected,
Accepted nautilus into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/nautilus/1:3.36.3-0ubuntu1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello milvi, or anyone else affected,
Accepted djvulibre into bionic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/djvulibre/3.5.27.1-8ubuntu0.2 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
The verification of the Stable Release Update for gnome-shell has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
The verification of the Stable Release Update for gnome-shell has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
The verification of the Stable Release Update for gnome-shell has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
The verification of the Stable Release Update for gnome-shell has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
Note that the gnome-shell-extension-no-annoyance extension exists
(presumably as a workaround rather than a solution to this bug).
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
I don't see uploads for Bionic or for Disco?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1827346
Title:
Power: Fail to set delay time when the value is 90 minutes
Hello David, or anyone else affected,
Accepted totem into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/totem/3.26.0-0ubuntu6.2 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello David, or anyone else affected,
Accepted totem into cosmic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/totem/3.26.2-1ubuntu3
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Accepting, but "there isn't really any regression risk here" isn't OK as
documented at https://wiki.ubuntu.com/StableReleaseUpdates - see "It's
just a one-line change!" and the documentation of this entry in the
Procedure section. Please could you fix this?
For example, what if this SRU
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
I'm not sure why this is filed against fetchmail?
You also haven't stated what version of empathy you're running nor what
Ubuntu release you're running.
Changing the bug task to empathy for now, but marking it
An upload of nautilus to bionic-proposed has been rejected from the
upload queue for the following reason: "As discussed on IRC: contains
changes unrelated to the fixes documented to be present in this
upload.".
--
You received this bug notification because you are a member of Ubuntu
Desktop
The verification of the Stable Release Update for appstream has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Sounds like this is a problem with the Network Manager OpenVPN plugin
rather than OpenVPN itself, so I'm retasking the bug.
** Package changed: openvpn (Ubuntu) => network-manager-openvpn (Ubuntu)
--
You
For Bionic:
Shouldn't this be 3.28.3-0ubuntu0.18.04.1 directly, rather than
3.28.3-0ubuntu0.18.04.1 then 3.28.3-0ubuntu0.18.04.2?
Missing Launchpad-Bugs-Fixed field in changes file. Did you use Ubuntu
or set vendor to Ubuntu if on Debian? Please re-upload with that.
Bugs like bug 1783363 appear
Hello Marco, or anyone else affected,
Accepted mutter into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mutter/3.28.3-1~ubuntu18.04.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Unsubscribing ~ubuntu-sponsors.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-menus in Ubuntu.
https://bugs.launchpad.net/bugs/1765799
Title:
Applications menu does not get populated with recently installed apps
using apt
Hello João, or anyone else affected,
Accepted gnome-menus into bionic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
menus/3.13.3-11ubuntu1.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
> Tested this extensively in budgie - installing/removing repeatedly via
gnome-software, budgie-welcome, command line. Works everytime.
Thank you for treating this carefully.
** Tags added: verification-needed verification-needed-bionic
--
You received this bug notification because you are a
>
[Regression Potential]
Fix is to rename a signal to avoid a name collision, low chance of introducing
new bugs.
Please update that to inform testers where to look for new bugs if the change
does happen to introduce any.
--
You received this bug notification because you are a member of
>
Asked on forum if anyone knows a suitable snap to test this:
https://forum.snapcraft.io/t/searching-for-a-snap-that-has-a-plug-with-multiple-slots
Looks like you got an answer there on how to reproduce? Accepting for
now, but please verify using that method (or by finding the culprit snap
that
Hello errors.ubuntu.com, or anyone else affected,
Accepted gnome-software into bionic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
software/3.28.1-0ubuntu4.18.04.2 in a few hours, and then in the
-proposed repository.
Please help us by
Hello errors.ubuntu.com, or anyone else affected,
Accepted gnome-software into bionic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
software/3.28.1-0ubuntu4.18.04.2 in a few hours, and then in the
-proposed repository.
Please help us by
** Changed in: openssh (Ubuntu)
Assignee: Ngo Quang Thong (quangthong1981) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/201786
Title:
ssh Agent
The verification of the Stable Release Update for gdm3 has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
I'd like confirmation from another SRU team member before accepting
because of an edge case situation with versions that has arisen here.
Details: https://irclogs.ubuntu.com/2018/07/04/%23ubuntu-devel.html
(latest logs not appeared yet but they will).
--
You received this bug notification
Does this want holding like bug 1771242?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-calendar in Ubuntu.
https://bugs.launchpad.net/bugs/1768555
Title:
Update gnome-calendar to 3.28.2
To manage notifications about this
The verification of the Stable Release Update for libgtop2 has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter
Hello Iain, or anyone else affected,
Accepted vte2.91 into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/vte2.91/0.52.2-1ubuntu1~18.04.1 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
SRU review: +1
It was quite painful to handle the quilt noise in revert-pcre2.patch and
slowed down my review quite a bit to identify the real changes in there.
I'd appreciate it if everyone could normalise their quilt refreshing in
the future by using "-p ab --no-timestamps --no-index" or
Hello Nikita, or anyone else affected,
Accepted gnome-terminal into bionic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
terminal/3.28.2-1ubuntu1~18.04.1 in a few hours, and then in the
-proposed repository.
Please help us by testing this
Hello Michael, or anyone else affected,
Accepted desktop-file-utils into artful-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/desktop-
file-utils/0.23-1ubuntu3.17.10.1 in a few hours, and then in the
-proposed repository.
Please help us by testing
Hello Michael, or anyone else affected,
Accepted desktop-file-utils into xenial-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/desktop-
file-utils/0.22-1ubuntu5.2 in a few hours, and then in the -proposed
repository.
Please help us by testing this
Hello Michael, or anyone else affected,
Accepted desktop-file-utils into bionic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/desktop-
file-utils/0.23-1ubuntu3.18.04.1 in a few hours, and then in the
-proposed repository.
Please help us by testing
Thank you for your report. This bug is better filed against netplan in
the first instance, so the netplan developers can consider your use
case.
If I were you, I'd expand on your use case, explaining what you're doing
and why you need it and so forth, if you want anything addressed before
We concluded that this isn't a snapd bug, except in so far as it depends
on systemd.
** Changed in: snapd (Ubuntu Trusty)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: maas (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: snapd (Ubuntu Trusty)
The verification of the Stable Release Update for gnome-shell has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
The verification of the Stable Release Update for gnome-shell has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
** Summary changed:
- Ubuntu-patched nautilus causes regression of file rename popover bug
+ Regression of file rename popover bug
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
15:25 tsimonq2: the gvfs fix looks good to me superficially,
though I think the surgery involved in the fix deserves a closer review
which will take me more time. I'll look again later. Thank you again for
driving both of these.
--
You received this bug notification because you are a member of
Hello Jeremy, or anyone else affected,
Accepted gjs into zesty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/gjs/1.48.5-0ubuntu0.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
09:26 looks like the tarball was generated with non-patched / out
of date config.sub; rebuilding now with extra debug to see if autoreconf
is actually done or not.
09:28 dh_update_autotools_config
09:28 dh_autoreconf are both run.
09:29 cat config.sub, shows timestamp='2016-11-04' so
The diff looks fine to me, except for one part of the m4 autoreconf
noise:
-x86_64-*kfreebsd*-gnu|x86_64-*linux*|ppc*-*linux*|powerpc*-*linux*| \
+x86_64-*kfreebsd*-gnu|x86_64-*linux*|powerpc*-*linux*| \
There are some other ppc related changes as well which I think are all
part of the same
> It looks like the packaging uses autoreconf...
Actually, looks like it previously did (prior to Zesty), but no longer
does?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gjs in Ubuntu.
https://bugs.launchpad.net/bugs/1698553
Hi Jeremy,
> There used to be a standing release exception from the Tech Board (TB)
for GNOME microreleases but this explicit exception was dropped when the
TB simplified the SRU policy in September 2015.
I was not aware of this. Thank you for pointing it out.
The current SRU policy is quite
Thank you for preparing this update! This presumably falls under:
https://wiki.ubuntu.com/StableReleaseUpdates#New_upstream_microreleases
Could you detail what automatic testing is available please, with
reference to the requirements in that section of the policy? It would
probably be worth
> It would probably be worth adding that to the bug description...
Actually the policy requires it: "The upstream QA process must be
documented/demonstrated and linked from the SRU tracking bug."
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
According to my history.log, I upgraded from ubuntu-session
3.24.1-0ubuntu8 to 3.24.1-0ubuntu9 on 2017-07-03. Then from
3.24.1-0ubuntu9 to 3.24.1-0ubuntu11 on 2017-07-10 (today). I think
you're looking at an older part of my log?
I only had the display manager prompt on upgrade today, defaulting
Note that I did select gdm3 manually at the prompt, so that is correct
now.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1703358
Title:
Display manager defaults to lightdm
This is the situation now:
robie@xps:~$ grep 'XSession=ubuntu' /var/lib/AccountsService/users/*
XSession=ubuntu
robie@xps:~$ echo $?
0
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
** Attachment added: "term.log"
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1703358/+attachment/4912194/+files/term.log
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
Public bug reported:
When I upgraded Artful earlier today using "sudo apt upgrade", I was
prompted to pick between gdm3 and lightdm. lightdm was selected by
default. I suspect that if I'd been running non-interactively, lightdm
would have been selected, which is incorrect for our transition to
** Attachment added: "history.log"
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1703358/+attachment/4912195/+files/history.log
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
A workaround for my gvim-based hang is to not have gvim open on the
sshfs when I suspend. I don't have that option with gsd-housekeeping, so
I basically have to unmount sshfs before suspend, which breaks
everything else (eg. open bash prompts). Using "sshfs -o reconnect"
works fine except for
I'm also hitting this with:
Jul 6 08:19:25 xps kernel: [93020.924360] gsd-housekeepin D0 1729
1350 0
Creating a task against gnome-settings-daemon in case a workaround is
possible.
** Also affects: gnome-settings-daemon (Ubuntu)
Importance: Undecided
Status: New
--
You
The original bug as reported was a failure to import certain
configuration files using network-mangaer-openvpn. This turned out to be
due to the use of inlined key material (comment 24). network-manager-
openvpn did not support this as a feature at the time, so was unable to
parse this type of
Hello Jeremy, or anyone else affected,
Accepted desktop-file-utils into trusty-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/desktop-
file-utils/0.22-1ubuntu1.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this
Accepting for Trusty. Precise is EOL, so I'm reluctant to break
expectations by touching it. If you think an exception is warranted,
perhaps ask ubuntu-release@?
** Description changed:
Note
Yes, I know precise is basically unsupported but it might be nice to fix
Travis here anyway.
Public bug reported:
Using gnome-terminal 3.24.2-0ubuntu1 from the current artful daily
installer.
gnome-terminal crashes if I click Terminal->Preferences->Profiles->Edit.
This is reliably reproducible on the live CD as well as on a freshly
installed system from the daily installer image.
The verification of the Stable Release Update for gnome-calendar has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
The verification of the Stable Release Update for gnome-calendar has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
The verification of the Stable Release Update for gnome-calendar has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
Hi Mark!
Thank you for pointing me to this bug. I spent some time looking into
this.
It seems that there is currently no established mechanism for ordering
NSS modules into nsswitch.conf automatically. Instead every package is
doing its own parsing mangling of the file on install. libnss-resolve
The verification of the Stable Release Update for gnome-settings-daemon
has completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that
Looks like this caused a regression in Xenial tracked in bug 1663695.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1644498
Title:
apt-get update returns "AppStream cache
The verification of the Stable Release Update for appstream has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
So it looks like this was a regression caused by the fix for bug 1644498
landing in Xenial?
** Tags added: regression-update
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1663695
Thank you for the patch and sorry for the delay. We're making an effort
to clear out languishing items in the sponsorship queue today.
vte needs fixing in Zesty before we can fix it in older releases. Please
see https://wiki.ubuntu.com/StableReleaseUpdates#Procedure
We also need a working test
14:01 rbasak: good catch, it was fixed in gnome-software
3.23.90 but zesty is still at 3.22.5 so we need to backport that patch
OK, let's remove verification-done for now to prevent accidents.
** Tags removed: verification-done
--
You received this bug notification because you are a member of
Is this fixed in Zesty? Current status is Triaged.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1621971
Title:
Add handler for snap: URLs
To manage notifications about
What's the real user impact of this please? What's the user action that
causes an attempt to xdg-open a snap: URL that currently fails? Please
document this in the "Impact" section.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Can I suggest that "the GNOME Micro Release Exception" statement
includes a link, so those of us ~ubuntu-sru who don't know about it can
look it up? I wouldn't block on this - but still waiting on Brian's
request I think.
--
You received this bug notification because you are a member of Ubuntu
Wait to accept this.
** Changed in: gnome-keyring (Ubuntu Xenial)
Status: In Progress => Incomplete
** Changed in: gnome-keyring (Ubuntu Yakkety)
Status: In Progress => Incomplete
** Changed in: gnome-keyring (Ubuntu Trusty)
Status: Triaged => Incomplete
--
You received
The verification of the Stable Release Update for glib2.0 has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
The verification of the Stable Release Update for appstream has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
Please:
1) Confirm how you tested (referring to the test plan is fine, but
please do so) what the results were, and which package versions you
tested before marking verification-done.
2) Fix the "Regression Potential: None" in the bug description and
explain how you have considered other users
Hello willm.wade, or anyone else affected,
Accepted nautilus into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/nautilus/1:3.18.4.is.3.14.3-0ubuntu6
in a few hours, and then in the -proposed repository.
Please help us by testing this new
Accepting, but a couple of comments:
1) "Regression potential: none" is not acceptable. See
https://wiki.ubuntu.com/StableReleaseUpdates#Procedure. Please fix this
before SRU verification.
2) Instead of " Adapted from
https://git.gnome.org/browse/nautilus/commit/?id=e66d3ca; in the
description
(these also impact other architectures - see http://people.canonical.com
/~ubuntu-archive/pending-sru.html)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1644498
Title:
apt-get
We have both success and not-fixed reports from -proposed testing.
However, amongst those who reported not-fixed, I can't find any
confirmation that the reporters did actually have both necessary
-proposed packages updated, except for Tommy who confirmed that updating
both packages did work.
So
We do however have a couple of autopkgtest regressions. Please see
http://autopkgtest.ubuntu.com/packages/a/appstream/xenial/amd64 and
http://autopkgtest.ubuntu.com/packages/i/isenkram/xenial/amd64. Please
could the people driving this SRU check those and comment?
--
You received this bug
Public bug reported:
See bug 1579475. I can manually follow through and see that the output
of "systemctl status amavis.service" is required for the report to be
helpful. Can the apport hook figure out the same thing?
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
Looks like the fix is in gtk+2.0, but will need backporting. The
upstream commit is:
https://git.gnome.org/browse/gtk+/commit/?id=d55b815
https://bug677329.bugzilla-attachments.gnome.org/attachment.cgi?id=321036=diff==patch=raw=1
I think these are identical but have not checked.
** Also
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I'm marking this bug as Incomplete.
If indeed this is a local configuration problem, you can find pointers
to
Sorry, wrong bug.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to yelp in Ubuntu.
https://bugs.launchpad.net/bugs/158308
Title:
Upgrade from 7.04 to 7.10 blocked with following error message:
To manage notifications about this bug
** Summary changed:
- ssh-add: Error reading response length from authentication socket.
+ gnome-keyring does not support ssh-add -c
** Description changed:
+ ssh-add does not work with -c (confirmation) when used with gnome-
+ keyring (which is the common default in many desktop
Public bug reported:
According to init(1), --version is expected to work. But instead I get:
$ init --version
init: unrecognized option '--version'
As we switch from upstart to systemd, I wanted to check which I was
running, and this seemed like an obvious way to do it.
ProblemType: Bug
1 - 100 of 125 matches
Mail list logo
