Split up unicode-data into its own bug; bug 1838323.
** No longer affects: unicode-data (Ubuntu)
** No longer affects: gnome-characters (Ubuntu Xenial)
** No longer affects: gnome-characters (Ubuntu Disco)
** No longer affects: gucharmap (Ubuntu Xenial)
** No longer affects: gucharmap (Ubuntu
icu split up into bug 1838322.
** Changed in: openjdk-8 (Ubuntu Xenial)
Status: New => Fix Released
** Changed in: openjdk-8 (Ubuntu Bionic)
Status: New => Fix Released
** Changed in: openjdk-8 (Ubuntu Disco)
Status: New => Fix Released
** No longer affects: icu (Ubuntu)
Fixed in eoan, just needs a rebuild in other releases with a newer
unicode-data that has Reiwa in it. Still dependent on font having the
actual glyphs included (not the case at this moment in eoan).
** Also affects: gucharmap (Ubuntu Disco)
Importance: Undecided
Status: New
** Also
gucharmap split up into bug 1838321
** No longer affects: gucharmap (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gucharmap in Ubuntu.
https://bugs.launchpad.net/bugs/1828884
Title:
[META] Handling Japanese new era "令和
Public bug reported:
[Background]
Many packages are affected by the requirement to support the new era "Reiwa"
(令和）
This is the meta bug to track packages that need fixes; which packages
have already been SRUd to previous releases, how to prioritize the work
needed, and general test cases for
Looks like noto sources now have the right glyphs (since their April 9
release, actually). It will need an update both in Debian and Ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gucharmap in Ubuntu.
mozc appears to be all done (LP: #1823444)
** Changed in: mozc (Ubuntu Xenial)
Status: New => Fix Released
** Changed in: mozc (Ubuntu Bionic)
Status: New => Fix Released
** Changed in: mozc (Ubuntu Cosmic)
Status: New => Fix Released
** Changed in: mozc (Ubuntu Disco)
unicode-data in eoan does include Reiwa. Reverse-depends probably still
need to be rebuilt (I'm testing gucharmap which seemed easy enough to
patch to work).
** Changed in: unicode-data (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of
Oops; picked the wrong openjdk...
FWIW; according to the email by Mitsuya Shibata, openjdk 8 and 11 at
least are affected (so, everything prior to disco if updates are not
applied. Openjdk-8 updates appear to already be at 8u212, which should
include Reiwa support. Marking as Fix Released so we
I don't think it's *-control-center.
At the time, that was filed there by pitti, who correctly pointed out
that something might need to depend on libnss-myhostname (from systemd)
for a fallback to resolving hostname via just /etc/hostname (since
/etc/hosts isn't changed). At this point though, it
** Tags removed: rls-x-incoming
** Tags added: rls-ee-incoming
** Also affects: gnome-control-center (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: unity-control-center (Ubuntu
** Also affects: gucharmap (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: ubuntu
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gucharmap in Ubuntu.
https://bugs.launchpad.net/bugs/1828884
Title:
mozc appears to already be Fix Released for most releases; this has been
handled as bug 1823444.
** Description changed:
[Background]
Many packages are affected by the requirement to support the new era "Reiwa"
(令和）
This is the meta bug to track packages that need fixes; which packages
Fix Committed
** Changed in: gnome-shell-extension-desktop-icons (Ubuntu)
Assignee: Mathieu Trudel-Lapierre (cyphermox) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell-extension-desktop-icons
in Ubuntu.
** Changed in: gnome-shell-extension-desktop-icons (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell-extension-desktop-icons
in Ubuntu.
ht
Public bug reported:
I'm seeing some weird issue with the new NM + openvpn; if I create a new
VPN connection, and add certificate options (verify name exactly, plus
TLS auth), these options are not saved, leading to the connection
failing.
The following versions lead to an invalid connection:
ii
Bug was confirmed fix, although we don't have a formal version number
for the pacakge that was tested, let's mark this verification-done.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are
@Alan,
Can you confirm which version of plymouth you had installed?
You can use the following command to do so:
dpkg -l plymouth | cat
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
That's not what I mean though. For SRU verification we should aim to
have a positive identification of the exact version of the plymouth
package that was used for the tests.
For example, this can be achieved by looking at 'dpkg -l plymouth |
cat':
要望=(U)不明/(I)インストール/(R)削除/(P)完全削除/(H)保持
|
@Alan, could you please confirm which version of plymouth you have
installed for the tests you did?
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1767918
Title:
Login
nical Foundations Team (canonical-foundations) => Mathieu
Trudel-Lapierre (cyphermox)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1767918
Title:
Login password from GDM is shown
** Changed in: fusiondirectory (Ubuntu Xenial)
Status: New => In Progress
** Changed in: fusiondirectory (Ubuntu Xenial)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
** Changed in: fusiondirectory (Ubuntu Bionic)
Status: New => In Progress
--
You
** Changed in: fusiondirectory (Ubuntu)
Status: New => In Progress
** Changed in: fusiondirectory (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subs
s: New => In Progress
** Changed in: dovecot (Ubuntu Xenial)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to shared-mime-info in Ubuntu.
https://bugs.launch
** Changed in: dovecot (Ubuntu)
Status: New => In Progress
** Changed in: dovecot (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to shared-mim
** Also affects: nplan (Ubuntu)
Importance: Undecided
Status: New
** Changed in: nplan (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
Still a bug; if systemd-networkd requires a restart, then systemd-
networkd has something that it gets confused about, that we'll need to
figure out.
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of
** Also affects: netplan.io (Ubuntu)
Importance: Undecided
Status: New
** Changed in: netplan.io (Ubuntu)
Status: New => In Progress
** Changed in: netplan.io (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
--
You received this bug notifi
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Changed in: netplan
Status: Incomplete => Confirmed
** Changed in: cloud-init (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop
This got landed in netplan.io 0.35 in bionic. The changes still should
be part of a SRU.
** Changed in: nplan (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
** Description changed:
+ [Impact]
+ Server users on s390x configuring qeth devices.
+
+ [Test case]
+ 1) Reconfigure an interface for a QETH device
+ 2) Verify that 'netplan apply' completes successfully, without error.
+
+ [Regression potential]
+ This change has minimal potential for
There was a misunderstanding there: I never suggested we should use xkb-
keymap instead (or at least, that's not the message I was trying to
convey).
The intent was to reduce delta by not removing so much code, when
console-setup merges are already difficult. I didn't foresee that some
of that
Your original config in comment #1 is correct: you must specify the
underlying devices, because those names are matched later for
"interfaces:" in the bond config.
The issue with 802.3ad is likely a driver issue or a bug in systemd; the
right mode needs to be set by networkd (which may require
This would be a systemd-networkd bug, which I suspect might have already
been fixed too. Reassigning to systemd.
** Package changed: nplan (Ubuntu) => systemd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in
MIR approved.
The new version synced from debian in bionic (UNAPPROVED) looks good
now, and appears to have corrected test suite issues:
18057438 | X- | volume-key | 0.3.9-4 | 6 hours
| * volume-key/0.3.9-4 Component: universe Section: misc
** Changed in:
unbound attempts to add itself as a local resolver (pointing to
127.0.0.1). I think this will require specific integration work so that
unbound can properly update/ tell systemd-networkd that it wants to be
able to serve as a resolver.
** Changed in: squid3 (Ubuntu)
Status: New => Invalid
sendmail only uses an update-libc.d script to reload the daemon on
changes to resolv.conf, which should be sufficient for DNS resolution to
remain working as it did with resolvconf; seeing as the nameserver will
generally not change from 127.0.0.53
** Changed in: sendmail (Ubuntu)
Status:
Have the tests been fixed? I really don't much like having things in
main that run tests but don't use the result; is there any way to just
ignore the test(s) that are really broken and otherwise keep the
remaining tests failing the build if they fail, such that we can catch a
possible regression?
Looks like the current behavior should be sufficient for postfix to
integrate as well as it did with resolvconf: marking this Invalid.
** Changed in: postfix (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
** Changed in: netplan
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1756322
Title:
'netplan apply' fails when trying to activate another
Wild guess is this is a test that expects user input, and the input
never shows up?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to volume-key in Ubuntu.
https://bugs.launchpad.net/bugs/1754422
Title:
[MIR] volume-key
To manage
Go for libmp3lame0, on the condition that CVE-2017-15019 be looked into.
** Changed in: lame (Ubuntu)
Status: Incomplete => Fix Committed
** Changed in: lame (Ubuntu)
Assignee: Ubuntu Security Team (ubuntu-security) => (unassigned)
** Changed in: lame (Ubuntu)
Assignee:
libtwolame0 is approved.
** Changed in: twolame (Ubuntu)
Status: Incomplete => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to twolame in Ubuntu.
https://bugs.launchpad.net/bugs/1753458
Title:
[MIR] twolame
libmpg123-0 's MIR is approved then.
** Changed in: mpg123 (Ubuntu)
Status: Incomplete => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mpg123 in Ubuntu.
https://bugs.launchpad.net/bugs/1753450
Title:
[MIR]
** Changed in: lame (Ubuntu)
Assignee: (unassigned) => Ubuntu Security Team (ubuntu-security)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to lame in Ubuntu.
https://bugs.launchpad.net/bugs/1753441
Title:
[MIR] lame
To manage
** Changed in: twolame (Ubuntu)
Assignee: (unassigned) => Ubuntu Security Team (ubuntu-security)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to twolame in Ubuntu.
https://bugs.launchpad.net/bugs/1753458
Title:
[MIR] twolame
** Changed in: mpg123 (Ubuntu)
Assignee: (unassigned) => Ubuntu Security Team (ubuntu-security)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mpg123 in Ubuntu.
https://bugs.launchpad.net/bugs/1753450
Title:
[MIR] mpg123
To
MIR ack for libmpg123-0 if the Security Team acknowledges they are aware
of this requirement.
** Changed in: mpg123 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mpg123 in Ubuntu.
MIR ack for libtwolame0 if the Security Team acknowledges they are aware
of this requirement.
** Changed in: twolame (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to twolame in Ubuntu.
This package has a long security history, and a currently left-open CVE
because the upload of 3.100 did not include closing the active CVE.
If there's a go-ahead from the Security Team (I'm not looking for a code
review, just an acknowledgement that they are aware of the requirement
for this
Ok, I'm opening the tasks for Xenial and Trusty, and we can decide
exactly where it makes sense to do the SRU for these changes.
Plus, I understand maybe it was still reproducible in some form on
bionic, so it this should be revisited in general.
** Also affects: console-setup (Ubuntu Xenial)
dnsmasq Suggests: resolvconf only, and checks before using it. None of
the steps involved would break with resolvconf not being present,
integration just happens via /etc/resolv.conf normally.
** Changed in: dnsmasq (Ubuntu)
Status: New => Invalid
--
You received this bug notification
vpnc and vpnc-scripts check for existance of /sbin/resolvconf and only
Suggests: resolvconf. DNS integration by modifying /etc/resolv.conf (and
thus the systemd symlink) should work appropriately and let systemd-
resolved know about the new nameservers.
** Changed in: vpnc-scripts (Ubuntu)
hanged in: systemd (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: netplan
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
--
You received this bug notificat
Sounds like this is a bug in systemd, since it's what will deal with the
actual devices.
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
nee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
** Changed in: systemd (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/161
Xenial is affected too (systemd v229 looks to be, in general), so when
SRUing we might as well push the fix there too, even if resolved is not
typically used on Xenial.
** Also affects: systemd (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Xenial)
igh
** Changed in: systemd (Ubuntu Bionic)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
** Changed in: systemd (Ubuntu Artful)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
--
You received this bug notification because you are a member of Ubunt
Public bug reported:
If I try to apply vlans directly:
network:
version: 2
renderer: networkd
ethernets:
eth0: {}
vlans:
vlan1:
id: 1
link: eth0
addresses: [ 192.168.0.10/23 ]
vlan10:
id: 10
link: eth0
addresses: [ 10.0.0.5/24 ]
The vlan
Assignee: Mathieu Trudel-Lapierre (cyphermox)
Status: In Progress
** Also affects: openssh (Ubuntu Zesty)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Zesty)
Importance: Undecided
Status: New
** Also affects: nplan (Ubuntu Zesty)
Importance: Undecided
Public bug reported:
I started a system with cloud-init disabled, etc. and a single real
network interface (ens3) that could be configured.
That VM has no configuration whatsoever for systemd-networkd, as that
would have to have been written by netplan, and cloud-init did not
generate netplan
Artful)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1712921
Title:
enabling networkd appears to eat u
** Also affects: systemd (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: nplan (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in
Indeed, it looks like systemd is handling this properly by itself. I'll
do some more testing but it looks like removing that is probably the
best thing to do. At least font/keymaps are set properly.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Public bug reported:
Moving off of resolvconf and to systemd-resolved requires that
resolv.conf is properly handled both in the case of new installs (done
as per 234-2ubuntu9 at least), but also in the case of upgrades from
previous releases or previous versions of systemd.
There are various use
** Changed in: rhythmbox-plugin-alternative-toolbar (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to rhythmbox in Ubuntu.
https://bugs.launchpad.net/bugs/1703662
Title:
[MIR]
(Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: nplan (Ubuntu Artful)
Importance: High
Assignee: Mathieu Trudel-Lapierre (cyphermox)
Status: Triaged
** Also affects: systemd (Ubuntu Zesty)
Importance: Undecided
Status: New
** Also affects: nplan
(Ubuntu)
Status: New => Incomplete
** Changed in: epiphany-browser (Ubuntu)
Assignee: Mathieu Trudel-Lapierre (cyphermox) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to epiphany-browser in Ubuntu.
hanged in: systemd (Ubuntu)
Status: New => Triaged
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in U
Verification done on xenial and yakkety with netplan 0.23~:
The parameters are being accepted by netplan parsing network v2 yaml;
and appropriately copied on to the resulting configuration for the
renderer. STP is not yet supported by systemd however, so further
testing could not be done.
**
We should probably try to avoid shipping more than one browser by
default. Currently we ship Firefox (and shipping a browser on live
images is up to the Desktop team, AFAIK). The package split appears to
make sense to provide just the webapp integration feature (but it's not
done yet).
I have not
Seems simple enough, given that it's a doc package; and it has a bug
subscriber, etc. MIR approved.
** Changed in: gnome-getting-started-docs (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
** Changed in: gnome-getting-started-docs (Ubuntu)
Status: Tria
*** This bug is a duplicate of bug 1686257 ***
https://bugs.launchpad.net/bugs/1686257
Indeed sounds like the issue I was having -- marking as a duplicate.
FTR, I no longer see an issue with gdm3; but I had reinstalled my system
with Ubuntu-GNOME directly, and in that case it worked; so it
It looks like the issues mentioned above are appropriately taken care
of; so I'm good with this MIR.
** Changed in: gnome-shell (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell
- Despite what is claimed in the bug description; iio-sensor-proxy is still a
Recommend, would need a MIR.
- There appears to be test that could run for gnome-shell, but they aren't
obviously being run as part of the build -- make check does not appear to run
run-tests.sh.
- There are a few
MIR approved.
** Changed in: mutter (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1685408
Title:
[MIR] mutter
To manage
Since this was in main previously, I don't see any reason to really
block it, but it still ought to have some review by the Security team
given the obvious security history for gdm and being a login manager.
** Changed in: gdm3 (Ubuntu)
Assignee: Mathieu Trudel-Lapierre (cyphermox) => Ubu
MIR approved.
** Changed in: caribou (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to caribou in Ubuntu.
https://bugs.launchpad.net/bugs/1685867
Title:
[MIR] caribou
To manage
MIR approved. The test fixes are committed to the packaging branch.
** Changed in: gnome-settings-daemon (Ubuntu)
Status: Incomplete => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in
MIR approved.
** Changed in: gjs (Ubuntu)
Status: New => Fix Committed
--
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/1683989
Title:
[MIR] gjs
To manage notifications about
MIR approved.
** Changed in: mozjs38 (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mozjs38 in Ubuntu.
https://bugs.launchpad.net/bugs/1683937
Title:
[MIR] mozjs38
To manage
** Changed in: mozjs38 (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mozjs38 in Ubuntu.
https://bugs.launchpad.net/bugs/1683937
Title:
[MIR] mozj
I've re-reviewed gnome-control-center since I mixed it up with gnome-
settings-daemon before, and since there had never been a MIR in the past
(although it was in main before); MIR approved.
** Changed in: gnome-control-center (Ubuntu)
Status: Incomplete => Fix Committed
--
You received
: New => Incomplete
** Changed in: gnome-settings-daemon (Ubuntu)
Importance: Undecided => High
** Changed in: gnome-settings-daemon (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
** Changed in: gnome-settings-daemon (Ubuntu)
Milestone: None =>
"Other distros do it" isn't sufficient rationale, by itself, to support
putting pcre2 in main. We already ship it, the question is whether it
should be in main, meaning whether Canonical will be responsible for
support, providing security updates, etc.
To mirror what doko mentioned earlier, what
** Changed in: pcre2 (Ubuntu)
Milestone: ubuntu-17.03 => ubuntu-17.05
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/163
Title:
[MIR] pcre2
To manage notifications
** Also affects: network-manager-openvpn (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Changed in: network-manager-openvpn (Ubuntu Yakkety)
Status: New => Triaged
** Changed in: network-manager-openvpn (Ubuntu Yakkety)
Importance: Undecided => Wishlist
--
You
To be clear, I share doko's feeling against having two versions of the
library in main if it can be avoided -- this is certainly not a
permanent situation, but most things don't appear to have switched to
pcre2 just yet (and I would expect they would in the near-ish term). In
that sense, I'd be
I understand the concerns, and I share them, but I don't think we should
alone make the decision. Perhaps bring this up for wider discussion on
the ubuntu-devel mailing list?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Sponsored the SRU. This does not need a fix in zesty as the fix is
already applied there (via newer upstream release).
Adam Collard, please update the bug description to follow the SRU
procedures (https://wiki.ubuntu.com/StableReleaseUpdates#Procedure). You
will want to subscribe ~ubuntu-sru when
This isn't caused by ubiquity if it's at startup, since ubiquity would
only care about it w/r/t partitioning, and that hasn't been the case
since somewhere during the development cycle of 16.04 -- when we updated
partman-base to stop trying to partition rpmb devices.
Closing the ubiquity task as
** Changed in: pcre2 (Ubuntu)
Milestone: None => ubuntu-17.03
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/163
Title:
[MIR] pcre2
To manage notifications about
Since it's been verified by Nara; marking verification-done.
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity in Ubuntu.
https://bugs.launchpad.net/bugs/1560162
Title:
Xenial: scaling is
This still needs verification. You would want to use 'break=bottom' on
the command-line when booting to stop before ubiquity starts, then
chroot into the system and apt-get install the new ubiquity to test
this.
The bug that was automatically found isn't a regression of this fix but
an issue with
** Changed in: ubiquity (Ubuntu Xenial)
Status: New => In Progress
** Changed in: ubiquity (Ubuntu Xenial)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subs
Public bug reported:
See included screenshot. There is something that looks like a hardcoded
string for "Bastien's computer" as a hostname as visible in bluetooth.
That is not the case, and may confuse users.
I've found the following string in gnome-bluetooth 3.18.2-1ubuntu2:
hanged in: systemd (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
** Changed in: dbus (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: In Progress => Invalid
** Changed in: ubuntu-r
It doesn't especially matter to me which packages make it to main or
not, but we shouldn't move packages around if they don't need to be.
Knowing what is affected also shows that there has been some work put in
preparing the MIR request.
As for the lintian warnings, no, it's not a blocker but
** Changed in: unity-control-center (Ubuntu)
Status: Confirmed => In Progress
** Changed in: unity-control-center (Ubuntu)
Assignee: anagha (anghakc) => Mathieu Trudel-Lapierre (mathieu-tl)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
How are you reproducing this? How can I verify the fix?
It seems to me as nautilus recognizes a dummy file correctly as plain
text rather than TeX document; so does the file command.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
1 - 100 of 678 matches
Mail list logo
