[Desktop-packages] [Bug 1843392] Re: [snap] smart card reader no longer works
*** This bug is a duplicate of bug 1967632 *** https://bugs.launchpad.net/bugs/1967632 Hi, Pascal. The snap with the new pcscd interface is awaiting approval from the Snapcraft team. Once that is done I'll post here so that someone can attempt to verify the fix. > I think I incidentally removed the 'duplicate' Don't worry, it remains logged in the full activity log page (link at the end of comment section), so I just added it back, thanks for the heads up. ** This bug has been marked a duplicate of bug 1967632 [snap] apparmor denied when trying to load pkcs11 module for smart card authentication -- 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/1843392 Title: [snap] smart card reader no longer works Status in Mozilla Firefox: Confirmed Status in chromium-browser package in Ubuntu: In Progress Status in firefox package in Ubuntu: Confirmed Bug description: chromium uses the Netscape Cryptographic Module to access smartcards for authentication purposes. This stopped working when switching to the snap version. Chromium would normally access the setup in ~/.pki/nssdb/pkcs11.txt That file would refer to a library used to access the smart card. I.e /usr/lib/x86_64-linux-gnu/pkcs11/opensc- pkcs11.so The problem can be bypassed by manually launching chromium via: /snap/chromium/current/usr/lib/chromium-browser/chrome To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1843392/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 2033433] Re: Chromium leaks tens of gigabytes of pixmaps (in the Xorg process) after using hardware accelerated video
Daniel, thanks a lot for guiding the debugging on this, and Andreas for carrying the debugging out. I thought incorrectly that this was already stated: The leak does not happen with VAAPI disabled ---> chromium --disable-features=VaapiVideoDecoder,VaapiVideoEncoder,VaapiVideoDecodeLinuxGL <--- (As such it does not occur in stable/candidate channels, that do not have VAAPI merged in.) We don't have much of a delta about hwacc with upstream right now, it's mostly patches for Ozone (which doesn't get used in Xorg, correct me if I'm wrong) and then the chromium.launcher that simply turns on some flags. Patches: https://git.launchpad.net/~chromium-team/chromium-browser/+git/snap-from-source/tree/build/chromium-patches/optimization?h=dev Flags: https://git.launchpad.net/~chromium-team/chromium-browser/+git/snap-from-source/tree/launcher/chromium.launcher?h=dev#n128 -- 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/2033433 Title: Chromium leaks tens of gigabytes of pixmaps (in the Xorg process) after using hardware accelerated video Status in chromium-browser package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Opinion Bug description: chromium 118.0.5966.0 2604 latest/edge Whenever I use chromium in a video session (meet, youtube) that used hardware acceleration, for a long time (like 20min or more), and then close it, the whole desktop freezes, and the laptop fan turns on. Logging in remotely I see that Xorg is at 100% CPU. The rest of the system is operational, but nothing graphical is. Just the mouse cursor moves around. SOMETIMES, if I wait a few minutes, Xorg resumes behaving normally, and I can use the desktop again, but most of the time I have to login remotely and kill -9 xorg (plain kill won't do it). With wayland, this does not happen. This could very well be an Xorg bug, but filing here first for visibility. $ lsgpu card0Intel Alderlake_p (Gen12) drm:/dev/dri/card0 └─renderD128 $ lscpu Architecture:x86_64 CPU op-mode(s):32-bit, 64-bit Address sizes: 46 bits physical, 48 bits virtual Byte Order:Little Endian CPU(s): 16 On-line CPU(s) list: 0-15 Vendor ID: GenuineIntel Model name:12th Gen Intel(R) Core(TM) i7-1270P CPU family: 6 Model: 154 Thread(s) per core: 2 Core(s) per socket: 12 Socket(s): 1 Stepping:3 CPU(s) scaling MHz: 41% CPU max MHz: 4800, CPU min MHz: 400, BogoMIPS:4992,00 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdp e1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqd q dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave a vx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb ssbd ibrs ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept_ ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid rdseed adx smap clflushopt clwb intel_pt sha_ni xsaveopt xsavec xgetbv1 xsaves split_lock_detect avx_vnni dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp hwp_pkg_req hfi umip pku ospke waitpkg gfni vaes vpclmulqdq tme rdpid movdiri movdir64b fsrm md_clear serialize pconfig arch_lbr ibt flush_l1d arch_capabilities Virtualization features: Virtualization:VT-x Caches (sum of all): L1d: 448 KiB (12 instances) L1i: 640 KiB (12 instances) L2:9 MiB (6 instances) L3:18 MiB (1 instance) NUMA: NUMA node(s): 1 NUMA node0 CPU(s): 0-15 Vulnerabilities: Itlb multihit: Not affected L1tf: Not affected Mds: Not affected Meltdown: Not affected Mmio stale data: Not affected Retbleed: Not affected Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl Spectre v1:Mitigation; usercopy/swapgs barriers and __user pointer sanitization Spectre v2:Mitigation; Enhanced IBRS, IBPB conditional, RSB filling, PBRSB-eIBRS SW sequence Srbds: Not affected Tsx async abort: Not affected
[Desktop-packages] [Bug 2009739] Re: hwacc build crashes on direct scanout.
** Tags removed: hwacc ** Tags added: kivu -- 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/2009739 Title: hwacc build crashes on direct scanout. Status in chromium-browser package in Ubuntu: New Bug description: This pertains to the HWACC branches of the chromium snap. When launched full-screen on an Intel iGPU, the hardware overlay use will result in a core dump. This could be related to direct-scanout and overlay planes? To reproduce: $ chromium --start-fullscreen OS: Ubuntu 22.10 Chromium: 111.0.5563.19-hwacc GPU: Alderlake iGPU stolk@workpc:/snap/chromium/current/bin$ snap info chromium name: chromium summary: Chromium web browser, open-source version of Chrome publisher: Canonical✓ store-url: https://snapcraft.io/chromium contact: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap license: unset description: | An open-source browser project that aims to build a safer, faster, and more stable way for all Internet users to experience the web. commands: - chromium.chromedriver - chromium snap-id: XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R tracking: latest/beta/hwacc refresh-date: yesterday at 08:52 PST channels: latest/stable:110.0.5481.177 2023-03-06 (2367) 156MB - latest/candidate: 111.0.5563.64 2023-03-08 (2381) 155MB - latest/beta: 111.0.5563.64 2023-03-07 (2380) 155MB - latest/edge: 112.0.5615.12 2023-03-03 (2375) 156MB - installed: 111.0.5563.19-hwacc(2376) 174MB - stolk@workpc:/snap/chromium/current/bin$ chromium --start-fullscreen [73039:73039:0308/101357.917887:WARNING:chrome_main_delegate.cc(618)] This is Chrome version 111.0.5563.19 (not a warning) [73039:73039:0308/101358.450380:WARNING:wayland_object.cc(152)] Binding to gtk_shell1 version 4 but version 5 is available. [73039:73039:0308/101358.450401:WARNING:wayland_object.cc(152)] Binding to zwp_pointer_gestures_v1 version 1 but version 3 is available. [73039:73039:0308/101358.450416:WARNING:wayland_object.cc(152)] Binding to zwp_linux_dmabuf_v1 version 3 but version 4 is available. Gtk-Message: 10:13:58.455: Not loading module "atk-bridge": The functionality is provided by GTK natively. Please try to not load it. [73039:73039:0308/101358.611145:WARNING:account_consistency_mode_manager.cc(70)] Desktop Identity Consistency cannot be enabled as no OAuth client ID and client secret have been configured. [73039:73039:0308/101358.625559:WARNING:wayland_surface.cc(151)] Server doesn't support zcr_alpha_compositing_v1. [73039:73039:0308/101358.625573:WARNING:wayland_surface.cc(166)] Server doesn't support overlay_prioritizer. [73039:73039:0308/101358.625579:WARNING:wayland_surface.cc(180)] Server doesn't support surface_augmenter. [73039:73039:0308/101358.625583:WARNING:wayland_surface.cc(195)] Server doesn't support wp_content_type_v1 [73039:73039:0308/101358.625586:WARNING:wayland_surface.cc(214)] Server doesn't support zcr_color_management_surface. [73039:73039:0308/101358.625774:WARNING:cursor_loader.cc(123)] Failed to load a platform cursor of type kNull [73039:73039:0308/101358.626013:VERBOSE1:wayland_cursor.cc(151)] Failed to hide cursor. No mouse enter serial found. [73209:73209:0308/101358.654205:ERROR:gpu_init.cc(525)] Passthrough is not supported, GL is egl, ANGLE is [73209:73209:0308/101358.657517:WARNING:sandbox_linux.cc(393)] InitializeSandbox() called with multiple threads in process gpu-process. [73039:73039:0308/101358.692393:WARNING:bluez_dbus_manager.cc(247)] Floss manager not present, cannot set Floss enable/disable. [73039:73039:0308/101358.706280:VERBOSE1:wayland_cursor.cc(151)] Failed to hide cursor. No mouse enter serial found. [73039:73039:0308/101358.706292:VERBOSE1:wayland_cursor.cc(151)] Failed to hide cursor. No mouse enter serial found. [73039:73039:0308/101358.706371:VERBOSE1:wayland_cursor.cc(151)] Failed to hide cursor. No mouse enter serial found. [73039:73039:0308/101358.706375:VERBOSE1:wayland_cursor.cc(151)] Failed to hide cursor. No mouse enter serial found. [73209:73209:0308/101358.722161:ERROR:gbm_pixmap_wayland.cc(75)] Cannot create bo with format= RGBA_ and usage=SCANOUT [73209:73209:0308/101358.722276:ERROR:gbm_pixmap_wayland.cc(75)] Cannot create bo with format= RGBA_ and usage=GPU_READ [73209:73209:0308/101358.722320:ERROR:shared_image_factory.cc(661)] CreateSharedImage: could not create backing. [73209:73209:0308/101358.722375:ERROR:shared_image_factory.cc(516)] DestroySharedImage: Could not find shared image mailbox [73209:73209:0308/101358.722458:ERROR:raster_decoder.cc(1117)] RasterDecoderImpl: Context lost during MakeCurrent. [73209:73209:0308/101358.722500:ERROR:gpu_service_impl.cc(980)] Exiting
[Desktop-packages] [Bug 2033433] Re: Chromium leaks tens of gigabytes of pixmaps (in the Xorg process) after using hardware accelerated video
** Tags added: kivu -- 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/2033433 Title: Chromium leaks tens of gigabytes of pixmaps (in the Xorg process) after using hardware accelerated video Status in chromium-browser package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Opinion Bug description: https://crbug.com/1467689 --- chromium 118.0.5966.0 2604 latest/edge Whenever I use chromium in a video session (meet, youtube) that used hardware acceleration, for a long time (like 20min or more), and then close it, the whole desktop freezes, and the laptop fan turns on. Logging in remotely I see that Xorg is at 100% CPU. The rest of the system is operational, but nothing graphical is. Just the mouse cursor moves around. SOMETIMES, if I wait a few minutes, Xorg resumes behaving normally, and I can use the desktop again, but most of the time I have to login remotely and kill -9 xorg (plain kill won't do it). With wayland, this does not happen. This could very well be an Xorg bug, but filing here first for visibility. $ lsgpu card0Intel Alderlake_p (Gen12) drm:/dev/dri/card0 └─renderD128 $ lscpu Architecture:x86_64 CPU op-mode(s):32-bit, 64-bit Address sizes: 46 bits physical, 48 bits virtual Byte Order:Little Endian CPU(s): 16 On-line CPU(s) list: 0-15 Vendor ID: GenuineIntel Model name:12th Gen Intel(R) Core(TM) i7-1270P CPU family: 6 Model: 154 Thread(s) per core: 2 Core(s) per socket: 12 Socket(s): 1 Stepping:3 CPU(s) scaling MHz: 41% CPU max MHz: 4800, CPU min MHz: 400, BogoMIPS:4992,00 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdp e1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqd q dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave a vx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb ssbd ibrs ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept_ ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid rdseed adx smap clflushopt clwb intel_pt sha_ni xsaveopt xsavec xgetbv1 xsaves split_lock_detect avx_vnni dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp hwp_pkg_req hfi umip pku ospke waitpkg gfni vaes vpclmulqdq tme rdpid movdiri movdir64b fsrm md_clear serialize pconfig arch_lbr ibt flush_l1d arch_capabilities Virtualization features: Virtualization:VT-x Caches (sum of all): L1d: 448 KiB (12 instances) L1i: 640 KiB (12 instances) L2:9 MiB (6 instances) L3:18 MiB (1 instance) NUMA: NUMA node(s): 1 NUMA node0 CPU(s): 0-15 Vulnerabilities: Itlb multihit: Not affected L1tf: Not affected Mds: Not affected Meltdown: Not affected Mmio stale data: Not affected Retbleed: Not affected Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl Spectre v1:Mitigation; usercopy/swapgs barriers and __user pointer sanitization Spectre v2:Mitigation; Enhanced IBRS, IBPB conditional, RSB filling, PBRSB-eIBRS SW sequence Srbds: Not affected Tsx async abort: Not affected ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: chromium-browser (not installed) ProcVersionSignature: Ubuntu 6.2.0-27.28-generic 6.2.15 Uname: Linux 6.2.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Aug 29 16:47:30 2023 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2033433/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
Re: [Desktop-packages] [Bug 2011281]
> Currently, I have a ~/snap/chromium/common/chromium/Default/Login Data which
> was last modified September 5. So perhaps passwords are still being written
> here.
Does this file have the expected number of entries, with sites you
recognize as having your saved passwords that you cannot nonetheless
display? I attach one such file as an example. Namely we are looking for
--->
INSERT INTO logins
VALUES('http://example.com','','','username','userPassword',X'763130ea422b31c5606d2e8435833cf73bb492',
...
<---
Also please confirm that version > last_compatible_version in that file.
When you enter a site for which you have a password saved, does the key
button appear in the address bar, as in the attached picture?
> So for you, chrome://settings/passwords shows your passwords under 'Saved
> Passwords' without having to specify --password-store=basic?
Yes. And --password-store=basic should be neither needed nor correct if
password-manager-service is connected, as it is for working without
keyring, but it was worth trying just in case something had gone funky
in that aspect.
And one more thing worth trying is to export your passwords, that is a
button under the vertical dots button in that page. Then look in the
generated CSV and see if the passwords are readable there.
--
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/2011281
Title:
chromium snap upgrade "lost" my passwords
Status in chromium-browser package in Ubuntu:
New
Bug description:
On upgrade to chromium snap revision 2333 (now since upgraded to
2367), I received a window with a notice about password migration:
"Password storage via the Gnome keyring has been fixed, but for it to
work, you have to rename your old
~/snap/chromium/common/chromium/Default/Login Data file so that a new,
working one can replace it."
I don't remember if I did this or not. However, when I went to use my
saved passwords in chromium today, I found that they were absent.
Tracking down the data in the chromium profile, I found that there was
a ~/snap/chromium/common/chromium/Default/Login Data.old containing
all of my passwords, and a
~/snap/chromium/common/chromium/Default/Login Data containing a single
password entry for a site that I happened to have created a new login
for in the past few days.
That's not a very user-friendly experience on upgrade.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2011281/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 2011281]
Forgot the attachments, here they are. ** Attachment added: "passwd.png" https://bugs.launchpad.net/bugs/2011281/+attachment/5699821/+files/passwd.png ** Attachment added: "login-data.dump" https://bugs.launchpad.net/bugs/2011281/+attachment/5699822/+files/login-data.dump -- 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/2011281 Title: chromium snap upgrade "lost" my passwords Status in chromium-browser package in Ubuntu: New Bug description: On upgrade to chromium snap revision 2333 (now since upgraded to 2367), I received a window with a notice about password migration: "Password storage via the Gnome keyring has been fixed, but for it to work, you have to rename your old ~/snap/chromium/common/chromium/Default/Login Data file so that a new, working one can replace it." I don't remember if I did this or not. However, when I went to use my saved passwords in chromium today, I found that they were absent. Tracking down the data in the chromium profile, I found that there was a ~/snap/chromium/common/chromium/Default/Login Data.old containing all of my passwords, and a ~/snap/chromium/common/chromium/Default/Login Data containing a single password entry for a site that I happened to have created a new login for in the past few days. That's not a very user-friendly experience on upgrade. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2011281/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2035220] Re: cve-2023-4863
** 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 chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/2035220
Title:
cve-2023-4863
Status in chromium-browser package in Ubuntu:
Fix Released
Status in firefox package in Ubuntu:
Fix Released
Status in firefox-esr package in Ubuntu:
New
Status in libwebp package in Ubuntu:
New
Status in thunderbird package in Ubuntu:
Fix Released
Status in chromium package in Debian:
New
Status in libwebp package in Debian:
Confirmed
Bug description:
[$NA][1479274] Critical CVE-2023-4863: Heap buffer overflow in WebP. Reported
by Apple Security Engineering and Architecture (SEAR) and The Citizen Lab at
The University of Torontoʼs Munk School on 2023-09-06
https://chromereleases.googleblog.com/2023/09/stable-channel-update-for-desktop_11.html
high profile remote vulnerability
themusicgod1@eva1:~$ apt-cache policy chromium-browser
chromium-browser:
Installed: 1:85.0.4183.83-0ubuntu2.22.04.1
Candidate: 1:85.0.4183.83-0ubuntu2.22.04.1
Version table:
current available snap:
chromium 116.0.5845.179
fix is in:
chromium 116.0.5845.187
ubuntu: 22.04.3 LTS jammy
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: chromium-browser 1:85.0.4183.83-0ubuntu2.22.04.1
ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
Uname: Linux 6.2.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 12 08:38:06 2023
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/sda2 ext4 228G 162G 55G 75% /
tmpfs tmpfs 3.9G 66M 3.8G 2% /dev/shm
/dev/sda2 ext4 228G 162G 55G 75% /
InstallationDate: Installed on 2017-04-18 (2337 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: MSI MS-7994
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic
root=UUID=333c5e4f-3f61-4abf-b950-f19431c843d6 ro text
Snap.Changes: no changes found
Snap.ChromeDriverVersion: ChromeDriver 116.0.5845.179
(17ff023f3eb4f6883321db9399bfc65560ef84a9-refs/branch-heads/5845@{#1745})
Snap.ChromiumVersion: Chromium 116.0.5845.179 snap
SourcePackage: chromium-browser
UpgradeStatus: Upgraded to jammy on 2023-06-14 (89 days ago)
dmi.bios.date: 12/16/2016
dmi.bios.release: 5.12
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5.80
dmi.board.asset.tag: Default string
dmi.board.name: H110M GAMING (MS-7994)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr5.80:bd12/16/2016:br5.12:svnMSI:pnMS-7994:pvr1.0:rvnMSI:rnH110MGAMING(MS-7994):rvr1.0:cvnMSI:ct3:cvr1.0:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: MS-7994
dmi.product.sku: Default string
dmi.product.version: 1.0
dmi.sys.vendor: MSI
mtime.conffile..etc.apport.crashdb.conf: 2020-06-07T21:16:26.397404
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2035220/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2035360] Re: GPU hangs in SketchUp on Intel gen12 due to outdated MESA library
Thanks, it seems you already pinned down the issue, I'll investigate how to get the newer Mesa in (I think that's provided by a gnome-* snap) and all the following is just for completeness. Can you attach the following information? ---> snap info chromium firefox snap connections chromium snap connections firefox <--- > In order to test if the system MESA has the fix while the Chromium snaps does not, I unpacked it and ran the Chromium binary against system libraries. In general, for testing purposes you can run the unconfined binary directly by calling /snap/chromium/current/usr/lib/chromium- browser/chrome or /snap/firefox/current/usr/lib/firefox/firefox. You can also verify if an issue is related to hardware acceleration by passing --disable-gpu. ** Also affects: firefox via https://gitlab.freedesktop.org/mesa/mesa/-/issues/9695 Importance: Unknown Status: Unknown ** Project changed: firefox => mesa -- 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/2035360 Title: GPU hangs in SketchUp on Intel gen12 due to outdated MESA library Status in Mesa: Unknown Status in chromium-browser package in Ubuntu: New Status in firefox package in Ubuntu: New Bug description: When opening a SketchUp model (example) in Firefox or Chromium, after ~5 seconds, the SketchUp logo freezes for ~4 seconds, and we see a blank page. The logs show the GPU hang and browser rendering context failed to initialise. This has 100% reproducibility on my 12-gen GPU. On this system with Ubuntu 23.04, I have always seen a GPU hang with the stock Ubuntu kernel or mainline. Log files as attachment - the output of 'dmesg' is at https://quora.org/OJnlVgn4xZ/dmesg.txt - the output of 'dmesg' with kernel boot args 'drm.debug=0x1e log_buf_len=16M' is at https://quora.org/OJnlVgn4xZ/dmesg-debug.txt - the output of /sys/class/drm/card0/error is at https://quora.org/OJnlVgn4xZ/i915-error.txt Since I was able to cause failure uncontained to the rendering process when performing this 5-8 times, there is an argument that this is a security (DoS) issue, though I'll let someone else make a judgement. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2035360/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2035603] [NEW] Duplicity 1.2.2-1 fails to build from source
Public bug reported: https://launchpadlibrarian.net/685130555/buildlog_ubuntu-mantic- amd64.duplicity_1.2.2-1_BUILDING.txt.gz ** Affects: duplicity (Ubuntu) Importance: Undecided Assignee: Nathan Teodosio (nteodosio) Status: Triaged ** Tags: ftbfs -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/2035603 Title: Duplicity 1.2.2-1 fails to build from source Status in duplicity package in Ubuntu: Triaged Bug description: https://launchpadlibrarian.net/685130555/buildlog_ubuntu-mantic- amd64.duplicity_1.2.2-1_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/2035603/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2035603] Re: Duplicity 1.2.2-1 fails to build from source
** Patch added: "duplicity.diff" https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/2035603/+attachment/5700826/+files/duplicity.diff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/2035603 Title: Duplicity 1.2.2-1 fails to build from source Status in duplicity package in Ubuntu: Triaged Bug description: https://launchpadlibrarian.net/685130555/buildlog_ubuntu-mantic- amd64.duplicity_1.2.2-1_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/2035603/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2035360] Re: GPU hangs in SketchUp on Intel gen12 due to outdated MESA library
** Also affects: firefox (Ubuntu) Importance: Undecided Status: New -- 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/2035360 Title: GPU hangs in SketchUp on Intel gen12 due to outdated MESA library Status in Mesa: Unknown Status in chromium-browser package in Ubuntu: New Status in firefox package in Ubuntu: New Bug description: When opening a SketchUp model (example) in Firefox or Chromium, after ~5 seconds, the SketchUp logo freezes for ~4 seconds, and we see a blank page. The logs show the GPU hang and browser rendering context failed to initialise. This has 100% reproducibility on my 12-gen GPU. On this system with Ubuntu 23.04, I have always seen a GPU hang with the stock Ubuntu kernel or mainline. Log files as attachment - the output of 'dmesg' is at https://quora.org/OJnlVgn4xZ/dmesg.txt - the output of 'dmesg' with kernel boot args 'drm.debug=0x1e log_buf_len=16M' is at https://quora.org/OJnlVgn4xZ/dmesg-debug.txt - the output of /sys/class/drm/card0/error is at https://quora.org/OJnlVgn4xZ/i915-error.txt Since I was able to cause failure uncontained to the rendering process when performing this 5-8 times, there is an argument that this is a security (DoS) issue, though I'll let someone else make a judgement. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2035360/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2035360] Re: GPU hangs in SketchUp on Intel gen12 due to outdated MESA library
Asked about the possibility of a rebuild at https://github.com/ubuntu/gnome-sdk/issues/167. ** Bug watch added: github.com/ubuntu/gnome-sdk/issues #167 https://github.com/ubuntu/gnome-sdk/issues/167 -- 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/2035360 Title: GPU hangs in SketchUp on Intel gen12 due to outdated MESA library Status in Mesa: Unknown Status in chromium-browser package in Ubuntu: New Status in firefox package in Ubuntu: New Bug description: When opening a SketchUp model (example: https://app.sketchup.com/share/tc/europe/9jWfPS5lgN8?stoken=KYi8KrAR6g3gv6OqLAKNEEMrQHLOA7jd8oV20HmBbHrZqyPRPmG1QlPurYkJnuw_) in Firefox or Chromium, after ~5 seconds, the SketchUp logo freezes for ~4 seconds, and we see a blank page. The logs show the GPU hang and browser rendering context failed to initialise. This has 100% reproducibility on my 12-gen GPU. On this system with Ubuntu 23.04, I have always seen a GPU hang with the stock Ubuntu kernel or mainline. Log files as attachment - the output of 'dmesg' is at https://quora.org/OJnlVgn4xZ/dmesg.txt - the output of 'dmesg' with kernel boot args 'drm.debug=0x1e log_buf_len=16M' is at https://quora.org/OJnlVgn4xZ/dmesg-debug.txt - the output of /sys/class/drm/card0/error is at https://quora.org/OJnlVgn4xZ/i915-error.txt Since I was able to cause failure uncontained to the rendering process when performing this 5-8 times, there is an argument that this is a security (DoS) issue, though I'll let someone else make a judgement. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2035360/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2035603] Re: Duplicity 1.2.2-1 fails to build from source
For consistency I followed the maintainer's patch style. ** Patch added: "duplicity.diff" https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/2035603/+attachment/5700853/+files/duplicity.diff ** Patch removed: "duplicity.diff" https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/2035603/+attachment/5700826/+files/duplicity.diff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/2035603 Title: Duplicity 1.2.2-1 fails to build from source Status in duplicity package in Ubuntu: Triaged Bug description: https://launchpadlibrarian.net/685130555/buildlog_ubuntu-mantic- amd64.duplicity_1.2.2-1_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/2035603/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2035360] Re: GPU hangs in SketchUp on Intel gen12 due to outdated MESA library
** Changed in: chromium-browser (Ubuntu) Status: New => Fix Committed ** Changed in: firefox (Ubuntu) Status: New => Fix Committed -- 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/2035360 Title: GPU hangs in SketchUp on Intel gen12 due to outdated MESA library Status in Mesa: New Status in chromium-browser package in Ubuntu: Fix Committed Status in firefox package in Ubuntu: Fix Committed Bug description: When opening a SketchUp model (example: https://app.sketchup.com/share/tc/europe/9jWfPS5lgN8?stoken=KYi8KrAR6g3gv6OqLAKNEEMrQHLOA7jd8oV20HmBbHrZqyPRPmG1QlPurYkJnuw_) in Firefox or Chromium, after ~5 seconds, the SketchUp logo freezes for ~4 seconds, and we see a blank page. The logs show the GPU hang and browser rendering context failed to initialise. This has 100% reproducibility on my 12-gen GPU. On this system with Ubuntu 23.04, I have always seen a GPU hang with the stock Ubuntu kernel or mainline. Log files as attachment - the output of 'dmesg' is at https://quora.org/OJnlVgn4xZ/dmesg.txt - the output of 'dmesg' with kernel boot args 'drm.debug=0x1e log_buf_len=16M' is at https://quora.org/OJnlVgn4xZ/dmesg-debug.txt - the output of /sys/class/drm/card0/error is at https://quora.org/OJnlVgn4xZ/i915-error.txt Since I was able to cause failure uncontained to the rendering process when performing this 5-8 times, there is an argument that this is a security (DoS) issue, though I'll let someone else make a judgement. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2035360/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1732482] Re: [snap] doesn't properly save desktop files for "create shortcuts" action
** Changed in: chromium-browser (Ubuntu) Status: Triaged => In Progress ** Changed in: chromium-browser (Ubuntu) Assignee: (unassigned) => Nathan Teodosio (nteodosio) ** Description changed: For chrome apps, the create shortcuts action should create desktop files but it doesn't. I suspect it has something to do with paths. - - -  - tracking:candidate - installed: 62.0.3202.94 (123) 246MB - -- 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/1732482 Title: [snap] doesn't properly save desktop files for "create shortcuts" action Status in chromium-browser package in Ubuntu: In Progress Bug description: For chrome apps, the create shortcuts action should create desktop files but it doesn't. I suspect it has something to do with paths. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1732482/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 2033017] Re: Chromium fails to get data from google end point verification helper app
Yes.
>logfile 2>&1 snap run chromium --enable-logging
If that doesn't prove sufficient you can also add --v=1.
Having journalctl -f running at the same time will allow you to see
Apparmor denials.
--
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/2033017
Title:
Chromium fails to get data from google end point verification helper
app
Status in chromium-browser package in Ubuntu:
New
Bug description:
I am trying out Google end-point verification. This is a system that
allows the admins of a Google Workplace env to set information
security requirements on the browsers/systems that connect. When using
snapped Chromium, it fails to fetch data from the host system.
The details:
Prelude
1. I use the latest Chromium from the snap-store (Version 116.0.5845.110
(Official Build) snap (64-bit))
2. I install the Google end-point verification extension:
https://chrome.google.com/webstore/detail/endpoint-verification/callobklhcbilhphinckomhgkigmfocg
3. I install the helper app:
https://support.google.com/a/users/answer/9018161?hl=en using apt.
What goes wrong
4. The helper app has a shell script that fetches the details of the host.
That works fine. Note that it detects the encrypted disk.
kristofer@kristofer-ThinkPad-X1-Nano-Gen-1:~$
/opt/google/endpoint-verification/bin/device_state.sh
serial_number: "PW00QL5N"
disk_encrypted: ENABLED
os_version: "22.04"
screen_lock_secured: ENABLED
hostname: "kristofer-ThinkPad-X1-Nano-Gen-1"
model: "20UN002KMH"
os_firewall: "no"
mac_addresses: "00:d2:b1:d3:c4:42"
mac_addresses: "00:16:3e:00:00:00"
mac_addresses: "00:16:3e:4f:fa:02"
mac_addresses: "a6:8d:49:a8:08:fb"
mac_addresses: "04:56:e5:dc:20:fd"
kristofer@kristofer-ThinkPad-X1-Nano-Gen-1:~$
5. The chromium extension attempts to get this data, but fails. Here are the
logs from the extension. Note that it has diskEncrypted set to false.
[230825 08:58:34.05] [ChromeDeviceInfoProvider] [WARNING] No policy set to
fetch device certificate.
[230825 08:58:34.05] [ChromeDeviceInfoProvider] [WARNING] Error getting
Device ID. Failed to retrieve the device id.
[230825 08:58:34.06] [ChromeDeviceInfoProvider] [DEBUG] Response:
{"osVersion":"22","diskEncrypted":false,"screenLockSecured":true,"deviceSerialNumber":"","deviceModel":"20UN002KMH","deviceHostName":"kristofer-ThinkPad-X1-Nano-Gen-1","deviceMacAddresses":[]}.
[230825 08:58:34.06] [NativeDeviceInfoProvider] [WARNING] Error while
fetching non-configurable device info. Specified native messaging host not
found.
The same extension, on the same machine, running on Chrome is able to detect
the data from (4):
[230825 09:00:49.97] [ChromeDeviceInfoProvider] [WARNING] No policy set to
fetch device certificate.
[230825 09:00:49.98] [ChromeDeviceInfoProvider] [DEBUG] Response:
{"osVersion":"22.04","diskEncrypted":true,"screenLockSecured":true,"deviceSerialNumber":"","deviceModel":"20UN002KMH","deviceHostName":"kristofer-ThinkPad-X1-Nano-Gen-1","deviceMacAddresses":["00:16:3e:4f:fa:02","00:16:3e:00:00:00","04:56:e5:dc:20:fd","a6:8d:49:a8:08:fb","00:d2:b1:d3:c4:42"],"deviceId":"QW2aBSoOVzwVDPNxJdhd1K5NtFs","osFirewall":false}.
I suspect, but I don't know, that the snap confinement prevents it
from fetching the data. Should you have any questions or need help to
get more detailed logs, please reach out to me.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2033017/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2033433] Re: Xorg 100% CPU and frozen desktop after closing chromium
Duly reproduced. I don't have SSH set up here and couldn't get out with Ctrl+Alt+Backspace either, had to resort to Sysrq. The journal shows a nouveau fault at the time of the crash. ** Changed in: chromium-browser (Ubuntu) Status: New => Confirmed ** Changed in: chromium-browser (Ubuntu) Importance: Undecided => High ** Attachment added: "journal" https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2033433/+attachment/5696501/+files/journal ** Tags added: xorg ** Tags added: nouveau -- 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/2033433 Title: Xorg 100% CPU and frozen desktop after closing chromium Status in chromium-browser package in Ubuntu: Confirmed Bug description: chromium 118.0.5966.0 2604 latest/edge Whenever I use chromium in a video session (meet, youtube) that used hardware acceleration, for a long time (like 20min or more), and then close it, the whole desktop freezes, and the laptop fan turns on. Logging in remotely I see that Xorg is at 100% CPU. The rest of the system is operational, but nothing graphical is. Just the mouse cursor moves around. SOMETIMES, if I wait a few minutes, Xorg resumes behaving normally, and I can use the desktop again, but most of the time I have to login remotely and kill -9 xorg (plain kill won't do it). With wayland, this does not happen. This could very well be an Xorg bug, but filing here first for visibility. $ lsgpu card0Intel Alderlake_p (Gen12) drm:/dev/dri/card0 └─renderD128 $ lscpu Architecture:x86_64 CPU op-mode(s):32-bit, 64-bit Address sizes: 46 bits physical, 48 bits virtual Byte Order:Little Endian CPU(s): 16 On-line CPU(s) list: 0-15 Vendor ID: GenuineIntel Model name:12th Gen Intel(R) Core(TM) i7-1270P CPU family: 6 Model: 154 Thread(s) per core: 2 Core(s) per socket: 12 Socket(s): 1 Stepping:3 CPU(s) scaling MHz: 41% CPU max MHz: 4800, CPU min MHz: 400, BogoMIPS:4992,00 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdp e1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqd q dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave a vx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb ssbd ibrs ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept_ ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid rdseed adx smap clflushopt clwb intel_pt sha_ni xsaveopt xsavec xgetbv1 xsaves split_lock_detect avx_vnni dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp hwp_pkg_req hfi umip pku ospke waitpkg gfni vaes vpclmulqdq tme rdpid movdiri movdir64b fsrm md_clear serialize pconfig arch_lbr ibt flush_l1d arch_capabilities Virtualization features: Virtualization:VT-x Caches (sum of all): L1d: 448 KiB (12 instances) L1i: 640 KiB (12 instances) L2:9 MiB (6 instances) L3:18 MiB (1 instance) NUMA: NUMA node(s): 1 NUMA node0 CPU(s): 0-15 Vulnerabilities: Itlb multihit: Not affected L1tf: Not affected Mds: Not affected Meltdown: Not affected Mmio stale data: Not affected Retbleed: Not affected Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl Spectre v1:Mitigation; usercopy/swapgs barriers and __user pointer sanitization Spectre v2:Mitigation; Enhanced IBRS, IBPB conditional, RSB filling, PBRSB-eIBRS SW sequence Srbds: Not affected Tsx async abort: Not affected ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: chromium-browser (not installed) ProcVersionSignature: Ubuntu 6.2.0-27.28-generic 6.2.15 Uname: Linux 6.2.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Aug 29 16:47:30 2023 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage:
[Desktop-packages] [Bug 2033433] Re: Xorg 100% CPU and frozen desktop after closing chromium
If you hit that again can you please also retrieve the log? -- 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/2033433 Title: Xorg 100% CPU and frozen desktop after closing chromium Status in chromium-browser package in Ubuntu: Confirmed Bug description: chromium 118.0.5966.0 2604 latest/edge Whenever I use chromium in a video session (meet, youtube) that used hardware acceleration, for a long time (like 20min or more), and then close it, the whole desktop freezes, and the laptop fan turns on. Logging in remotely I see that Xorg is at 100% CPU. The rest of the system is operational, but nothing graphical is. Just the mouse cursor moves around. SOMETIMES, if I wait a few minutes, Xorg resumes behaving normally, and I can use the desktop again, but most of the time I have to login remotely and kill -9 xorg (plain kill won't do it). With wayland, this does not happen. This could very well be an Xorg bug, but filing here first for visibility. $ lsgpu card0Intel Alderlake_p (Gen12) drm:/dev/dri/card0 └─renderD128 $ lscpu Architecture:x86_64 CPU op-mode(s):32-bit, 64-bit Address sizes: 46 bits physical, 48 bits virtual Byte Order:Little Endian CPU(s): 16 On-line CPU(s) list: 0-15 Vendor ID: GenuineIntel Model name:12th Gen Intel(R) Core(TM) i7-1270P CPU family: 6 Model: 154 Thread(s) per core: 2 Core(s) per socket: 12 Socket(s): 1 Stepping:3 CPU(s) scaling MHz: 41% CPU max MHz: 4800, CPU min MHz: 400, BogoMIPS:4992,00 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdp e1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqd q dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave a vx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb ssbd ibrs ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept_ ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid rdseed adx smap clflushopt clwb intel_pt sha_ni xsaveopt xsavec xgetbv1 xsaves split_lock_detect avx_vnni dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp hwp_pkg_req hfi umip pku ospke waitpkg gfni vaes vpclmulqdq tme rdpid movdiri movdir64b fsrm md_clear serialize pconfig arch_lbr ibt flush_l1d arch_capabilities Virtualization features: Virtualization:VT-x Caches (sum of all): L1d: 448 KiB (12 instances) L1i: 640 KiB (12 instances) L2:9 MiB (6 instances) L3:18 MiB (1 instance) NUMA: NUMA node(s): 1 NUMA node0 CPU(s): 0-15 Vulnerabilities: Itlb multihit: Not affected L1tf: Not affected Mds: Not affected Meltdown: Not affected Mmio stale data: Not affected Retbleed: Not affected Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl Spectre v1:Mitigation; usercopy/swapgs barriers and __user pointer sanitization Spectre v2:Mitigation; Enhanced IBRS, IBPB conditional, RSB filling, PBRSB-eIBRS SW sequence Srbds: Not affected Tsx async abort: Not affected ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: chromium-browser (not installed) ProcVersionSignature: Ubuntu 6.2.0-27.28-generic 6.2.15 Uname: Linux 6.2.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Aug 29 16:47:30 2023 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2033433/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 2033433] Re: Xorg 100% CPU and frozen desktop after closing chromium
The journal and >log 2>&1 snap run --strace='-o strace' chromium --enable- logging=stderr would be very thorough if that runs fine. Thanks for testing and have a good crash! -- 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/2033433 Title: Xorg 100% CPU and frozen desktop after closing chromium Status in chromium-browser package in Ubuntu: Confirmed Bug description: chromium 118.0.5966.0 2604 latest/edge Whenever I use chromium in a video session (meet, youtube) that used hardware acceleration, for a long time (like 20min or more), and then close it, the whole desktop freezes, and the laptop fan turns on. Logging in remotely I see that Xorg is at 100% CPU. The rest of the system is operational, but nothing graphical is. Just the mouse cursor moves around. SOMETIMES, if I wait a few minutes, Xorg resumes behaving normally, and I can use the desktop again, but most of the time I have to login remotely and kill -9 xorg (plain kill won't do it). With wayland, this does not happen. This could very well be an Xorg bug, but filing here first for visibility. $ lsgpu card0Intel Alderlake_p (Gen12) drm:/dev/dri/card0 └─renderD128 $ lscpu Architecture:x86_64 CPU op-mode(s):32-bit, 64-bit Address sizes: 46 bits physical, 48 bits virtual Byte Order:Little Endian CPU(s): 16 On-line CPU(s) list: 0-15 Vendor ID: GenuineIntel Model name:12th Gen Intel(R) Core(TM) i7-1270P CPU family: 6 Model: 154 Thread(s) per core: 2 Core(s) per socket: 12 Socket(s): 1 Stepping:3 CPU(s) scaling MHz: 41% CPU max MHz: 4800, CPU min MHz: 400, BogoMIPS:4992,00 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdp e1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqd q dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave a vx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb ssbd ibrs ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept_ ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid rdseed adx smap clflushopt clwb intel_pt sha_ni xsaveopt xsavec xgetbv1 xsaves split_lock_detect avx_vnni dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp hwp_pkg_req hfi umip pku ospke waitpkg gfni vaes vpclmulqdq tme rdpid movdiri movdir64b fsrm md_clear serialize pconfig arch_lbr ibt flush_l1d arch_capabilities Virtualization features: Virtualization:VT-x Caches (sum of all): L1d: 448 KiB (12 instances) L1i: 640 KiB (12 instances) L2:9 MiB (6 instances) L3:18 MiB (1 instance) NUMA: NUMA node(s): 1 NUMA node0 CPU(s): 0-15 Vulnerabilities: Itlb multihit: Not affected L1tf: Not affected Mds: Not affected Meltdown: Not affected Mmio stale data: Not affected Retbleed: Not affected Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl Spectre v1:Mitigation; usercopy/swapgs barriers and __user pointer sanitization Spectre v2:Mitigation; Enhanced IBRS, IBPB conditional, RSB filling, PBRSB-eIBRS SW sequence Srbds: Not affected Tsx async abort: Not affected ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: chromium-browser (not installed) ProcVersionSignature: Ubuntu 6.2.0-27.28-generic 6.2.15 Uname: Linux 6.2.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Aug 29 16:47:30 2023 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2033433/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 2035220] Re: cve-2023-4863
** Changed in: chromium-browser (Ubuntu)
Status: New => In Progress
** Changed in: chromium-browser (Ubuntu)
Importance: Undecided => Critical
** Changed in: chromium-browser (Ubuntu)
Assignee: (unassigned) => Nathan Teodosio (nteodosio)
--
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/2035220
Title:
cve-2023-4863
Status in chromium-browser package in Ubuntu:
In Progress
Status in libwebp package in Ubuntu:
New
Status in chromium package in Debian:
New
Status in libwebp package in Debian:
New
Bug description:
[$NA][1479274] Critical CVE-2023-4863: Heap buffer overflow in WebP. Reported
by Apple Security Engineering and Architecture (SEAR) and The Citizen Lab at
The University of Torontoʼs Munk School on 2023-09-06
https://chromereleases.googleblog.com/2023/09/stable-channel-update-for-desktop_11.html
high profile remote vulnerability
themusicgod1@eva1:~$ apt-cache policy chromium-browser
chromium-browser:
Installed: 1:85.0.4183.83-0ubuntu2.22.04.1
Candidate: 1:85.0.4183.83-0ubuntu2.22.04.1
Version table:
current available snap:
chromium 116.0.5845.179
fix is in:
chromium 116.0.5845.187
ubuntu: 22.04.3 LTS jammy
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: chromium-browser 1:85.0.4183.83-0ubuntu2.22.04.1
ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
Uname: Linux 6.2.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 12 08:38:06 2023
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/sda2 ext4 228G 162G 55G 75% /
tmpfs tmpfs 3.9G 66M 3.8G 2% /dev/shm
/dev/sda2 ext4 228G 162G 55G 75% /
InstallationDate: Installed on 2017-04-18 (2337 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: MSI MS-7994
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic
root=UUID=333c5e4f-3f61-4abf-b950-f19431c843d6 ro text
Snap.Changes: no changes found
Snap.ChromeDriverVersion: ChromeDriver 116.0.5845.179
(17ff023f3eb4f6883321db9399bfc65560ef84a9-refs/branch-heads/5845@{#1745})
Snap.ChromiumVersion: Chromium 116.0.5845.179 snap
SourcePackage: chromium-browser
UpgradeStatus: Upgraded to jammy on 2023-06-14 (89 days ago)
dmi.bios.date: 12/16/2016
dmi.bios.release: 5.12
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5.80
dmi.board.asset.tag: Default string
dmi.board.name: H110M GAMING (MS-7994)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr5.80:bd12/16/2016:br5.12:svnMSI:pnMS-7994:pvr1.0:rvnMSI:rnH110MGAMING(MS-7994):rvr1.0:cvnMSI:ct3:cvr1.0:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: MS-7994
dmi.product.sku: Default string
dmi.product.version: 1.0
dmi.sys.vendor: MSI
mtime.conffile..etc.apport.crashdb.conf: 2020-06-07T21:16:26.397404
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2035220/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2004532] Re: Hardware acceleration broken for amdgpu/mesa in snap
Marking Firefox as fix released as well since now Firefox is on core22 and that was confirmed in earlier comments to solve the problem. Please reset if observed otherwise. -- 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/2004532 Title: Hardware acceleration broken for amdgpu/mesa in snap Status in ubuntu-spotify-app: New Status in chromium-browser package in Ubuntu: Fix Released Status in firefox package in Ubuntu: Fix Released Bug description: Possible, proposed solutions Option 1: Please install from these channels and report back with success or failure. snap refresh --channel candidate/core22 firefox Option 2: chromium --ozone-platform=wayland MOZ_ENABLE_WAYLAND=1 firefox If nothing works, it is possible around the issue by disabling hardware acceleration. Original bug report --- Snap packages which use hardware accelerated graphics are broken after the last routine system upgrade via apt. My system is using AMD Radeon RX 5500 XT graphics card from ASUS, with stock amdgpu kernel drivers. Two snap packages which are now unusable are Mozilla Firefox and Chromium browsers. Both display animated speckled color garbage inside their windows, overlayed with the correct image. Disabling hardware acceleration in the settings for the snap version of Firefox fixed it. Also, Firefox version installed from the original Mozilla tarball into /opt/ works just fine with the acceleration enabled on the same system, as well as glmark2 benchmark. Looks like the issue is only affecting snap packages. $ snap list firefox chromium Name Version Rev Tracking Publisher Notes chromium 109.0.5414.119 2295 latest/stable canonical✓ - firefox 109.0.1-1 2311 latest/stable mozilla✓- $ dpkg -l snapd|grep ^ii ii snapd 2.58+22.10 amd64Daemon and tooling that enable snap packages $ dpkg -l mesa\* | grep ^ii ii mesa-utils8.5.0-1 amd64Miscellaneous Mesa utilities -- symlinks ii mesa-utils-bin:amd64 8.5.0-1 amd64Miscellaneous Mesa utilities -- native applications ii mesa-va-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VA-API video acceleration drivers ii mesa-vdpau-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VDPAU video acceleration drivers ii mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa Vulkan graphics drivers $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.10 Release:22.10 Codename: kinetic $ uname -a Linux xx 5.19.0-29-generic #30-Ubuntu SMP PREEMPT_DYNAMIC Wed Jan 4 12:14:09 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: snap (not installed) ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Feb 1 22:55:48 2023 InstallationDate: Installed on 2020-08-02 (913 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: snap UpgradeStatus: Upgraded to kinetic on 2023-02-02 (0 days ago) --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE DRM.card0-DP-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAebQd34yoBAAQcAQS1PCJ4nz4xrlBHrCcMUFQhCABxQIGAgcCpwNHAgQABAQEBTdAAoPBwPoAwIGUMWFQhAAAaKGgAoPBwPoAIkGUMWFQhAAAa/QAwPYeHOAEKICAgICAg/ABMRyBIRFIgNEsKICAgAfsCAxlxRJAEAwEjCQcHgwEAAOMFwADjBgUBAjqAGHE4LUBYLEUAWFQhAAAeVl4AoKCgKVAwIDUAWFQhAAAaKQ== modes: 3840x2160 3840x2160 3840x2160 3840x2160 3840x2160 2560x1440 1920x1200 1920x1080 1920x1080 1920x1080 1600x1200 1680x1050 1600x900 1280x1024 1440x900 1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 800x600 720x480 720x480 640x480 640x480 640x480 DRM.card0-DP-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-DP-3: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DiskUsage: Filesystem Type Size Used Avail Use% Mounted on /dev/nvme0n1p2 ext4 916G 222G 648G 26% / tmpfs tmpfs 16G 0 16G 0% /dev/shm /dev/nvme0n1p2 ext4 916G 222G 648G 26% / DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2020-08-02 (914 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" -
Re: [Desktop-packages] [Bug 2004532] Re: Hardware acceleration broken for amdgpu/mesa in snap
Santiago, Spotify is proprietary, there is nothing for us to do. You have to request them to update their base from core20 to core22. According to 'snap info spotify', their contact link is https://community.spotify.com/t5/Desktop-Linux/bd-p/desktop_linux. ** No longer affects: snapd (Ubuntu) ** Changed in: firefox (Ubuntu) Status: Confirmed => Fix Released -- 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/2004532 Title: Hardware acceleration broken for amdgpu/mesa in snap Status in ubuntu-spotify-app: New Status in chromium-browser package in Ubuntu: Fix Released Status in firefox package in Ubuntu: Fix Released Bug description: Possible, proposed solutions Option 1: Please install from these channels and report back with success or failure. snap refresh --channel candidate/core22 firefox Option 2: chromium --ozone-platform=wayland MOZ_ENABLE_WAYLAND=1 firefox If nothing works, it is possible around the issue by disabling hardware acceleration. Original bug report --- Snap packages which use hardware accelerated graphics are broken after the last routine system upgrade via apt. My system is using AMD Radeon RX 5500 XT graphics card from ASUS, with stock amdgpu kernel drivers. Two snap packages which are now unusable are Mozilla Firefox and Chromium browsers. Both display animated speckled color garbage inside their windows, overlayed with the correct image. Disabling hardware acceleration in the settings for the snap version of Firefox fixed it. Also, Firefox version installed from the original Mozilla tarball into /opt/ works just fine with the acceleration enabled on the same system, as well as glmark2 benchmark. Looks like the issue is only affecting snap packages. $ snap list firefox chromium Name Version Rev Tracking Publisher Notes chromium 109.0.5414.119 2295 latest/stable canonical✓ - firefox 109.0.1-1 2311 latest/stable mozilla✓- $ dpkg -l snapd|grep ^ii ii snapd 2.58+22.10 amd64Daemon and tooling that enable snap packages $ dpkg -l mesa\* | grep ^ii ii mesa-utils8.5.0-1 amd64Miscellaneous Mesa utilities -- symlinks ii mesa-utils-bin:amd64 8.5.0-1 amd64Miscellaneous Mesa utilities -- native applications ii mesa-va-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VA-API video acceleration drivers ii mesa-vdpau-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VDPAU video acceleration drivers ii mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa Vulkan graphics drivers $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.10 Release:22.10 Codename: kinetic $ uname -a Linux xx 5.19.0-29-generic #30-Ubuntu SMP PREEMPT_DYNAMIC Wed Jan 4 12:14:09 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: snap (not installed) ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Feb 1 22:55:48 2023 InstallationDate: Installed on 2020-08-02 (913 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: snap UpgradeStatus: Upgraded to kinetic on 2023-02-02 (0 days ago) --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE DRM.card0-DP-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAebQd34yoBAAQcAQS1PCJ4nz4xrlBHrCcMUFQhCABxQIGAgcCpwNHAgQABAQEBTdAAoPBwPoAwIGUMWFQhAAAaKGgAoPBwPoAIkGUMWFQhAAAa/QAwPYeHOAEKICAgICAg/ABMRyBIRFIgNEsKICAgAfsCAxlxRJAEAwEjCQcHgwEAAOMFwADjBgUBAjqAGHE4LUBYLEUAWFQhAAAeVl4AoKCgKVAwIDUAWFQhAAAaKQ== modes: 3840x2160 3840x2160 3840x2160 3840x2160 3840x2160 2560x1440 1920x1200 1920x1080 1920x1080 1920x1080 1600x1200 1680x1050 1600x900 1280x1024 1440x900 1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 800x600 720x480 720x480 640x480 640x480 640x480 DRM.card0-DP-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-DP-3: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DiskUsage: Filesystem Type Size Used Avail Use% Mounted on /dev/nvme0n1p2 ext4 916G 222G 648G 26% / tmpfs tmpfs 16G 0 16G 0%
[Desktop-packages] [Bug 2035220] Re: cve-2023-4863
For your information, Chromium is now in 116.0.5845.187 in x86, and
should be in ARM too tomorrow.
--
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/2035220
Title:
cve-2023-4863
Status in chromium-browser package in Ubuntu:
In Progress
Status in firefox package in Ubuntu:
New
Status in firefox-esr package in Ubuntu:
New
Status in libwebp package in Ubuntu:
New
Status in thunderbird package in Ubuntu:
New
Status in chromium package in Debian:
New
Status in libwebp package in Debian:
New
Bug description:
[$NA][1479274] Critical CVE-2023-4863: Heap buffer overflow in WebP. Reported
by Apple Security Engineering and Architecture (SEAR) and The Citizen Lab at
The University of Torontoʼs Munk School on 2023-09-06
https://chromereleases.googleblog.com/2023/09/stable-channel-update-for-desktop_11.html
high profile remote vulnerability
themusicgod1@eva1:~$ apt-cache policy chromium-browser
chromium-browser:
Installed: 1:85.0.4183.83-0ubuntu2.22.04.1
Candidate: 1:85.0.4183.83-0ubuntu2.22.04.1
Version table:
current available snap:
chromium 116.0.5845.179
fix is in:
chromium 116.0.5845.187
ubuntu: 22.04.3 LTS jammy
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: chromium-browser 1:85.0.4183.83-0ubuntu2.22.04.1
ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
Uname: Linux 6.2.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 12 08:38:06 2023
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/sda2 ext4 228G 162G 55G 75% /
tmpfs tmpfs 3.9G 66M 3.8G 2% /dev/shm
/dev/sda2 ext4 228G 162G 55G 75% /
InstallationDate: Installed on 2017-04-18 (2337 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: MSI MS-7994
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic
root=UUID=333c5e4f-3f61-4abf-b950-f19431c843d6 ro text
Snap.Changes: no changes found
Snap.ChromeDriverVersion: ChromeDriver 116.0.5845.179
(17ff023f3eb4f6883321db9399bfc65560ef84a9-refs/branch-heads/5845@{#1745})
Snap.ChromiumVersion: Chromium 116.0.5845.179 snap
SourcePackage: chromium-browser
UpgradeStatus: Upgraded to jammy on 2023-06-14 (89 days ago)
dmi.bios.date: 12/16/2016
dmi.bios.release: 5.12
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5.80
dmi.board.asset.tag: Default string
dmi.board.name: H110M GAMING (MS-7994)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr5.80:bd12/16/2016:br5.12:svnMSI:pnMS-7994:pvr1.0:rvnMSI:rnH110MGAMING(MS-7994):rvr1.0:cvnMSI:ct3:cvr1.0:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: MS-7994
dmi.product.sku: Default string
dmi.product.version: 1.0
dmi.sys.vendor: MSI
mtime.conffile..etc.apport.crashdb.conf: 2020-06-07T21:16:26.397404
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2035220/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2011281]
In bug description: 1> when I went to use my saved passwords in chromium today, I found that they were absent. In your last comment: 2> chromium continues to be able to *use* my saved passwords. But I don't know where they're actually saved Which one is correct/up to date? Likewise for 3> I found that there was a ~/snap/chromium/common/chromium/Default/Login Data.old containing all of my passwords, and a ~/snap/chromium/common/chromium/Default/Login Data containing a single password entry and 4> But I don't know where they're actually saved It looks impossible that Chromium is accessing passwords from 'Login Data.old'; there is no longer any reference to that, anywhere, so I think quote 3 might not be up to date. Depending on the situation you could try --password-store=basic, but given the already buggy circumstances, better have those configuration files backed up. Without a reproducible case and access to those data files, which of course you must not share as it contains passwords, this is hard to debug. -- 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/2011281 Title: chromium snap upgrade "lost" my passwords Status in chromium-browser package in Ubuntu: New Bug description: On upgrade to chromium snap revision 2333 (now since upgraded to 2367), I received a window with a notice about password migration: "Password storage via the Gnome keyring has been fixed, but for it to work, you have to rename your old ~/snap/chromium/common/chromium/Default/Login Data file so that a new, working one can replace it." I don't remember if I did this or not. However, when I went to use my saved passwords in chromium today, I found that they were absent. Tracking down the data in the chromium profile, I found that there was a ~/snap/chromium/common/chromium/Default/Login Data.old containing all of my passwords, and a ~/snap/chromium/common/chromium/Default/Login Data containing a single password entry for a site that I happened to have created a new login for in the past few days. That's not a very user-friendly experience on upgrade. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2011281/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2007652] Re: [snap] PWA don't launch as applications, just another chromium window
** This bug is no longer a duplicate of bug 1732482 [snap] doesn't properly save desktop files for "create shortcuts" action -- 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/2007652 Title: [snap] PWA don't launch as applications, just another chromium window Status in chromium-browser package in Ubuntu: Confirmed Bug description: I have recently converted from deb to snap package of chromium and progressive web applications (PWAs) launch just as another window of chromium and are not recognized as separate application by the window manager (for example when switching using Super+Tab) or dock (grouped under chromium windows). This is either a regression of the snap package vs deb or ubuntu 20.04 vs ubuntu 18.04 (I am not able to differentiate between these two since both happened together). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2007652/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2035603] Re: Duplicity 1.2.2-1 fails to build from source
** Description changed: https://launchpadlibrarian.net/685130555/buildlog_ubuntu-mantic- amd64.duplicity_1.2.2-1_BUILDING.txt.gz + + For the record this builds fine with the latest upstream release + setup.py so I'm not poking them. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/2035603 Title: Duplicity 1.2.2-1 fails to build from source Status in duplicity package in Ubuntu: Triaged Bug description: https://launchpadlibrarian.net/685130555/buildlog_ubuntu-mantic- amd64.duplicity_1.2.2-1_BUILDING.txt.gz For the record this builds fine with the latest upstream release setup.py so I'm not poking them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/2035603/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2007652] Re: [snap] PWA don't launch as applications, just another chromium window
With the help of 3v1n0 it's confirmed that this is Mutter interpretation of a sandboxed application. Whether this is a bug is then a matter of opinion and actually complicated[1]. You may need to convince Gnome maintainers about it or use another desktop environment. [1] https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/84 ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu) Status: New => Opinion ** Changed in: chromium-browser (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2007652 Title: [snap] PWA don't launch as applications, just another chromium window Status in chromium-browser package in Ubuntu: Invalid Status in mutter package in Ubuntu: Opinion Bug description: I have recently converted from deb to snap package of chromium and progressive web applications (PWAs) launch just as another window of chromium and are not recognized as separate application by the window manager (for example when switching using Super+Tab) or dock (grouped under chromium windows). This is either a regression of the snap package vs deb or ubuntu 20.04 vs ubuntu 18.04 (I am not able to differentiate between these two since both happened together). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2007652/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2035360] Re: GPU hangs in SketchUp on Intel gen12 due to outdated MESA library
The Gnome snap has been built with a newer Mesa. Could you try snap refresh --candidate gnome-42-2204 and then start the browser? Does the issue go away? -- 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/2035360 Title: GPU hangs in SketchUp on Intel gen12 due to outdated MESA library Status in Mesa: New Status in chromium-browser package in Ubuntu: New Status in firefox package in Ubuntu: New Bug description: When opening a SketchUp model (example: https://app.sketchup.com/share/tc/europe/9jWfPS5lgN8?stoken=KYi8KrAR6g3gv6OqLAKNEEMrQHLOA7jd8oV20HmBbHrZqyPRPmG1QlPurYkJnuw_) in Firefox or Chromium, after ~5 seconds, the SketchUp logo freezes for ~4 seconds, and we see a blank page. The logs show the GPU hang and browser rendering context failed to initialise. This has 100% reproducibility on my 12-gen GPU. On this system with Ubuntu 23.04, I have always seen a GPU hang with the stock Ubuntu kernel or mainline. Log files as attachment - the output of 'dmesg' is at https://quora.org/OJnlVgn4xZ/dmesg.txt - the output of 'dmesg' with kernel boot args 'drm.debug=0x1e log_buf_len=16M' is at https://quora.org/OJnlVgn4xZ/dmesg-debug.txt - the output of /sys/class/drm/card0/error is at https://quora.org/OJnlVgn4xZ/i915-error.txt Since I was able to cause failure uncontained to the rendering process when performing this 5-8 times, there is an argument that this is a security (DoS) issue, though I'll let someone else make a judgement. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2035360/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2039460] [NEW] Please merge network-manager-applet 1.34.0-1 from Debian unstable
Public bug reported: Builds successfully in Mantic. ** Affects: network-manager-applet (Ubuntu) Importance: Wishlist Status: Confirmed ** Patch added: "nma.diff" https://bugs.launchpad.net/bugs/2039460/+attachment/5709932/+files/nma.diff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/2039460 Title: Please merge network-manager-applet 1.34.0-1 from Debian unstable Status in network-manager-applet package in Ubuntu: Confirmed Bug description: Builds successfully in Mantic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/2039460/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2039187] v3
The last patch wouldn't build in Jammy due to older Glib, this one builds there too (attached build log in Jammy). ** Patch added: "xdg-deskop-portal-gtk3.diff" https://bugs.launchpad.net/bugs/2039187/+attachment/5709124/+files/xdg-deskop-portal-gtk3.diff ** Attachment added: "jammy-xdg.log" https://bugs.launchpad.net/bugs/2039187/+attachment/5709125/+files/jammy-xdg.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal-gtk in Ubuntu. https://bugs.launchpad.net/bugs/2039187 Title: Thunderbird doesn't accept URI attachments anymore Status in xdg-desktop-portal-gtk package in Ubuntu: Confirmed Bug description: The desktop portal constructs an mailto: url with an attachment= but thunderbird upstream explicitly decided to not allow adding files from an URL for security reasons. One can still use the -compose option though, as this patch does. Test case - * Install the proposed package. * Log out and back in. * Set Thunberbird as default client in Gnome Control Panel. * Open Nautilus and try to attach two files to the same email. They can be creatively named, it should not break on weird characters. * Thunderbird should open with the corresponding files attached. * [For regression testing] Set Evolution as the default. * Open Nautilus and try to attach two files to the same email. They can be creatively named, it should not break on weird characters. It only attaches one file, this is however not a regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/2039187/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1996267] Re: [snap] Doesn't store encrypted passwords unless interface is connected
> According to the chromium documented cited, this is wrong. Maybe it's a different way of interpreting the terminology. If it applied a rot13 to your password (of course that would be very stupid but it's just for the sake of the argument) and stored that in a file, I could say that it is stored in plain text and that however they aren't stored in the clear, i.e. they are not stored exactly as they are, there is some sort of transformation*, trivial or not, applied to them. Otherwise, you could prove me wrong by pointing to the file where you see Chromium password stored in the clear. > For many people an autoconnect for the password-manager-service would probably solve this Then you're welcome to follow up in [1], in which the automatic connection of the interface has been declined. I cannot override the policy reviewers' decision. *I think the transformation is the one Evan Carroll describes in LP:2038875. [1] https://forum.snapcraft.io/t/auto-connecting-the-cups-control-and- password-manager-service-interfaces-for-the-chromium-snap/4592/6 -- 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/1996267 Title: [snap] Doesn't store encrypted passwords unless interface is connected Status in chromium-browser package in Ubuntu: Confirmed Bug description: In the Snap package of Chromium, Chromium is not protecting passwords with gnome-keyring (or KWallet). As a result, copying the Chromium profile directory from the snap directory gives access to all stored passwords. This is a HIGH security risk. Regular users who are used to storing their passwords in browsers are probably unaware of this. Note that Chromium is started with the command line option “--password-store=basic”. This hack should never have been released to the public. The Chromium documentation states: > --password-store=basic (to use the plain text store) https://chromium.googlesource.com/chromium/src/+/master/docs/linux/password_storage.md To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1996267/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1996267] Re: [snap] Doesn't store encrypted passwords unless interface is connected
> What is there to prove? The documentation *literally* says it is plain > text. The documentation isn't the code that is executed. The only source of truth is code and the proof is in the pudding, namely execution. However that was not my point at all, you didn't read what I said carefully enough. You can prove me wrong easily, grep the Chromium state files (or the whole filesystem if you want) for your password and see if it returns something. Or else show me the plain text file where it is stored. Answer: It is Now I've already investigated the issue and the file where your credentials are stored is: ---> % less "$HOME/snap/chromium/common/chromium/Default/Login Data" ".../Login Data" may be a binary file. See it anyway? % file "$HOME/snap/chromium/common/chromium/Default/Login Data" .../Login Data: SQLite 3.x database <--- So much for plain text[1]. You could even go ahead and SQL dump it and see if you could find the password in the clear. I didn't. Which of course does not mean it is not easy to retrieve it. > Also: Any attacker can just copy the entire browser profile to another > machine and then access the passwords. So he does not have to care about > the implementation details of the password storage at all. > > On the other side, normal Chrome/Chromium (without Snap and this command > line argument) is using Gnome Keyring to protect the passwords. In that > case, the attacker would need the login password or a equivalent secret > from PAM and friends. Right. But as I said this was declined by policy reviewers and you are welcome to follow up in that link. [1] https://en.wikipedia.org/wiki/Plain_text -- 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/1996267 Title: [snap] Doesn't store encrypted passwords unless interface is connected Status in chromium-browser package in Ubuntu: Confirmed Bug description: In the Snap package of Chromium, Chromium is not protecting passwords with gnome-keyring (or KWallet). As a result, copying the Chromium profile directory from the snap directory gives access to all stored passwords. This is a HIGH security risk. Regular users who are used to storing their passwords in browsers are probably unaware of this. Note that Chromium is started with the command line option “--password-store=basic”. This hack should never have been released to the public. The Chromium documentation states: > --password-store=basic (to use the plain text store) https://chromium.googlesource.com/chromium/src/+/master/docs/linux/password_storage.md To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1996267/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2038875] Re: Snap uses hardcoded key and salt for password and cookie encryption
*** This bug is a duplicate of bug 1996267 *** https://bugs.launchpad.net/bugs/1996267 That is a good target for a duplicate, marking it accordingly, thanks for the heads-up. ** This bug has been marked a duplicate of bug 1996267 [snap] Doesn't store encrypted passwords unless interface is connected -- 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/2038875 Title: Snap uses hardcoded key and salt for password and cookie encryption Status in chromium-browser package in Ubuntu: Won't Fix Bug description: A working Ubuntu install includes Gnome which includes the gnome- keyring. The snap version of Ubuntu does not make use of it. On an install of Debian with Gnome, the key ring is used. However, with Ubuntu everything is encrypted with the static key of peanuts and the salt of saltysalt, and openly accessible as sqlite databases in ~/snap/chromium/common/chromium, including passwords from the browser and the cookies. This should probably be fixed. If a laptop is physically compromised it's trivial to decrypt this with a tool like xbrowser. You can verify that gnome-libcrypt isn't chosen by default with --enable-logging=stderr --v=1 redirect stderr to a log and look for Crypt. You can see /why/ gnome-libcrypt isn't chosen with chromium --password-store=gnome-libcrypt --enable-logging=stderr --v=1 and again looking for messages with Crypt. I don't think this is a vulnerability per se, Chrome ships in Debian with the ability to use a basic store too. But it's an undesirable configuration and a regression from Debian when it's run on a platform with gnome and libsecret, and only doesn't work because of snap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2038875/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2007702] Re: Deb version numbering is misleading
I'm proposing changing the version number from 1:85.0.4183.83-0ubuntu3 to 2:1+snap, similar to what Firefox does. ** Description changed: For Ubuntu >= Focal the transitional debs are frozen at the version number 1:85... - This might make one think[1] that it will install a critically outdated - Chromium while it does not, because it installs the snap. + This might make one think[1][2] that it will install a critically + outdated Chromium while it does not, because it installs the snap. - [1] https://answers.launchpad.net/ubuntu/+source/chromium- - browser/+question/702591 + [1] https://answers.launchpad.net/ubuntu/+source/chromium-browser/+question/702591 + [2] https://askubuntu.com/q/1420925 ** Patch added: "chromium.diff" https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2007702/+attachment/5710244/+files/chromium.diff -- 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/2007702 Title: Deb version numbering is misleading Status in chromium-browser package in Ubuntu: Triaged Bug description: For Ubuntu >= Focal the transitional debs are frozen at the version number 1:85... This might make one think[1][2] that it will install a critically outdated Chromium while it does not, because it installs the snap. [1] https://answers.launchpad.net/ubuntu/+source/chromium-browser/+question/702591 [2] https://askubuntu.com/q/1420925 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2007702/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2038727] Re: Chromium snap theme parsing error
Great! Thanks for testing. This will slowly flow into other channels. -- 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/2038727 Title: Chromium snap theme parsing error Status in chromium-browser package in Ubuntu: Fix Committed Bug description: Chromium Version 117.0.5938.149 (Official Build) snap (64-bit) not following my GTK theme. Starting the Chromium snap from the terminal yields a theme parsing error: (chrome:95638): Gtk-WARNING **: 11:01:12.220: Theme parsing error: gtk.css:1:0: Failed to import: Error opening file /home/aej/.local/share/themes/Adwaita_modified/gtk-3.0/gtk.css: Permission denied Previous versions of the Chromium snap have not had this problem. Debian 11 + XFCE. I have been running the chromium snap for about two years without an issue like this on this system. I have reverted to the previous version of the chromium snap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2038727/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 2007702] Re: Deb version numbering is misleading
Hi Lukas, thanks for having a look! > But I wonder if we should rather change the version number to > "2:1snap1-0ubuntu1", in order to use a similar format as we have on > Firefox (LP: #1892724)? What do you think? So, my hunch reaction to that scheme is "god, are all those numbers really meaningful and necessary?" Being this is a package that installs a snap, with all the upstream and almost all downstream changes handled in the snap, I couldn't think in a way we would benefit from more than one "free" (i.e., not epoch) number, and that is why I suggested a simpler scheme — just for the principle of parcimony's sake. Now, there can definitely be shortsight from my side, as I'm usually only bumping version numbers, not reworking or creating them. At any rate, both schemes solve the problem of misleading users, and I'm glad to change to either. -- 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/2007702 Title: Deb version numbering is misleading Status in chromium-browser package in Ubuntu: Triaged Bug description: For Ubuntu >= Focal the transitional debs are frozen at the version number 1:85... This might make one think[1][2] that it will install a critically outdated Chromium while it does not, because it installs the snap. [1] https://answers.launchpad.net/ubuntu/+source/chromium-browser/+question/702591 [2] https://askubuntu.com/q/1420925 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2007702/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967632] Re: [snap] apparmor denied when trying to load pkcs11 module for smart card authentication
Parallel install is OK, I committed the fix for that weeks ago... In the wrong branch. (: Rebuilt now, with my limited connection I cannot donwload it to test it, but I tested by making local changes by unsquashing and trying the snap. Can you please give it another try and let me know? The revision number must be 2671. Thanks for the help testing. -- 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/1967632 Title: [snap] apparmor denied when trying to load pkcs11 module for smart card authentication Status in Mozilla Firefox: Confirmed Status in chromium-browser package in Ubuntu: In Progress Status in firefox package in Ubuntu: Triaged Bug description: I use a smart card to access government sites. I have that working in firefox and chrome on ubuntu impish, and gave jammy a try, but there firefox won't load the library, giving me a generic error. dmesg, however, shows this apparmor denied message: [sáb abr 2 17:32:27 2022] audit: type=1400 audit(1648931547.646:115): apparmor="DENIED" operation="file_mmap" profile="snap.firefox.firefox" name="/run/user/1000/doc/e0bac853/libaetpkss.so.3.5.4112" pid=3680 comm="firefox" requested_mask="m" denied_mask="m" fsuid=1000 ouid=0 Note also the path, that's not what I typed into the firefox dialog box. I have the .so copied to /usr/lib/x86_64-linux-gnu/libaetpkss.so.3.5.4112, and that's what I typed in when prompted for its path by firefox. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 2 17:34:09 2022 InstallationDate: Installed on 2022-03-20 (13 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220319) Snap.Changes: no changes found SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1967632/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 2039460] Re: Please merge network-manager-applet 1.34.0-1 from Debian unstable
Thanks for having a look, Bryce. I addressed your points; the build is [2]. Should I always propose the debdiff with the release name instead of UNRELEASED even though it is unreleased at that given point? I'm used not to, but maybe that's something particular of Gnome[1]. [1] https://wiki.debian.org/Gnome/Git#UNRELEASED [2] https://launchpad.net/~nteodosio/+archive/ubuntu/rebuilds/+build/26952466 ** Patch added: "nma2.diff" https://bugs.launchpad.net/bugs/2039460/+attachment/5715233/+files/nma2.diff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/2039460 Title: Please merge network-manager-applet 1.34.0-1 from Debian unstable Status in network-manager-applet package in Ubuntu: Confirmed Bug description: Builds successfully in Mantic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/2039460/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2042077] [NEW] Dark mode only works for some GTK windows
Public bug reported:
Works for nautilus, gnome-{power-statistics,disks}.
Doesn't work for gnome-{control-center,text-editor,calculator,calendar},
which remain on light mode.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: gnome-shell 45.0-1ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
Date: Tue Oct 31 10:52:00 2023
DisplayManager:
InstallationDate: Installed on 2022-05-16 (533 days ago)
InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64
(20220419)
RelatedPackageVersions: mutter-common 45.0-3ubuntu3
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to mantic on 2023-01-17 (287 days ago)
** Affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug mantic
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/2042077
Title:
Dark mode only works for some GTK windows
Status in gnome-shell package in Ubuntu:
New
Bug description:
Works for nautilus, gnome-{power-statistics,disks}.
Doesn't work for gnome-{control-center,text-
editor,calculator,calendar}, which remain on light mode.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: gnome-shell 45.0-1ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
Date: Tue Oct 31 10:52:00 2023
DisplayManager:
InstallationDate: Installed on 2022-05-16 (533 days ago)
InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64
(20220419)
RelatedPackageVersions: mutter-common 45.0-3ubuntu3
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to mantic on 2023-01-17 (287 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2042077/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2042077] Re: Dark mode only works for some GTK windows
ADW_COLOR_SCHEME_FORCE_DARK=. fixes it but only in a Gnome environment.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/2042077
Title:
Dark mode only works for some GTK windows
Status in gnome-shell package in Ubuntu:
New
Bug description:
Works for nautilus, gnome-{power-statistics,disks}.
Doesn't work for gnome-{control-center,text-
editor,calculator,calendar}, which remain on light mode.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: gnome-shell 45.0-1ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
Date: Tue Oct 31 10:52:00 2023
DisplayManager:
InstallationDate: Installed on 2022-05-16 (533 days ago)
InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64
(20220419)
RelatedPackageVersions: mutter-common 45.0-3ubuntu3
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to mantic on 2023-01-17 (287 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2042077/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2042077] Screen shot
** Attachment added: "Screenshot from 2023-10-31
10-47-43.png"
https://bugs.launchpad.net/bugs/2042077/+attachment/5714608/+files/Screenshot%20from%202023-10-31%0A%2010-47-43.png
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/2042077
Title:
Dark mode only works for some GTK windows
Status in gnome-shell package in Ubuntu:
New
Bug description:
Works for nautilus, gnome-{power-statistics,disks}.
Doesn't work for gnome-{control-center,text-
editor,calculator,calendar}, which remain on light mode.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: gnome-shell 45.0-1ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
Date: Tue Oct 31 10:52:00 2023
DisplayManager:
InstallationDate: Installed on 2022-05-16 (533 days ago)
InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64
(20220419)
RelatedPackageVersions: mutter-common 45.0-3ubuntu3
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to mantic on 2023-01-17 (287 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2042077/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2040290] Re: [Snap] PWA icon not shown in Ubuntu Dock
Thanks for the report. Do you recognize your issue in LP:2007652? If you right click and add to favorites, does the icon show on the dock? ** Changed in: chromium-browser (Ubuntu) Status: New => Triaged -- 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/2040290 Title: [Snap] PWA icon not shown in Ubuntu Dock Status in chromium-browser package in Ubuntu: Triaged Bug description: When I install a Progressive Web App (PWA) using the Chromium Browser (Snap 118.0.5993.88) the app gets added correctly to the application list (the one that appears when you press the Windows key twice) from which it can be opened. However, when you open the application it is not shown as a separate application in the Ubuntu Dock (on the left) but seems like a regular second window of Chromium. Additionally, the icon of the PWA is not shown. I added a screenshot to visualize my problem exemplarily using Spotify. This makes switching between multiple PWAs a lot more complicated, since you have to iterate through all open PWAs and other Chromium windows. I guess this is a bug, because on my Manjaro-Gnome system Chromium PWAs appear as separate applications with the correct icon in the dock (Dash-To-Dock extension). I'm using Ubuntu 23.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2040290/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2040290] Re: [Snap] PWA icon not shown in Ubuntu Dock
*** This bug is a duplicate of bug 2007652 *** https://bugs.launchpad.net/bugs/2007652 Yeah sorry about that, this is actually the way Gnome Shell interprets sandboxed applications — other desktop environments have the desired behavior. ** This bug has been marked a duplicate of bug 2007652 [snap] PWA don't launch as applications, just another chromium window -- 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/2040290 Title: [Snap] PWA icon not shown in Ubuntu Dock Status in chromium-browser package in Ubuntu: Triaged Bug description: When I install a Progressive Web App (PWA) using the Chromium Browser (Snap 118.0.5993.88) the app gets added correctly to the application list (the one that appears when you press the Windows key twice) from which it can be opened. However, when you open the application it is not shown as a separate application in the Ubuntu Dock (on the left) but seems like a regular second window of Chromium. Additionally, the icon of the PWA is not shown. I added a screenshot to visualize my problem exemplarily using Spotify. This makes switching between multiple PWAs a lot more complicated, since you have to iterate through all open PWAs and other Chromium windows. I guess this is a bug, because on my Manjaro-Gnome system Chromium PWAs appear as separate applications with the correct icon in the dock (Dash-To-Dock extension). I'm using Ubuntu 23.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2040290/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2032992] Re: [snap] chromium snap does not allow to read symlinks to /usr/share/javascript
** Bug watch added: Mozilla Bugzilla #1849961 https://bugzilla.mozilla.org/show_bug.cgi?id=1849961 ** Also affects: chromium-browser via https://bugzilla.mozilla.org/show_bug.cgi?id=1849961 Importance: Unknown Status: Unknown ** No longer affects: chromium-browser ** Also affects: firefox via https://bugzilla.mozilla.org/show_bug.cgi?id=1849961 Importance: Unknown Status: Unknown -- 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/2032992 Title: [snap] chromium snap does not allow to read symlinks to /usr/share/javascript Status in Mozilla Firefox: Unknown Status in chromium-browser package in Ubuntu: In Progress Status in firefox package in Ubuntu: In Progress Bug description: Steps to reproduce: 1) Install chromium snap snap install chromium 2) Install openjdk-21 documentation sudo apt install openjdk-21-doc 3) Browse API documentation chromium /usr/share/doc/openjdk-21-doc/api/index.html The search bar is inactive and dev console contains: jquery-3.6.1.min.js:1 Failed to load resource: net::ERR_FILE_NOT_FOUND $ls -l /usr/share/doc/openjdk-21-jre-headless/api/script-dir/jquery-3.6.1.min.js lrwxrwxrwx 1 root root 43 Mar 17 13:31 /usr/share/doc/openjdk-21-jre-headless/api/script-dir/jquery-3.6.1.min.js -> ../../../../javascript/jquery/jquery.min.js cat /usr/share/doc/openjdk-21-jre-headless/api/script-dir/jquery-3.6.1.min.js prints the file contents Downloaded version of chrome opens documentation with active search bar and no javascript errors /tmp/chrome/chrome /usr/share/doc/openjdk-21-doc/api/index.html Expected results: Chromium snap should be able to follow symlink into /usr/share/javascript and correctly load OpenJDK API documentation. Note: this probably should be a specific exclusion for Debian-based systems. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/2032992/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967632] Re: [snap] apparmor denied when trying to load pkcs11 module for smart card authentication
For some reason some binaries are no longer making it into the snap. :| I'm investigating... -- 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/1967632 Title: [snap] apparmor denied when trying to load pkcs11 module for smart card authentication Status in Mozilla Firefox: Confirmed Status in chromium-browser package in Ubuntu: In Progress Status in firefox package in Ubuntu: Triaged Bug description: I use a smart card to access government sites. I have that working in firefox and chrome on ubuntu impish, and gave jammy a try, but there firefox won't load the library, giving me a generic error. dmesg, however, shows this apparmor denied message: [sáb abr 2 17:32:27 2022] audit: type=1400 audit(1648931547.646:115): apparmor="DENIED" operation="file_mmap" profile="snap.firefox.firefox" name="/run/user/1000/doc/e0bac853/libaetpkss.so.3.5.4112" pid=3680 comm="firefox" requested_mask="m" denied_mask="m" fsuid=1000 ouid=0 Note also the path, that's not what I typed into the firefox dialog box. I have the .so copied to /usr/lib/x86_64-linux-gnu/libaetpkss.so.3.5.4112, and that's what I typed in when prompted for its path by firefox. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 2 17:34:09 2022 InstallationDate: Installed on 2022-03-20 (13 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220319) Snap.Changes: no changes found SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1967632/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2019045] Re: [snap] New Ubuntu font with normal weight displayed as bold in Google Docs in Chromium after upgrading to Lunar
Thanks for your input Gunnar, that might be really playing a role in the
problem.
After all, it turns out the error Andreas reported is also present when
the behavior is correct, i.e. with ubuntu-fonts-classic I get
--->
Failed to get origin+type directory: { uri:
filesystem:https://docs.google.com/persistent/docs/fonts/4iCs6KVjbNBYlgo6fQ.woff2,
storage key: { origin: https://docs.google.com, top-level site:
https://google.com, nonce: , ancestor chain bit: Same-Site } } error:-4
<---
** Changed in: chromium-browser (Ubuntu)
Importance: Medium => Low
--
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/2019045
Title:
[snap] New Ubuntu font with normal weight displayed as bold in Google
Docs in Chromium after upgrading to Lunar
Status in chromium-browser package in Ubuntu:
Triaged
Status in fonts-ubuntu package in Ubuntu:
Confirmed
Bug description:
I am experiencing a rendering regression after upgrading from Kinetic to
Lunar.
Google Docs using the Ubuntu font family are displayed incorrectly in
Chromium: the normal weight font is rendered identically to the bold weight
one, instead of being thicker than light and thinner than medium.
Printing is also affected, unless I use Google Docs' download to PDF
function, although that probably triggers a server-side rendering.
This issue does not occur in Firefox or Google Chrome.
One thing that may be relevant: if I force-refresh my test Google Doc
I see all four Ubuntu font lines initially being rendered as bold. The
light and medium lines are then re-rendered with the correct weight.
It's as if bold was the default weight and the normal variant
disappeared.
As far as I can tell I was already running Chromium 112.0.5615.49 in
Kinetic, and with Chromium being a snap I don't quite understand why
the Ubuntu series would matter.
I have also tried version 114.0.5735.16 (in latest/beta at the
moment); the symptoms are identical.
The attachments show the rendering error.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2019045/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2039460] Re: Please merge network-manager-applet 1.34.0-1 from Debian unstable
No problem, Simon, thank you for responding and sponsoring! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/2039460 Title: Please merge network-manager-applet 1.34.0-1 from Debian unstable Status in network-manager-applet package in Ubuntu: Fix Released Bug description: Builds successfully in Mantic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/2039460/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1732482] Re: [snap] doesn't properly save desktop files for "create shortcuts" action
This is supposedly fixed in edge and beta channels (x86 and ARMv8): snap refresh --edge chromium #Or snap refresh --beta chromium #And then connect the required plugs: snap connect chromium:dot-local-share-applications snap connect chromium:dot-local-share-icons Your report of whether this works or not would be very welcome. -- 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/1732482 Title: [snap] doesn't properly save desktop files for "create shortcuts" action Status in chromium-browser package in Ubuntu: Fix Committed Bug description: For chrome apps, the create shortcuts action should create desktop files but it doesn't. I suspect it has something to do with paths. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1732482/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2036647] Journal log
Yesterday I got crashes whenever I tried to maximize it or resize it. I started Ubuntu on Wayland from SDDM though. After I started it from GDM I no longer reproduce the problem, although I rebooted in between so... I didn't get a crash file in /var/crash. I attach the journal from yesterday, filtered for gnome-terminal. You can see 3 segfaults, and I think that is indeed the number of times I tried the terminal before giving up on it. ** Attachment added: "journal-b-1-grep-gnome-terminal-C3.txt" https://bugs.launchpad.net/bugs/2036647/+attachment/5702600/+files/journal-b-1-grep-gnome-terminal-C3.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/2036647 Title: gnome-terminal-server crashed with SIGSEGV in g_utf8_pointer_to_offset() Status in gnome-terminal package in Ubuntu: Confirmed Bug description: Gnome terminal just crashed, was moving pointer across window. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-terminal 3.49.92-2ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Sep 19 22:39:00 2023 ExecutablePath: /usr/libexec/gnome-terminal-server InstallationDate: Installed on 2023-09-18 (1 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230918) ProcCmdline: /usr/libexec/gnome-terminal-server SegvAnalysis: Segfault happened at: 0x7f58c3c30180 : movzbl (%rsi),%ecx PC (0x7f58c3c30180) ok source "(%rsi)" (0x5646400b2000) not located in a known VMA region (needed readable region)! destination "%ecx" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-terminal StacktraceTop: g_utf8_pointer_to_offset () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 ??? () at /lib/x86_64-linux-gnu/libvte-2.91.so.0 ??? () at /lib/x86_64-linux-gnu/libvte-2.91.so.0 ??? () at /lib/x86_64-linux-gnu/libvte-2.91.so.0 ??? () at /lib/x86_64-linux-gnu/libgtk-3.so.0 Title: gnome-terminal-server crashed with SIGSEGV in g_utf8_pointer_to_offset() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2036647/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2035360] Re: GPU hangs in SketchUp on Intel gen12 due to outdated MESA library
Sorry, I hadn't seen you already had done those tests in the linked bug report. > the chromium snap needs the updated MESA library It uses the one gnome-42-2204 exposes. If migrating to candidate didn't help, then the problem should be something else. -- 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/2035360 Title: GPU hangs in SketchUp on Intel gen12 due to outdated MESA library Status in Mesa: New Status in chromium-browser package in Ubuntu: Fix Committed Status in firefox package in Ubuntu: Fix Committed Bug description: When opening a SketchUp model (example: https://app.sketchup.com/share/tc/europe/9jWfPS5lgN8?stoken=KYi8KrAR6g3gv6OqLAKNEEMrQHLOA7jd8oV20HmBbHrZqyPRPmG1QlPurYkJnuw_) in Firefox or Chromium, after ~5 seconds, the SketchUp logo freezes for ~4 seconds, and we see a blank page. The logs show the GPU hang and browser rendering context failed to initialise. This has 100% reproducibility on my 12-gen GPU. On this system with Ubuntu 23.04, I have always seen a GPU hang with the stock Ubuntu kernel or mainline. Log files as attachment - the output of 'dmesg' is at https://quora.org/OJnlVgn4xZ/dmesg.txt - the output of 'dmesg' with kernel boot args 'drm.debug=0x1e log_buf_len=16M' is at https://quora.org/OJnlVgn4xZ/dmesg-debug.txt - the output of /sys/class/drm/card0/error is at https://quora.org/OJnlVgn4xZ/i915-error.txt Since I was able to cause failure uncontained to the rendering process when performing this 5-8 times, there is an argument that this is a security (DoS) issue, though I'll let someone else make a judgement. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2035360/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2036426] Re: gnome calculator crash on IMF server error
The problem looks to be var bodyinput = yield session.send_async (message, 1, new GLib.Cancellable()); That is not the signature of the function and it doesn't return the body input. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/2036426 Title: gnome calculator crash on IMF server error Status in gnome-calculator package in Ubuntu: New Bug description: Description: Ubuntu 23.04 Release: 23.04 gnome-calculator: Installed: 1:44.0-1ubuntu1 Candidate: 1:44.0-1ubuntu1 Version table: *** 1:44.0-1ubuntu1 500 500 http://mirror.sg.gs/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status when i tried to open the app, it crashed immediately with this in the log: ** (gnome-calculator:75655): WARNING **: 19:43:34.821: currency- provider.vala:161: Couldn't download IMF currency rate file: HTTP/2 Error: INTERNAL_ERROR (gnome-calculator:75655): libsoup-WARNING **: 19:43:34.821: (../libsoup/soup-session.c:334):soup_session_dispose: runtime check failed: (soup_connection_manager_get_num_conns (priv->conn_manager) == 0) (gnome-calculator:75655): libsoup-WARNING **: 19:43:34.821: (../libsoup/soup-connection-manager.c:84):soup_host_free: runtime check failed: (host->conns == NULL) Segmentation fault (core dumped) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/2036426/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2035360] Re: GPU hangs in SketchUp on Intel gen12 due to outdated MESA library
** Changed in: chromium-browser (Ubuntu) Status: Fix Committed => New ** Changed in: firefox (Ubuntu) Status: Fix Committed => New -- 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/2035360 Title: GPU hangs in SketchUp on Intel gen12 due to outdated MESA library Status in Mesa: New Status in chromium-browser package in Ubuntu: New Status in firefox package in Ubuntu: New Bug description: When opening a SketchUp model (example: https://app.sketchup.com/share/tc/europe/9jWfPS5lgN8?stoken=KYi8KrAR6g3gv6OqLAKNEEMrQHLOA7jd8oV20HmBbHrZqyPRPmG1QlPurYkJnuw_) in Firefox or Chromium, after ~5 seconds, the SketchUp logo freezes for ~4 seconds, and we see a blank page. The logs show the GPU hang and browser rendering context failed to initialise. This has 100% reproducibility on my 12-gen GPU. On this system with Ubuntu 23.04, I have always seen a GPU hang with the stock Ubuntu kernel or mainline. Log files as attachment - the output of 'dmesg' is at https://quora.org/OJnlVgn4xZ/dmesg.txt - the output of 'dmesg' with kernel boot args 'drm.debug=0x1e log_buf_len=16M' is at https://quora.org/OJnlVgn4xZ/dmesg-debug.txt - the output of /sys/class/drm/card0/error is at https://quora.org/OJnlVgn4xZ/i915-error.txt Since I was able to cause failure uncontained to the rendering process when performing this 5-8 times, there is an argument that this is a security (DoS) issue, though I'll let someone else make a judgement. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2035360/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2033433] Re: Chromium leaks tens of gigabytes of pixmaps (in the Xorg process) after using hardware accelerated video
I will, but just to update expectations: Each revision of Chromium in beta and edge need to be manually reviewed because of a new plug[1]. So expect some a couple of days of delay. Or install it manually from [2]. [1] https://forum.snapcraft.io/t/request-for-personal-files-interface-in-chromium-for-local-share-applications/36629/14 [2] https://launchpad.net/~chromium-team/+snap/chromium-snap-from-source-dev/+build/2240399 -- 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/2033433 Title: Chromium leaks tens of gigabytes of pixmaps (in the Xorg process) after using hardware accelerated video Status in chromium-browser package in Ubuntu: Fix Committed Status in xorg-server package in Ubuntu: Opinion Bug description: https://crbug.com/1467689 --- chromium 118.0.5966.0 2604 latest/edge Whenever I use chromium in a video session (meet, youtube) that used hardware acceleration, for a long time (like 20min or more), and then close it, the whole desktop freezes, and the laptop fan turns on. Logging in remotely I see that Xorg is at 100% CPU. The rest of the system is operational, but nothing graphical is. Just the mouse cursor moves around. SOMETIMES, if I wait a few minutes, Xorg resumes behaving normally, and I can use the desktop again, but most of the time I have to login remotely and kill -9 xorg (plain kill won't do it). With wayland, this does not happen. This could very well be an Xorg bug, but filing here first for visibility. $ lsgpu card0Intel Alderlake_p (Gen12) drm:/dev/dri/card0 └─renderD128 $ lscpu Architecture:x86_64 CPU op-mode(s):32-bit, 64-bit Address sizes: 46 bits physical, 48 bits virtual Byte Order:Little Endian CPU(s): 16 On-line CPU(s) list: 0-15 Vendor ID: GenuineIntel Model name:12th Gen Intel(R) Core(TM) i7-1270P CPU family: 6 Model: 154 Thread(s) per core: 2 Core(s) per socket: 12 Socket(s): 1 Stepping:3 CPU(s) scaling MHz: 41% CPU max MHz: 4800, CPU min MHz: 400, BogoMIPS:4992,00 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdp e1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqd q dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave a vx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb ssbd ibrs ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept_ ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid rdseed adx smap clflushopt clwb intel_pt sha_ni xsaveopt xsavec xgetbv1 xsaves split_lock_detect avx_vnni dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp hwp_pkg_req hfi umip pku ospke waitpkg gfni vaes vpclmulqdq tme rdpid movdiri movdir64b fsrm md_clear serialize pconfig arch_lbr ibt flush_l1d arch_capabilities Virtualization features: Virtualization:VT-x Caches (sum of all): L1d: 448 KiB (12 instances) L1i: 640 KiB (12 instances) L2:9 MiB (6 instances) L3:18 MiB (1 instance) NUMA: NUMA node(s): 1 NUMA node0 CPU(s): 0-15 Vulnerabilities: Itlb multihit: Not affected L1tf: Not affected Mds: Not affected Meltdown: Not affected Mmio stale data: Not affected Retbleed: Not affected Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl Spectre v1:Mitigation; usercopy/swapgs barriers and __user pointer sanitization Spectre v2:Mitigation; Enhanced IBRS, IBPB conditional, RSB filling, PBRSB-eIBRS SW sequence Srbds: Not affected Tsx async abort: Not affected ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: chromium-browser (not installed) ProcVersionSignature: Ubuntu 6.2.0-27.28-generic 6.2.15 Uname: Linux 6.2.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Aug 29 16:47:30 2023 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage:
[Desktop-packages] [Bug 2019045] Re: [snap] New Ubuntu font with normal weight displayed as bold in Google Docs in Chromium after upgrading to Lunar
Andreas noticed in the duplicate report that > The chromium console log also shows a lot of these 404 errors for *.woff2 > fonts: > > GET > filesystem:https://docs.google.com/persistent/docs/fonts/KFO8CneDtsqEr0keqCMhbCc_Mn33tY0.woff2 > net::ERR_FILE_NOT_FOUND -- 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/2019045 Title: [snap] New Ubuntu font with normal weight displayed as bold in Google Docs in Chromium after upgrading to Lunar Status in chromium-browser package in Ubuntu: Triaged Status in fonts-ubuntu package in Ubuntu: Confirmed Bug description: I am experiencing a rendering regression after upgrading from Kinetic to Lunar. Google Docs using the Ubuntu font family are displayed incorrectly in Chromium: the normal weight font is rendered identically to the bold weight one, instead of being thicker than light and thinner than medium. Printing is also affected, unless I use Google Docs' download to PDF function, although that probably triggers a server-side rendering. This issue does not occur in Firefox or Google Chrome. One thing that may be relevant: if I force-refresh my test Google Doc I see all four Ubuntu font lines initially being rendered as bold. The light and medium lines are then re-rendered with the correct weight. It's as if bold was the default weight and the normal variant disappeared. As far as I can tell I was already running Chromium 112.0.5615.49 in Kinetic, and with Chromium being a snap I don't quite understand why the Ubuntu series would matter. I have also tried version 114.0.5735.16 (in latest/beta at the moment); the symptoms are identical. The attachments show the rendering error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2019045/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967632] Re: [snap] apparmor denied when trying to load pkcs11 module for smart card authentication
Thanks Ludovic, so for those smart cards, the pcscd interface has been merged in Snapd (but is apparently only available from 2.60.4 on, so currently you need the beta channel of it), and so I update the test case to a simpler: ---> snap refresh --beta snapd snap refresh --channel stable/pkcs chromium snap connect chromium:pcscd chromium --enable-logging=stderr >chr.log 2>&1 <--- -- 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/1967632 Title: [snap] apparmor denied when trying to load pkcs11 module for smart card authentication Status in Mozilla Firefox: Confirmed Status in chromium-browser package in Ubuntu: In Progress Status in firefox package in Ubuntu: Triaged Bug description: I use a smart card to access government sites. I have that working in firefox and chrome on ubuntu impish, and gave jammy a try, but there firefox won't load the library, giving me a generic error. dmesg, however, shows this apparmor denied message: [sáb abr 2 17:32:27 2022] audit: type=1400 audit(1648931547.646:115): apparmor="DENIED" operation="file_mmap" profile="snap.firefox.firefox" name="/run/user/1000/doc/e0bac853/libaetpkss.so.3.5.4112" pid=3680 comm="firefox" requested_mask="m" denied_mask="m" fsuid=1000 ouid=0 Note also the path, that's not what I typed into the firefox dialog box. I have the .so copied to /usr/lib/x86_64-linux-gnu/libaetpkss.so.3.5.4112, and that's what I typed in when prompted for its path by firefox. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 2 17:34:09 2022 InstallationDate: Installed on 2022-03-20 (13 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220319) Snap.Changes: no changes found SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1967632/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037581] Re: Missing ubuntu font when viewing some google docs
*** This bug is a duplicate of bug 2019045 *** https://bugs.launchpad.net/bugs/2019045 Thanks for the report, Andreas, this is a duplicate of LP:2019045, you noticed something important in the log and I'm passing your comment to that report. ** This bug has been marked a duplicate of bug 2019045 [snap] New Ubuntu font with normal weight displayed as bold in Google Docs in Chromium after upgrading to Lunar -- 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/2037581 Title: Missing ubuntu font when viewing some google docs Status in chromium-browser package in Ubuntu: New Bug description: chromium snap chromium 118.0.5993.11 2645 latest/edge canonical✓ - In chromium, some google doc documents render with an incorrect font. It looks all "bold". I can provide a link in PVT if needed, but see attached screenshots for chrome, and chromium. The chromium console log also shows a lot of these 404 errors for *.woff2 fonts: GET filesystem:https://docs.google.com/persistent/docs/fonts/KFO8CneDtsqEr0keqCMhbCc_Mn33tY0.woff2 net::ERR_FILE_NOT_FOUND The document is using the "Ubuntu" font, that seems to be the culprit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2037581/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037151] Re: Chromium glitches, Brave too, might be GPU
Hi Peter, thanks for doing that! > as it says in my other post i did try running with --disable-gpu No, you tried chromium --disable-gpu-driver-bug-workarounds, which is not the same. > there was a new Chromium snap this morning, and it seems to have fixed the bug! yay! my props to the dev team for getting this fixed so quickly! 117.0.5938.92 was released shortly after 117.0.5938.88, I did nothing but to submit a new build, so upstream probably catched the problem. (: ** Changed in: chromium-browser (Ubuntu) Status: New => Fix Released -- 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/2037151 Title: Chromium glitches, Brave too, might be GPU Status in chromium-browser package in Ubuntu: Fix Released Bug description: Hi there! I have a theory what this problem is, and i am going to post it in detail here https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/2037093 This was not supposed to be a "new" bug report, I wanted to use Apport and somehow attach my Apport output to an *existing* bug thread in bugs.launchpad.net Is there a way to do that? short version: i think its very similar to this: https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/2035360 also, Brave has already fixed the issue, i got a snap update from them about 8 hours ago and YES it fixed it. know anyone on their tech team who can tell you how they fixed it? ;-);-) cheers Peter Fisera https://earthangelconsulting.com ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-panel 1:3.44.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME-Flashback:GNOME Date: Fri Sep 22 20:25:51 2023 ExecutablePath: /usr/bin/gnome-panel GsettingsChanges: b'org.gnome.gnome-panel.layout' b'object-id-list' b"['menu-bar', 'indicators', 'show-desktop', 'window-list', 'workspace-switcher', 'launcher', 'launcher-0', 'launcher-1', 'launcher-2', 'launcher-3', 'launcher-4', 'launcher-5', 'launcher-6', 'launcher-7', 'launcher-8', 'launcher-9', 'launcher-10', 'launcher-11', 'launcher-12', 'launcher-13', 'launcher-14', 'launcher-15', 'launcher-16', 'launcher-17', 'launcher-18', 'launcher-19', 'launcher-20', 'launcher-21', 'launcher-22', 'launcher-23', 'launcher-24', 'launcher-25', 'launcher-26', 'launcher-27', 'launcher-28', 'launcher-29']" b'org.gnome.gnome-panel.layout' b'toplevel-id-list' b"['top-panel', 'bottom-panel']" InstallationDate: Installed on 2021-11-17 (675 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: gnome-panel UpgradeStatus: Upgraded to jammy on 2023-02-20 (215 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME-Flashback:GNOME DRM.card0-DP-1: enabled: disabled dpms: On status: disconnected edid-base64: modes: DRM.card1-HDMI-A-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAEadIjE9cBABkdAQOAMx14KtlFolVNoCcSUFS37wDRwIFAgYCVALMAcU+BwIEAAjqAGHE4LUBYLEUA/R4RAAAe/wBLNkxNVEYxMjA1OTUK/QAySxhTEQAKICAgICAg/ABBU1VTIFZTMjM5CiAgAdECAyJxTwECAxESEwQUBQ4PHR4fECMJFweDAQAAZQMMABAAjArQiiDgLRAQPpYA/R4RAAAYAR0AclHQHiBuKFUA/R4RAAAeAR0AvFLQHiC4KFVA/R4RAAAejArQkCBAMSAMQFUA/R4RAAAY6Q== modes: 1920x1080 1920x1080 1920x1080 1920x1080 1680x1050 1280x1024 1280x1024 1440x900 1280x960 1280x800 1152x864 1280x720 1280x720 1280x720 1280x720 1280x720 1440x576 1440x576 1024x768 1024x768 1024x768 1440x480 1440x480 1440x480 1440x480 832x624 800x600 800x600 800x600 800x600 720x576 720x576 720x576 720x480 720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480 640x480 720x400 DRM.card1-eDP-1: enabled: enabled dpms: On status: connected edid-base64: AP///wA4cE0AADMdAQSlIhN4A2hQmFxYjigbUFQBAQEBAQEBAQEBAQEBAQEBkYqABHE4MkAwIDUAWMIQAAAavTmABHE4MkAwIDUAWMIQAAAa/QAwkJqaIwEKICAgICAg/gBMTTE1NkxGLTJGMDEKAEk= modes: 1920x1080 1920x1080 1680x1050 1280x1024 1440x900 1280x800 1280x720 1024x768 800x600 640x480 DiskUsage: Filesystem Type Size Used Avail Use% Mounted on /dev/nvme0n1p2 ext4 468G 400G 45G 91% / tmpfs tmpfs 7.6G 162M 7.4G 3% /dev/shm /dev/nvme0n1p2 ext4 468G 400G 45G 91% / DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-11-17 (677 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: ASUSTeK COMPUTER INC. ROG Strix
[Desktop-packages] [Bug 2037093] Re: Chromium glitches and images/stylesheets not loading well
*** This bug is a duplicate of bug 2037151 *** https://bugs.launchpad.net/bugs/2037151 ** This bug has been marked a duplicate of bug 2037151 Chromium glitches, Brave too, might be GPU -- 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/2037093 Title: Chromium glitches and images/stylesheets not loading well Status in chromium-browser package in Ubuntu: Confirmed Bug description: Hello, I am using Chromium installed through the software center. Running Ubuntu LTS 22.04.2 on a Lenovo ThinkPad T14 Gen 1. The app has several glitches, screen breaks and crashes. Upon reloading some stylesheets and images don't load correctly. Happy to add more screenshots or help test/reproduce. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2037093/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2033433] Re: Chromium leaks tens of gigabytes of pixmaps (in the Xorg process) after using hardware accelerated video
Great, thanks for your continued testing on this bug report! I'm pushing it to beta as well. -- 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/2033433 Title: Chromium leaks tens of gigabytes of pixmaps (in the Xorg process) after using hardware accelerated video Status in chromium-browser package in Ubuntu: Fix Committed Status in xorg-server package in Ubuntu: Opinion Bug description: https://crbug.com/1467689 --- chromium 118.0.5966.0 2604 latest/edge Whenever I use chromium in a video session (meet, youtube) that used hardware acceleration, for a long time (like 20min or more), and then close it, the whole desktop freezes, and the laptop fan turns on. Logging in remotely I see that Xorg is at 100% CPU. The rest of the system is operational, but nothing graphical is. Just the mouse cursor moves around. SOMETIMES, if I wait a few minutes, Xorg resumes behaving normally, and I can use the desktop again, but most of the time I have to login remotely and kill -9 xorg (plain kill won't do it). With wayland, this does not happen. This could very well be an Xorg bug, but filing here first for visibility. $ lsgpu card0Intel Alderlake_p (Gen12) drm:/dev/dri/card0 └─renderD128 $ lscpu Architecture:x86_64 CPU op-mode(s):32-bit, 64-bit Address sizes: 46 bits physical, 48 bits virtual Byte Order:Little Endian CPU(s): 16 On-line CPU(s) list: 0-15 Vendor ID: GenuineIntel Model name:12th Gen Intel(R) Core(TM) i7-1270P CPU family: 6 Model: 154 Thread(s) per core: 2 Core(s) per socket: 12 Socket(s): 1 Stepping:3 CPU(s) scaling MHz: 41% CPU max MHz: 4800, CPU min MHz: 400, BogoMIPS:4992,00 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdp e1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqd q dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave a vx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb ssbd ibrs ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept_ ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid rdseed adx smap clflushopt clwb intel_pt sha_ni xsaveopt xsavec xgetbv1 xsaves split_lock_detect avx_vnni dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp hwp_pkg_req hfi umip pku ospke waitpkg gfni vaes vpclmulqdq tme rdpid movdiri movdir64b fsrm md_clear serialize pconfig arch_lbr ibt flush_l1d arch_capabilities Virtualization features: Virtualization:VT-x Caches (sum of all): L1d: 448 KiB (12 instances) L1i: 640 KiB (12 instances) L2:9 MiB (6 instances) L3:18 MiB (1 instance) NUMA: NUMA node(s): 1 NUMA node0 CPU(s): 0-15 Vulnerabilities: Itlb multihit: Not affected L1tf: Not affected Mds: Not affected Meltdown: Not affected Mmio stale data: Not affected Retbleed: Not affected Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl Spectre v1:Mitigation; usercopy/swapgs barriers and __user pointer sanitization Spectre v2:Mitigation; Enhanced IBRS, IBPB conditional, RSB filling, PBRSB-eIBRS SW sequence Srbds: Not affected Tsx async abort: Not affected ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: chromium-browser (not installed) ProcVersionSignature: Ubuntu 6.2.0-27.28-generic 6.2.15 Uname: Linux 6.2.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Aug 29 16:47:30 2023 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2033433/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net
[Desktop-packages] [Bug 2033433] Re: Chromium leaks tens of gigabytes of pixmaps (in the Xorg process) after using hardware accelerated video
This is now released to beta and edge. And thank you, Jianhui, for contributing the fix! ** Changed in: chromium-browser (Ubuntu) Status: Fix Committed => Fix Released -- 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/2033433 Title: Chromium leaks tens of gigabytes of pixmaps (in the Xorg process) after using hardware accelerated video Status in chromium-browser package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Opinion Bug description: https://crbug.com/1467689 --- chromium 118.0.5966.0 2604 latest/edge Whenever I use chromium in a video session (meet, youtube) that used hardware acceleration, for a long time (like 20min or more), and then close it, the whole desktop freezes, and the laptop fan turns on. Logging in remotely I see that Xorg is at 100% CPU. The rest of the system is operational, but nothing graphical is. Just the mouse cursor moves around. SOMETIMES, if I wait a few minutes, Xorg resumes behaving normally, and I can use the desktop again, but most of the time I have to login remotely and kill -9 xorg (plain kill won't do it). With wayland, this does not happen. This could very well be an Xorg bug, but filing here first for visibility. $ lsgpu card0Intel Alderlake_p (Gen12) drm:/dev/dri/card0 └─renderD128 $ lscpu Architecture:x86_64 CPU op-mode(s):32-bit, 64-bit Address sizes: 46 bits physical, 48 bits virtual Byte Order:Little Endian CPU(s): 16 On-line CPU(s) list: 0-15 Vendor ID: GenuineIntel Model name:12th Gen Intel(R) Core(TM) i7-1270P CPU family: 6 Model: 154 Thread(s) per core: 2 Core(s) per socket: 12 Socket(s): 1 Stepping:3 CPU(s) scaling MHz: 41% CPU max MHz: 4800, CPU min MHz: 400, BogoMIPS:4992,00 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdp e1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqd q dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave a vx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb ssbd ibrs ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept_ ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid rdseed adx smap clflushopt clwb intel_pt sha_ni xsaveopt xsavec xgetbv1 xsaves split_lock_detect avx_vnni dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp hwp_pkg_req hfi umip pku ospke waitpkg gfni vaes vpclmulqdq tme rdpid movdiri movdir64b fsrm md_clear serialize pconfig arch_lbr ibt flush_l1d arch_capabilities Virtualization features: Virtualization:VT-x Caches (sum of all): L1d: 448 KiB (12 instances) L1i: 640 KiB (12 instances) L2:9 MiB (6 instances) L3:18 MiB (1 instance) NUMA: NUMA node(s): 1 NUMA node0 CPU(s): 0-15 Vulnerabilities: Itlb multihit: Not affected L1tf: Not affected Mds: Not affected Meltdown: Not affected Mmio stale data: Not affected Retbleed: Not affected Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl Spectre v1:Mitigation; usercopy/swapgs barriers and __user pointer sanitization Spectre v2:Mitigation; Enhanced IBRS, IBPB conditional, RSB filling, PBRSB-eIBRS SW sequence Srbds: Not affected Tsx async abort: Not affected ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: chromium-browser (not installed) ProcVersionSignature: Ubuntu 6.2.0-27.28-generic 6.2.15 Uname: Linux 6.2.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Aug 29 16:47:30 2023 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2033433/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1798450] Re: [snap] File dialogs show snap's home directory instead of user's
As said in #12 this should be fixed by now. If not, please state if this is observed in both programs (Libreoffice and Chromium) or only one of them or a different one, and also attach the output of apt list --installed | grep desktop-portal ** Changed in: chromium-browser (Ubuntu) Status: Confirmed => Incomplete ** Changed in: libreoffice (Ubuntu) Status: Confirmed => Incomplete -- 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/1798450 Title: [snap] File dialogs show snap's home directory instead of user's Status in chromium-browser package in Ubuntu: Incomplete Status in libreoffice package in Ubuntu: Incomplete Bug description: How to reproduce: - Find a web page that has a file chooser, e.g. https://developer.mozilla.org/docs/Web/HTML/Element/input/file - Click the "Choose File" button - Click "Home" if you didn't start here - See that Chromium uses `/home/$USER/snap/chromium/500` as the home folder Expected behavior: The file picker should use the user's home folder, not the snap's, because everything else would be confusing for end users. Versions: snap2.35.4+18.10 snapd 2.35.4+18.10 series 16 ubuntu 18.10 kernel 4.18.11-surface-linux-surface Chromium 70.0.3538.67 snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1798450/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1732482] Re: [snap] doesn't properly save desktop files for "create shortcuts" action
** Changed in: chromium-browser (Ubuntu) Status: In Progress => Fix Committed -- 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/1732482 Title: [snap] doesn't properly save desktop files for "create shortcuts" action Status in chromium-browser package in Ubuntu: Fix Committed Bug description: For chrome apps, the create shortcuts action should create desktop files but it doesn't. I suspect it has something to do with paths. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1732482/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037151] Re: Chromium glitches, Brave too, might be GPU
Hi Peter, thanks for trying to submit a bug report via Apport. As it seems it initially failed to target the correct package, can you try 'apport-collect 2037151'? Is the issue reproducible if you completely disable hardware acceleration, i.e. 'chromium --disable-gpu'? What if you revert to the previous revision of Chromium with 'snap revert chromium' and try again launching it normally? Does Chromium report something suspicious in stderr? -- 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/2037151 Title: Chromium glitches, Brave too, might be GPU Status in chromium-browser package in Ubuntu: New Bug description: Hi there! I have a theory what this problem is, and i am going to post it in detail here https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/2037093 This was not supposed to be a "new" bug report, I wanted to use Apport and somehow attach my Apport output to an *existing* bug thread in bugs.launchpad.net Is there a way to do that? short version: i think its very similar to this: https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/2035360 also, Brave has already fixed the issue, i got a snap update from them about 8 hours ago and YES it fixed it. know anyone on their tech team who can tell you how they fixed it? ;-);-) cheers Peter Fisera https://earthangelconsulting.com ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-panel 1:3.44.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME-Flashback:GNOME Date: Fri Sep 22 20:25:51 2023 ExecutablePath: /usr/bin/gnome-panel GsettingsChanges: b'org.gnome.gnome-panel.layout' b'object-id-list' b"['menu-bar', 'indicators', 'show-desktop', 'window-list', 'workspace-switcher', 'launcher', 'launcher-0', 'launcher-1', 'launcher-2', 'launcher-3', 'launcher-4', 'launcher-5', 'launcher-6', 'launcher-7', 'launcher-8', 'launcher-9', 'launcher-10', 'launcher-11', 'launcher-12', 'launcher-13', 'launcher-14', 'launcher-15', 'launcher-16', 'launcher-17', 'launcher-18', 'launcher-19', 'launcher-20', 'launcher-21', 'launcher-22', 'launcher-23', 'launcher-24', 'launcher-25', 'launcher-26', 'launcher-27', 'launcher-28', 'launcher-29']" b'org.gnome.gnome-panel.layout' b'toplevel-id-list' b"['top-panel', 'bottom-panel']" InstallationDate: Installed on 2021-11-17 (675 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: gnome-panel UpgradeStatus: Upgraded to jammy on 2023-02-20 (215 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2037151/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2033433] Re: Chromium leaks tens of gigabytes of pixmaps (in the Xorg process) after using hardware accelerated video
I'm committing this to edge only as there are reports of H264 failure in the upstream tracker. Let's see if we can reproduce it. ** Changed in: chromium-browser (Ubuntu) Status: Confirmed => Fix Committed -- 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/2033433 Title: Chromium leaks tens of gigabytes of pixmaps (in the Xorg process) after using hardware accelerated video Status in chromium-browser package in Ubuntu: Fix Committed Status in xorg-server package in Ubuntu: Opinion Bug description: https://crbug.com/1467689 --- chromium 118.0.5966.0 2604 latest/edge Whenever I use chromium in a video session (meet, youtube) that used hardware acceleration, for a long time (like 20min or more), and then close it, the whole desktop freezes, and the laptop fan turns on. Logging in remotely I see that Xorg is at 100% CPU. The rest of the system is operational, but nothing graphical is. Just the mouse cursor moves around. SOMETIMES, if I wait a few minutes, Xorg resumes behaving normally, and I can use the desktop again, but most of the time I have to login remotely and kill -9 xorg (plain kill won't do it). With wayland, this does not happen. This could very well be an Xorg bug, but filing here first for visibility. $ lsgpu card0Intel Alderlake_p (Gen12) drm:/dev/dri/card0 └─renderD128 $ lscpu Architecture:x86_64 CPU op-mode(s):32-bit, 64-bit Address sizes: 46 bits physical, 48 bits virtual Byte Order:Little Endian CPU(s): 16 On-line CPU(s) list: 0-15 Vendor ID: GenuineIntel Model name:12th Gen Intel(R) Core(TM) i7-1270P CPU family: 6 Model: 154 Thread(s) per core: 2 Core(s) per socket: 12 Socket(s): 1 Stepping:3 CPU(s) scaling MHz: 41% CPU max MHz: 4800, CPU min MHz: 400, BogoMIPS:4992,00 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdp e1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqd q dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave a vx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb ssbd ibrs ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept_ ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid rdseed adx smap clflushopt clwb intel_pt sha_ni xsaveopt xsavec xgetbv1 xsaves split_lock_detect avx_vnni dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp hwp_pkg_req hfi umip pku ospke waitpkg gfni vaes vpclmulqdq tme rdpid movdiri movdir64b fsrm md_clear serialize pconfig arch_lbr ibt flush_l1d arch_capabilities Virtualization features: Virtualization:VT-x Caches (sum of all): L1d: 448 KiB (12 instances) L1i: 640 KiB (12 instances) L2:9 MiB (6 instances) L3:18 MiB (1 instance) NUMA: NUMA node(s): 1 NUMA node0 CPU(s): 0-15 Vulnerabilities: Itlb multihit: Not affected L1tf: Not affected Mds: Not affected Meltdown: Not affected Mmio stale data: Not affected Retbleed: Not affected Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl Spectre v1:Mitigation; usercopy/swapgs barriers and __user pointer sanitization Spectre v2:Mitigation; Enhanced IBRS, IBPB conditional, RSB filling, PBRSB-eIBRS SW sequence Srbds: Not affected Tsx async abort: Not affected ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: chromium-browser (not installed) ProcVersionSignature: Ubuntu 6.2.0-27.28-generic 6.2.15 Uname: Linux 6.2.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Aug 29 16:47:30 2023 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2033433/+subscriptions
[Desktop-packages] [Bug 2037093] Re: Chromium glitches and images/stylesheets not loading well
Thanks for the report, Gloria. Can you please run 'apport-collect 2037093'? Is the issue reproducible if you disable hardware acceleration, i.e. 'chromium --disable-gpu'? What if you revert to the previous revision with 'snap revert chromium'? Does Chromium report something suspicious in stderr? -- 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/2037093 Title: Chromium glitches and images/stylesheets not loading well Status in chromium-browser package in Ubuntu: New Bug description: Hello, I am using Chromium installed through the software center. Running Ubuntu LTS 22.04.2 on a Lenovo ThinkPad T14 Gen 1. The app has several glitches, screen breaks and crashes. Upon reloading some stylesheets and images don't load correctly. Happy to add more screenshots or help test/reproduce. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2037093/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1732482] Re: [snap] doesn't properly save desktop files for "create shortcuts" action
Thanks for testing! Julian, I think you already know that and just wanted to perform thorough testing, but in case it was not clear, the fix is not yet in stable. Yet you noted something in test case A: > File chrome-pdplehbldmmknfihajdehomkoigcbhib-Default.desktop was created in ~/Desktop Did you expect that? I'd assume that is the wrong behavior but then I don't use PWAs. What you describe in cases B and C is (what I believe to be) the expected behavior. > In all 3 cases the dock never showed the App icon when I opened the app but the Chromium Icon. I don't know if this could be fixed as if I open any PWA and then I want to open Chromium, it will show the PWA window and not open a Chromium window. That is a known issue but with Gnome Shell (c.f. LP:#2007652 for that); it doesn't happen in other desktop environments (tested Unity, Icewm). -- 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/1732482 Title: [snap] doesn't properly save desktop files for "create shortcuts" action Status in chromium-browser package in Ubuntu: Fix Committed Bug description: For chrome apps, the create shortcuts action should create desktop files but it doesn't. I suspect it has something to do with paths. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1732482/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1732482] Re: [snap] doesn't properly save desktop files for "create shortcuts" action
WBGSReject, you seem to have tested stable! And apparently you observed the same as Julian (#34) in test A. So I also extend my question to you: Do you expect the PWA on the desktop or as a launcher? I'll be investigating if there is any consensus on that, but otherwise I might simply combine the two approaches, namely creating both a desktop launcher (~/Desktop) and a dock/activities/menu launcher (~/.local/share/applications). -- 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/1732482 Title: [snap] doesn't properly save desktop files for "create shortcuts" action Status in chromium-browser package in Ubuntu: Fix Committed Bug description: For chrome apps, the create shortcuts action should create desktop files but it doesn't. I suspect it has something to do with paths. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1732482/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798450] Re: [snap] File dialogs show snap's home directory instead of user's
** Changed in: chromium-browser (Ubuntu) Status: Incomplete => Fix Released ** Changed in: libreoffice (Ubuntu) Status: Incomplete => Fix Released -- 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/1798450 Title: [snap] File dialogs show snap's home directory instead of user's Status in chromium-browser package in Ubuntu: Fix Released Status in libreoffice package in Ubuntu: Fix Released Bug description: How to reproduce: - Find a web page that has a file chooser, e.g. https://developer.mozilla.org/docs/Web/HTML/Element/input/file - Click the "Choose File" button - Click "Home" if you didn't start here - See that Chromium uses `/home/$USER/snap/chromium/500` as the home folder Expected behavior: The file picker should use the user's home folder, not the snap's, because everything else would be confusing for end users. Versions: snap2.35.4+18.10 snapd 2.35.4+18.10 series 16 ubuntu 18.10 kernel 4.18.11-surface-linux-surface Chromium 70.0.3538.67 snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1798450/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1732482] Re: [snap] doesn't properly save desktop files for "create shortcuts" action
** Changed in: chromium-browser (Ubuntu) Status: Fix Committed => Fix Released -- 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/1732482 Title: [snap] doesn't properly save desktop files for "create shortcuts" action Status in chromium-browser package in Ubuntu: Fix Released Bug description: For chrome apps, the create shortcuts action should create desktop files but it doesn't. I suspect it has something to do with paths. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1732482/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2038727] Re: Chromium snap theme parsing error
** Changed in: chromium-browser (Ubuntu) Status: Triaged => In Progress -- 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/2038727 Title: Chromium snap theme parsing error Status in chromium-browser package in Ubuntu: In Progress Bug description: Chromium Version 117.0.5938.149 (Official Build) snap (64-bit) not following my GTK theme. Starting the Chromium snap from the terminal yields a theme parsing error: (chrome:95638): Gtk-WARNING **: 11:01:12.220: Theme parsing error: gtk.css:1:0: Failed to import: Error opening file /home/aej/.local/share/themes/Adwaita_modified/gtk-3.0/gtk.css: Permission denied Previous versions of the Chromium snap have not had this problem. Debian 11 + XFCE. I have been running the chromium snap for about two years without an issue like this on this system. I have reverted to the previous version of the chromium snap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2038727/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 2038727] Re: Chromium snap theme parsing error
Given that this stopped working for you exactly in 117.0.5938.149, which included some related changes (e.g. changing the default XDG_DATA_HOME), one of them is probably affecting you here. But before we continue, please clarify this: You only notice it not only in the stderr log but also in the user interface itself, which doesn't use your custom theme, as it did before that release, right? > $HOME/.config/gtk-3.0/settings.ini does not exist. How do you set your theme? Can you confirm that ---> $ readlink $HOME/snap/chromium/current/.local/share/themes /snap/chromium//data-dir/themes <--- and that ---> chromium file:///snap/chromium/current/data-dir/themes < lists a bunch of theme directories? -- 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/2038727 Title: Chromium snap theme parsing error Status in chromium-browser package in Ubuntu: Incomplete Bug description: Chromium Version 117.0.5938.149 (Official Build) snap (64-bit) not following my GTK theme. Starting the Chromium snap from the terminal yields a theme parsing error: (chrome:95638): Gtk-WARNING **: 11:01:12.220: Theme parsing error: gtk.css:1:0: Failed to import: Error opening file /home/aej/.local/share/themes/Adwaita_modified/gtk-3.0/gtk.css: Permission denied Previous versions of the Chromium snap have not had this problem. Debian 11 + XFCE. I have been running the chromium snap for about two years without an issue like this on this system. I have reverted to the previous version of the chromium snap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2038727/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2038875] Re: Snap uses hardcoded key and salt for password and cookie encryption
Well true, I'm removing the duplicate mark, however it does explain why we cannot do this: https://forum.snapcraft.io/t/auto-connecting-the-cups-control-and- password-manager-service-interfaces-for-the-chromium-snap/4592/6 ** This bug is no longer a duplicate of bug 1836616 [snap] Upgrade from deb to snap forgets saved passwords ** Changed in: chromium-browser (Ubuntu) Status: New => Won't Fix -- 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/2038875 Title: Snap uses hardcoded key and salt for password and cookie encryption Status in chromium-browser package in Ubuntu: Won't Fix Bug description: A working Ubuntu install includes Gnome which includes the gnome- keyring. The snap version of Ubuntu does not make use of it. On an install of Debian with Gnome, the key ring is used. However, with Ubuntu everything is encrypted with the static key of peanuts and the salt of saltysalt, and openly accessible as sqlite databases in ~/snap/chromium/common/chromium, including passwords from the browser and the cookies. This should probably be fixed. If a laptop is physically compromised it's trivial to decrypt this with a tool like xbrowser. You can verify that gnome-libcrypt isn't chosen by default with --enable-logging=stderr --v=1 redirect stderr to a log and look for Crypt. You can see /why/ gnome-libcrypt isn't chosen with chromium --password-store=gnome-libcrypt --enable-logging=stderr --v=1 and again looking for messages with Crypt. I don't think this is a vulnerability per se, Chrome ships in Debian with the ability to use a basic store too. But it's an undesirable configuration and a regression from Debian when it's run on a platform with gnome and libsecret, and only doesn't work because of snap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2038875/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2038727] Re: Chromium snap theme parsing error
Andy, I released a tentative fix to the edge channel. If you want to try it, refresh your snap with snap refresh --edge chromium Please note that a transition back to stable channel might not always be smooth (e.g. password storage can become incompatible), so you could generate a snapshot and then restore it[1] or also use parallel installs[2] to protect yourself against such problems. [1] https://forum.snapcraft.io/t/snapshots/9468 [2] https://forum.snapcraft.io/t/parallel-installs/7679 -- 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/2038727 Title: Chromium snap theme parsing error Status in chromium-browser package in Ubuntu: Fix Committed Bug description: Chromium Version 117.0.5938.149 (Official Build) snap (64-bit) not following my GTK theme. Starting the Chromium snap from the terminal yields a theme parsing error: (chrome:95638): Gtk-WARNING **: 11:01:12.220: Theme parsing error: gtk.css:1:0: Failed to import: Error opening file /home/aej/.local/share/themes/Adwaita_modified/gtk-3.0/gtk.css: Permission denied Previous versions of the Chromium snap have not had this problem. Debian 11 + XFCE. I have been running the chromium snap for about two years without an issue like this on this system. I have reverted to the previous version of the chromium snap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2038727/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2039187] [NEW] Thunderbird doesn't accept URI attachments anymore
Public bug reported: The desktop portal constructs an mailto: url with an attachment= but thunderbird upstream explicitly decided to not allow adding files from an URL for security reasons. One can still use the -compose option though, as this patch does. Test case - * Install the proposed package. * Log out and back in. * Set Thunberbird as default client in Gnome Control Panel. * Open Nautilus and try to attach two files to the same email. They can be creatively named, it should not break on weird characters. * Thunderbird should open with the corresponding files attached. * [For regression testing] Set Evolution as the default. * Open Nautilus and try to attach two files to the same email. They can be creatively named, it should not break on weird characters. It only attaches one file, this is however not a regression. ** Affects: xdg-desktop-portal-gtk (Ubuntu) Importance: Undecided Assignee: Nathan Teodosio (nteodosio) Status: Confirmed ** Tags: patch ** Patch added: "xdg-deskop-portal-gtk.diff" https://bugs.launchpad.net/bugs/2039187/+attachment/5708881/+files/xdg-deskop-portal-gtk.diff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal-gtk in Ubuntu. https://bugs.launchpad.net/bugs/2039187 Title: Thunderbird doesn't accept URI attachments anymore Status in xdg-desktop-portal-gtk package in Ubuntu: Confirmed Bug description: The desktop portal constructs an mailto: url with an attachment= but thunderbird upstream explicitly decided to not allow adding files from an URL for security reasons. One can still use the -compose option though, as this patch does. Test case - * Install the proposed package. * Log out and back in. * Set Thunberbird as default client in Gnome Control Panel. * Open Nautilus and try to attach two files to the same email. They can be creatively named, it should not break on weird characters. * Thunderbird should open with the corresponding files attached. * [For regression testing] Set Evolution as the default. * Open Nautilus and try to attach two files to the same email. They can be creatively named, it should not break on weird characters. It only attaches one file, this is however not a regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/2039187/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2038727] Re: Chromium snap theme parsing error
So I followed up there and now I know the full recipe for you, with no need to worry about backwards incompatibility: * [Create a snapshot] snap save chromium * [Switch to edge] snap refresh --edge chromium * Launch Chromium normally, see if the problem is fixed * [Switch back to stable (if desired)] snap refresh --stable chromium * [Restore your stable data (if desired)] snap restore You can also query your saved sets with 'snap saved'. -- 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/2038727 Title: Chromium snap theme parsing error Status in chromium-browser package in Ubuntu: Fix Committed Bug description: Chromium Version 117.0.5938.149 (Official Build) snap (64-bit) not following my GTK theme. Starting the Chromium snap from the terminal yields a theme parsing error: (chrome:95638): Gtk-WARNING **: 11:01:12.220: Theme parsing error: gtk.css:1:0: Failed to import: Error opening file /home/aej/.local/share/themes/Adwaita_modified/gtk-3.0/gtk.css: Permission denied Previous versions of the Chromium snap have not had this problem. Debian 11 + XFCE. I have been running the chromium snap for about two years without an issue like this on this system. I have reverted to the previous version of the chromium snap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2038727/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 2038727] Re: Chromium snap theme parsing error
Ah, sorry, silly I dispatched builds a bit before I committed changes. At least both of us learned something new about the snapshots. I'll build again and let you know, thanks for your disposition in testing the fix. -- 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/2038727 Title: Chromium snap theme parsing error Status in chromium-browser package in Ubuntu: Fix Committed Bug description: Chromium Version 117.0.5938.149 (Official Build) snap (64-bit) not following my GTK theme. Starting the Chromium snap from the terminal yields a theme parsing error: (chrome:95638): Gtk-WARNING **: 11:01:12.220: Theme parsing error: gtk.css:1:0: Failed to import: Error opening file /home/aej/.local/share/themes/Adwaita_modified/gtk-3.0/gtk.css: Permission denied Previous versions of the Chromium snap have not had this problem. Debian 11 + XFCE. I have been running the chromium snap for about two years without an issue like this on this system. I have reverted to the previous version of the chromium snap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2038727/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1996267] Re: [snap] Doesn't store encrypted passwords unless interface is connected
> I don't see how this debate is apropos. Whether or not the passwords are stored in the clear, or obscured with symmetric encryption using hard coded parameters in chrome is irrelevant. Both of these scenarios are entirely unacceptable. You are right, but if a statement presented as a certainty and is however inaccurate, I think it there is no harm in having a discussion to settle it, because the thread can serve a purpose for other people, and one different from ours. If it became unclear, the fact that the current behavior is undesired is undisputed. > So you'll have a tool you can run.. The command will be simple, > >xbrowser export chrome passwords > > And you'll be able to dump all the passwords. I've already nudged folks internally and there will be a new review of the auto-connection request, that will be a great proof-of-concept and I thank you in advance. -- 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/1996267 Title: [snap] Doesn't store encrypted passwords unless interface is connected Status in chromium-browser package in Ubuntu: Confirmed Bug description: In the Snap package of Chromium, Chromium is not protecting passwords with gnome-keyring (or KWallet). As a result, copying the Chromium profile directory from the snap directory gives access to all stored passwords. This is a HIGH security risk. Regular users who are used to storing their passwords in browsers are probably unaware of this. Note that Chromium is started with the command line option “--password-store=basic”. This hack should never have been released to the public. The Chromium documentation states: > --password-store=basic (to use the plain text store) https://chromium.googlesource.com/chromium/src/+/master/docs/linux/password_storage.md To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1996267/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2039701] Re: chromium freezes gnome if hardware acceleration is activated in browser setttings (U20.04) Intel HD-Grafik 4400
Another possible hint to collect: Does this happen both in X11 and Wayland? -- 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/2039701 Title: chromium freezes gnome if hardware acceleration is activated in browser setttings (U20.04) Intel HD-Grafik 4400 Status in chromium-browser package in Ubuntu: New Bug description: Ubuntu 20.04 have to deaktivate hardware acceleration in browser stetting in order to prevent delay and crash of chromium broswer and chrome browser. Was able to reboot with strg+alt+F(x) sudo reboot found line /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed in syslog when crash happened. Let me to this via gürgelschnüffel: vainfo libva info: VA-API version 1.7.0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_7 libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed libva info: va_openDriver() returns 1 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_6 libva info: va_openDriver() returns 0 vainfo: VA-API version: 1.7 (libva 2.6.0) vainfo: Driver version: Intel i965 driver for Intel(R) Haswell - 2.4.0 vainfo: Supported profile and entrypoints VAProfileMPEG2Simple: VAEntrypointVLD VAProfileMPEG2Simple: VAEntrypointEncSlice VAProfileMPEG2Main : VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointEncSlice VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileH264MultiviewHigh : VAEntrypointVLD VAProfileH264MultiviewHigh : VAEntrypointEncSlice VAProfileH264StereoHigh : VAEntrypointVLD VAProfileH264StereoHigh : VAEntrypointEncSlice VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main: VAEntrypointVLD VAProfileVC1Advanced: VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc VAProfileJPEGBaseline : VAEntrypointVLD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2039701/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2039701] Re: chromium freezes gnome if hardware acceleration is activated in browser setttings (U20.04) Intel HD-Grafik 4400
> Was able to reboot with strg+alt+F(x) sudo reboot Once this happens again, can you please collect dmesg and journalctl (some hundreds of lines are probably enough) before rebooting? Instead of launching Chromium normally, use chromium --enable-logging=stderr > chromium.log 2>&1 Also: snap connections chromium snap info chromium > via gürgelschnüffel: > > vainfo First the most important question: What is Gürgelschnüffel? Now, running vainfo in your host system doesn't help much, because Chromium is supposed to use the driver provided by the (not ideally named, I know) Gnome snap, /snap/gnome-42-2204/current/usr/lib/x86_64-linux- gnu/dri/iHD_drv_video.so. -- 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/2039701 Title: chromium freezes gnome if hardware acceleration is activated in browser setttings (U20.04) Intel HD-Grafik 4400 Status in chromium-browser package in Ubuntu: New Bug description: Ubuntu 20.04 have to deaktivate hardware acceleration in browser stetting in order to prevent delay and crash of chromium broswer and chrome browser. Was able to reboot with strg+alt+F(x) sudo reboot found line /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed in syslog when crash happened. Let me to this via gürgelschnüffel: vainfo libva info: VA-API version 1.7.0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_7 libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed libva info: va_openDriver() returns 1 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_6 libva info: va_openDriver() returns 0 vainfo: VA-API version: 1.7 (libva 2.6.0) vainfo: Driver version: Intel i965 driver for Intel(R) Haswell - 2.4.0 vainfo: Supported profile and entrypoints VAProfileMPEG2Simple: VAEntrypointVLD VAProfileMPEG2Simple: VAEntrypointEncSlice VAProfileMPEG2Main : VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointEncSlice VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileH264MultiviewHigh : VAEntrypointVLD VAProfileH264MultiviewHigh : VAEntrypointEncSlice VAProfileH264StereoHigh : VAEntrypointVLD VAProfileH264StereoHigh : VAEntrypointEncSlice VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main: VAEntrypointVLD VAProfileVC1Advanced: VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc VAProfileJPEGBaseline : VAEntrypointVLD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2039701/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2039690] Re: If you move or delete bookmarks, the bookmark manager always jumps back to the beginning, which is really annoying when you want to organize bookmarks.
Thanks for the report. Cannot reproduce. The bookmark manager is chrome://bookmarks/, right? Anyway, this would be most likely a ticket for upstream to tackle, crbug.com. ** Changed in: chromium-browser (Ubuntu) Status: New => Incomplete -- 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/2039690 Title: If you move or delete bookmarks, the bookmark manager always jumps back to the beginning, which is really annoying when you want to organize bookmarks. Status in chromium-browser package in Ubuntu: Incomplete Bug description: If you move or delete bookmarks, the bookmark manager always jumps back to the beginning, which is really annoying when you want to organize bookmarks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2039690/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 2038875] Re: Snap uses hardcoded key and salt for password and cookie encryption
If password-manager-service is connected with snap connect chromium:password-manager-service then it uses the operating system's key ring. So are you pointing out that Chromium ought to use gnome-libcrypt instead of basic when no key ring is detected? -- 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/2038875 Title: Snap uses hardcoded key and salt for password and cookie encryption Status in chromium-browser package in Ubuntu: New Bug description: A working Ubuntu install includes Gnome which includes the gnome- keyring. The snap version of Ubuntu does not make use of it. On an install of Debian with Gnome, the key ring is used. However, with Ubuntu everything is encrypted with the static key of peanuts and the salt of saltysalt, and openly accessible as sqlite databases in ~/snap/chromium/common/chromium, including passwords from the browser and the cookies. This should probably be fixed. If a laptop is physically compromised it's trivial to decrypt this with a tool like xbrowser. You can verify that gnome-libcrypt isn't chosen by default with --enable-logging=stderr --v=1 redirect stderr to a log and look for Crypt. You can see /why/ gnome-libcrypt isn't chosen with chromium --password-store=gnome-libcrypt --enable-logging=stderr --v=1 and again looking for messages with Crypt. I don't think this is a vulnerability per se, Chrome ships in Debian with the ability to use a basic store too. But it's an undesirable configuration and a regression from Debian when it's run on a platform with gnome and libsecret, and only doesn't work because of snap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2038875/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2038875] Re: Snap uses hardcoded key and salt for password and cookie encryption
** Tags added: password-storage -- 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/2038875 Title: Snap uses hardcoded key and salt for password and cookie encryption Status in chromium-browser package in Ubuntu: New Bug description: A working Ubuntu install includes Gnome which includes the gnome- keyring. The snap version of Ubuntu does not make use of it. On an install of Debian with Gnome, the key ring is used. However, with Ubuntu everything is encrypted with the static key of peanuts and the salt of saltysalt, and openly accessible as sqlite databases in ~/snap/chromium/common/chromium, including passwords from the browser and the cookies. This should probably be fixed. If a laptop is physically compromised it's trivial to decrypt this with a tool like xbrowser. You can verify that gnome-libcrypt isn't chosen by default with --enable-logging=stderr --v=1 redirect stderr to a log and look for Crypt. You can see /why/ gnome-libcrypt isn't chosen with chromium --password-store=gnome-libcrypt --enable-logging=stderr --v=1 and again looking for messages with Crypt. I don't think this is a vulnerability per se, Chrome ships in Debian with the ability to use a basic store too. But it's an undesirable configuration and a regression from Debian when it's run on a platform with gnome and libsecret, and only doesn't work because of snap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2038875/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 2038727] Re: Chromium snap theme parsing error
> ---> > How do you set your theme? > > I set my theme using xfce4-settings-manager "Appearance" and "Window Manager" > selections. Should I be doing something else? > <--- I don't think so, that should be a valid use case, we can surely rule out the possibility of XFCE setting the system theme incorrectly. I need to investigate how it does it though. > ---> > $HOME/snap/chromium/current/.local/share/themes is a broken link because > /snap/chromium//data-dir does not exist in either snap 2655 (the one I am > complaining about) or snap 2642 (which works fine for me). > <--- > > ---> > chromium file:///snap/chromium/current/data-dir/themes > > Does list a bunch of theme directories > <--- That's all as expected indeed. > ---> > As I stated at the end of Comment #2, the chromium snap works fine if I add > GTK_THEME=Adwaita to the Exec= line in the application's desktop file. > <--- Sorry, I missed that because Launchpad collapses long answers. But anyway, if I read correctly, Adwaita is not your theme, but Adwaita_modified. Does it work with GTK_THEME=Adwaita_modified? And maybe my tests were moot, because gtk-theme interface provides the Yaru themes I tried. I will later try with a therefrom absent theme or a custom theme. ** Changed in: chromium-browser (Ubuntu) Status: Incomplete => New ** Changed in: chromium-browser (Ubuntu) Importance: Undecided => Low -- 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/2038727 Title: Chromium snap theme parsing error Status in chromium-browser package in Ubuntu: New Bug description: Chromium Version 117.0.5938.149 (Official Build) snap (64-bit) not following my GTK theme. Starting the Chromium snap from the terminal yields a theme parsing error: (chrome:95638): Gtk-WARNING **: 11:01:12.220: Theme parsing error: gtk.css:1:0: Failed to import: Error opening file /home/aej/.local/share/themes/Adwaita_modified/gtk-3.0/gtk.css: Permission denied Previous versions of the Chromium snap have not had this problem. Debian 11 + XFCE. I have been running the chromium snap for about two years without an issue like this on this system. I have reverted to the previous version of the chromium snap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2038727/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2038727] Re: Chromium snap theme parsing error
What is $HOME/.config/gtk-3.0/settings.ini? -- 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/2038727 Title: Chromium snap theme parsing error Status in chromium-browser package in Ubuntu: Incomplete Bug description: Chromium Version 117.0.5938.149 (Official Build) snap (64-bit) not following my GTK theme. Starting the Chromium snap from the terminal yields a theme parsing error: (chrome:95638): Gtk-WARNING **: 11:01:12.220: Theme parsing error: gtk.css:1:0: Failed to import: Error opening file /home/aej/.local/share/themes/Adwaita_modified/gtk-3.0/gtk.css: Permission denied Previous versions of the Chromium snap have not had this problem. Debian 11 + XFCE. I have been running the chromium snap for about two years without an issue like this on this system. I have reverted to the previous version of the chromium snap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2038727/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2038727] Re: Chromium snap theme parsing error
Do you have a reproducer recipe? I tried with various themes I found in /usr/share/themes: GTK_THEME=Yaru-viridian chromium GTK_THEME=Yaru-blue chromium and it seems to be working fine. -- 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/2038727 Title: Chromium snap theme parsing error Status in chromium-browser package in Ubuntu: Incomplete Bug description: Chromium Version 117.0.5938.149 (Official Build) snap (64-bit) not following my GTK theme. Starting the Chromium snap from the terminal yields a theme parsing error: (chrome:95638): Gtk-WARNING **: 11:01:12.220: Theme parsing error: gtk.css:1:0: Failed to import: Error opening file /home/aej/.local/share/themes/Adwaita_modified/gtk-3.0/gtk.css: Permission denied Previous versions of the Chromium snap have not had this problem. Debian 11 + XFCE. I have been running the chromium snap for about two years without an issue like this on this system. I have reverted to the previous version of the chromium snap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2038727/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2038727] Re: Chromium snap theme parsing error
** Changed in: chromium-browser (Ubuntu) Status: In Progress => Fix Committed -- 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/2038727 Title: Chromium snap theme parsing error Status in chromium-browser package in Ubuntu: Fix Committed Bug description: Chromium Version 117.0.5938.149 (Official Build) snap (64-bit) not following my GTK theme. Starting the Chromium snap from the terminal yields a theme parsing error: (chrome:95638): Gtk-WARNING **: 11:01:12.220: Theme parsing error: gtk.css:1:0: Failed to import: Error opening file /home/aej/.local/share/themes/Adwaita_modified/gtk-3.0/gtk.css: Permission denied Previous versions of the Chromium snap have not had this problem. Debian 11 + XFCE. I have been running the chromium snap for about two years without an issue like this on this system. I have reverted to the previous version of the chromium snap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2038727/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1836616] Re: [snap] Upgrade from deb to snap forgets saved passwords
** Tags added: password-storage -- 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/1836616 Title: [snap] Upgrade from deb to snap forgets saved passwords Status in chromium-browser package in Ubuntu: Fix Released Bug description: On Ubuntu 19.10, when upgrading from the deb package to the snap¹, the password-manager-service interface is not auto-connected. As a result, chromium is unable to talk to org.freedesktop.Secret.Service over D-Bus, and it falls back to the basic unencrypted stored. See https://forum.snapcraft.io/t/auto-connecting-the-cups-control-and- password-manager-service-interfaces-for-the-chromium-snap/4592 for why auto-connection was denied for the password-manager-service interface. This is bad user experience, as the transition should be seamless. Aside of auto-connection, one possible solution would be to do the connection in the deb’s pre-install script (which installs the snap from the store, and is executed as root). That has pretty much the same security implications though, so it requires input from the security team before proceeding. Yet another solution would be for the wrapper script (/usr/bin/chromium-browser) to extract the stored passwords from the keyring and import them into the basic unencrypted sqlite store for the snap, but that feels clunky and fragile. Or a log message / dialog box at startup to inform the user that they should connect the interface manually. But that's not great UX, and doesn't provide a seamless transition. ¹ https://discourse.ubuntu.com/t/call-for-testing-chromium-browser-deb-to-snap-transition/11179 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1836616/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2038875] Re: Snap uses hardcoded key and salt for password and cookie encryption
*** This bug is a duplicate of bug 1836616 *** https://bugs.launchpad.net/bugs/1836616 Found the duplicate target; See there that the interface auto-connection was denied by Snap Store. ** This bug has been marked a duplicate of bug 1836616 [snap] Upgrade from deb to snap forgets saved passwords -- 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/2038875 Title: Snap uses hardcoded key and salt for password and cookie encryption Status in chromium-browser package in Ubuntu: New Bug description: A working Ubuntu install includes Gnome which includes the gnome- keyring. The snap version of Ubuntu does not make use of it. On an install of Debian with Gnome, the key ring is used. However, with Ubuntu everything is encrypted with the static key of peanuts and the salt of saltysalt, and openly accessible as sqlite databases in ~/snap/chromium/common/chromium, including passwords from the browser and the cookies. This should probably be fixed. If a laptop is physically compromised it's trivial to decrypt this with a tool like xbrowser. You can verify that gnome-libcrypt isn't chosen by default with --enable-logging=stderr --v=1 redirect stderr to a log and look for Crypt. You can see /why/ gnome-libcrypt isn't chosen with chromium --password-store=gnome-libcrypt --enable-logging=stderr --v=1 and again looking for messages with Crypt. I don't think this is a vulnerability per se, Chrome ships in Debian with the ability to use a basic store too. But it's an undesirable configuration and a regression from Debian when it's run on a platform with gnome and libsecret, and only doesn't work because of snap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2038875/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2038727] Re: Chromium snap theme parsing error
OK, I managed to reproduce the issue. > Proposition < Chromium loads a dark theme when it finds a theme but cannot read it. Chromium loads a light theme when it doesn't find a theme. I'll take a good guess that you cannot actually notice the visual difference between Adwaita and Adwaita-modified in Chromium — please confirm or deny this. Before, Chromium wouldn't even find Adwaita-modified and thus give you no error message, and would load a default, light theme, that you identify as "matching your system theme", as you can still observe by giving GTK_THEME=random-string in the command line. Now, due to changes in XDG_DATA_HOME, Chromium finds your Adwaita- modified, but cannot nonetheless read it due to snap confinement, and decides to load instead a dark theme regardless of your system settings. As to the why there is this behavior mismatch of loading a light theme in one case and a dark one in other, I don't know yet. ** Changed in: chromium-browser (Ubuntu) Status: New => Triaged ** Tags added: regression ** Changed in: chromium-browser (Ubuntu) Assignee: (unassigned) => Nathan Teodosio (nteodosio) -- 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/2038727 Title: Chromium snap theme parsing error Status in chromium-browser package in Ubuntu: Triaged Bug description: Chromium Version 117.0.5938.149 (Official Build) snap (64-bit) not following my GTK theme. Starting the Chromium snap from the terminal yields a theme parsing error: (chrome:95638): Gtk-WARNING **: 11:01:12.220: Theme parsing error: gtk.css:1:0: Failed to import: Error opening file /home/aej/.local/share/themes/Adwaita_modified/gtk-3.0/gtk.css: Permission denied Previous versions of the Chromium snap have not had this problem. Debian 11 + XFCE. I have been running the chromium snap for about two years without an issue like this on this system. I have reverted to the previous version of the chromium snap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2038727/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967632] Re: [snap] apparmor denied when trying to load pkcs11 module for smart card authentication
Can you ascertain if your smart card is supported by OpenSC? -- 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/1967632 Title: [snap] apparmor denied when trying to load pkcs11 module for smart card authentication Status in Mozilla Firefox: Confirmed Status in chromium-browser package in Ubuntu: In Progress Status in firefox package in Ubuntu: Triaged Bug description: I use a smart card to access government sites. I have that working in firefox and chrome on ubuntu impish, and gave jammy a try, but there firefox won't load the library, giving me a generic error. dmesg, however, shows this apparmor denied message: [sáb abr 2 17:32:27 2022] audit: type=1400 audit(1648931547.646:115): apparmor="DENIED" operation="file_mmap" profile="snap.firefox.firefox" name="/run/user/1000/doc/e0bac853/libaetpkss.so.3.5.4112" pid=3680 comm="firefox" requested_mask="m" denied_mask="m" fsuid=1000 ouid=0 Note also the path, that's not what I typed into the firefox dialog box. I have the .so copied to /usr/lib/x86_64-linux-gnu/libaetpkss.so.3.5.4112, and that's what I typed in when prompted for its path by firefox. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 2 17:34:09 2022 InstallationDate: Installed on 2022-03-20 (13 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220319) Snap.Changes: no changes found SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1967632/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 2039187] Re: Thunderbird doesn't accept URI attachments anymore
Hi Lucas, thanks for having a look. > Just to understand a bit better, is this bug affecting just Jammy? Any > other Ubuntu series? Please target the correct series in the bug. No, it goes all the way to Focal. The mention to Jammy was because in the upstream pull request the first version of the patch failed to build in Jammy. Sorry for the lack of clarity. I'm used to first having the patch to the development release uploaded and only then composing the SRU. Is that not the recommended procedure? > Apart from that, the packaging changes LGTM. I see there is an ongoing > discussion in your upstream PR, maybe it is a good idea to wait a bit to > see if the patch requires some changes. Sure, makes sense. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal-gtk in Ubuntu. https://bugs.launchpad.net/bugs/2039187 Title: Thunderbird doesn't accept URI attachments anymore Status in xdg-desktop-portal-gtk package in Ubuntu: Confirmed Bug description: The desktop portal constructs an mailto: url with an attachment= but thunderbird upstream explicitly decided to not allow adding files from an URL for security reasons. One can still use the -compose option though, as this patch does. Test case - * Install the proposed package. * Log out and back in. * Set Thunberbird as default client in Gnome Control Panel. * Open Nautilus and try to attach two files to the same email. They can be creatively named, it should not break on weird characters. * Thunderbird should open with the corresponding files attached. * [For regression testing] Set Evolution as the default. * Open Nautilus and try to attach two files to the same email. They can be creatively named, it should not break on weird characters. It only attaches one file, this is however not a regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/2039187/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2039701] Re: chromium freezes gnome if hardware acceleration is activated in browser setttings (U20.04) Intel HD-Grafik 4400
OK, hang on, the title claims that Gnome crashes if hardware acceleration is activated. You are now reporting problems also with it deactivated, right? > If its turned off then it is ok. But it crashed anyway when the indicator applet was showing incoming mail last time. With hardware acceleration turned off? > Now the gnome crashed as i resized a yt window, a had also strange glitches in the player if i maximized it but its rather rare. With hardware acceleration turned off? You apparently have an extension installed, is the problem reproducible with it uninstalled? Did you try reproducing the problem in a non- snapped version of the browser? For my future reference: The video issues here described are not related to hardware accelerated video decoding, as the user is in stable channel and, at the time of writing, only beta and edge channels have hardware accelerated video decoding. -- 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/2039701 Title: chromium freezes gnome if hardware acceleration is activated in browser setttings (U20.04) Intel HD-Grafik 4400 Status in chromium-browser package in Ubuntu: New Bug description: Ubuntu 20.04 have to deaktivate hardware acceleration in browser stetting in order to prevent delay and crash of chromium broswer and chrome browser. Was able to reboot with strg+alt+F(x) sudo reboot found line /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed in syslog when crash happened. Let me to this via gürgelschnüffel: vainfo libva info: VA-API version 1.7.0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_7 libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed libva info: va_openDriver() returns 1 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_6 libva info: va_openDriver() returns 0 vainfo: VA-API version: 1.7 (libva 2.6.0) vainfo: Driver version: Intel i965 driver for Intel(R) Haswell - 2.4.0 vainfo: Supported profile and entrypoints VAProfileMPEG2Simple: VAEntrypointVLD VAProfileMPEG2Simple: VAEntrypointEncSlice VAProfileMPEG2Main : VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointEncSlice VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileH264MultiviewHigh : VAEntrypointVLD VAProfileH264MultiviewHigh : VAEntrypointEncSlice VAProfileH264StereoHigh : VAEntrypointVLD VAProfileH264StereoHigh : VAEntrypointEncSlice VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main: VAEntrypointVLD VAProfileVC1Advanced: VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc VAProfileJPEGBaseline : VAEntrypointVLD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2039701/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2039187] Re: Thunderbird doesn't accept URI attachments anymore
** Patch removed: "xdg-deskop-portal-gtk2.diff" https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/2039187/+attachment/5709117/+files/xdg-deskop-portal-gtk2.diff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal-gtk in Ubuntu. https://bugs.launchpad.net/bugs/2039187 Title: Thunderbird doesn't accept URI attachments anymore Status in xdg-desktop-portal-gtk package in Ubuntu: Confirmed Status in xdg-desktop-portal-gtk source package in Focal: New Status in xdg-desktop-portal-gtk source package in Jammy: New Status in xdg-desktop-portal-gtk source package in Lunar: New Status in xdg-desktop-portal-gtk source package in Mantic: Confirmed Bug description: The desktop portal constructs an mailto: url with an attachment= but thunderbird upstream explicitly decided to not allow adding files from an URL for security reasons. One can still use the -compose option though, as this patch does. Test case - * Install the proposed package. * Log out and back in. * Set Thunberbird as default client in Gnome Control Panel. * Open Nautilus and try to attach two files to the same email. They can be creatively named, it should not break on weird characters. * Thunderbird should open with the corresponding files attached. * [For regression testing] Set Evolution as the default. * Open Nautilus and try to attach two files to the same email. They can be creatively named, it should not break on weird characters. It only attaches one file, this is however not a regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/2039187/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2019045] Re: [snap] New Ubuntu font with normal weight displayed as bold in Google Docs in Chromium after upgrading to Lunar
Workaround: apt install fonts-ubuntu- fonts-ubuntu-classic -- 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/2019045 Title: [snap] New Ubuntu font with normal weight displayed as bold in Google Docs in Chromium after upgrading to Lunar Status in chromium-browser package in Ubuntu: Triaged Status in fonts-ubuntu package in Ubuntu: Confirmed Bug description: I am experiencing a rendering regression after upgrading from Kinetic to Lunar. Google Docs using the Ubuntu font family are displayed incorrectly in Chromium: the normal weight font is rendered identically to the bold weight one, instead of being thicker than light and thinner than medium. Printing is also affected, unless I use Google Docs' download to PDF function, although that probably triggers a server-side rendering. This issue does not occur in Firefox or Google Chrome. One thing that may be relevant: if I force-refresh my test Google Doc I see all four Ubuntu font lines initially being rendered as bold. The light and medium lines are then re-rendered with the correct weight. It's as if bold was the default weight and the normal variant disappeared. As far as I can tell I was already running Chromium 112.0.5615.49 in Kinetic, and with Chromium being a snap I don't quite understand why the Ubuntu series would matter. I have also tried version 114.0.5735.16 (in latest/beta at the moment); the symptoms are identical. The attachments show the rendering error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2019045/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2019045] Re: [snap] New Ubuntu font with normal weight displayed as bold in Google Docs in Chromium after upgrading to Lunar
The new font relies on some different mechanism to determine the style of a given typeface, as each different style points to a same file. The old font doesn't do that. Maybe that could be tripping the resolution. ---> # ubuntu-fonts lrwxrwxrwx 1 root root 20 jun 21 10:35 UbuntuMono-B.ttf -> 'UbuntuMono[wght].ttf' lrwxrwxrwx 1 root root 27 jun 21 10:35 UbuntuMono-BI.ttf -> 'UbuntuMono-Italic[wght].ttf' -rw-r--r-- 1 root root 169K mar 24 2023 'UbuntuMono-Italic[wght].ttf' lrwxrwxrwx 1 root root 20 jun 21 10:35 UbuntuMono-R.ttf -> 'UbuntuMono[wght].ttf' lrwxrwxrwx 1 root root 27 jun 21 10:35 UbuntuMono-RI.ttf -> 'UbuntuMono-Italic[wght].ttf' -rw-r--r-- 1 root root 169K mar 24 2023 'UbuntuMono[wght].ttf' lrwxrwxrwx 1 root root 21 jun 21 10:35 Ubuntu-B.ttf -> 'Ubuntu[wdth,wght].ttf' lrwxrwxrwx 1 root root 28 jun 21 10:35 Ubuntu-BI.ttf -> 'Ubuntu-Italic[wdth,wght].ttf' lrwxrwxrwx 1 root root 21 jun 21 10:35 Ubuntu-C.ttf -> 'Ubuntu[wdth,wght].ttf' -rw-r--r-- 1 root root 664K jun 21 10:34 'Ubuntu-Italic[wdth,wght].ttf' lrwxrwxrwx 1 root root 21 jun 21 10:35 Ubuntu-L.ttf -> 'Ubuntu[wdth,wght].ttf' lrwxrwxrwx 1 root root 28 jun 21 10:35 Ubuntu-LI.ttf -> 'Ubuntu-Italic[wdth,wght].ttf' lrwxrwxrwx 1 root root 21 jun 21 10:35 Ubuntu-M.ttf -> 'Ubuntu[wdth,wght].ttf' lrwxrwxrwx 1 root root 28 jun 21 10:35 Ubuntu-MI.ttf -> 'Ubuntu-Italic[wdth,wght].ttf' lrwxrwxrwx 1 root root 21 jun 21 10:35 Ubuntu-R.ttf -> 'Ubuntu[wdth,wght].ttf' lrwxrwxrwx 1 root root 28 jun 21 10:35 Ubuntu-RI.ttf -> 'Ubuntu-Italic[wdth,wght].ttf' lrwxrwxrwx 1 root root 21 jun 21 10:35 Ubuntu-Th.ttf -> 'Ubuntu[wdth,wght].ttf' -rw-r--r-- 1 root root 1,1M jun 21 10:34 'Ubuntu[wdth,wght].ttf' # ubuntu-fonts-classic -rw-r--r-- 1 root root 187K set 26 2011 UbuntuMono-B.ttf -rw-r--r-- 1 root root 212K set 26 2011 UbuntuMono-BI.ttf -rw-r--r-- 1 root root 201K set 26 2011 UbuntuMono-R.ttf -rw-r--r-- 1 root root 206K set 26 2011 UbuntuMono-RI.ttf -rw-r--r-- 1 root root 326K jul 10 2015 Ubuntu-B.ttf -rw-r--r-- 1 root root 349K jul 10 2015 Ubuntu-BI.ttf -rw-r--r-- 1 root root 343K jul 10 2015 Ubuntu-C.ttf -rw-r--r-- 1 root root 406K jul 10 2015 Ubuntu-L.ttf -rw-r--r-- 1 root root 401K jul 10 2015 Ubuntu-LI.ttf -rw-r--r-- 1 root root 334K jul 10 2015 Ubuntu-M.ttf -rw-r--r-- 1 root root 359K jul 10 2015 Ubuntu-MI.ttf -rw-r--r-- 1 root root 346K jul 10 2015 Ubuntu-R.ttf -rw-r--r-- 1 root root 378K jul 10 2015 Ubuntu-RI.ttf -rw-r--r-- 1 root root 235K fev 18 2022 Ubuntu-Th.ttf <--- -- 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/2019045 Title: [snap] New Ubuntu font with normal weight displayed as bold in Google Docs in Chromium after upgrading to Lunar Status in chromium-browser package in Ubuntu: Triaged Status in fonts-ubuntu package in Ubuntu: Confirmed Bug description: I am experiencing a rendering regression after upgrading from Kinetic to Lunar. Google Docs using the Ubuntu font family are displayed incorrectly in Chromium: the normal weight font is rendered identically to the bold weight one, instead of being thicker than light and thinner than medium. Printing is also affected, unless I use Google Docs' download to PDF function, although that probably triggers a server-side rendering. This issue does not occur in Firefox or Google Chrome. One thing that may be relevant: if I force-refresh my test Google Doc I see all four Ubuntu font lines initially being rendered as bold. The light and medium lines are then re-rendered with the correct weight. It's as if bold was the default weight and the normal variant disappeared. As far as I can tell I was already running Chromium 112.0.5615.49 in Kinetic, and with Chromium being a snap I don't quite understand why the Ubuntu series would matter. I have also tried version 114.0.5735.16 (in latest/beta at the moment); the symptoms are identical. The attachments show the rendering error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2019045/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade
I see the bug is addressed, but for what it's worth, one more data point. I just run into the issue today when doing apt remove fonts-ubuntu* What I didn't notice was that a replacement instead of a removal was carried out fonts-ubuntu (0.83-6ubuntu1 => 0.869-0ubuntu1) After a while I turned back to Firefox — which I had set up to use Ubuntu font as default — and it had corrupted font. That was not during installation, it was my normal several months old Mantic environment. Restarting Firefox solved the problem. I can reproduce it with apt install fonts-ubuntu fonts-ubuntu-classic- ** Attachment added: "zalgo:firefox-right:chromium-left.png" https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2034986/+attachment/5712410/+files/zalgo%3Afirefox-right%3Achromium-left.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2034986 Title: some text became unreadable during a distribution upgrade Status in Cinnamon: New Status in Ubuntu MATE: New Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: In Progress Status in ubuntu-release-upgrader source package in Jammy: Fix Committed Status in ubuntu-release-upgrader source package in Lunar: Fix Released Status in ubuntu-meta source package in Mantic: Fix Released Status in ubuntu-release-upgrader source package in Mantic: In Progress Bug description: [ Impact ] * On Ubuntu Mate with the Lunar series, when running ubuntu-release-upgrader, the displayed font of running applications (including the upgrader) becomes very corrupted. * This is not just a display problem, it is also a functional one. The release upgrader will have text corrupted to the point where a dialog asks a decision, and displays two buttons, but the text is unreadable and one has to guess which button is the one that carries out their desired action. * In the early parts of the upgrader tool, users are told in bold: "To prevent data loss close all open applications and documents." This is just before the "Start Upgrade" button is available. But they may not do so. Many applications may have a corrupted font. * To address this, an additional environment variable is being passed along to pkexec, XDG_CURRENT_DESKTOP, as this is the critical criteria for making the Mate version of the fix work. * Also in the change are * an update to tests * from pre-build.sh * an update of the mirrors.cfg, adding and removing several mirrors * a refresh of the po files [ Test Plan ] * acquire an Ubuntu Mate environment running Ubuntu Lunar on amd64 * as user, run "update-manager -d" * monitor the "Distribution Upgrade" screen. During the "Installing the upgrades" step (and mind that this step will be long), observe the text of the "Distribution Upgrade" screen and verify that the font does not corrupt. * Repeat the above for Ubuntu Desktop [ Where problems could occur ] * We are changing, at release time, ubuntu-release upgrader. If we are careless, we could regress upgrades for a wider group of users than just Ubuntu Mate. That said, it is believed that passing the additional XDG_CURRENT_DESKTOP variable is relatively low risk. [ Other Info ] * TBD --- Original description: I was upgrading from Lunar to Mantic the other day and left a couple of applications open during the upgrade process. During the upgrade the text in audacious became unreadable (I'll attach a screenshot) and I seem to recall the title bar of Firefox being unreadable but the contents of web pages still being readable. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-release-upgrader-core 1:23.10.5 ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0 Uname: Linux 6.5.0-4-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Sep 8 15:39:27 2023 InstallationDate: Installed on 2018-08-10 (1855 days ago) InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago) VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 126: Error executing command as another user: Request dismissed VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490 To manage notifications about this bug go to:
[Desktop-packages] [Bug 2019045] Re: [snap] New Ubuntu font with normal weight displayed as bold in Google Docs in Chromium after upgrading to Lunar
Bold renders fine given simple CSS: Ubuntu. Ubuntu bold. This looks specific to Google Docs. ** Attachment added: "fonts.png" https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2019045/+attachment/5712423/+files/fonts.png -- 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/2019045 Title: [snap] New Ubuntu font with normal weight displayed as bold in Google Docs in Chromium after upgrading to Lunar Status in chromium-browser package in Ubuntu: Triaged Status in fonts-ubuntu package in Ubuntu: Confirmed Bug description: I am experiencing a rendering regression after upgrading from Kinetic to Lunar. Google Docs using the Ubuntu font family are displayed incorrectly in Chromium: the normal weight font is rendered identically to the bold weight one, instead of being thicker than light and thinner than medium. Printing is also affected, unless I use Google Docs' download to PDF function, although that probably triggers a server-side rendering. This issue does not occur in Firefox or Google Chrome. One thing that may be relevant: if I force-refresh my test Google Doc I see all four Ubuntu font lines initially being rendered as bold. The light and medium lines are then re-rendered with the correct weight. It's as if bold was the default weight and the normal variant disappeared. As far as I can tell I was already running Chromium 112.0.5615.49 in Kinetic, and with Chromium being a snap I don't quite understand why the Ubuntu series would matter. I have also tried version 114.0.5735.16 (in latest/beta at the moment); the symptoms are identical. The attachments show the rendering error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2019045/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2019045] Re: [snap] New Ubuntu font with normal weight displayed as bold in Google Docs in Chromium after upgrading to Lunar
More information dump:
* It's easier to see the error Andreas mentioned with --enable-
logging=stderr:
--->
[246126:246235:1023/123348.818876:WARNING:obfuscated_file_util.cc(1323)] Failed
to get origin+type directory: { uri:
filesystem:https://docs.google.com/persistent/docs/fonts/4iCv6KVjbNBYlgoCxCvTsg.woff2,
storage key: { origin: https://docs.google.com, top-level site:
https://google.com, nonce: , ancestor chain bit: Same-Site } } error:-4
[246126:246235:1023/123348.818941:WARNING:obfuscated_file_util.cc(1323)] Failed
to get origin+type directory: { uri:
filesystem:https://docs.google.com/persistent/docs/fonts/4iCp6KVjbNBYlgoKejZPsmyN.woff2,
storage key: { origin: https://docs.google.com, top-level site:
https://google.com, nonce: , ancestor chain bit: Same-Site } } error:-4
<---
I don't quite understand the process there, an uneducated guess: It is
trying to fetch a font and then storing it using the filesystem API —
which would save it in snap/chromium/common/chromium/Default/File\
Systems but that directory doesn't even exist. Maybe Firefox's
implementation differs from Chromium's critically enough to hit this
bug. Disabling that with --disable-file-system has no effect.
* Docs uses a remote font instead of a system font because --disable-
remote-fonts prevents the Ubuntu font from loading despite it still
being listed (the 't' character is a giveaway). This is in line with the
error message.
* Since we don't get the problem in Firefox, I tried switching the user
agent to Firefox just to see if behavior changed; it didn't.
--
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/2019045
Title:
[snap] New Ubuntu font with normal weight displayed as bold in Google
Docs in Chromium after upgrading to Lunar
Status in chromium-browser package in Ubuntu:
Triaged
Status in fonts-ubuntu package in Ubuntu:
Confirmed
Bug description:
I am experiencing a rendering regression after upgrading from Kinetic to
Lunar.
Google Docs using the Ubuntu font family are displayed incorrectly in
Chromium: the normal weight font is rendered identically to the bold weight
one, instead of being thicker than light and thinner than medium.
Printing is also affected, unless I use Google Docs' download to PDF
function, although that probably triggers a server-side rendering.
This issue does not occur in Firefox or Google Chrome.
One thing that may be relevant: if I force-refresh my test Google Doc
I see all four Ubuntu font lines initially being rendered as bold. The
light and medium lines are then re-rendered with the correct weight.
It's as if bold was the default weight and the normal variant
disappeared.
As far as I can tell I was already running Chromium 112.0.5615.49 in
Kinetic, and with Chromium being a snap I don't quite understand why
the Ubuntu series would matter.
I have also tried version 114.0.5735.16 (in latest/beta at the
moment); the symptoms are identical.
The attachments show the rendering error.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2019045/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2038727] Re: Chromium snap theme parsing error
It's built now, please have a look if it fixes the issue now. -- 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/2038727 Title: Chromium snap theme parsing error Status in chromium-browser package in Ubuntu: Fix Committed Bug description: Chromium Version 117.0.5938.149 (Official Build) snap (64-bit) not following my GTK theme. Starting the Chromium snap from the terminal yields a theme parsing error: (chrome:95638): Gtk-WARNING **: 11:01:12.220: Theme parsing error: gtk.css:1:0: Failed to import: Error opening file /home/aej/.local/share/themes/Adwaita_modified/gtk-3.0/gtk.css: Permission denied Previous versions of the Chromium snap have not had this problem. Debian 11 + XFCE. I have been running the chromium snap for about two years without an issue like this on this system. I have reverted to the previous version of the chromium snap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2038727/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1843392] Re: [snap] smart card reader no longer works
*** This bug is a duplicate of bug 1967632 *** https://bugs.launchpad.net/bugs/1967632 Hi Pascal, not sure you receive notifications for the duplicate, but in LP:1967632 I have released a tentative fix with a test case. -- 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/1843392 Title: [snap] smart card reader no longer works Status in Mozilla Firefox: Confirmed Status in chromium-browser package in Ubuntu: In Progress Status in firefox package in Ubuntu: Confirmed Bug description: chromium uses the Netscape Cryptographic Module to access smartcards for authentication purposes. This stopped working when switching to the snap version. Chromium would normally access the setup in ~/.pki/nssdb/pkcs11.txt That file would refer to a library used to access the smart card. I.e /usr/lib/x86_64-linux-gnu/pkcs11/opensc- pkcs11.so The problem can be bypassed by manually launching chromium via: /snap/chromium/current/usr/lib/chromium-browser/chrome To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1843392/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
