** Changed in: sosreport (Ubuntu Xenial)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1883320
Title:
[kvm] change check_enabled to /dev/kvm
To manage notificatio
** Changed in: sosreport (Ubuntu Xenial)
Status: Won't Fix => In Progress
** Changed in: sosreport (Ubuntu Xenial)
Assignee: (unassigned) => Eric Desrochers (slashd)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
** Also affects: sosreport (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: sosreport (Ubuntu Xenial)
Importance: Undecided => Low
** Changed in: sosreport (Ubuntu Xenial)
Assignee: (unassigned) => Eric Desrochers (slashd)
** Changed in: sosreport (
** Changed in: sosreport (Ubuntu Xenial)
Status: New => In Progress
** Changed in: sosreport (Ubuntu Xenial)
Assignee: (unassigned) => Eric Desrochers (slashd)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: sosreport (Ubuntu Xenial)
Status: Won't Fix => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884293
Title:
Update to maintenance release v3.9.1
To manage notifica
** Description changed:
[Impact]
Endpoints that have been updated with python 3.8 seem to cause issues
with sshuttle.
[Test Case]
Client
$ python3 --version
Python 3.8.2
$ lsb_release -rd
Description:Ubuntu Focal Fossa (development branch)
Release:20.04
$
** Tags removed: sts-sponsor-slashd
** 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/1873368
Title:
ssshuttle server fails to connect endpoints with python 3.8
To manage notificatio
y
(python-pytest-runner, python-pytest-cov
- Added a DEP3 header in the quilt patch.
- Slighly modified d/changelog to reflect the minor changes.
- Eric
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
** Tags added: sts-sponsor-slashd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873368
Title:
ssshuttle server fails to connect endpoints with python 3.8
To manage notifications about this bug go
** Changed in: sshuttle (Ubuntu Focal)
Assignee: Dan Hill (hillpd) => Felipe Reyes (freyes)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873368
Title:
ssshuttle server fails to connect endpoi
Public bug reported:
cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION="Ubuntu 18.04.4 LTS"
screenfetch
./+o+- @BazUbu
y- -yy+ OS: Ubuntu 18.04 bionic
** Description changed:
+ [Impact]
+
+ [Test Case]
+
+ [Regression Potential]
+
+ [Other Info]
+
+ [Original Description]
+
Client
$ python3 --version
Python 3.8.2
$ lsb_release -rd
Description:Ubuntu Focal Fossa (development branch)
Release:20.04
- $ apt-cache policy
@freyes
Do you have your focal debdiff handy still ?
I'll be happy to sponsor the work you did for sshuttle focal.
- Eric
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873368
Title:
sssh
Next step is to introduce the fix through SRU into sshuttle version
"0.78.5-1".
** Changed in: sshuttle (Ubuntu Groovy)
Assignee: Dan Hill (hillpd) => (unassigned)
** Changed in: sshuttle (Ubuntu Focal)
Status: Confirmed => In Progress
--
You received this bug notification because y
[Groovy]
# Launchpad
https://launchpad.net/ubuntu/+source/sshuttle
# rmadison
sshuttle | 1.0.3-1 | groovy/universe | source, all
# changelog
sshuttle (1.0.3-1) unstable; urgency=medium
[ Brian May ]
* Update to latest upstream version. Closes: #953621.
* Upstream has drop
@smoser,
Not for focal, but for the active development release and debian
unstable I suggest we bump to 1.0.2.
As part of the SRU, just cherry-pick the desired fix.
- Eric
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
[Autopkgtest regression report (sosreport/3.9.1-1ubuntu0.2]
Regression PASSED at 3rd attempts.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886494
Title:
sosreport does not correctly enable the m
modern dh compat
version, ...
* (B) Cherry-pick the 3.8 fix[0] into Debian so that Ubuntu can then
follows.
- Eric
** Bug watch added: Debian Bug tracker #953621
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953621
** Also affects: sshuttle (Debian) via
https://bugs.debian.org/cgi-bin
/comments/6
It is just a matter of retrying the job until it passes. I'm on it.
- Eric
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886494
Title:
sosreport does not correctly enable the maas p
Public bug reported:
Two-finger scrolling works fine on boot, but on my Thinkpad T440s after
I resume from suspend, two-finger scrolling no longer works. Touchpad
still works to move the mouse and click, but two-finger scrolling does
not.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xser
[VERIFICATION FOCAL]
This has been tested running sosreport (3.9.1-1ubuntu0.20.04.2)
# sos_logs/sos.log revealed that the MAAS plugin has been exercised on a
MAAS snap install as expected.
# No errors found.
# Logs
sos.log:2020-07-09 15:18:38,105 INFO: [plugin:maas] added cmd output 'systemctl
[VERIFICATION BIONIC]
This has been tested running sosreport (3.9.1-1ubuntu0.18.04.2)
# sos_logs/sos.log revealed that the MAAS plugin has been exercised on a
MAAS snap install as expected.
# No errors found.
# Logs
sos.log:2020-07-09 15:12:01,034 INFO: [plugin:maas] added cmd output 'systemctl
** Description changed:
For Bionic release, current cifs-utils package version is 6.8-1. This
version is missing an ACL tools fix that is needed for Azure xSMB.
Commit in question which needs to be backported:
0feb1a80f3777f4c244b46958aa9f730de9e18b6 setcifsacl: fix adding ACE when
ow
Uploaded in Bionic/18.04LTS.
It is now waiting for SRU team approval for the package to start
building in bionic-proposed pocket for its testing/verification phase.
Regards,
Eric
** Description changed:
For Bionic release, current cifs-utils package version is 6.8-1. This
version is
ifs-utils (Ubuntu Bionic)
Status: New => In Progress
** Changed in: cifs-utils (Ubuntu Bionic)
Assignee: (unassigned) => Eric Desrochers (slashd)
** Description changed:
For Bionic release, current cifs-utils package version is 6.8-1. This
version is missing an ACL tools fix tha
Uploaded in Bionic/18.04LTS. It is now waiting for SRU team approval.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886494
Title:
sosreport does not correctly enable the maas plugin for a snap inst
Uploaded in Focal/20.04LTS. It is now waiting for SRU team approval.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886494
Title:
sosreport does not correctly enable the maas plugin for a snap insta
I'm also affected by this bug. It is many months later, but a recent
update to some 20.04 package caused this to start happening. Any
suggested solutions other than "learn docker, install a new VM etc"?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
** Description changed:
[Impact]
sosreport doesn't exercise the MAAS plugin if it is installed as a SNAP.
Only work if installed as a DEB package.
[Test Case]
* snap install maas
* sosreport -a
* Looking the sosreport archive content and validate that MAAS information
haven
** Description changed:
[Impact]
sosreport doesn't exercise the MAAS plugin if it is installed as a SNAP.
Only work if installed as a DEB package.
[Test Case]
* snap install maas
- * sosreport -a
+ * sosreport -a
* Looking the sosreport archive content and validate that MAAS
** Description changed:
+ [Impact]
+
+ sosreport doesn't exercise the MAAS plugin if it is installed as a SNAP.
+ Only work if installed as a DEB package.
+
+ [Test Case]
+
+ * snap install maas
+ * sosreport -a
+ * Looking the sosreport archive content and validate that MAAS information
have
=> In Progress
** Changed in: sosreport (Ubuntu Focal)
Assignee: (unassigned) => Eric Desrochers (slashd)
** Changed in: sosreport (Ubuntu Bionic)
Assignee: (unassigned) => Eric Desrochers (slashd)
** Changed in: sosreport (Ubuntu Groovy)
Status: In Progress => Fix
nce: Undecided
Status: New
** Changed in: sosreport (Ubuntu Groovy)
Assignee: (unassigned) => Eric Desrochers (slashd)
** Changed in: sosreport (Ubuntu Groovy)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs,
$ git log --oneline 3.9.1..HEAD sos/report//plugins/maas.py
6c334d55 [plugins] Convert docstrings to class attrs
=> 1417827a [maas] Add snap support to maas plugin
71428ba1 [global] Fix report import paths
dfcabc68 [4.0] Re-organize tree for sos-4.0
The plug update has been added after 3.9.1. We
Public bug reported:
"GCE request" seems to indicate a preference for the 'noop' scheduler,
but w/ a recently created GCE instance using the Ubuntu18 image &
5.3.0-1029-gcp kernel, noop is not an available option (only 'none' and
'mq-deadline' are available). Apparently 5.0 kernels no longer suppo
** Tags removed: verification-needed verification-needed-bionic
verification-needed-focal
** Tags added: verification-done verification-done-bionic
verification-done-focal
** Changed in: sosreport (Ubuntu Xenial)
Status: Confirmed => Won't Fix
--
You received this bug notification becau
Public bug reported:
I've tried with the past two daily images to install in VirtualBox and
both have crashed while installing.
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: ubuntu-release-upgrader-core 1:20.10.3
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-2
@dnegreira,
Did you have the time to test the new sosreport build ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884293
Title:
Update to maintenance release v3.9.1
To manage notifications about
IMHO, no further testings is needed for sosreport in EOAN, as it will
soon reach EOL anyway and the current testing I did where satisfying.
We don't expect UA customer to run complex environment on EOAN. They
stick to LTS version on purpose.
- Eric
--
You received this bug notification be
IMHO, no further testings is needed for sosreport in EOAN, as it will
soon reach EOL anyway and the current testing I did was satisfying.
We don't expect UA customer to run complex environment on EOAN (Cloud,
JuJu, MAAS, Landscape and such). They stick to LTS version on purpose.
- Eric
--
arameter all works as expected.
* --upload work and got uploaded into our FTP uploads/ folder.
- Eric
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884293
Title:
Update to maintenance re
This above has been tested in a variety of server type : HW, containers
and VM.
** Tags removed: verification-needed-eoan
** Tags added: verification-done-eoan
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
d.
* No non-legit 0 size files found.
* Commonly used parameter all works as expected.
* --upload work and got uploaded into our FTP uploads/ folder.
- Eric
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/188
[VERIFICATION BIONIC]
Test with sosreport: 3.9.1-1ubuntu0.18.04.1
* Running sosreport from for instance an LXD container, no longer reveal
KVM details from its host as it was previously (if KVM was installed at
the host level):
** ls -altr sos_commands/kvm
ls: cannot access 'sos_commands/kvm':
[VERIFICATION FOCAL]
Test with sosreport: 3.9.1-1ubuntu0.20.04.1
* Running sosreport from for instance an LXD container, no longer reveal
KVM details from its host as it was previously (if KVM was installed at
the host level):
** ls -altr sos_commands/kvm
ls: cannot access 'sos_commands/kvm': N
[VERIFICATION EOAN]
Test with sosreport: 3.9.1-1ubuntu0.19.10.1
* Running sosreport from for instance an LXD container, no longer reveal
KVM details from its host as it was previously (if KVM was installed at
the host level):
** ls -altr sos_commands/kvm
ls: cannot access 'sos_commands/kvm': No
to worry about here.
** ls sos_logs/
sos.log ui.log
No Stack Trace file found.
* No non-legit 0 size files found.
* Commonly used parameter all works as expected.
* --upload work and got uploaded into our FTP uploads/ folder.
- Eric
--
You received this bug notification because you
[Autopkgtest regression report (sosreport/3.9.1-1ubuntu0.18.04.1)]
Regression is now gone after the 3rd attempt. It was indeed related to
the autopkgtest environment.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
[Autopkgtest regression report (sosreport/3.9.1-1ubuntu0.18.04.1)]
http://autopkgtest.ubuntu.com/packages/s/sosreport/bionic/armhf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884293
Title:
Updat
Reminder that there is still a bounty for this issue at BountySource
https://www.bountysource.com/issues/55506502-add-va-api-hardware-
decoding-support-on-linux
I got an email from BountySource that they're going to start taking old
bounties for themselves starting *2020-07-1* (reproduced below)
** Description changed:
[Impact]
sosreport 3.9.1 is now released.
It would be great to find sosreport v3.9.1 in supported stable releases,
and active development release considering the fact that the releases
(especially LTSes) are going to be supported for a couple of years.
[Autopkgtest regression report (sosreport/3.9.1-1ubuntu0.18.04.1)]
sos-run-nonroot.py PASS
sos-run.py PASS
simple.shFAIL non-zero exit status 1
...
File "/tmp/autopkgtest.xKfdM6/build.M79/src/sos/utilities.py", line 259, in
return ''.join(ln.decode('utf-8', 'ignore
signee: (unassigned) => Eric Desrochers (slashd)
** Changed in: sosreport (Ubuntu Bionic)
Assignee: (unassigned) => Eric Desrochers (slashd)
** Changed in: sosreport (Ubuntu Groovy)
Importance: Undecided => Medium
** Changed in: sosreport (Ubuntu Eoan)
Importance: Undecided => Med
signee: (unassigned) => Eric Desrochers (slashd)
** Changed in: sosreport (Ubuntu Eoan)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884293
Title:
Update to
For the package to get promoted from focal-proposed to focal-updates,
one needs to change the tag from 'verification-needed-focal' to
'verification-done-focal' and leave a comment with the outcome of the
-proposed package testing.
Once one does that, the vagrant package will turn green in pending
https://wiki.ubuntu.com/StableReleaseUpdates#Verification
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871685
Title:
[SRU] vagrant spits out ruby deprecation warnings on every call
To manage noti
** Description changed:
[Impact]
sosreport 3.9.1 is now released.
It would be great to find sosreport v3.9.1 in supported stable releases,
and active development release considering the fact that the releases
(especially LTSes) are going to be supported for a couple of years.
-
t; - d/p/0003-kvm-change-trigger-to-dev-kvm.patch <==
** Changed in: sosreport (Ubuntu Groovy)
Status: In Progress => Fix Released
** Changed in: sosreport (Ubuntu Focal)
Status: New => In Progress
** Changed in: sosreport (Ubuntu Focal)
Assignee: (unassigned) =
** Changed in: sosreport (Ubuntu Bionic)
Status: In Progress => Confirmed
** Changed in: sosreport (Ubuntu Xenial)
Status: In Progress => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
ndecided
Status: Fix Released
** Affects: sosreport (Ubuntu Xenial)
Importance: Medium
Assignee: Eric Desrochers (slashd)
Status: In Progress
** Affects: sosreport (Ubuntu Bionic)
Importance: Medium
Assignee: Eric Desrochers (slashd)
Status
pick the commit into v0.78 (if feasible) through SRU
for Focal and any other impacted and supported releases.
- Eric
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873368
Title:
ssshuttle ser
Reminder that there is still a bounty for this issue at BountySource
https://www.bountysource.com/issues/55506502-add-va-api-hardware-
decoding-support-on-linux
I got an email from BountySource that they're going to start taking old
bounties for themselves starting *2020-07-1* (reproduced below)
* Also affects: sosreport (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: sosreport (Ubuntu Groovy)
Importance: Undecided
Assignee: Eric Desrochers (slashd)
Status: In Progress
** Also affects: sosreport (Ubuntu Focal)
Importance: Undecided
Status:
thub.com/sosreport/sos/pull/2063/commits/dc58a038c18ff3e838d883d4b31aad5dac7ea9e1
** Affects: sosreport (Ubuntu)
Importance: Undecided
Assignee: Eric Desrochers (slashd)
Status: In Progress
** Affects: sosreport (Ubuntu Xenial)
Importance: Undecided
Status: New
** Affects: s
** Also affects: makedumpfile (Ubuntu)
Importance: Undecided
Status: New
** Changed in: makedumpfile (Ubuntu Groovy)
Importance: Undecided => Medium
** Changed in: makedumpfile (Ubuntu Groovy)
Status: New => In Progress
** Changed in: makedumpfile (Ubuntu Groovy)
Assigne
[Groovy sponsor]
Nitpicking:
* Renamed "align_PMD_SECTION_MASK_with_PHYS_MASK.patch"
0003-align_PMD_SECTION_MASK_with_PHYS_MASK.patch to match his current
little friend "0002-adapt-makefile-to-debian.patch"
* Added more detail in the debian/changelog to ease future reference in a
simple look:
[Groovy sponsor]
Nitpicking:
* Renamed "align_PMD_SECTION_MASK_with_PHYS_MASK.patch"
0003-align_PMD_SECTION_MASK_with_PHYS_MASK.patch to match his current
little friend "0002-adapt-makefile-to-debian.patch"
* Added more detail in the debian/changelog to ease future reference in a
simple look:
[Groovy sponsor]
Nitpicking:
* Renamed "align_PMD_SECTION_MASK_with_PHYS_MASK.patch"
0003-align_PMD_SECTION_MASK_with_PHYS_MASK.patch which his little
current friend "0002-adapt-makefile-to-debian.patch"
* Added more detail in the debian/changelog to ease future reference in a
simple look:
Disregard my last comment (#15) ...
I was confused for a second between :
#define PHYS_MASK ((1UL << PHYS_MASK_SHIFT) - 1)
#define PMD_SECTION_MASK((1UL << 40) - 1)
so PMD_SECTION_MASK fix is not found in debian yet.
I'll sponsor the debdiff over the
27;
makedumpfile (1:1.6.7-2)
# arch/arm64.c
84 #define PMD_SECTION_MASK((1UL << 40) - 1)
- Eric
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1869465
Title:
Kdump-Tools: Makedumpfile F
** Tags removed: sts-sponsor-mfo
** Tags added: sts-sponsor-mfo-and-slashd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1869465
Title:
Kdump-Tools: Makedumpfile Failed, Falling Back To 'Cp'
To man
am, let's do it.
Debian maintainer will be the ultimate approver/merger.
- Eric
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573095
Title:
Cloud images fail to boot when a serial port is not
@Hui
Again so sorry for the delay
I've removed all instances of the dmic_detect=0 and attached the dmesg for
both the 5.3.0-46 and 5.3.0-53 versions.
Thank you so much
On Wed, May 13, 2020 at 9:55 PM Hui Wang wrote:
> @Eric,
>
> please run "sudo grep dmic_detect /etc/* -r
@Eric
We are in discussion atm trying to resolve the maintainer transition upstream.
As soon as the maintainer aspect is figured out, hopefully the code will be
merge in the official project and not only the fork.
And then I'll be happy to update the Ubuntu apt-mirror package in the
U
This is quite ridiculous, would it not be possible to apply the fix toe
apt-mirror already?
I'd rather not use a modified third party apt-mirror tool if it can be
helped.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
This happened to me just now on a fresh installation of 20.04. Exactly
as reported - first attempt at calibration with a Spyder 3 fails, on the
second attempt gnome-control-center crashes hard.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
Thanks Till. Still no luck:
Remove and reinstall:
---
Preparing to unpack .../0-printer-driver-postscript-hp_3.20.3+dfsg0-2_amd64.deb
...
Unpacking printer-driver-postscript-hp (3.20.3+dfsg0-2) over (3.20.3+dfsg0-2)
...
Preparing to unpack .../1-libsane-hpaio_3.20.3+dfsg0-2_amd64.deb ...
Unpacki
** Changed in: systemd (Ubuntu Xenial)
Status: In Progress => Won't Fix
** Changed in: systemd (Ubuntu Xenial)
Assignee: Eric Desrochers (slashd) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
it and problem persisted.
- Eric
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879987
Title:
machine get stuck at boot if specified 'console=ttyS* ' doesn't exist.
To manage noti
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: initramfs-tools (Ubuntu)
Status: New => Confirmed
** Changed in: initramfs-tools (Ubuntu)
Importance: Undecided => High
** Changed in: initramfs-tools (Ubuntu)
Assignee: (unassigned) => Guilherme G
** Summary changed:
- kernel get stuck at boot if specified 'console=ttyS* ' doesn't exist.
+ machine get stuck at boot if specified 'console=ttyS* ' doesn't exist.
** Also affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification becaus
Related public bugs found here and there:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960355
https://github.com/systemd/systemd/issues/15783
https://github.com/systemd/systemd/issues/15656
** Bug watch added: Debian Bug tracker #960355
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=96
I observed the random kernel spew on my reproducer but I also want to
add that it was also noticed on my VMware impacted contact who brought
this up to my attention at the first place.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
I don't know yet if related, but I also observed the following:
syslog:May 21 17:25:27 ubuntu kernel: [0.00] random: get_random_bytes
called from start_kernel+0x99/0x4fd with crng_init=0
syslog:May 21 17:25:27 ubuntu kernel: [1.902484] random: lvm: uninitialized
urandom read (4 bytes
from dmesg (took from virsh dump)
[0.00] Command line: BOOT_IMAGE=/vmlinuz-4.15.0-101-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro console=ttyS4
..
[1.053683] Warning: unable to open an initial console.
--
You received this bug notification because you are a member of Ubunt
** Changed in: linux (Ubuntu)
Importance: Medium => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879987
Title:
kernel get stuck at boot if specified 'console=ttyS* ' doesn't exist.
To man
Public bug reported:
kernel get stucks at boot if console=ttyS* is specified in the kernel
cmdline and that serial HW isn't available on the system.
Reproduced with:
4.4 (from Xenial), 4.15 (from Bionic), 5.4 (native, Focal) and 5.7-next
(mainline)
Removing the non-existent 'console=ttyS*' para
** Description changed:
kernel get stucks at boot if console=ttyS* is specified in the kernel
cmdline and that serial HW isn't available on the system.
Reproduced with:
4.4 (from Xenial), 4.15 (from Bionic), 5.4 (native, Focal) and 5.7-next
(mainline)
- Removing the non-existent 'co
** Description changed:
kernel get stucks at boot if console=ttyS* is specified in the kernel
cmdline and that serial HW isn't available on the system.
Reproduced with:
4.4 (from Xenial), 4.15 (from Bionic), 5.4 (native, Focal) and 5.7-next
(mainline)
Removing the non-existent 'co
** Description changed:
[Impact]
In Xenial/16.04LTS, one can't generate network interface name from
"phys_port_name" attribute.
"phys_port_name" indicates the interface physical port name within the
NIC.
[Test Case]
Check that udev (systemd-udevd) provides the phys_port_name
** Description changed:
[Impact]
In Xenial/16.04LTS, one can't generate network interface name from
"phys_port_name" attribute.
"phys_port_name" indicates the interface physical port name within the
NIC.
[Test Case]
Check that udev (systemd-udevd) provides the phys_port_name
Public bug reported:
Whenever the opacity of an object is changed to <1 that object vanish.
This occurs on my laptop (Intel HD Graphics 620) and on my office
desktop (NVIDIA GP108).
This appears to be a problem only with the repository version - I have
removed the repository version and installed
Same problem installing 3.20.5 on Ubuntu 20.04 (after an upgrade from 18.04)
Looks like hplip uses Python 2.7, but the python-pyqt5 package (Python 2
bindings for Qt5) is no longer available in the distro.
The corresponding package for Python3 is python3-pyqt5, which is available
--
You received
Public bug reported:
HP Laserjet 3030 prints PDFs with photos extremely slowly (sometimes 10 min per
page).
Worked fine under Ubuntu 16.04.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: cups 2.3.1-9ubuntu1.1
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-ge
ludes the code works (without the packaging layer)
What we want to know is if the package of sosreport (binary package)
works and do what we expect it to do.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on
how to enable and use -proposed.
- Eric
--
You received thi
(including their dependencies), that the binaries
are executed as expected, configuration (sos.conf) is in place,
Basically, the test result will be closer to reality where users will
install the sosreport binary package. They won't run sosreport from the
source package.
- Eric
--
** Changed in: json-c (Ubuntu)
Status: Fix Released => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878723
Title:
Kernel panic when used with upstart after 0.11-4ubuntu2.1 update
T
Public bug reported:
On ubuntu 20.04, there are no status overlay icon (green/orange/red dot)
over Nextcloud synced directories in Nautilus.
Packages installed:
python-nautilus
nextcloud-desktop
nautilus-nextcloud
Description:Ubuntu 20.04 LTS
Release:20.04
nextcloud-desktop:
Insta
I also experienced this bug today. What seems to have happened is that
upstart init filled all of the memory on my machine while libjson-c2 was
updating, leading to oom-killer killing everything. The kernel panic
here would happen if oom-killer tries to act on init. After a reboot my
machine manage
Since rabbitmq-server is a critical package and the (merge) upstream
bump has already been made.
Would it be possible to when time permit modernize (or at least evaluate
it) the packaging aspect ? It's the perfect time to do so before groovy
become stable in October.
I see this as work we do now,
801 - 900 of 10556 matches
Mail list logo
