libopencc1.1 1.1.1+git20200624+ds2-4ubuntu1 in hirsute amd64:
universe/libs/optional/100% -> main
libopencc1.1 1.1.1+git20200624+ds2-4ubuntu1 in hirsute arm64:
universe/libs/optional/100% -> main
libopencc1.1 1.1.1+git20200624+ds2-4ubuntu1 in hirsute armhf:
universe/libs/optional/100% -> main
This was it, the amd64 snap in the stable channel now displays the new
tab page correctly.
** Changed in: chromium-browser (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
[Expired for mutter (Ubuntu) because there has been no activity for 60
days.]
** Changed in: mutter (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in 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 Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
*** This bug is a duplicate of bug 1616650 ***
https://bugs.launchpad.net/bugs/1616650
Thanks for your attention into this bug. Surprise to know this problem exist
since 2016 ;)
I remember the apt version of chromium will show an "!" mark on the 3-dot menu
button to tell you restart
same issue here -
Jan 25 20:32:39 oculus vlc_vlc.desktop[1414205]: [7f3134417940]
vdpau_chroma filter error: video mixer attributes failure: An invalid handle
value was provided.
Jan 25 20:32:39 oculus vlc_vlc.desktop[1414205]: [7f3134417940]
vdpau_chroma filter error: video mixer
Hello all,
Can you look in upstream and if no information about your problem, please
create an issue?
- https://github.com/paulusmack/ppp/pulls?q=is%3Apr+sort%3Aupdated-desc
- https://github.com/paulusmack/ppp/issues?q=is%3Aissue+sort%3Aupdated-desc+
Thanks in advance.
--
You received this
Thanks!
** Also affects: gnome-control-center via
https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1239
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in
It does say that, but still, I think forcing focus on that window is a
good thing, because one can switch windows unintentionally. E.g. having
accidentally clicked on underlying window, or if some other window pops
up.
Anyway, here's the upstream issue:
Thanks for your report.
This is an upstream GNOME matter, and should better be discussed there.
OTOH, it looks like the discussion has already started.
https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1222
So possibly in GNOME 40 (Ubuntu 21.10).
However, in the meantime you can use
Well, it says "Press Esc to cancel", doesn't it?
Anyway, please feel free to report it upstream.
https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in
** Package changed: ubuntu => xorg (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1913229
Title:
Arrow keys do not select the folder on Desktop
Status in xorg package in
You have been subscribed to a public bug:
1. Go to Desktop (Super + D). Not in the file explorer.
2. Press arrow keys to select files or folders.
Expected this to happen - Arrows keys should have selected the files or
folders.
What actually happened - Arrow keys do not select a folder or file.
** Changed in: chromium-browser (Ubuntu)
Assignee: (unassigned) => Olivier Tilloy (osomon)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1908284
Title:
[snap] chromium
Tentative fix for the snap: https://git.launchpad.net/~chromium-team
/chromium-browser/+git/snap-from-
source/commit/?id=3058eebc1bf787c5692511386508d10895f73f5a
** Changed in: chromium-browser (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you
This bug was fixed in the package opencc -
1.1.1+git20200624+ds2-4ubuntu1
---
opencc (1.1.1+git20200624+ds2-4ubuntu1) hirsute; urgency=medium
* debian/libopencc1.1.symbols:
- Refreshed due to s390x on Ubuntu (LP: #1912882)
-- Gunnar Hjalmarsson Sat, 23 Jan 2021 11:12:00
** Changed in: ubuntu-drivers-common (Ubuntu)
Status: Invalid => Fix Released
** Changed in: ubuntu-drivers-common (Ubuntu)
Importance: Undecided => Medium
** Changed in: nvidia-prime (Ubuntu)
Status: Invalid => Fix Released
** Changed in: nvidia-prime (Ubuntu)
Importance:
I suspect a regression introduced by
https://chromium.googlesource.com/chromium/src/+/5012d34829ca24488da8e768eb8bcf9e42278637
when building with optimize_webui=false, which results in the resource
bundle missing a bunch of new tab page resources, including chrome
As suggested in https://askubuntu.com/a/1310367, disabling
chrome://flags/#ntp-webui works around the issue. There must be more to
it though, because the official Google Chrome package doesn't seem to be
affected.
--
You received this bug notification because you are a member of Desktop
Public bug reported:
Reproduction steps:
- Open gnome-control-center
- Go to "Keyboard shortcuts"
- Try to change any shortcut (but don't actually change it, just wait until the
"shortcut selector" window opens)
- Switch to another window (alt+tab)
What happens:
I can switch to another window,
Public bug reported:
Description:Ubuntu 20.04.1 LTS
Release:20.04
xorg:
Installed: 1:7.7+19ubuntu14
Candidate: 1:7.7+19ubuntu14
Version table:
*** 1:7.7+19ubuntu14 500
500 http://nl.archive.ubuntu.com/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status
Public bug reported:
I'm trying to set a shortcut for keyboard layout switching, but it's
impossible to use some keyboard buttons. Also, pressing some
combinations leads to unexpected results.
For example:
- Shift+Ctrl - impossible to set
- Shift+Alt - impossible to set
- Ctrl+Alt - impossible
*** This bug is a duplicate of bug 1793640 ***
https://bugs.launchpad.net/bugs/1793640
Ah indeed removing timidity (package timidity-daemon) fixed the issue.
Thanks for your really quick feedback.
** This bug has been marked a duplicate of bug 1793640
Pulseaudio fails to detect sound
I see sched_setaffinity also used in base/cpu_affinity_posix.cc, so I
doubt it's only beneficial on ARM.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1900679
Title:
[snap]
> @avamander, do you have a reproducer for this?
I'm just using it on a Ryzen 9 3900x and Radeon R7 360. I have GPU
acceleration enabled to the extent it is possible.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in
Not just the snap, the deb packages for xenial and bionic appear to be
similarly affected.
** Summary changed:
- [snap] Start-up page is blank after upgrading to version 88
+ Start-up page is blank after upgrading to version 88
** Changed in: chromium-browser (Ubuntu)
Status: New =>
Public bug reported:
Lenovo ideapad 730s touchpad wrist detection does not work.
I have tried both synaptics and libinput drivers. The libinput driver's scroll
coasting does not work. With the synaptics driver, using synclient to set
PalmDetect=1 has no effect.
In KDE's touchpad settings,
with lenovo ideapad 730s, wrist and pressure detection still don't work under
5.11.
with libinput, scroll coasting doesn't work.
I am current back to using synaptics. using synclient to turn PalmDetect on
has no effect.
--
You received this bug notification because you are a member of Desktop
So I did a bit of looking and it appears that Chromium only calls
sched_setaffinity for it's renderer threads on Android (maybe?). I'm not
super familiar with Chromium source code so it's a bit difficult for me
to tell, but I tried playing videos etc. which might trigger some sort
of rendering
Public bug reported:
Bug Description
On ubuntu we have a handy shortcut to take screenshots then select the
are to grab. By default the shortcut is assigned to shift+print (Prt
Scrn key on the keyboard). If I go into Google Chrome, open the options
panel (the 3 little vertical dots), then go
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-screenshot (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-screenshot in Ubuntu.
Public bug reported:
Software updates stated "Broadcom Inc. and subsidiaries: BCM4312 802.11b/g
LP-PHY (Wireless 1397 WLAN Mini-Card)
Using Broadcom 802.11 Linux STA wireless driver source from
bcmwl-kernel-source (proprietary)
do not use this device..
After placing a bullet next to"
Before I grab'n'build 5.11, I'd like to know if my issue is similar.
I have a lenovo ideapad 730s.
The touchpad works fine for pointing, single, double and triple clicks.
I have tried both the synaptics and libinput drivers. It's been a while since
I was comparing them; IIRC, I'm currently
** Package changed: ubuntu => firefox (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1913176
Title:
Firefox and Ubuntu Software Centre has bug
Status in firefox package in
You have been subscribed to a public bug:
Hi Everyone.
I'm currently running Ubuntu 20.04.1 LTS (Focal Fossa), I'm new of
Ubuntu and learning how to use it.
I watched YouTube about "Ubuntu tutorial" on Firefox browser, When I
press keyboard space to pause the video on YouTube website, it turn
(OS is Ubuntu 20.04 on x64)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1913181
Title:
Chromium Browser (snap) Crashes when at-Sign is Entered
Status in chromium-browser
Public bug reported:
The Chromium Browser (snap) in version stable (88.0.4324.96) and beta
(88.0.4324.87) crashes reproducibly if the at sign is entered via the
keyboard.
I'm using KDE Desktop and German keyboard layout, meaning the "at" sign
is at the hotkey "AltGr-Q".
Pressing this key
** Changed in: evince (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1897856
Title:
snap launch fails: symbol lookup error
Status in
** Package changed: evince (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1910763
Title:
Steam Proton fails with Kernel 5.8.0-36 Ubuntu 20.04.1
Status in
> retry the test
with a trigger on libxmlb to get the -proposed version installed.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1907433
Title:
[SRU] New stable release 2.64.6
Okay I've verified this now, thanks for adding. Using
2.64.6-1~ubuntu20.04.1 I tested
- Logging in to Ubuntu
- Logging out from Ubuntu
- Fast user switching w/gdm3
- Many applications which use GLib, including gedit and epiphany-browser
It seems good to me.
There are two outstanding
** Description changed:
I've just booted into Ubuntu 20.04 after several days or using another
release and found that the Chromium snap was updated on booting from
version 87.0.4280.141 to version 88.0.4324.96. I haven't changed any
settings but I find that Chromium's start-up or new tab
Public bug reported:
I've just booted into Ubuntu 20.04 after several days or using another
release and found that the Chromium snap was updated on booting from
version 87.0.4280.141 to version 88.0.4324.96. I haven't changed any
settings but I find that Chromium's start-up or new tab page is
This bug was fixed in the package ubuntu-drivers-common -
1:0.8.6.3~0.20.04.2
---
ubuntu-drivers-common (1:0.8.6.3~0.20.04.2) focal; urgency=medium
* Skip tests on riscv64, replacing powerpc which is no longer part of
focal. Thus make ubuntu-drivers-common available on focal on
This bug was fixed in the package ubuntu-drivers-common -
1:0.8.6.3~0.20.04.2
---
ubuntu-drivers-common (1:0.8.6.3~0.20.04.2) focal; urgency=medium
* Skip tests on riscv64, replacing powerpc which is no longer part of
focal. Thus make ubuntu-drivers-common available on focal on
Gracias, sin embargo hay otro problema ahora, ciertamente el monitor
reconoce una resolución mayor y aparentemente se solucionó la falla, el
detalle es que ahora aparece el escritorio pero el teclado y el mouse no
responden, se queda colgada y no puedo ingresar el usuario, por lo tanto no
puedo
This bug was fixed in the package nvidia-prime - 0.8.15.3~0.20.04.1
---
nvidia-prime (0.8.15.3~0.20.04.1) focal; urgency=medium
[ Alberto Milone ]
* prime-select:
- Enable runtimepm in on-demand mode if supported (LP: #1895855).
- Disable workaround for on-demand mode.
This has been pulled in as part of the backport in LP: #1904583 .
Skipping verification in favor of general testing in the aforementioned
bug.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-prime in Ubuntu.
This bug was fixed in the package nvidia-prime - 0.8.15.3~0.20.04.1
---
nvidia-prime (0.8.15.3~0.20.04.1) focal; urgency=medium
[ Alberto Milone ]
* prime-select:
- Enable runtimepm in on-demand mode if supported (LP: #1895855).
- Disable workaround for on-demand mode.
The verification of the Stable Release Update for ubuntu-drivers-common
has completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that
Please try to scan with hpaio Sane backend. It should help.
The escl Sane backend, which you are currently using, is buggy and most of
issue was resolved with next Sane version.
** Changed in: simple-scan (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because
The verification of the Stable Release Update for nvidia-prime has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
This bug was fixed in the package ubuntu-drivers-common -
1:0.8.6.3~0.20.10.1
---
ubuntu-drivers-common (1:0.8.6.3~0.20.10.1) groovy; urgency=medium
* UbuntuDrivers/detect.py,
tests/test_ubuntu_drivers.py:
- Prefer LTSB releases over NFB ones for non gpgpu cases too.
*
This bug was fixed in the package nvidia-prime - 0.8.15.3~0.20.10.1
---
nvidia-prime (0.8.15.3~0.20.10.1) groovy; urgency=medium
* debian/postinst.in:
- Remove obsolete udev rules (LP: #1904583).
* debian/rules:
- Add postinst file to the autoclean target.
*
Settings as triaged for libtiff so it's picked up by the proposed
migration report
** Changed in: tiff (Ubuntu Hirsute)
Status: Invalid => Triaged
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to tiff in Ubuntu.
I have been watching this issue for several months and am excited that
it is finally moving forward. It looks to me like all the organizational
details have now been resolved. What's still holding us back from
getting the latest Thunderbird?
--
You received this bug notification because you are
Thank you for the verification! Since we are slowly preparing things for
.2, I will release the ubuntu-drivers-common SRUs a day early from their
usual 7-day aging period.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-prime in
Unfortunately, I seem to be on that version of gnome-shell-extension-
desktop-icons and still experience the freeze when I enable the desktop
icons extension. Here's the dpkg output and gnome-shell logs:
https://pastebin.ubuntu.com/p/yqDTV5KBmC/
** Changed in: gnome-shell-extension-desktop-icons
I made a duplicate bug report. The reply to me to post comments here in
this bug report instead. The specs for my bug report is here:
https://bugs.launchpad.net/bugs/1912816
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
apt update then apt upgrade fixed the problem for me about four days
ago. Thank you for fixing this.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in
Ubuntu.
https://bugs.launchpad.net/bugs/1905519
The verification of the Stable Release Update for tracker has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
This bug was fixed in the package tracker - 2.3.6-0ubuntu1
---
tracker (2.3.6-0ubuntu1) focal; urgency=medium
* New upstream version (lp: #1896073)
* debian/rules:
- build without Bsymbolic and strip Bsymbolic-function, fixes the
tracker search hanging (lp: #1861358)
The verification of the Stable Release Update for tracker has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
This bug was fixed in the package tracker - 2.3.6-0ubuntu1
---
tracker (2.3.6-0ubuntu1) focal; urgency=medium
* New upstream version (lp: #1896073)
* debian/rules:
- build without Bsymbolic and strip Bsymbolic-function, fixes the
tracker search hanging (lp: #1861358)
This bug was fixed in the package pulseaudio - 1:13.99.1-1ubuntu3.10
---
pulseaudio (1:13.99.1-1ubuntu3.10) focal; urgency=medium
* d/p/0703-switch-on-unknown.patch
- The 0703-switch-on-unknown.patch was introduced from the version of
ubuntu3.9, this patch could bring a
Public bug reported:
I got the problem after upgrading to Ubuntu 20.04 from 18.04. I re-
installed cups. Printer is recognised over usb and also in the wireless
network.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: cups 2.3.1-9ubuntu1.1
ProcVersionSignature: Ubuntu 5.4.0-62.70-generic
** Bug watch added: gitlab.gnome.org/GNOME/gnome-disk-utility/-/issues #43
https://gitlab.gnome.org/GNOME/gnome-disk-utility/-/issues/43
** Changed in: gnome-disk-utility
Importance: Medium => Unknown
** Changed in: gnome-disk-utility
Status: Expired => Unknown
** Changed in:
Public bug reported:
My system freezes when I'm in lockscreen. This happens every few ours
after I leave the computer running some low to mediocre computation
tasks, no memory problems. It does not happen when I run heavy tasks. I
can only hard reboot, nothing else is working.
ProblemType: Bug
>From the ML:
Hi Christian,
an update on the PPP issue:
- we have internally tried the Patch provided by the PPP team and it didn't
work as expected.
- we have found out that default value for "ipv6cp-accept-remote" is wrong as
well. Changing this solved the issue and the PPP client received
Public bug reported:
I don't know, it just a message appeared that there was an error.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libmbim-glib4:amd64 1.22.0-2
ProcVersionSignature: Ubuntu 5.4.0-62.70-generic 5.4.78
Uname: Linux 5.4.0-62-generic x86_64
ApportVersion:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: chromium-browser (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
This issue is fixed in libfprint v1.90.2
** Changed in: fprintd (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fprintd in Ubuntu.
https://bugs.launchpad.net/bugs/1893059
Title:
Need
Okay. I'm happy that it's so easy to reproduce. Upgrading to 21.04 isn't
really a solution right now.
Will mutter receive the 3.38 upgrade on LTS or is there another way to
fix it?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter
The verification of the Stable Release Update for pulseaudio has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
This bug was fixed in the package pulseaudio - 1:13.99.2-1ubuntu2.3
---
pulseaudio (1:13.99.2-1ubuntu2.3) groovy; urgency=medium
* d/p/0703-switch-on-unknown.patch
- The 0703-switch-on-unknown.patch was introduced from the version of
ubuntu2.2, this patch could bring a
*** This bug is a duplicate of bug 1616650 ***
https://bugs.launchpad.net/bugs/1616650
This is indeed quite unfortunate, and it's not limited to chromium, it's
a problem that potentially affects all snaps.
I suggest enabling the "Refresh App Awareness" experimental feature
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1913027/+attachment/5456533/+files/UdevDb.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1913027/+attachment/5456534/+files/acpidump.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
apport information
** Attachment added: "Snap.ChromiumPrefs.txt"
https://bugs.launchpad.net/bugs/1913027/+attachment/5456527/+files/Snap.ChromiumPrefs.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
apport information
** Attachment added: "Snap.Info.core.txt"
https://bugs.launchpad.net/bugs/1913027/+attachment/5456530/+files/Snap.Info.core.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
apport information
** Attachment added: "Snap.Info.core18.txt"
https://bugs.launchpad.net/bugs/1913027/+attachment/5456531/+files/Snap.Info.core18.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
apport information
** Attachment added: "Snap.Info.chromium.txt"
https://bugs.launchpad.net/bugs/1913027/+attachment/5456529/+files/Snap.Info.chromium.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
apport information
** Attachment added: "Snap.Connections.txt"
https://bugs.launchpad.net/bugs/1913027/+attachment/5456528/+files/Snap.Connections.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
apport information
** Attachment added: "Snap.Info.gtk-common-themes.txt"
https://bugs.launchpad.net/bugs/1913027/+attachment/5456532/+files/Snap.Info.gtk-common-themes.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1913027/+attachment/5456525/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1913027/+attachment/5456526/+files/ProcModules.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1913027/+attachment/5456524/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1913027/+attachment/5456523/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1913027/+attachment/5456521/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1913027/+attachment/5456515/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1913027/+attachment/5456522/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1913027/+attachment/5456516/+files/Dependencies.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1913027/+attachment/5456518/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1913027/+attachment/5456519/+files/Lsusb.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1913027/+attachment/5456517/+files/Lspci.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1913027/+attachment/5456520/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
Public bug reported:
When I am using chromium while it is being updated by snap in the
background, every new tab will become "Aw snap" with SIGTRAP error.
While the current working tabs remains working, open new tab is not
possible without restart the whole chromium.
I'd like to suggest to
The 2.3.6-0ubuntu1 update works as described
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to tracker in Ubuntu.
I just verified on focal on a machine with BIOS ID:097E (202005-27873):
- kernel : 5.6.0-1042-oem
$ apt list nvidia-prime ubuntu-drivers-common
Listing... Done
nvidia-prime/focal,focal,now 0.8.14 all [installed,automatic]
ubuntu-drivers-common/now 1:0.8.6.3~0.20.04.2 amd64 [installed,local]
$
99 matches
Mail list logo
