Hi Steve,
You said:
~
Picking and choosing specific versions of packages from the archive as INPUT
into the ISO, as opposed to taking the most recent version of packages at the
time the ISO is built, would simply enable bad practices (omitting security
updates) and lure
The rationale behind this request is that the Telco customer has a
requirement to include such bootable Custom/Minimal 16.04 ISO image into
the block storage deliverable that they can provide to their own
customers.
The server is not connected to Internet
There are no local Ubuntu mirror servers
Public bug reported:
glusterfs-server installation fails on Bionic
apt-get install glusterfs-server
...
Job for glustereventsd.service failed because a timeout was exceeded.
See "systemctl status glustereventsd.service" and "journalctl -xe" for details.
invoke-rc.d: initscript glustereventsd,
Hi Joe,
I tried to install the Test Kernel on Xenial but I stumbled upon this
dependency issue
sudo dpkg -i linux-headers-4.15.0-43-generic_4.15.0-43.47~lp1779756_amd64.deb
...
linux-headers-4.15.0-43-generic depends on libssl1.1 (>= 1.1.0); however:
Package libssl1.1 is not installed.
Unfor
** Attachment added: ""bt" and "bt -l" from Kernel crashdump"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791758/+attachment/5187256/+files/CRASH_BT.log
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a memb
** Attachment added: "Call Trace from dmesg"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791758/+attachment/5187255/+files/DMESG_CALL_TRACE.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
Public bug reported:
The following Oops was discovered by user:
[684766.39] BUG: unable to handle kernel paging request at 2268
[684766.667642] IP: [] n_tty_receive_buf_common+0x6a/0xae0
[684766.668487] PGD 8019574fe067 PUD 19574ff067 PMD 0
[684766.669194] Oops: [#1] SMP
The verification was done using Test Case 1 and Test Case 2
However I noticed that in the Trusty version the lock file
is located at /var/lib/ebtables/lock
Whereas on the Xenial/Yakkety/Zesty versions lock file is
at /run/ebtables.lock
--
You received this bug notification because you are a mem
Hi All,
I have successfully tested the following versions of ebtables
for Trusty: 2.0.10.4-3ubuntu1.14.04.1 OK
for Xenial: 2.0.10.4-3.4ubuntu2 OK
for Yakkety: 2.0.10.4-3.5ubuntu1.16.10.1 OK
for Zesty: 2.0.10.4-3.5ubuntu1.17.04.1 OK
Szilard
** Tags removed: verif
** Description changed:
[Impact]
* ebtables uses creation of a file with an exclusive flag
as a lock to synchronize table modification when used
with --concurrent parameter.
* If ebtables crashes it will leave a stale lock file.
This will prevent another copy of ebtabl
this is only a test bugreport
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1668931
Title:
test
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/166
11 matches
Mail list logo
