Public bug reported:
Ubuntu 20.4 LTS
Nautilus 3.36.3
What I expect to happen:
When selecting "Show Hidden Files" checkbox, I expect any icons on my desktop
for hidden files to appear and for icons for regular files to remain visible.
What actually happens:
when I select the "Show Hidden
I can confirm steps in #4 fixes a problem in Ubuntu 18.04. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1786822
Title:
Pinta constantly crashes in Ubuntu 18.04 fresh install
To manage
The following errors can be found in UbiquitySyslog.txt which was
automatically attached to this bug report:
Jul 18 18:22:17 ubuntu kernel: [ 182.025929] SQUASHFS error: zlib
decompression failed, data probably corrupt
Jul 18 18:22:17 ubuntu kernel: [ 182.025932] SQUASHFS error:
Hi Daniel,
First I have to admit I am fairly new to Ubuntu
I had an issue upgrading from 19.04 to 20.04 - so I decided to do a fresh
install.
First boot sequence got stuck on a Splash screen with a spinning wheel. I
searched the internet for a solution:
https://itsfoss.com/fix-ubuntu-freezing/
To get this working on 18.04, delete all the blacklisted module name
from /lib/modprobe.d/*.conf
Then, add the module name to `/etc/modules-load.d/myfoo-module.conf`.
After that three things are needed:
$ sudo update-initramfs -u
$ sudo depmod -a
$ sudo systemctl reboot
--
You received this
Public bug reported:
This happened immediately after booting a Live CD for GNUradio.
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: libpam-systemd:amd64 204-5ubuntu20.24
ProcVersionSignature: Ubuntu 3.19.0-28.30~14.04.1-generic 3.19.8-ckt5
Uname: Linux 3.19.0-28-generic x86_64
OK, this is really strange, after tons of reboots to Ubuntu and Win 10, it
started working again after I disabled the legacy boot option.
Still would like a solution to the timeouts other than rebooting twice, though.
I'm a developer, so if there are multiple code changes that need to be tested,
Can you attach a dmesg output please? I want to see if it's the same
issue I'm facing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886541
Title:
touchpad not workin on lenovo ideapad, installed
I've started bluetoothd with the debug option. Here's what happens when
trying to pair with a bluetooth mouse:
bluetoothd[5497]: src/agent.c:agent_ref() 0x559521027e80: ref=2
bluetoothd[5497]: src/device.c:bonding_request_new() Requesting bonding for
E5:5B:67:2A:09:76
bluetoothd[5497]:
Now we're getting somewhere!
chrome://gpu shows:
```
Vulkan: Disabled
...
Video Acceleration Information
Vulkan Information
Device Performance Information
Log Messages
[4784:4784:0719/142605.755018:ERROR:vaapi_wrapper.cc(511)] : vaInitialize
failed: unknown libva error
Can we try pulling in https://packages.ubuntu.com/bionic-updates/mesa-
va-drivers instead of the base bionic package pulled right now by the
https://launchpad.net/~chromium-team/+snap/chromium-snap-from-source-
enable-vaapi build config (which doesn't use Bionic-Updates)?
--
You received this
If you need a fix for the bug in previous versions of Ubuntu, please
perform as much as possible of the SRU Procedure [1] to bring the need
to a developer's attention.
[1]: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure
--
You received this bug notification because you are a member of
** Package changed: ubuntu => xorg (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888142
Title:
notification for some apps cannot be disabled in ubuntu 20.04 release
To manage
** Package changed: ubuntu => ubiquity (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888150
Title:
crashes when trying to install with ZFS option on HPE Proliant
Microserver Gen+ with 3
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Reviewing your log files attached to this bug report it
seems that there is a problem with your installation media (CD/DVD).
You can verify the integrity of the Ubuntu ISO files you downloaded by
following the
Public bug reported:
There is a new ESR release of Thunderbird and I don't see an issue about
the plans for the move to that new version. There looks to be some
changes to the profile that are one way--once you have moved that
profile to version 78, you can't work with it on older versions of
Test Kernels here:
https://kernel.ubuntu.com/~kmously/kernel-kmously-bc5bba9-bgA6
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887703
Title:
[Regression] 5.4 is not identifying all ports on
The bug does not occure with proprietary nvidia driver
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874217
Title:
[nvidia] Dual monitor setup with secondary monitor in portrait-right
mode cause
Doesn't seem to be happening with 20.04, for now at least.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873093
Title:
Gnome-terminal tab bar steals keyboard focus
To manage notifications about
** Changed in: libsimpleini (Ubuntu)
Status: Confirmed => 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/1871790
Title:
Missing dependency on libicu-dev for libsimpleini-dev
To
You have been subscribed to a public bug:
After upgrading a laptop configured with LVM from 18.04 to 20.04 the volume
group is no longer found.
During boot the console shows
Volume group "vg01" not found
Cannot process volume group vg01
Gave up waiting for suspend/resume device
ALERT!
Just reported the bug upstream : https://github.com/lm-sensors/lm-
sensors/issues/257
** Bug watch added: github.com/lm-sensors/lm-sensors/issues #257
https://github.com/lm-sensors/lm-sensors/issues/257
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Success!
Thank you very much !
On Sun, Jul 19, 2020 at 2:15 PM Steve Daigle wrote:
> Sounds good - going for walk with my wife - Will follow those steps and
> get back to you in a few hours.
>
> Thanks for your help
>
> Steve
>
>
> On Sun, Jul 19, 2020 at 2:05 PM Daniel Letzeisen <
>
You're welcome. I will mark as Fix Released. Reopen it if you experience
the no boot issue again.
** Changed in: xorg (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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 1888166
and then change the status of the bug to 'Confirmed'.
If, due to the
Public bug reported:
[Impact]
the alsa upstream worte the ucm3 files for amd renoir audio, but to
load the ucm3, it depends on the kernel module name, and the upstream
ucm3 needs the name snd-xxx, so we need to backport the patches
from mainline kernel to change the kernel module name to meet
I'm changing this ticket to lvm2 and focal, removing the currently marked as
affected "Ubuntu on IBM z Systems" project, since the logs show that they come
from a amd64 system.
Nevertheless, the referenced LP 1874381, was on s390x.
** Project changed: ubuntu-z-systems => lvm2 (Ubuntu)
** Also
However, this could even be marked as duplicate of LP 1874381 ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887964
Title:
VG unavailable after upgrade from 18.04 to 20.04 Cannot process volume
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/1885756
Public bug reported:
pressing the power button initializes power up of a HP specter, but does
not boot into ubuntu. esc pressed repeatedly to bring up bios menu is
required.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu
Public bug reported:
Release is mint 20, Ubuntu 20.04.
Version of the package is 5.5.2.1-0ubuntu3.
The machine should not freeze and not even accept sysreq input. The driver
should not crash.
The machine freezes on hibernate randomly, disconnects randomly from PEAP/EAP
networks. This does not
Public bug reported:
Package: stunnel4
Version: 3:5.44-1ubuntu3
Package: libssl1.1
Version: 1.1.1g-1+ubuntu18.04.1+deb.sury.org+1
stunnel4 is randomly crashing on ubuntu 18.04
Jul 19 19:37:47 localhost stunnel: LOG2[765]: Double free attempt:
ptr=0x7fc1bc0a79d0 alloc=client.c:1398
Public bug reported:
Description: Ubuntu 18.04.4 LTS
Release: 18.04
apt-cache policy clamav
clamav:
Installed: 0.102.3+dfsg-0ubuntu0.18.04.1
Candidate: 0.102.3+dfsg-0ubuntu0.18.04.1
The current version of ClamAV for 18.04.4 LTS is 0.102.3+dfsg-
0ubuntu0.18.04.1. The current stable version
** Summary changed:
- soc/amd/renoir: improve the amd renoir audio driver to prepare to work with
ucm3
+ soc/amd/renoir: detect dmic from acpi table
** Changed in: linux (Ubuntu Groovy)
Status: Incomplete => Fix Committed
--
You received this bug notification because you are a member
The problem also might be that I'm running Chromium inside XWayland
rather than natively on X11. I'll try popping over to X11 to see whether
it works...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
>From X11 without Wayland:
Vulkan still shows as disabled but the init error doesn't turn up.
Log Messages
[18061:18061:0719/145212.290039:ERROR:sandbox_linux.cc(374)] :
InitializeSandbox() called with multiple threads in process gpu-process.
Apparently issue still exists because today I updated from Linux Mint
19.3 to 20.04 (Ulyana) and received this exact error which was resolved
by David Lechner's fix in post #3.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Apparently issue still exists because today I updated from Linux Mint
18.3 to 20.04 (Ulyana) and received this exact error which was resolved
by David Lechner's fix in post #3.
--
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 1461162 ***
https://bugs.launchpad.net/bugs/1461162
** This bug has been marked a duplicate of bug 1461162
Rotate layer, save and crash appears
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have a Ryzen 5 3600x and I have the same issue. I get freezes where I
can't move the cursor and the only fix is manually rebooting the PC.
Data corruption is something that I'm already experiencing here. Not
sure what to do. I'm not using Ubuntu, though. It is also reproducible
on Ubuntu,
I'm attaching the captured btsnoop logs
** Description changed:
Expected behavior:
1.Pressing the “Cancel” button during device pairing should close the
pairing code prompt
2.Re-pairing BT keyboard after cancelling initial pairing should re-open
the pairing code prompt
I'm attaching the dmesg result
** Attachment added: "dmesg logs"
https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/1888164/+attachment/5394188/+files/dmesg%20result%20for%20Ubuntu.txt
** Description changed:
Expected behavior:
1.Pressing the “Cancel” button during
After a bit more troubleshooting, working with xrandr and the xorg.conf
doesn't seem to have any effect when on the tty, and xrandr throws a
cannot connect to display error.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
[Impact]
the alsa upstream worte the ucm3 files for amd renoir audio, but to
load the ucm3, it depends on the kernel module name, and the upstream
- ucm3 needs the name snd-xxx, so we need to backport the patches
+ ucm3 needs the name snd-xxx, so we need to backport
Public bug reported:
Currently I'm using a 4K AOC monitor on 20.04 LTS with a DisplayPort
cable.
Normally, there is a gear widget in the lower right corner of the screen
that allows me to select between XServer and Wayland. This gear is
missing. Switching to an HDMI cable corrects the issue but
Public bug reported:
This is an upstream issue-read the following bug reports.
https://github.com/linuxmint/cinnamon/issues/9401
https://github.com/linuxmint/cinnamon/issues/9468
I will shortly publish a patch/debdiff to allow for possible SRU.
This is a REGRESSION of a commit in Cinnamon
Public bug reported:
Touchpad not detected in Obsidian N141ZU after fresh install of Ubuntu 20.04.
Touchpad does not show up in /proc/bus/input/devices (file attached).
USB Mouse works correctly.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-40-generic 5.4.0-40.44
I'm not sure where you got that info, but nomodeset is like a "safe" video
mode, where a generic, unaccelerated driver is used. From the log:
[0.043487] You have booted with nomodeset. This means your GPU drivers are
DISABLED
[0.043487] Any video related functionality will be severely
This change was made by a bot.
** Changed in: linux (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/1888151
Title:
Touchpad not detected in Obsidian N141ZU
Sounds good - going for walk with my wife - Will follow those steps and get
back to you in a few hours.
Thanks for your help
Steve
On Sun, Jul 19, 2020 at 2:05 PM Daniel Letzeisen <1888...@bugs.launchpad.net>
wrote:
> I'm not sure where you got that info, but nomodeset is like a "safe" video
Hello. Is there any movements toward this bug extinction?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874217
Title:
[nvidia] Dual monitor setup with secondary monitor in portrait-right
mode
Unfortunately, I'm not sure how best to reproduce this. I can tell you
that we were seeing this on really busy units.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1565744
Title:
"Mutex
Gnome team have fixed this upstream, see fix
https://gitlab.gnome.org/GNOME/gnome-online-accounts/-/issues/42
v3.18.2 will not be fixed.
I have manually compiled and installed v3.18.3 with my own API key but
it still does not work. Gnome team have advised that 3.18 is now
unsupported and latest
I ran into this today. So annoying. I kept getting "Please check that
the PPA name or format is correct." This error message is so
misleading... The Internet is littered with people working around the
"add-apt-repository" script since no one can really figure out the real
reason for this error
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: software-properties (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/1364176
** Description changed:
- For focal and oem-5.6 kernel, these all 5 patches are needed, for
- groovy kernel, since the 1st patch is already in the 5.8 kernel, the
- groovy kernel only needs the last 3 patches [3/5, 4/5 and 5/5].
+ Groovy kernel already merged the patchset
[Impact]
- the alsa
Hey, does this relate to you?
https://github.com/linuxmint/cinnamon/issues/9468
https://github.com/linuxmint/cinnamon/issues/9401
** Bug watch added: github.com/linuxmint/cinnamon/issues #9468
https://github.com/linuxmint/cinnamon/issues/9468
** Bug watch added:
Public bug reported:
I installed mercurial-keyring with:
sudo apt-get install mercurial-keyring
When I try to use it I get:
$ hg pull
pulling from ***
keyring: keyring backend doesn't seem to work, password can not be restored.
Falling back to prompts. Error
Hi! Ronn-NG maintainer here.
If I retroactively produced a Ronn-NG 0.8.2 patch release with just the
bugfix for this, would you be interested in pulling that in to an update
release for Ubuntu 20.x, so that users on the older Ubuntu version could
get the fix too?
--
You received this bug
Public bug reported:
ubuntu desktop 20.04 ISO image on USB crashes when trying to install
with ZFS experimental option. I am trying to install on HPE Proliant
Microserver Gen10+, 16GB RAM, 3 SSD's 500GB each.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15
I've packaged the fix for xenial in this branch:
https://code.launchpad.net/~bryce/ubuntu/+source/apache2/+git/apache2/+ref/ubuntu
/xenial-devel/
However I've not been able to construct a configuration+workload to
reproduce the error message. Can someone describe a way to trigger the
messages
Public bug reported:
Expected behavior:
1. Pressing the “Cancel” button during device pairing should close the
pairing code prompt
2. Re-pairing BT keyboard after cancelling initial pairing should re-open
the pairing code prompt
Problem:
1. Pressing the “Cancel” button during
I am seeing this again on the latest stable release on Ubuntu 20.04 on a
Dell Precision with attached displays.
Linux bdp 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64
x86_64 x86_64 GNU/Linux
TU117GLM [Quadro T1000 Mobile]
nvidia-driver-440
BTW the fix first appeared in 5.50 (commit
f1b8cdef95d6b51cab122f2be0694521f47092d0).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887910
Title:
[bionic]blutoothd segfault when you cancel the
Test on Tiger Lake platfrom.
codename: focal
CID: 202006-28008
BIOS: 0.5.2
kernel: 5.6.0-1020-oem
Steps:
1. $ sudo apt update
2. $ sudo apt dist-upgrade
3. check audio, "Dummy output"
4. Add proposed developer option
5. $ sudo apt install linux-firmware => update to 1.187.2
6. sudo reboot
Test on Tiger Lake platfrom.
codename: focal
CID: 202006-28008
BIOS: 0.5.2
kernel: 5.6.0-1020-oem
Steps:
1. $ sudo apt update
2. $ sudo apt dist-upgrade
3. check audio, "Dummy output"
4. Add proposed developer option
5. $ sudo apt install linux-firmware => update to 1.187.2
6. $ sudo reboot
I'm going to remove Ubuntu Sponsors from this briefly, until the
following are fixed:
1. The issue mentioned in comment #7 - The Bug Description on this page
needs improving.
2. The email address used in the patch needs replacing
with your real email.
3. Need to mention the bug ID and the
Oh, I can't remove Ubuntu Sponsors. Still, please fix all of the above.
** Also affects: bluez (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: bluez (Ubuntu Groovy)
Importance: High
Status: In Progress
** Also affects: bluez (Ubuntu Bionic)
Importance:
** Also affects: dash-to-dock via
https://github.com/micheleg/dash-to-dock/issues/1274
Importance: Unknown
Status: Unknown
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of
** Description changed:
This is an upstream issue-read the following bug reports.
https://github.com/linuxmint/cinnamon/issues/9401
https://github.com/linuxmint/cinnamon/issues/9468
I will shortly publish a patch/debdiff to allow for possible SRU.
This is a REGRESSION of a
Public bug reported:
Do not know what is the problem
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15 [modified:
lib/partman/automatically_partition/question]
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (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/1870995
[Expired for gnome-control-center (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: gnome-control-center (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for firefox (Ubuntu) because there has been no activity for 60
days.]
** Changed in: firefox (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for dbus (Ubuntu) because there has been no activity for 60
days.]
** Changed in: dbus (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/1871538
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (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/1877655
[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 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 dbus (Ubuntu Focal) because there has been no activity for
60 days.]
** Changed in: dbus (Ubuntu Focal)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for libinput (Ubuntu) because there has been no activity for 60
days.]
** Changed in: libinput (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (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/1878315
[Expired for xorg-server (Ubuntu) because there has been no activity for
60 days.]
** Changed in: xorg-server (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (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/1878495
[Expired for im-config (Ubuntu) because there has been no activity for
60 days.]
** Changed in: im-config (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
I made a new transparent layer, then made a circle with the oval
selection tool. Then I hit X to put white as my foreground color. Then
used bucket fill tool to fill the circle in white, but instead, it
crashed the gimp.
KUbuntu 18.04.4 LTS
Bug information is in a text file
*** This bug is a duplicate of bug 1532508 ***
https://bugs.launchpad.net/bugs/1532508
I think bug 1532508 has been around for so long that it's now about any
case in which the lock screen is used.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:
apport-collect 1887914
When reporting bugs in the future please use apport by using 'ubuntu-
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 1888068
and then change the status of the bug to 'Confirmed'.
If, due to the
The issue was resolved by enabling hardware decoding via option in the
media player.
** Changed in: 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/1887599
Title:
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It seems that your bug report is not filed about a
specific source package though, rather it is just filed against Ubuntu
in general. It is important that bug reports be filed about source
packages so that people
** Changed in: firefox (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879742
Title:
When using Google Meet on Firefox, delay sending sound from
any idea here? maybe it is caused by gnome-terminal and scrollbar-
handling (reducing inner width)?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880397
Title:
scrolling in gnome-terminal destroys
** Summary changed:
- Jogl 2.3.2 crashes with "Profile GL4bc is not available on X11GraphicsDevice"
- solved in Jogl 2.4.0
+ Jogl 2.3.2 crashes with "Profile GL4bc is not available on X11GraphicsDevice"
- fixed in Jogl 2.4.0
--
You received this bug notification because you are a member of
The following errors can be found in UbiquitySyslog.txt which was
automatically attached to this bug report:
Jul 3 10:11:44 ubuntu finish-install: W: Failed to fetch
http://in.archive.ubuntu.com/ubuntu/dists/focal/InRelease Temporary failure
resolving 'in.archive.ubuntu.com'
Jul 3 10:11:44
** Tags added: focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1532508
Title:
Screen contents revealed briefly on resume, before even unlocking
To manage notifications about this bug go to:
*** This bug is a duplicate of bug 1532508 ***
https://bugs.launchpad.net/bugs/1532508
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1532508, so it is being marked as such. Please
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
** Changed in: linux (Ubuntu Focal)
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887909
[Expired for xorg-server (Ubuntu) because there has been no activity for
60 days.]
** Changed in: xorg-server (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (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/1879432
[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
Bugs, which is subscribed to Ubuntu.
101 - 200 of 241 matches
Mail list logo
