[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]
** Changed in: pulseaudio (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
Actually this bug may be invalid.
'gnome-shell' already recommends package 'gnome-remote-desktop'. If a
minimal install omits recommended packages then it won't get installed.
All of this seems quite reasonable to me.
** Changed in: gnome-shell (Ubuntu)
Status: New => Opinion
** Changed
Thanks for the information. I can confirm your system crashed because of
the nouveau kernel driver. It's not a very stable driver and does cause
a lot of bugs so I would always recommend installing the Nvidia driver
instead.
Nov 11 16:15:52 lenovo /usr/libexec/gdm-x-session[2605]: (WW)
Public bug reported:
I'm using Ubuntu 20.04 (all upgrades)
I was using MATE until I decided to go back to budgie since MATE started
hogging system resources.
after removing MATE and trying to login with budgie I only get a gray screen.
I reinstalled lightdm, budgie desktop, nvidia drivers, etc.
Public bug reported:
Everything is described here:
https://askubuntu.com/questions/1369790/hdmi-audio-device-not-found-anywhere-please-help
** Affects: alsa-driver (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- HDMI audio output nowehere to be found
+ HDMI audio
@xnox Could you finish the verification and tag the bug verification-
done?
" * Configure and use openssl with any engine and ensure that it
continues to work"
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in
Unfortunately, I have no idea on how to bisect this, due to the fact
that there is not an independent repo for systemd-resolved and
attempting to work on the whole systemd seems to dounting and risky as
an experience for me. Is there a ppa with a more recent systemd-
resolved to try on focal
Loading the configuration only once will resolve this issue, and is the
recommended code fix.
On top of this bug fix, and as mentioned above, we recommend that future
versions will incorporate an API change that will shift the ownership on
releasing the pointers to the engine that allocated them
Tested on a manjaro system that being rolling uses the latest systemd.
There is no issue there.
Hence the problem appears to be a systemd-resolved bug specific to the
systemd version shipped with ubuntu 20.04.
Because the issue breaks local resolution via mDNS in some
configurations, I think
The audio jack would appear to be a factor in the issue.
I plugged the speakers into my laptop. The bug didn't trigger.
With the speakers unplugged from the affected system, and bluetooth headphones
connected, the bug also didn't trigger.
Should I continue posting here, or move to the Mozilla
This issue is spamming the log with messages
Failed to get Yr.no forecast data: 404 Not Found
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libgweather in Ubuntu.
https://bugs.launchpad.net/bugs/1918044
Title:
(Update
So my understanding from #34 and #35 is that this is an upstream OpenSSL
issue, that should be discussed with the OpenSSL people.
The feedback in #34 suggests that this problem can be solved by not
parsing the configuration file twice, I have not investigated that as of
yet.
The feedback in #35
Yes, the problem occurs with the upstream build as well. I have
commented there, adding that my speakers are plugged into an audio jack
(though I'm not yet convinced that's at the root of the problem)
The XPS is running 20.04 as well.
--
You received this bug notification because you are a
Hi Olivier,
Once the problem is triggered, it survives a reboot, and even switching
operating systems (to Manjaro). I have to physically plug the microphone
into a different USB port to fix it.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
** Also affects: speech-dispatcher (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- Firefox sometimes causes garbled audio
+ Firefox sometimes causes garbled audio, caused by speech dispatcher
--
You received this bug notification because you are a member of Ubuntu
Thanks for the report Benjamin. This sounds similar to
https://bugzilla.mozilla.org/show_bug.cgi?id=1719968. Could you test on
the affected machine with an upstream build (as downloaded from
https://www.mozilla.org/en/firefox/download/thanks/), and let us know
whether you're observing the same
Thanks for the report Benjamin. Just so that I understand correctly,
even after killing and restarting pulseaudio, the microphone won't
register sound until the machine is rebooted?
** Changed in: firefox (Ubuntu)
Status: New => Incomplete
** Also affects: pulseaudio (Ubuntu)
Might be related to https://github.com/systemd/systemd/issues/11342
** Bug watch added: github.com/systemd/systemd/issues #11342
https://github.com/systemd/systemd/issues/11342
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
An update to the comment above. We have found out a sequence of commands
that seems to reproduce the issue reliably: in the spread session
started by the command from the comment above, if you type this:
systemctl stop 'snap-disabled\x2dsvcs\x2dkept-x1.mount'
systemctl daemon-reload
There is now only a transient ADT regression in Regression in linux-
hwe-5.13 (armhf), which is not a valid ADT because armhf ADT runs in lxd
containers and does not boot the requested kernel.
Please release this package.
--
You received this bug notification because you are a member of Ubuntu
Hi Daniel,
In my understanding, the crash is not reproducible after my workaround
(switching to the nvidia driver), because the nvidia-resume.service is not
masked (my theory).
Therefore, I switched back to the Nouveau driver, and I reproduced the
problem and collected the system logs as you
> can you provide steps on how this is reproducable then?
So far we have not been able to isolate the problem, so the only way so
far is to run the spread tests from the snapd directory (from the master
branch):
spread -debug -repeat 20 google:ubuntu-
add-apt-repository also silently deletes the [trusted=yes] option, which
is appropriate but undocumented. There needs to be clearer documentation
on what options work and what doesn't. Hopefully all options are
supported.
--
You received this bug notification because you are a member of Ubuntu
For me this seems to be fixed under Kubuntu 21.10 with Gwenview 21.08.2
from kubuntu-backports-ppa.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to exiv2 in Ubuntu.
https://bugs.launchpad.net/bugs/1941752
Title:
Created attachment 143424
New crash information added by DrKonqi
gwenview (20.12.3) using Qt 5.15.2
- What I was doing when the application crashed:
This is a little bizarre. I encountered this while rapidly scrolling
through thumbnails in a directory. One particular image reliably crashes
25 matches
Mail list logo
