We'd kind of need this to work anyway outside of the context of cloud-
init-local.
If one sets up netplan rules for a device, and for instance, attempts to
set the MTU in networkd .link files, this change would not take effect
until the system is rebooted. netplan could trigger --subsystem-
match=
This is somewhat related to
https://github.com/systemd/systemd/issues/3998.
For now, there's still no way to do this in systemd; it will require an
upstream fix.
** Bug watch added: github.com/systemd/systemd/issues #3998
https://github.com/systemd/systemd/issues/3998
--
You received this bu
This is most likely a ubiquity bug; where the connection is created with
the wrong permission settings.
** Package changed: network-manager (Ubuntu) => ubiquity (Ubuntu)
** Changed in: ubiquity (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
** Changed in: ub
** Changed in: ubiquity (Ubuntu Xenial)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to humanity-icon-theme in
Ubuntu.
https://bugs.launchpad.net/bugs/1622686
Title:
double header
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
Touch seeded packages, which is subscribed to humanity-icon-theme in
Ubuntu.
I can't reproduce this issue here; trying to install ubuntu-server and
preseeding apt-
setup/local0/repository="http://ppa.launchpad.net/cyphermox/ppa/ubuntu
zesty main".
The preseeded repository is indeed showing in sources.list and is
written correctly.
If you can still reproduce this bug, plea
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 I
Given the large number of changes in a "backport" SRU and the changes to
patches (looks like they are upstreamed, but maybe some bits are
missing?), I think this bug is lacking in terms of a comprehensive set
of test cases.
Some time ago I had captured the kind of tests I'd normally do when
upload
Setting the Vivid tasks to Won't Fix since it's been EOL for a little
while.
** Changed in: shadow (Ubuntu Vivid)
Status: Triaged => Won't Fix
** Changed in: openssh (Ubuntu Vivid)
Status: Triaged => Won't Fix
** Changed in: lightdm (Ubuntu Vivid)
Status: Triaged => Won't Fi
No, it's not widely broken. Some things are broken on some hardware, and
it's not all broken in the same way, that's why I asked for logs -- so
we can know what the actual issue is.
I don't have all the hardware in the world, so I can't reproduce these
issues myself.
Dave, if you're still having
All the listed test cases appear to have been covered and successfully
verified for both xenial and yakkety. We're just waiting for Jason to do
his testing (he said "tomorrow" Friday December 16...). If that gets
done then, the updates should be good to release on Monday (there aren't
usually SRU p
Milestoning, since we should try to not drop the ball on this bug; I
will need to revisit the mailing list thread and how exactly we do the
naming for these devices.
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
** Changed in: systemd (Ubu
** Changed in: isc-dhcp (Ubuntu Xenial)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
** Changed in: initramfs-tools (Ubuntu Xenial)
Milestone: None => xenial-updates
** Changed in: initramfs-tools (Ubuntu Xenial)
Assignee: (unassigned) => Mathieu Trudel
All non-MAAS remote rootfs -based test cases have been verified for
Yakkety now. Everything checks out. I will now do the last test case
remaining which is to do a standard (non-remote root) install and
upgrade to proposed packages to make sure standard installs aren't
broken.
** Description chang
d-i install with proposed enable also passed. As far as I am concerned,
this is verification-done for *Xenial*.
We may still want to wait for Jason DeRose's input on the SRU.
** Description changed:
initramfs' configure_networking function uses ipconfig to configure the
network.
ipconfig do
I've done all the non-MAAS test cases on xenial so far except for
completing an installation with proposed enabled (it's a little more
complicated); things are working as expected. I removed the "Booting an
iSCSI remote root via IPv6 (no ip6=, d-i use case)" as it makes no sense
-- d-i will not set
** Description changed:
initramfs' configure_networking function uses ipconfig to configure the
network.
ipconfig does not support dhcpv6. See:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164
Related bugs:
* bug 1229458: grub2 needed changes
* bug 1621615: network not
jderose is a community contributor. I don't know how to reach him other
than over IRC/Launchpad (which I did). I removed that entry for now, but
we should have his input on that SRU as one more data point to validate
that we're not breaking things that worked.
--
You received this bug notificatio
** Description changed:
initramfs' configure_networking function uses ipconfig to configure the
network.
ipconfig does not support dhcpv6. See:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164
Related bugs:
* bug 1229458: grub2 needed changes
* bug 1621615: network not
** Description changed:
initramfs' configure_networking function uses ipconfig to configure the
network.
ipconfig does not support dhcpv6. See:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164
Related bugs:
* bug 1229458: grub2 needed changes
* bug 1621615: network not
This isn't how VPNs are supposed to work. I understand that things get
incredibly complicated in this case, but they are complicated in the
first place.
Some things to watch out for:
- IPv4 and IPv6 should both be configured the same way; you want either
both to be set to split-tunnelling ("Use
** Tags removed: verification-done
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1633479
Title:
dhclient does not wait for ipv6 d
** Changed in: initramfs-tools (Ubuntu)
Status: New => Triaged
** Changed in: initramfs-tools (Ubuntu)
Importance: Undecided => Medium
** Changed in: initramfs-tools (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
--
You received this bug not
ipv6 changes for isc-dhcp running in the initramfs are in zesty, too.
** Changed in: isc-dhcp (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bug
initramfs-tools fixed for ipv6 are already in zesty.
** Changed in: initramfs-tools (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpa
If we want to do this, let's use ip6=stateless or ip6=dhcp rather than
only/only-S.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1632808
Title:
configure_network
Verification completed on yakkety as well; the revert is working as
expected.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
ht
scotte, Jason, could either of you verify that the revert returned
initramfs-tools in a state that works for you?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/16314
d) is "unavoidable" if we're do make use of ROUNDTTT, and to be frank,
seems like a reasonable side-effect. There's only so much that can be
done to handle both IPv4 and IPv6 in the initramfs, and I think we can
live we a few extra seconds booting. Furthermore, systems that do not
get their IP addr
Fixed in zesty:
https://launchpad.net/ubuntu/+source/isc-dhcp/4.3.3-5ubuntu17
** Changed in: isc-dhcp (Ubuntu Zesty)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubunt
ed in initramfs-tools, and as such the affected code paths would
not be run.
** Affects: isc-dhcp (Ubuntu)
Importance: High
Assignee: Mathieu Trudel-Lapierre (cyphermox)
Status: In Progress
** Affects: isc-dhcp (Ubuntu Xenial)
Importance: High
Assignee: Mathieu Trudel-Lap
The changes were reverted.
** Changed in: initramfs-tools (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1633643
Title:
** Description changed:
[Impact]
-
- * 0.122ubuntu8.3 of initramfs-tools no longer correctly processed
- ip=dhcp or ip=:eth0:dhcp
-
- * Regression-updates
-
- * The fix better parses the ip= command line argument.
+ * initramfs-tools SRUs introduced regressions in ip= syntax, which ca
** Changed in: initramfs-tools (Ubuntu)
Status: Fix Released => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1621507
Title:
initramfs-tools configure
Reopening, as we reverted the SRU (but will also fix things in Zesty and
Yakkety with a better method than overriding ip=)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/162
*** This bug is a duplicate of bug 1621507 ***
https://bugs.launchpad.net/bugs/1621507
** This bug has been marked a duplicate of bug 1621507
initramfs-tools configure_networking() fails to dhcp ipv6 addresses
--
You received this bug notification because you are a member of Ubuntu
Touch
Seems to me like we're at the point where considering a straight revert
of the SRU would be in order (and I'm certainly considering it for the
short term), in order to move forward again at a later time when this is
more solid -- not that the end goal is still going to be happening
(though maybe no
I managed to reproduce it once trying to move from the on-laptop miniDP
connector to the dock's full-size DP connector -- then I had a black
background (well, no backgound) and the window trails.
It looks to me like an issue in compiz, but it might really be X. In
doubt, I'm not going to change th
I've tried this on my own Lenovo Thinkpad X230 (also a 2306CTO), and I
can't reproduce the issue at all. I've tried both the dock's full-sized
DP connector and miniDP on the laptop itself (undocked), both work with
no issues at all, and no artifacts on the external screen (or the panel,
for that ma
Could you please try with a different monitor or share more of the
details of how you are using this, such as which resolution is picked?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.n
** Also affects: initramfs-tools (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1631474
Title:
No netwo
If you have issues with wireless not coming up after suspend, please run
'sudo iw dev wlan0 scan', and see if the applet then changes (it may
take a few seconds) to wireless and displays the list of APs. It does
not seem to me like any other workarounds are likely to work for
everyone.
If you have
If you're seeing the wrong icon in nm-applet, please file *YOUR OWN* new
bug report, and write the number here. Me-too's distract developers from
being able to understand what the problem is, because many people have
slightly different issues that all look similar.
As we understand it, the origina
This bug was fixed in the package e2fsprogs - 1.43.3-1
---
e2fsprogs (1.43.3-1) unstable; urgency=medium
* Fix e2fsck's handling of timestamps on 32-bit system (Closes: #836559)
* E2fsck will sanity check and repair the extra isize fields in inodes
and the superblock.
* Fix
System boots correctly with the new initramfs-tools. Verification-done.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://
Assignee: Mathieu Trudel-Lapierre (cyphermox)
Status: In Progress
** Affects: initramfs-tools (Ubuntu Xenial)
Importance: Critical
Assignee: Mathieu Trudel-Lapierre (cyphermox)
Status: In Progress
** Affects: initramfs-tools (Ubuntu Yakkety)
Importance: Critical
Blocker:
Checking support status of binary dependencies...
* libautopilot-qt binary and source package is in universe
* python3-autopilot binary and source package is in universe
Now, we might not want mediaplayer-app-autopilot in main, it seems like
only mediaplayer-app is really needed there?
Found some lintian warnings; but I wouldn't consider them blockers (but
please see about fixing them):
N: Processing binary package mediaplayer-app-autopilot (version
0.20.5+16.10.20160921-0ubuntu1, arch all) ...
I: mediaplayer-app-autopilot: extended-description-is-probably-too-short
N:
N:
** Also affects: mediaplayer-app (Ubuntu)
Importance: Undecided
Status: New
** Changed in: mediaplayer-app (Ubuntu)
Status: New => In Progress
** Changed in: mediaplayer-app
Assignee: Mathieu Trudel-Lapierre (cyphermox) => (unassigned)
** Changed in: mediaplay
)
Status: New => In Progress
** Changed in: klibc (Ubuntu Yakkety)
Status: New => In Progress
** Changed in: klibc (Ubuntu Xenial)
Status: New => In Progress
** Changed in: klibc (Ubuntu Yakkety)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
** Chang
I still see this issue from lintian:
I: libcontent-hub0: hardening-no-fortify-functions
usr/lib/x86_64-linux-gnu/libcontent-hub.so.0.2.0
However, as discussed the -D_FORTIFY_SOURCE=2 option is properly passed at
build time, and we no longer have the lintian warning about bindnow, which
seems t
gt; In Progress
** Changed in: isc-dhcp (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
** Changed in: isc-dhcp (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is s
N: Processing binary package libcontent-hub0 (version
0.2+16.10.20160830-0ubuntu1, arch amd64) ...
I: libcontent-hub0: hardening-no-bindnow
usr/lib/x86_64-linux-gnu/libcontent-hub.so.0.2.0
I: libcontent-hub0: hardening-no-fortify-functions
usr/lib/x86_64-linux-gnu/libcontent-hub.so.0.2.0
N: Pro
** Changed in: initramfs-tools (Ubuntu)
Status: New => Triaged
** Changed in: initramfs-tools (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to klibc in Ubuntu.
https://bugs.laun
** Changed in: network-manager (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: network-manager (Ubuntu Xenial)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, whi
Looks good to me; thanks. MIR approved.
** Changed in: unity-notifications (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-notifications in
Ubuntu.
https://bugs.launchpad.net
** Package changed: grub2 (Ubuntu) => fontconfig (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/1614840
Title:
Fontcaching takes long and cache seems damaged
** Changed in: ubiquity (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1611010
Title:
yakkety desktop - non-english instal
al) or we'll need to modify debconf-
apt-progress and python-apt to account for the changes.
** Changed in: ubiquity (Ubuntu)
Status: Confirmed => In Progress
** Changed in: ubiquity (Ubuntu)
Assignee: Ubuntu Installer Team (ubuntu-installer) => Mathieu
Trudel-Lapierre (cyph
Please provide any extra information you can to reproduce and debug this
issue. I can't reproduce it. If both IPv4 and IPv6 are set to not take
the default route, things are behaving correctly here; just like the DNS
settings are correctly configured when no split-tunnelling is in use at
all.
Also
It appears like bindnow isn't enabled; please see if it's feasible to
enable this security feature:
I: qtdeclarative5-unity-notifications-plugin: hardening-no-bindnow
usr/lib/x86_64-linux-gnu/unity8/qml/Unity/Notifications/libnotifyclientplugin.so
I: qtdeclarative5-unity-notifications-plugin: har
** Changed in: unity-notifications (Ubuntu)
Status: New => In Progress
** Changed in: unity-notifications (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, wh
What is the state of this MIR? Is it ready for another round of review?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-download-manager in
Ubuntu.
https://bugs.launchpad.net/bugs/1488425
Title:
[MIR] ubuntu-download
I was pointed at this bug by Stéphane, and looked again with some extra
logging patched in. I'm under the impression that NM is doing exactly as
it's told, which also means dnsmasq will do the same: it's simply not
configuring a "global" nameserver to go with the per-domain ones.
>From what I can
In general, please run 'sudo iw dev wlan0 scan' (or a variation of this
command with the right interface name for your system). Your system
should, from there, show scan results in the nm-applet menu.
If this *does not* solve your issue, please file a new bug report, and
report here what the numbe
The linked upstream bug was gnome-bugs #767317, removing for now until
we can isolate *one issue per bug*, rather than be looking at multiple
different things all dumped in one large heap of comments.
Again, if you think you're seeing this issue, please file *your own*
bug; it's easy for developer
Joakim, please file your own bug report (or point to yours if you
already created one). Despite things looking similar, it doesn't mean
it's the same issue. There are many different failure scenarios for
NetworkManager and wireless devices, some of which are caused by devices
failing to scan approp
Blockers:
- I'm concerned about the number of bugs open; we should have an idea whether
they are all really still issues. There are a few older bugs with no response
at all, or no change in months.
- Security team should explicitly sign-off on the review that was previously
done, since this pa
I've maintained NetworkManager for a while, and routinely use OpenVPN
for various things. Pushing nameservers from the openvpn server to the
client works as intended, as far as I can tell. If you use the default
settings, which I believe are to tunnel everything through the VPN, you
will only use t
** Tags removed: block-proposed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to packagekit in Ubuntu.
https://bugs.launchpad.net/bugs/1496292
Title:
Needs to be ported to packagekit 1
Status in aptdaemon package in Ubuntu:
The only remaining unknown is whether the new packagekit might break
click, snap or other such other software provider.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to packagekit in Ubuntu.
https://bugs.launchpad.net/bugs/1496
** Changed in: ubiquity (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to console-setup in Ubuntu.
https://bugs.launchpad.net/bugs/1578285
Title:
Ubiquity 16.10.1 fails at k
** Also affects: console-setup (Ubuntu Yakkety)
Importance: High
Assignee: Mathieu Trudel-Lapierre (cyphermox)
Status: In Progress
** Changed in: console-setup (Ubuntu Xenial)
Status: New => Fix Released
** Changed in: console-setup (Ubuntu Xenial)
Status:
** Description changed:
+ [Impact]
+ Regression in console-setup 1.108ubuntu15.1 in xenial-proposed which
introduced a dependency loop caused logins to fail in around 10% of boots.
+
+ [Test case]
+ 1) reboot
+ 2) attempt to login
+
+ In the failure case, the system will display an error messag
** Changed in: console-setup (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to console-setup in Ubuntu.
https://bugs.launchpad.net/bugs/1591622
Title:
Can't login to system, sy
** Changed in: network-manager (Ubuntu)
Status: New => In Progress
** Changed in: network-manager (Ubuntu)
Importance: Undecided => Medium
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
--
You received this bug not
We carry the mentioned commit in Xenial and yakkety now.
** Changed in: network-manager (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs
Public bug reported:
Currently, NM will write all search domains to both any DNS-handling
plugins running, and also to resolv.conf / resolvconf; in all cases.
The issue is that doing so means that in the split-DNS case on VPNs, you
might get a negative response from all nameservers, then a new re
This is a regression in proposed, not updates.
** Tags removed: regression-update
** Tags added: regression-proposed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to console-setup in Ubuntu.
https://bugs.launchpad.net/bugs/159
ntu Xenial)
Importance: Undecided => High
** Changed in: pkgsel (Ubuntu Xenial)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
** Changed in: unattended-upgrades (Ubuntu Xenial)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
--
You recei
sel (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1585771
Title:
Automatic se
That's really unattended-upgrades; not d-i itself.
** Package changed: debian-installer (Ubuntu) => unattended-upgrades
(Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.laun
It works, once you know you need to use that to substract from
something.
ie>
unmanaged=*,except:type:wifi
Will work correctly. Closing as Invalid.
** Changed in: network-manager (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Tou
** Changed in: network-manager (Ubuntu)
Status: New => In Progress
** Changed in: network-manager (Ubuntu)
Importance: Undecided => Medium
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
--
You received this bug not
Public bug reported:
NetworkManager currently only reads configuration files from
/etc/NetworkManager/NetworkManager.conf and /etc/NetworkManager/conf.d.
It should be possible to also read and write config from
/run/NetworkManager/conf.d; so that any changes to the system
configuration done by NM
Public bug reported:
This should work to set any device that are not wifi to be unmanaged.
[keyfile]
unmanaged=except:type:wifi
It doesn't. It needs to work. :)
** Affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because y
** Also affects: ubiquity (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ubiquity (Ubuntu)
Status: New => In Progress
** Changed in: ubiquity (Ubuntu)
Importance: Undecided => Medium
** Changed in: ubiquity (Ubuntu)
Assignee: (unassigned) => Mathi
** Changed in: openssl (Ubuntu Precise)
Status: New => Invalid
** Changed in: openssl (Ubuntu Trusty)
Status: New => Invalid
** Changed in: sbsigntool (Ubuntu Precise)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
** Changed in: sbsigntool (Ubun
Cip Man, you're seeing a different issue with the wireless device. This
isn't the same bug.
What gets fixed here is that wireless devices may be seen as *ethernet*
rather than wireless, because of confusion in NM in detecting the device
type -- it doesn't mean you definitely would have a list of w
That seems wrong. This change was done because you might otherwise get
stray SCAN_DONE signals when the scan is in progress -- we should still
be getting a SCAN_DONE signal later from the supplicant when we get the
scan results. The issue here is that the scan may not be done correctly
on return fr
** Description changed:
+ [Impact]
+ Debconf prompts are incredibly ugly on virtual console; colors are off from
the "official" aubergine background. This applies to Ubuntu specifically since
other flavors may specify a different color scheme that may not be affected.
+
+ [Test case]
+ 1) sudo
** Description changed:
+ [Impact]
+ Console font and other configs from kbd/console-setup may not be applied on
boot.
+
+ [Test case]
+ 1) Configure a keymap / key translation table.
+ 2) Boot the system
+ 3) Console should have the key translation table applied.
+
+ [Regression potential]
+ M
** Changed in: console-setup (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to console-setup in Ubuntu.
https://bugs.launchpad.net/bugs/1576893
Title:
console colors are not
** Description changed:
+ [Impact]
+ Keymaps are not correctly set on virtual console (in gettys)
+
+ [Test case]
+ Set keymap, using us, intl variant. Test that dead keys behave correctly (ie.
hitting an apostrophe and then e yields "é" rather than "'e".
+
+ [Regression potential]
+ System tha
** Changed in: console-setup (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to console-setup in Ubuntu.
https://bugs.launchpad.net/bugs/1572697
Title:
broken symlink console
Status: New => In Progress
** Changed in: console-setup (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: console-setup (Ubuntu)
Status: In Progress => Fix Released
** Changed in: console-setup (Ubuntu Xenial)
Assignee: (unassigned) => Mathieu Trudel-L
Nice catch.
There is a keyboard-setup.init script; but that's not being installed
either because for upstart, all these were replaced by a single upstart
job to deal with the keyboards.
The net result appears to be that keymap is not correctly set in a VT --
I'll look to find other reports of thi
** Description changed:
+ [Impact]
+ Validating signature using sbsigntool for EFI binaries on Precise and Trusty.
+
+ [Test case]
+ 1) pull-lp-source shim-signed
+ 2) sbverify --cert MicCorUEFCA2011_2011-06-27.crt shim.efi.signed
+
+ [Regression potential]
+ Complex signing scenarios may pass v
** Also affects: openssl (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: sbsigntool (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: openssl (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: sbsigntool (Ubuntu
*** This bug is a duplicate of bug 1477350 ***
https://bugs.launchpad.net/bugs/1477350
** This bug has been marked a duplicate of bug 1477350
Rgression building sbsigntool with binutils >= 2.22-6ubuntu1.2 in precise
--
You received this bug notification because you are a member of Ubuntu
301 - 400 of 734 matches
Mail list logo
