** Description changed:
This is reproducible in Bionic and late.
Here's an example running 'focal':
$ lsb_release -cs
focal
$ uname -r
5.3.0-24-generic
+ The error is:
+ blk_update_request: I/O error, dev loop2, sector 0
+
How to trigger it:
-
$ sosreport -o block
Booting with "systemd.log_level=debug" revealed:
Dec 18 17:26:22 ubuntu systemd-udevd[1326]: value '[dmi/id]sys_vendor' is 'QEMU'
Dec 18 17:26:22 ubuntu systemd-udevd[1326]: created db file
'/run/udev/data/b7:2' for '/devices/virtual/block/loop2'
Dec 18 17:26:22 ubuntu systemd[1]: dev-loop2.devic
I also filed a sosreport upstream issue, because I believe sosreport
shouldn't try to query "unused" block device such as loop device.
https://github.com/sosreport/sos/issues/1897
but situation remain that there is something going wrong with loop
device and systemd/systemd-udevd at boot as explai
** Description changed:
This is reproducible in Bionic and late.
Here's an example running 'focal':
$ lsb_release -cs
focal
$ uname -r
5.3.0-24-generic
The error is:
blk_update_request: I/O error, dev loop2, sector 0
+
+ and on more recent kernel:
+
+ kernel: [18135.1
Interesting fact,
If I modified "snapd.service" to prevent snapd to run and reboot. I
don't get the problem with the first unused loop device which is
/dev/loop0 since nothing is using a loop device.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
Talking with mvo (snap team) on the subject trying to eliminate some
components:
[09:48:27] so snapd does not do anything "special" with block devices
beside using them
[09:48:39] it uses the standard system mount units to do that
[09:49:01] so if you see strange things with extra block device
# losetup -l
NAME SIZELIMIT OFFSET AUTOCLEAR RO BACK-FILE
DIO LOG-SEC
/dev/loop1 0 0 1 1 /var/lib/snapd/snaps/core_7270.snap
0 512
/dev/loop2 0 0 1 1 /var/lib/snapd/snaps/core_8268.snap
0 512
/dev/loop0
losetup -l
NAME SIZELIMIT OFFSET AUTOCLEAR RO BACK-FILE
DIO LOG-SEC
/dev/loop1 0 0 1 1 /var/lib/snapd/snaps/core_7270.snap
0 512
/dev/loop2 0 0 1 1 /var/lib/snapd/snaps/core_8268.snap
0 512
/dev/loop0
# parted code (3.3-1) from focal
-
libparted/arch/linux.c:
.
=> if (fsync (fd) < 0 || close (fd) < 0)
if (ped_exception_throw (
PED_EXCEPTION_WARNING,
@thadeu,
To respond your question "What is the exact problem this is causing?"
So far it's not causing much problem, it's pretty harmless, but while
running sosreport block plugin (which most Canonical customer uses) it
may lead to output "blk" error to the stderr and save syslog ||
kern.log.
As
It then might be a problem with "/dev/loop-control" device node. Which
dynamically find or allocate a free device, but also add and remove loop
devices from the running system.
# drivers/block/loop.c
2090 static void loop_remove(struct loop_device *lo)
2091 {
2092 del_gendisk(lo-
Agreed with your comment #11
will start a discussion with the linux-block maintainer.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1856871
Title:
i/o error if next unused loop device is queried
T
Ok so in fact the inconsistency is due to "parted" that will try to
probe devices iff the given block device return informations from
stat(), regardless if the block device is available or not.
Seems like the only trigger/criteria is the stat() return. Since the
loop device stat doesn't clear/rese
so 2 things come to my mind right now
Does the kernel (loop driver) do the right thing by not clear/reset the
loop device' stats after the umount/detached operation ?
and/or
Does parted need to smarter and not only based is detection only on
stat() ?
Let's circle back on Jan 2020.
** Also
so 2 things come to my mind right now
Does the kernel (loop driver) do the right thing by not clear/reset the
loop device' stats after the umount/detached operation ?
and/or
Does parted need to be smarter and not only based is detection on stat()
to assume if its a legit device or not to be
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864475
Title:
Mstflint package - add RoCE disable support
To manage notifications about this bug go to:
https://bugs.launchpad.net/
Pushed into focal along with LP: #1865212.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868215
Title:
SRU: [lxd] Drop db collection and introduce lxd.buginfo
To manage notifications about this bu
autopkgtest tested locally:
Everything worked!
autopkgtest [13:01:30]: test simple.sh: ---]
autopkgtest [13:01:31]: test simple.sh: - - - - - - - - - - results - - - - -
- - - - -
simple.shPASS
autopkgtest [13:01:31]: summary
sos-run-nonroot.p
Excuse pages...
autopkgtest for sosreport/3.9-1ubuntu2: amd64: Pass, arm64: Pass, armhf:
Pass, ppc64el: Pass, s390x: Pass
logs:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/s/sosreport/20200325_181101_c8abf@/log.gz
.
[FOCAL]
Note: lxd only available via SNAP.
# lsb_release -cs
focal
# snap list lxd
Name Version RevTracking Publisher Notes
lxd 3.0.411348 3.0/stable/… canonical✓ -
# ls -altr /sos_commands/lxd/lxd.buginfo
-rw-r--r-- 1 root root 22017 Mar 25 16:41
/sos_commands/lxd/lxd.b
** Changed in: containerd (Ubuntu Bionic)
Assignee: (unassigned) => Jorge Niedbalski (niedbalski)
** Changed in: containerd (Ubuntu Bionic)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
** Also affects: lxcfs (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: lxcfs (Ubuntu Eoan)
Importance: Undecided
Status: New
** Also affects: lxcfs (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: lxcfs (Ubuntu Bionic)
Assigne
** Tags added: sts-sponsor-volunteer
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868215
Title:
SRU: [lxd] Drop db collection and introduce lxd.buginfo
To manage notifications about this bug go t
** Also affects: sosreport (Ubuntu Eoan)
Importance: Undecided
Status: New
** Also affects: sosreport (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: sosreport (Ubuntu Xenial)
Importance: Undecided
Status: New
** Tags removed: sts
** Tags added: s
[sts-sponsor]
Sponsored for E/B.
Thanks Kellen for your contribution.
- Eric
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860813
Title:
LXC container reports spike in swap occasionally
To mana
[STS-SPONSOR]
Sponsored for E/B.
Thanks for your contribution Seyeong.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868215
Title:
SRU: [lxd] Drop db collection and introduce lxd.buginfo
To mana
Public bug reported:
This bug has been brought to my attention the following:
There is a Debian bug report
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949622
The proftpd-basic package in Xenial and Bionic suffers from this bug.
The impact is very widespread. Every person that uses Filezill
** Description changed:
- This bug has been brought to my attention. More details to come.
+ This bug has been brought to my attention the following:
+
+ There is a Debian bug report
+ https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949622
+
+ The proftpd-basic package in Xenial and Bionic suf
** Description changed:
This bug has been brought to my attention the following:
There is a Debian bug report
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949622
The proftpd-basic package in Xenial and Bionic suffers from this bug.
The impact is very widespread. Every person t
** Description changed:
This bug has been brought to my attention the following:
There is a Debian bug report
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949622
- The proftpd-basic package in Xenial and Bionic suffers from this bug.
- The impact is very widespread. Every person t
For now I don't see the point to fix other Ubuntu releases as only focal
contains filezilla "3.46" and Focal also already got the proftpd-basic
fix.
Focal:
proftpd-dfsg-1.3.6c/debian/patches/upstream_4385
Upstream bug mentionned:
All my users that use the filezilla client 3.46.1+ fail to connect
Filezilla is cross-platform so I think it is also fair to say there is
various filezilla in the field (outside what the Ubuntu archive is
providing today).
https://filezilla-project.org/download.php?show_all=1
My point is that If we go with the SRU (process to fix a package) in
version earlier th
** Changed in: proftpd (Ubuntu Xenial)
Status: New => Incomplete
** Changed in: proftpd (Ubuntu Bionic)
Status: New => Incomplete
** Changed in: proftpd (Ubuntu Eoan)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
uires root
https://github.com/sosreport/sos/blob/master/tests/simple.sh
** Affects: sosreport (Ubuntu)
Importance: Low
Assignee: Eric Desrochers (slashd)
Status: In Progress
** Tags: sts
** Changed in: sosreport (Ubuntu)
Assignee: (unassigned) => Eric Desrochers (slashd)
** Changed in: sosreport (Ubuntu)
Status: Confirmed => In Progress
** Changed in: sosreport (Ubuntu)
Importance: Wishlist => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1865212
Title:
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1862830
Title:
Update sosreport to 3.9
To manage notifications abou
ance: Undecided
Status: Fix Released
** Affects: collectd (Ubuntu Bionic)
Importance: Medium
Assignee: Eric Desrochers (slashd)
Status: In Progress
** Tags: sts
** Description changed:
Upstream bug & fix:
https://github.com/collectd/collectd/issues/2951
https://
$ lsb_release -cs
bionic
$ uname -r
4.15.0-76-generic
$ awk '{ print NF }' /proc/diskstats
14
14
14
14
14
14
14
14
14
14
14
14
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1865895
Title:
/proc/d
$ lsb_release -cs
bionic
$ uname -r
5.0.0-41-generic
$ awk '{ print NF }' /proc/diskstats
18
18
18
18
18
18
18
18
18
18
18
18
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1865895
Title:
/proc/di
$ lsb_release -cs
bionic
$ uname -r
4.18.0-25-generic
$ awk '{ print NF }' /proc/diskstats
14
14
14
14
14
14
14
14
14
14
14
14
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1865895
Title:
/proc/d
** Description changed:
Upstream bug & fix:
https://github.com/collectd/collectd/issues/2951
https://github.com/collectd/collectd/pull/2952/commits/6ce52f70cc1e6450df3454f19743a29295b84050
+
https://github.com/collectd/collectd/pull/2952/commits/42f8dc033f5009dda7202ceee97e57bbbedf6fc3
** Description changed:
+ Kernel change introducing the diskstat format field add:
+
https://github.com/torvalds/linux/commit/bdca3c87fb7ad1cc61d231d37eb0d8f90d001e0c
+
Upstream bug & fix:
https://github.com/collectd/collectd/issues/2951
https://github.com/collectd/collectd/commit/6ce5
** Description changed:
- Kernel change introducing the diskstat format field add:
+ ## DRAFT ###
+
+ [Impact]
+ With v4.19, Linux gained extra fields in /proc/diskstats:
https://github.com/torvalds/linux/commit/bdca3c87fb7ad1cc61d231d37eb0d8f90d001e0c
+
+ [Test Case]
+
+ * Follow the proced
** Description changed:
- ## DRAFT ###
-
[Impact]
With v4.19, Linux gained extra fields in /proc/diskstats:
https://github.com/torvalds/linux/commit/bdca3c87fb7ad1cc61d231d37eb0d8f90d001e0c
[Test Case]
* Follow the procedure here:
https://collectd.org/wiki/index.php/First_steps
Uploaded in Bionic.
** Description changed:
[Impact]
With v4.19, Linux gained extra fields in /proc/diskstats:
https://github.com/torvalds/linux/commit/bdca3c87fb7ad1cc61d231d37eb0d8f90d001e0c
[Test Case]
* Follow the procedure here:
https://collectd.org/wiki/index.php/First_s
** Also affects: collectd (Ubuntu Eoan)
Importance: Undecided
Status: New
** Changed in: collectd (Ubuntu Eoan)
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/bu
** Tags removed: sts-sponsor
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1595627
Title:
Pacemaker fails to start and reports a Library Error
To manage notifications about this bug go to:
https://
** Tags removed: sts-sponsor
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1593378
Title:
crash in slap_bv2ad using repeated tags
To manage notifications about this bug go to:
https://bugs.launchpa
I don't have the error "Too many levels of symbolic links" when doing an
"ls" command but I do have a problem using "df" on Xenial after
installing Openstack with lxd using "conjure-up"
"df" works fine, but after a reboot, it hangs.
A "strace df" shows that it hangs at doing :
..
stat("/sys/fs/cg
To continue my previous comment...
It is reproducible with :
binfmt-support (2.1.6-1)
systemd(229-4ubuntu6)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1555760
Title:
Too many levels of
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released
** Summary changed:
- kernel panic (General protection fault) on module hpsa (lockup_detected)
+ General protection fault panic on module hpsa with lockup_detected attribute
--
You received this bug notification because yo
It has been brought to my attention by a user experiencing the issue on
Trusty (14.04 LTS) the following :
"I installed libqb0 from proposed repo and it works as expected. No more
issues when starting with pid >99,999"
Eric
** Tags removed: verification-needed
** Tags added: verification-done
-
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1593378
Title:
crash in slap_bv2ad using repeated tags
To manage notifications ab
The following has been brought to my attention by a user :
"I got verification from the system test, the fix solves the ldap issue.
Thank you for the fix"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
@xnox,
I have notice a block in Bionic when choosing 'Enable Network' option in
recovery mode on different bionic vanilla system and I can reproduce all
the time.
I also asked colleagues to give it a try (for a second pair of eye on
this) and they have the same result as me.
Basically, when choo
pstree command seems to shorten the processes name. So in fact 'systemd
'tty-ask' is 'systemd-tty-ask-password-agent'
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682637
Title:
during recovery mod
Here's a screenshot of what it looks like when block. [bionic-recovery-
mode.png]
** Attachment added: "bionic-recovery-mode.png"
https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1682637/+attachment/5127018/+files/Screenshot_bionic-recovery_2018-04-25_10_58_23.png
--
You rece
Here's a screenshot of what it looks like when block. [bionic-recovery-
mode.png]
** Attachment added: "bionic-recovery-mode.png"
https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1682637/+attachment/5127019/+files/Screenshot_bionic-recovery_2018-04-25_10_58_23.png
--
You rece
I did the same exercise on my reproducer and got the following pstree
output:
When is switch to vtty with systemd.debug-shell=1, here what I got :
# pstree
systemd-+-bash---pstree
|-recovery-menu---network---systemctl---(sd-askpwagent)
|-systemd-journal
# ps
root 486
I did the same exercise on my reproducer and got the following pstree
output:
When is switch to vtty with systemd.debug-shell=1, here what I got :
# pstree
systemd-+-bash---pstree
|-recovery-menu---network---systemctl---(sd-askpwagent)
|-systemd-journal
# ps
root 486
I did the same exercise on my reproducer and got the following pstree
output:
When is switch to vtty with systemd.debug-shell=1, here what I got :
# pstree
systemd-+-bash---pstree
|-recovery-menu---network---systemctl---systemd-tty-ask
|-systemd-journal
# ps
root 486
Additionally,
When doing a systemd-analyze blame:
"Bootup is not yet finished. Please try again later"
systemctl list-jobs is showing a 100 jobs in 'waiting' state
Seems like systemd is not fully initialise in 'Recovery Mode'
--
You received this bug notification because you are a member of U
Public bug reported:
This bug has been introduced by the fix of (LP: #1682637) in Bionic.
I have notice a block in Bionic when choosing 'Enable Network' option in
recovery mode on different bionic vanilla system and I can reproduce all
the time.
I also asked colleagues to give it a try (for a se
I filed a new bug LP: #1766872 .
If someone experience the same problem, please provide some feedbacks in
the new bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682637
Title:
during recovery m
** Description changed:
- This bug has been introduced by the fix of (LP: #1682637) in Bionic.
+ This bug has been noticed after the introduction of the fix of (LP:
+ #1682637) in Bionic.
I have notice a block in Bionic when choosing 'Enable Network' option in
recovery mode on different bio
** Description changed:
This bug has been noticed after the introduction of the fix of (LP:
#1682637) in Bionic.
I have notice a block in Bionic when choosing 'Enable Network' option in
recovery mode on different bionic vanilla system and I can reproduce all
the time.
I also aske
** Also affects: horizon (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: horizon (Ubuntu Bionic)
Importance: Undecided
Assignee: Felipe Reyes (freyes)
Status: Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
I did some progress...
I was able to make a few 'enabled|static' services to start such as :
dbus.socket
networking.service
system-resolved.service
NetworkManger doesn't seems to start well.
By making the following changes :
# /lib/recovery-mode/options/network
-
** Changed in: friendly-recovery (Ubuntu Xenial)
Assignee: Eric Desrochers (slashd) => (unassigned)
** Changed in: friendly-recovery (Ubuntu Artful)
Assignee: Eric Desrochers (slashd) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
By reading more about systemd, I start to think the blocker here to
start the desired services is "Type=oneshot" instruction in friendly-
recovery.service.
"
Behavior of oneshot is similar to simple; however, it is expected that the
process has to exit before systemd starts follow-up units.
"
Ne
So all the remaining jobs are basically waiting for friendly-recovery to
exit to start due to the "oneshot" instruction, which make xnox patch
(revno 152) not working.
Some waiting jobs are units in which the desired network services in revno 152
depends on.
I totally understand why "oneshot" is
or possibly add After=network.target or something around those line.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766872
Title:
'Enable Network' in recovery mode not working in Bionic
To manage n
I set both back to 'Confirmed'.
** Changed in: casper (Ubuntu)
Status: Fix Released => Confirmed
** Changed in: systemd (Ubuntu)
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
** Changed in: ubiquity (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767720
Title:
Ubiquity crashed during install of 18.04 with error 'BadAccess
(a
Can you please provide the following cmd outputs for each of your
affected system ? and the content of "/var/log/installer/"
# lspci -nnvv
# dmidecode
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/176
Seems like using "GDK_SYNCHRONIZE=1" might be the way to do it instead
of --sync ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767720
Title:
Ubiquity crashed during install of 18.04 with error 'B
https://developer.gnome.org/gtk3/stable/gtk-x11.html
...
GDK_SYNCHRONIZE. If set, GDK makes all X requests synchronously. This is a
useful option for debugging, but it will slow down the performance considerably.
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
Chris Jensen (crjensen),
On what type of HW were you able to reproduce ?
Normally, if you select 'Try Ubuntu' and then go in terminal you should be able
to run "dmidecode" and "lspci" just fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
Chris, yeah I see you are installing Ubuntu on a MAC (Apple inc). I was
curious to see if there was a common HW to everyone (graphic card,...)
but it doesn't seems like it so far)
As stated in comment#10 to comment#12, it would be good to have a dump
in 'sync' mode.
--
You received this bug noti
## VERIFICATION TRUSTY ##
I have tested the [Test Case] step above in the description, and
couldn't reproduce the problem I was able to reproduce in previous
version.
# dpkg
ii xfsprogs 3.1.9ubuntu2.1amd64
- Eric
** Tags removed: verification-needed-trusty
** Tags added: verification-
I *think* I start to see a tendencies where affected system might all
have a GeForce 3D controller.
So far:
Launchpad description : Product Name: HP Spectre x360 Convertible 15-bl1XX
https://store.hp.com/us/en/pdp/hp-spectre-x360-convertible-laptop-15t-touch-1wb97av-1
|
Processor and graphics
By curiosity, does anyone one not having a GeForce graphic card affected
by this bug so far (minus the Apple one) ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767720
Title:
Ubiquity crashed duri
PJSingh5000 (pjsingh5000),
It's because you try to open the ubiquity python program directly with
gdb.
Install python3 debug symbol (python3-dbg), then try something like this
:
gdb -ex r --args /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity gtk_ui
or if the process is already running :
gdb p
This bug was fixed a few years ago.
# Debian unstable
ksh-93u+20120801/debian/changelog: * cd built-in now properly fixed upstream.
(Really Closes: #679966)
ksh-93u+20120801/debian/changelog: * New upstream release (closes: #679966)
# Trusty
ksh-93u+20120801/debian/changelog: * cd built-in no
A test package is now available for testing (pre-sru) to determine if
this fixes the problem in Ubuntu as well.
# Instructions
sudo add-apt-repository ppa:slashd/sf143225ksh
sudo apt-get update
sudo apt-get install ksh
# Validation
dpkg -l | grep -i ksh should reveal version : ksh - 93u+20120801
^^ should reveal version: ksh - 93u+20120801-1+sf143225b2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1697501
Title:
ksh segfault on job_chksave () after it receive a SIGCHLD (Signal 17)
To man
Action items :
- tracking down upstream maintenance
- fix segfaulting binaries
- evaluating all dependencies
- base dep8 tests included
** Tags added: sts
** Changed in: pcp (Ubuntu)
Assignee: (unassigned) => Dariusz Gadomski (dgadomski)
--
You received this bug notification because you a
Public bug reported:
[Availability]
Available:
pcp | 3.11.10 | artful/universe | source, amd64, arm64, armhf, i386,
ppc64el, s390x
[Rationale]
This is a valuable source of metrics for large deployments. There are numerous
users with large installations interested in having it in fully su
** Description changed:
[Availability]
Available:
pcp | 3.11.10 | artful/universe | source, amd64, arm64, armhf, i386,
ppc64el, s390x
+
[Rationale]
This is a valuable source of metrics for large deployments. There are
numerous users with large installations interested in having
** Description changed:
[Availability]
Available:
pcp | 3.11.10 | artful/universe | source, amd64, arm64, armhf, i386,
ppc64el, s390x
[Rationale]
This is a valuable source of metrics for large deployments. There are
numerous users with large installations interested in having
The following, must first be addressed before this package would be accepted
into main :
- tracking down upstream maintenance
- fix segfaulting binaries
- evaluating all dependencies
- base dep8 tests included
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Other discussions
# systemd or sysv ??
Dariusz:
Do we need to port it to systemd or are sysv script is fine?
Christian:
In general sysv is fine, but there are a few issues due using the "old" calls
e.g. if you have PCP running in a container it will collide on the Host (no
service start,
** Also affects: sssd (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: sssd (Ubuntu Xenial)
Assignee: (unassigned) => Victor Tapia (vtapia)
** Changed in: sssd (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: sssd (Ubuntu Xenial)
Status: New
*** This bug is a duplicate of bug 1695870 ***
https://bugs.launchpad.net/bugs/1695870
IMHO, I would suggest, to make the Xenial SRU process easier, to
continue with the original bug and nominate Xenial to it and then mark
this bug as duplicate.
It'll facilitate the verification for the SRU t
*** This bug is a duplicate of bug 1695870 ***
https://bugs.launchpad.net/bugs/1695870
** This bug has been marked a duplicate of bug 1695870
[regression] sssd won't start if autofs is not installed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
Uploaded into Xenial upload queue. Now waiting for SRU team approval to
start building in xenial-proposed.
- Eric
** Tags removed: verification-done
** Tags added: verification-done-trusty
** Tags removed: sts-sru-done
** Tags added: sts-sru-needed
--
You received this bug notification because
** Tags removed: sts-sru-needed
** Tags added: sts-sru-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1366997
Title:
Duplicate entry error for primary key following cluster size change
To manag
** Description changed:
[Impact]
* On Trusty, SSSD does not start when AutoFS is not installed because the
AutoFS "starting" signal is not emitted.
* This only affects the upstart service (Trusty). Systemd services work fine.
[Test Case]
* Install SSSD in a machine without A
** Description changed:
[Impact]
- * The compiler optimization dropped parts from the ksh job
+ * The compiler optimization dropped parts from the ksh job
locking mechanism from the binary code. As a consequence, ksh could terminate
unexpectedly with a segmentation fault after it receiv
** Tags removed: sts-sru-needed
** Tags added: sts-sru-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1686679
Title:
[SRU] Ubuntu16.04 : autofs is extremely long with large number of
direct ma
501 - 600 of 3379 matches
Mail list logo
