Thank you for your report and helping to make Ubuntu better.
The relevant code that failed is here:
https://git.launchpad.net/ubuntu/+source/screen/tree/debian/screen.preinst?h=ubuntu
/bionic-devel
As far as I can tell, this would only happen if /run/screen/ didn't
exist prior to your release
/var/log/boot.log: Starting dGPU off during boot...
/var/log/boot.log:[FAILED] Failed to start dGPU off during boot.
Unfortunately my Clevo laptop doesn't have an option in the firmware to disable
Secure boot and I'm already running in BIOS mode rather than UEFI. (Same basic
details as
Confirmed it broke monit the same way on all our live 16.04 servers.
Also em unable to re-monitor service that once went un-monitored due to failure
attempts.
Gives the dreaded:
`Invalid action "action=monitor"`
message.
Haven't yet tested how that affects general reportability and
OS and package versions:
squirrel:~ 0:55> cat /etc/os-release | grep VERSION=
VERSION="18.04.1 LTS (Bionic Beaver)"
squirrel:~ 0:56> dpkg -s libosinfo-bin | grep '^Version:'
Version: 1.1.0-1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
>From log:
Preparing to unpack .../screen_4.6.2-1ubuntu1_amd64.deb ...
chmod: cannot access '/run/screen': No such file or directory
[1mdpkg:[0m error processing archive
/var/cache/apt/archives/screen_4.6.2-1ubuntu1_amd64.deb (--unpack):
new screen package pre-installation script subprocess
Public bug reported:
There does not seem to be an entity in the database for 'ubuntu18.04'.
The latest is 'ubuntu17.10':
squirrel:~ 0:47> osinfo-query os | grep ubuntu18.04
squirrel:~ 1:48> osinfo-query os | grep ubuntu
ubuntu10.04 | Ubuntu 10.04 LTS |
Public bug reported:
After few suspends or detach-/attachments of USB devices libinput starts
ignoring new devices due to too many input devices. Unnecessary to say
there is only one device attached.
journalctr reports this behavior:
/usr/lib/gdm3/gdm-x-session[1407]: (**) PixArt USB Optical
I've generated a report with a version pre 7.3, then, upgrade apport and
report it with 7.4 and I didn't trigger any crash.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You received this bug notification because you
Confirmed to be an issue on Bionic
The upstream fix is in v1.39.1 originally, but was also picked for 1.38.1.
Due to that Cosmic already has the fix that is required.
Note: I verified that it works on cosmic and it does work
** Changed in: libguestfs (Ubuntu Bionic)
Status: New =>
Will be good to see this issue addressed. I encountered this bug while
running regression test for Xyce 6.9 parallel build and the error
occurred in Zoltan module. I wonder whether this has an impact on other
packages--for example ngspice--built with mpi options. SHould we be
suspicious of openmpi
Logs not necessary at this time, will attach patches and other
information as needed.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I get the same on my 16.04 test server.
However, things seems to work fine, if I allocate enough memory, on my
test 18.04 server VM (which runs on the aforementioned 16.04 test
server).
My real purpose here is to update the Ubuntu serverguide to deal with
bug 1769130.
--
You received this bug
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: kexec-tools (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794230
Title:
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
It look like an exim4 maintainer script experienced a failure on release
upgrade from Xenial to Bionic following a local configuration
customisation in the Xenial timeframe that Bionic's exim4 does not
understand,
I think we have a couple of open questions on this bug in Ubuntu then:
1) Is it fixed upstream?
2) Sam's question: what's the actual impact to Ubuntu users?
Since we can't make progress without these questions answered, and
depending on the answers we might not consider this to be a bug in
I've no other reason for this to MIR this apart from the requirement for
DPDK, so I'm OK with it being lowered in priority
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1786201
Title:
MIR for
Public bug reported:
Every update I have problem signalization
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: grub-efi-amd64-signed 1.93.5+2.02-2ubuntu8.4
ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
Uname: Linux 4.15.0-34-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.3
FYI: I'm going to try breaking up some dependencies in DPDK so that not
all of DPDK will end up in Main. The intention is to have commonly used
and well tested PMDs and libs in main, but some of the more edge-cases
can stay in Universe.
In that sense the lib that needs intel-ipsec-mb would become
Dep8 tests (rather basic) complete and ok.
Waiting for MP review and PPA testing now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1792400
Title:
smbd failed in host when both lxd container and
This also affects Bionic and I added a bug task for it, but lets
complete Cosmic before starting/considering the SRU.
** Also affects: amavisd-new (Ubuntu Cosmic)
Importance: Undecided
Status: Triaged
** Also affects: amavisd-new (Ubuntu Bionic)
Importance: Undecided
Status:
** Also affects: virt-manager (Ubuntu Cosmic)
Importance: Low
Status: Invalid
** Also affects: libguestfs (Ubuntu Cosmic)
Importance: Low
Status: Confirmed
** Also affects: virt-manager (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: libguestfs
As to Joshua's question:
Customization of hostname is using "hostnamectl set-hostname theNewHostName"
which requires 'dbus.service' is running. We found the dbus.service might not
be running when perl/cloud-init executes the hostnamectl command on Ubuntu18.04
(Open-vm-tools v10.2.0).
As the
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1794232
and then change the status of the bug to 'Confirmed'.
If, due to the
Public bug reported:
See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908087, please
upgrade to python3-pysimplesoap 1.16-2.1 from Debian.
** Affects: pysimplesoap (Ubuntu)
Importance: Undecided
Status: New
** Tags: cosmic
--
You received this bug notification because you
We have just spent today hunting down a user bug report for Xyce (which
uses Trilinos, and its Zoltan library) that turn out to be exactly this
issue -- the user is seeing strange results from Xyce, and one of our
developers tracked it to exactly the issue that MPI_Send "to" the same
processor is
Public bug reported:
[Impact]
When attempting to create a geneve tunnel on Ubuntu 16.04 Xenial, in
an OS environment with open vswitch, where ipv6 has been disabled,
the create fails with the error :
“ovs-vsctl: Error detected while setting up 'geneve0': could not
add network device geneve0
Strongswan hit a rather similar issue with a build time test timing out
that was always fine in the past and now seems flaky (worked on retry).
Local tests were all successful, if there really is any slowdown on the
builders it might be the same issue - so I dupped it here to re-check
once there
This is fixed with x-x-v-ati 1:18.1.0-1
Thanks!
** Changed in: xorg-server (Ubuntu)
Status: Incomplete => Fix Released
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
install mesa from a ppa:
apt-add-repository ppa:canonical-x/x-staging
and install updates
** Changed in: xorg (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
abc
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg (not installed)
ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140
Uname: Linux 4.4.0-134-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 25
*** This bug is a duplicate of bug 1794059 ***
https://bugs.launchpad.net/bugs/1794059
Those builds used to be very reliable so far but recently started to
"sometimes" break on:
Failure in 'test_multiread': timeout(14) (i = 0)
I started to work on that in bug 1794224 , but it has all the
Looks like the recent astroid rebuild/changes removed the file, but it's
still present in alembic
** Changed in: alembic (Ubuntu)
Importance: Critical => High
** Changed in: astroid (Ubuntu)
Importance: Critical => High
** Changed in: dh-python (Ubuntu)
Importance: Critical => High
**
401 - 432 of 432 matches
Mail list logo
