Having this problem on my newly installed Ubuntu 20.04 system. Tried using the
11n_disable=1
workaround, didn't work.
modinfo output:
$ modinfo iwlwifi | grep 9260
firmware: iwlwifi-9260-th-b0-jf-b0-46.ucode
Turning networking off and back on resets the issue, but after about
half a
Public bug reported:
I'm using Ubuntu 19.10 installed yesterday...
** Affects: pulseaudio (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for exim4 (Ubuntu) because there has been no activity for 60
days.]
** Changed in: exim4 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/832030
[Expired for alsa-driver (Ubuntu) because there has been no activity for
60 days.]
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for gnome-shell-extension-appindicator (Ubuntu) because there
has been no activity for 60 days.]
** Changed in: gnome-shell-extension-appindicator (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
[Expired for gnome-shell-extension-appindicator (Ubuntu) because there
has been no activity for 60 days.]
** Changed in: gnome-shell-extension-appindicator (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
[Expired for hplip (Ubuntu) because there has been no activity for 60
days.]
** Changed in: hplip (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871011
[Expired for ubiquity (Ubuntu) because there has been no activity for 60
days.]
** Changed in: ubiquity (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for grub-installer (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: grub-installer (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for upower (Ubuntu) because there has been no activity for 60
days.]
** Changed in: upower (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872917
[Expired for network-manager (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: network-manager (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for grub-installer (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: grub-installer (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for gtk+2.0 (Ubuntu) because there has been no activity for 60
days.]
** Changed in: gtk+2.0 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1871794 ***
https://bugs.launchpad.net/bugs/1871794
Maybe different machines have different root cause for this issue, for
my case:
I have 3 laptops: 1 dell laptop with intel BT 8087:0aaa, 1 dell laptop
with Atheros BT 0cf3:e007 and 1 lenovo laptop with
Hi all, I'm using ubuntu 20.04 on a raspberry pi (64bit version). And
the problem is still present. My netplan:
root@rbpi3-002:/etc/netplan# cat /etc/resolv.conf
# This file is managed by man:systemd-resolved(8). Do not edit.
#
# This is a dynamic resolv.conf file for connecting local clients
So in my case, my VM was configured with only 256MB of memory. This
caused no problem on the normal -virtual kernel but caused all sorts of
problems when I installed -lowlatency in the guest.
Upgrading to 384MB solved the problem reliably here, so perhaps this is
not the same thing afterall.
-
Public bug reported:
installation/ unninstalation
ProblemType: Package
DistroRelease: Ubuntu 19.10
Package: mutter 3.34.3-1ubuntu1~19.10.1
ProcVersionSignature: Ubuntu 5.3.0-59.53-generic 5.3.18
Uname: Linux 5.3.0-59-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.9
AptOrdering:
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884405
Title:
package mutter 3.34.3-1ubuntu1~19.10.1 failed to install/upgrade:
package is in a very bad
Public bug reported:
startx don't came up
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: nvidia-340 (not installed)
ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
Uname: Linux 5.4.0-37-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27
Kernel version 5.4.0-37-lowlatency, btw
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872964
Title:
Reliable crash in lowlatency kernel with LXD
To manage notifications about this bug go to:
I have an LXD Virtual Machine refusing to boot after installing the
-lowlatency kernel on it. Sounds like these _might_ be related, so
here's my info. I'm on a NUC too, btw.
Host: Ubuntu 20.04 LTS, LXD 4.2 snap (running -lowlatency)
Guest: Ubuntu 20.04 LTS
The guest was running without problems
Same as jacj and Edwin. With 440.64 Nvidia driver with Ubuntu 20.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1846374
Title:
Having a video playing/paused when switched to another user
** Description changed:
- exFAT is, to my knowledge, the only file format supporting files greater
- than 4GB which can be read, written, and formatted with the standard GUI
- tools of both Windows and macOS. Though not a free standard, it is
- otherwise ideal for external storage such as USB
** Changed in: fwupd (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: fwupd-signed (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Can you please file a bug report upstream with this one?
https://github.com/fwupd/fwupd
When filing upstream fill out everything in the template.
** Changed in: fwupd (Ubuntu)
Status: New => Triaged
** Changed in: fwupd (Ubuntu)
Importance: Undecided => Wishlist
--
You received this
Did that already, got rid of the problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884101
Title:
jackdbus produces high cpu load
To manage notifications about this bug go to:
Try the following in Ubuntu LTS 20.04, to clear things out.
1. Create a new gnome user and log in.
2. Build Rhythmbox 3.4.3 from source. This should take 15 mins + 200 MB
disk space
$ sudo apt-get build-dep rhythmbox
$ sudo apt-get install git
$ git clone
Public bug reported:
I was trying to fix my crakling, static-filled audio by running some
pulseaudio commands in the console. The sound settings gui was open, and
I think this error appeared when I tried to open a dropdown
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: shim-signed
Correction: Applying following patch does not solve this assertion
failure:
diff --git a/src/engine-eds.cpp b/src/engine-eds.cpp
index 153a9ea..8e2674f 100644
--- a/src/engine-eds.cpp
+++ b/src/engine-eds.cpp
@@ -879,6 +879,11 @@ private:
if (tzid == nullptr)
return nullptr;
The KDE_HOME_READONLY workaround stopped working and failure behavior
changed last week after I applied updates to kubuntu 20.04.
Instead of a logout as previously experienced, NFS home now results in a
black screen with a mouse pointer.
See attached apt history.log and .xsession-errors for more
Created attachment 129548
apt history.log
apt history log showing updates that correspond to timing of
KDE_HOME_READONLY workaround no longer working.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Created attachment 129549
.xsession-errors
.xsession-errors file for new black screen behavior after recent
updates. Note that the read-only home directory error is no longer
displayed, so not sure how this relates to previous behavior.
--
You received this bug notification because you are a
The underlying issue is that
i_cal_timezone_get_builtin_timezone_from_tzid and
i_cal_timezone_get_builtin_timezone included from /usr/include/libical-
glib/i-cal-timezone.h (libical-dev) fail to determine the timezone for
"Etc/Utc" or "Etc/UTC".
** Also affects: libical3 (Ubuntu)
Importance:
*** This bug is a duplicate of bug 1871794 ***
https://bugs.launchpad.net/bugs/1871794
Finally, i have the same problem on Vivobook S15 and Headset QC35 II that
worked perfectly before upgrade to 20.04.
It's very annoying issue in this period of containment and remote calls.
Don't push me
*** This bug is a duplicate of bug 1871794 ***
https://bugs.launchpad.net/bugs/1871794
Finally , i h
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878194
Title:
[Sennheiser HD 4.50 BTNC]
This thread takes several months without solution for Ubuntu 18.04 users.
I recently requested a backport to be able to update Stunnel to its latest
version.
Stunnel crash continuously and I think the update would help fix this problem.
Please Bionic Backports I request to give priority to my
Public bug reported:
I had similar issues when 20.04 was released, then it disappeared with
an upgrade - but sadly it's back. I have short intermittent freezings of
the OS. About every 15-30 seconds Ubunut freezes for a second or two. Eg
when writing this description, the OS freezes every second
*** This bug is a duplicate of bug 1871794 ***
https://bugs.launchpad.net/bugs/1871794
I had the same issue with my BOSE QC35 II on Ubuntu 20.04 recently updated from
19 .
My config: Asus VivoBook S15 .
To correct this issue i only had to enable this line in /etc/pulse/daemon.conf
On Thu, Jun 18, 2020 at 8:30 AM Dimitri John Ledkov <
1863...@bugs.launchpad.net> wrote:
> Can someone please provide clear reproducer instructions?
>
> Ideally starting with a clean state (i.e. no installs / brand install)
> with affected hardware details (model, firmware version numbers, SKU
>
Public bug reported:
As of 5 days ago (6/15/20) and after several recent Mint 19.3 software
updates, GIMP 2.10.20 started crashing. I can open GIMP OK and even open
an image file. But as soon as I use the mouse, even to click on the
opened image, or click a menu item, GIMP crashes and I end up at
I think you should bring this discussion upstream.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884387
Title:
fwupdmgr file read error on RTL810xE PCI Express Fast Ethernet
controller
To
It's been years. This is still annoying. May as well download my
applications from websites like a Windows user if package management is
going to be this dirty on Linux.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Gnome Settings>Appearance> auto hide dock //enable it
automatically you might see icons getting hidden behind dock (keep
windows away from dock).
Not only desktop getting hidden under dock looks unaesthetic,
But don't you think dock should remain hidden till the user points
Over time and several reboots later, the issue has reappeared, so the
workaround above is definitely not a permanent solution.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1787867
Title:
Ubuntu
Okay, thanks for the info. Should there be a less-alarming message ?
Something like "this device does not support the verify operation" ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884387
Title:
Here's what I've tried (that I can remember):
- Reinstalling all the ALSA packages
- Rebooting, turning off the sound devices in the BIOS, letting it boot, then
reboot, turn the sound devices back on, and let it boot
- rm -rf ~/.config/pulseaudio && pulseaudio -k
- sudo alsa force-reload
-
** Description changed:
BUG condition:
Gnome Settings>Appearance> disable "auto hide the dock"
You will see clock gets displaced to a bit right from the center from
the screen & this looks bad.
WORKAROUND:
Enable "auto hide the dock" from gnome settings
+
+ //this is probably a
Public bug reported:
My sound card stopped being recognized suddenly today. lspci shows the
card, but alsa and pulseaudio don't see it. I verified that the kernel
modules are installed.
I noticed this today when I logged on and the only audio device was the
dummy device. I tried the various
I'm also having this problem. Ubuntu 20.04, wine-5.0 (Ubuntu 5.0-3ubuntu1)
downloaded from the
official repository, Notepad++ 7.8.6.
Clipboard works fine a couple times after restarting notepad++, then at
some point I need to copy several times, then CTRL+C doesn't seem to work
anymore but
Public bug reported:
BUG condition:
Gnome Settings>Appearance> disable "auto hide the dock"
You will see clock gets displaced to a bit right from the center from
the screen & this looks bad.
WORKAROUND:
Enable "auto hide the dock" from gnome settings
ProblemType: Bug
DistroRelease: Ubuntu
** Description changed:
- I was refreshing my spare laptop: clean Windows 10 installation with
- unallocated space left followed by Ubuntu installation.
+ I was refreshing my spare Lenovo laptop: clean Windows 10 installation
+ with unallocated space left followed by Ubuntu installation.
Not all devices can have their ROM read. This is one that can't.
** Changed in: fwupd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884387
Title:
fwupdmgr
Public bug reported:
me aparecio el error
La ejecucion de grub-install/dev/sda fallo
esto es un error fatal
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules:
Public bug reported:
I was refreshing my spare laptop: clean Windows 10 installation with
unallocated space left followed by Ubuntu installation.
Ubuntu 20.04 dual boot installation failed with: grub-install: error:
failed to register the EFI boot entry: Invalid argument.
ProblemType: Bug
Hello dears - me too:
it is a ASUS with Ryzen and Kubuntu LTS 20.04 - It happens from my point of
view only with battary power.
May be it is related to also happen
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873325 with missing
firmware, that also not can found in git repo for Linux
** Attachment added: "demonstration.jpg"
https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1538615/+attachment/5385654/+files/demonstration.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
sudo fwupdmgr verify [DEVICEID]
gives
failed to verify RTL810xE PCI Express Fast Ethernet controller: failed
to read firmware: Error reading from file: Input/output error
Is there some file-permission error in the system, or the fwupd
definition for this device is wrong,
What's new : I can reproduce the problem on Ubuntu 20.04 live USB, so
I'm sure the root cause is not a broken config on my side.
To summarize :
Ubuntu 20.04 / Fedora 32.1 are affected. (Ubuntu 19.10 is not)
- Rhythmbox 3.4.4 fully affected (wrong sink at start + output is switched to a
RAOP
** Package changed: ubuntu => network-config (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884104
Title:
Ubuntu 20.04 Server "Losing" IP4 address
To manage notifications about this bug
NOT fixed in 5.4.0; it just recurred here on cold start from battery
power.
OS: Ubuntu 20.04 focal
Kernel: x86_64 Linux 5.4.0-37-generic
Uptime: 17m
Packages: 2908
Shell: bash 5.0.16
Resolution: 5360x1440
DE: GNOME 3.36.2
WM: BudgieWM
WM Theme: Pocillo
GTK Theme: Pocillo-dark [GTK2/3]
Public bug reported:
fwupdmgr --show-all-devices get-devices
does show three devices, one updatable.
fwupdmgr refresh
says "Successfully downloaded new metadata: 0 local devices supported"
sudo fwupdmgr verify [DEVICEID]
gives
failed to verify [DEVICENAME]: no results for XPath query
Looking at the history around isc-dhcp, it appears if i read it properly that
isc-dhcp sever for Ubuntu has been abandoned.
If this is the case should it even be in the focal build
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: grub-installer (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/1875911
** Description changed:
[Impact]
This is a bug fix release that includes:
- translation updates;
- bug fix updates for netspeed, drivemount and window-picker applets;
NEWS
Change log for 3.63.4:
I just did an update and "Files" was updated with it, so I checked, and
for me at least, it appears this behavior is fixed. Here is what was
updated with this update:
Upgrade: libgirepository-1.0-1:amd64 (1.64.0-2, 1.64.1-1~ubuntu20.04.1),
gir1.2-freedesktop:amd64 (1.64.0-2,
void *resolve_builtin_cpu(void) {
__builtin_cpu_init();
if (__builtin_cpu_supports("sse4.1"))
return sse41;
else
return portable;
}
Is the right way to implement ifunc resolver.
** Changed in: gcc-10 (Ubuntu)
Status: New => Invalid
** Changed in: glibc (Ubuntu)
Aha! nevermind
One has to call __builtin_cpu_init in ifunc resolver as documented at
https://gcc.gnu.org/onlinedocs/gcc-10.1.0/gcc/x86-Built-in-
Functions.html#x86-Built-in-Functions
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
in high contrast mode the calendar display uncomfortable
i.e. the weekends and the column with the number of week are very hard
to comprehend :(
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-37.41-generic
Public bug reported:
I am trying to use ifunc
On good architectures like armhf & arm64, glibc passes hwcaps argument
to the ifunc resolver function, which one can use to test for various
features.
On x86_64, no argument is passed, thus I'm trying to use
__builtin_cpu_supports() function
This was fixed in commit https://gitlab.gnome.org/GNOME/gnome-
applets/-/commit/37f11c22511e112777d59cb34d5d7733508c31b4
This is part of the GNOME Applets 3.36.3 release.
** Changed in: gnome-applets (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you
Public bug reported:
[Impact]
This is a bug fix release that includes:
- translation updates;
- bug fix updates for netspeed, drivemount and window-picker applets;
NEWS
Change log for 3.63.4:
https://gitlab.gnome.org/GNOME/gnome-applets/-/commit/ea8ec983c8d5e285c341b7a9448e0bf20d43d363
Change
** Attachment added: "test_builtin_ifunc.c"
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1884382/+attachment/5385629/+files/test_builtin_ifunc.c
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
[Impact]
The nautilus desktop file shipped in GNOME has been renamed by nautilus [1].
The drivemount applet is still using the old desktop file id which prevents it
from opening nautilus.
Fixed in:
** Bug watch added: gitlab.gnome.org/GNOME/gnome-applets/-/issues #17
https://gitlab.gnome.org/GNOME/gnome-applets/-/issues/17
** Also affects: gnome-applets via
https://gitlab.gnome.org/GNOME/gnome-applets/-/issues/17
Importance: Unknown
Status: Unknown
--
You received this bug
For every error when executing
sudo apt upgrade
unable to make backup link of './usr/lib/i386-linux-gnu/libkrb5.so.3.3'
before installing new version: Input/output error
remove the referenced file
sudo rm -rf /usr/lib/i386-linux-gnu/libkrb5.so.3.3
then proceed.
--
You received this bug
The package that is installed in the stock version of ubuntu (20.04) is
1:6.4.3-0
As I said, still getting the same error.
On Sat, Jun 20, 2020 at 11:45 AM Marc Bruell wrote:
> I updated both ubuntu 20.04 and mate 20.04, and I continue to get the
> error that the object can't be opened.
>
>
To proceed with upgrade, for every error
dpkg: error processing archive
/var/cache/apt/archives/libgl1-mesa-dri_19.2.8-0ubuntu0~18.04.3_i386.deb
(--unpack):
unable to make backup link of './usr/lib/i386-linux-gnu/dri/vmwgfx_dri.so'
before installing new version: Input/output error
I updated both ubuntu 20.04 and mate 20.04, and I continue to get the error
that the object can't be opened.
On Sat, Jun 20, 2020 at 1:35 AM Tim Passingham <1869...@bugs.launchpad.net>
wrote:
> I am now using version Version: 6.4.4.2
> Build ID: 1:6.4.4-0ubuntu0.20.04.1
> CPU threads: 8; OS:
** Attachment added: "patcl_list_mint.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875199/+attachment/5385619/+files/patcl_list_mint.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Attaching files as requested...
Please let me know if I can provide any additional information, and
thank you as always for your help!
** Attachment added: "pactl_list_ubuntu.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875199/+attachment/5385618/+files/pactl_list_ubuntu.txt
It's exactly the same with kernel 5.7.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875150
Title:
Mouse and keyboard intermittently stop working until Logitech Unifying
Receiver is replugged
Public bug reported:
Text labels should be clipped (like with text-overflow: ellipsis).
See first param on the screenshot.
Ubuntu 20.04
gnome-control-center:
Installed: 1:3.36.2-0ubuntu1
Candidate: 1:3.36.2-0ubuntu1
** Affects: gnome-control-center (Ubuntu)
Importance: Undecided
This bug was fixed in commit https://gitlab.gnome.org/GNOME/gnome-
applets/-/commit/acbb16cb49a3d0d6abe93bf5a1e9b8b42fdbcf4b
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879140
Title:
This bug is ubuntu-specific.
Fedora's 3.36.3 gnonme-control-center does not have this issue, see this
report & closure upstream
https://gitlab.gnome.org/GNOME/gnome-control-
center/-/issues/1034#note_844891
In my case Tweaks does NOT exhibit this bug. This weird behavior only
happens in
I'm having the same issue - dead cursor appears after machine has gone
to sleep when I have multiple monitors connected. I'm on Ubuntu 20.04
and use Wayland, on an AMD GPU. I have updated everything with apt to
the most recent version and the issue is still occurring for me.
--
You received this
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-tweaks (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/1854660
Public bug reported:
[Impact]
When a netspeed applet with opened dialogs is destroyed then the dialogs
are not properly destroyed. This can result in leaked memory.
This bug is fixed in the GNOME Applets release 3.36.4 (in commit
https://gitlab.gnome.org/GNOME/gnome-
** Attachment added: "Bug"
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1882630/+attachment/5385616/+files/VID-20200620-WA0002.mp4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
#9 new bug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1882630
Title:
[amdgpu] Plymouth boot animation (dots) drawn over the desktop
wallpaper
To manage notifications about this bug go to:
I hope that soon it will be fix on the next update kernel :(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872108
Title:
Bass not on working Lenovo ThinkPad X1 Carbon 7th gen running focal
To
another crash yesterday no new error links, ran another prevboot.
On Thu, Jun 18, 2020 at 7:57 AM DavidJr.
wrote:
> Crashed again overnight. No response from mouse, keyboard, or power
> button. Hard rebooted. Dont see any new error links. I have reinstalled
> TeamViewer and disabled dash to
Hello,
i'm back to this issue. I reinstalled Ubuntu 20.04 on the same laptop
and i'm still having sound related issues, as other seems to also
feedback.
Main issue is the stability of the computer with default settings. It
happens on a random (but high ratio) basis that the computer gets
Hi Thierry,
>From memory I did set "on demand" mode and it worked correctly.
Now it is a strange situation, kernel 5.4.0-28 is the latest that boots
correctly in my setup if only built in screen (on later versions, it hangs
shortly after Linux boot started, Lenovo sign still there and progress
Ah, I was too fast.
It is fixed once restarted. After some usage still gets the same error
(using shortcut and also from clipit Preferences menu)
Thank you and best regards,
Igor
pet, 19. lip 2020. u 08:35 Igor Racic napisao je:
> It is fixed.
> Thank you!
>
> čet, 18. lip 2020. u 23:35
** Attachment added: "Bug 2"
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1882630/+attachment/5385614/+files/VID-20200620-WA0001.mp4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
This bug was fixed in the package systemd - 245.6-1ubuntu1
---
systemd (245.6-1ubuntu1) groovy; urgency=medium
[ Balint Reczey ]
* Merge to Ubuntu from Debian unstable
- Dropped changes:
* Don't try calling NULL callback in bus_wait_for_units_clear.
* test: Skip
This bug was fixed in the package systemd - 245.6-1ubuntu1
---
systemd (245.6-1ubuntu1) groovy; urgency=medium
[ Balint Reczey ]
* Merge to Ubuntu from Debian unstable
- Dropped changes:
* Don't try calling NULL callback in bus_wait_for_units_clear.
* test: Skip
This bug was fixed in the package systemd - 245.6-1ubuntu1
---
systemd (245.6-1ubuntu1) groovy; urgency=medium
[ Balint Reczey ]
* Merge to Ubuntu from Debian unstable
- Dropped changes:
* Don't try calling NULL callback in bus_wait_for_units_clear.
* test: Skip
I have the same problem with mainline 5.7 kernel.
** Summary changed:
- [Inspiron 5391, Realtek ALC3204] Sound stopped to work, errors in dmesg
+ [Inspiron 5391, Realtek ALC3204] Sound stopped to work, "error : DSP panic!"
in dmesg
** Description changed:
Sound worked, but accidentally
1 - 100 of 176 matches
Mail list logo
