https://github.com/systemd/systemd/issues/8686 seems related.
** Bug watch added: github.com/systemd/systemd/issues #8686
https://github.com/systemd/systemd/issues/8686
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
xserver-xorg now has an apport hook. So in order of ubuntu-bug to work,
it is necessary to have python3-apport installed, per LP: #1730035.
Definitely not a bug.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
@cran: you can wait for your mirror, or download the debs from
archive.ubuntu.com.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libva in Ubuntu.
https://bugs.launchpad.net/bugs/1756380
Title:
vaapi VP9 hardware decoding
I edited /etc/gdm3/custom.conf and put WaylandEnable=false back in (I
had it enabled before to test). Greeter came right up on reboot and my
external monitor works again.
What is curious is that my session choice in both cases was/is Gnome on
Xorg. So is it possible there's some change in the
Hi Daniel,
On Mon, Mar 5, 2018 at 9:56 PM, Daniel van Vugt
<daniel.van.v...@canonical.com> wrote:
> Nish,
>
> To figure the problem out you will need to be logged in already while
> it's happening(!), so..
Yeah, tricky when the machine physically seems to be hung (no
touchpad,
But if I plug in my usb-c dongle, it immediately freezes and the fans
start to spin. Unplugging the dongle has no effect. Suggestions for
debugging?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
I just rebooted again and without hitting any keys, it did come up to
the greeter without issue.
--
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.net/bugs/1753576
Title:
GDM freeze
Hrm, I'm not entirely sure what just changed. I rebooted and unlike
before, I hit Escape at the splash screen, and the GDM greeter showed up
just fine (after hitting Escape again to go back to graphics mode). I'll
see if that's reproducible shortly.
--
You received this bug notification because
Oh also the splash screen correctly displays on both monitors, so i
think it must be in X that the multiple displays fail.
I'll see if I can figure out how to get to a temrinal.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
@vanvugt: no, as it's not crashed (afaict), it's just 100% cpu (based
upon fans). Numlock is still responsive as is sysrq, but i can't get to
any ttys (that is, ctrl+alt+f2, etc don't seem to work).
I even tried booting with 'text' and annoyingly gdm still started (I
might be misremembering how
Public bug reported:
Here is what I know so far:
After rebooting this morning on Bionic (after receiving the gnome theme
updates, I think), upon reboot the CPU pegs and the greeter is never
displayed (there is a graphics system running, but I'm not sure what
it's doing). My num lock / caps lock
Public bug reported:
While not necessarily a critical issue for the Ubuntu keyrings, as
Debian uses newer keys periodically, it becomes impossible with the
default keyrings to verify the latest Debian archive files.
It seems reasonable to ensure the keyring contents in all releases are
the same,
+1 for the issue.
Its broken for some VPN cases. Maintainer please note that some VPN
application updates DNS with resolvconf package and removes those
setting on exist. This is breaking the DNS resolution in some rare
cases.
--
You received this bug notification because you are a member of
** Changed in: openexr (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 openexr in Ubuntu.
https://bugs.launchpad.net/bugs/1742243
Title:
Please merge with Debian
linked:
https://code.launchpad.net/~nacc/ubuntu/+source/openexr/+git/openexr/+merge/335904
** Changed in: openexr (Ubuntu)
Assignee: (unassigned) => Nish Aravamudan (nacc)
** Changed in: openexr (Ubuntu)
Status: New => In Progress
--
You received this bug notification
Public bug reported:
TBD
** Affects: openexr (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openexr in Ubuntu.
https://bugs.launchpad.net/bugs/1742243
Title:
Ubuntu)
Assignee: (unassigned) => Nish Aravamudan (nacc)
** Changed in: lvm2 (Ubuntu)
Milestone: None => ubuntu-18.02
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/
Does the Ubuntu php build use the bundled tzdata? A lot of stuff comes from
the system not the source (e.g, pcre iirc)
On Dec 1, 2017 18:40, "Eric Desrochers"
wrote:
> Same thing with new php pkg release in debian/unstable (php - 7.1.12-1).
> It still displays
Is this already fixed in proposed (MRE to latest upstream php 7.0 and
7.1)?
On Dec 1, 2017 03:48, "Bug Watch Updater" <1734...@bugs.launchpad.net>
wrote:
> ** Changed in: php7.0 (Debian)
>Status: Unknown => New
>
> --
> You received this bug notification because you are subscribed to
Just to be clear, this isn't a bug based upon comment 1 but new tasks
were opened in comment 2?
If it's purely an SRU regression in tzdata that should be figured out.
Im guessing this is an upstream php issue. Has it been fixed there?
--
You received this bug notification because you are a
... ERROR
I'll see if it might need some restrictions (or if the runner env
changed)?
-Nish
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1720126
Title:
[ip link
If someone is interested in the proper upstream fixes, please file a new
bug and we will need to fix bionic and prepare a distinct SRU for the
existing releases.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in
On Wed, Nov 1, 2017 at 7:15 AM, Jan Gutter <1720...@bugs.launchpad.net> wrote:
> @arges
>
> Hi, would you need any more testing from us?
Nope, your part is done. All SRUs have to bake for 7 days in -proposed
to shake out regressions.
--
You received this bug notification because you are a
On 20.10.2017 [08:24:37 -0700], Nish Aravamudan wrote:
> On 20.10.2017 [07:18:15 -], Jan Gutter wrote:
> > I had a look at the two proposals and could not spot any obvious
> > mistakes:
> >
> > - the correct upstream git commit has been cherry-picked
> &
On 20.10.2017 [07:09:00 -], Jan Gutter wrote:
> I concur with option 2), unnecessary deviation will just cause
> confusion.
Thank you for confirming that!
> Regarding the other buffer sizes, the last time I looked they were
> mostly OK. The issue reared its head in this particular case
shepherding this one through!
You're welcome, I'll upload them both today.
Thank you and Monique for filing the SRU template properly!
-Nish
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bu
I have set up two MPs with the adjustments (it looks like Monique's
latest debdiffs followed path 2) from my previous comment already) to
the DEP3 headers that I think make the most sense. Please take a look at
them and if you approve the changes I will upload them.
I note also there are a number
On 19.10.2017 [09:35:19 -], Jan Gutter wrote:
> @nacc
>
> Thanks so much for the explanation. I also found
> https://wiki.ubuntu.com/ServerTeam/KnowledgeBase#Merge_Proposals_and_Reviewing
> that details a bit more of the internal processes. As relative outsiders
> to the Ubuntu process, I'd
the debdiffs?
Thanks,
Nish
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1720126
Title:
[ip link] Message truncated error for large number of passthrough VFs
Status
cherry-pick 72b365e83
$ git ubuntu build-source
And it should spit out a commit that has the quiltify'd and
changelogify'd result that you can use as a base or to submit.
Feel free to find me on IRC if you want some more pointers.
In the meanwhile, I'll try and look at Monique's debdiffs this week.
@jangutter: I'm not sure why you built from source? I assume you
actually tested the version in 17.04 and it worked.
The proper solution is to backport the Debian change to xenial and
trusty, most likely. A git repository that can be used with `git-ubuntu`
(sudo snap install --classic
** Also affects: iproute2 (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: iproute2 (Ubuntu Zesty)
Importance: Undecided
Status: New
** Changed in: iproute2 (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: iproute2 (Ubuntu Xenial)
** Description changed:
+ [Impact]
+
+ A severe regression has been found in the GTK 3 variant of Gvim.
+ Upon start-up, it crashes immediately with multiple failed
+ assertions.
+
+ A second related, but less severe problem may occur when opening
+ new tabs within the GTK 3 variant of Gvim.
+
in the container image by
default is checked that this doesn't regress going forward :)
** Changed in: lvm2 (Ubuntu)
Assignee: Nish Aravamudan (nacc) => (unassigned)
** Changed in: open-iscsi (Ubuntu)
Assignee: Nish Aravamudan (nacc) => (unassigned)
--
You received this bug notification becau
Sponsored to artful.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to logrotate in Ubuntu.
https://bugs.launchpad.net/bugs/1709670
Title:
logrotate never recovers if the statefile is corrupted
Status in logrotate package
Unsubscribing sponsors based upon IRC discussion with rharper:
10:57 < nacc> rharper: is LP: #1671951 actually ready to sponsor?
10:57 < ubottu> Launchpad bug 1671951 in systemd (Ubuntu) "networkd should
allow configuring IPV6 MTU" [Medium,New]
1), 2) and 3) done and approved/merged.
Now the AAs need to do the actual pocket copy & promotion for the older
releases.
** Changed in: ubuntu-meta (Ubuntu Xenial)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
** Changed in: ubuntu-meta (Ubuntu Zesty)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1700826
Title:
please include
** Changed in: ubuntu-meta (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 ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1700826
Title:
please include numactl
Here is my understanding of next steps:
1) A MP should be submitted against the Artful seeds to update the 17.10
image(s) (which have not been release-published yet). On the next run, that
will lead to numactl showing up in main in 17.10.
2) A MP should be submitted against the Zesty seeds to
This is bit of a funky SRU (IMO). It seems like we want version 2 (from
the linked repository) in all releases > 12.04. However, given that is
not yet present in any release != 12.04, I'm not sure we need to worry
about the exact version (that is, they can all be 2?).
My immediate feedback is the
@zwets, to be clear, file the bug at: https://bugs.launchpad.net
/~ubuntu-motd
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to base-files in Ubuntu.
https://bugs.launchpad.net/bugs/1701068
Title:
motd.ubuntu.com currently
@zwets, would you be willing to file a new bug? It's basically a clarity
issue on the messsage itself. It isn't actually saying you are running
16.10 or 17.04 or anything else. It's just letting you know that 16.10
goes EOL soon. So update your machines. But not necessarily that this
particular
@zwets: agreed, I see that as well. I assume the server side of
motd.ubuntu.com is not using the USER_AGENT lsb value correctly?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to base-files in Ubuntu.
Sponsored the upload to Trusty.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/1593907
Title:
ntpdate startup routine prevents ntp service from launching up on
Ubuntu 16.04
@kai-holthaus: after editing the service file, did you issue a `sudo
systemctl daemon-reload` ?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1569925
Title:
Shutdown
@Kai: Hrm, that is odd -- was your 16.04 system the fresh install or an
upgraded one?
The lines I pasted in #49 are supposed to be present in 16.04 (afaict).
If they don't, can you provide `apt policy open-iscsi` in a pastebin?
And can you test if changing those lines to match fixes the issue
@Kai: In xenial, open-iscsi.service should have the following lines
alreadY
Wants=network-online.target remote-fs-pre.target iscsid.service
After=network-online.target iscsid.service
Can you confirm that is the case on your system?
--
You received this bug notification because you are a member
** Also affects: net-tools (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: net-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
@kai-holthause or @gimpeystrada: would either of you be able to test
with the daily artful (17.10) ISO?
@kai-holthause: I think you did find a real ordering issue, nicely done
:)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
@kai-holthaus: also, afaict, that might mean you are hitting a
*different* bug (yay for so many bugs) in open-iscsi relative to
@gimpeystrada, as @gimpeystrada and others in this channel have said
they experience this issue with a fresh install of 16.04 (16.10 and
17.04 as well). That's ok, we can
@kai-holthaus: Thank you for the excellent data point, again, and for
your willingness to provide the data!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1569925
Title:
@kai-holthaus: thank you for responding so quickly. Can you set up a
persistent journal as described in c#8 and provide the journal as
mentioned in that comment for the failed shutdown?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
@gimpeystrada: Thank you for providing your journal logs (in the future,
providing the raw journal file is better, as then we can run
`journalctl` on it locally). From the logs:
Apr 26 08:52:13 ICTM1612S02H1 iscsiadm[3234]: iscsiadm: initiator reported
error (8 - connection timed out)
Apr 26
** Changed in: openssh (Ubuntu Trusty)
Status: Confirmed => Triaged
** Tags added: server-next
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1334916
Title:
** Also affects: openssh (Ubuntu Trusty)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1334916
Title:
sshd-ConsoleKit
*** This bug is a duplicate of bug 1334916 ***
https://bugs.launchpad.net/bugs/1334916
Hello and thank you for filing this bug report. I've opened a task in
the other bug for Trusty and that is the best place to follow up on it.
** This bug has been marked a duplicate of bug 1334916
Hello and thank you for filing this bug report.
It appears you have a local configuration error, as indicated by sshd:
Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255:
/etc/ssh/sshd_config: line 66: Bad configuration option: X11UseForwarding
/etc/ssh/sshd_config:
** Changed in: openssh (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1693944
Title:
package openssh-server 1:7.2p2-4ubuntu2.2
** Changed in: dnsmasq (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1682136
Title:
dnsmasq bad hex constant with 2 mac
On Wed, May 24, 2017 at 1:45 PM, Scott <1569...@bugs.launchpad.net> wrote:
> Fresh install 16.04 download ISO from ubuntu
> Can confirm this issue as well.
> If I manually log out of the iscsi session reboot no issue
Interesting data point.
> If I am logged into iscsi session reboot hangs. Need
Thank you for reporting this bug. I will add it to the server team
backlog, as it does appear to be a real issue.
** Changed in: openvpn (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Translated from DpkgTerminalLog:
Preparing to unpack ... / libnss3_2% 3a3.28.4-0ubuntu0.17.04.1_amd64.deb ...
Unpacking libnss3: amd64 (2: 3.28.4-0ubuntu0.17.04.1) about (2:
3.26.2-1ubuntu1) ...
Preparing to unpack ... / libxslt1.1_1.1.29-2ubuntu0.1_amd64.deb ...
Unpacking libxslt1.1: amd64
I am unable to reproduce this issue. Per the changelog, sysv-rc (from
src:sysvinit) dropped the invoke.rc bits in 2.88dsf-59.3ubuntu1:
sysvinit (2.88dsf-59.3ubuntu1) xenial; urgency=low
* Dropped various changes for invoke.rc which has moved to
init-system-helpers.
# apt install
Hello and thank you for filing this bug report.
Can you provide (perhaps as attachments if needed) an example command
and output that show the exact issue?
Please mark it as New once you have done so.
** Changed in: rsync (Ubuntu)
Status: New => Incomplete
--
You received this bug
Thank you very much for filing this bug report. It seems like it is a
real issue and I will place it on the Server Team's backlog for now.
** Changed in: dnsmasq (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Hello and thank you for filing this bug report. 12.04 has gone EOL in
the meanwhile, though. Does this issue occur with Trusty or later?
** Changed in: dnsmasq (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
In Artful, we have (running with -proposed for open-iscsi and lvm2):
● snapd.service loaded failed failed Snappy daemon
● snapd.socket loaded failed failed Socket activation for snapp
● systemd-journald-audit.socket loaded failed failed Journal Audit
lvm2 fix is in 2.02.168-2ubuntu1 in artful.
** Changed in: lvm2 (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: open-iscsi (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
** Changed in: lvm2 (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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1576341
Title:
systemd in degraded state on
@sdeziel, afaict, that is an upstream fix committed,but not the ubuntu
package in artful.
** Changed in: shadow (Ubuntu)
Status: Fix Committed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shadow in
Ubuntu)
Assignee: (unassigned) => Nish Aravamudan (nacc)
** Changed in: lvm2 (Ubuntu)
Status: Confirmed => In Progress
** Changed in: lvm2 (Ubuntu)
Assignee: (unassigned) => Nish Aravamudan (nacc)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
On 08.05.2017 [11:25:03 -], Balint Reczey wrote:
> >> 1.b i'd like another way to do that, but not sure what a better way would
> >> be.
> >
> > Yeah, I spent some time looking at the CPC generater and it seems like
> > this is pretty hard-coded:
> >
> > 999-cpc-fixes.chroot:
> > ##
** Changed in: dlm (Ubuntu)
Assignee: (unassigned) => Nish Aravamudan (nacc)
** Changed in: lvm2 (Ubuntu)
Assignee: (unassigned) => Nish Aravamudan (nacc)
** Changed in: ocfs2-tools (Ubuntu)
Assignee: (unassigned) => Nish Aravamudan (nacc)
--
You received this bug not
Thank you for the prompt testing. I'm marking a few potential src
packages where the actual issue might lie.
** Also affects: accountsservice (Ubuntu)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Changed in:
Lukas, thank you for the detailed information. However
On Mon, Apr 24, 2017 at 9:33 AM, Lukas Dzunko wrote:
> Hello Paul. DNS leak mean that DNS queries still hit local DNS server
> while VPN connection is active. DNS resolver should query only DNS
> servers defined by VPN while
https://anonscm.debian.org/cgit/resolvconf/resolvconf.git/commit/?id=05a25d1d831ebe3955fb9641a3ba708bca68d35a
1.80 isn't out yet, so we should probably just backport the fix to the
affected releases.
** Also affects: resolvconf (Ubuntu Zesty)
Importance: High
Status: Confirmed
** Also
Hi Paul,
https://wiki.ubuntu.com/StableReleaseUpdates is the standard reference.
It takes at least 7 days in -proposed before the SRU team will release
it.
Thanks,
Nish
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
@Alberto,
why did you mark the samba task critical? As far as I can tell, there is
no bug in samba itself, all of these bugs are in update-manager and just
have been seen with various binary packages which we're marking this bug
and then indicating they are invalid.
** Changed in: samba (Ubuntu)
** Tags removed: verification-needed yakkety
** Tags added: verification-done-yakkety verification-needed-xenial
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1639776
On 29.03.2017 [03:19:16 -], Serge Hallyn wrote:
> Thanks, Nish. My thoughts:
>
> 1.a sounds good
Ack.
> 1.b i'd like another way to do that, but not sure what a better way would
> be.
Yeah, I spent some time looking at the CPC generater and it seems like
this is pretty h
Based upon c#6 unsubscribing ubuntu-sponsors.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to location-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1640320
Title:
FTBFS in zesty
Status in location-service package in
** Changed in: cyrus-sasl2 (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu.
https://bugs.launchpad.net/bugs/1672941
Title:
FTBFS with older versions of
I uploaded the fix today to 16.04 and 16.10, will need to go through the
SRU process.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1639776
Title:
dnsmasq fails to send
** Description changed:
+ [Impact]
+
+ * suspend/resume (which involves disconnection of network devices)
+ leads to dnsmasq failures.
+
+ [Test Case]
+
+ * suspend/resume on 16.04 or 16.10 when using dnsmasq, and see failures
+ upon resume.
+
+ [Regression Potential]
+
+ * The fix was
This is probably going to be tricky to debug as it's probably hardware
dependent.
Can you first run `sudo dmesg -C`, then suspend and resume and then
attach the output of `dmesg` ?
** Changed in: pm-utils (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because
: New
** Changed in: dnsmasq (Ubuntu)
Status: Triaged => Fix Released
** Changed in: dnsmasq (Ubuntu Yakkety)
Status: New => In Progress
** Changed in: dnsmasq (Ubuntu Xenial)
Status: New => In Progress
** Changed in: dnsmasq (Ubuntu Xenial)
Assignee: (unassigned
** Changed in: apt (Ubuntu)
Importance: Undecided => Wishlist
--
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/678440
Title:
"apt-get changelog" doesn't take source package
** Changed in: apt (Ubuntu)
Importance: Undecided => Low
--
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/1186924
Title:
"apt-get install taskname^" is not documented
This was fixed on c.u.c by using Julian's suggested mod_rewrite changes.
No changes are needed to extract-changelogs or apt.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
** Changed in: extract-changelogs
Status: In Progress => Invalid
** Changed in: apt (Ubuntu)
Status: New => Invalid
** Changed in: extract-changelogs
Assignee: Nish Aravamudan (nacc) => (unassigned)
--
You received this bug notification because you are a member
Thanks to juliank on IRC: https://gist.github.com/julian-
klode/600237d0b61cf92b01748b25cf5921d7 A potential configuration-only
change for old clients backwards-compatiblity.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Ok, the audit stuff was 'resolved' in LP: #1457054, where I think
everyone decided to agree that unprivileged containers didn't matter...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
heh, after a few more sips of coffee and actually reading the manpage,
my 1.d.1 is obviously incorrect because CAP_ADMIN_READ is not a
capability. So in effect it's masking out the audit socket :)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Wanted to level-set (and subscribing pitti and hallyn for their advice):
1) LXD unprivileged containers:
4 services in the Zesty daily are failed at start:
1.a) iscsid.service
This is because iscsid needs CAP_IPC_LOCK to run mlockall().
Unprivileged containers end up failing in the host
** Also affects: libnl3 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libnl3 in Ubuntu.
https://bugs.launchpad.net/bugs/1673491
Title:
[Zesty] libvirtd Segmentation
** Summary changed:
- fails in lxd container
+ systemd in degraded state on startup in LXD containers
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1576341
Title:
16.04:
$ lxc launch xenial x1
$ lxc file pull x1/etc/cloud/build.info -
build_name: server
serial: 20160211-034510
$ lxc exec x1 systemctl is-system-running
degraded
$ lxc exec x1 -- systemctl --state=failed
UNIT LOAD ACTIVE SUBDESCRIPTION
● dev-hugepages.mount
Did some digging on the mlockall failure:
/* we don't want our active sessions to be paged out... */
if (mlockall(MCL_CURRENT | MCL_FUTURE)) {
log_error("failed to mlockall, exiting...");
log_close(log_pid);
exit(ISCSI_ERR);
Any chance you've been able to reproduce this with 16.04 or later? the
upstart -> systemd differences are rather significant.
I wonder if upstart is not opening /dev/console for input early enough
or so.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
1 - 100 of 162 matches
Mail list logo