qemu 2.11 is in proposed
** Changed in: qemu (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1722495
Title:
[Ubuntu18.04] qemu gets a trap when give
qemu 2.11 is in proposed
** Changed in: qemu (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1723381
Title:
ubuntu18.04 - qemu segfaults when tries to
Linked two MPs which - if merged - will eliminate the ususal suspects
and leave the actual real cases for discussion on each MRE/SRU activity.
** Branch linked: lp:~paelzer/britney/hints-ubuntu-trusty-postgresqlMREs
** Branch linked: lp:~paelzer/britney/hints-ubuntu-xenial-postgresqlMREs
** Also
I'm not sure on the bug tasks, but the MPs will certainly go on the
queue of the SRU Team where they are at the right place.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1748161
Title:
improve brit
I see your debian bug and assume that should be the change, but here
gnome-themes-standard ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1748122
Title:
incorrect tools.conf template is shipped wit
Public bug reported:
On every postgres MRE we mention some regular failing tests.
Those were mostly caused by changes in the environment and fixes were done for
later Ubuntu releases but not SRUable.
We should not ask the release team to force them on every SRU but cover those
where it is correc
After a discussion with the Debian maintainer I agree to revert this change.
I uploaded chrony_3.2-2ubuntu3_source.changes [1] with that change.
[1]: https://launchpad.net/ubuntu/+source/chrony/3.2-2ubuntu3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
I discussed with Pitti, via adding the extra trigger of vagrant this will work.
So we will retry the tests originally triggered by distro-info and qemu but
with &trigger=vagrant%2F2.0.2%2Bdfsg-2 appended.
That would force it to pin the tested + vagrant from proposed and that should
work.
Full li
Version https://launchpad.net/ubuntu/+source/nova/2:17.0.0~b3-0ubuntu4
with a fix inbound (allow stderr for now).
Thanks James for the quick response!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/174
Public bug reported:
autopkgtest issue in vagrant-mutate
These tests are fairly new in vagrant-mutate (1.2.0-3)
* Add DEP-8 smoke test
by Antonio Terceiro on Thu, 02 Feb 2017 11:47:08
These tests curre
MP for the badtest to unblock the others in b-proposed for now [1].
@James / Corey - please take a look and ack there if ok with you, so that a
release team member can merge it.
[1]: https://code.launchpad.net/~paelzer/britney/hints-ubuntu-mask-nova-
for-oslo-policy-deprecation/+merge/337331
**
Public bug reported:
Nova fails in autopkgtest
autopkgtest [15:24:49]: test nova-daemons: [---
/usr/lib/python2.7/dist-packages/oslo_policy/policy.py:623: UserWarning: Policy
"os_compute_api:os-extended-volumes":"rule:admin_or_owner" was deprecated for
removal in 17.0.0. Reas
FYI:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-bionic/bionic/amd64/n/nova/20180207_152622_85443@/log.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
FYI Currently blocks:
- openssl
- python-oslo-policy
- qemu
- libvirt
- tntnet
- python-os-vif
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1748123
Title:
Policy "os_compute_api:os-server-usage":"r
FYI: The discussion in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889010
nicely outlined that we rely on those hooks in chrony.
That makes having them working critical for 18.04 to have it working correctly
for late or changing network topology.
We (cyphermox and me) discussed how I could
The changes in 1.5 are not too bad actually, furthermore we (mdeslaur
and me) found that without 1.5 we run into FTBFS https://bugs.debian.org
/cgi-bin/bugreport.cgi?bug=888133
So maybe after all we should go 1.5
** Summary changed:
- please merge virt-manager 1.4.3
+ please merge virt-manager 1
Public bug reported:
Contains quite some fixes, so we want to merge that for 18.04
There is 1.5 upstream, but maybe jumping to a new major should be 18.10 - and
for now focus on the stability of 1.4.3.
** Affects: virt-manager (Ubuntu)
Importance: High
Status: Triaged
** Changed i
Hi Tobias,
thanks for the update - it isn't 100% clear to me, does the ppa completely fix
the issue for you and also shows no other regression that you'd see?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
I asked around way more, but the TL;DR summary is that it never worked
and that no group is able or willing to do the verification for a full
SRU.
Backports would therefore be the option to go, but due to the (probably trivial
once you know the fix) complex build issue it not feasible for me to d
LGTM in regression checks, uploading ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746431
Title:
virt-aa-helper: do not fail with memory slots specified in guest xml
To manage notifications ab
LGTM in regression checks, uploading ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1747442
Title:
virt-manager fails to show virtual console: internal error: unable to
execute QEMU command 'ge
MP's for the seed changes are up:
platform:
https://code.launchpad.net/~paelzer/ubuntu-seeds/18.04-ntp-to-chrony-platform/+merge/337257
ubuntu:
https://code.launchpad.net/~paelzer/ubuntu-seeds/18.04-ntp-to-chrony-ubuntu/+merge/337256
Waiting now for:
- the general MIR team ack and setting to fix
Ok, this now has all prereqs resolved.
It is ready for the actual MIR + seed change.
Setting the state back to new (we reused the bugno, but it is for the MIR
actually)
So todo's now are:
@MIR Team ack and set fix committed
@Cpaelzer - Propose a seed change.
** Changed in: chrony (Ubuntu)
Branch is merged now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1644364
Title:
[MIR] htop
To manage notifications about this bug go to:
https://bugs.launchpad.net/htop/+bug/1644364/+subscriptio
Thanks Mathias - I was waiting on an ack on
https://code.launchpad.net/~paelzer/ubuntu-seeds/18.04-support-
htop/+merge/337201 which will trigger the mismatch then.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
Yeah it seems this was discussed plenty of times but not accepted that
(actually in any) way.
I tried around a bit and discussed with more people, but didn't find a good way
to hard control it.
Note: on IRC it also came up that a hot-attach fails with the message in
comment #23.
But on a guest
All fixes in Debian now, triggered a sync to make it an autosync again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1745922
Title:
sanlock 3.6.0-1 breaks on install missing sanlock user
To manage
That is the new libvirt 4.0 which gives the better messages.
Interesting.
Could be an arm specific lack of virtio (which is generic).
IIRC there was something that arm only worked with modern (virtio 1) and might
force this.
But I could be wrong (too old info).
The XML as well as the qemu comman
respin of the build available in the same ppa.
(Including the final fix as committed upstream)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746431
Title:
virt-aa-helper: do not fail with memory sl
FYI: Test build available at [1] in a ppa - grouped with another fix
that will be uploaded.
[1]: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3122
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
Already in 4.0.0-1 and thereby in Bionic already.
** Changed in: libvirt (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746875
Title:
integrate: libvirt:
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 ge
Hi Pnuke,
there is no dmesg attache, but since you added rules I assume you have no
denies anymore (can only guess).
Your log holds some warnigns which could be misconfiguration:
2018-01-31T23:14:55.066207Z 0 [Warning] Changed limits: max_open_files: 1024
(requested 5000)
2018-01-31T23:14:55.066
Found it
budgie-desktop-common: /etc/profile.d/10-budgie-desktop.sh
But I had no issue in it.
You might check if it is still in original state with
$ dpkg --verify budgie-desktop-common
Maybe the budgie developers can help you better, but I'd still expect a
local change that needs to be fixed.
-
Thank you for taking the time to report this bug and helping to make Ubuntu
better.
But sorry -why is this an apache2 bug?
The bug description isn't clear enough what is going on and [1] doesn't hold
useful info to spot what this is about.
[1]: http://lmgtfy.com/?q=magic+tag+apache
Since there
Hi Rene,
I think while the spamassasin upgrade fails the reason is in budgie desktop.
>From your log:
-su: 28: /etc/profile.d/10-budgie-desktop.sh: Syntax error: word unexpected
(expecting ")")
The spamassassin upgrade tries to execute something with a login.
That will source anything in /etc/p
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 ge
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 ge
Hi Sven,
>From your log:
insserv: warning: script 'jabber-irc' missing LSB tags and overrides
insserv: There is a loop between service LazyLibrarian and jabber-irc if stopped
insserv: loop involving service jabber-irc at depth 2
insserv: loop involving service LazyLibrarian at depth 1
insserv: St
Hi Janusz,
your logs show an issue in your configuration:
>From your log:
Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255:
/etc/ssh/sshd_config: line 89: Bad configuration option: OD
/etc/ssh/sshd_config: terminating, 1 bad configuration options
You'd have to fix up your custo
hank you for taking the time to report this bug and helping to make
Ubuntu better.
On upgrading a service this service has to be restarted to pick up the fixes.
Rather rarely a real issue occurs that the newer version does e.g. fail with
the formerly working configuration.
But most of the time wh
Upstream had a fix, but on another place.
So I unrolled the second part of the fix and used the upstream fix for an
ubuntu2 upload.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1747589
Title:
asyn
** Tags added: libvirt-18.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1747442
Title:
virt-manager fails to show virtual console: internal error: unable to
execute QEMU command 'getfd': No fil
** Summary changed:
- ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Unable to start the guest from
Ubuntu1804 KVM host machine
+ virt-aa-helper: do not fail with memory slots specified in guest xml
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
@MIR Team - we realized that this has no MIR Team ack yet, so I kindly
ask you as well to formally ack this MIR.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1644364
Title:
[MIR] htop
To manage no
Builds complete against new nss, also all other bugs we wanted are grouped.
New chrony uploaded to bionic - once passed we can do the seeding.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1744072
Tit
** Description changed:
--- MIR ---
1. Availability: The package is Ubuntu universe and builds for the
architectures it is designed to work on.
2. Rationale:
2.1 NTP in general is needed quite a lot, but we want to exchange ntpd
which is the current implementation in main w
** Changed in: freeipa (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746947
Title:
failing autopkgtest due to password issue by nss
To manage notifications
Linked lp:~paelzer/ubuntu-seeds/18.04-support-htop which is the proposed
seed change.
** Branch linked: lp:~paelzer/ubuntu-seeds/18.04-support-htop
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/164436
Released in Debian (thanks) and also 2.1.0-2 is in Bionic universe now.
That said all preconditions for the MIR ack to be ok are complete.
I'll prep a seed change to review (IIRC this was only adding to main,
not about shipping it on disk - let me know if intentions were
otherwise)
** Changed in:
FYI - For various downstream consumers of ncurse it is still compiled with
--with-abi-version=5.
As ncurse 6 was explicitly mentioned I'D assume it is abi ver 6, and that might
be the reason.
I have no insight in any planned transition, just wanted to let you know.
--
You received this bug noti
Public bug reported:
Hi,
I tried to fulfil to the promise that dpb made and tried to help with som
eolder proposed migrations.
After a while I found something I can actually help, so I looked at asyncpg.
Building version 0.13.0-1 was failing on armhf [1]
Error (all 198 of them):
E ValueError:
The fix is committed now but we collect a few more before an update.
Let me know if this is more urgent than I assume.
Until then please add the rule I listed above to
/etc/apparmor.d/usr.sbin.libvirtd and restart libvirtd, then you'll be
good.
** Changed in: libvirt (Ubuntu)
Status: Tria
Importance: Undecided => Medium
** Changed in: libvirt (Ubuntu)
Assignee: (unassigned) => ChristianEhrhardt (paelzer)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1747442
Title:
vir
Regression tests on ppa complete, I'm good to sponsor this once the security
updated are complete.
Since those are complex that might be a few more days.
I'll keep an open todo on this to check the status.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
After some updates for the 2018 version of the code uploaded both into
b-proposed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1747071
Title:
multiple issues with debian/copyright
To manage notif
This was a huge archaeological endeavor, but I managed to fix all that were
incomplete and a few more cleanups.
I updated licenses as needed, checked copyright and added it, grouped files
that now need new groups and so on.
For some obvious cases I did so with the help of copyright generators, bu
Public bug reported:
nss in version 3.35 in upstream changed [2] the default file format [1] (if no
explicit one is specified).
For now we reverted that change in bug 1746947 until all packages depending on
it are ready to work with that correctly.
This bug here is about to track when the rever
Built with said change - and now testing against the nss in the ppa (should all
work):
- install 4.4 (ppa) -> OK
- install 4.6 (proposed + ppa) -> OK
- old python call against 4.4 (ppa) -> OK
- new python call against 4.6 (proposed + ppa) -> OK
I dupped Corosync on here, so lets verify it fixes t
Hi Sosha,
the crash itself is in libxml2 so I add a bug task for that.
>From the libvirt POV this seems to be in a stage where it initializes its
>state drivers.
virStateInitialize iterates on drivers and calls stateInitialize of the
respective backend.
I can't see from your trace which that is
I was discussing this with Timo and he correctly pointed out that reverting [1]
might be enough.
This would allow to get all fixes of 3.35, but at the same time not run into
this bug here all over the place.
Building with that for some test runs.
[1]: https://github.com/nss-
dev/nss/commit/33b1
*** This bug is a duplicate of bug 1746947 ***
https://bugs.launchpad.net/bugs/1746947
Tracked down to an issue in nss changing defaults without consuming packages
not being ready.
Handling in nss, therefore marking as dup.
** This bug has been marked a duplicate of bug 1746947
failing au
For a better overview and to make a decision (as a +really version always sucks
to some extend) I did some tests:
- built nss 3.34 with the freebl3 change in ppa [1] as
2:3.35-2ubuntu1+really3.34-1ubuntu2
- set up some containers to test
- ran the sequence of installs/commands that freeipa tests
Actually both packages report 9 hits in lintian.
Well cleaning up both then ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1747071
Title:
multiple issues with debian/copyright
To manage notifica
Thanks for the ping, yes this all makes sense.
I cleaned the source as far as possible to just still allow the build we need
but not yet the copyright files (all refs were there in the base this was
copied and renamed from).
I'll clean up the file in a follow up upload.
--
You received this bu
** Also affects: nss (Ubuntu)
Importance: Undecided
Status: New
** Changed in: nss (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746947
Title:
fail
>From Debian - looks good:
We're packaging it and should have it in sid by end of next week.
That should be well before the import sync freeze for Bionic Beaver
(planned for March 1st).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
https://github.com/hishamhm/htop/issues/720 completed
2.1.0 released.
I opened Debian bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889634 to
poll if they would mind packing that soon.
If not we will likely go ahead for 18.04.
** Bug watch added: Debian Bug tracker #889634
https://bug
I want to decouple things a bit to make this bug less blocking, so I will:
1. prep a nss upload 2:3.35-2ubuntu1+really3.34.1-1ubuntu1
That will (for now) skip the nss merge that I meant to do to help while
coming by, but seems to
cause issues.
2. test that in a ppa if it would test correctl
Hi Timo,
according to my sniff tests it will fail later on in 4.6.2 as well.
It seems the new nss makes the crypto/passwords no more behave the way as
expected.
Of course the autopkgtest for 4.6.2 won't fail (as there is no old
cert8.db, so the call is skipped), but if there would be one (e.g. on
Public bug reported:
I wanted to request that ipxe-qemu-256k-compat inherits the MIR from ipxe where
it was absed on.
Since we knew this will show up we prepared (but were unable to open a bug
until the new queue was passed), thereby this MIR is a bit special and does not
hold the usual templat
@Seth - I copied some of our mail thread to make clear that you more or
less acked already, but I subscribed you to add an explicit ack here in
case needed.
@MIR Team - I think this is already "complete" other than the component
override that still has to be done. Also we have already a package i
** Summary changed:
- virsh api is stuck when vm is down with NFS borken
+ virsh api is stuck when vm is down with NFS broken
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746630
Title:
virsh api
Hi Steve - thanks for the ping,
Since Nish is back he is on that already.
He had MPs up last week, but not yet ready for review when I looked last.
Subscribing him here to ensure we all talked about the same thing.
** Changed in: kopanocore (Ubuntu)
Assignee: ChristianEhrhardt (paelzer
It also seems to have effect on bug 1746948 with corosync postinst.
I only thought "hey nss minor update, why not pull it in", but without
help to understand and resolve this I might be forced to go to a
3.35+really3.34 update to go back as I'm not enough of an nss expert to
resolve :-/
--
You r
Public bug reported:
Hi,
I was failed by autopkgtests of freeipa, but not the old "ip route output
changed" case.
Like:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/f/freeipa/20180201_161632_c9091@/log.gz
It essentiall
Subscribing tjaalton to get his opinion on this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746947
Title:
failing autopkgtest due to password issue by nss
To manage notifications about this bug
Public bug reported:
This could to be very much the same as bug 1746947 (might dup once sure)
Set up Bionic like autopkgtest does:
Use Pinning to get the autopkgtest style:
# cat /etc/apt/preferences.d/nssonlyproposed
Package: *
Pin: release a=bionic
Pin-Priority: 1001
Package: libnss3 libnss3-to
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 ge
Hi Alexander,
on upgrade the server needs to restart and this fails:
>From the log:
invoke-rc.d: initscript mysql, action "start" failed.
There isn't much more to that in the log itself, the following might be
interesting:
$ systemctl status mysql
Never the less there is more to be found in you
Hi,
first of all on the title:
" Also data files are located on NTFS partition so that MySQL server on windows
server installation can also access same data files"
That IMHO is a typical "might work but should not be relied on" case.
For example on upgrades mysql might upgrade the database, that
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 ge
Hi Seyeong,
thanks for the analysis and backport.
The patches look good to me
- two structural changes with no net-effect (to let the backport apply)
- there could have been a backport without those, but I agree that this looks
clearer
- the actual fix seems ok, skipping if no data avail sounds r
** Also affects: libvirt (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: libvirt (Ubuntu)
Status: New => Fix Released
** Changed in: libvirt (Ubuntu Xenial)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
B
This is acked quite a while now.
Is this coming to 18.04 still?
I subscribed Andreas and Timo who were the last people I heard talking
about sssd - maybe you know about the current plans.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
Also passed all regression tests on ppc without a hickup.
Other than waiting for the security update to pass we are ready.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1712803
Title:
spapr_hcall fr
I replied on the mailing list.
I also took a reminder to pick this up once upstream.
I'll later on (before 18.04 release) pick a collection of fixes for libvirt to
stabilize it further - this change will be part of it.
** Tags added: libvirt-18.04
--
You received this bug notification because
Public bug reported:
Seems correct and should be picked to stabilize 4.0 in Bionic.
See: https://www.redhat.com/archives/libvir-
list/2018-January/msg00547.html
** Affects: libvirt (Ubuntu)
Importance: Undecided
Status: New
** Tags: libvirt-18.04
** Tags added: libvirt-18.04
--
Sorry I missed the initial mailing list link in all the initial text :-/
It was just too similar to another bug that was coming by last week that I
short-cut the wrong way.
Thanks Shivaprasad for clarifications.
Also thansk Nish to spot there is a new revision.
With a new look I recreated the ca
** Changed in: libvirt (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746431
Title:
ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Unable to start the guest
from
I don't know when/where this was changed.
But triggers now behave correctly (in general) in regard to the order of
unpack/setup/trigger.
Here 18.04 on the reported package:
Preparing to unpack .../php7.2-curl_7.2.1-1ubuntu2_amd64.deb ...
Unpacking php7.2-curl (7.2.1-1ubuntu2) ...
Setting up php7
Arr [1] looks depressing, never the less I added one more there.
See [2] for the bug.
[1]: https://sourceforge.net/p/net-snmp/bugs/search/?q=segfault&limit=100
[2]: https://sourceforge.net/p/net-snmp/bugs/2823/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
The error still exists in the latest versions.
Here a bit of extra info:
I rebuilt the crash data and added package info.
$ sudo apport-retrace /var/crash/_usr_bin_python2.7.0.crash
--rebuild-package-info --sandbox system
These c libraries into pytohn bindings are annoying to debug.
But I see it
Prepped SRU template here in the bug, also the builds in the ppa are
complete.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1712803
Title:
spapr_hcall from ubuntu_kvm_unit_test failed on ppc64el wi
** Bug watch added: Debian Bug tracker #889011
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889011
** Also affects: chrony (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889011
Importance: Unknown
Status: Unknown
--
You received this bug notification because
** Changed in: nss (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1744328
Title:
libfreebl3.so should be public, not in the nss subdir
To manage
Shairng my two cents on moin as Doko asked for an update - sorry
probably not what you wanted to hear :-/
Moin is - so far - not intended to be py3 compatible.
There is a full detailed status on [1].
So short-term it is unlikely to become py3 compatible.
OTOH one could decide to demote it to univ
Bionic will have what currently is in [1] right now.
I'd ask you to test with that if possible.
Also to be sure since I successfully started hundreds of guests for testing on
P8 recently.
Is this again on P9 like (can't find the other bug atm :-/)?
[1]: https://launchpad.net/~ci-train-ppa-servi
Un-Duped as I found the recent issue being related to an apparmor
profile that was not yet there in Xenial.
But I was made aware (thanks Vincent) that most likely you need to start
it with "-a" which "was needed in chrony version prior to 2.2 to run any
command that reconfigures some aspect of chr
IRC from #systemd
[11:57] Hi, I'm *almost* happy with RuntimeDirectory and
RuntimeDirectoryMode - I'd need to set user/group as well. doc says set
User/Group, but that breaks the actual ExecStart :-/
[11:57] I'd almost need an inverse of PermissionsStartOnly
[11:58] I don't know... using an u
801 - 900 of 5815 matches
Mail list logo
