looks like this is fixed with Kernel 6.12.6.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2073538
Title:
kacpi_notify high cpu on interrupt gpe17
To manage notifications about this bug go to:
http
I have this same issue on the HP Victus with a Ryzen 5-8645HS and NVIDIA
GeForce RTX 4050, it keeps having ACPI issues or so it says.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2073538
Title:
kac
This is the last bug on my todo list relating to ROCm in Ubuntu Noble.
If a rebuild doesn't get in until after release, users can set the
environment variable HSA_OVERRIDE_GFX_VERSION=10.3.0 as a workaround.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
Public bug reported:
There are fixes in rocprim 5.7.1-2 for gfx1031, gfx1032, gfx1033,
gfx1034, gfx1035 and gfx1036 (i.e., all RDNA 2 GPU hardware except for
Navi 21). In rocsparse, the rocprim bug manifests as failures in the
prune_dense2csr_by_percentage tests [1]. The rocprim library is header-
Thanks Graham!
For posterity, here are the test logs.
** Attachment added: "rocblas-5.5.1+dfsg-5-test.txt.gz"
https://bugs.launchpad.net/ubuntu/+source/rocblas/+bug/2063017/+attachment/5768898/+files/rocblas-5.5.1+dfsg-5-test.txt.gz
--
You received this bug notification because you are a me
Public bug reported:
Please sync hipfft 5.7.1-1 (universe) from Debian unstable (main)
The goal of this update is to get as much of the ROCm stack as possible onto
version 5.7.1. While the update of hipfft from 5.5.0 to 5.7.1 is an upstream
version change, this is just matching the same upstream
Public bug reported:
Please sync rocfft 5.7.1-1 (universe) from Debian unstable (main)
The goal of this update is to get as much of the ROCm stack as possible onto
version 5.7.1. While the update of rocfft from 5.5.0 to 5.7.1 is an upstream
version change, this is just matching the same upstream
Public bug reported:
Please sync hipsparse 5.7.1-1 (universe) from Debian unstable (main)
The goal of this update is to get as much of the ROCm stack as possible onto
version 5.7.1. While the update of hipsparse from 5.5.1 to 5.7.1 is technically
a upstream version change, this is just matching t
Public bug reported:
Please sync hipblas 5.5.1-4 (universe) from Debian unstable (main)
Changelog entries since current noble version 5.5.1-3build1:
hipblas (5.5.1-4) unstable; urgency=medium
* d/p/0007-hipsolver-compatibility.patch: add guard for hipblasOperation_t,
which had been misse
Public bug reported:
Please sync hipcub 5.7.1-3 (universe) from Debian unstable (main)
This package update builds the tests for Navi 31, Navi 32 and Navi 33
hardware, as well as fixing errors on Navi 22, Navi 23, Navi 24 and
Rembrandt hardware (if built against rocprim 5.7.1-2 or later; the
macro
Public bug reported:
Please sync rccl 5.4.3-3 (universe) from Debian unstable (main)
This package update adds tests and documentation, as well as enabling
support for Navi 31, Navi 32 and Navi 33 hardware.
Changelog entries since current noble version 5.4.3-1:
rccl (5.4.3-3) unstable; urgency=m
Public bug reported:
Please sync rocsparse 5.7.1-3 (universe) from Debian unstable (main)
This version builds the library for Navi 31, Navi 32 and Navi 33 GPUs.
There are a collection of other minor fixes.
# d/changelog since 5.7.1-2
rocsparse (5.7.1-3) unstable; urgency=medium
[ Christian K
Public bug reported:
Please sync rocblas 5.5.1+dfsg-5 (universe) from Debian unstable (main)
This version builds the library for Navi 31, Navi 32 and Navi 33 GPUs.
I will follow up with a build and test log.
# d/changelog since rocblas 5.5.1+dfsg-4
rocblas (5.5.1+dfsg-5) unstable; urgency=medi
** Attachment added: "rocsolver-5.5.1-5-install.txt"
https://bugs.launchpad.net/ubuntu/+source/rocsolver/+bug/2063016/+attachment/5768702/+files/rocsolver-5.5.1-5-install.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
Public bug reported:
Please sync rocsolver 5.5.1-5 (universe) from Debian unstable (main)
This version builds with -DOPTIMAL=ON, which significantly increases
performance at the cost of increased build time and binary size. It also
builds the library for Navi 31, Navi 32 and Navi 33 GPUs. There a
** Description changed:
Please sync rocprim 5.7.1-2 (universe) from Debian unstable (main)
- This sync requires a FeatureFreeze exception. This package version
- requires rocm-hipamd 5.7.1, which is being tracked in
- https://bugs.launchpad.net/ubuntu/+source/rocm-hipamd/+bug/2058606.
+ This
Thank you very much. The ROCm stack is in much better shape now that
rocm-hipamd 5.7.1-3 has migrated.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061048
Title:
Please RM arm64 binaries
To manag
rocrand 5.7.1-4 has been published
** Changed in: rocrand (Ubuntu)
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/bugs/2060424
Title:
Sync rocrand 5.7.1-4 (universe) fr
The stdgpu source package no longer produces the libstdgpu-hip-dev and
libstdgpu-hip0d binary packages on arm64 as of
1.3.0+git20220507.32e0517-5ubuntu1. There is a FTBFS bug affecting
stdgpu on amd64 and ppc64el on both noble and noble-proposed, so this
version won't migrate immediately. Regardles
To summarize the current state of this ticket, I still request removal
of:
hipcc 5.2.3-12 noble arm64
libamdhip64-5 5.2.3-12 noble arm64
libamdhip64-dev 5.2.3-12 noble arm64
libhiprtc-builtins5 5.2.3-12 noble arm64
libstdgpu-hip-dev 1.3.0+git20220507.32e0517-5 noble arm64
libstdgpu-hip0d 1.3.0+gi
> It is straightforward to drop libamdhip64-dev from the stdgpu build
depends on arm64, so the leftover openmp variants should not block any
future fixes to this package. I will prepare a merge request doing that.
The merge request:
https://code.launchpad.net/~slavik81/ubuntu/+source/stdgpu/+git/s
Hi Steve,
I believe the rocm-hipamd request is complete. Here is a listing of the
reasoning for every reverse-depends of rocm-hipamd:
Reverse-Depends
===
* libhiprand-dev (for libamdhip64-dev) - removed in in this request
* libhiprand1 (for libamdhip64-5) - removed in in this request
** Patch added: "rm-rocm-arm64-2061253.debdiff"
https://bugs.launchpad.net/ubuntu/+source/stdgpu/+bug/2061253/+attachment/5764916/+files/rm-rocm-arm64-2061253.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
Public bug reported:
rocm-hipamd FTBFS on arm64 in noble due to
https://bugs.launchpad.net/ubuntu/+source/mumax3/+bug/2032624. It seems
unlikely that a fix for glibc can be merged in time for noble. I have
requested for the arm64 binaries for rocm-hipamd be removed from the
archive so that fixes f
Considering stdgpu further, it would be sufficient to only remove:
libstdgpu-hip-dev 1.3.0+git20220507.32e0517-5 noble arm64
libstdgpu-hip0d 1.3.0+git20220507.32e0517-5 noble arm64
It is straightforward to drop libamdhip64-dev from the stdgpu build
depends on arm64, so the leftover openmp variant
While the build dependency on librocthrust-dev is not an issue, the
build dependency on libamdhip64-dev is.
** Changed in: stdgpu (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
The header-only libraries are librocprim-dev, librocthrust-dev and
libhipcub-dev. Those are not arm64 binaries and should not be removed.
My apologies for including them in this list.
However, the arm64 binaries for stdgpu should still be removed. Not
because they depend on librocthrust-dev, but b
Oof. You're right. Thank you for catching that error .
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061048
Title:
Please RM arm64 binaries
To manage notifications about this bug go to:
https://bu
** Description changed:
The rocm-hipamd package has been FTBFS on arm64 in noble since the
update to glibc 2.38 last year, as per
https://bugs.launchpad.net/ubuntu/+source/rocm-hipamd/+bug/2032624. In
fact, all libraries written in the HIP language have been FTBFS on arm64
since then. Th
** Description changed:
The rocm-hipamd package has been FTBFS on arm64 in noble since the
update to glibc 2.38 last year, as per
https://bugs.launchpad.net/ubuntu/+source/rocm-hipamd/+bug/2032624. In
fact, all libraries written in the HIP language have been FTBFS on arm64
since then. Th
** Description changed:
The rocm-hipamd package has been FTBFS on arm64 in noble since the
update to glibc 2.38 last year, as per
https://bugs.launchpad.net/ubuntu/+source/rocm-hipamd/+bug/2032624. In
fact, all libraries written in the HIP language have been FTBFS on arm64
- since then. Th
** Also affects: rocrand (Ubuntu)
Importance: Undecided
Status: New
** Also affects: rocprim (Ubuntu)
Importance: Undecided
Status: New
** Also affects: rocthrust (Ubuntu)
Importance: Undecided
Status: New
** Also affects: rocfft (Ubuntu)
Importance: Undecided
Public bug reported:
The rocm-hipamd package has been FTBFS on arm64 in noble since the
update to glibc 2.38 last year, as per
https://bugs.launchpad.net/ubuntu/+source/rocm-hipamd/+bug/2032624. In
fact, all libraries written in the HIP language have been FTBFS on arm64
since then. This is blockin
I had to fight a bit to figure out how to build ucx due to the
"debian.upstream" directory, but I've completed an arm64 build. I can
confirm that when autoconf fails to find libamdhip64-dev, it will just
disable ROCm support.
I must admit, I didn't restart my arm64 build after fixing the
maintaine
I realized that I should update the maintainer in d/control when
creating an ubuntu revision, so I deleted the original patch and have
reattached it with that change included.
** Patch removed: "rm-rocm-arm64-2060999.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ucx/+bug/2060999/+attachme
I've attached a debdiff for a new version including the necessary
package changes.
** Patch added: "rm-rocm-arm64-2060999.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ucx/+bug/2060999/+attachment/5763926/+files/rm-rocm-arm64-2060999.debdiff
--
You received this bug notification because
** Merge proposal linked:
https://code.launchpad.net/~slavik81/ubuntu/+source/ucx/+git/ucx/+merge/464136
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060999
Title:
Please drop libamdhip64-5 fr
** Description changed:
rocm-hipamd FTBFS on arm64 in noble due to
https://bugs.launchpad.net/ubuntu/+source/mumax3/+bug/2032624. It seems
- unlikely that a fix for glibc can be merged for noble. I will be
+ unlikely that a fix for glibc can be merged in time for noble. I will be
requesting
Public bug reported:
rocm-hipamd FTBFS on arm64 in noble due to
https://bugs.launchpad.net/ubuntu/+source/mumax3/+bug/2032624. It seems
unlikely that a fix for glibc can be merged for noble. I will be
requesting that the arm64 binaries for rocm-hipamd be removed from the
archive so that fixes for
All HIP language libraries have been FTBFS on arm64 since the vector
types were added, so this issue has been blocking the libraries from
syncing for several months. The only ones that have been able to update
have been the ones that had always been broken on arm64 for other
reasons.
I've opened a
** Merge proposal linked:
https://code.launchpad.net/~slavik81/ubuntu/+source/glibc/+git/glibc/+merge/464058
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2032624
Title:
mumax3 test suite fails
** Patch added: "rocthrust-changelog.diff"
https://bugs.launchpad.net/ubuntu/+source/rocthrust/+bug/2060585/+attachment/5762300/+files/rocthrust-changelog.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
** Attachment added: "rocthrust-5.7.1-2-install.txt"
https://bugs.launchpad.net/ubuntu/+source/rocthrust/+bug/2060585/+attachment/5762299/+files/rocthrust-5.7.1-2-install.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
# d/changelog since 5.3.3-4
rocthrust (5.7.1-2) unstable; urgency=medium
* Migrate to unstable
* d/rules: use rocprim arch conversion to ensure that the rocthrust tests
behave the same on all RDNA 2 hardware
-- Cordell Bloor Tue, 26 Mar 2024 11:40:24 -0600
rocthrust (5.7.1-2~exp1) ex
Public bug reported:
Please sync rocthrust 5.7.1-2 (universe) from Debian unstable (main)
This sync requires a FeatureFreeze exception. This package version
requires rocm-hipamd 5.7.1 and would benefit from rocprim 5.7.1, which
are being tracked in https://bugs.launchpad.net/ubuntu/+source/rocm-
# d/changelog since 5.5.1-1
rocprim (5.7.1-2) unstable; urgency=medium
* Migrate to unstable
* Add d/p/test-warp-sort-ppc64el.patch to drop test_warp_sort from
librocprim-tests on ppc64el due to FTBFS when compiling with clang-17.
This is a workaround for bug #1065206
* Add d/p/verb
** Patch added: "changelog.diff"
https://bugs.launchpad.net/ubuntu/+source/rocprim/+bug/2060565/+attachment/5762210/+files/changelog.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060565
Titl
** Attachment added: "rocprim-5.7.1-2-install.txt"
https://bugs.launchpad.net/ubuntu/+source/rocprim/+bug/2060565/+attachment/5762209/+files/rocprim-5.7.1-2-install.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
Public bug reported:
Please sync rocprim 5.7.1-2 (universe) from Debian unstable (main)
This sync requires a FeatureFreeze exception. This package version
requires rocm-hipamd 5.7.1, which is being tracked in
https://bugs.launchpad.net/ubuntu/+source/rocm-hipamd/+bug/2058606.
# Why a new upstrea
** Patch added: "changelog.diff"
https://bugs.launchpad.net/ubuntu/+source/rocrand/+bug/2060424/+attachment/5762044/+files/changelog.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060424
Titl
# d/changelog since 5.3.3-6
rocrand (5.7.1-4) unstable; urgency=medium
* d/rules: use CMAKE_SKIP_INSTALL_RPATH to enable rpath in build tests
-- Cordell Bloor Sun, 07 Apr 2024 20:59:16 -0600
rocrand (5.7.1-3) unstable; urgency=medium
* Add d/p/0005-rocrand-public-hip-host.patch to fix r
Public bug reported:
Please sync rocrand 5.7.1-4 (universe) from Debian unstable (main)
This sync requires a FeatureFreeze exception. This package version
requires rocm-hipamd 5.7.1, which is being tracked in
https://bugs.launchpad.net/ubuntu/+source/rocm-hipamd/+bug/2058606.
# Why a new upstrea
** Attachment added: "rocrand-5.7.1-4-install.txt"
https://bugs.launchpad.net/ubuntu/+source/rocrand/+bug/2060424/+attachment/5762043/+files/rocrand-5.7.1-4-install.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
For comparison, I've uploaded a test log of the rdepends using rocm-
hipamd 5.2.3-12 on the same system. Note that is that the two failures
are identical to the previous log for the rdepends using the rocm-hipamd
5.7.1-3 package.
** Attachment added: "test log for rdepends with rocm-hipamd 5.2.3-1
** Description changed:
Please sync rocm-hipamd 5.7.1-3 (universe) from Debian unstable (main)
This sync requires a FeatureFreeze exception
# Why a new upstream version is necessary
The Ubuntu Noble FeatureFreeze occurred while the ROCm stack on Debian
was transitioning from ROC
The rdepends for rocm-hipamd are nearly all FTBFS due to the addition of
'cf-protection=return' and 'cf-protection=branch' to the CXXFLAGS. This
is not a problem introduced by rocm-hipamd 5.7.1, but occurs with the
current rocm-hipamd 5.2.3 as well. As such, this update has no effect on
whether the
I've pushed the change to salsa, so future versions of rocr-runtime will
be restricted to 64-bit architectures [1]. However, I'm not sure it's
worth uploading a new version of the package just for that. I'll wait
and see for a couple weeks if there are any more bugs reported before
making another u
Note that no version of rocr-runtime has ever built successfully for
armhf. rocr-runtime should probably be limited to amd64, arm64 and
ppc64el (as those are the only architectures that have driver support
from AMDGPU KFD).
I've been cautious about dropping architectures that successfully built
be
It's perhaps worth noting that every version of rocr-runtime has failed
to build on armhf. The failure was not introduced by this update.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058594
Title:
** Attachment added: "test log (run prebuilt rocrand tests; build rocprim and
run tests)"
https://bugs.launchpad.net/ubuntu/+source/rocm-hipamd/+bug/2058606/+attachment/5757790/+files/noble_rocm-hipamd_5.7.1-2_tests.log
--
You received this bug notification because you are a member of Ubuntu
** Attachment added: "install log"
https://bugs.launchpad.net/ubuntu/+source/rocm-hipamd/+bug/2058606/+attachment/5757740/+files/noble_rocm-hipamd_5.7.1-2_install.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
** Attachment added: "build log"
https://bugs.launchpad.net/ubuntu/+source/rocm-hipamd/+bug/2058606/+attachment/5757739/+files/noble_rocm-hipamd_5.7.1-2_build.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
Public bug reported:
Please sync rocm-hipamd 5.7.1-2 (universe) from Debian unstable (main)
This sync requires a FeatureFreeze exception
# Why a new upstream version is necessary
The Ubuntu Noble FeatureFreeze occurred while the ROCm stack on Debian
was transitioning from ROCm 5.2 with clang-15
Public bug reported:
Please sync rocr-runtime 5.7.1-2 (universe) from Debian unstable (main)
The 5.7.1-2 version of the package should allow rccl to build
successfully on arm64 and ppc64el. It should also fix HIP on Rembrandt
APUs (gfx1035), which was completely broken in 5.7.1-1 (as illustrated
Public bug reported:
We expect that each line sent to stdout/stderr from a program running
within a podman container will be captured as a single journald entry.
Instead, conmon is sometimes splitting individual application log lines
into many journald entries. This can make journald log entries f
Power cable unplug also did the trick for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1859592
Title:
Bluetooth unavailable after updates - Reading Intel version
information failed (-110)
To
Public bug reported:
After a reboot in Kubuntu 21.04 (and 20.10) the IBus Panel icon appears
in the system tray despite "Show icon on system tray" NOT being checked.
Right clicking on the IBus Panel icon, checking "Show icon on system
tray" and then unchecking again it causes the icon to be correc
/usr is a separate ZFS file system, separate from /. My system boots
and operates normally. The only issue is with the grub script,
/etc/grub.d/10_linux_zfs. I had to do some hacking of this script for
it to parse the Linux images properly.
If you think /usr is not supported as a separate ZFS f
Public bug reported:
Description:Ubuntu 20.04.1 LTS
Release:20.04
grub-common: 2.04-1ubuntu26.4
I expect grub-update to create grub.cfg with Linux entries for ZFS.
Instead I am left with an empty list and an unbootable OS.
The output from update-grub:
Sourcing file `/etc/default/grub
Public bug reported:
First time log in after update to 20.04 (from 18.04) and gui pops up
with this failure.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-42-generic 5.4.0-42.46
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86
I see this on Ubuntu 19.04 with Gnome & Wayland
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1295267
Title:
Windows change Monitor/Desktop after screen lock
To manage notifications about this bug
*** This bug is a duplicate of bug 1838711 ***
https://bugs.launchpad.net/bugs/1838711
Public bug reported:
package sendmail-bin 8.15.2-13 failed to install/upgrade: installed
sendmail-bin package post-installation script subprocess returned error
exit status 2
ProblemType: Package
DistroRel
Public bug reported:
Installer crashed with an Input/Output error. Trying to install from a
memarex 8gig flash drive
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: ubiquity 19.04.9
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
ApportVersion: 2.
$ diff -r /boot/efi/EFI/lubuntu/ /boot/efi/EFI/ubuntu/
$
** Summary changed:
- lubuntu grub-install puts efi in the wrong directory
+ lubuntu grub-install puts efi in the wrong directory - could make an
unbootable state
** Summary changed:
- lubuntu grub-install puts efi in the wrong directo
Public bug reported:
Lubuntu 19.04
grub-install from grub2-common 2.02+dfsg1-12ubuntu2
Summary:
The lubuntu installer puts the EFI in EFI/ubuntu. The firmware appears
to be hard coded to this path. Lubuntu grub-install puts the EFI in
EFI/lubuntu only, and NOT in EFI/ubuntu, which can result in
At least on Ubuntu 18.04, I found that the version from the apt package
starts up much faster than the snap version. I ended up swapping them
using `sudo snap remove gnome-calculator && sudo apt install gnome-
calculator`
--
You received this bug notification because you are a member of Ubuntu
Bu
Public bug reported:
I was trying to correct the tool icons being to small by adjusting the
theme icon settings when GIMP crashed. I have two 4K monitors (one
horizontal and one landscape) and run KDE. I had just selected "Custom
Icon Size" from the pulldown. Something is a little off in those
With friendly-recovery version 0.2.38ubuntu1, selecting the check
filesystems option results in an error message like:
/etc/default/rcS: file or directory not found
This file does not exist on my system. I don't know if the problem I'm
reporting is related to this issue, but it does seem to be t
Public bug reported:
Recently (starting around 22-10-2018) started having issues with
suspend, in that it seems to either inconsistently enter suspend state
or come out of suspend state too frequently, such that it ends up
draining the battery very quickly when left alone.
I'm very inexperienced
Got this on a new X1 Carbon with a fresh Bionic install after it failed
to wake from sleep the first time (black screen) but then after closing
the laptop and waiting a few minutes, it recovered and I had this error.
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
Public bug reported:
my wireless connection cut out at the final stage in the installation
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Archite
For the record, I think the lxd.migrate requires that the deb packages
still be installed (it's a transition step for the case where you were
previously actively using the deb packaged lxd and want to move to the
snap, so it has to be run after the snap install but prior to the deb
removal). Hence
There was some confusion on Adam's part. The migrate step is only
required if switching from the apt packaged lxd to the snap, which isn't
required on bionic (but was on older releases).
>From my own testing, the only way I could replicate this on a fresh
bionic VM was to accept the default for I
Oh, I forgot to mention that when Adam and I were discussing what was
going on with this issue, he also pointed out that several people have
had issues with CDK and ZFS recently (e.g., https://github.com/conjure-
up/conjure-up/issues/1430) which are being still investigated, so even
if you get past
Public bug reported:
A couple hours ago, Firefox crashed on me for seemingly no reason. A
flashplugin-installer error dialog popped up, which I dismissed without
reading. I'd seen a similar dialog that said "flashplugin-installer
failure to download extra data files" a few times before and had bee
This bug has persisted through three LTS releases (12.04, 14.04, 16.04)
and had bitten me on each one.
Are there plans to fix this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1269921
Title:
netw
Public bug reported:
I have never been able to update this driver.
ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: nvidia-opencl-icd-340 340.96-0ubuntu3.16.04.1
ProcVersionSignature: Ubuntu 4.8.0-36.38-generic 4.8.16
Uname: Linux 4.8.0-36-generic x86_64
NonfreeKernelModules: wl
.tmp.uni
I see that this was assigned to somebody back in May, but the packaging
bug still exists.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1550950
Title:
package openjdk-9-jdk 9~b102-1 failed to instal
This appears to have been fixed at some point. I can no longer
reproduce.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1589753
Title:
Layout breaks after doing things in other tabs
To manage notif
Add me to the list for whom this is annoying. ImageMagick switch from
libjasper to libopenjp2 two years ago, and the Debian upstream packages
was fixed a year ago, so why is this not fixed on Ubuntu yet?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
Sure. I would add this block to the top of the nginx default site file:
server {
listen 443 ssl deferred;
root /usr/share/nginx/html;
index index.html index.htm;
# Make site accessible from http://localhost/
server_name localhost;
location / {
I just investigated on Xenial, and this problem appears not to exist
there. The behaviour is the same (SYN+ACK retransmission after
TCP_DEFER_ACCEPT timeout), but this time nginx correctly continues the
connection. So it seems that this was fixed somewhere between trusty and
xenial.
For the fixed
I have located the bug fix: http://hg.nginx.org/nginx/rev/5b549cc7f698.
Such a fix would be extremely easy to backport if there is interest in
doing so. Otherwise, the fix landed in 1.7.11, so any version later than
that is safe.
--
You received this bug notification because you are a member of U
Public bug reported:
Summary:
When nginx has a server that is configured in the 'deferred' listen mode
and it takes the client more than approx. 1 second to send data, nginx
will hang and eventually time the connection out.
Tested Versions:
lsb_release -rd:
Description:Ubuntu 14.0
Scratch that. Still a bug. This problem only occurs if you have zoomed
in a few notches, but it happens regardless of whether the zooming in
was done by an add-on or done through View -> Zoom -> Zoom In.
The trigger for this seems to specifically be the inspector. I don't see
the problem when open
Opps. This appears to be a bug in the NoSquint add-on. I see that
NoSquint is no longer maintained as of April. So, that's that. :(
I guess this bug can be closed.
** Changed in: firefox (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubu
** Attachment added: "the fixed layout after moving the tab into a new window"
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1589753/+attachment/4678513/+files/fixed.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
Public bug reported:
I'm pretty sure this wasn't happening a couple months ago, so this seems
to be a recently introduced.
Steps to Reproduce:
1. Visit https://mmistakes.github.io/hpstr-jekyll-theme/
2. Click 3-lined Menu icon.
3. Click 'About'.
4. Right-click the author image and open the inspe
ntu 3.13.0-32.57-generic 3.13.11.4
> Uname: Linux 3.13.0-32-generic x86_64
> ApportVersion: 2.14.1-0ubuntu3.2
> Architecture: amd64
> AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC0: cory 1767 F pulseaudio
> Date: Mon May 23 17:51:0
neric 3.13.11.4
Uname: Linux 3.13.0-32-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: cory 1767 F pulseaudio
Date: Mon May 23 17:51:05 2016
DuplicateSignature: package:linux-image-3.13.0-86-generic
1 - 100 of 522 matches
Mail list logo
