[Desktop-packages] [Bug 310270] Re: Dell XPS M1330 volume keys as pressed two times
** Changed in: kdemultimedia Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/310270 Title: Dell XPS M1330 volume keys as pressed two times Status in KDE Multimedia: Invalid Status in xserver-xorg-input-evdev package in Ubuntu: Incomplete Bug description: All my volume multimedia keys (vol-up, vol-down, mute) works bad on my Dell XPS M1330 on Kubuntu with Kde4.2 beta. Every keys works as if it was pressed twice, so i raise up my volume by two levels, and when I mute the volume, it mutes and than unmutes. Sorry for my english. If you need more information, ask me. Everything was working good on Gnome. To manage notifications about this bug go to: https://bugs.launchpad.net/kdemultimedia/+bug/310270/+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 310270]
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/310270 Title: Dell XPS M1330 volume keys as pressed two times Status in KDE Multimedia: Invalid Status in xserver-xorg-input-evdev package in Ubuntu: Incomplete Bug description: All my volume multimedia keys (vol-up, vol-down, mute) works bad on my Dell XPS M1330 on Kubuntu with Kde4.2 beta. Every keys works as if it was pressed twice, so i raise up my volume by two levels, and when I mute the volume, it mutes and than unmutes. Sorry for my english. If you need more information, ask me. Everything was working good on Gnome. To manage notifications about this bug go to: https://bugs.launchpad.net/kdemultimedia/+bug/310270/+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 1989590] Re: Can't click on dock items if status drop-down is shown
** Changed in: gnome-shell Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1989590 Title: Can't click on dock items if status drop-down is shown Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Triaged Bug description: Steps: 1. open any of the system status drop-downs 2. click on any app icon in the Ubuntu Dock Expected: 1. the system status drop-down goes away Current: 1. nothing happens ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43~beta-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 14 16:49:59 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-08-31 (13 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220829) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/zsh RelatedPackageVersions: mutter-common 43~beta-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1989590/+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 258705]
Dear Christopher M. Penalver, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- 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/258705 Title: [Upstream] Calc XY (scatter) chart Sort by x values has wrong x,y in tooltip Status in LibreOffice: Confirmed Status in OpenOffice: Confirmed Status in libreoffice package in Ubuntu: Confirmed Status in openoffice.org package in Ubuntu: Won't Fix Bug description: Binary package hint: openoffice.org 1) LibreOffice: lsb_release -rd Description: Ubuntu 11.04 Release: 11.04 OpenOffice: lsb_release -rd Description: Ubuntu 8.04.1 Release: 8.04 2) LibreOffice: apt-cache policy libreoffice-calc libreoffice-calc: Installed: 1:3.3.2-1ubuntu5 Candidate: 1:3.3.2-1ubuntu5 Version table: *** 1:3.3.2-1ubuntu5 0 500 http://us.archive.ubuntu.com/ubuntu/ natty-updates/main i386 Packages 500 http://us.archive.ubuntu.com/ubuntu/ natty-proposed/main i386 Packages 100 /var/lib/dpkg/status 1:3.3.2-1ubuntu4 0 500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages OpenOffice: apt-cache policy openoffice.org-calc openoffice.org-calc: Installed: 1:2.4.1-1ubuntu2 Candidate: 1:2.4.1-1ubuntu2 Version table: *** 1:2.4.1-1ubuntu2 0 500 http://us.archive.ubuntu.com hardy-updates/main Packages 100 /var/lib/dpkg/status 1:2.4.0-3ubuntu6 0 500 http://us.archive.ubuntu.com hardy/main Packages 3) What is expected to happen in Calc via the Terminal: cd ~/Desktop && wget https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/258705/+attachment/403067/+files/xyscatterbug.ods && localc -nologo xyscatterbug.ods double click the XY (Scatter), sorted by X values chart and hover the mouse icon over a data point, the pop up notes the correct X,Y value. 4) What happens instead is it does not. The pop-up is using the data values top to bottom, to display the data point values from left to right. ProblemType: Bug Architecture: amd64 Date: Sat Aug 16 22:36:17 2008 DistroRelease: Ubuntu 8.04 Package: openoffice.org-core 1:2.4.1-1ubuntu2 PackageArchitecture: amd64 ProcEnviron: PATH=/usr/lib/openoffice/program:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: openoffice.org Uname: Linux 2.6.24-19-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/258705/+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 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog
This bug is mighty annoying. E.g. you can't simply type to get out of the save dialog, if you wrongly typed . You first need to mouse the pointer to the text field. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal-gtk in Ubuntu. https://bugs.launchpad.net/bugs/1949340 Title: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog Status in Mozilla Firefox: New Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in gtk4 package in Ubuntu: Confirmed Status in xdg-desktop-portal-gnome package in Ubuntu: Confirmed Status in xdg-desktop-portal-gtk package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Open Chromium (release does not matter, here deb-packaged version from 18.04 LTS is used) 2a. Navigate to some page, press + 2b. Navigate to some page, with "Ask where to save each file before downloading" enabled try to download some file Actual result: * file chooser dialog is unfocused, user should select the window by mouse and then hit for specified location Expected result: * file chooser dialog is focused, user can simply hit to save in previously selected location. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1949340/+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 1922559] Re: osk: umlauts do not work in password prompts
** Tags added: jammy kinetic
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1922559
Title:
osk: umlauts do not work in password prompts
Status in GNOME Shell:
New
Status in gnome-shell package in Ubuntu:
Won't Fix
Bug description:
When I try to input a german umlaut like "ü" in a gnome-shell password
prompt using the onscreen keyboard, nothing appears in the input
field. In regular applications like gedit umlauts work however, so it
seems to be specific to password prompts.
Couldn't find anything interesting the the journalctl log, only
messages related to gnome-shell at the time of trying to input the
umlaut are:
Apr 05 14:41:24 pc gnome-shell[2094]: Couldn't find child [0x55cb1c6ece70
Gjs_ui_windowPreview_WindowPreview:last-child ("Loading…")] in window slots
Apr 05 14:41:25 pc gnome-shell[2094]: Couldn't find child [0x55cb1c6ece70
Gjs_ui_windowPreview_WindowPreview:first-child ("Home")] in window slots
Apr 05 14:41:25 pc gnome-shell[2094]: Couldn't find child [0x55cb1c6ece70
Gjs_ui_windowPreview_WindowPreview:last-child ("Home")] in window slots
Apr 05 14:41:25 pc gnome-shell[2094]: Couldn't find child [0x55cb1c6ece70
Gjs_ui_windowPreview_WindowPreview:last-child ("Home")] in window slots
Apr 05 14:41:25 pc gnome-shell[2094]: Couldn't find child [0x55cb1c6ece70
Gjs_ui_windowPreview_WindowPreview:last-child ("Home")] in window slots
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: gnome-shell 3.38.4-1ubuntu1
Uname: Linux 5.11.11+ x86_64
ApportVersion: 2.20.11-0ubuntu61
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Mon Apr 5 14:24:19 2021
DisplayManager: gdm3
RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1922559/+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 1980271] Re: Snap doesn't refresh automatically immediately after snap is quit when update is pending
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/1980271 Title: Snap doesn't refresh automatically immediately after snap is quit when update is pending Status in snapd: In Progress Status in firefox package in Ubuntu: Confirmed Bug description: Impact / What Currently Happens -- Many people open their chosen web browser (Firefox or Chromium) immediately after logging in and keep the app running continuously. Eventually, there will be a snap update available. The system notifies that there is a pending update and to "Close the app to avoid notifications." Most people will eventually close the app, but the pending update is not applied until the next snap refresh is attempted which could be hours away. This is a frustrating experience because it feels like the notification is not helpful. I think many users would prefer the snap to just update silently in the background with little or no notification. Test Case - From Ubuntu 22.04 LTS with the Firefox snap installed by default Keep Firefox running Wait for a new Firefox release (happens at least monthly) Receive a notification about a pending update for Firefox Close Firefox Wait a few minutes Open Firefox Workaround -- Close the app that needs to be updated Open a terminal and run this command: snap refresh Other Info -- This issue was mentioned in the original post and in the first comment at https://forum.snapcraft.io/t/refresh-app-awareness-call-for-testing/29123 Suggested Mitigation Would it help to run a `snap refresh` immediately after Ubuntu is booted? To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1980271/+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 1985066] Re: cannot refresh snap "firefox": snap "firefox" has running apps (firefox)
*** This bug is a duplicate of bug 1980271 *** https://bugs.launchpad.net/bugs/1980271 ** This bug has been marked a duplicate of bug 1980271 Snap doesn't refresh automatically immediately after snap is quit when update is pending -- 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/1985066 Title: cannot refresh snap "firefox": snap "firefox" has running apps (firefox) Status in firefox package in Ubuntu: Confirmed Bug description: Firefox installed via 22.04 snap does not seem to update properly. There is a log line (or error printout on manual execution), but it does not really point me to the actual bug. I already know firefox is running for some other user - that machine is never up and not running firefox - but I do not see how that matters. # snap list firefox Name VersionRev Tracking Publisher Notes firefox 103.0.1-1 1635 latest/stable mozilla✓ - # snap info firefox | grep latest/stable tracking: latest/stable latest/stable:103.0.2-12022-08-09 (1670) 171MB - # sudo snap refresh firefox error: cannot refresh "firefox": snap "firefox" has running apps (firefox), pids: 19113,19246,19268,19361,19524,19529,19588,19874,20047,20075,20105,20127 # firefox --version Mozilla Firefox 103.0.1 (expected: 103.0.2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1985066/+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 1980271] Re: Snap doesn't refresh automatically immediately after snap is quit when update is pending
** Also affects: firefox (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1980271 Title: Snap doesn't refresh automatically immediately after snap is quit when update is pending Status in snapd: In Progress Status in firefox package in Ubuntu: Confirmed Bug description: Impact / What Currently Happens -- Many people open their chosen web browser (Firefox or Chromium) immediately after logging in and keep the app running continuously. Eventually, there will be a snap update available. The system notifies that there is a pending update and to "Close the app to avoid notifications." Most people will eventually close the app, but the pending update is not applied until the next snap refresh is attempted which could be hours away. This is a frustrating experience because it feels like the notification is not helpful. I think many users would prefer the snap to just update silently in the background with little or no notification. Test Case - From Ubuntu 22.04 LTS with the Firefox snap installed by default Keep Firefox running Wait for a new Firefox release (happens at least monthly) Receive a notification about a pending update for Firefox Close Firefox Wait a few minutes Open Firefox Workaround -- Close the app that needs to be updated Open a terminal and run this command: snap refresh Other Info -- This issue was mentioned in the original post and in the first comment at https://forum.snapcraft.io/t/refresh-app-awareness-call-for-testing/29123 Suggested Mitigation Would it help to run a `snap refresh` immediately after Ubuntu is booted? To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1980271/+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 1996813] Re: Firefox Snap update message but no update available
*** This bug is a duplicate of bug 1980271 *** https://bugs.launchpad.net/bugs/1980271 If I remember correctly I had a error message a few days ago when I tried "# snap refresh firefox" while Firefox was running but this error message is now gone. Could successfully "# snap refresh firefox" after "# killall firefox". ** This bug has been marked a duplicate of bug 1980271 Snap doesn't refresh automatically immediately after snap is quit when update is pending -- 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/1996813 Title: Firefox Snap update message but no update available Status in firefox package in Ubuntu: New Status in snapd package in Ubuntu: New Bug description: >Pending update for "firefox" snap > >Close the app to avoid disruptions (13 days left) Showed up today and is pestering me since I switched to Ubuntu LTS 22.04! Discovery shows no update. # snap info firefox name: firefox summary: Mozilla Firefox web browser publisher: Mozilla✓ store-url: https://snapcraft.io/firefox contact: https://support.mozilla.org/kb/file-bug-report-or-feature-request-mozilla license: unset description: | Firefox is a powerful, extensible web browser with support for modern web application technologies. commands: - firefox - firefox.geckodriver snap-id: 3wdHCAVyZEmYsCMFDE9qt92UV8rC8Wdk tracking: latest/stable/ubuntu-22.04 refresh-date: 5 days ago, at 23:18 CET channels: latest/stable:107.0-2 2022-11-15 (2088) 249MB - latest/candidate: 107.0-2 2022-11-11 (2088) 249MB - latest/beta: 107.0b9-12022-11-04 (2062) 187MB - latest/edge: 109.0a1 2022-11-16 (2106) 193MB - esr/stable: 102.5.0esr-1 2022-11-15 (2077) 183MB - esr/candidate:102.5.0esr-1 2022-11-08 (2077) 183MB - esr/beta: ↑ esr/edge: 102.2.0esr-2 2022-09-02 (1793) 182MB - installed: 106.0.5-1 (2067) 213MB - # snap refresh firefox snap "firefox" has no updates available Ubuntu 22.04.1 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1996813/+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 1988631] Re: Firefox snap update doesn't work and popup is very annoying
*** This bug is a duplicate of bug 1980271 *** https://bugs.launchpad.net/bugs/1980271 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/1988631 Title: Firefox snap update doesn't work and popup is very annoying Status in firefox package in Ubuntu: Confirmed Bug description: Each time snap thinks that firefox should be updated (-> so this happens quite often) a popup message appears and stays above all other windows all the time to remind me to close firefox. It also gives me a couple of days that are granted to me to do that. I can close this popup - but after a shot time it comes up again. This popup is very annoying and distracts me from the work that I'm just doing. Every day in the evening I shut down my computer completely, so firefox is also closed. In the morning I start it up and firefox gets automatically started again (as intended by me). But it seems that snap is not capable to handle a shutdown and restart to do its work. It just prefers to annoy me in multiple ways instead: it takes away my authority over my system and my decision when I'm prepared to do an update or not. It doesn't give me a choice to skip a specific version when I don't want to use it. It tries to put me under pressure to do the update like a bad sales agent (only ... days left). All of this was perfectly solved when firefox was a normal APT package. The system I'm running is Kubuntu, based on Ubuntu 22.04.1 LTS Firefox is 104.0.1 - but it happend already with older versions of it as well To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1988631/+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 1985066] Re: cannot refresh snap "firefox": snap "firefox" has running apps (firefox)
Sorry, can still confirm seeing this happening independently of https://bugs.launchpad.net/snapd/+bug/1980271 with user switching. "snap refesh firefox" complains if firefox isn't closed by the user and worse, how can a regular user handle this if an other user has firefox running as well? If I understand correctly the solution could be the same (https://github.com/snapcore/snapd/pull/12231) but I don't think this is invalidating this bug but will allow potentially that both will be closed by the same fix. -- 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/1985066 Title: cannot refresh snap "firefox": snap "firefox" has running apps (firefox) Status in firefox package in Ubuntu: Confirmed Bug description: Firefox installed via 22.04 snap does not seem to update properly. There is a log line (or error printout on manual execution), but it does not really point me to the actual bug. I already know firefox is running for some other user - that machine is never up and not running firefox - but I do not see how that matters. # snap list firefox Name VersionRev Tracking Publisher Notes firefox 103.0.1-1 1635 latest/stable mozilla✓ - # snap info firefox | grep latest/stable tracking: latest/stable latest/stable:103.0.2-12022-08-09 (1670) 171MB - # sudo snap refresh firefox error: cannot refresh "firefox": snap "firefox" has running apps (firefox), pids: 19113,19246,19268,19361,19524,19529,19588,19874,20047,20075,20105,20127 # firefox --version Mozilla Firefox 103.0.1 (expected: 103.0.2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1985066/+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 1996813] Re: Firefox Snap update message but no update available
** Package changed: snap (Ubuntu) => snapd (Ubuntu) ** Tags added: jammy -- 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/1996813 Title: Firefox Snap update message but no update available Status in firefox package in Ubuntu: New Status in snapd package in Ubuntu: New Bug description: >Pending update for "firefox" snap > >Close the app to avoid disruptions (13 days left) Showed up today and is pestering me since I switched to Ubuntu LTS 22.04! Discovery shows no update. # snap info firefox name: firefox summary: Mozilla Firefox web browser publisher: Mozilla✓ store-url: https://snapcraft.io/firefox contact: https://support.mozilla.org/kb/file-bug-report-or-feature-request-mozilla license: unset description: | Firefox is a powerful, extensible web browser with support for modern web application technologies. commands: - firefox - firefox.geckodriver snap-id: 3wdHCAVyZEmYsCMFDE9qt92UV8rC8Wdk tracking: latest/stable/ubuntu-22.04 refresh-date: 5 days ago, at 23:18 CET channels: latest/stable:107.0-2 2022-11-15 (2088) 249MB - latest/candidate: 107.0-2 2022-11-11 (2088) 249MB - latest/beta: 107.0b9-12022-11-04 (2062) 187MB - latest/edge: 109.0a1 2022-11-16 (2106) 193MB - esr/stable: 102.5.0esr-1 2022-11-15 (2077) 183MB - esr/candidate:102.5.0esr-1 2022-11-08 (2077) 183MB - esr/beta: ↑ esr/edge: 102.2.0esr-2 2022-09-02 (1793) 182MB - installed: 106.0.5-1 (2067) 213MB - # snap refresh firefox snap "firefox" has no updates available Ubuntu 22.04.1 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1996813/+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 1985066] Re: cannot refresh snap "firefox": snap "firefox" has running apps (firefox)
** Changed in: firefox (Ubuntu) Status: Invalid => 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/1985066 Title: cannot refresh snap "firefox": snap "firefox" has running apps (firefox) Status in firefox package in Ubuntu: Confirmed Bug description: Firefox installed via 22.04 snap does not seem to update properly. There is a log line (or error printout on manual execution), but it does not really point me to the actual bug. I already know firefox is running for some other user - that machine is never up and not running firefox - but I do not see how that matters. # snap list firefox Name VersionRev Tracking Publisher Notes firefox 103.0.1-1 1635 latest/stable mozilla✓ - # snap info firefox | grep latest/stable tracking: latest/stable latest/stable:103.0.2-12022-08-09 (1670) 171MB - # sudo snap refresh firefox error: cannot refresh "firefox": snap "firefox" has running apps (firefox), pids: 19113,19246,19268,19361,19524,19529,19588,19874,20047,20075,20105,20127 # firefox --version Mozilla Firefox 103.0.1 (expected: 103.0.2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1985066/+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 1996813] [NEW] Firefox Snap update message but no update available
Public bug reported: >Pending update for "firefox" snap > >Close the app to avoid disruptions (13 days left) Showed up today and is pestering me since I switched to Ubuntu LTS 22.04! Discovery shows no update. # snap info firefox name: firefox summary: Mozilla Firefox web browser publisher: Mozilla✓ store-url: https://snapcraft.io/firefox contact: https://support.mozilla.org/kb/file-bug-report-or-feature-request-mozilla license: unset description: | Firefox is a powerful, extensible web browser with support for modern web application technologies. commands: - firefox - firefox.geckodriver snap-id: 3wdHCAVyZEmYsCMFDE9qt92UV8rC8Wdk tracking: latest/stable/ubuntu-22.04 refresh-date: 5 days ago, at 23:18 CET channels: latest/stable:107.0-2 2022-11-15 (2088) 249MB - latest/candidate: 107.0-2 2022-11-11 (2088) 249MB - latest/beta: 107.0b9-12022-11-04 (2062) 187MB - latest/edge: 109.0a1 2022-11-16 (2106) 193MB - esr/stable: 102.5.0esr-1 2022-11-15 (2077) 183MB - esr/candidate:102.5.0esr-1 2022-11-08 (2077) 183MB - esr/beta: ↑ esr/edge: 102.2.0esr-2 2022-09-02 (1793) 182MB - installed: 106.0.5-1 (2067) 213MB - # snap refresh firefox snap "firefox" has no updates available Ubuntu 22.04.1 LTS ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Affects: snap (Ubuntu) Importance: Undecided Status: New ** Also affects: snap (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1996813 Title: Firefox Snap update message but no update available Status in firefox package in Ubuntu: New Status in snap package in Ubuntu: New Bug description: >Pending update for "firefox" snap > >Close the app to avoid disruptions (13 days left) Showed up today and is pestering me since I switched to Ubuntu LTS 22.04! Discovery shows no update. # snap info firefox name: firefox summary: Mozilla Firefox web browser publisher: Mozilla✓ store-url: https://snapcraft.io/firefox contact: https://support.mozilla.org/kb/file-bug-report-or-feature-request-mozilla license: unset description: | Firefox is a powerful, extensible web browser with support for modern web application technologies. commands: - firefox - firefox.geckodriver snap-id: 3wdHCAVyZEmYsCMFDE9qt92UV8rC8Wdk tracking: latest/stable/ubuntu-22.04 refresh-date: 5 days ago, at 23:18 CET channels: latest/stable:107.0-2 2022-11-15 (2088) 249MB - latest/candidate: 107.0-2 2022-11-11 (2088) 249MB - latest/beta: 107.0b9-12022-11-04 (2062) 187MB - latest/edge: 109.0a1 2022-11-16 (2106) 193MB - esr/stable: 102.5.0esr-1 2022-11-15 (2077) 183MB - esr/candidate:102.5.0esr-1 2022-11-08 (2077) 183MB - esr/beta: ↑ esr/edge: 102.2.0esr-2 2022-09-02 (1793) 182MB - installed: 106.0.5-1 (2067) 213MB - # snap refresh firefox snap "firefox" has no updates available Ubuntu 22.04.1 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1996813/+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 1993019] Re: UnboundLocalError: local variable 'version' referenced before assignment
I have also encountered this issue
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1993019
Title:
UnboundLocalError: local variable 'version' referenced before
assignment
Status in ubuntu-drivers-common package in Ubuntu:
Confirmed
Bug description:
Hello, we received a drive-by complaint about the ubuntu-drivers
autoinstall tool:
< Fhazal> hye i have problem with ubuntu 22.04 nvidia auto install command
< Fhazal> this error appear when i try to auto install recommended driver
< Fhazal> https://pastebin.com/ydZVFT24
The contents of the pastebin:
Traceback (most recent call last):
File "/usr/bin/ubuntu-drivers", line 513, in
greet()
File "/usr/lib/python3/dist-packages/click/core.py", line 1128, in __call__
return self.main(*args, **kwargs)
File "/usr/lib/python3/dist-packages/click/core.py", line 1053, in main
rv = self.invoke(ctx)
File "/usr/lib/python3/dist-packages/click/core.py", line 1659, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File "/usr/lib/python3/dist-packages/click/core.py", line 1395, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "/usr/lib/python3/dist-packages/click/core.py", line 754, in invoke
return __callback(*args, **kwargs)
File "/usr/lib/python3/dist-packages/click/decorators.py", line 84, in
new_func
return ctx.invoke(f, obj, *args, **kwargs)
File "/usr/lib/python3/dist-packages/click/core.py", line 754, in invoke
return __callback(*args, **kwargs)
File "/usr/bin/ubuntu-drivers", line 432, in autoinstall
command_install(config)
File "/usr/bin/ubuntu-drivers", line 187, in command_install
UbuntuDrivers.detect.nvidia_desktop_pre_installation_hook(to_install)
File "/usr/lib/python3/dist-packages/UbuntuDrivers/detect.py", line 839, in
nvidia_desktop_pre_installation_hook
with_nvidia_kms = version >= 470
UnboundLocalError: local variable 'version' referenced before assignment
Skimming the version on my system it sure feels plausible:
def nvidia_desktop_pre_installation_hook(to_install):
'''Applies changes that need to happen before installing the NVIDIA
drivers'''
with_nvidia_kms = False
# Enable KMS if nvidia >= 470
for package_name in to_install:
if package_name.startswith('nvidia-driver-'):
try:
version = int(package_name.split('-')[-1])
except ValueError:
pass
finally:
with_nvidia_kms = version >= 470
if with_nvidia_kms:
set_nvidia_kms(1)
If there was an exception splitting, indexing, or converting to an
int, that 'version' variable may not have a value.
Thanks
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1993019/+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 1993581] Re: [snap] posix_spawn: No such file or directory
** Attachment removed: "disabled.png" https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1993581/+attachment/5631029/+files/disabled.png ** Attachment removed: "crash-logged.png" https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1993581/+attachment/5631028/+files/crash-logged.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1993581 Title: [snap] posix_spawn: No such file or directory Status in chromium-browser package in Ubuntu: Fix Released Bug description: Chromium from the edge channel fails to launch with % chromium [17618:17618:1019/163156.976437:FATAL:spawn_subprocess.cc(221)] posix_spawn: No such file or directory (2) % snap info chromium channels: latest/stable:106.0.5249.119 2022-10-14 (2136) 150MB - latest/candidate: 106.0.5249.119 2022-10-13 (2136) 150MB - latest/beta: 107.0.5304.36 2022-10-13 (2135) 152MB - latest/edge: 108.0.5355.0 2022-10-18 (2146) 153MB - installed: 108.0.5355.0 (2146) 153MB - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1993581/+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 1993581] Re: [snap] posix_spawn: No such file or directory
** Attachment added: "crash-logged.png" https://bugs.launchpad.net/bugs/1993581/+attachment/5631028/+files/crash-logged.png ** Attachment added: "disabled.png" https://bugs.launchpad.net/bugs/1993581/+attachment/5631029/+files/disabled.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1993581 Title: [snap] posix_spawn: No such file or directory Status in chromium-browser package in Ubuntu: Fix Released Bug description: Chromium from the edge channel fails to launch with % chromium [17618:17618:1019/163156.976437:FATAL:spawn_subprocess.cc(221)] posix_spawn: No such file or directory (2) % snap info chromium channels: latest/stable:106.0.5249.119 2022-10-14 (2136) 150MB - latest/candidate: 106.0.5249.119 2022-10-13 (2136) 150MB - latest/beta: 107.0.5304.36 2022-10-13 (2135) 152MB - latest/edge: 108.0.5355.0 2022-10-18 (2146) 153MB - installed: 108.0.5355.0 (2146) 153MB - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1993581/+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 1993581] -
The crash pad maintainer pointed out that I was wrong[1]: It is meant to
be enabled in Chromium. That led me to realize the now painfully obvious
cause: chrome_crashpad_handler was generated all along, just simply not
staged; It was introduced — for Linux — in 108 after all.
Now to the question, "is it useful for us, or should we leave it
disabled as in [2]?"
With two builds, one with crash pad disabled and one with it enabled, I
empirically ascertained that although reporting is disabled in Chromium
{attachment: disabled.png} for both, this does not mean that the crash
pad is not being used for both.
Rather, the crash pad makes crash reports generation possible. When
entering about:crash, which generates a sample crash, in the URL bar,
only the build with crash pad enabled generates a report in
about:crashes {attachment: crash-logged.png} and in
~/snap/chromium/common/chromium/Crash Reports/.
So it's better that the crash pad is left enabled.
[1]: https://bugs.chromium.org/p/chromium/issues/detail?id=1377365
[2]: https://launchpad.net/bugs/1926590
--
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/1993581
Title:
[snap] posix_spawn: No such file or directory
Status in chromium-browser package in Ubuntu:
Fix Released
Bug description:
Chromium from the edge channel fails to launch with
% chromium
[17618:17618:1019/163156.976437:FATAL:spawn_subprocess.cc(221)]
posix_spawn: No such file or directory (2)
% snap info chromium
channels:
latest/stable:106.0.5249.119 2022-10-14 (2136) 150MB -
latest/candidate: 106.0.5249.119 2022-10-13 (2136) 150MB -
latest/beta: 107.0.5304.36 2022-10-13 (2135) 152MB -
latest/edge: 108.0.5355.0 2022-10-18 (2146) 153MB -
installed: 108.0.5355.0 (2146) 153MB -
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1993581/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding
> Is there any ETA for finishing the legal review of the inclusion of
the non-free driver?
I'm afraid not. :(
> For these description items:
>
> - Distro version (`grep VERSION= /etc/os_release`);
> - GPU (`lscpu`);
>
> Do you mean?
>
> - Distro version (`grep VERSION= /etc/os-release`);
> - GPU (`lsgpu`);
Just found out about that one. :) Either is fine.
> Hardware decode on stable/hwacc worked out of the box for me, thanks!
Great to hear that! But do note that stable/hwacc is at 105 and falling
behind, so unresolved CVEs will start accumulating and I don't recommend
using it on a regular basis. Unfortunately, so far it is the only one I
could get VDAVideoDecoder on.
--
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 stable/hwacc chromium
2. Start Chromium,
snap run chromium
3. Open a video, e.g. one from https://github.com/chthomos/video-
media-samples.
4. Enter about:media-internals in the address bar, click the
corresponding box (if the video is playing, it will have the "(kPlay)"
identifier) 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,Dav1d}VideoDecoder;
- Xorg or Wayland (`echo $WAYLAND_DISPLAY`);
- Distro version (`grep VERSION= /etc/os_release`);
- GPU (`lscpu`);
- CPU generation (`lscpu`).
Currently it seems to work for all reporters on Xorg.
The version in stable/hwacc is fixed.
Versions in other channels (edge/hwacc, beta/hwacc, candidate/hwacc)
follow the Chromium release cycle (dev, beta and stable channels as in
https://omahaproxy.appspot.com/all.json?os=linux).
--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
Re: [Desktop-packages] [Bug 1996267] [NEW] Insecure passwort storage in Chromium (Snap)
Hello Erlenmayr, thanks for your report. > In the Snap package of Chromium, Chromium is not protecting passwords > with gnome-keyring (or KWallet). You can connect the corresponding interface for that: snap connect chromium:password-manager-service > As a result, copying the Chromium profile directory from the snap > directory gives access to all stored passwords. Please note those passwords are not stored in the clear, though they can be discovered by going into Chromium's Settings > Passwords. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1996267 Title: [snap] Doesn't store encrypted passwords unless interface is connected Status in chromium-browser package in Ubuntu: Confirmed Bug description: In the Snap package of Chromium, Chromium is not protecting passwords with gnome-keyring (or KWallet). As a result, copying the Chromium profile directory from the snap directory gives access to all stored passwords. This is a HIGH security risk. Regular users who are used to storing their passwords in browsers are probably unaware of this. Note that Chromium is started with the command line option “--password-store=basic”. This hack should never have been released to the public. The Chromium documentation states: > --password-store=basic (to use the plain text store) https://chromium.googlesource.com/chromium/src/+/master/docs/linux/password_storage.md To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1996267/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding
Unfortunately, no.
--
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 stable/hwacc chromium
2. Start Chromium,
snap run chromium
3. Open a video, e.g. one from https://github.com/chthomos/video-
media-samples.
4. Enter about:media-internals in the address bar, click the
corresponding box (if the video is playing, it will have the "(kPlay)"
identifier) 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,Dav1d}VideoDecoder;
- Xorg or Wayland (`echo $WAYLAND_DISPLAY`);
- Distro version (`grep VERSION= /etc/os_release`);
- GPU (`lscpu`);
- CPU generation (`lscpu`).
Currently it seems to work for all reporters on Xorg.
The version in stable/hwacc is fixed.
Versions in other channels (edge/hwacc, beta/hwacc, candidate/hwacc)
follow the Chromium release cycle (dev, beta and stable channels as in
https://omahaproxy.appspot.com/all.json?os=linux).
--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
Re: [Desktop-packages] [Bug 1995876] Re: drag and drop from desktop to docked app doesn't work
*** This bug is a duplicate of bug 1727321 *** https://bugs.launchpad.net/bugs/1727321 Fine, it's a duplicate. All I care about is that this bug gets fixed not how many duplicates of the same bug there are. Obviously if there are many duplicates it's important enough to people to want it fixed! On 11/8/22 8:59 AM, Daniel van Vugt wrote: > *** This bug is a duplicate of bug 1727321 *** > https://bugs.launchpad.net/bugs/1727321 > > This does seem to be an exact duplicate of bug 1727321, although that > one is a little terse. > > ** Tags added: dnd > > ** This bug has been marked a duplicate of bug 1727321 > drag and drop through the side panel to activate the window is not > working. > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1995876 Title: drag and drop from desktop to docked app doesn't work Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: I am using Ubuntu 22.04.1 LTS Nautilus 1:42.2-0ubuntu1 What I did: I click on a file, in this case an html file on my desktop and hold the left mouse button down. I drag the file on top of one of the docked apps Firefox for example. What I expected to happen: In any other non-Linux operating system I would expect that file to be opened by the application the file was dropped onto. What happened: In Ubuntu with Nautilus the file doesn't open with the docked application I dropped the file onto. What happened instead: Nothing ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Nov 7 07:16:03 2022 InstallationDate: Installed on 2022-06-03 (156 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to jammy on 2022-08-21 (77 days ago) usr_lib_nautilus: evince42.3-0ubuntu2 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 python3-nautilus 1.2.3-3.1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1995876/+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 1892559] Re: [MIR] ccid opensc pcsc-lite
Foundations doesn't have any aspirations of driving this forward currently. So we'll let it sit here for now. ** Tags added: fr-2980 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1892559 Title: [MIR] ccid opensc pcsc-lite Status in ccid package in Ubuntu: In Progress Status in opensc package in Ubuntu: Incomplete Status in pam-pkcs11 package in Ubuntu: Invalid Status in pcsc-lite package in Ubuntu: Incomplete Status in pcsc-perl package in Ubuntu: Invalid Status in pcsc-tools package in Ubuntu: Invalid Bug description: ==> ccid <== [Availability] ccid is in universe, and builds on all architectures. [Rationale] The desktop team and security team are interested in bringing smartcard authentication to enterprise desktop environments. [Security] No CVEs for ccid are listed in our database. Doesn't appear to bind to a socket. No privileged executables, but does have udev rules. Probably needs a security review. [Quality assurance] No test suite. Does require odd hardware that we'll probably need to buy. I don't see debconf questions. ccid is well maintained in Debian by upstream author. One open wishlist bug in BTS, harmless. One open bug in launchpad, not security, but looks very frustrating for the users. The upstream author was engaged but it never reached resolution. https://bugs.launchpad.net/ubuntu/+source/ccid/+bug/1175465 Has a debian/watch file. Quilt packaging. P: ccid source: no-dep5-copyright P: ccid source: package-uses-experimental-debhelper-compat-version 13 [Dependencies] Minimal dependencies, in main [Standards compliance] Appears to satisfy FHS and Debian policy [Maintenance] The desktop team will subscribe to bugs, however it is expected that the security team will assist with security-relevant questions. [Background information] ccid provides drivers to interact with usb-connected smart card readers. ==> libpam-pkcs11 <== [Availability] Source package pam-pkcs11 is in universe and builds on all architectures. [Rationale] The desktop team and security team are interested in bringing smartcard authentication to enterprise desktop environments. [Security] No CVEs in our database. Doesn't appear to bind to sockets. No privileged executables (but is a PAM module). As a PAM module this will require a security review. [Quality assurance] The package does not call pam-auth-update in its postinst #1650366 Does not ask questions during install. One Ubuntu bug claims very poor behaviour if a card isn't plugged in. No Debian bugs. Occasional updates in Debian by long-term maintainer. Does require odd hardware that we'll probably need to buy. Does not appear to run tests during build. Has scary warnings in the build logs. Has a debian/watch file. Ancient standards version; other smaller lintian messages, mostly documentation problems. Quilt packaging. [Dependencies] Depends on libcurl4, libldap-2.4-2, libpam0g, libpcsclite1, libssl1.1 All are in main. [Standards compliance] The package does not call pam-auth-update in its postinst #1650366 Otherwise looks to conform to FHS and Debian policies [Maintenance] The desktop team will subscribe to bugs, however it is expected that the security team will assist with security-relevant questions. [Background information] This PAM module can use CRLs and full-chain verification of certificates. It can also do LDAP, AD, and Kerberos username mapping. ==> libpcsc-perl <== [Availability] Source package pcsc-perl is in universe, builds for all architectures, plus i386 [Rationale] The desktop team and security team are interested in bringing smartcard authentication to enterprise desktop environments. [Security] There are no cves for pcsc-perl in our database. No privileged executables. Doesn't appear to bind to sockets. Probably needs a security review. [Quality assurance] Library package not intended to be used directly. No debconf questions. No bugs in Debian. No bugs in Ubuntu. Does require odd hardware that we'll probably need to buy. Tests exist, not run during the build; probably can't run during the build. Includes debian/watch file. A handful of lintian issues Quilt packaging. [Dependencies] libpcsc-perl depends upon libpcsclite1, libc6, perl, perlapi-5.30.0. All are in main. [Standards compliance] One oddity, Card.pod is stored in /usr/lib/x86_64-linux-gnu/perl5/5.30/Chipcard/PCSC/ Many other perl packages have .pod files in these directory trees so maybe it's fine, but it seems funny all the same. Otherwise appears to satisfy FHS and Debian policy. [Maintenance] The desktop team will subscribe to bugs, however it is expected that the security team will assist with security-relevant questions.
[Desktop-packages] [Bug 1993581] Re: [snap] posix_spawn: No such file or directory
** Attachment added: "crash-logged.png" https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1993581/+attachment/5631010/+files/crash-logged.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1993581 Title: [snap] posix_spawn: No such file or directory Status in chromium-browser package in Ubuntu: Fix Released Bug description: Chromium from the edge channel fails to launch with % chromium [17618:17618:1019/163156.976437:FATAL:spawn_subprocess.cc(221)] posix_spawn: No such file or directory (2) % snap info chromium channels: latest/stable:106.0.5249.119 2022-10-14 (2136) 150MB - latest/candidate: 106.0.5249.119 2022-10-13 (2136) 150MB - latest/beta: 107.0.5304.36 2022-10-13 (2135) 152MB - latest/edge: 108.0.5355.0 2022-10-18 (2146) 153MB - installed: 108.0.5355.0 (2146) 153MB - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1993581/+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 1993581] Re: [snap] posix_spawn: No such file or directory
The crash pad maintainer pointed out that I was wrong[1]: It is meant to
be enabled in Chromium. That led me to realize the now painfully obvious
cause: chrome_crashpad_handler was generated all along, just simply not
staged; It was introduced — for Linux — in 108 after all.
Now to the question, "is it useful for us, or should we leave it
disabled as in [2]?"
With two builds, one with crash pad disabled and one with it enabled, I
empirically ascertained that although reporting is disabled in Chromium
{attachment: disabled.png} for both, this does not mean that the crash
pad is not being used for both.
Rather, the crash pad makes crash reports generation possible. When
entering about:crash, which generates a sample crash, in the URL bar,
only the build with crash pad enabled generates a report in
about:crashes {attachment: crash-logged.png} and in
~/snap/chromium/common/chromium/Crash Reports/.
So it's better that the crash pad is left enabled.
[1]: https://bugs.chromium.org/p/chromium/issues/detail?id=1377365
[2]: https://launchpad.net/bugs/1926590
** Attachment added: "disabled.png"
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1993581/+attachment/5631009/+files/disabled.png
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1993581
Title:
[snap] posix_spawn: No such file or directory
Status in chromium-browser package in Ubuntu:
Fix Released
Bug description:
Chromium from the edge channel fails to launch with
% chromium
[17618:17618:1019/163156.976437:FATAL:spawn_subprocess.cc(221)]
posix_spawn: No such file or directory (2)
% snap info chromium
channels:
latest/stable:106.0.5249.119 2022-10-14 (2136) 150MB -
latest/candidate: 106.0.5249.119 2022-10-13 (2136) 150MB -
latest/beta: 107.0.5304.36 2022-10-13 (2135) 152MB -
latest/edge: 108.0.5355.0 2022-10-18 (2146) 153MB -
installed: 108.0.5355.0 (2146) 153MB -
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1993581/+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 1950040] Re: Wayland Screensharing broken in Ubuntu 21.10
I also have crash problems with Ubuntu 22.04 with recent versions of Firefox. I can share my whole screen, but not a single window. I did _not_ experience crashes with 22.04 and slightly older versions of Firefox. Some time in the last month, a new version of Firefox came along (I install with snap) and single window sharing stopped working. One of my crash logs if someone wants to check if this is strictly related to this bug: https://crash- stats.mozilla.org/report/index/99a89d4b-74f3-477b-b9e2-188d10221116 P.S. I just found https://bugzilla.mozilla.org/show_bug.cgi?id=1790496 which I think is tracking my issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal-gtk in Ubuntu. https://bugs.launchpad.net/bugs/1950040 Title: Wayland Screensharing broken in Ubuntu 21.10 Status in chromium-browser package in Ubuntu: Invalid Status in firefox package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Invalid Status in pipewire package in Ubuntu: Invalid Status in xdg-desktop-portal package in Ubuntu: Invalid Status in xdg-desktop-portal-gtk package in Ubuntu: Fix Released Bug description: Freshly installed Ubuntu 21.10, screen sharing does not work with any browser, tested the following options: - Firefox snap - Firefox deb - Chromium snap - Chromium flatpak Steps to reproduce: 1. Go to https://www.webrtc-experiment.com/Pluginfree-Screen-Sharing/#7325517390736006 2. Select to share the whole desktop in the xdg-desktop-portal 3. Notice the orange screen share indicator in Gnome-Shell but actually nothing is shared in the browser. This should be handled high priority since this is a critical feature during the pandemic. Filed against ubuntu-meta since I don't know exactly which package to blame, whether it's pipewire, xdg-desktop portal or some problem directely with mutter / gnome-shell, please reassign accordingly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1950040/+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 1996705] Re: many xruns independently of soundcard and latency
Thank you for taking the time to report this issue and helping to make Ubuntu better. Examining the information you have given us, this does not appear to be a bug report so we are closing it and converting it to a question in the support tracker. We understand the difficulties you are facing, but it is better to raise problems you are having in the support tracker at https://answers.launchpad.net/ubuntu if you are uncertain if they are bugs. If you would prefer live chat support, you can find an IRC support channel for your flavor of Ubuntu here: https://wiki.ubuntu.com/IRC/ChannelList. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org. For help on reporting bugs, see https://help.ubuntu.com/community/ReportingBugs. ** Changed in: jackd2 (Ubuntu) Status: New => Invalid ** Converted to question: https://answers.launchpad.net/ubuntu/+source/jackd2/+question/703843 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1996705 Title: many xruns independently of soundcard and latency Status in jackd2 package in Ubuntu: Invalid Bug description: Hi, xruns occur (1-3 every 8-15 seconds) happens with any soundcard, at any latency stops when power supply is unplugged To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1996705/+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 1995743] Re: webdav error trying to connect to nextcloud
** Package changed: ubuntu => gvfs (Ubuntu) ** Tags added: kinetic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1995743 Title: webdav error trying to connect to nextcloud Status in gvfs package in Ubuntu: New Bug description: upgraded to ubuntu 22.10 from 22.04 and webdav fails to connect to nextcloud. Reimaged back to 22.04 and it worked. Error message is "Message recipient disconnected from message bus without replying Please select another viewer and try again." I have tried webdav from mate 22.10 and gnome 22.10 with same failure. Crash report fails as well but I was able to get a copy before deleted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1995743/+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 1995743] [NEW] webdav error trying to connect to nextcloud
You have been subscribed to a public bug: upgraded to ubuntu 22.10 from 22.04 and webdav fails to connect to nextcloud. Reimaged back to 22.04 and it worked. Error message is "Message recipient disconnected from message bus without replying Please select another viewer and try again." I have tried webdav from mate 22.10 and gnome 22.10 with same failure. Crash report fails as well but I was able to get a copy before deleted. ** Affects: gvfs (Ubuntu) Importance: Undecided Status: New ** Tags: gvfsd-dav webdav -- webdav error trying to connect to nextcloud https://bugs.launchpad.net/bugs/1995743 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs 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 1978989] Re: FTBFS on armhf since version 102: the final link step segfaults
Also happened on the dev snap and this patch solved it, thanks! ** Changed in: chromium-browser (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1978989 Title: FTBFS on armhf since version 102: the final link step segfaults Status in chromium-browser package in Ubuntu: Fix Released Bug description: Example build log: [51110/51110] LINK ./chrome FAILED: chrome python3 "../../build/toolchain/gcc_link_wrapper.py" --output="./chrome" -- ../../../../../usr/bin/clang++-10 -Wl,--version-script=../../build/linux/chrome.map -Wl,--build-id=sha1 -fPIC -Wl,-z,noexecstack -Wl,-z,relro -Wl,-z,now --target=arm-linux-gnueabihf -no-canonical-prefixes -Wl,-O2 -Wl,--gc-sections -rdynamic -Wl,-z,defs -Wl,--as-needed -nostdlib++ -pie -Wl,--disable-new-dtags -Wl,-rpath=\$ORIGIN -o "./chrome" -Wl,--start-group @"./chrome.rsp" ./libffmpeg.so -Wl,--end-group -ldl -lpthread -lrt -lgmodule-2.0 -lgobject-2.0 -lgthread-2.0 -lglib-2.0 -lnss3 -lnssutil3 -lsmime3 -lplds4 -lplc4 -lnspr4 -latk-1.0 -latk-bridge-2.0 -lcups -lgio-2.0 -ldbus-1 -latomic -lresolv -lexpat -luuid -ldrm -lxcb -lxkbcommon -lX11 -lXcomposite -lXdamage -lXext -lXfixes -lXrender -lXrandr -lXtst -lgbm -lwayland-client -lpangocairo-1.0 -lpango-1.0 -lcairo -lasound -lXi -lpci -latspi -lxshmfence clang++-10: error: unable to execute command: Segmentation fault (core dumped) clang++-10: error: linker command failed due to signal (use -v to see invocation) ninja: build stopped: subcommand failed. This is observed for the deb package builds targeting bionic (built with clang 10), on armhf only (other architectures build fine). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1978989/+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 1961508] Re: Dock displaying over window after resuming from blank screen
Same issue here. Ubuntu 22.04.1 LTS with Wayland. Everything was fine before the upgrade from Ubuntu 20.04. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1961508 Title: Dock displaying over window after resuming from blank screen Status in Dash to dock: Unknown Status in Mutter: New Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I have Blank Screen set to happen after 2 minutes of inactivity. When resuming from a Blank Screen (by moving the mouse or touching the keyboard), the Dock is displayed over the top of the current program. To get it back to normal I need to click "Restore Down" on the current programs window and then "Maximize" so that the Dock no longer overlaps it. (Note: I have Auto-hide dock turned off.) This only happens sometimes. I can't reproduce the bug it every time. - 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu - Ubuntu 21.10 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center - Not sure (I guess the Dock is part of the Gnome interface?) 3) What you expected to happen - Dock should not overlap the current program on resume from screen blank. 4) What happened instead - The Dock overlaps the current program on resume from screen blank. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2022-02-18 (24 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Package: gnome-shell-extension-ubuntu-dock PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1 Tags: wayland-session impish Uname: Linux 5.13.0-35-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1961508/+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 1950282] Re: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support
to SRU team this is why & when we would need this modemmanager package soon at least 2 of top 3 PC OEMs have introduced new RPL-based platforms + FM350-GL to launch with Jammy (22.04) in Q1 '23 and with the fore- runners we need conclude the "feature complete" image release by Nov-18, 2022, and final (production candidate) release by Dec-09, 2022 So the requested timelines for modemmanager updated package is SRU (for Jammy) by the end of Nov '22. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1950282 Title: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Incomplete Status in modemmanager package in Ubuntu: New Bug description: :55:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device [14c3:4d75] (rev 01) Subsystem: Hewlett-Packard Company Device [103c:8914] https://lore.kernel.org/linux- wireless/20211101035635.26999-1-ricardo.marti...@linux.intel.com/ Modemmanager requires >= 1.19.1, the detail info is in lp:1962525 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X136 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-07-13 (119 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Intel Corporation Alder Lake Client Platform Package: linux-firmware 1.187.20+staging.31 PackageArchitecture: all ProcFB: 0 i915 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9007-oem root=UUID=56278c18-b6d3-4b07-b758-32f574db7ae0 ro i915.force_probe=46c0 automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-9007.7+staging.29-oem 5.14.14 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.14.0-9007-oem N/A linux-backports-modules-5.14.0-9007-oem N/A linux-firmware 1.187.20+staging.31 Tags: focal Uname: Linux 5.14.0-9007-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 08/23/2021 dmi.bios.vendor: Intel Corporation dmi.bios.version: ADLPFWI1.R00.2347.A00.2108230957 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: AlderLake-M LP5 RVP dmi.board.vendor: Intel Corporation dmi.board.version: 1 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.43 dmi.modalias: dmi:bvnIntelCorporation:bvrADLPFWI1.R00.2347.A00.2108230957:bd08/23/2021:efr1.43:svnIntelCorporation:pnAlderLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnAlderLake-MLP5RVP:rvr1:cvnIntelCorporation:ct9:cvr0.1:sku01010002: dmi.product.family: Alder Lake Client System dmi.product.name: Alder Lake Client Platform dmi.product.sku: 01010002 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1950282/+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 1981190] Re: Fibcom FM350-GL not able connect to network with 5G mode
to SRU team this is why & when we would need this modemmanager package soon at least 2 of top 3 PC OEMs have introduced new RPL-based platforms + FM350-GL to launch with Jammy (22.04) in Q1 '23 and with the fore- runners we need conclude the "feature complete" image release by Nov-18, 2022, and final (production candidate) release by Dec-09, 2022 So the requested timelines for modemmanager updated package is SRU (for Jammy) by the end of Nov '22. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmbim in Ubuntu. https://bugs.launchpad.net/bugs/1981190 Title: Fibcom FM350-GL not able connect to network with 5G mode Status in OEM Priority Project: Confirmed Status in libmbim package in Ubuntu: Confirmed Status in libqmi package in Ubuntu: Confirmed Status in modemmanager package in Ubuntu: Confirmed Bug description: Fibcom FM350-GL can support 5G network (https://www.fibocom.com/en/products/5G-FM350-GL.html). But in Ubuntu 22.04, system can only connect to mobile network with 4G mode. General | path: /org/freedesktop/ModemManager1/Modem/0 |device id: e045a43cd7977e24e1a11af409a780c054e26b0e Hardware | manufacturer: generic |model: MBIM [14C3:4D75] |firmware revision: 81600..00.29.18.01_GC | C01 | h/w revision: V1.0.6 |supported: gsm-umts, lte | current: gsm-umts, lte | equipment id: 352750140002001 System | device: /sys/devices/pci:00/:00:1c.0/:73:00.0 | drivers: mtk_t7xx | plugin: generic | primary port: wwan0mbim0 |ports: wwan0 (net), wwan0at0 (at), wwan0mbim0 (mbim) Status | unlock retries: sim-pin (3), sim-pin2 (3) |state: connected | power state: on | access tech: lte | signal quality: 74% (recent) Modes|supported: allowed: 3g, 4g; preferred: none | current: allowed: 3g, 4g; preferred: none IP |supported: ipv4, ipv6, ipv4v6 3GPP | imei: 352750140002001 |enabled locks: sim, fixed-dialing | operator id: 46692 |operator name: Chunghwa Telecom | registration: home 3GPP EPS | ue mode of operation: csps-2 | initial bearer path: /org/freedesktop/ModemManager1/Bearer/0 SIM | primary sim path: /org/freedesktop/ModemManager1/SIM/0 Bearer |paths: /org/freedesktop/ModemManager1/Bearer/1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-06-15 (26 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) NonfreeKernelModules: nvidia_modeset nvidia Package: modemmanager 1.18.6-1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.17.0-9012.13+exp.27-oem 5.17.9 Tags: jammy Uname: Linux 5.17.0-9012-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1981190/+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 1996705] Re: many xruns independently of soundcard and latency
Lenovo ThinkPad P15s -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1996705 Title: many xruns independently of soundcard and latency Status in jackd2 package in Ubuntu: New Bug description: Hi, xruns occur (1-3 every 8-15 seconds) happens with any soundcard, at any latency stops when power supply is unplugged To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1996705/+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 1996705] Re: many xruns independently of soundcard and latency
Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.6 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.15.0-50-lowlatency (64-bit) Graphics Platform: X11 Processors: 4 × 11th Gen Intel® Core™ i7-1185G7 @ 3.00GHz Memory: 31.1 Gio of RAM Graphics Processor: Mesa Intel® Xe Graphics -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1996705 Title: many xruns independently of soundcard and latency Status in jackd2 package in Ubuntu: New Bug description: Hi, xruns occur (1-3 every 8-15 seconds) happens with any soundcard, at any latency stops when power supply is unplugged To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1996705/+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 1996705] Re: many xruns independently of soundcard and latency
typical jackd messages: Wed Oct 12 10:00:14 2022: ERROR: JackEngine::XRun: client = Bitwig Studio was not finished, state = Running Wed Oct 12 10:00:14 2022: ERROR: JackAudioDriver::ProcessGraphAsyncMaster: Process error Wed Oct 12 10:00:14 2022: Jack: JackEngine::ClientNotify: no callback for notification = 3 Wed Oct 12 10:00:14 2022: Jack: JackEngine::ClientNotify: no callback for notification = 3 Wed Oct 12 10:00:14 2022: Jack: JackClient::ClientNotify ref = 2 name = dbusapi notify = 3 Wed Oct 12 10:00:14 2022: Jack: JackClient::kXRunCallback Wed Oct 12 10:00:14 2022: Jack: JackEngine::ClientNotify: no callback for notification = 3 Wed Oct 12 10:00:14 2022: Jack: JackEngine::ClientNotify: no callback for notification = 3 Wed Oct 12 10:00:14 2022: Jack: JackEngine::ClientNotify: no callback for notification = 3 Wed Oct 12 10:00:14 2022: Jack: JackEngine::ClientNotify: no callback for notification = 3 Wed Oct 12 10:00:14 2022: Jack: Process: graph not finished! Wed Oct 12 10:00:14 2022: Jack: Process: waiting to switch delta = 10692 Wed Oct 12 10:00:14 2022: ERROR: JackAudioDriver::ProcessGraphAsyncMaster: Process error Wed Oct 12 10:00:14 2022: Jack: Process: graph not finished! Wed Oct 12 10:00:14 2022: Jack: Process: waiting to switch delta = 16085 Wed Oct 12 10:00:14 2022: ERROR: JackAudioDriver::ProcessGraphAsyncMaster: Process error Wed Oct 12 10:00:14 2022: Jack: Process: graph not finished! Wed Oct 12 10:00:14 2022: Jack: Process: waiting to switch delta = 21391 Wed Oct 12 10:00:14 2022: ERROR: JackAudioDriver::ProcessGraphAsyncMaster: Process error Wed Oct 12 10:00:19 2022: Jack: Process: graph not finished! Wed Oct 12 10:00:19 2022: Jack: Process: waiting to switch delta = 5481 Wed Oct 12 10:00:19 2022: ERROR: JackEngine::XRun: client = Bitwig Studio was not finished, state = Running Wed Oct 12 10:00:19 2022: ERROR: JackAudioDriver::ProcessGraphAsyncMaster: Process error Wed Oct 12 10:00:19 2022: Jack: Process: graph not finished! Wed Oct 12 10:00:19 2022: Jack: Process: waiting to switch delta = 10647 Wed Oct 12 10:00:19 2022: ERROR: JackEngine::XRun: client = Bitwig Studio was not finished, state = Triggered Wed Oct 12 10:00:19 2022: ERROR: JackAudioDriver::ProcessGraphAsyncMaster: Process error Wed Oct 12 10:00:19 2022: Jack: Process: graph not finished! Wed Oct 12 10:00:19 2022: Jack: Process: waiting to switch delta = 16094 Wed Oct 12 10:00:19 2022: ERROR: JackAudioDriver::ProcessGraphAsyncMaster: Process error Wed Oct 12 10:00:19 2022: Jack: JackRequest::Notification Wed Oct 12 10:00:19 2022: Jack: JackEngine::ClientNotify: no callback for notification = 3 Wed Oct 12 10:00:19 2022: Jack: JackEngine::ClientNotify: no callback for notification = 3 Wed Oct 12 10:00:19 2022: Jack: JackClient::ClientNotify ref = 2 name = dbusapi notify = 3 Wed Oct 12 10:00:19 2022: Jack: JackClient::kXRunCallback Wed Oct 12 10:00:19 2022: Jack: JackEngine::ClientNotify: no callback for notification = 3 Wed Oct 12 10:00:19 2022: Jack: JackEngine::ClientNotify: no callback for notification = 3 Wed Oct 12 10:00:19 2022: Jack: JackEngine::ClientNotify: no callback for notification = 3 Wed Oct 12 10:00:19 2022: Jack: JackEngine::ClientNotify: no callback for notification = 3 Wed Oct 12 10:00:19 2022: Jack: JackRequest::Notification Wed Oct 12 10:00:19 2022: Jack: JackEngine::ClientNotify: no callback for notification = 3 Wed Oct 12 10:00:19 2022: Jack: JackEngine::ClientNotify: no callback for notification = 3 Wed Oct 12 10:00:19 2022: Jack: JackClient::ClientNotify ref = 2 name = dbusapi notify = 3 Wed Oct 12 10:00:19 2022: Jack: JackClient::kXRunCallback Wed Oct 12 10:00:19 2022: Jack: JackEngine::ClientNotify: no callback for notification = 3 Wed Oct 12 10:00:19 2022: Jack: JackEngine::ClientNotify: no callback for notification = 3 Wed Oct 12 10:00:19 2022: Jack: JackEngine::ClientNotify: no callback for notification = 3 Wed Oct 12 10:00:19 2022: Jack: JackEngine::ClientNotify: no callback for notification = 3 Wed Oct 12 10:00:24 2022: Jack: Process: graph not finished! Wed Oct 12 10:00:24 2022: Jack: JackRequest::Notification Wed Oct 12 10:00:24 2022: Jack: JackEngine::ClientNotify: no callback for notification = 3 Wed Oct 12 10:00:24 2022: Jack: JackEngine::ClientNotify: no callback for notification = 3 Wed Oct 12 10:00:24 2022: Jack: JackClient::ClientNotify ref = 2 name = dbusapi notify = 3 Wed Oct 12 10:00:24 2022: Jack: JackClient::kXRunCallback Wed Oct 12 10:00:24 2022: Jack: JackEngine::ClientNotify: no callback for notification = 3 Wed Oct 12 10:00:24 2022: Jack: JackEngine::ClientNotify: no callback for notification = 3 Wed Oct 12 10:00:24 2022: Jack: JackEngine::ClientNotify: no callback for notification = 3 Wed Oct 12 10:00:24 2022: Jack: JackEngine::ClientNotify: no callback for notification = 3 Wed Oct 12 10:00:24 2022: Jack: JackRequest::Notification Wed Oct 12 10:00:24 2022: Jack: JackEngine::ClientNotify: no callback for notification = 3 Wed Oct 12
[Desktop-packages] [Bug 1996705] Re: many xruns independently of soundcard and latency
when I plug OR unplug PSU, an alsa-jack client appears shortly and disappears, named: alsa-jack.jackP.2436.13: out_000 out_001 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1996705 Title: many xruns independently of soundcard and latency Status in jackd2 package in Ubuntu: New Bug description: Hi, xruns occur (1-3 every 8-15 seconds) happens with any soundcard, at any latency stops when power supply is unplugged To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1996705/+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 1996705] [NEW] many xruns independently of soundcard and latency
Public bug reported: Hi, xruns occur (1-3 every 8-15 seconds) happens with any soundcard, at any latency stops when power supply is unplugged ** Affects: jackd2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1996705 Title: many xruns independently of soundcard and latency Status in jackd2 package in Ubuntu: New Bug description: Hi, xruns occur (1-3 every 8-15 seconds) happens with any soundcard, at any latency stops when power supply is unplugged To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1996705/+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
