Public bug reported:
Upgrading esm3 on Trusty is failed.
Preparing to unpack .../libx11-6_2%3a1.6.2-1ubuntu2.1+esm3_amd64.deb ...
Unpacking libx11-6:amd64 (2:1.6.2-1ubuntu2.1+esm3) over (2:1.6.2-1ubuntu2.1) ...
dpkg: error processing archive
/var/cache/apt/archives/libx11-6_2%3a1.6.2-1ubuntu2.1+
Public bug reported:
TBD
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Tags: sts
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchp
** Description changed:
+ [Impact]
+ Azure 18.04 has issue with /dev/disk/by-path/ has the same path name when vm
has multiple disks.
+
+ [Test Plan]
+ 1. launch 18.04 on azure
+ 2. add extra disk to #1 vm
+ 3. check the path
+
+ xtrusia@test-canonical:~$ udevadm info --name=/dev/sda | grep ID_
** Patch added: "lp1996958_bionic.debdiff"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1996958/+attachment/5631294/+files/lp1996958_bionic.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubunt
Assignee: (unassigned) => Seyeong Kim (seyeongkim)
--
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/1996958
Title:
[Azure] 18.04 - /by-path/ has the same path
Status
I deleted the patch as if I put higher Lun number when I add disk ( in
Azure UI ), it works fine. even with this patch, it is the same.
** Patch removed: "lp1996958_bionic.debdiff"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1996958/+attachment/5631295/+files/lp1996958_bionic.debdif
buntu)
Importance: Undecided
Status: Fix Released
** Affects: systemd (Ubuntu Bionic)
Importance: Undecided
Assignee: Seyeong Kim (seyeongkim)
Status: In Progress
** Affects: systemd (Ubuntu Focal)
Importance: Undecided
Status: Fix Released
** Tags
** Patch added: "lp1923115_bionic.debdiff"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1923115/+attachment/5485751/+files/lp1923115_bionic.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubunt
** Description changed:
[Impact]
systemd-networkd renames nic just after udev renamed it
e.g
kernel: [ 2.827368] vmxnet3 :0b:00.0 ens192: renamed from eth0
kernel: [ 7.562729] vmxnet3 :0b:00.0 eth0: renamed from ens192
systemd-networkd[511]: ens192: Interface name chan
** Description changed:
[Impact]
systemd-networkd renames nic just after udev renamed it
e.g
kernel: [ 2.827368] vmxnet3 :0b:00.0 ens192: renamed from eth0
kernel: [ 7.562729] vmxnet3 :0b:00.0 eth0: renamed from ens192
systemd-networkd[511]: ens192: Interface name chan
** No longer affects: systemd (Ubuntu)
** No longer affects: rsyslog (Ubuntu)
--
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/1748147
Title:
Upgrading systemd sets incorre
** Bug watch added: Debian Bug tracker #894510
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894510
** Also affects: systemd via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894510
Importance: Unknown
Status: Unknown
** Project changed: systemd => debhelper
** Also affec
** Description changed:
+ [Impact]
+
+ When installing postgresql, many warning msgs are raised
+ Please refer to Original Description
+
+ [Test Case]
+
+ 1. create ubuntu instance
+ 2. apt install postgresql
+
+
+ [Regression Potentials]
+ This change is quite small(just escaping), and it is
** Patch added: "lp1538284_xenial.debdiff"
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1538284/+attachment/5103452/+files/lp1538284_xenial.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam in Ubuntu.
https
** Changed in: pam (Ubuntu Trusty)
Status: New => Won't Fix
** Changed in: pam (Ubuntu Xenial)
Status: New => In Progress
** Changed in: pam (Ubuntu Artful)
Status: New => In Progress
** Changed in: pam (Ubuntu Xenial)
Assignee: (unassigned) => Sey
Hello, Thanks for your cooperation.
Tested on Xenial
1. create xenial instance
2. add proposed repository
3. apt install libpam-runtime
4. apt install postgresql
warnings are gone.
Thanks!
dpkg -l | grep pam
ii libpam-modules:amd641.1.8-3.2ubuntu2
am
Hello,
Tested on artful
1. create artful instance
2. add proposed repository
3. apt install libpam-runtime
4. apt install p ostgresql
warnings are gone
Thanks!
dpkg -l | grep pam
ii libpam-cap:amd641:2.25-1.1amd64
POSIX 1003.1e capabilities
@racb, adconrad
Yes, exactly...
As you can see debian bugs.
In the beginning, I meant to fix it like that
e.g running systemd-tmpfiles for all files in /var/lib/tmpfiles.d/ not just for
systemd defined files, by running it without argument
But the maintainer didn't accept mine, you can check
FYI
systemd-tmpfiles command running when installing or upgrading systemd
is in debhelper pkg
cat autoscripts/postinst-init-tmpfiles
if [ "$1" = "configure" ] || [ "$1" = "abort-upgrade" ]; then
# In case this system is running systemd, we need to ensure that all
# necessary tmpf
** Patch added: "lp1717714_artful.debdiff"
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1717714/+attachment/5032831/+files/lp1717714_artful.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubu
** Patch added: "lp1717714_zesty.debdiff"
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1717714/+attachment/5032830/+files/lp1717714_zesty.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubunt
** Patch added: "lp1717714_xenial.debdiff"
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1717714/+attachment/5032829/+files/lp1717714_xenial.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubu
** Patch added: "lp1717714_bionic.debdiff"
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1717714/+attachment/5032832/+files/lp1717714_bionic.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubu
** Patch added: "lp1717714_trusty.debdiff"
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1717714/+attachment/5032828/+files/lp1717714_trusty.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubu
11.0-2ubuntu17)
I am aware this is a non-default configuration, but I think this should
work.
** Tags removed: patch
** Tags added: sts-sru-needed
** Changed in: apparmor (Ubuntu)
Assignee: (unassigned) => Seyeong Kim (xtrusia)
--
You received this bug notification because you are
** Patch added: "lp1717714_artful.debdiff"
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1717714/+attachment/5033301/+files/lp1717714_artful.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubu
** Patch added: "lp1717714_xenial.debdiff"
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1717714/+attachment/5033299/+files/lp1717714_xenial.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubu
** Patch removed: "lp1717714_trusty.debdiff"
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1717714/+attachment/5032828/+files/lp1717714_trusty.debdiff
** Patch removed: "lp1717714_xenial.debdiff"
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1717714/+attachment/5032829/
** Patch added: "lp1717714_bionic.debdiff"
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1717714/+attachment/5033302/+files/lp1717714_bionic.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubu
** Patch added: "lp1717714_zesty.debdiff"
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1717714/+attachment/5033300/+files/lp1717714_zesty.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubunt
Hello Eric, ddstreet
#1740892 seems starting to fix
Could you guys can sponsor this issue as well?
Thanks a lot
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1316970
Tit
sure, no problem
Thanks eric
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1316970
Title:
g_dbus memory leak in lrmd
Status in glib2.0 package in Ubuntu:
New
Status i
Hello ddstreet
I confirmed that glib2.0 patch is needed.
I installed patched_pacemaker only on my system and running just 1 hour.
it started with 4700(RES) but now it is 8000(RES).
after installing glib2.0
it started with 4612, now is is 4688
Thanks
[1] is script to reproduce this issue. nee
Public bug reported:
[Impact]
This issue is found while debugging pacemaker lrmd memory leak
glib2.0 gio function g_dbus_proxy_new_for_bus_sync has leak as [1] said
this is affected to Trusty
[Test Case]
https://pastebin.ubuntu.com/p/fqK6Cx3SKK/
you can check memory leak with this script
[Re
** Patch added: "lp1750741_trusty_glib2.0.debdiff"
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1750741/+attachment/5059468/+files/lp1750741_trusty_glib2.0.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Description changed:
[Impact]
lrmd daemon with upstart resource has memory leak in Trusty
affected to pacemaker 1.1.10.
- affected to glib2.0 2.40.2-0ubuntu1
+ affected to glib2.0 2.40.2-0ubuntu1 >> for glib2.0 created new lp [3]
Please note that patch for pacemaker is created mys
Hello ddstreet
yep, it is tricky..
In the beginning, I added only one line but build failed.
3 commits for building, only one line is related to memroy leak
directly.
I retried it and attaching build link on lp
Thanks
https://launchpad.net/~xtrusia/+archive/ubuntu/sf160627-glib/+build/1438319
Public bug reported:
[Impact]
When using redirect url on /etc/apt/sources.list
apt update command hangs
this is affected with commit
https://anonscm.debian.org/git/apt/apt.git/commit/?id=dd547ebaffd2aceb42e2908f1d5f0ab386af6cb1
In my test, moving below[1] code after[2]
[1]
###
if (ContentLeng
@ddstreet
After analyzing code.
I don't think this fix is possible without any big changes for trusty.
and glib2.0 affects many pkgs it seems.
it is quite dangerous to fix this with large commits.
so lets focus on pacemaker instead of glib2.0
how about this ddstreet?
Thanks
--
You received
Hello Julian, no news for this?
--
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/1751225
Title:
apt update hangs when repository url is redirect url
Status in apt package in Ub
Thanks a lot!
--
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/1751225
Title:
apt update hangs when repository url is redirect url
Status in apt package in Ubuntu:
Invalid
St
Hello,
I verified this -proposed pkg is working.
1. upgrade apt pkg
2. insert above url in test case to sources.list
3. apt update
4. check if it hangs or not
dpkg -l
ii apt 1.2.26
amd64commandline package manager
Thanks
** Tags removed: verification-n
** Description changed:
[Impact]
If PID is larger than 6 digits.
apparmor denies process.
this fix is committed, but not released. so all supporting version are
affected.
[Test Case]
1. making pid over 6 digits
- - i used touch command to do it
- 2. snap install canoni
** Also affects: glib2.0 (Ubuntu)
Importance: Undecided
Status: New
** Patch removed: "lp1316970_trusty.debdiff"
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1316970/+attachment/5031302/+files/lp1316970_trusty.debdiff
--
You received this bug notification because you are
** Attachment added: "valgrind-beforepatch"
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1316970/+attachment/5047144/+files/valgrind-beforepatch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
** Attachment added: "valgrind-afterpatch"
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1316970/+attachment/5047145/+files/valgrind-afterpatch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
ht
** Patch added: "lp1316970_trusty_glib2.0.debdiff"
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1316970/+attachment/5047147/+files/lp1316970_trusty_glib2.0.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Patch added: "lp1316970_trusty_pacemaker.debdiff"
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1316970/+attachment/5047146/+files/lp1316970_trusty_pacemaker.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
Changed in: glib2.0 (Ubuntu Trusty)
Assignee: (unassigned) => Seyeong Kim (xtrusia)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1316970
Title:
g_dbus memory leak in lr
Hello, I tested on xenial
ii apparmor 2.10.95-0ubuntu2.8
tested same steps as test case section.
there is no DENIED after installing proposed pkg
Thanks
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug n
Hello, I tested on artful
ii apparmor 2.11.0-2ubuntu17.1
tested same steps as test case section.
Thanks
** Tags removed: verification-needed-artful
** Tags added: verification-done-artful
--
You received this bug notification because you are a member of Ubun
Hello
on trusty
apt-get download apparmor_2.10.95-0ubuntu2.6~14.04.2_amd64.ddb
dpkg -x apparmor... t
cat t/etc/apparmor.d/tunables/kernelvars
@{pid}={[1-9],[1-9][0-9],[1-9][0-9][0-9],[1-9][0-9][0-9][0-9],[1-9][0-9][0-9][0-9][0-9],[1-9][0-9][0-9][0-9][0-9][0-9]}
which is old one.
I checked ap
Thanks Eric
ii apparmor 2.10.95-0ubuntu2.6~14.04.3
there is no pre-installed snapd on trusty so i needed to install snapd
first
1. set sysctl
2. add -proposed
3. apt install snapd
4. reboot
5. snap install --dangerous oldverioncore
symptom is gone
Thanks.
** Tags
** Patch added: "lp1316970_trusty_pacemaker_v2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1316970/+attachment/5047782/+files/lp1316970_trusty_pacemaker_v2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is su
Hello ddstreet
Thanks for the review.
I changed some code for pacemaker. ( char -> gchar for matching type,
with g_free)
and glib2.0 patch is needed in my test.
without it, memory leak is there. 4kB leak every 10 second at least.
Thanks.
--
You received this bug notification because you are
hmm, this has leak more than before..
testing..
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1316970
Title:
g_dbus memory leak in lrmd
Status in glib2.0 package in Ubu
** Patch added: "lp1316970_trusty_pacemaker_v3.debdiff"
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1316970/+attachment/5048947/+files/lp1316970_trusty_pacemaker_v3.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is su
@ddstreet
Could you please review V3 again?
Thanks in advance!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1316970
Title:
g_dbus memory leak in lrmd
Status in glib2.
For V3.
It seems that g_variant_unref(value); part is needed.
Added it again and no memory leaks.
in g_variant_lookup_value, it calls g_variant_get_child_value
so as you said. it need to be unref value as well i think.
Thanks.
--
You received this bug notification because you are a member of
sorry not commenting at once
mvo: the almost-ready 2.31 release will fix this
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1717714
Title:
@{pid} variable broken on sys
Hello Eric
I'm attaching mvo's PM
mvo: yes, please ignore the failure of snapd. there was a server side
change in the store that makes the autopkgtests fail
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
=1546
Requires some heavy backporting to older releases, see:
https://bugzilla.redhat.com/show_bug.cgi?id=1166147#c2.
** Changed in: pcre3 (Ubuntu Trusty)
Status: New => In Progress
** Changed in: pcre3 (Ubuntu Trusty)
Assignee: (unassigned) => Seyeong Kim (xtrusia)
**
** Changed in: pcre3 (Ubuntu Utopic)
Status: New => In Progress
** Changed in: pcre3 (Ubuntu Utopic)
Assignee: (unassigned) => Seyeong Kim (xtrusia)
** Patch added: "utopic-cve-2014-8964.debdiff"
https://bugs.launchpad.net/ubuntu/+source/pcre3/+bug/1396768/+at
ete => In Progress
** Changed in: e2fsprogs (Ubuntu Precise)
Assignee: (unassigned) => Seyeong Kim (xtrusia)
** Changed in: e2fsprogs (Ubuntu Trusty)
Assignee: (unassigned) => Seyeong Kim (xtrusia)
** Changed in: e2fsprogs (Ubuntu)
Assignee: Rafael David Tinoco (inad
** Patch added: "trusty-fix-multiply-claimed.debdiff"
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1321418/+attachment/4454739/+files/trusty-fix-multiply-claimed.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscr
** Description changed:
+ [Impact]
+
+ on Trusty
+
+ logging to syslog via cron causes timestamp abnormals after several
+ hours.
+
+ [Test Case]
+
+ 1. run below first,
+ while true ; do logger "hello syslog" ; sleep 1; done
+
+ 2. register below script to crontab
+ for i in {1..100} ; do lo
** Patch added: "lp1429427_trusty.debdiff"
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1429427/+attachment/4916080/+files/lp1429427_trusty.debdiff
** Description changed:
[Impact]
on Trusty
logging to syslog via cron causes timestamp abnormals after several
hours.
right,
In my test, only 7a2e247 commit fixes this symptom.
but
I think be45099 is worth SRUing with 7a2e247 as commit's description
5a11a1d is quite far
uploaded debdiff for two patches.
Thanks
** Patch added: "lp1429427_trusty2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bu
I tested -proposed pkg and this symptom is fixed with it.
ii rsyslog 7.4.4-1ubuntu2.7 amd64..
Thanks.
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is sub
** Changed in: util-linux (Ubuntu Eoan)
Assignee: (unassigned) => Seyeong Kim (seyeongkim)
** Changed in: util-linux (Ubuntu Focal)
Assignee: (unassigned) => Seyeong Kim (seyeongkim)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
** Patch added: "lp1886300_groovy.debdiff"
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1886300/+attachment/5394575/+files/lp1886300_groovy.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in
** Patch added: "lp1886300_focal.debdiff"
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1886300/+attachment/5394576/+files/lp1886300_focal.debdiff
** No longer affects: util-linux (Ubuntu Eoan)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
** Description changed:
+ [Impact]
+
+ rename.ul refuses to rename links that don't resolve.
+
+ bionic rename.ul renames links whether or not they resolve (util-linux
+ 2.31.1-0.4ubuntu3.6).
+
+ focal rename.ul refuses to rename links that don't resolve (regression)
+ (util-linux 2.34-0.1ubunt
** Patch added: "lp1886300_groovy.debdiff"
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1886300/+attachment/5395090/+files/lp1886300_groovy.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in
** Patch removed: "lp1886300_groovy.debdiff"
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1886300/+attachment/5394575/+files/lp1886300_groovy.debdiff
** Patch removed: "lp1886300_focal.debdiff"
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1886300/+attachment/53945
@mfo
Thanks for your advice, re-uploaded patches
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1886300
Title:
rename.ul refuses to rename links that don't resolve (re
Hello, I uploaded pkg to ppa
https://launchpad.net/~xtrusia/+archive/ubuntu/lp1733321
and checked ppc64el build and testing.
It worked fine without any issue.
Could you please adjust Kleber's debdiff as well?
Thanks a lot.
--
You received this bug notification because you are a member of Ubun
** Description changed:
[Impact]
The killswitches-no-urfkill autopkgtest fails sometimes because nmcli
reports the old state when it's called right after rfkill block/unblock.
Adding a sleep before calling nmcli fixes the issue.
ppc64el ADT log from failed testcase:
https://obje
** Description changed:
[Impact]
The killswitches-no-urfkill autopkgtest fails sometimes because nmcli
reports the old state when it's called right after rfkill block/unblock.
Adding a sleep before calling nmcli fixes the issue.
ppc64el ADT log from failed testcase:
https://obje
I uploaded patch for bionic sru. but I didn't subscribe sru-sponsors yet
because I'm still confirming reproducer.
I'll update description after reproducing this issue in my local.
Thanks.
** Tags added: sts
** Changed in: network-manager (Ubuntu Bionic)
Assignee: (unassig
** Patch removed: "lp1794478_bionic.debdiff"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1794478/+attachment/5329464/+files/lp1794478_bionic.debdiff
** Patch added: "lp1794478_bionic.debdiff"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1794478/+attachm
** Description changed:
[Impact]
+
+ In case creating bond interface, IPv4 address is not automatically
+ assigned when IPv6 has manual setting.
+
[Test Case]
+
+ 1. create 18.04.4 instance, network-manager version is 1.10.6-2ubuntu.1.2 as
original description.
+ 2. ipv6 manual, ipv4 auto
why bugproxy keep attaching old debdiff I've changed
--
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.launchpad.net/bugs/1794478
Title:
Automatic ipv4 not assigned to bond interface is
Hello
I've verified this -proposed pkg on my local.
#2 on description working fine.
xtrusia@ubuntu:~$ dpkg -l | grep network-manager
ii network-manager1.10.6-2ubuntu1.4
amd64network management framework (daemon and userspace
to
** Changed in: apparmor (Ubuntu)
Assignee: (unassigned) => Seyeong Kim (xtrusia)
** Changed in: apparmor (Ubuntu Trusty)
Assignee: (unassigned) => Seyeong Kim (xtrusia)
** Changed in: apparmor (Ubuntu)
Status: New => In Progress
** Changed in: apparmor (Ubun
** Description changed:
+ [SRU justification]
+
+ [Impact]
+
$ sudo aa-complain /etc/apparmor.d/usr.lib.postfix.*
Setting /etc/apparmor.d/usr.lib.postfix.anvil to complain mode.
Traceback (most recent call last):
- File "/usr/sbin/aa-complain", line 30, in
- tool.cmd_complain()
-
** Patch added: "tools-fix-multi-profile-vivid.debdiff"
https://bugs.launchpad.net/apparmor/+bug/1378095/+attachment/4364897/+files/tools-fix-multi-profile-vivid.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to appa
** Patch added: "tools-fix-multi-profile-trusty.debdiff"
https://bugs.launchpad.net/apparmor/+bug/1378095/+attachment/4364898/+files/tools-fix-multi-profile-trusty.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ap
@tyhicks
got it Thanks :)
** Changed in: apparmor (Ubuntu)
Assignee: Seyeong Kim (xtrusia) => (unassigned)
** Changed in: apparmor (Ubuntu Trusty)
Assignee: Seyeong Kim (xtrusia) => (unassigned)
** Changed in: apparmor (Ubuntu)
Status: In Progress => Confirmed
** C
@tyhicks
quiestion :)
you are planning to adopt you mentioned for multiple release? trusty,
utopic etc..
Thanks
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1378095
Ti
It works for me
ii packagekit0.8.17-4ubuntu6~gcc5.4ubuntu1.1
amd64
** 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 packagekit in
** Patch added: "yakkety-check-null-in-aptintf-init.debdiff"
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1569292/+attachment/4651215/+files/yakkety-check-null-in-aptintf-init.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
** Description changed:
[Impact]
When trying to join AD domain via realm command, it hangs.
after researching, packagekit got segfault.
[Testcase]
realm -v join int.domainname.com --user login
* Resolving: _ldap._tcp.int.domanname.com
* Performing LDAP DSE lookup on: 19
** Patch removed: "xenial-check-null-in-aptintf-init.debdiff"
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1569292/+attachment/4649721/+files/xenial-check-null-in-aptintf-init.debdiff
** Patch removed: "yakkety-check-null-in-aptintf-init.debdiff"
https://bugs.launchpad.net/ubu
** Patch added: "yakkety-check-null-in-aptintf-init.debdiff"
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1569292/+attachment/4651258/+files/yakkety-check-null-in-aptintf-init.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
** Package changed: realmd (Ubuntu) => packagekit (Ubuntu)
--
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/1569292
Title:
Can't join to AD domain
Status in realmd:
Ne
@niklas-andersson
Hello, It seems that
https://github.com/hughsie/PackageKit/commit/e94b80f90179db18221b2eff93b4561b5418fbfb
fixes this issue ( especially, code checking whether_proxy is null )
I uploaded ppa only for testing with this commit and dependent commits.
Could you please test this PP
** Description changed:
+ [Impact]
+
+ When trying to join AD domain via realm command, it hangs.
+ after researching, packagekit got segfault.
+
+ [Testcase]
+
realm -v join int.domainname.com --user login
- * Resolving: _ldap._tcp.int.domanname.com
- * Performing LDAP DSE lookup on: 19
need to be sponsored that can be combined 4 patches
** Patch added: "xenial-check-null-in-aptintf-init.debdiff"
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1569292/+attachment/4649721/+files/xenial-check-null-in-aptintf-init.debdiff
--
You received this bug notification because
** Changed in: packagekit (Ubuntu Xenial)
Status: New => In Progress
** Changed in: packagekit (Ubuntu Xenial)
Assignee: (unassigned) => Seyeong Kim (xtrusia)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscri
1 - 100 of 129 matches
Mail list logo
