Hello Juerg,
Em quinta-feira, 20 de janeiro de 2022, às 12:32:48 -03, Juerg Haefliger
escreveu:
> If you want this fixed in Ubuntu I need to know what series are
> affected. Hirsute goes EOL at the end of the month. Are Impish and/or
> Jammy working or affected as well?
I upgraded to Impish a
Hello,
I’d just like to report that I haven’t seen this problem in a while. The
last time I see the “retry page fault” messages in my log was on August 9.
I’ve been using the ‘amdgpu/picasso*‘ files from linux-firmware commit
c46b8c364b82 (“ice: update package file to 1.3.26.0”) so apparently
Hello,
For some reason, in the past week or so this bug has been freezing my
machine every couple of days or so (I’m surprised that AMD wasn’t able
to reproduce the problem yet¹). You can imagine how “pleasant” it makes
using this computer.
Today I got an interesting error in dmesg, perhaps
Em segunda-feira, 12 de julho de 2021, às 15:12:19 -03, Alex Deucher
escreveu:
> Does the latest firmware in the firmware git tree help?
> https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.g
> it/log/amdgpu
I updated the picasso* files from commit:
d79c26779d45 amdgpu:
Em quinta-feira, 17 de junho de 2021, às 10:07:39 -03, Christian Ehrhardt
escreveu:
> The dependencies already are (and would stay)
> iptables (>= 1.8.1-1) | firewalld
> from Package: libvirt-daemon-system.
> This is very much the same in Debian where we have kept it enabled.
> Therefore I
Em quinta-feira, 17 de junho de 2021, às 00:45:30 -03, Thiago Jung
Bauermann escreveu:
> > > I think it may be related to a change in mesa. Specifically mesa
> > > commit
> > > 820dec3f7c7. For more info see
> > > https://gitlab.freedesktop.org/mesa/
I was finally able to spend a bit of time on this. Unfortunately, there’s
not much to report back.
Em terça-feira, 8 de junho de 2021, às 15:13:36 -03, Thiago Jung Bauermann
escreveu:
> Em terça-feira, 8 de junho de 2021, às 10:30:24 -03, Alex Deucher
escreveu:
> > Can you narrow d
** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #1598
https://gitlab.freedesktop.org/drm/amd/-/issues/1598
** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #920
https://gitlab.freedesktop.org/drm/amd/-/issues/920
--
You received this bug notification because you are
Thanks for your input.
Em terça-feira, 8 de junho de 2021, às 10:30:24 -03, Alex Deucher escreveu:
> Can you narrow down which specific firmware file causes the problem?
Ok, I will try.
Also, is it possible and/or worthwhile trying to bisect firmware versions from
the linux-firmware repo? How
Em quarta-feira, 26 de maio de 2021, às 16:46:14 -03, Thiago Jung Bauermann
escreveu:
> But perhaps the upstream version is not too bad?
I take this back. I've been running with the upstream picasso* files since
Wednesday, and I just had two freezes in less than one hour.
linux-firmw
Over the weekend I was finally able to revert back to the previous versions
of the org.freedesktop.Platform and org.freedesktop.Platform.GL.default
flatpak runtimes. It turns out that the `flatpak history` command wasn't
necessay for the rollback.
Em sexta-feira, 14 de maio de 2021, às
Em sábado, 15 de maio de 2021, às 11:24:17 -03, Thiago Jung Bauermann
escreveu:
> Unexpectedly, 1.197 is now reliable too! I have been running it for about
> half a day (which is more than what was possible before) and it is fine.
After 4 days of stability I just had the retry page fault p
The latest upstream firmware is stable, so I reverted back to 1.197 so that
I could test only the picasso* files.
Before doing that, I decided to run for a while with pristine linux-
firmware 1.197 to double-check that the bug happens quickly.
Unexpectedly, 1.197 is now reliable too! I have
Hello Seth,
Thank you for the quick and detailed response.
Em sexta-feira, 14 de maio de 2021, às 13:14:22 -03, Seth Forshee escreveu:
> Before we revert we should see if newer firmware fixes the issue, and
> make sure we are only changing the specific firmware files for your
> hardware.
Ok,
This is the dmesg of an instance where I was able to continue using the
laptop despite the GPU bug (in the case of the dmesg I attached
previously, I had to ssh in to the machine to turn it off).
Notice that there are two instances of the retry page fault, one of them
right within 15 minutes of
Public bug reported:
After upgrading linux-firmware from 1.190.5 to 1.197 (as part of the
upgrade from Ubuntu 20.10 to 21.04), I started experiencing frequent and
severe GPU instability. When this happens, I see this error in dmesg:
[20061.061069] amdgpu :03:00.0: amdgpu: [gfxhub0] retry
Hello Christian,
Thank you for your quick and thorough response!
Em quarta-feira, 12 de maio de 2021 08:12:17 -03 você escreveu:
> Hi Thiago,
> the problem is that firewalld isn't in main and thereby not fully
> supported which means that libvirt (that is in main) can not depend on
> it - see
More information I should have mentioned earlier:
The impact of this bug is that libvirt can't start the default network:
bauermann@popigai:~$ virsh -c qemu:///system net-start default
error: Failed to start network default
error: internal error: firewalld is set to use the nftables backend, but
Public bug reported:
I use the firewalld package to manage my firewall configuration. I just
installed the libvirt-daemon set of packages (see below) and libvirtd
registers this error in the journal:
libvirtd[1063]: internal error: firewalld is set to use the nftables
backend, but the required
FYI: I just had Choqok crash on me with a backtrace nearly identical to
the one in this bug report, using Qt 4.8.5, therefore with the fix for
this bug. My situation doesn't involve alt+tab so it may indeed be
something different. I opened this Qt bug report:
I have the same problem on Ubuntu 12.04.3 LTS on i386. I have plenty of
space both in /tmp and /var/tmp (they're on the same partition):
hactar% LANG= df -h /tmp /var/tmp
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/hactar--vg-root 120G 107G 7.1G 94% /
Thanks for the quick response!
After running update-guestfs-appliance the error message changed, so I
was probably hitting a bug that was fixed already.
Now the failure is:
hactar% LANG= libguestfs-test-tool
= Test starts here =
LIBGUESTFS_DEBUG=1
TMPDIR=(not set)
libguestfs: new
I still get the following warning though:
warning: Unable to get device geometry for /var/tmp/guestfs.BxDbcl/root
It appears to be harmless. I can still use guestfish to access disk
images.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Public bug reported:
In Ubuntu 12.04.3 LTS on i386 update-guestfs-appliance fails with the
following error message:
E: No downloadable files for libgnutls26 version 2.12.20-2ubuntu1;
perhaps it is a local or obsolete package?
I tried to run this command in an attempt to fix bug #1186228. That
I have the same problem on Ubuntu 12.04.3 LTS on i386. I have plenty of
space both in /tmp and /var/tmp (they're on the same partition):
hactar% LANG= df -h /tmp /var/tmp
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/hactar--vg-root 120G 107G 7.1G 94% /
Sorry, this bug is invalid. I forgot that I had manually upgraded
libgnutls26 so that I could install a newer version of git-annex. I
downgraded to 12.04's repository version of the package and update-
guestfs-appliance is working now.
I was pretty sure that I checked libgnutls26's version before
Thanks for the quick response!
After running update-guestfs-appliance the error message changed, so I
was probably hitting a bug that was fixed already.
Now the failure is:
hactar% LANG= libguestfs-test-tool
= Test starts here =
LIBGUESTFS_DEBUG=1
TMPDIR=(not set)
libguestfs: new
I still get the following warning though:
warning: Unable to get device geometry for /var/tmp/guestfs.BxDbcl/root
It appears to be harmless. I can still use guestfish to access disk
images.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
Current Android cellphones can only be accessed via MTP, which is not
supported at all in 12.04. This leads to user frustration when a very
common and simple usecase (plug phone in computer, access it) simply
doesn't work at all. It should just work.
I would consider adding
I finished reviewing the patch. It looks great to me. Also the gcore-
relro.exp testcase which exercises the patch passes, and there are no
regressions on i686 nor x86_64.
Thanks for working on it, Steve!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I was able to reproduce this bug.
It was fixed in GDB 7.4, so you can install Precise's gdb package to fix
the bug.
Precise's release is not far away so I'll see whether a new package with
this fix for Oneiric is feasible.
** Changed in: gdb-linaro
Status: New = Triaged
** Project
I'm reviewing this patch.
I ran the GDB testsuite with it and there are no regressions on
i686-linux.
Tomorrow I'll test it on x86_64 and finish my review of the code.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Evolution also fails to load the GTK Oxygen theme with the same error
message. I created a gtk2-engines-oxygen package with the patch from KDE
bug#263182 applied and Evolution now works correctly with the Oxygen
theme.
Here's the upstream commit which I used:
33 matches
Mail list logo
