[Desktop-packages] [Bug 1979412] Re: [snap] Chromium crashes when downloading
Thanks for the feedback. Let's consider this bug fixed. Feel free to re- open if the problem occurs again. ** Changed in: chromium-browser (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/1979412 Title: [snap] Chromium crashes when downloading Status in chromium-browser package in Ubuntu: Fix Released Bug description: For a couple of weeks, I observe random crashes of Chromium when you click on a link that starts a non-HTML download (e.g. PDF or an MS Excel file). After restarting Chromium and restoring the tabs, a second click on the link starts the download without problems, probably because this issue is not 100% reproducible in the first place. Observed with Chromium 102.0.5005.115 (officiel build) snap (64-Bit) on Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1979412/+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 1979412] Re: [snap] Chromium crashes when downloading
I don’t observe them any more. It has never been really well reproducible but I tend to think that the problem is gone. -- 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/1979412 Title: [snap] Chromium crashes when downloading Status in chromium-browser package in Ubuntu: Incomplete Bug description: For a couple of weeks, I observe random crashes of Chromium when you click on a link that starts a non-HTML download (e.g. PDF or an MS Excel file). After restarting Chromium and restoring the tabs, a second click on the link starts the download without problems, probably because this issue is not 100% reproducible in the first place. Observed with Chromium 102.0.5005.115 (officiel build) snap (64-Bit) on Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1979412/+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 1984031] [NEW] The username 'at' cannot list on logon screen
Public bug reported: OS: Ubuntu 20.04.x LTS (Desktop) Problem description: When I try to use 'at' as my username, after rebooting, gnome-initial-setup reappears and asks to create a new user. Re-produce procedures (1): 1. Del all other users from terminal 2. Reboot to OS. 3. Add a user by gnome-initial-setup dialog. 4. Use 'at' as username and login name. 5. After setup finish, reboot. 6. When boot to OS, gnome-initial-setup will pop again for asking create a new user. Re-produce procedures (2): 1. Create a user (e.g. username is 'user') 2. Check this user account can be showed on the logon screen and can login into OS. 3. Logout 'user' account and swith to terminal to modify the account with root permission. 4. Modify account 'user' to 'at' 5. After finish, reboot 6. When boot to OS, gnome-initial-setup will pop again for asking create a new user. 7. At this moment, switch to terminal with root permission 8. Modify account 'at' to 'am' and reboot 9. After boot to OS, gnome-initial-setup doesn't pop up and account 'am' is showed on logon screen. Is this a bug or 'at' is a reserved word? I can't find any document relevant about this restriction. ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: gdm3 logon username ** Summary changed: - Some username cannot list on logon screen + The username 'at' cannot list on logon screen -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1984031 Title: The username 'at' cannot list on logon screen Status in gdm3 package in Ubuntu: New Bug description: OS: Ubuntu 20.04.x LTS (Desktop) Problem description: When I try to use 'at' as my username, after rebooting, gnome-initial-setup reappears and asks to create a new user. Re-produce procedures (1): 1. Del all other users from terminal 2. Reboot to OS. 3. Add a user by gnome-initial-setup dialog. 4. Use 'at' as username and login name. 5. After setup finish, reboot. 6. When boot to OS, gnome-initial-setup will pop again for asking create a new user. Re-produce procedures (2): 1. Create a user (e.g. username is 'user') 2. Check this user account can be showed on the logon screen and can login into OS. 3. Logout 'user' account and swith to terminal to modify the account with root permission. 4. Modify account 'user' to 'at' 5. After finish, reboot 6. When boot to OS, gnome-initial-setup will pop again for asking create a new user. 7. At this moment, switch to terminal with root permission 8. Modify account 'at' to 'am' and reboot 9. After boot to OS, gnome-initial-setup doesn't pop up and account 'am' is showed on logon screen. Is this a bug or 'at' is a reserved word? I can't find any document relevant about this restriction. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1984031/+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 1983529] Re: No sound after upgrade to prerelease Kinetic (Thinkpad X1E Gen 4)
*** This bug is a duplicate of bug 1979113 *** https://bugs.launchpad.net/bugs/1979113 This was fixed by installing wireplumber, so I think it's a duplicate of https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1979113 ** This bug has been marked a duplicate of bug 1979113 Kinetic sound disappeared after today updates -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1983529 Title: No sound after upgrade to prerelease Kinetic (Thinkpad X1E Gen 4) Status in alsa-driver package in Ubuntu: New Bug description: Not sure if it's relevant, but there are some errors in dmesg: $ sudo dmesg | grep audio [ 14.290226] snd_hda_intel :01:00.1: Handle vga_switcheroo audio client [ 14.440430] sof-audio-pci-intel-tgl :00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100 [ 14.445129] sof-audio-pci-intel-tgl :00:1f.3: Digital mics found on Skylake+ platform, using SOF driver [ 14.445811] sof-audio-pci-intel-tgl :00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040100 [ 14.445861] sof-audio-pci-intel-tgl :00:1f.3: init of i915 and HDMI codec failed [ 14.448966] sof-audio-pci-intel-tgl :00:1f.3: use msi interrupt mode [ 15.467232] sof-audio-pci-intel-tgl :00:1f.3: codec #2 probe error, ret: -5 [ 15.467478] sof-audio-pci-intel-tgl :00:1f.3: hda codecs found, mask 1 [ 15.467479] sof-audio-pci-intel-tgl :00:1f.3: using HDA machine driver skl_hda_dsp_generic now [ 15.467484] sof-audio-pci-intel-tgl :00:1f.3: DMICs detected in NHLT tables: 2 [ 15.478062] sof-audio-pci-intel-tgl :00:1f.3: Firmware info: version 2:1:1-3964a [ 15.478066] sof-audio-pci-intel-tgl :00:1f.3: Firmware: ABI 3:21:0 Kernel ABI 3:18:0 [ 15.478068] sof-audio-pci-intel-tgl :00:1f.3: warn: FW ABI is more recent than kernel [ 15.478073] sof-audio-pci-intel-tgl :00:1f.3: unknown sof_ext_man header type 3 size 0x30 [ 15.584074] sof-audio-pci-intel-tgl :00:1f.3: Firmware info: version 2:1:1-3964a [ 15.584079] sof-audio-pci-intel-tgl :00:1f.3: Firmware: ABI 3:21:0 Kernel ABI 3:18:0 [ 15.584080] sof-audio-pci-intel-tgl :00:1f.3: warn: FW ABI is more recent than kernel [ 15.591457] sof-audio-pci-intel-tgl :00:1f.3: Topology: ABI 3:21:0 Kernel ABI 3:18:0 [ 15.591461] sof-audio-pci-intel-tgl :00:1f.3: warn: topology ABI is more recent than kernel [ 15.624250] sof-audio-pci-intel-tgl :00:1f.3: ASoC: Parent card not yet available, widget card binding deferred [ 15.643720] snd_hda_codec_realtek ehdaudio0D0: autoconfig for ALC287: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker [ 15.643726] snd_hda_codec_realtek ehdaudio0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 15.643727] snd_hda_codec_realtek ehdaudio0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [ 15.643728] snd_hda_codec_realtek ehdaudio0D0:mono: mono_out=0x0 [ 15.643729] snd_hda_codec_realtek ehdaudio0D0:inputs: [ 15.643730] snd_hda_codec_realtek ehdaudio0D0: Mic=0x19 Because of those ABI warnings, I tried building the latest mainline kernel from source, and the ABI warnings went away, but I still have no sound. $ sudo dmesg | grep audio # On latest upstream kernel [ 17.519958] snd_hda_intel :01:00.1: Handle vga_switcheroo audio client [ 17.804900] sof-audio-pci-intel-tgl :00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100 [ 17.805661] sof-audio-pci-intel-tgl :00:1f.3: Digital mics found on Skylake+ platform, using SOF driver [ 17.806225] sof-audio-pci-intel-tgl :00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040100 [ 17.806265] sof-audio-pci-intel-tgl :00:1f.3: init of i915 and HDMI codec failed [ 17.808071] sof-audio-pci-intel-tgl :00:1f.3: use msi interrupt mode [ 21.844005] sof-audio-pci-intel-tgl :00:1f.3: codec #2 probe error, ret: -5 [ 21.844263] sof-audio-pci-intel-tgl :00:1f.3: hda codecs found, mask 1 [ 21.844264] sof-audio-pci-intel-tgl :00:1f.3: using HDA machine driver skl_hda_dsp_generic now [ 21.844267] sof-audio-pci-intel-tgl :00:1f.3: DMICs detected in NHLT tables: 2 [ 21.853970] sof-audio-pci-intel-tgl :00:1f.3: Firmware info: version 2:1:1-3964a [ 21.853971] sof-audio-pci-intel-tgl :00:1f.3: Firmware: ABI 3:21:0 Kernel ABI 3:21:0 [ 21.853979] sof-audio-pci-intel-tgl :00:1f.3: unknown sof_ext_man header type 3 size 0x30 [ 21.961252] sof-audio-pci-intel-tgl :00:1f.3: Firmware info: version 2:1:1-3964a [ 21.961255] sof-audio-pci-intel-tgl :00:1f.3: Firmware: ABI 3:21:0 Kernel ABI 3:21:0 [ 21.967719] sof-audio-pci-intel-tgl :00:1f.3: Topology: ABI 3:21:0 Kernel ABI 3:21:0 [ 21.979145] snd_hda_codec_realtek ehdaudio0D0: autoconfig for ALC287: line_outs=1
[Desktop-packages] [Bug 1453819] Re: transmission-cli always saves to ~/Downloads
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: transmission (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1453819 Title: transmission-cli always saves to ~/Downloads Status in transmission package in Ubuntu: Confirmed Bug description: Even when given a specific path with the -w switch, transmission-cli always insists on saving the download to ~/Downloads, which is really annoying when that fs does not have room. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1453819/+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 1983998] Re: USB sound card not detected
Unfortunately, from what I'm reading in the description and logs, it appears as though this USB device isn't "standards compliant", meaning it reports values outside of the standard range that Apple created and Linux adopted for audio devices to be driverless. I'm seeing these warnings: > Warning! Unlikely big volume range (=496), cval->res is probably wrong. > Warning! Unlikely big volume range (=1008), cval->res is probably wrong. This is something we don't see on compatible audio devices with the Linux kernel. Basically, this means the USB-C lavalier microphones you bought, while they work with Windows, likely don't work without special tweaking in either macOS or Linux. Unfortunately, because of this, that means they're in a very narrow set of audio devices that are not supported. As an audio expert myself (leader of Ubuntu Studio, 28 years in production and professional audio), I'd suggest getting a good set of regular lavalier microphones and a decent audio interface. You'll likely run into trouble by using an all-in-one USB lavalier microphone. For further support, consult appropriate forums as bug trackers are no place for support. ** Changed in: alsa-driver (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1983998 Title: USB sound card not detected Status in alsa-driver package in Ubuntu: Invalid Bug description: usbc mics https://www.boya-mic.com/lavaliermicrophones/1430.html connects and immediately disconnects, ls usb hangs for a while, when usbc device is connected. it works on win laptop well. ``` [10877.622942] usb 3-4: new full-speed USB device number 28 using xhci_hcd [10877.779590] usb 3-4: New USB device found, idVendor=0c76, idProduct=153f, bcdDevice= 1.00 [10877.779596] usb 3-4: New USB device strings: Mfr=0, Product=1, SerialNumber=0 [10877.779599] usb 3-4: Product: USB PnP Audio Device [10877.983589] usb 3-4: Warning! Unlikely big volume range (=496), cval->res is probably wrong. [10877.983593] usb 3-4: [51] FU [Mic Playback Volume] ch = 1, val = 0/7936/16 [10878.009593] usb 3-4: Warning! Unlikely big volume range (=1008), cval->res is probably wrong. [10878.009597] usb 3-4: [49] FU [Speaker Playback Volume] ch = 2, val = -16129/-1/16 [10878.035587] usb 3-4: Warning! Unlikely big volume range (=496), cval->res is probably wrong. [10878.035591] usb 3-4: [50] FU [Mic Capture Volume] ch = 1, val = 0/7936/16 [10878.038757] input: USB PnP Audio Device as /devices/pci:00/:00:01.2/:02:00.0/:03:08.0/:06:00.3/usb3/3-4/3-4:1.3/0003:0C76:153F.001B/input/input45 [10878.095081] hid-generic 0003:0C76:153F.001B: input,hidraw6: USB HID v1.00 Device [USB PnP Audio Device] on usb-:06:00.3-4/input3 [10878.095179] usb 3-3: USB disconnect, device number 27 [10878.426945] usb 3-3: new full-speed USB device number 29 using xhci_hcd [10878.587590] usb 3-3: New USB device found, idVendor=0c76, idProduct=153f, bcdDevice= 1.00 [10878.587597] usb 3-3: New USB device strings: Mfr=0, Product=1, SerialNumber=0 [10878.587599] usb 3-3: Product: USB PnP Audio Device [10878.783592] usb 3-3: Warning! Unlikely big volume range (=496), cval->res is probably wrong. [10878.783597] usb 3-3: [51] FU [Mic Playback Volume] ch = 1, val = 0/7936/16 [10878.809597] usb 3-3: Warning! Unlikely big volume range (=1008), cval->res is probably wrong. [10878.809601] usb 3-3: [49] FU [Speaker Playback Volume] ch = 2, val = -16129/-1/16 [10878.835592] usb 3-3: Warning! Unlikely big volume range (=496), cval->res is probably wrong. [10878.835596] usb 3-3: [50] FU [Mic Capture Volume] ch = 1, val = 0/7936/16 [10878.838754] input: USB PnP Audio Device as /devices/pci:00/:00:01.2/:02:00.0/:03:08.0/:06:00.3/usb3/3-3/3-3:1.3/0003:0C76:153F.001C/input/input46 [10878.895092] hid-generic 0003:0C76:153F.001C: input,hidraw5: USB HID v1.00 Device [USB PnP Audio Device] on usb-:06:00.3-3/input3 [10878.895190] usb 3-4: USB disconnect, device number 28 ``` ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-45.48-generic 5.15.39 Uname: Linux 5.15.0-45-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: vany 12211 F pulseaudio /dev/snd/controlC0: vany 12211 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Aug 8 18:28:32 2022 InstallationDate: Installed on 2020-11-26 (619 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: USB sound card not detected
[Desktop-packages] [Bug 1981163] Re: [upstream] In Compose window, if a PDf is joined and clicked to open, Thunderbird launches Firefox instead of Evince
Launchpad has imported 37 comments from the remote bug at https://bugzilla.mozilla.org/show_bug.cgi?id=1698140. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2021-03-12T17:01:32+00:00 9-henry wrote: ## Steps to Reproduce Compose or Edit a message with a pdf attachment. Open the pdf attachment (through double click or context menu). ## Result Get popup message ``` You have chosen to open: .pdf which is: HTML document ``` So the type is HTML, which means you'll likely get a recommendation to open in a browser, rather than the default pdf reader. Also get the printed error message ``` JavaScript error: resource://pdf.js/PdfStreamConverter.jsm, line 140: TypeError: can't access property "getInterface", requestor is null ``` *Note: opening attachments when viewing a message (not composition), in either a tab or a separate window works fine.* ## Expected The file to be treated as a PDF and no error message. ## Origin? Looking in `PdfStreamConverter.jsm`, the error is from `getDOMWindow` (https://searchfox.org/mozilla- central/rev/9ae77e4ce3378bd683ac9a86b729ea6b6bd22cb8/toolkit/components/pdfjs/content/PdfStreamConverter.jsm#136), which is called by `proxy.onStopRequest`. The problem seems to be that both `aChannel.notificationCallbacks` and `aChannel.loadGroup.notificationCallbacks` are `null`. *Note: opening an attachment in a viewed message (not composing), does not seem to pass through the same code.* On the the thunderbird side, I've tracked down the trigger for the error to `openURI` in `MsgComposeCommands.js` (https://searchfox.org/comm- central/rev/9bc3ba1480090c4e89d5152e458f19c79b3d6ac4/mail/components/compose/content/MsgComposeCommands.js#7171). I couldn't really pinpoint the origin much beyond this because the code is passing through interfaces (and probably between c++ and javascript), and I'm not familiar enough to navigate this. Why is it treated as HTML instead? I think the reason the document is treated as as HTML is a side effect of the JavaScript error. Also in `PdfStreamConverter.jsm`, the `onStartRequest` method changes the `contentType` from `application/pdf` to `text/html` (https://searchfox.org/mozilla- central/rev/9ae77e4ce3378bd683ac9a86b729ea6b6bd22cb8/toolkit/components/pdfjs/content/PdfStreamConverter.jsm#1231). Supposedly, this is done to break some loop. My guess is that it is meant to be set back to `application/pdf` during `onStopRequest`, but this method errors before it can do so. Reply at: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1981163/comments/0 On 2021-10-14T11:09:08+00:00 9-henry wrote: Note: The patch for bug 1734428 fixes the case where the user has opted to view pdfs within Thunderbird and they still have a 3pane window open. In other cases, this bug will still be seen (error in console, and treated as a `text/html` instead of `application/pdf`). E.g. if you choose to view pdfs using your system document viewer, or if you only have open a single composition window. Reply at: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1981163/comments/1 On 2021-10-25T11:36:33+00:00 9-henry wrote: *** Bug 1737408 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1981163/comments/2 On 2021-10-25T11:40:11+00:00 9-henry wrote: *** Bug 1735585 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1981163/comments/3 On 2021-10-27T13:45:00+00:00 Mkmelin+mozilla wrote: *** Bug 1732045 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1981163/comments/4 On 2021-11-12T07:48:27+00:00 Mkmelin+mozilla wrote: *** Bug 1740759 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1981163/comments/5 On 2021-11-12T15:43:50+00:00 Wls220spring wrote: *** Bug 1729922 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1981163/comments/6 On 2021-11-13T15:01:39+00:00 Anjeyelf wrote: Windows 10 Computer default open pdf using Adobe Acrobat Thunderbird
[Desktop-packages] [Bug 1983372] Re: gnome-desktop 43 transition tracking bug
** Changed in: gnome-desktop (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1983372 Title: gnome-desktop 43 transition tracking bug Status in gnome-desktop package in Ubuntu: Fix Released Bug description: Here's a transition coordination bug https://people.canonical.com/~ubuntu-archive/transitions/html/auto- gnome-desktop.html The gnome-desktop library has a fairly strict dependency on gnome- desktop3-data. That means we can't "smoothly" migrate the library out of kinetic-proposed. The migration will happen all at once, when everything is done. - Remove gnome-books LP: #1983267 - Remove kylin-greeter LP: #1983369 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop/+bug/1983372/+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 1981163] Re: In Compose window, if a PDf is joined and clicked to open, Thunderbird launches Firefox instead of Evince
** Also affects: thunderbird via https://bugzilla.mozilla.org/show_bug.cgi?id=1698140 Importance: Unknown Status: Unknown ** Tags added: upstream ** Summary changed: - In Compose window, if a PDf is joined and clicked to open, Thunderbird launches Firefox instead of Evince + [upstream] In Compose window, if a PDf is joined and clicked to open, Thunderbird launches Firefox instead of Evince ** Changed in: thunderbird (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1981163 Title: [upstream] In Compose window, if a PDf is joined and clicked to open, Thunderbird launches Firefox instead of Evince Status in Mozilla Thunderbird: Unknown Status in thunderbird package in Ubuntu: Confirmed Bug description: In Thunderbird on Ubuntu Gnome, I set Evince as default program to open pdf files from Thunderbird. In received messages, and those saved on "Sent" folder, it works perfectly. But in the "Compose" window: if I add a pdf file to the message, and double-click on it to open and verify it, Thunderbird always uses Firefox to show it. In case Firefox is not installed (has been removed), I have an error message telling there is not associated application for pdf files and to go to Preferences - where Evince is already and still defined as default. It happens since many months and bug is still present in Thunderbird 102 / Ubuntu 22.10 beta. It's not the same as bug 234349 as here, it's not an URL file but directly a pdf joined in a mail. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1981163/+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 1983660] Re: Chromium seems to drive all data into swap, until choking
Thanks for the feedback. I'm marking this bug invalid as it doesn't appear to be a bug in the chromium package itself. Feel free to follow up with the developers of that extension. ** Changed in: chromium-browser (Ubuntu) Status: Incomplete => Invalid -- 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/1983660 Title: Chromium seems to drive all data into swap, until choking Status in chromium-browser package in Ubuntu: Invalid Bug description: For the last day(s) my machine runs Chrome very very slow and sluggish until it stops reacting at all. I haven't done any changes except of the daily updates and snap refresh. What I found out, is that the memory space used is almost immediately the swap space. Same after cold boot: it starts pretty usual, but soon almost all memory data seem to be sent into swap space, despite of RAM being available. (See attachment, taken shortly before total non-reaction. CPU isn't very busy, RAM is aplenty.) Swappiness is okay at 60. I very much suspect Chrome, since when using Firefox, with my (in Chrome) usual sites, everything looks fine, it doesn't choke, and the swap space used is almost negligible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1983660/+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 1981186] Re: Thunderbird 102 : keeps an empty window even if all calendar alarms closed
** Changed in: thunderbird (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1981186 Title: Thunderbird 102 : keeps an empty window even if all calendar alarms closed Status in thunderbird package in Ubuntu: Fix Released Bug description: Since Thunderbird 102 (deb version on Ubuntu 22.10), a new bug appeared on calendar : when a window opens with many alarm reminders, after having reported or closed all of them, it remains an empty window with "0 reminder" title, instead of closing the floating window as before. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1981186/+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 1981163] Re: In Compose window, if a PDf is joined and clicked to open, Thunderbird launches Firefox instead of Evince
Duplicate of upstream bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1698140 ** Bug watch added: Mozilla Bugzilla #1698140 https://bugzilla.mozilla.org/show_bug.cgi?id=1698140 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1981163 Title: In Compose window, if a PDf is joined and clicked to open, Thunderbird launches Firefox instead of Evince Status in thunderbird package in Ubuntu: New Bug description: In Thunderbird on Ubuntu Gnome, I set Evince as default program to open pdf files from Thunderbird. In received messages, and those saved on "Sent" folder, it works perfectly. But in the "Compose" window: if I add a pdf file to the message, and double-click on it to open and verify it, Thunderbird always uses Firefox to show it. In case Firefox is not installed (has been removed), I have an error message telling there is not associated application for pdf files and to go to Preferences - where Evince is already and still defined as default. It happens since many months and bug is still present in Thunderbird 102 / Ubuntu 22.10 beta. It's not the same as bug 234349 as here, it's not an URL file but directly a pdf joined in a mail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1981163/+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 1983998] Re: USB sound card not detected
** Package changed: ubuntu => alsa-driver (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1983998 Title: USB sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: usbc mics https://www.boya-mic.com/lavaliermicrophones/1430.html connects and immediately disconnects, ls usb hangs for a while, when usbc device is connected. it works on win laptop well. ``` [10877.622942] usb 3-4: new full-speed USB device number 28 using xhci_hcd [10877.779590] usb 3-4: New USB device found, idVendor=0c76, idProduct=153f, bcdDevice= 1.00 [10877.779596] usb 3-4: New USB device strings: Mfr=0, Product=1, SerialNumber=0 [10877.779599] usb 3-4: Product: USB PnP Audio Device [10877.983589] usb 3-4: Warning! Unlikely big volume range (=496), cval->res is probably wrong. [10877.983593] usb 3-4: [51] FU [Mic Playback Volume] ch = 1, val = 0/7936/16 [10878.009593] usb 3-4: Warning! Unlikely big volume range (=1008), cval->res is probably wrong. [10878.009597] usb 3-4: [49] FU [Speaker Playback Volume] ch = 2, val = -16129/-1/16 [10878.035587] usb 3-4: Warning! Unlikely big volume range (=496), cval->res is probably wrong. [10878.035591] usb 3-4: [50] FU [Mic Capture Volume] ch = 1, val = 0/7936/16 [10878.038757] input: USB PnP Audio Device as /devices/pci:00/:00:01.2/:02:00.0/:03:08.0/:06:00.3/usb3/3-4/3-4:1.3/0003:0C76:153F.001B/input/input45 [10878.095081] hid-generic 0003:0C76:153F.001B: input,hidraw6: USB HID v1.00 Device [USB PnP Audio Device] on usb-:06:00.3-4/input3 [10878.095179] usb 3-3: USB disconnect, device number 27 [10878.426945] usb 3-3: new full-speed USB device number 29 using xhci_hcd [10878.587590] usb 3-3: New USB device found, idVendor=0c76, idProduct=153f, bcdDevice= 1.00 [10878.587597] usb 3-3: New USB device strings: Mfr=0, Product=1, SerialNumber=0 [10878.587599] usb 3-3: Product: USB PnP Audio Device [10878.783592] usb 3-3: Warning! Unlikely big volume range (=496), cval->res is probably wrong. [10878.783597] usb 3-3: [51] FU [Mic Playback Volume] ch = 1, val = 0/7936/16 [10878.809597] usb 3-3: Warning! Unlikely big volume range (=1008), cval->res is probably wrong. [10878.809601] usb 3-3: [49] FU [Speaker Playback Volume] ch = 2, val = -16129/-1/16 [10878.835592] usb 3-3: Warning! Unlikely big volume range (=496), cval->res is probably wrong. [10878.835596] usb 3-3: [50] FU [Mic Capture Volume] ch = 1, val = 0/7936/16 [10878.838754] input: USB PnP Audio Device as /devices/pci:00/:00:01.2/:02:00.0/:03:08.0/:06:00.3/usb3/3-3/3-3:1.3/0003:0C76:153F.001C/input/input46 [10878.895092] hid-generic 0003:0C76:153F.001C: input,hidraw5: USB HID v1.00 Device [USB PnP Audio Device] on usb-:06:00.3-3/input3 [10878.895190] usb 3-4: USB disconnect, device number 28 ``` ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-45.48-generic 5.15.39 Uname: Linux 5.15.0-45-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: vany 12211 F pulseaudio /dev/snd/controlC0: vany 12211 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Aug 8 18:28:32 2022 InstallationDate: Installed on 2020-11-26 (619 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: USB sound card not detected UpgradeStatus: Upgraded to jammy on 2022-05-23 (76 days ago) dmi.bios.date: 04/01/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1407 dmi.board.asset.tag: Default string dmi.board.name: TUF GAMING X570-PLUS (WI-FI) dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1407:bd04/01/2020:br5.14:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS(WI-FI):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1983998/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 1983998] [NEW] USB sound card not detected
You have been subscribed to a public bug: usbc mics https://www.boya-mic.com/lavaliermicrophones/1430.html connects and immediately disconnects, ls usb hangs for a while, when usbc device is connected. it works on win laptop well. ``` [10877.622942] usb 3-4: new full-speed USB device number 28 using xhci_hcd [10877.779590] usb 3-4: New USB device found, idVendor=0c76, idProduct=153f, bcdDevice= 1.00 [10877.779596] usb 3-4: New USB device strings: Mfr=0, Product=1, SerialNumber=0 [10877.779599] usb 3-4: Product: USB PnP Audio Device [10877.983589] usb 3-4: Warning! Unlikely big volume range (=496), cval->res is probably wrong. [10877.983593] usb 3-4: [51] FU [Mic Playback Volume] ch = 1, val = 0/7936/16 [10878.009593] usb 3-4: Warning! Unlikely big volume range (=1008), cval->res is probably wrong. [10878.009597] usb 3-4: [49] FU [Speaker Playback Volume] ch = 2, val = -16129/-1/16 [10878.035587] usb 3-4: Warning! Unlikely big volume range (=496), cval->res is probably wrong. [10878.035591] usb 3-4: [50] FU [Mic Capture Volume] ch = 1, val = 0/7936/16 [10878.038757] input: USB PnP Audio Device as /devices/pci:00/:00:01.2/:02:00.0/:03:08.0/:06:00.3/usb3/3-4/3-4:1.3/0003:0C76:153F.001B/input/input45 [10878.095081] hid-generic 0003:0C76:153F.001B: input,hidraw6: USB HID v1.00 Device [USB PnP Audio Device] on usb-:06:00.3-4/input3 [10878.095179] usb 3-3: USB disconnect, device number 27 [10878.426945] usb 3-3: new full-speed USB device number 29 using xhci_hcd [10878.587590] usb 3-3: New USB device found, idVendor=0c76, idProduct=153f, bcdDevice= 1.00 [10878.587597] usb 3-3: New USB device strings: Mfr=0, Product=1, SerialNumber=0 [10878.587599] usb 3-3: Product: USB PnP Audio Device [10878.783592] usb 3-3: Warning! Unlikely big volume range (=496), cval->res is probably wrong. [10878.783597] usb 3-3: [51] FU [Mic Playback Volume] ch = 1, val = 0/7936/16 [10878.809597] usb 3-3: Warning! Unlikely big volume range (=1008), cval->res is probably wrong. [10878.809601] usb 3-3: [49] FU [Speaker Playback Volume] ch = 2, val = -16129/-1/16 [10878.835592] usb 3-3: Warning! Unlikely big volume range (=496), cval->res is probably wrong. [10878.835596] usb 3-3: [50] FU [Mic Capture Volume] ch = 1, val = 0/7936/16 [10878.838754] input: USB PnP Audio Device as /devices/pci:00/:00:01.2/:02:00.0/:03:08.0/:06:00.3/usb3/3-3/3-3:1.3/0003:0C76:153F.001C/input/input46 [10878.895092] hid-generic 0003:0C76:153F.001C: input,hidraw5: USB HID v1.00 Device [USB PnP Audio Device] on usb-:06:00.3-3/input3 [10878.895190] usb 3-4: USB disconnect, device number 28 ``` ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-45.48-generic 5.15.39 Uname: Linux 5.15.0-45-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: vany 12211 F pulseaudio /dev/snd/controlC0: vany 12211 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Aug 8 18:28:32 2022 InstallationDate: Installed on 2020-11-26 (619 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: USB sound card not detected UpgradeStatus: Upgraded to jammy on 2022-05-23 (76 days ago) dmi.bios.date: 04/01/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1407 dmi.board.asset.tag: Default string dmi.board.name: TUF GAMING X570-PLUS (WI-FI) dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1407:bd04/01/2020:br5.14:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS(WI-FI):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- USB sound card not detected https://bugs.launchpad.net/bugs/1983998 You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. -- 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 1983660] Re: Chromium seems to drive all data into swap, until choking
I am pretty much settled with the Audio Downloader Prime. I don't know what it actually does, but within a few minutes it starts showing a sluggish mouse movement and filling swap. Disabling returns the mouse pointer to functional, though swap stays at a high level, though not increasing any further. Thanks a bunch for helping out! Uwe -- 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/1983660 Title: Chromium seems to drive all data into swap, until choking Status in chromium-browser package in Ubuntu: Incomplete Bug description: For the last day(s) my machine runs Chrome very very slow and sluggish until it stops reacting at all. I haven't done any changes except of the daily updates and snap refresh. What I found out, is that the memory space used is almost immediately the swap space. Same after cold boot: it starts pretty usual, but soon almost all memory data seem to be sent into swap space, despite of RAM being available. (See attachment, taken shortly before total non-reaction. CPU isn't very busy, RAM is aplenty.) Swappiness is okay at 60. I very much suspect Chrome, since when using Firefox, with my (in Chrome) usual sites, everything looks fine, it doesn't choke, and the swap space used is almost negligible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1983660/+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 1034999] Re: libreoffice-calc very slow to open/save documents with large cell contents
** Changed in: df-libreoffice Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1034999 Title: libreoffice-calc very slow to open/save documents with large cell contents Status in LibreOffice: Fix Released Status in libreoffice package in Ubuntu: Confirmed Bug description: Libreoffice-calc 3.6 takes a long time (30sec to minutes) to open/save spreadsheets containing cells with a lot of content. This is a regression from libreoffice 3.5 in 12.04 (tested with 1:3.5.4-0ubuntu1) To reproduce: 1) Open the attached spreadsheet, which contains 1 cell with ~4k characters in it Expected results: Spreadsheet opens quickly (<2sec on my 2.4Ghz Core2Duo w/ SSD) Actual results: Libreoffice splash screen shows, libreoffice window is displayed as a gray rectangle with no content, and libreoffice window then becomes unresponsive. CPU usage is at 100% on one core. The system stays in this state for ~30sec. The document eventually opens and libreoffice functions normally. Saving documents with lots of data in a cell takes just as long as opening/reading those documents, with similar symptoms - libreoffice becomes unresponsive, one CPU core is at full utilization, etc. The amount of text in the cell is directly correlated to the length of time required to open/save the doc. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: libreoffice-calc 1:3.6.0~rc4-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-8.8-generic 3.5.0 Uname: Linux 3.5.0-8-generic x86_64 ApportVersion: 2.4-0ubuntu6 Architecture: amd64 Date: Thu Aug 9 13:20:27 2012 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta amd64 (20100901.1) ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: Upgraded to quantal on 2012-08-07 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1034999/+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 1034999]
It's a mystery to me why Assignee wasn't set and bug not marked Fixed when it really looks fixed when tested. I do it now. Thanks Caolan! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1034999 Title: libreoffice-calc very slow to open/save documents with large cell contents Status in LibreOffice: Fix Released Status in libreoffice package in Ubuntu: Confirmed Bug description: Libreoffice-calc 3.6 takes a long time (30sec to minutes) to open/save spreadsheets containing cells with a lot of content. This is a regression from libreoffice 3.5 in 12.04 (tested with 1:3.5.4-0ubuntu1) To reproduce: 1) Open the attached spreadsheet, which contains 1 cell with ~4k characters in it Expected results: Spreadsheet opens quickly (<2sec on my 2.4Ghz Core2Duo w/ SSD) Actual results: Libreoffice splash screen shows, libreoffice window is displayed as a gray rectangle with no content, and libreoffice window then becomes unresponsive. CPU usage is at 100% on one core. The system stays in this state for ~30sec. The document eventually opens and libreoffice functions normally. Saving documents with lots of data in a cell takes just as long as opening/reading those documents, with similar symptoms - libreoffice becomes unresponsive, one CPU core is at full utilization, etc. The amount of text in the cell is directly correlated to the length of time required to open/save the doc. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: libreoffice-calc 1:3.6.0~rc4-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-8.8-generic 3.5.0 Uname: Linux 3.5.0-8-generic x86_64 ApportVersion: 2.4-0ubuntu6 Architecture: amd64 Date: Thu Aug 9 13:20:27 2012 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta amd64 (20100901.1) ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: Upgraded to quantal on 2012-08-07 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1034999/+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 1034999]
Caolán McNamara committed a patch related to this issue. It has been pushed to "libreoffice-7-4-0": https://git.libreoffice.org/core/commit/81b5088a61b4202e8e8ce69c5bca5474482ed98b tdf#108560 horribly slow to paste many lines into editeng with a11y active It will be available in 7.4.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1034999 Title: libreoffice-calc very slow to open/save documents with large cell contents Status in LibreOffice: Fix Released Status in libreoffice package in Ubuntu: Confirmed Bug description: Libreoffice-calc 3.6 takes a long time (30sec to minutes) to open/save spreadsheets containing cells with a lot of content. This is a regression from libreoffice 3.5 in 12.04 (tested with 1:3.5.4-0ubuntu1) To reproduce: 1) Open the attached spreadsheet, which contains 1 cell with ~4k characters in it Expected results: Spreadsheet opens quickly (<2sec on my 2.4Ghz Core2Duo w/ SSD) Actual results: Libreoffice splash screen shows, libreoffice window is displayed as a gray rectangle with no content, and libreoffice window then becomes unresponsive. CPU usage is at 100% on one core. The system stays in this state for ~30sec. The document eventually opens and libreoffice functions normally. Saving documents with lots of data in a cell takes just as long as opening/reading those documents, with similar symptoms - libreoffice becomes unresponsive, one CPU core is at full utilization, etc. The amount of text in the cell is directly correlated to the length of time required to open/save the doc. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: libreoffice-calc 1:3.6.0~rc4-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-8.8-generic 3.5.0 Uname: Linux 3.5.0-8-generic x86_64 ApportVersion: 2.4-0ubuntu6 Architecture: amd64 Date: Thu Aug 9 13:20:27 2012 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta amd64 (20100901.1) ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: Upgraded to quantal on 2012-08-07 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1034999/+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 1970148] Re: Brave & Chrome browsers freezes on download and print to pdf
I can confirm #3 I've had the same behaviour on 2 very different PCs with fresh installs of 22.04 Desktop since May 2022 affecting: Chromium Version 101.0.4951.15 Edge Version 104.0.1293.47 Chrome (installed for testing, same problem) I can confirm #6 Installing xdg-desktop-portal-gnome appears to have resolved the issue on both machines for Chromium and Edge These machines were running Bionic previously and this problem did not exist. -- 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/1970148 Title: Brave & Chrome browsers freezes on download and print to pdf Status in chromium-browser package in Ubuntu: Invalid Bug description: Whenever any file is downloaded, the browser will freeze. Download files, from any page does not work. Same issue with Firefox. Similarly, the browser will freeze when a page is printed to pdf. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1970148/+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 1899156] Re: VPN through Network Manager GUI with Pulse Connect Secure host name problem
Having the same problem since the upgrade from Ubuntu 21.04 to Ubuntu 22.04.1 LTS. SSL vpn does not connect with certificate error (Server certificate verify failed: signer not found) followed by a 404. Tried selecting root intermediate & appliance cert via the vpn config (next to the option 'CA certificate) as well as adding them to the system to no avail. NetworkManager version 1.36.6 & openconnection version v8.20-1. Usig the CLI as a work around also works for me -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1899156 Title: VPN through Network Manager GUI with Pulse Connect Secure host name problem Status in network-manager package in Ubuntu: Confirmed Bug description: Release version: Ubuntu 20.04.1 LTS Version of network-manager-openconnect: 1.2.6-1 Version of openconnect: 8.05-1 VPN connection created through Network Manager GUI with VPN Protocol: Pulse Connect Secure converts gateway host name to IP when making a connection. It results in getting HTTP 404 error in NetworkManager.service logs because of failed SSL certificate validation. Screenshot attached. Gateway in Network Manager GUI is in URL format: https://xxx When using openconnect command: sudo openconnect --protocol=pulse https://xxx all works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1899156/+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 1899156] Re: VPN through Network Manager GUI with Pulse Connect Secure host name problem
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1899156 Title: VPN through Network Manager GUI with Pulse Connect Secure host name problem Status in network-manager package in Ubuntu: Confirmed Bug description: Release version: Ubuntu 20.04.1 LTS Version of network-manager-openconnect: 1.2.6-1 Version of openconnect: 8.05-1 VPN connection created through Network Manager GUI with VPN Protocol: Pulse Connect Secure converts gateway host name to IP when making a connection. It results in getting HTTP 404 error in NetworkManager.service logs because of failed SSL certificate validation. Screenshot attached. Gateway in Network Manager GUI is in URL format: https://xxx When using openconnect command: sudo openconnect --protocol=pulse https://xxx all works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1899156/+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 1981163] Re: In Compose window, if a PDf is joined and clicked to open, Thunderbird launches Firefox instead of Evince
Hi, thanks for the answer. Upstream report done : https://bugzilla.mozilla.org/show_bug.cgi?id=1783679 ** Bug watch added: Mozilla Bugzilla #1783679 https://bugzilla.mozilla.org/show_bug.cgi?id=1783679 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1981163 Title: In Compose window, if a PDf is joined and clicked to open, Thunderbird launches Firefox instead of Evince Status in thunderbird package in Ubuntu: New Bug description: In Thunderbird on Ubuntu Gnome, I set Evince as default program to open pdf files from Thunderbird. In received messages, and those saved on "Sent" folder, it works perfectly. But in the "Compose" window: if I add a pdf file to the message, and double-click on it to open and verify it, Thunderbird always uses Firefox to show it. In case Firefox is not installed (has been removed), I have an error message telling there is not associated application for pdf files and to go to Preferences - where Evince is already and still defined as default. It happens since many months and bug is still present in Thunderbird 102 / Ubuntu 22.10 beta. It's not the same as bug 234349 as here, it's not an URL file but directly a pdf joined in a mail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1981163/+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 1981186] Re: Thunderbird 102 : keeps an empty window even if all calendar alarms closed
Hi, this bug doesn't occur anymore since a few days, it seems that the last updates resolved it… Thanks! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1981186 Title: Thunderbird 102 : keeps an empty window even if all calendar alarms closed Status in thunderbird package in Ubuntu: New Bug description: Since Thunderbird 102 (deb version on Ubuntu 22.10), a new bug appeared on calendar : when a window opens with many alarm reminders, after having reported or closed all of them, it remains an empty window with "0 reminder" title, instead of closing the floating window as before. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1981186/+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 1983788] Re: Update gnome-remote-desktop to 42.4
** Description changed: Impact -- This is a new stable release in the GNOME 42 series - Test Case #1 - - Install all updates. Log out and log back in. - Open the Settings app to the Sharing page. Turn on Sharing and turn on Remote Desktop Sharing. - Turn it off then on because there may be a gnome-control-center bug with initial enabling. + Test Cases + -- + Complete all the test cases from https://wiki.ubuntu.com/DesktopTeam/TestPlans/RemoteDesktop - From a second computer, connect to the first computer using Remmina. - - The Remote Desktop page on the first computer provides the username and - password to use. I wasn't able to get the "Remote Desktop Address" to - work (maybe avahi doesn't work well?) so just use the first computer's - IP address. - - So something like: - RDP jeremy@192.168.1.1 - - Ensure that the connection works. - - Test Case #2 - - Do test case #1 but this time also enable the Legacy VNC option on the Remote Desktop Sharing page. - Connect using VNC instead and ensure that the connection works. + except for the "New Audio Forwarding Feature" test case. What Could Go Wrong --- RDP Sharing is a new feature for Ubuntu 22.04 LTS as part of GNOME 42. (Previously only VNC Sharing was offered.) RDP Sharing can be used for providing remote support so it's important that this feature works well because it may be difficult for the remote admin to fix issues in person. gnome-remote-desktop is part of GNOME Core and falls under the GNOME Stable Release Update microrelease exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME ** Description changed: Impact -- This is a new stable release in the GNOME 42 series Test Cases -- - Complete all the test cases from https://wiki.ubuntu.com/DesktopTeam/TestPlans/RemoteDesktop + Complete all the test cases from + https://wiki.ubuntu.com/DesktopTeam/TestPlans/RemoteDesktop except for the "New Audio Forwarding Feature" test case. What Could Go Wrong --- RDP Sharing is a new feature for Ubuntu 22.04 LTS as part of GNOME 42. (Previously only VNC Sharing was offered.) RDP Sharing can be used for providing remote support so it's important that this feature works well because it may be difficult for the remote admin to fix issues in person. gnome-remote-desktop is part of GNOME Core and falls under the GNOME Stable Release Update microrelease exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1983788 Title: Update gnome-remote-desktop to 42.4 Status in gnome-remote-desktop package in Ubuntu: Fix Released Status in gnome-remote-desktop source package in Jammy: Triaged Bug description: Impact -- This is a new stable release in the GNOME 42 series Test Cases -- Complete all the test cases from https://wiki.ubuntu.com/DesktopTeam/TestPlans/RemoteDesktop except for the "New Audio Forwarding Feature" test case. What Could Go Wrong --- RDP Sharing is a new feature for Ubuntu 22.04 LTS as part of GNOME 42. (Previously only VNC Sharing was offered.) RDP Sharing can be used for providing remote support so it's important that this feature works well because it may be difficult for the remote admin to fix issues in person. gnome-remote-desktop is part of GNOME Core and falls under the GNOME Stable Release Update microrelease exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1983788/+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 1981148] Re: saving dialog focus skips to search bar
I added bug tasks to lubuntu-meta and ubuntu-mate-meta, because it was reported that this is xdg-desktop-portal-gtk misbehaving in these desktop environments, whereas it works fine in GNOME. For Lubuntu, there is a xdg-desktop-portal-lxqt implementation that appears to solve the problem, so it's just a matter of getting it installed on users' machines. I'm not sure what the solution might be for MATE. ** Also affects: lubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-mate-meta (Ubuntu) Importance: Undecided Status: New ** Summary changed: - saving dialog focus skips to search bar + Focusing the filename in GTK's portal file dialog triggers search ** Tags added: snap -- 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/1981148 Title: Focusing the filename in GTK's portal file dialog triggers search Status in firefox package in Ubuntu: Confirmed Status in lubuntu-meta package in Ubuntu: New Status in ubuntu-mate-meta package in Ubuntu: New Bug description: I'm still wondering why my Ubuntu forces the snap version of Firefox onto me, despite apt-pinning, but OK, I guess being frustrated about that would be a lost cause. In any case: The snap version of Firefox that my Ubuntu has decided to install despite my apt-pinning has a bug in the saving dialog. I've recorded a video and left it online, here: https://anonfiles.com/X4ec15w7y3/simplescreenrecorder-2022-07-10_15.57.54_mkv Following protocol: 1) $ lsb_release -rd Description: Ubuntu 22.04 LTS Release: 22.04 2) $ apt-cache policy firefox firefox: Installed: 1:1snap1-0ubuntu2 Candidate: 1:1snap1-0ubuntu2 Version table: *** 1:1snap1-0ubuntu2 500 500 http://de.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status 102.0.1+build1-0ubuntu0.18.04.1 999 500 http://ppa.launchpad.net/ubuntu-mozilla-security/ppa/ubuntu bionic/main amd64 Packages 500 https://ppa.launchpadcontent.net/ubuntu-mozilla-security/ppa/ubuntu bionic/main amd64 Packages (note how Ubuntu doesn't give a damn about the pin priority, but whatever) 3) I'm trying to save a downloaded document. 3.1) Firefox opens the save dialogue. 3.2) I would like to enter a filename into the filename bar 4) following 3.1: 4.2) When I try to change the filename, the focus immediately jumps to the search bar and the dialogue for some reason tries to search for the entered letters on the drive. I can click back to focus on the filename bar, sometimes I can manage to type one or two letters, before the focus jumps, again. This does not happen with the version I installed using apt, but which repeatedly gets removed by the Ubuntu updating process, to install the snap version, which sadly never seems to work without problems. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Sun Jul 10 16:00:53 2022 InstallationDate: Installed on 2022-03-07 (125 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220228) 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/ubuntu/+source/firefox/+bug/1981148/+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 1853638] Re: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data
I am having the same issue. Unfortunately the systems are already in production so testing is a bit limited and the issue was not present at first (not sure why or we didn't notice somehow). I can confirm that I am seeing approx. 8% loss and huge latency > 1s sometimes. Both tested with Ubuntu 18.04 and Ubuntu 20.04 with standard kernel and Libvirt/Openstack VMs. No difference. Bond with LACP, bond first NIC primary and bond second NIC primary makes absolutely no difference. Changed almost all NIC parameters (offloading, ring size, queues) etc., still same result. My last bet was to completely remove the bond and just use the first NIC interface. That worked and now I have stable latency and no loss. Don't know what exactly causes this because we already replaced the NIC with Mellanox and even had the same issue, so I am not sure if this is an issue that happens when the BCM NIC is present but NOT USED somehow (was installed on mainboard). But I can't do further testing now. Removing the bond was my solution as @niveditasinghvi solution did not work for me. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1853638 Title: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: The issue appears to be with the BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Basically, we are dropping data, as you can see from the benchmark tool as follows: tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ ./benchmark_rate --rx_rate 10e6 --tx_rate 10e6 --duration 300 [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_3.14.1.1-0-g98c7c986 [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:00.07] Creating the usrp device with: ... [INFO] [X300] X300 initialization sequence... [INFO] [X300] Maximum frame size: 1472 bytes. [INFO] [X300] Radio 1x clock: 200 MHz [INFO] [GPS] Found an internal GPSDO: LC_XO, Firmware Rev 0.929a [INFO] [0/DmaFIFO_0] Initializing block control (NOC ID: 0xF1F0D000) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1308 MB/s) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1316 MB/s) [INFO] [0/Radio_0] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/Radio_1] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/DDC_0] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DDC_1] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DUC_0] Initializing block control (NOC ID: 0xD0C0) [INFO] [0/DUC_1] Initializing block control (NOC ID: 0xD0C0) Using Device: Single USRP: Device: X-Series Device Mboard 0: X310 RX Channel: 0 RX DSP: 0 RX Dboard: A RX Subdev: SBX-120 RX RX Channel: 1 RX DSP: 0 RX Dboard: B RX Subdev: SBX-120 RX TX Channel: 0 TX DSP: 0 TX Dboard: A TX Subdev: SBX-120 TX TX Channel: 1 TX DSP: 0 TX Dboard: B TX Subdev: SBX-120 TX [00:00:04.305374] Setting device timestamp to 0... [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:04.310990] Testing receive rate 10.00 Msps on 1 channels [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:04.318356] Testing transmit rate 10.00 Msps on 1 channels [00:00:06.693119] Detected Rx sequence error. D[00:00:09.402843] Detected Rx sequence error. DD[00:00:40.927978] Detected Rx sequence error. D[00:01:44.982243] Detected Rx sequence error. D[00:02:11.400692] Detected Rx sequence error. D[00:02:14.805292] Detected Rx sequence error. D[00:02:41.875596] Detected Rx sequence error. D[00:03:06.927743] Detected Rx sequence error. D[00:03:47.967891] Detected Rx sequence error. D[00:03:58.233659] Detected Rx sequence error. D[00:03:58.876588] Detected Rx sequence error. D[00:04:03.139770] Detected Rx sequence error. D[00:04:45.287465] Detected Rx sequence error. D[00:04:56.425845] Detected Rx sequence error. D[00:04:57.929209] Detected Rx sequence error. [00:05:04.529548] Benchmark complete. Benchmark rate summary: Num received samples: 2995435936 Num dropped samples: 4622800 Num overruns detected:0
[Desktop-packages] [Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding
Sorry I did not make clear describe the problem. (I thought the previous
version is working, so the current is a small problem.)
I am using ubuntu-frame to make Wayland test:
https://github.com/MirServer/ubuntu-frame
If the ubnutu-frame is started, the Wayland display is ready. So I just
used native chromium and snap version chromium to confirm the display
result.
--
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/1816497
Title:
[snap] vaapi chromium no video hardware decoding
Status in chromium-browser package in Ubuntu:
In Progress
Bug description:
To test the snap with VA-API changes,
1. Install the Chromium snap,
sudo snap install --channel candidate/hwacc chromium
2. If on Xorg (`echo $WAYLAND_DISPLAY` is empty),
snap run chromium --disable-features=UseChromeOSDirectVideoDecoder
--enable-features=VaapiVideoDecoder
If on Wayland (`echo $WAYLAND_DISPLAY` is not empty),
chromium --enable-features=VaapiVideoDecoder --disable-
features=UseChromeOSDirectVideoDecoder --ozone-platform=wayland
3. Open a video, e.g. one from https://github.com/chthomos/video-
media-samples
4. Enter about:media-internals in the address bar and note what the
page says for kVideoDecoderName.
Please report
- The value for kVideoDecoderName from step 4. Success is typically
{Vaapi,VDA,Mojo}VideoDecoder while failure is {FFMpeg,Vpx}VideoDecoder;
- If failed, the video used for testing, including codec and resolution if
possible;
- Xorg or Wayland (`echo $WAYLAND_DISPLAY`);
- Distro version (`grep VERSION= /etc/os_release`);
- GPU (`lscpu`);
- CPU generation (`lscpu`).
About the last point, it may be that unfortunately only those with
newer generations of Intel CPUs will have luck with this, but it's
still an uncertainty. So reports are highly welcome.
--Original Bug report -
Libva is no longer working for snap installed chromium 72.0.3626.109
(Official Build) snap (64-bit)
I followed this instruction
sudo snap install --channel=candidate/vaapi chromium
My amdgpu can use libva
`vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple: VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main: VAEntrypointVLD
VAProfileVC1Advanced: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileHEVCMain : VAEntrypointVLD
VAProfileHEVCMain10 : VAEntrypointVLD
VAProfileJPEGBaseline : VAEntrypointVLD
VAProfileNone : VAEntrypointVideoProc`
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+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 1816497] Re: [snap] vaapi chromium no video hardware decoding
> I already setup WAYLAND_DISPLAY=wayland-99. I setup a wayland display.
Hmm, I'm not sure if this is clear: The variable WAYLAND_DISPLAY is set
as a consequence of a Wayland session being started. One should not
manually set WAYLAND_DISPLAY; that does not start Wayland.
> The WAYLAND_DISPLAY will displayed chromium browser.
I don't understand what this means.
Also it would be nice if you could address the points in #164, as your
situation is still unclear to me.
--
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/1816497
Title:
[snap] vaapi chromium no video hardware decoding
Status in chromium-browser package in Ubuntu:
In Progress
Bug description:
To test the snap with VA-API changes,
1. Install the Chromium snap,
sudo snap install --channel candidate/hwacc chromium
2. If on Xorg (`echo $WAYLAND_DISPLAY` is empty),
snap run chromium --disable-features=UseChromeOSDirectVideoDecoder
--enable-features=VaapiVideoDecoder
If on Wayland (`echo $WAYLAND_DISPLAY` is not empty),
chromium --enable-features=VaapiVideoDecoder --disable-
features=UseChromeOSDirectVideoDecoder --ozone-platform=wayland
3. Open a video, e.g. one from https://github.com/chthomos/video-
media-samples
4. Enter about:media-internals in the address bar and note what the
page says for kVideoDecoderName.
Please report
- The value for kVideoDecoderName from step 4. Success is typically
{Vaapi,VDA,Mojo}VideoDecoder while failure is {FFMpeg,Vpx}VideoDecoder;
- If failed, the video used for testing, including codec and resolution if
possible;
- Xorg or Wayland (`echo $WAYLAND_DISPLAY`);
- Distro version (`grep VERSION= /etc/os_release`);
- GPU (`lscpu`);
- CPU generation (`lscpu`).
About the last point, it may be that unfortunately only those with
newer generations of Intel CPUs will have luck with this, but it's
still an uncertainty. So reports are highly welcome.
--Original Bug report -
Libva is no longer working for snap installed chromium 72.0.3626.109
(Official Build) snap (64-bit)
I followed this instruction
sudo snap install --channel=candidate/vaapi chromium
My amdgpu can use libva
`vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple: VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main: VAEntrypointVLD
VAProfileVC1Advanced: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileHEVCMain : VAEntrypointVLD
VAProfileHEVCMain10 : VAEntrypointVLD
VAProfileJPEGBaseline : VAEntrypointVLD
VAProfileNone : VAEntrypointVideoProc`
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+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 1983859] [NEW] tracker-extract crashes with SIGSYS when upgrading from 20.04 to 22.04
Public bug reported: When upgrading Ubuntu Desktop from 20.04 to 22.04, there's often (pretty much always) a crash from tracker-extract, as described in the following error report: https://errors.ubuntu.com/oops/d7866d85-14cc-11ed-a52b-fa163e55efd0 The crash occurs during the upgrade, which means it's fairly hard to investigate exactly what's going on as apport fails to extract a stack trace, the binaries being overwritten during the upgrade. However, the crash occurs because of a unhandled SIGSYS, meaning a seccomp filter issue. I've tried backporting this patch fixing a similar issue: https://gitlab.gnome.org/GNOME/tracker- miners/-/commit/4cda983b02e49f6bd28b94a6b96c9fe7026887ef but it doesn't apply, likely due to the code having diverged too much since. My proposal is thus to disable tracker-extract during upgrade, including in all user sessions. I'm assuming that the new version will be enabled automatically as its unit file changed name anyway. ** Affects: tracker (Ubuntu) Importance: High Status: Confirmed ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: High Status: Confirmed ** Tags: fr-2595 ** Also affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: New => Confirmed ** Changed in: ubuntu-release-upgrader (Ubuntu) Importance: Undecided => High ** Tags added: fr-2595 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1983859 Title: tracker-extract crashes with SIGSYS when upgrading from 20.04 to 22.04 Status in tracker package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Bug description: When upgrading Ubuntu Desktop from 20.04 to 22.04, there's often (pretty much always) a crash from tracker-extract, as described in the following error report: https://errors.ubuntu.com/oops/d7866d85-14cc-11ed-a52b-fa163e55efd0 The crash occurs during the upgrade, which means it's fairly hard to investigate exactly what's going on as apport fails to extract a stack trace, the binaries being overwritten during the upgrade. However, the crash occurs because of a unhandled SIGSYS, meaning a seccomp filter issue. I've tried backporting this patch fixing a similar issue: https://gitlab.gnome.org/GNOME/tracker- miners/-/commit/4cda983b02e49f6bd28b94a6b96c9fe7026887ef but it doesn't apply, likely due to the code having diverged too much since. My proposal is thus to disable tracker-extract during upgrade, including in all user sessions. I'm assuming that the new version will be enabled automatically as its unit file changed name anyway. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1983859/+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 1816497] Re: [snap] vaapi chromium no video hardware decoding
I already setup WAYLAND_DISPLAY=wayland-99. I setup a wayland display.
I confirmed the native chromium-browser did work with --enable-
features=VaapiVideoDecoder --disable-
features=UseChromeOSDirectVideoDecoder --ozone-platform=wayland. The
WAYLAND_DISPLAY will displayed chromium browser.
The only problem is using snap chromium. So I made a report this time.
--
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/1816497
Title:
[snap] vaapi chromium no video hardware decoding
Status in chromium-browser package in Ubuntu:
In Progress
Bug description:
To test the snap with VA-API changes,
1. Install the Chromium snap,
sudo snap install --channel candidate/hwacc chromium
2. If on Xorg (`echo $WAYLAND_DISPLAY` is empty),
snap run chromium --disable-features=UseChromeOSDirectVideoDecoder
--enable-features=VaapiVideoDecoder
If on Wayland (`echo $WAYLAND_DISPLAY` is not empty),
chromium --enable-features=VaapiVideoDecoder --disable-
features=UseChromeOSDirectVideoDecoder --ozone-platform=wayland
3. Open a video, e.g. one from https://github.com/chthomos/video-
media-samples
4. Enter about:media-internals in the address bar and note what the
page says for kVideoDecoderName.
Please report
- The value for kVideoDecoderName from step 4. Success is typically
{Vaapi,VDA,Mojo}VideoDecoder while failure is {FFMpeg,Vpx}VideoDecoder;
- If failed, the video used for testing, including codec and resolution if
possible;
- Xorg or Wayland (`echo $WAYLAND_DISPLAY`);
- Distro version (`grep VERSION= /etc/os_release`);
- GPU (`lscpu`);
- CPU generation (`lscpu`).
About the last point, it may be that unfortunately only those with
newer generations of Intel CPUs will have luck with this, but it's
still an uncertainty. So reports are highly welcome.
--Original Bug report -
Libva is no longer working for snap installed chromium 72.0.3626.109
(Official Build) snap (64-bit)
I followed this instruction
sudo snap install --channel=candidate/vaapi chromium
My amdgpu can use libva
`vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple: VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main: VAEntrypointVLD
VAProfileVC1Advanced: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileHEVCMain : VAEntrypointVLD
VAProfileHEVCMain10 : VAEntrypointVLD
VAProfileJPEGBaseline : VAEntrypointVLD
VAProfileNone : VAEntrypointVideoProc`
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+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 1983502] Re: [snap] seccomp denials for syscall=314 on amd64
Awesome, thank you Olivier! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1983502 Title: [snap] seccomp denials for syscall=314 on amd64 Status in thunderbird package in Ubuntu: In Progress Bug description: $ snap list thunderbird Name VersionRev Tracking Publisher Notes thunderbird 102.1.0-2 237 latest/stable canonical✓ - During normal operation, the following is logged: Aug 03 12:07:58 foo kernel: audit: type=1326 audit(1659542878.718:511): auid=1000 uid=1000 gid=1000 ses=9 subj=? pid=154377 comm="thunderbird-bin" exe="/snap/thunderbird/237/thunderbird-bin" sig=0 arch=c03e syscall=314 compat=0 ip=0x7e4137c4473d code=0x5 And something similar when the crash reporter executes: Aug 03 12:02:04 foo kernel: audit: type=1326 audit(1659542524.642:510): auid=1000 uid=1000 gid=1000 ses=9 subj=? pid=150188 comm="crashreporter" exe="/snap/thunderbird/237/crashreporter" sig=0 arch=c03e syscall=314 compat=0 ip=0x7e5f095e773d code=0x5 # Additional information: $ lsb_release -rd Description: Ubuntu 20.04.4 LTS Release: 20.04 $ uname -a Linux foo 5.15.0-43-generic #46~20.04.1-Ubuntu SMP Thu Jul 14 15:20:17 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1983502/+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 1816497] Re: [snap] vaapi chromium no video hardware decoding
I get the exact error you report on #161 if I try the Wayland command
(chromium --enable-features=VaapiVideoDecoder --disable-
features=UseChromeOSDirectVideoDecoder --ozone-platform=wayland) under
Xorg. Please double check you are not under Xorg when trying the Wayland
command.
--
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/1816497
Title:
[snap] vaapi chromium no video hardware decoding
Status in chromium-browser package in Ubuntu:
In Progress
Bug description:
To test the snap with VA-API changes,
1. Install the Chromium snap,
sudo snap install --channel candidate/hwacc chromium
2. If on Xorg (`echo $WAYLAND_DISPLAY` is empty),
snap run chromium --disable-features=UseChromeOSDirectVideoDecoder
--enable-features=VaapiVideoDecoder
If on Wayland (`echo $WAYLAND_DISPLAY` is not empty),
chromium --enable-features=VaapiVideoDecoder --disable-
features=UseChromeOSDirectVideoDecoder --ozone-platform=wayland
3. Open a video, e.g. one from https://github.com/chthomos/video-
media-samples
4. Enter about:media-internals in the address bar and note what the
page says for kVideoDecoderName.
Please report
- The value for kVideoDecoderName from step 4. Success is typically
{Vaapi,VDA,Mojo}VideoDecoder while failure is {FFMpeg,Vpx}VideoDecoder;
- If failed, the video used for testing, including codec and resolution if
possible;
- Xorg or Wayland (`echo $WAYLAND_DISPLAY`);
- Distro version (`grep VERSION= /etc/os_release`);
- GPU (`lscpu`);
- CPU generation (`lscpu`).
About the last point, it may be that unfortunately only those with
newer generations of Intel CPUs will have luck with this, but it's
still an uncertainty. So reports are highly welcome.
--Original Bug report -
Libva is no longer working for snap installed chromium 72.0.3626.109
(Official Build) snap (64-bit)
I followed this instruction
sudo snap install --channel=candidate/vaapi chromium
My amdgpu can use libva
`vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple: VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main: VAEntrypointVLD
VAProfileVC1Advanced: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileHEVCMain : VAEntrypointVLD
VAProfileHEVCMain10 : VAEntrypointVLD
VAProfileJPEGBaseline : VAEntrypointVLD
VAProfileNone : VAEntrypointVideoProc`
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+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 1816497] Re: [snap] vaapi chromium no video hardware decoding
Wait,
> chrome://flags/#ozone-platform-hint , not work.
1. What does "not work" mean here? Does Chromium not even launch, or
does it start but not hardware accelerated? If the former, does dropping
the flags (--enable-features=VaapiVideoDecoder etc.) makes it launch?
> I remember in previouse snap it is working, but withtout
vaapivideodecoder working. It is another problem, ...
2. So, in previous versions of the snap, Chromium would launch, but
without hardware acceleration, correct me if I understand wrong.
> ... but the wayland is sure working.
3. You mean that snap is supposed to work under Wayland, not that
Wayland itself works, right?
4. I'm also interested in your `snap run --shell chromium`, `vainfo`
output under Wayland.
> does wayland mode conflict with vaapivdideodecoder feature ?
I, for one, could get hardware acceleration in Chromium under Wayland
working with `chromium --enable-features=VaapiVideoDecoder --disable-
features=UseChromeOSDirectVideoDecoder --ozone-platform=wayland`.
** Description changed:
To test the snap with VA-API changes,
1. Install the Chromium snap,
sudo snap install --channel candidate/hwacc chromium
- 2. snap run chromium --disable-features=UseChromeOSDirectVideoDecoder
+ 2. If on Xorg (`echo $WAYLAND_DISPLAY` is empty),
+
+snap run chromium --disable-features=UseChromeOSDirectVideoDecoder
--enable-features=VaapiVideoDecoder
+
+If on Wayland (`echo $WAYLAND_DISPLAY` is not empty),
+
+ chromium --enable-features=VaapiVideoDecoder --disable-
+ features=UseChromeOSDirectVideoDecoder --ozone-platform=wayland
3. Open a video, e.g. one from https://github.com/chthomos/video-media-
samples
4. Enter about:media-internals in the address bar and note what the page
says for kVideoDecoderName.
Please report
- The value for kVideoDecoderName from step 4. Success is typically
{Vaapi,VDA,Mojo}VideoDecoder while failure is {FFMpeg,Vpx}VideoDecoder;
- If failed, the video used for testing, including codec and resolution if
possible;
- Xorg or Wayland (`echo $WAYLAND_DISPLAY`);
- Distro version (`grep VERSION= /etc/os_release`);
- GPU (`lscpu`);
- CPU generation (`lscpu`).
About the last point, it may be that unfortunately only those with newer
generations of Intel CPUs will have luck with this, but it's still an
uncertainty. So reports are highly welcome.
--Original Bug report -
Libva is no longer working for snap installed chromium 72.0.3626.109
(Official Build) snap (64-bit)
I followed this instruction
sudo snap install --channel=candidate/vaapi chromium
My amdgpu can use libva
`vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple: VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main: VAEntrypointVLD
VAProfileVC1Advanced: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileHEVCMain : VAEntrypointVLD
VAProfileHEVCMain10 : VAEntrypointVLD
VAProfileJPEGBaseline : VAEntrypointVLD
VAProfileNone : VAEntrypointVideoProc`
--
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/1816497
Title:
[snap] vaapi chromium no video hardware decoding
Status in chromium-browser package in Ubuntu:
In Progress
Bug description:
To test the snap with VA-API changes,
1. Install the Chromium snap,
sudo snap install --channel candidate/hwacc chromium
2. If on Xorg (`echo $WAYLAND_DISPLAY` is empty),
snap run chromium --disable-features=UseChromeOSDirectVideoDecoder
--enable-features=VaapiVideoDecoder
If on Wayland (`echo $WAYLAND_DISPLAY` is not empty),
chromium --enable-features=VaapiVideoDecoder --disable-
features=UseChromeOSDirectVideoDecoder --ozone-platform=wayland
3. Open a video, e.g. one from https://github.com/chthomos/video-
media-samples
4. Enter about:media-internals in the address bar and note what the
page says for kVideoDecoderName.
Please report
- The value for kVideoDecoderName from step 4. Success is typically
{Vaapi,VDA,Mojo}VideoDecoder while failure is {FFMpeg,Vpx}VideoDecoder;
- If failed,
[Desktop-packages] [Bug 1979412] Re: [snap] Chromium crashes when downloading
The chromium snap is now at version 104.0.5112.79. Torsten, are you still observing these crashes with the latest update? Do you have extensions activated? If so, can you try disabling them all and running chromium for a while, downloading files as you normally do, and let us know whether the crashes are still happening? ** 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/1979412 Title: [snap] Chromium crashes when downloading Status in chromium-browser package in Ubuntu: Incomplete Bug description: For a couple of weeks, I observe random crashes of Chromium when you click on a link that starts a non-HTML download (e.g. PDF or an MS Excel file). After restarting Chromium and restoring the tabs, a second click on the link starts the download without problems, probably because this issue is not 100% reproducible in the first place. Observed with Chromium 102.0.5005.115 (officiel build) snap (64-Bit) on Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1979412/+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 1982898] Re: CVE-2021-46829: Buffer overwrite in io-gif-animation.c composite_frame() in gdk-pixbuf
This bug was fixed in the package gdk-pixbuf - 2.40.0+dfsg-3ubuntu0.3 --- gdk-pixbuf (2.40.0+dfsg-3ubuntu0.3) focal-security; urgency=medium * SECURITY UPDATE: Buffer overwrite in io-gif-animation.c composite_frame() (LP: #1982898) - debian/patches/CVE-2021-46829.patch: gif: Check for overflow when compositing or clearing frames. - CVE-2021-46829 -- Joshua Peisach Tue, 26 Jul 2022 20:42:00 -0400 ** Changed in: gdk-pixbuf (Ubuntu Focal) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1982898 Title: CVE-2021-46829: Buffer overwrite in io-gif-animation.c composite_frame() in gdk-pixbuf Status in gdk-pixbuf package in Ubuntu: In Progress Status in gdk-pixbuf source package in Focal: Fix Released Bug description: [Impact] * A buffer overwrite exists in gdk-pixbuf's thumbnailer. * The GIF loader runs out of memory with specifically crafted files with bad frame data (and images with its sizes) over the integer limit. * After gdk-pixbuf-thum runs out of memory, other apps can and on low RAM systems like my old iMac, the system can completely run out of memory. * Or, in other ways, bad gif files in other applications can open the door for exploits. * Any app using gdk-pixbuf is affected, mainly file managers and image viewers. [Test Plan] * Take the POC's - they can be found in the issue in the GNOME repo * Open them in an application that uses gdk-pixbuf. I have managed to produce reactions with: - Nautilus, GNOME's file manager - Nemo, Cinnamon's file manager - Thunar, XFCE's file manager, which has its own thumbnailere (tumbler) that also inevitably fails and crashes - PCManFM, LXDE's file manager which straight up crashes - Caja, MATE's file manager causes libpixbufloader-gif to segfault (app still usable, no memory issues) - Eye of GNOME (eog) triggers the segfault in syslog - Eye of MATE (eom) segfaults * If you or the system couldn't tell something is wrong, cat /var/log/syslog and enjoy the segfaults or out of memory warnings or even kernel spam. [Where problems could occur] * The patch itself is simple, but since gdk-pixbuf is often used with GTK apps a mistake here could be problematic. * It is possible, and has happened in the past (which has been patched) that other bad GIFs can cause other crashes. * That patch is essentially overflow checks - changes with GLib (GNOME's, not to be confused with glibc) and the functions used in not only the patch but all of gdk-pixbuf can cause problems * Other failures to properly handle GIFs and broken or intentionally tampered GIFs can continue and always will open the door for security holes for other bugs * Again, overall a simple patch but as long as the GIFs remain handled properly, and no changes to the GLib functions are made and to other apps that use gdk-pixbuf (and assuming are not affected by the change and still work), the patch does not have much regression potential. [Other Info] * Besides Buffer overwrite/overflow issues, as aforementioned out of memory errors can happen. * Files attached are examples or crashes * Again, all apps using gdk-pixbuf are affected * https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/merge_requests/121/ * https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/190 * https://github.com/pedrib/PoC/blob/master/fuzzing/CVE-2021-46829/CVE-2021-46829.md ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgdk-pixbuf2.0-0 2.40.0+dfsg-3ubuntu0.2 ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Tue Jul 26 19:33:41 2022 InstallationDate: Installed on 2021-11-24 (244 days ago) InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210826) SourcePackage: gdk-pixbuf UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1982898/+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 1983660] Re: Chromium seems to drive all data into swap, until choking
Any of these extensions could be the culprit really, so you'll have to re-enable them one by one until you manage to identify the faulty one. Then I would suggest filing an issue against the extension itself (and keeping us posted here). -- 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/1983660 Title: Chromium seems to drive all data into swap, until choking Status in chromium-browser package in Ubuntu: Incomplete Bug description: For the last day(s) my machine runs Chrome very very slow and sluggish until it stops reacting at all. I haven't done any changes except of the daily updates and snap refresh. What I found out, is that the memory space used is almost immediately the swap space. Same after cold boot: it starts pretty usual, but soon almost all memory data seem to be sent into swap space, despite of RAM being available. (See attachment, taken shortly before total non-reaction. CPU isn't very busy, RAM is aplenty.) Swappiness is okay at 60. I very much suspect Chrome, since when using Firefox, with my (in Chrome) usual sites, everything looks fine, it doesn't choke, and the swap space used is almost negligible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1983660/+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 1983660] Re: Chromium seems to drive all data into swap, until choking
I think I can give a first 'all clear', and taking a deep breath on your side. Chrome itself looks fine. I made a mistake: I have some 8 extensions installed, of which around 5 were enabled, and I forgot to note which. Silly me. At least, disabling all has seen my Chrome working properly for the last hour, with a steady 9 MB of swap. Maybe it helps to give the list of installed, currently disabled, extensions? Adblock Plus EditThisCookke Simple Autoscroll Audio Downloader Prime Reload All Tabs Stream Recorder - download HLS ... Dynu Dynamic DNS client RSS Subscription Extension, Reader Any suggestion with which to start the re-enabling? -- 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/1983660 Title: Chromium seems to drive all data into swap, until choking Status in chromium-browser package in Ubuntu: Incomplete Bug description: For the last day(s) my machine runs Chrome very very slow and sluggish until it stops reacting at all. I haven't done any changes except of the daily updates and snap refresh. What I found out, is that the memory space used is almost immediately the swap space. Same after cold boot: it starts pretty usual, but soon almost all memory data seem to be sent into swap space, despite of RAM being available. (See attachment, taken shortly before total non-reaction. CPU isn't very busy, RAM is aplenty.) Swappiness is okay at 60. I very much suspect Chrome, since when using Firefox, with my (in Chrome) usual sites, everything looks fine, it doesn't choke, and the swap space used is almost negligible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1983660/+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 1983502] Re: [snap] seccomp denials for syscall=314 on amd64
The crash reporter is fixed with https://github.com/ubuntu/thunderbird/pull/2. ** Changed in: thunderbird (Ubuntu) Status: New => In Progress ** Changed in: thunderbird (Ubuntu) Assignee: (unassigned) => Olivier Tilloy (osomon) ** Changed in: thunderbird (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1983502 Title: [snap] seccomp denials for syscall=314 on amd64 Status in thunderbird package in Ubuntu: In Progress Bug description: $ snap list thunderbird Name VersionRev Tracking Publisher Notes thunderbird 102.1.0-2 237 latest/stable canonical✓ - During normal operation, the following is logged: Aug 03 12:07:58 foo kernel: audit: type=1326 audit(1659542878.718:511): auid=1000 uid=1000 gid=1000 ses=9 subj=? pid=154377 comm="thunderbird-bin" exe="/snap/thunderbird/237/thunderbird-bin" sig=0 arch=c03e syscall=314 compat=0 ip=0x7e4137c4473d code=0x5 And something similar when the crash reporter executes: Aug 03 12:02:04 foo kernel: audit: type=1326 audit(1659542524.642:510): auid=1000 uid=1000 gid=1000 ses=9 subj=? pid=150188 comm="crashreporter" exe="/snap/thunderbird/237/crashreporter" sig=0 arch=c03e syscall=314 compat=0 ip=0x7e5f095e773d code=0x5 # Additional information: $ lsb_release -rd Description: Ubuntu 20.04.4 LTS Release: 20.04 $ uname -a Linux foo 5.15.0-43-generic #46~20.04.1-Ubuntu SMP Thu Jul 14 15:20:17 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1983502/+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 1983502] Re: [snap] seccomp denials for syscall=314 on amd64
I can confirm that the crash reporter dialog doesn't submit crashes, and
that the same fix that was used in firefox (stage libcurl) makes it
work.
FTR, I used this trick to test-crash thunderbird:
https://superuser.com/a/678426
i.e. input the following in the devtools console:
Cu.import("resource://gre/modules/ctypes.jsm");
let zero = new ctypes.intptr_t(8);
let badptr = ctypes.cast(zero, ctypes.PointerType(ctypes.int32_t));
badptr.contents;
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1983502
Title:
[snap] seccomp denials for syscall=314 on amd64
Status in thunderbird package in Ubuntu:
New
Bug description:
$ snap list thunderbird
Name VersionRev Tracking Publisher Notes
thunderbird 102.1.0-2 237 latest/stable canonical✓ -
During normal operation, the following is logged:
Aug 03 12:07:58 foo kernel: audit: type=1326
audit(1659542878.718:511): auid=1000 uid=1000 gid=1000 ses=9 subj=?
pid=154377 comm="thunderbird-bin"
exe="/snap/thunderbird/237/thunderbird-bin" sig=0 arch=c03e
syscall=314 compat=0 ip=0x7e4137c4473d code=0x5
And something similar when the crash reporter executes:
Aug 03 12:02:04 foo kernel: audit: type=1326
audit(1659542524.642:510): auid=1000 uid=1000 gid=1000 ses=9 subj=?
pid=150188 comm="crashreporter"
exe="/snap/thunderbird/237/crashreporter" sig=0 arch=c03e
syscall=314 compat=0 ip=0x7e5f095e773d code=0x5
# Additional information:
$ lsb_release -rd
Description: Ubuntu 20.04.4 LTS
Release: 20.04
$ uname -a
Linux foo 5.15.0-43-generic #46~20.04.1-Ubuntu SMP Thu Jul 14 15:20:17 UTC
2022 x86_64 x86_64 x86_64 GNU/Linux
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1983502/+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 1977679] Re: Firefox opens KML file in neverending loop if associated with "System Handler"
Sorry for the lack of feedback, this is clearly a valid issue that should be looked into. Would you mind filing an upstream bug report at https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox and sharing the link to it here? ** Changed in: firefox (Ubuntu) Status: Expired => 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/1977679 Title: Firefox opens KML file in neverending loop if associated with "System Handler" Status in firefox package in Ubuntu: New Bug description: Found when trying open a KML export file from Google Timeline. It can be reproduced even with an empty KML file. Steps: * Create an empty file "test.kml" (run "$ touch test.kml") * Open the application "Files" * Right click on the test.kml and open it with Firefox * Open with "System Handler" and check the option "Do this automatically for files like this from now on" (see "Screenshot from 2022-06-05 11-13-23.png") Expected result: * No infinite opening Actual result: * Firefox starts opening the file again and again (see "Screenshot from 2022-06-05 11-04-35.png") Used SW: * Ubuntu 22.04 LTS * Firefox 101.0 * Files 42.1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1977679/+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 1981148] Re: saving dialog focus skips to search bar
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: firefox (Ubuntu) Status: New => Confirmed -- 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/1981148 Title: saving dialog focus skips to search bar Status in firefox package in Ubuntu: Confirmed Bug description: I'm still wondering why my Ubuntu forces the snap version of Firefox onto me, despite apt-pinning, but OK, I guess being frustrated about that would be a lost cause. In any case: The snap version of Firefox that my Ubuntu has decided to install despite my apt-pinning has a bug in the saving dialog. I've recorded a video and left it online, here: https://anonfiles.com/X4ec15w7y3/simplescreenrecorder-2022-07-10_15.57.54_mkv Following protocol: 1) $ lsb_release -rd Description: Ubuntu 22.04 LTS Release: 22.04 2) $ apt-cache policy firefox firefox: Installed: 1:1snap1-0ubuntu2 Candidate: 1:1snap1-0ubuntu2 Version table: *** 1:1snap1-0ubuntu2 500 500 http://de.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status 102.0.1+build1-0ubuntu0.18.04.1 999 500 http://ppa.launchpad.net/ubuntu-mozilla-security/ppa/ubuntu bionic/main amd64 Packages 500 https://ppa.launchpadcontent.net/ubuntu-mozilla-security/ppa/ubuntu bionic/main amd64 Packages (note how Ubuntu doesn't give a damn about the pin priority, but whatever) 3) I'm trying to save a downloaded document. 3.1) Firefox opens the save dialogue. 3.2) I would like to enter a filename into the filename bar 4) following 3.1: 4.2) When I try to change the filename, the focus immediately jumps to the search bar and the dialogue for some reason tries to search for the entered letters on the drive. I can click back to focus on the filename bar, sometimes I can manage to type one or two letters, before the focus jumps, again. This does not happen with the version I installed using apt, but which repeatedly gets removed by the Ubuntu updating process, to install the snap version, which sadly never seems to work without problems. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Sun Jul 10 16:00:53 2022 InstallationDate: Installed on 2022-03-07 (125 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220228) 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/ubuntu/+source/firefox/+bug/1981148/+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 1983781] Re: Firefox file picker changes focus incorrectly when typing
*** This bug is a duplicate of bug 1981148 *** https://bugs.launchpad.net/bugs/1981148 ** This bug has been marked a duplicate of bug 1981148 saving dialog focus skips to search bar -- 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/1983781 Title: Firefox file picker changes focus incorrectly when typing Status in Ubuntu MATE: Incomplete Status in firefox package in Ubuntu: New Status in marco package in Ubuntu: New Bug description: 1. Start Firefox 2. Try to download something. (I usually right-click an image, and then use "save image as". But any download operation that starts the file picker will do.) 3. Highlight the name of the file to be saved. 4. Start typing over the file name 5. The focus will change to the "search" box on the file picker, and all additional keystrokes will go there. The only way to change the file name is to a. type one character in the file name box b. mouse-click in the file name box c. type the next character in the file name box (repeat until file name is complete or your have gone insane :) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2018-08-04 (1464 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) NonfreeKernelModules: nvidia_modeset nvidia Package: marco ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Snap: firefox 103.0.1-1 (latest/stable) Snap.Changes: no changes found Tags: jammy Uname: Linux 5.15.0-43-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-05-21 (77 days ago) UserGroups: adm bumblebee cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1983781/+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 1983660] Re: Chromium seems to drive all data into swap, until choking
Could it be that an extension is misbehaving? Can you try disabling them all in chrome://extensions, then restart and use chromium for a while, to see if that makes a difference? While using chromium, you can also inspect the CPU and memory used by each individual tab by invoking the chromium task manager with the Shift+ESC keyboard shortcut. -- 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/1983660 Title: Chromium seems to drive all data into swap, until choking Status in chromium-browser package in Ubuntu: Incomplete Bug description: For the last day(s) my machine runs Chrome very very slow and sluggish until it stops reacting at all. I haven't done any changes except of the daily updates and snap refresh. What I found out, is that the memory space used is almost immediately the swap space. Same after cold boot: it starts pretty usual, but soon almost all memory data seem to be sent into swap space, despite of RAM being available. (See attachment, taken shortly before total non-reaction. CPU isn't very busy, RAM is aplenty.) Swappiness is okay at 60. I very much suspect Chrome, since when using Firefox, with my (in Chrome) usual sites, everything looks fine, it doesn't choke, and the swap space used is almost negligible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1983660/+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 1983788] Re: Update gnome-remote-desktop to 42.4
This bug was fixed in the package gnome-remote-desktop - 42.4-1 --- gnome-remote-desktop (42.4-1) unstable; urgency=medium * New upstream release (LP: #1983788) -- Jeremy Bicha Sun, 07 Aug 2022 16:46:54 -0400 ** Changed in: gnome-remote-desktop (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1983788 Title: Update gnome-remote-desktop to 42.4 Status in gnome-remote-desktop package in Ubuntu: Fix Released Status in gnome-remote-desktop source package in Jammy: Triaged Bug description: Impact -- This is a new stable release in the GNOME 42 series Test Case #1 Install all updates. Log out and log back in. Open the Settings app to the Sharing page. Turn on Sharing and turn on Remote Desktop Sharing. Turn it off then on because there may be a gnome-control-center bug with initial enabling. From a second computer, connect to the first computer using Remmina. The Remote Desktop page on the first computer provides the username and password to use. I wasn't able to get the "Remote Desktop Address" to work (maybe avahi doesn't work well?) so just use the first computer's IP address. So something like: RDP jeremy@192.168.1.1 Ensure that the connection works. Test Case #2 Do test case #1 but this time also enable the Legacy VNC option on the Remote Desktop Sharing page. Connect using VNC instead and ensure that the connection works. What Could Go Wrong --- RDP Sharing is a new feature for Ubuntu 22.04 LTS as part of GNOME 42. (Previously only VNC Sharing was offered.) RDP Sharing can be used for providing remote support so it's important that this feature works well because it may be difficult for the remote admin to fix issues in person. gnome-remote-desktop is part of GNOME Core and falls under the GNOME Stable Release Update microrelease exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1983788/+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 1983815] Re: no detection of the hdmi display moinitor
Thanks for the bug report. This may be caused by: * The Intel kernel graphics crash mentioned in CurrentDmesg.txt * An Nvidia driver problem (if the HDMI port is wired to the Nvidia GPU) * Something else Firstly, to see if we can stop the Intel graphics crash from happening please try adding this to /etc/environment: MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 and then reboot. ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Also affects: nvidia-graphics-drivers-515 (Ubuntu) Importance: Undecided Status: New ** Tags added: hyb i915 nvidia rid ** Tags removed: hyb rid ** Tags added: hybrid ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: nvidia-graphics-drivers-515 (Ubuntu) Status: New => Incomplete ** Tags added: multimonitor -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1983815 Title: no detection of the hdmi display moinitor Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-515 package in Ubuntu: Incomplete Bug description: In the windows, hdmi display monitor work. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..03.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 515.65.01 Wed Jul 20 14:00:58 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Aug 8 16:27:14 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:22e9] Subsystem: Lenovo Device [17aa:22e9] InstallationDate: Installed on 2022-08-07 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 21BVCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-43-generic root=UUID=240545ce-be3b-4291-87da-1fe7a719dca4 ro text SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/07/2022 dmi.bios.release: 1.24 dmi.bios.vendor: LENOVO dmi.bios.version: N3BET46W (1.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 21BVCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0T76530 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.12 dmi.modalias: dmi:bvnLENOVO:bvrN3BET46W(1.24):bd06/07/2022:br1.24:efr1.12:svnLENOVO:pn21BVCTO1WW:pvrThinkPadT16Gen1:rvnLENOVO:rn21BVCTO1WW:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21BV_BU_Think_FM_ThinkPadT16Gen1: dmi.product.family: ThinkPad T16 Gen 1 dmi.product.name: 21BVCTO1WW dmi.product.sku: LENOVO_MT_21BV_BU_Think_FM_ThinkPad T16 Gen 1 dmi.product.version: ThinkPad T16 Gen 1 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983815/+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 1983112] Re: Appstream does not install config file
** Attachment added: "scenario_2_appstream.txt" https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+attachment/5607337/+files/scenario_2_appstream.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1983112 Title: Appstream does not install config file Status in appstream package in Ubuntu: New Bug description: After performing an Ubuntu automated server install, and installing the ubuntu-desktop-minimal package (which includes appstream as a dependency) then the snap-store, the snap-store will fail to display search results for .deb packages in the Ubuntu apt repositories. This is due to a missing config file (/etc/apt/apt.conf.d/50appstream) which is supposed to be installed as part of the appstream package. The issue can be fixed by re-installing appstream with the following command-line: apt-get -y install --reinstall -o Dpkg::Options::="--force-confmiss" appstream ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: appstream 0.15.2-2 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Fri Jul 29 15:25:44 2022 InstallationDate: Installed on 2022-07-27 (1 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: appstream UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+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 1983112] Re: Appstream does not install config file
** Attachment added: "scenario_3_installer.zip" https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+attachment/5607336/+files/scenario_3_installer.zip -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1983112 Title: Appstream does not install config file Status in appstream package in Ubuntu: New Bug description: After performing an Ubuntu automated server install, and installing the ubuntu-desktop-minimal package (which includes appstream as a dependency) then the snap-store, the snap-store will fail to display search results for .deb packages in the Ubuntu apt repositories. This is due to a missing config file (/etc/apt/apt.conf.d/50appstream) which is supposed to be installed as part of the appstream package. The issue can be fixed by re-installing appstream with the following command-line: apt-get -y install --reinstall -o Dpkg::Options::="--force-confmiss" appstream ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: appstream 0.15.2-2 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Fri Jul 29 15:25:44 2022 InstallationDate: Installed on 2022-07-27 (1 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: appstream UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+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 1983112] Re: Appstream does not install config file
** Attachment added: "scenario_2_installer.zip" https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+attachment/5607335/+files/scenario_2_installer.zip -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1983112 Title: Appstream does not install config file Status in appstream package in Ubuntu: New Bug description: After performing an Ubuntu automated server install, and installing the ubuntu-desktop-minimal package (which includes appstream as a dependency) then the snap-store, the snap-store will fail to display search results for .deb packages in the Ubuntu apt repositories. This is due to a missing config file (/etc/apt/apt.conf.d/50appstream) which is supposed to be installed as part of the appstream package. The issue can be fixed by re-installing appstream with the following command-line: apt-get -y install --reinstall -o Dpkg::Options::="--force-confmiss" appstream ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: appstream 0.15.2-2 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Fri Jul 29 15:25:44 2022 InstallationDate: Installed on 2022-07-27 (1 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: appstream UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+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 1983112] Re: Appstream does not install config file
** Attachment added: "scenario_1_installer.zip" https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+attachment/5607334/+files/scenario_1_installer.zip -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1983112 Title: Appstream does not install config file Status in appstream package in Ubuntu: New Bug description: After performing an Ubuntu automated server install, and installing the ubuntu-desktop-minimal package (which includes appstream as a dependency) then the snap-store, the snap-store will fail to display search results for .deb packages in the Ubuntu apt repositories. This is due to a missing config file (/etc/apt/apt.conf.d/50appstream) which is supposed to be installed as part of the appstream package. The issue can be fixed by re-installing appstream with the following command-line: apt-get -y install --reinstall -o Dpkg::Options::="--force-confmiss" appstream ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: appstream 0.15.2-2 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Fri Jul 29 15:25:44 2022 InstallationDate: Installed on 2022-07-27 (1 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: appstream UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+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 1983112] Re: Appstream does not install config file
Reuploading previous attachments after redacting sensitive information. Original comment copied below: Okay, I've gone down the rabbit hole with this one. It's possible this is 2 separate issues. I tested 3 scenarios: Scenario 1 - Performed a clean Ubuntu Server install (interactive), and installed ubuntu-desktop-minimal post-deployment. After rebooting, the 50appstream config is present, and I installed snap-store and gnome-software. Neither snap-store nor gnome-software showed any .deb packages. Only snaps. I tried re-installing appstream and forcing a refresh of the cache, but still no .deb packages shown. Nothing I have tried in this install has been able to fix the issue. Scenario 2 - I performed a clean install using our automated install image (/var/log/installer contents attached) WITHOUT our appstream config reinstall script that I shared previously. After deployment, ubuntu-desktop-minimal is already installed, and 50appstream config is MISSING (see attachment). Both snap-store and gnome-software only show snaps. No .deb packages. Next, I ran the appstream re-install script I shared previously and rebooted the machine. After the reboot, gnome-software correctly shows .deb packages. However, snap-store is still only showing snaps!!! Scenario 3 - I performed a clean install using our automated install image (/var/log/installer contents attached), this time including our appstream config reinstall script. After the deployment, 50appstream config is PRESENT. Both snap-store and gnome-software work correctly and show both snaps and .deb packages. The varying behaviour between all 3 has completely blown my mind. I really don't know what is the cause of the issue, and potentially this is even 2 separate issues, since in Scenario 1, neither snap-store nor gnome-software work correctly. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1983112 Title: Appstream does not install config file Status in appstream package in Ubuntu: New Bug description: After performing an Ubuntu automated server install, and installing the ubuntu-desktop-minimal package (which includes appstream as a dependency) then the snap-store, the snap-store will fail to display search results for .deb packages in the Ubuntu apt repositories. This is due to a missing config file (/etc/apt/apt.conf.d/50appstream) which is supposed to be installed as part of the appstream package. The issue can be fixed by re-installing appstream with the following command-line: apt-get -y install --reinstall -o Dpkg::Options::="--force-confmiss" appstream ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: appstream 0.15.2-2 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Fri Jul 29 15:25:44 2022 InstallationDate: Installed on 2022-07-27 (1 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: appstream UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+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 1983112] Re: Appstream does not install config file
** Attachment removed: "installer logs for Scenario 1" https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+attachment/5607134/+files/scenario_1_installer.zip ** Attachment removed: "scenario_2_installer.zip" https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+attachment/5607135/+files/scenario_2_installer.zip ** Attachment removed: "scenario_2_appstream.txt" https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+attachment/5607136/+files/scenario_2_appstream.txt ** Attachment removed: "scenario_3_installer.zip" https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+attachment/5607137/+files/scenario_3_installer.zip -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1983112 Title: Appstream does not install config file Status in appstream package in Ubuntu: New Bug description: After performing an Ubuntu automated server install, and installing the ubuntu-desktop-minimal package (which includes appstream as a dependency) then the snap-store, the snap-store will fail to display search results for .deb packages in the Ubuntu apt repositories. This is due to a missing config file (/etc/apt/apt.conf.d/50appstream) which is supposed to be installed as part of the appstream package. The issue can be fixed by re-installing appstream with the following command-line: apt-get -y install --reinstall -o Dpkg::Options::="--force-confmiss" appstream ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: appstream 0.15.2-2 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Fri Jul 29 15:25:44 2022 InstallationDate: Installed on 2022-07-27 (1 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: appstream UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+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 1983815] [NEW] no detection of the hdmi display moinitor
Public bug reported: In the windows, hdmi display monitor work. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..03.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 515.65.01 Wed Jul 20 14:00:58 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Aug 8 16:27:14 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:22e9] Subsystem: Lenovo Device [17aa:22e9] InstallationDate: Installed on 2022-08-07 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 21BVCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-43-generic root=UUID=240545ce-be3b-4291-87da-1fe7a719dca4 ro text SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/07/2022 dmi.bios.release: 1.24 dmi.bios.vendor: LENOVO dmi.bios.version: N3BET46W (1.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 21BVCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0T76530 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.12 dmi.modalias: dmi:bvnLENOVO:bvrN3BET46W(1.24):bd06/07/2022:br1.24:efr1.12:svnLENOVO:pn21BVCTO1WW:pvrThinkPadT16Gen1:rvnLENOVO:rn21BVCTO1WW:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21BV_BU_Think_FM_ThinkPadT16Gen1: dmi.product.family: ThinkPad T16 Gen 1 dmi.product.name: 21BVCTO1WW dmi.product.sku: LENOVO_MT_21BV_BU_Think_FM_ThinkPad T16 Gen 1 dmi.product.version: ThinkPad T16 Gen 1 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1983815 Title: no detection of the hdmi display moinitor Status in xorg package in Ubuntu: New Bug description: In the windows, hdmi display monitor work. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..03.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 515.65.01 Wed Jul 20 14:00:58 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Aug 8 16:27:14 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device
[Desktop-packages] [Bug 1983810] Re: Updated to Ubuntu 22.10 and Pipewire detects no audio device
** Package changed: ubuntu => pipewire (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pipewire in Ubuntu. https://bugs.launchpad.net/bugs/1983810 Title: Updated to Ubuntu 22.10 and Pipewire detects no audio device Status in pipewire package in Ubuntu: New Bug description: I just updated to Ubuntu 22.10 a few days ago, apparently, it comes automatically with Pipewire as the audio server. But it detects no audio device on my laptop (neither input nor output). My laptop is "Dell Latitude 3520", and I have "Ubuntu Kinetic Kudu (development branch) 64-bit" on Wayland (and GNOME 42.3 if it is useful information as well) When I run "apt list | grep pipewire" I see this output: ``` WARNING: apt does not have a stable CLI interface. Use with caution in scripts. gstreamer1.0-pipewire/kinetic,now 0.3.56-1 amd64 [installed,automatic] gstreamer1.0-pipewire/kinetic 0.3.56-1 i386 libpipewire-0.3-0/kinetic,now 0.3.56-1 amd64 [installed,automatic] libpipewire-0.3-0/kinetic 0.3.56-1 i386 libpipewire-0.3-common/kinetic,kinetic,now 0.3.56-1 all [installed,automatic] libpipewire-0.3-dev/kinetic 0.3.56-1 amd64 libpipewire-0.3-dev/kinetic 0.3.56-1 i386 libpipewire-0.3-modules/kinetic,now 0.3.56-1 amd64 [installed,automatic] libpipewire-0.3-modules/kinetic 0.3.56-1 i386 pipewire-alsa/kinetic 0.3.56-1 amd64 pipewire-alsa/kinetic 0.3.56-1 i386 pipewire-audio-client-libraries/kinetic,kinetic 0.3.56-1 all pipewire-bin/kinetic,now 0.3.56-1 amd64 [installed,automatic] pipewire-bin/kinetic 0.3.56-1 i386 pipewire-doc/kinetic,kinetic 0.3.56-1 all pipewire-jack/kinetic 0.3.56-1 amd64 pipewire-jack/kinetic 0.3.56-1 i386 pipewire-media-session/kinetic,now 0.4.1-3ubuntu1 amd64 [installed,automatic] pipewire-pulse/kinetic,now 0.3.56-1 amd64 [installed,automatic] pipewire-pulse/kinetic 0.3.56-1 i386 pipewire-tests/kinetic 0.3.56-1 amd64 pipewire-tests/kinetic 0.3.56-1 i386 pipewire-v4l2/kinetic 0.3.56-1 amd64 pipewire-v4l2/kinetic 0.3.56-1 i386 pipewire/kinetic,now 0.3.56-1 amd64 [installed,automatic] pipewire/kinetic 0.3.56-1 i386 vlc-plugin-pipewire/kinetic 3-2 amd64 ``` This is the output of lsb_release -rd: ``` Description: Ubuntu Kinetic Kudu (development branch) Release: 22.10 ``` I saw similar bug reports and discussions on the internet, with some workarounds and ways to try to see if they fix this, but I decided to report it just to mention automatic upgrade to 22.10 breaks audio devices by default in some cases. If I did something and fixed it, I will write here. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: pipewire 0.3.56-1 ProcVersionSignature: Ubuntu 5.14.0-1033.36-oem 5.14.21 Uname: Linux 5.14.0-1033-oem x86_64 ApportVersion: 2.22.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Aug 8 10:43:02 2022 InstallationDate: Installed on 2022-03-02 (158 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: pipewire UpgradeStatus: Upgraded to kinetic on 2022-08-03 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1983810/+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 1983810] [NEW] Updated to Ubuntu 22.10 and Pipewire detects no audio device
You have been subscribed to a public bug: I just updated to Ubuntu 22.10 a few days ago, apparently, it comes automatically with Pipewire as the audio server. But it detects no audio device on my laptop (neither input nor output). My laptop is "Dell Latitude 3520", and I have "Ubuntu Kinetic Kudu (development branch) 64-bit" on Wayland (and GNOME 42.3 if it is useful information as well) When I run "apt list | grep pipewire" I see this output: ``` WARNING: apt does not have a stable CLI interface. Use with caution in scripts. gstreamer1.0-pipewire/kinetic,now 0.3.56-1 amd64 [installed,automatic] gstreamer1.0-pipewire/kinetic 0.3.56-1 i386 libpipewire-0.3-0/kinetic,now 0.3.56-1 amd64 [installed,automatic] libpipewire-0.3-0/kinetic 0.3.56-1 i386 libpipewire-0.3-common/kinetic,kinetic,now 0.3.56-1 all [installed,automatic] libpipewire-0.3-dev/kinetic 0.3.56-1 amd64 libpipewire-0.3-dev/kinetic 0.3.56-1 i386 libpipewire-0.3-modules/kinetic,now 0.3.56-1 amd64 [installed,automatic] libpipewire-0.3-modules/kinetic 0.3.56-1 i386 pipewire-alsa/kinetic 0.3.56-1 amd64 pipewire-alsa/kinetic 0.3.56-1 i386 pipewire-audio-client-libraries/kinetic,kinetic 0.3.56-1 all pipewire-bin/kinetic,now 0.3.56-1 amd64 [installed,automatic] pipewire-bin/kinetic 0.3.56-1 i386 pipewire-doc/kinetic,kinetic 0.3.56-1 all pipewire-jack/kinetic 0.3.56-1 amd64 pipewire-jack/kinetic 0.3.56-1 i386 pipewire-media-session/kinetic,now 0.4.1-3ubuntu1 amd64 [installed,automatic] pipewire-pulse/kinetic,now 0.3.56-1 amd64 [installed,automatic] pipewire-pulse/kinetic 0.3.56-1 i386 pipewire-tests/kinetic 0.3.56-1 amd64 pipewire-tests/kinetic 0.3.56-1 i386 pipewire-v4l2/kinetic 0.3.56-1 amd64 pipewire-v4l2/kinetic 0.3.56-1 i386 pipewire/kinetic,now 0.3.56-1 amd64 [installed,automatic] pipewire/kinetic 0.3.56-1 i386 vlc-plugin-pipewire/kinetic 3-2 amd64 ``` This is the output of lsb_release -rd: ``` Description:Ubuntu Kinetic Kudu (development branch) Release:22.10 ``` I saw similar bug reports and discussions on the internet, with some workarounds and ways to try to see if they fix this, but I decided to report it just to mention automatic upgrade to 22.10 breaks audio devices by default in some cases. If I did something and fixed it, I will write here. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: pipewire 0.3.56-1 ProcVersionSignature: Ubuntu 5.14.0-1033.36-oem 5.14.21 Uname: Linux 5.14.0-1033-oem x86_64 ApportVersion: 2.22.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Aug 8 10:43:02 2022 InstallationDate: Installed on 2022-03-02 (158 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: pipewire UpgradeStatus: Upgraded to kinetic on 2022-08-03 (4 days ago) ** Affects: pipewire (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic third-party-packages wayland-session -- Updated to Ubuntu 22.10 and Pipewire detects no audio device https://bugs.launchpad.net/bugs/1983810 You received this bug notification because you are a member of Desktop Packages, which is subscribed to pipewire in Ubuntu. -- 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
