[Desktop-packages] [Bug 1935604] [NEW] network-manager-applet: stored auto connect VPN gets changed when viewing settings
Public bug reported: Xubuntu 20.04.2 LTS focal Applet version from network-manager-gnome 1.8.24-1uubuntu3 amd64 Please note: the issue described below only seems to occur when building the applet on my xubuntu 20.04.2 LTS machines. (I have not tried other ubuntu variants). If I'm on my home xubuntu machine the problem seems to appear whether I'm using the ubuntu package, the ubuntu source archive, the upstream archive, or the upstream source distribution. The problem does _not_ seem to occur when building the exact same upstream sources in debian using xfce as its window manager. (I have not tried other debian variants). Experienced If I open an existing connection with an existing VPN, the selected VPN in the VPN drop down list appears to always show the incorrect VPN. This results in a situation where opening a connection and clicking "save" on the general tab always changes the selected VPN, even if I did not make any change. Expected When I open an existing connection, the VPN listed should be the VPN actually on the connection, not some other random VPN from my list Reproduction Steps 1. Open nm-connection-editor 2. Add multiple VPNs with different names (i.e. US VPN East, US VPN West, Corp VPN East, Corp VPN Europe, Corp VPN West) 3. Create a connection (I've reproduced this on wireless and wired connections) 4. Set the connection to automatically connect to VPN 5. Choose any VPN to automatically connect to 6. Save and close 7. re-open nm-connection-editor 8. Edit the same connection created before 9. Note that the automatic VPN has changed to a different VPN in your list without you having to do antying 10. Click save without changing anything 11. re-open network-manager-editor 12. Note again that the VPN connection is _again_ incorrect The symptom you should be experiencing is that the VPN that is chosen when you save - gets saved and used by the connection, but the user interface does not display the correct VPN when viewed in the connection editor. This means that any time you edit the connection it might be swapping your selected VPN without your knowledge. ** Affects: network-manager-applet (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1935604 Title: network-manager-applet: stored auto connect VPN gets changed when viewing settings Status in network-manager-applet package in Ubuntu: New Bug description: Xubuntu 20.04.2 LTS focal Applet version from network-manager-gnome 1.8.24-1uubuntu3 amd64 Please note: the issue described below only seems to occur when building the applet on my xubuntu 20.04.2 LTS machines. (I have not tried other ubuntu variants). If I'm on my home xubuntu machine the problem seems to appear whether I'm using the ubuntu package, the ubuntu source archive, the upstream archive, or the upstream source distribution. The problem does _not_ seem to occur when building the exact same upstream sources in debian using xfce as its window manager. (I have not tried other debian variants). Experienced If I open an existing connection with an existing VPN, the selected VPN in the VPN drop down list appears to always show the incorrect VPN. This results in a situation where opening a connection and clicking "save" on the general tab always changes the selected VPN, even if I did not make any change. Expected When I open an existing connection, the VPN listed should be the VPN actually on the connection, not some other random VPN from my list Reproduction Steps 1. Open nm-connection-editor 2. Add multiple VPNs with different names (i.e. US VPN East, US VPN West, Corp VPN East, Corp VPN Europe, Corp VPN West) 3. Create a connection (I've reproduced this on wireless and wired connections) 4. Set the connection to automatically connect to VPN 5. Choose any VPN to automatically connect to 6. Save and close 7. re-open nm-connection-editor 8. Edit the same connection created before 9. Note that the automatic VPN has changed to a different VPN in your list without you having to do antying 10. Click save without changing anything 11. re-open network-manager-editor 12. Note again that the VPN connection is _again_ incorrect The symptom you should be experiencing is that the VPN that is chosen when you save - gets saved and used by the connection, but the user interface does not display the correct VPN when viewed in the connection editor. This means that any time you edit the connection it might be swapping your selected VPN without your knowledge. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1935604/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net
[Desktop-packages] [Bug 1923381] Re: [Lenovo ThinkPad T450s] regression: no display when waking from suspend
** Changed in: xorg-server (Ubuntu) Status: Expired => New ** Tags added: suspend-resume -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1923381 Title: [Lenovo ThinkPad T450s] regression: no display when waking from suspend Status in xorg-server package in Ubuntu: New Bug description: I have two Lenovo T450s laptops running Ubuntu 20.10. A few weeks ago, suspend stopped working properly: with an external monitor, the external monitor no longer registers the connection when waking from suspend. Without, the laptop screen is black and the machine unresponsive until hard-rebooted, when waking from suspend ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-70.78-generic 5.4.94 Uname: Linux 5.4.0-70-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Apr 11 17:53:01 2021 DistUpgraded: 2020-06-01 15:46:34,953 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.4.0-66-generic, x86_64: installed virtualbox, 6.1.16, 5.4.0-67-generic, x86_64: installed virtualbox, 6.1.16, 5.4.0-70-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:5036] InstallationDate: Installed on 2019-01-24 (808 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: LENOVO 20BXCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-70-generic root=UUID=a6081f39-700f-4698-bda4-464e53d9d229 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-06-01 (314 days ago) dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: JBET66WW (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET66WW(1.30):bd09/13/2017:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450s dmi.product.name: 20BXCTO1WW dmi.product.sku: LENOVO_MT_20BX_BU_Think_FM_ThinkPad T450s dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.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-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1923381/+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 1923381] Re: [Lenovo ThinkPad T450s] regression: no display when waking from suspend
[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg-server (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1923381 Title: [Lenovo ThinkPad T450s] regression: no display when waking from suspend Status in xorg-server package in Ubuntu: Expired Bug description: I have two Lenovo T450s laptops running Ubuntu 20.10. A few weeks ago, suspend stopped working properly: with an external monitor, the external monitor no longer registers the connection when waking from suspend. Without, the laptop screen is black and the machine unresponsive until hard-rebooted, when waking from suspend ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-70.78-generic 5.4.94 Uname: Linux 5.4.0-70-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Apr 11 17:53:01 2021 DistUpgraded: 2020-06-01 15:46:34,953 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.4.0-66-generic, x86_64: installed virtualbox, 6.1.16, 5.4.0-67-generic, x86_64: installed virtualbox, 6.1.16, 5.4.0-70-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:5036] InstallationDate: Installed on 2019-01-24 (808 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: LENOVO 20BXCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-70-generic root=UUID=a6081f39-700f-4698-bda4-464e53d9d229 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-06-01 (314 days ago) dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: JBET66WW (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET66WW(1.30):bd09/13/2017:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450s dmi.product.name: 20BXCTO1WW dmi.product.sku: LENOVO_MT_20BX_BU_Think_FM_ThinkPad T450s dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.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-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1923381/+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 1935570] Re: [HP Compaq Pro 6300 MT, Realtek ALC221, Black Mic, Front] Recording problem
Please plug the mic in, and run pa-info > pa-info.txt, then upload the pa-info.txt -- 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/1935570 Title: [HP Compaq Pro 6300 MT, Realtek ALC221, Black Mic, Front] Recording problem Status in alsa-driver package in Ubuntu: New Bug description: Hi, the mic does not work in my Ubuntu OS. Can you guys do something i am very frustrated? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ravisah96 1576 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jul 8 19:57:18 2021 InstallationDate: Installed on 2021-06-08 (30 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Mic, Front Symptom_Type: None of the above Title: [HP Compaq Pro 6300 MT, Realtek ALC221, Black Mic, Front] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2012 dmi.bios.release: 2.83 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: K01 v02.83 dmi.board.asset.tag: MXL312111Y dmi.board.name: 339A dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: MXL312111Y dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrK01v02.83:bd10/29/2012:br2.83:svnHewlett-Packard:pnHPCompaqPro6300MT:pvr:rvnHewlett-Packard:rn339A:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP Compaq Pro 6300 MT dmi.product.sku: C6Z93UT#ABA dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1935570/+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 1934286] Re: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases.
As the ModemManager is only considered, mbim-proxy is started by the ModemManager service: "Jul 09 08:20:21 ubuntu-ThinkEdge-SE30 ModemManager[578]: spawning new mbim-proxy (try 1)..." And, the execution path is decided at https://github.com/linux-mobile-broadband/libmbim/blob/master/src/libmbim-glib/mbim-device.c#L1421: argc[0] = g_strdup (LIBEXEC_PATH "/mbim-proxy"); This looks like that the mbim-proxy is only used by the ModemManager service. -- 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/1934286 Title: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases. Status in OEM Priority Project: Confirmed Status in libmbim package in Ubuntu: New Status in libqmi package in Ubuntu: New Status in modemmanager package in Ubuntu: New Status in modemmanager source package in Focal: Fix Committed Status in libmbim source package in Hirsute: Fix Committed Status in libqmi source package in Hirsute: Fix Committed Status in modemmanager source package in Hirsute: Fix Committed Bug description: [Impact] Some IOT products use wireless modems which can be working only when recent versions of the ModemManager suite are used. The following 2 modems need the ModemManager suite to be upgraded: * Foxconn SDX55 T99W175 5G sub6 PCIE Modem * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem The main fix requested is to add the FCC unlock mechanism for Foxconn modems. * FCC unlock operation for Foxconn modems https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/534/commits * dms: new 'Foxconn Set FCC authentication' command https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/merge_requests/254/commits The minimum versions of the ModemManager suite required to enable the support for the above 2 mentioned modems have been verified: (LP: #1928665) * ModemManager: 1.16.6 * libmbim: 1.24.8 * libqmi : 1.28.6 The ModemManager suite in the Impish release meets the requirements. [Test Plan] = How to Reproduce the Bug = Execute the following commands to list the modems detected by ModemManager in Hirsute and Focal releases: $ mmcli --list-modems No modems were found = Test Procedure = 1. Install the Ubuntu system on the tested hardware The following images will be used to verify the version of the ModemManager suite: * Impish: https://cdimage.ubuntu.com/daily-live/current/impish-desktop-amd64.iso * Hirsute: https://releases.ubuntu.com/21.04/ubuntu-21.04-desktop-amd64.iso * Focal: https://releases.ubuntu.com/focal/ubuntu-20.04.2.0-desktop-amd64.iso 2. Upgrade the kernel and driver ( for Foxconn and Quectel modem ) The kernel needs to get some patches from 5.13 and includes a back ported Quectel driver to support these 2 modems. We have prepared a kernel packages for testing: https://people.canonical.com/~mschiu77/lp1928665/v2/ 3. Install the ModemManager suite ( for Hirsute and Focal releases ) The ModemManager suite will be installed from the -proposed component: $ sudo apt update $ sudo apt install modemmanager $ sudo apt install libqmi-utils 4. Execute the following commands 4.1 Get the run-time environment $ uname -ar $ lsb_release -a $ mmcli -V $ qmicli -V 4.2 Check the status of the ModemManager service $ sudo systemctl status ModemManager.service 4.3 List the detected modems $ mmcli --list-modems 4.4 Check the modem’s status $ mmcli --modem 0 4.5 Install and execute Lenovo’s FCC unlock app ( for Quectel modem only ) $ sudo snap install --devmode --dangerous dpr-wwan_1.0-wwan- test_amd64.snap 4.6 Enable the detected modem $ sudo mmcli --modem 0 --enable 4.7 Check the modem’s status $ mmcli --modem 0 = Analyze the Tested Result = 1. Check if installed packages are working The result of test procedure 4.1 and 4.2 can be used to make sure the installed packages are working. If the Modemmanager.service is active(running), the packages are working. 2. Check if the supported modem can be detected The result of test procedure 4.3 can be used to see if the modem can be detected by ModemManager or not. The supported modems should be listed. 3. Check if the modem can be enabled If the modem can be enabled, the state of the modem in the test procedure 4.7 will be set to be registered. = Certification Validation = Additionally to the aforementioned test cases, the Certification Team will perform some coverage testing across supported devices to make sure the other modems still work as expected. [Where problems could occur] There is a risk that modems supported in the old versions of ModemManager suite may not be supported in the newer versions. [Other Info] We need to upgrade to these 3 packages (in Impish) at
Re: [Desktop-packages] [Bug 1935570] Re: [HP Compaq Pro 6300 MT, Realtek ALC221, Black Mic, Front] Recording problem
Hi, When I plug the headphones in it detects microphone as input but I don't get the microphone working and then I don't get output sound. On Thu, Jul 8, 2021, 9:50 PM Hui Wang <1935...@bugs.launchpad.net> wrote: > After you plug a mic to the mic jack, does the system detect this > plugging? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1935570 > > Title: > [HP Compaq Pro 6300 MT, Realtek ALC221, Black Mic, Front] Recording > problem > > Status in alsa-driver package in Ubuntu: > New > > Bug description: > Hi, > > the mic does not work in my Ubuntu OS. Can you guys do something i am > very frustrated? > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: alsa-base 1.0.25+dfsg-0ubuntu5 > ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 > Uname: Linux 5.8.0-59-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27.18 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: ravisah96 1576 F pulseaudio > CasperMD5CheckResult: skip > CurrentDesktop: ubuntu:GNOME > Date: Thu Jul 8 19:57:18 2021 > InstallationDate: Installed on 2021-06-08 (30 days ago) > InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 > (20210209.1) > PackageArchitecture: all > ProcEnviron: >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > SourcePackage: alsa-driver > Symptom: audio > Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed > Symptom_Card: Built-in Audio - HDA Intel PCH > Symptom_Jack: Black Mic, Front > Symptom_Type: None of the above > Title: [HP Compaq Pro 6300 MT, Realtek ALC221, Black Mic, Front] > Recording problem > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 10/29/2012 > dmi.bios.release: 2.83 > dmi.bios.vendor: Hewlett-Packard > dmi.bios.version: K01 v02.83 > dmi.board.asset.tag: MXL312111Y > dmi.board.name: 339A > dmi.board.vendor: Hewlett-Packard > dmi.chassis.asset.tag: MXL312111Y > dmi.chassis.type: 6 > dmi.chassis.vendor: Hewlett-Packard > dmi.modalias: > dmi:bvnHewlett-Packard:bvrK01v02.83:bd10/29/2012:br2.83:svnHewlett-Packard:pnHPCompaqPro6300MT:pvr:rvnHewlett-Packard:rn339A:rvr:cvnHewlett-Packard:ct6:cvr: > dmi.product.family: 103C_53307F G=D > dmi.product.name: HP Compaq Pro 6300 MT > dmi.product.sku: C6Z93UT#ABA > dmi.sys.vendor: Hewlett-Packard > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1935570/+subscriptions > -- 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/1935570 Title: [HP Compaq Pro 6300 MT, Realtek ALC221, Black Mic, Front] Recording problem Status in alsa-driver package in Ubuntu: New Bug description: Hi, the mic does not work in my Ubuntu OS. Can you guys do something i am very frustrated? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ravisah96 1576 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jul 8 19:57:18 2021 InstallationDate: Installed on 2021-06-08 (30 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Mic, Front Symptom_Type: None of the above Title: [HP Compaq Pro 6300 MT, Realtek ALC221, Black Mic, Front] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2012 dmi.bios.release: 2.83 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: K01 v02.83 dmi.board.asset.tag: MXL312111Y dmi.board.name: 339A dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: MXL312111Y dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrK01v02.83:bd10/29/2012:br2.83:svnHewlett-Packard:pnHPCompaqPro6300MT:pvr:rvnHewlett-Packard:rn339A:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP Compaq Pro 6300 MT dmi.product.sku: C6Z93UT#ABA dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1935570/+subscriptions -- Mailing
[Desktop-packages] [Bug 1935581] [NEW] evince no longer shows bookmarks for DjVu files
Public bug reported: Evince used to have no problem showing bookmarks when viewing a djvu file. Version 3.22.1 was fine. Now evince version 3.38.2 just shows a blank pane for bookmarks. I'm not sure if the bug is in evince or in djvused, so the bug report is mirrored for each package. The djvused bug report has more details: https://bugs.launchpad.net/ubuntu/+source/djvulibre/+bug/1935580 ** Affects: evince (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1935581 Title: evince no longer shows bookmarks for DjVu files Status in evince package in Ubuntu: New Bug description: Evince used to have no problem showing bookmarks when viewing a djvu file. Version 3.22.1 was fine. Now evince version 3.38.2 just shows a blank pane for bookmarks. I'm not sure if the bug is in evince or in djvused, so the bug report is mirrored for each package. The djvused bug report has more details: https://bugs.launchpad.net/ubuntu/+source/djvulibre/+bug/1935580 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1935581/+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 1935570] Re: [HP Compaq Pro 6300 MT, Realtek ALC221, Black Mic, Front] Recording problem
After you plug a mic to the mic jack, does the system detect this plugging? -- 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/1935570 Title: [HP Compaq Pro 6300 MT, Realtek ALC221, Black Mic, Front] Recording problem Status in alsa-driver package in Ubuntu: New Bug description: Hi, the mic does not work in my Ubuntu OS. Can you guys do something i am very frustrated? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ravisah96 1576 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jul 8 19:57:18 2021 InstallationDate: Installed on 2021-06-08 (30 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Mic, Front Symptom_Type: None of the above Title: [HP Compaq Pro 6300 MT, Realtek ALC221, Black Mic, Front] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2012 dmi.bios.release: 2.83 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: K01 v02.83 dmi.board.asset.tag: MXL312111Y dmi.board.name: 339A dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: MXL312111Y dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrK01v02.83:bd10/29/2012:br2.83:svnHewlett-Packard:pnHPCompaqPro6300MT:pvr:rvnHewlett-Packard:rn339A:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP Compaq Pro 6300 MT dmi.product.sku: C6Z93UT#ABA dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1935570/+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 1891270] Re: Iranian calendar shows in Azerbaijani language
** Changed in: ubiquity (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1891270 Title: Iranian calendar shows in Azerbaijani language Status in gnome-calendar package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: Fix Committed Bug description: I already installed Ubuntu 20.04.1 LTS and set location on Iran during installation. After finishing installation successfully, I open the calendar by clicking at the top of the screen (where the clock is shown), I see the calendar with Azerbaijani names for month and weekdays. Such as "آقوست" for August and "جومعه آخشامی" for Thursday. But it should show in Iranian names such as "اوت" for August and "پنجشنبه" for Thursday. Description: Ubuntu 20.04.1 LTS Release: 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1891270/+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 1935570] [NEW] [HP Compaq Pro 6300 MT, Realtek ALC221, Black Mic, Front] Recording problem
Public bug reported: Hi, the mic does not work in my Ubuntu OS. Can you guys do something i am very frustrated? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ravisah96 1576 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jul 8 19:57:18 2021 InstallationDate: Installed on 2021-06-08 (30 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Mic, Front Symptom_Type: None of the above Title: [HP Compaq Pro 6300 MT, Realtek ALC221, Black Mic, Front] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2012 dmi.bios.release: 2.83 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: K01 v02.83 dmi.board.asset.tag: MXL312111Y dmi.board.name: 339A dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: MXL312111Y dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrK01v02.83:bd10/29/2012:br2.83:svnHewlett-Packard:pnHPCompaqPro6300MT:pvr:rvnHewlett-Packard:rn339A:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP Compaq Pro 6300 MT dmi.product.sku: C6Z93UT#ABA dmi.sys.vendor: Hewlett-Packard ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1935570 Title: [HP Compaq Pro 6300 MT, Realtek ALC221, Black Mic, Front] Recording problem Status in alsa-driver package in Ubuntu: New Bug description: Hi, the mic does not work in my Ubuntu OS. Can you guys do something i am very frustrated? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ravisah96 1576 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jul 8 19:57:18 2021 InstallationDate: Installed on 2021-06-08 (30 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Mic, Front Symptom_Type: None of the above Title: [HP Compaq Pro 6300 MT, Realtek ALC221, Black Mic, Front] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2012 dmi.bios.release: 2.83 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: K01 v02.83 dmi.board.asset.tag: MXL312111Y dmi.board.name: 339A dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: MXL312111Y dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrK01v02.83:bd10/29/2012:br2.83:svnHewlett-Packard:pnHPCompaqPro6300MT:pvr:rvnHewlett-Packard:rn339A:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP Compaq Pro 6300 MT dmi.product.sku: C6Z93UT#ABA dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1935570/+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 1935074] Re: Plugins cease to work due change in plugin loading and key shortcuts handling
** Attachment removed: "IpAddr.txt" https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1935074/+attachment/5509959/+files/IpAddr.txt ** Attachment removed: "IpRoute.txt" https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1935074/+attachment/5509960/+files/IpRoute.txt -- 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/1935074 Title: Plugins cease to work due change in plugin loading and key shortcuts handling Status in thunderbird package in Ubuntu: New Bug description: One example: Thunderbird cannot anymore handle the "s" key shortcut as expected(handing it over to the Nostalgy++ plugin for doing what it does when receiving this key) and as it worked before the update. The developer write: "Attention for TB 78.11: on TB loading, TB first sets Nostalgy keys, and after that, it sets its own TB keys, overwriting the keysetting of Nostalgy. In earlier versions of TB, TB did wait with loadiing of addons until TB itself was ready. That means after TB start, out of the box, the keys do not work. There is a workaround: open TB addons page (tools-> addons), deactivate Nostalgy++ with the blue slider switch, then reactivate Nostalgy++. Now it sets its key after TB is ready and they stay until the next restart." IMHO It's not good to introduce such a major functionality and API behaviour change with a minor version update labelled as security. (A similar thing happened with enigmail, by the way, which has been made impossible to use and replaced with a broken and incomplete internal implementation). ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: thunderbird 1:78.11.0+build1-0ubuntu0.20.10.2 ProcVersionSignature: Ubuntu 5.8.0-59.66-lowlatency 5.8.18 Uname: Linux 5.8.0-59-lowlatency x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu50.7 Architecture: amd64 BuildID: 20210528153351 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 126: Error executing command as another user: Request dismissed Date: Thu Jul 8 20:47:47 2021 ExecutablePath: /usr/lib/thunderbird/thunderbird Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2020-04-12 (451 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Locales: extensions.sqlite corrupt or missing PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:732 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=78.11.0/20210528153351 (In use) RunningIncompatibleAddons: False SourcePackage: thunderbird Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to groovy on 2020-11-03 (247 days ago) dmi.bios.date: 02/18/2021 dmi.bios.release: 1.38 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET51W (1.38 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QV00CEGE dmi.board.vendor: LENOVO dmi.board.version: SDK0T08861 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrN2OET51W(1.38):bd02/18/2021:br1.38:efr1.23:svnLENOVO:pn20QV00CEGE:pvrThinkPadX1Extreme2nd:rvnLENOVO:rn20QV00CEGE:rvrSDK0T08861WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme 2nd dmi.product.name: 20QV00CEGE dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme 2nd dmi.product.version: ThinkPad X1 Extreme 2nd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1935074/+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 1934286] Re: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases.
Looking at the changes in the libmbim upload for Focal I noticed that mbim-proxy was moved from /usr/lib/libmbim/ to /usr/libexec/. This ends up moving a binary that is not included in $PATH and is installed by default on Ubuntu 20.04 LTS afaict. I don't know how many people would have scripts expecting libmbim to be in /usr/lib/libmbim/ but I don't think changing it out from under them is great. Could we patch the package so it exists in both places? libmbim (1.22.0-2.2) unstable; urgency=medium * Non-maintainer upload. * Bump debhelper to 12, no further changes * Bump Standards-Version to 4.5.0 (no further changes) * Move mbim-proxy to /usr/libexec (Closes: #954145) ... -- 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/1934286 Title: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases. Status in OEM Priority Project: Confirmed Status in libmbim package in Ubuntu: New Status in libqmi package in Ubuntu: New Status in modemmanager package in Ubuntu: New Status in modemmanager source package in Focal: Fix Committed Status in libmbim source package in Hirsute: Fix Committed Status in libqmi source package in Hirsute: Fix Committed Status in modemmanager source package in Hirsute: Fix Committed Bug description: [Impact] Some IOT products use wireless modems which can be working only when recent versions of the ModemManager suite are used. The following 2 modems need the ModemManager suite to be upgraded: * Foxconn SDX55 T99W175 5G sub6 PCIE Modem * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem The main fix requested is to add the FCC unlock mechanism for Foxconn modems. * FCC unlock operation for Foxconn modems https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/534/commits * dms: new 'Foxconn Set FCC authentication' command https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/merge_requests/254/commits The minimum versions of the ModemManager suite required to enable the support for the above 2 mentioned modems have been verified: (LP: #1928665) * ModemManager: 1.16.6 * libmbim: 1.24.8 * libqmi : 1.28.6 The ModemManager suite in the Impish release meets the requirements. [Test Plan] = How to Reproduce the Bug = Execute the following commands to list the modems detected by ModemManager in Hirsute and Focal releases: $ mmcli --list-modems No modems were found = Test Procedure = 1. Install the Ubuntu system on the tested hardware The following images will be used to verify the version of the ModemManager suite: * Impish: https://cdimage.ubuntu.com/daily-live/current/impish-desktop-amd64.iso * Hirsute: https://releases.ubuntu.com/21.04/ubuntu-21.04-desktop-amd64.iso * Focal: https://releases.ubuntu.com/focal/ubuntu-20.04.2.0-desktop-amd64.iso 2. Upgrade the kernel and driver ( for Foxconn and Quectel modem ) The kernel needs to get some patches from 5.13 and includes a back ported Quectel driver to support these 2 modems. We have prepared a kernel packages for testing: https://people.canonical.com/~mschiu77/lp1928665/v2/ 3. Install the ModemManager suite ( for Hirsute and Focal releases ) The ModemManager suite will be installed from the -proposed component: $ sudo apt update $ sudo apt install modemmanager $ sudo apt install libqmi-utils 4. Execute the following commands 4.1 Get the run-time environment $ uname -ar $ lsb_release -a $ mmcli -V $ qmicli -V 4.2 Check the status of the ModemManager service $ sudo systemctl status ModemManager.service 4.3 List the detected modems $ mmcli --list-modems 4.4 Check the modem’s status $ mmcli --modem 0 4.5 Install and execute Lenovo’s FCC unlock app ( for Quectel modem only ) $ sudo snap install --devmode --dangerous dpr-wwan_1.0-wwan- test_amd64.snap 4.6 Enable the detected modem $ sudo mmcli --modem 0 --enable 4.7 Check the modem’s status $ mmcli --modem 0 = Analyze the Tested Result = 1. Check if installed packages are working The result of test procedure 4.1 and 4.2 can be used to make sure the installed packages are working. If the Modemmanager.service is active(running), the packages are working. 2. Check if the supported modem can be detected The result of test procedure 4.3 can be used to see if the modem can be detected by ModemManager or not. The supported modems should be listed. 3. Check if the modem can be enabled If the modem can be enabled, the state of the modem in the test procedure 4.7 will be set to be registered. = Certification Validation = Additionally to the aforementioned test cases, the Certification Team will perform some coverage testing across supported devices to make sure the other modems still work as expected.
[Desktop-packages] [Bug 1930721]
*** Bug 1714199 has been marked as a duplicate of this bug. *** -- 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/1930721 Title: Issue after update Ubuntu on version 21. Firefox often freeze Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Fix Released Bug description: Bug report: I have the same issue on both versions of Firefox. On deb. and snap version I have issue after update Ubuntu on version 21. Firefox often freeze. Can you please help me and repair it? Is possible automatically send diagnostic data for Ubuntu and Firefox developers during freeze? I am sorry, I am not IT expert ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: firefox 89.0+build2-0ubuntu0.21.04.1 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BuildID: 20210527174632 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Jun 3 15:20:50 2021 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sk_SK.UTF-8 SHELL=/bin/bash SourcePackage: firefox UpgradeStatus: Upgraded to hirsute on 2021-05-14 (20 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1930721/+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 1930721]
*** Bug 1715829 has been marked as a duplicate of this bug. *** -- 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/1930721 Title: Issue after update Ubuntu on version 21. Firefox often freeze Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Fix Released Bug description: Bug report: I have the same issue on both versions of Firefox. On deb. and snap version I have issue after update Ubuntu on version 21. Firefox often freeze. Can you please help me and repair it? Is possible automatically send diagnostic data for Ubuntu and Firefox developers during freeze? I am sorry, I am not IT expert ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: firefox 89.0+build2-0ubuntu0.21.04.1 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BuildID: 20210527174632 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Jun 3 15:20:50 2021 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sk_SK.UTF-8 SHELL=/bin/bash SourcePackage: firefox UpgradeStatus: Upgraded to hirsute on 2021-05-14 (20 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1930721/+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 1930721]
*** Bug 1717089 has been marked as a duplicate of this bug. *** -- 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/1930721 Title: Issue after update Ubuntu on version 21. Firefox often freeze Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Fix Released Bug description: Bug report: I have the same issue on both versions of Firefox. On deb. and snap version I have issue after update Ubuntu on version 21. Firefox often freeze. Can you please help me and repair it? Is possible automatically send diagnostic data for Ubuntu and Firefox developers during freeze? I am sorry, I am not IT expert ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: firefox 89.0+build2-0ubuntu0.21.04.1 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BuildID: 20210527174632 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Jun 3 15:20:50 2021 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sk_SK.UTF-8 SHELL=/bin/bash SourcePackage: firefox UpgradeStatus: Upgraded to hirsute on 2021-05-14 (20 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1930721/+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 1930721]
*** Bug 1715934 has been marked as a duplicate of this bug. *** -- 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/1930721 Title: Issue after update Ubuntu on version 21. Firefox often freeze Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Fix Released Bug description: Bug report: I have the same issue on both versions of Firefox. On deb. and snap version I have issue after update Ubuntu on version 21. Firefox often freeze. Can you please help me and repair it? Is possible automatically send diagnostic data for Ubuntu and Firefox developers during freeze? I am sorry, I am not IT expert ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: firefox 89.0+build2-0ubuntu0.21.04.1 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BuildID: 20210527174632 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Jun 3 15:20:50 2021 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sk_SK.UTF-8 SHELL=/bin/bash SourcePackage: firefox UpgradeStatus: Upgraded to hirsute on 2021-05-14 (20 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1930721/+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 1930721]
*** Bug 1712561 has been marked as a duplicate of this bug. *** -- 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/1930721 Title: Issue after update Ubuntu on version 21. Firefox often freeze Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Fix Released Bug description: Bug report: I have the same issue on both versions of Firefox. On deb. and snap version I have issue after update Ubuntu on version 21. Firefox often freeze. Can you please help me and repair it? Is possible automatically send diagnostic data for Ubuntu and Firefox developers during freeze? I am sorry, I am not IT expert ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: firefox 89.0+build2-0ubuntu0.21.04.1 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BuildID: 20210527174632 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Jun 3 15:20:50 2021 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sk_SK.UTF-8 SHELL=/bin/bash SourcePackage: firefox UpgradeStatus: Upgraded to hirsute on 2021-05-14 (20 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1930721/+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 1934286] Re: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases.
Hello Jerry, or anyone else affected, Accepted modemmanager into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/modemmanager/1.16.6-2~20.04 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: modemmanager (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed-focal -- 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/1934286 Title: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases. Status in OEM Priority Project: Confirmed Status in libmbim package in Ubuntu: New Status in libqmi package in Ubuntu: New Status in modemmanager package in Ubuntu: New Status in modemmanager source package in Focal: Fix Committed Status in libmbim source package in Hirsute: Fix Committed Status in libqmi source package in Hirsute: Fix Committed Status in modemmanager source package in Hirsute: Fix Committed Bug description: [Impact] Some IOT products use wireless modems which can be working only when recent versions of the ModemManager suite are used. The following 2 modems need the ModemManager suite to be upgraded: * Foxconn SDX55 T99W175 5G sub6 PCIE Modem * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem The main fix requested is to add the FCC unlock mechanism for Foxconn modems. * FCC unlock operation for Foxconn modems https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/534/commits * dms: new 'Foxconn Set FCC authentication' command https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/merge_requests/254/commits The minimum versions of the ModemManager suite required to enable the support for the above 2 mentioned modems have been verified: (LP: #1928665) * ModemManager: 1.16.6 * libmbim: 1.24.8 * libqmi : 1.28.6 The ModemManager suite in the Impish release meets the requirements. [Test Plan] = How to Reproduce the Bug = Execute the following commands to list the modems detected by ModemManager in Hirsute and Focal releases: $ mmcli --list-modems No modems were found = Test Procedure = 1. Install the Ubuntu system on the tested hardware The following images will be used to verify the version of the ModemManager suite: * Impish: https://cdimage.ubuntu.com/daily-live/current/impish-desktop-amd64.iso * Hirsute: https://releases.ubuntu.com/21.04/ubuntu-21.04-desktop-amd64.iso * Focal: https://releases.ubuntu.com/focal/ubuntu-20.04.2.0-desktop-amd64.iso 2. Upgrade the kernel and driver ( for Foxconn and Quectel modem ) The kernel needs to get some patches from 5.13 and includes a back ported Quectel driver to support these 2 modems. We have prepared a kernel packages for testing: https://people.canonical.com/~mschiu77/lp1928665/v2/ 3. Install the ModemManager suite ( for Hirsute and Focal releases ) The ModemManager suite will be installed from the -proposed component: $ sudo apt update $ sudo apt install modemmanager $ sudo apt install libqmi-utils 4. Execute the following commands 4.1 Get the run-time environment $ uname -ar $ lsb_release -a $ mmcli -V $ qmicli -V 4.2 Check the status of the ModemManager service $ sudo systemctl status ModemManager.service 4.3 List the detected modems $ mmcli --list-modems 4.4 Check the modem’s status $ mmcli --modem 0 4.5 Install and execute Lenovo’s FCC unlock app ( for Quectel modem only ) $ sudo snap install --devmode --dangerous dpr-wwan_1.0-wwan- test_amd64.snap 4.6 Enable the detected modem $ sudo mmcli --modem 0 --enable 4.7 Check the modem’s status $ mmcli --modem 0 = Analyze the Tested Result = 1. Check if installed packages are working The result of test procedure 4.1 and 4.2 can be used to make sure the
[Desktop-packages] [Bug 1931701] Re: autopkgtests failures on armhf of 7.1.4
The problem is actually located in libbootstraplo.so as the trace already suggested. Replacing the library with a "good" compilation confirmed it. # Problematic frame: # C [libbootstraplo.so+0x1c4b8] stoc_impreg::mergeKeys(com::sun::star::uno::Reference const&, com::sun::star::uno::Reference const&, std::vector >&)+0xb https://cgit.freedesktop.org/libreoffice/core/tree/stoc/source/implementationregistration/mergekeys.cxx?h=libreoffice-7-1#n54 ** Attachment added: "hs_err_pid31616.log" https://bugs.launchpad.net/ubuntu/+source/gcc-9/+bug/1931701/+attachment/5509978/+files/hs_err_pid31616.log -- 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/1931701 Title: autopkgtests failures on armhf of 7.1.4 Status in gcc-10 package in Ubuntu: New Status in gcc-9 package in Ubuntu: Incomplete Status in libreoffice package in Ubuntu: New Status in gcc-10 source package in Hirsute: New Status in gcc-9 source package in Hirsute: Incomplete Status in libreoffice source package in Hirsute: New Status in gcc-10 source package in Impish: New Status in gcc-9 source package in Impish: Incomplete Status in libreoffice source package in Impish: New Bug description: The autopkgtests for 7.1.4~rc2-0ubuntu1 on impish/armhf has started to fail reliably. https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/armhf/libr/libreoffice/20210610_121847_0ab56@/log.gz "/usr/lib/libreoffice/program/unopkg" add -f "/tmp/tmp.oOlP0i1pzN/out/sdk/LINUXexample.out/bin/SampleDialog.oxt" # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0xf47474b8, pid=35616, tid=35643 # # JRE version: OpenJDK Runtime Environment (11.0.12+4) (build 11.0.12-ea+4-Ubuntu-0ubuntu2) # Java VM: OpenJDK Server VM (11.0.12-ea+4-Ubuntu-0ubuntu2, mixed mode, g1 gc, linux-) # Problematic frame: # C [libbootstraplo.so+0x1c4b8] stoc_impreg::mergeKeys(com::sun::star::uno::Reference const&, com::sun::star::uno::Reference const&, std::vector >&)+0xb # # Core dump will be written. Default location: Core dumps may be processed with "/usr/share/apport/apport %p %s %c %d %P %E" (or dumping to /usr/lib/libreoffice/sdk/examples/DevelopersGuide/BasicAndDialogs/CreatingDialogs/core.35616) # # An error report file with more information is saved as: # /tmp/hs_err_pid35616.log # # If you would like to submit a bug report, please visit: # https://bugs.launchpad.net/ubuntu/+source/openjdk-lts # ERROR: Exception occurred: Binary URP bridge disposed during call ./binaryurp/source/bridge.cxx:613 ERROR: unopkg failed. make[1]: Leaving directory '/usr/lib/libreoffice/sdk/examples/DevelopersGuide/BasicAndDialogs/CreatingDialogs' make[1]: *** [Makefile:112: /tmp/tmp.oOlP0i1pzN/out/sdk/LINUXexample.out/misc/devguide_basicanddialogs_creatingdialogs_register_component.flag] Error 1 make[1]: Target 'ALL' not remade because of errors. make: *** [/tmp/autopkgtest.U74TIg/build.myd/src/odk/CustomTarget_build-examples_java.mk:62: /tmp/autopkgtest.U74TIg/build.myd/src/workdir/CustomTarget/odk/build-examples_java.done] Error 2 make: Target 'CustomTarget_odk/build-examples_java' not remade because of errors. While a re-run of the test for 7.1.3-0ubuntu1 were successful it suggests it is binary problem. https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/armhf/libr/libreoffice/20210609_234830_1265b@/log.gz liberoffice is built with gcc-9/g++-9 on armhf to avoid https://bugs.launchpad.net/ubuntu/+source/gcc-10/+bug/1891623 A significant difference in the used toolchain points to the update of gcc-9 7.1.3-0ubuntu1 was built with gcc 9.3.0-24ubuntu1 https://launchpadlibrarian.net/537628130/buildlog_ubuntu-impish-armhf.libreoffice_1%3A7.1.3-0ubuntu1_BUILDING.txt.gz 7.1.4~rc2-0ubuntu1 was built with gcc 9.4.0-1ubuntu1 https://launchpadlibrarian.net/542492348/buildlog_ubuntu-impish-armhf.libreoffice_1%3A7.1.4~rc2-0ubuntu1_BUILDING.txt.gz Regarding 21.04/Hirsute 1:7.1.4~rc2-0ubuntu0.21.04.1~lo1 built and successfully ran autopkgtests, see https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1931272 If was using the gcc-9 9.3.0-23ubuntu2 available at the time. The no-change rebuild against 9.4.0-1ubuntu1~21.04 results in the same failure now. https://launchpadlibrarian.net/543392061/buildlog_ubuntu-hirsute-armhf.libreoffice_1%3A7.1.4~rc2-0ubuntu0.21.04.1~lo1_BUILDING.txt.gz https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute-libreoffice-experimental/hirsute/armhf/libr/libreoffice/20210612_113218_f7f69@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-10/+bug/1931701/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to :
[Desktop-packages] [Bug 1934286] Please test proposed package
Hello Jerry, or anyone else affected, Accepted libmbim into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libmbim/1.24.8-1~21.04 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: libqmi (Ubuntu Hirsute) Status: New => Fix Committed -- 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/1934286 Title: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases. Status in OEM Priority Project: Confirmed Status in libmbim package in Ubuntu: New Status in libqmi package in Ubuntu: New Status in modemmanager package in Ubuntu: New Status in libmbim source package in Hirsute: Fix Committed Status in libqmi source package in Hirsute: Fix Committed Status in modemmanager source package in Hirsute: Fix Committed Bug description: [Impact] Some IOT products use wireless modems which can be working only when recent versions of the ModemManager suite are used. The following 2 modems need the ModemManager suite to be upgraded: * Foxconn SDX55 T99W175 5G sub6 PCIE Modem * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem The main fix requested is to add the FCC unlock mechanism for Foxconn modems. * FCC unlock operation for Foxconn modems https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/534/commits * dms: new 'Foxconn Set FCC authentication' command https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/merge_requests/254/commits The minimum versions of the ModemManager suite required to enable the support for the above 2 mentioned modems have been verified: (LP: #1928665) * ModemManager: 1.16.6 * libmbim: 1.24.8 * libqmi : 1.28.6 The ModemManager suite in the Impish release meets the requirements. [Test Plan] = How to Reproduce the Bug = Execute the following commands to list the modems detected by ModemManager in Hirsute and Focal releases: $ mmcli --list-modems No modems were found = Test Procedure = 1. Install the Ubuntu system on the tested hardware The following images will be used to verify the version of the ModemManager suite: * Impish: https://cdimage.ubuntu.com/daily-live/current/impish-desktop-amd64.iso * Hirsute: https://releases.ubuntu.com/21.04/ubuntu-21.04-desktop-amd64.iso * Focal: https://releases.ubuntu.com/focal/ubuntu-20.04.2.0-desktop-amd64.iso 2. Upgrade the kernel and driver ( for Foxconn and Quectel modem ) The kernel needs to get some patches from 5.13 and includes a back ported Quectel driver to support these 2 modems. We have prepared a kernel packages for testing: https://people.canonical.com/~mschiu77/lp1928665/v2/ 3. Install the ModemManager suite ( for Hirsute and Focal releases ) The ModemManager suite will be installed from the -proposed component: $ sudo apt update $ sudo apt install modemmanager $ sudo apt install libqmi-utils 4. Execute the following commands 4.1 Get the run-time environment $ uname -ar $ lsb_release -a $ mmcli -V $ qmicli -V 4.2 Check the status of the ModemManager service $ sudo systemctl status ModemManager.service 4.3 List the detected modems $ mmcli --list-modems 4.4 Check the modem’s status $ mmcli --modem 0 4.5 Install and execute Lenovo’s FCC unlock app ( for Quectel modem only ) $ sudo snap install --devmode --dangerous dpr-wwan_1.0-wwan- test_amd64.snap 4.6 Enable the detected modem $ sudo mmcli --modem 0 --enable 4.7 Check the modem’s status $ mmcli --modem 0 = Analyze the Tested Result = 1. Check if installed packages are working The result of test procedure 4.1 and 4.2 can be used to make sure the installed packages are working. If the Modemmanager.service is active(running), the packages are working. 2.
[Desktop-packages] [Bug 1934286] Please test proposed package
Hello Jerry, or anyone else affected, Accepted libqmi into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libqmi/1.28.6-1~21.04 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/1934286 Title: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases. Status in OEM Priority Project: Confirmed Status in libmbim package in Ubuntu: New Status in libqmi package in Ubuntu: New Status in modemmanager package in Ubuntu: New Status in libmbim source package in Hirsute: Fix Committed Status in libqmi source package in Hirsute: Fix Committed Status in modemmanager source package in Hirsute: Fix Committed Bug description: [Impact] Some IOT products use wireless modems which can be working only when recent versions of the ModemManager suite are used. The following 2 modems need the ModemManager suite to be upgraded: * Foxconn SDX55 T99W175 5G sub6 PCIE Modem * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem The main fix requested is to add the FCC unlock mechanism for Foxconn modems. * FCC unlock operation for Foxconn modems https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/534/commits * dms: new 'Foxconn Set FCC authentication' command https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/merge_requests/254/commits The minimum versions of the ModemManager suite required to enable the support for the above 2 mentioned modems have been verified: (LP: #1928665) * ModemManager: 1.16.6 * libmbim: 1.24.8 * libqmi : 1.28.6 The ModemManager suite in the Impish release meets the requirements. [Test Plan] = How to Reproduce the Bug = Execute the following commands to list the modems detected by ModemManager in Hirsute and Focal releases: $ mmcli --list-modems No modems were found = Test Procedure = 1. Install the Ubuntu system on the tested hardware The following images will be used to verify the version of the ModemManager suite: * Impish: https://cdimage.ubuntu.com/daily-live/current/impish-desktop-amd64.iso * Hirsute: https://releases.ubuntu.com/21.04/ubuntu-21.04-desktop-amd64.iso * Focal: https://releases.ubuntu.com/focal/ubuntu-20.04.2.0-desktop-amd64.iso 2. Upgrade the kernel and driver ( for Foxconn and Quectel modem ) The kernel needs to get some patches from 5.13 and includes a back ported Quectel driver to support these 2 modems. We have prepared a kernel packages for testing: https://people.canonical.com/~mschiu77/lp1928665/v2/ 3. Install the ModemManager suite ( for Hirsute and Focal releases ) The ModemManager suite will be installed from the -proposed component: $ sudo apt update $ sudo apt install modemmanager $ sudo apt install libqmi-utils 4. Execute the following commands 4.1 Get the run-time environment $ uname -ar $ lsb_release -a $ mmcli -V $ qmicli -V 4.2 Check the status of the ModemManager service $ sudo systemctl status ModemManager.service 4.3 List the detected modems $ mmcli --list-modems 4.4 Check the modem’s status $ mmcli --modem 0 4.5 Install and execute Lenovo’s FCC unlock app ( for Quectel modem only ) $ sudo snap install --devmode --dangerous dpr-wwan_1.0-wwan- test_amd64.snap 4.6 Enable the detected modem $ sudo mmcli --modem 0 --enable 4.7 Check the modem’s status $ mmcli --modem 0 = Analyze the Tested Result = 1. Check if installed packages are working The result of test procedure 4.1 and 4.2 can be used to make sure the installed packages are working. If the Modemmanager.service is active(running), the packages are working. 2. Check if the supported modem can be detected The result of test
[Desktop-packages] [Bug 1934286] Re: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases.
Hello Jerry, or anyone else affected, Accepted modemmanager into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/modemmanager/1.16.6-2~21.04 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: modemmanager (Ubuntu Hirsute) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-hirsute ** Changed in: libmbim (Ubuntu Hirsute) Status: New => Fix Committed -- 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/1934286 Title: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases. Status in OEM Priority Project: Confirmed Status in libmbim package in Ubuntu: New Status in libqmi package in Ubuntu: New Status in modemmanager package in Ubuntu: New Status in libmbim source package in Hirsute: Fix Committed Status in libqmi source package in Hirsute: Fix Committed Status in modemmanager source package in Hirsute: Fix Committed Bug description: [Impact] Some IOT products use wireless modems which can be working only when recent versions of the ModemManager suite are used. The following 2 modems need the ModemManager suite to be upgraded: * Foxconn SDX55 T99W175 5G sub6 PCIE Modem * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem The main fix requested is to add the FCC unlock mechanism for Foxconn modems. * FCC unlock operation for Foxconn modems https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/534/commits * dms: new 'Foxconn Set FCC authentication' command https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/merge_requests/254/commits The minimum versions of the ModemManager suite required to enable the support for the above 2 mentioned modems have been verified: (LP: #1928665) * ModemManager: 1.16.6 * libmbim: 1.24.8 * libqmi : 1.28.6 The ModemManager suite in the Impish release meets the requirements. [Test Plan] = How to Reproduce the Bug = Execute the following commands to list the modems detected by ModemManager in Hirsute and Focal releases: $ mmcli --list-modems No modems were found = Test Procedure = 1. Install the Ubuntu system on the tested hardware The following images will be used to verify the version of the ModemManager suite: * Impish: https://cdimage.ubuntu.com/daily-live/current/impish-desktop-amd64.iso * Hirsute: https://releases.ubuntu.com/21.04/ubuntu-21.04-desktop-amd64.iso * Focal: https://releases.ubuntu.com/focal/ubuntu-20.04.2.0-desktop-amd64.iso 2. Upgrade the kernel and driver ( for Foxconn and Quectel modem ) The kernel needs to get some patches from 5.13 and includes a back ported Quectel driver to support these 2 modems. We have prepared a kernel packages for testing: https://people.canonical.com/~mschiu77/lp1928665/v2/ 3. Install the ModemManager suite ( for Hirsute and Focal releases ) The ModemManager suite will be installed from the -proposed component: $ sudo apt update $ sudo apt install modemmanager $ sudo apt install libqmi-utils 4. Execute the following commands 4.1 Get the run-time environment $ uname -ar $ lsb_release -a $ mmcli -V $ qmicli -V 4.2 Check the status of the ModemManager service $ sudo systemctl status ModemManager.service 4.3 List the detected modems $ mmcli --list-modems 4.4 Check the modem’s status $ mmcli --modem 0 4.5 Install and execute Lenovo’s FCC unlock app ( for Quectel modem only ) $ sudo snap install --devmode --dangerous dpr-wwan_1.0-wwan- test_amd64.snap 4.6 Enable the detected modem $ sudo mmcli --modem 0 --enable 4.7 Check the modem’s status $ mmcli --modem 0 = Analyze the Tested Result = 1. Check if installed packages are working The result of test procedure
[Desktop-packages] [Bug 1935074] [NEW] Plugins cease to work due change in plugin loading and key shortcuts handling
Public bug reported: One example: Thunderbird cannot anymore handle the "s" key shortcut as expected(handing it over to the Nostalgy++ plugin for doing what it does when receiving this key) and as it worked before the update. The developer write: "Attention for TB 78.11: on TB loading, TB first sets Nostalgy keys, and after that, it sets its own TB keys, overwriting the keysetting of Nostalgy. In earlier versions of TB, TB did wait with loadiing of addons until TB itself was ready. That means after TB start, out of the box, the keys do not work. There is a workaround: open TB addons page (tools-> addons), deactivate Nostalgy++ with the blue slider switch, then reactivate Nostalgy++. Now it sets its key after TB is ready and they stay until the next restart." IMHO It's not good to introduce such a major functionality and API behaviour change with a minor version update labelled as security. (A similar thing happened with enigmail, by the way, which has been made impossible to use and replaced with a broken and incomplete internal implementation). ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: thunderbird 1:78.11.0+build1-0ubuntu0.20.10.2 ProcVersionSignature: Ubuntu 5.8.0-59.66-lowlatency 5.8.18 Uname: Linux 5.8.0-59-lowlatency x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu50.7 Architecture: amd64 BuildID: 20210528153351 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 126: Error executing command as another user: Request dismissed Date: Thu Jul 8 20:47:47 2021 ExecutablePath: /usr/lib/thunderbird/thunderbird Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2020-04-12 (451 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Locales: extensions.sqlite corrupt or missing PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:732 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=78.11.0/20210528153351 (In use) RunningIncompatibleAddons: False SourcePackage: thunderbird Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to groovy on 2020-11-03 (247 days ago) dmi.bios.date: 02/18/2021 dmi.bios.release: 1.38 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET51W (1.38 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QV00CEGE dmi.board.vendor: LENOVO dmi.board.version: SDK0T08861 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrN2OET51W(1.38):bd02/18/2021:br1.38:efr1.23:svnLENOVO:pn20QV00CEGE:pvrThinkPadX1Extreme2nd:rvnLENOVO:rn20QV00CEGE:rvrSDK0T08861WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme 2nd dmi.product.name: 20QV00CEGE dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme 2nd dmi.product.version: ThinkPad X1 Extreme 2nd dmi.sys.vendor: LENOVO ** Affects: thunderbird (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- 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/1935074 Title: Plugins cease to work due change in plugin loading and key shortcuts handling Status in thunderbird package in Ubuntu: New Bug description: One example: Thunderbird cannot anymore handle the "s" key shortcut as expected(handing it over to the Nostalgy++ plugin for doing what it does when receiving this key) and as it worked before the update. The developer write: "Attention for TB 78.11: on TB loading, TB first sets Nostalgy keys, and after that, it sets its own TB keys, overwriting the keysetting of Nostalgy. In earlier versions of TB, TB did wait with loadiing of addons until TB itself was ready. That means after TB start, out of the box, the keys do not work. There is a workaround: open TB addons page (tools-> addons), deactivate Nostalgy++ with the blue slider switch, then reactivate Nostalgy++. Now it sets its key after TB is ready and they stay until the next restart." IMHO It's not good to introduce such a major functionality and API behaviour change with a minor version update labelled as security. (A similar thing happened with enigmail, by the way, which has been made impossible to use and replaced with a broken and incomplete internal implementation). ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: thunderbird 1:78.11.0+build1-0ubuntu0.20.10.2 ProcVersionSignature: Ubuntu 5.8.0-59.66-lowlatency 5.8.18 Uname: Linux 5.8.0-59-lowlatency x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu50.7 Architecture:
[Desktop-packages] [Bug 1934286] Re: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases.
I'm modifying the description to indicate that the packages should be installed from -proposed on Focal and Hirsute and not from impish (which is what it currently says). ** Description changed: [Impact] Some IOT products use wireless modems which can be working only when recent versions of the ModemManager suite are used. The following 2 modems need the ModemManager suite to be upgraded: * Foxconn SDX55 T99W175 5G sub6 PCIE Modem * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem The main fix requested is to add the FCC unlock mechanism for Foxconn modems. * FCC unlock operation for Foxconn modems https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/534/commits * dms: new 'Foxconn Set FCC authentication' command https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/merge_requests/254/commits The minimum versions of the ModemManager suite required to enable the support for the above 2 mentioned modems have been verified: (LP: #1928665) * ModemManager: 1.16.6 * libmbim: 1.24.8 * libqmi : 1.28.6 The ModemManager suite in the Impish release meets the requirements. [Test Plan] = How to Reproduce the Bug = Execute the following commands to list the modems detected by ModemManager in Hirsute and Focal releases: $ mmcli --list-modems No modems were found = Test Procedure = 1. Install the Ubuntu system on the tested hardware The following images will be used to verify the version of the ModemManager suite: * Impish: https://cdimage.ubuntu.com/daily-live/current/impish-desktop-amd64.iso * Hirsute: https://releases.ubuntu.com/21.04/ubuntu-21.04-desktop-amd64.iso * Focal: https://releases.ubuntu.com/focal/ubuntu-20.04.2.0-desktop-amd64.iso 2. Upgrade the kernel and driver ( for Foxconn and Quectel modem ) The kernel needs to get some patches from 5.13 and includes a back ported Quectel driver to support these 2 modems. We have prepared a kernel packages for testing: https://people.canonical.com/~mschiu77/lp1928665/v2/ 3. Install the ModemManager suite ( for Hirsute and Focal releases ) - The ModemManager suite will be installed from Impish: + The ModemManager suite will be installed from the -proposed component: $ sudo apt update - $ sudo apt install modemmanager/impish - $ sudo apt install libqmi-utils/impish + $ sudo apt install modemmanager + $ sudo apt install libqmi-utils 4. Execute the following commands 4.1 Get the run-time environment $ uname -ar $ lsb_release -a $ mmcli -V $ qmicli -V 4.2 Check the status of the ModemManager service $ sudo systemctl status ModemManager.service 4.3 List the detected modems $ mmcli --list-modems 4.4 Check the modem’s status $ mmcli --modem 0 4.5 Install and execute Lenovo’s FCC unlock app ( for Quectel modem only ) $ sudo snap install --devmode --dangerous dpr-wwan_1.0-wwan- test_amd64.snap 4.6 Enable the detected modem $ sudo mmcli --modem 0 --enable 4.7 Check the modem’s status $ mmcli --modem 0 = Analyze the Tested Result = 1. Check if installed packages are working The result of test procedure 4.1 and 4.2 can be used to make sure the installed packages are working. If the Modemmanager.service is active(running), the packages are working. 2. Check if the supported modem can be detected The result of test procedure 4.3 can be used to see if the modem can be detected by ModemManager or not. The supported modems should be listed. 3. Check if the modem can be enabled If the modem can be enabled, the state of the modem in the test procedure 4.7 will be set to be registered. - = Certification Validation = Additionally to the aforementioned test cases, the Certification Team will perform some coverage testing across supported devices to make sure the other modems still work as expected. [Where problems could occur] There is a risk that modems supported in the old versions of ModemManager suite may not be supported in the newer versions. [Other Info] We need to upgrade to these 3 packages (in Impish) at the same time: * ModemManager: 1.16.6 * libmbim: 1.24.8 * libqmi : 1.28.6 To support the mentioned 2 modems, the system needs to use kernels which include specific patches and kernel config options . For ex., there is a patched 5.11 kernel which is working for: https://bugs.launchpad.net/austin/+bug/1928665/comments/7 -- 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/1934286 Title: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases. Status in OEM Priority Project: Confirmed Status in libmbim package in Ubuntu: New Status in libqmi package in Ubuntu: New Status in
[Desktop-packages] [Bug 1935070] [NEW] Traceback during 'ubuntu-drivers list'
Public bug reported: ubuntu@doubletusk:~$ sudo ubuntu-drivers list ERROR:root:could not open aplay -l Traceback (most recent call last): File "/usr/share/ubuntu-drivers-common/detect/sl-modem.py", line 35, in detect aplay = subprocess.Popen( File "/usr/lib/python3.8/subprocess.py", line 858, in __init__ self._execute_child(args, executable, preexec_fn, close_fds, File "/usr/lib/python3.8/subprocess.py", line 1704, in _execute_child raise child_exception_type(errno_num, err_msg, err_filename) FileNotFoundError: [Errno 2] No such file or directory: 'aplay' nvidia-driver-418-server, (kernel modules provided by nvidia-dkms-418-server) nvidia-driver-470, (kernel modules provided by nvidia-dkms-470) nvidia-driver-460-server, (kernel modules provided by nvidia-dkms-460-server) nvidia-driver-465, (kernel modules provided by nvidia-dkms-465) nvidia-driver-450-server, (kernel modules provided by nvidia-dkms-450-server) nvidia-driver-460, (kernel modules provided by nvidia-dkms-460) ubuntu@doubletusk:~$ apt-cache policy ubuntu-drivers-common ubuntu-drivers-common: Installed: 1:0.9.0~0.20.04.1 Candidate: 1:0.9.0~0.20.04.1 Version table: *** 1:0.9.0~0.20.04.1 500 500 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1:0.8.6.5~0.20.04.1 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 1:0.8.1 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages ubuntu@doubletusk:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS Release:20.04 Codename: focal ** Affects: ubuntu-drivers-common (Ubuntu) Importance: Undecided Status: New -- 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/1935070 Title: Traceback during 'ubuntu-drivers list' Status in ubuntu-drivers-common package in Ubuntu: New Bug description: ubuntu@doubletusk:~$ sudo ubuntu-drivers list ERROR:root:could not open aplay -l Traceback (most recent call last): File "/usr/share/ubuntu-drivers-common/detect/sl-modem.py", line 35, in detect aplay = subprocess.Popen( File "/usr/lib/python3.8/subprocess.py", line 858, in __init__ self._execute_child(args, executable, preexec_fn, close_fds, File "/usr/lib/python3.8/subprocess.py", line 1704, in _execute_child raise child_exception_type(errno_num, err_msg, err_filename) FileNotFoundError: [Errno 2] No such file or directory: 'aplay' nvidia-driver-418-server, (kernel modules provided by nvidia-dkms-418-server) nvidia-driver-470, (kernel modules provided by nvidia-dkms-470) nvidia-driver-460-server, (kernel modules provided by nvidia-dkms-460-server) nvidia-driver-465, (kernel modules provided by nvidia-dkms-465) nvidia-driver-450-server, (kernel modules provided by nvidia-dkms-450-server) nvidia-driver-460, (kernel modules provided by nvidia-dkms-460) ubuntu@doubletusk:~$ apt-cache policy ubuntu-drivers-common ubuntu-drivers-common: Installed: 1:0.9.0~0.20.04.1 Candidate: 1:0.9.0~0.20.04.1 Version table: *** 1:0.9.0~0.20.04.1 500 500 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1:0.8.6.5~0.20.04.1 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 1:0.8.1 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages ubuntu@doubletusk:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS Release:20.04 Codename: focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1935070/+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 1931958] Re: 0~git20200629+e7aa92a-8 is FTFBS
** Merge proposal linked: https://code.launchpad.net/~sergiodj/ubuntu/+source/gstreamer1.0/+git/gstreamer1.0/+merge/405405 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1931958 Title: 0~git20200629+e7aa92a-8 is FTFBS Status in gstreamer1.0 package in Ubuntu: New Status in libcamera package in Ubuntu: New Bug description: Fails to build due to gstreamer using deprecated g_memdup: /usr/include/gstreamer-1.0/gst/base/gstbytereader.h: In function ‘guint8* gst_byte_reader_dup_data_unchecked(GstByteReader*, guint)’: /usr/include/gstreamer-1.0/gst/base/gstbytereader.h:365:41: error: ‘void* g_memdup(gconstpointer, guint)’ is deprecated: Use 'g_memdup2' instead [-Werror=deprecated-declarations] 365 | return (guint8 *) g_memdup (data, size); | ^ In file included from /usr/include/glib-2.0/glib.h:82, from /usr/include/gstreamer-1.0/gst/gst.h:27, from ../src/gstreamer/gstlibcamerasrc.h:12, from ../src/gstreamer/gstlibcamerasrc.cpp:34: /usr/include/glib-2.0/glib/gstrfuncs.h:257:23: note: declared here 257 | gpointer g_memdup (gconstpointer mem, Fixed in gstreamer upstream: https://gitlab.freedesktop.org/gstreamer/gstreamer/-/commit/b16e96dd878e0c5e7baeb8fad62ca43de1f66982 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1931958/+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 1926843] Re: online accounts integration with fb isn't working
https://www.asus.com/Motherboards- Components/Motherboards/Accessories/TPM-M-R2-0/ can you confirm its should works with gnome-online-accounts this TPM_M modules or other? so user id be stored on motherboard? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1926843 Title: online accounts integration with fb isn't working Status in gnome-online-accounts package in Ubuntu: Fix Released Status in gnome-online-accounts source package in Focal: Fix Released Status in gnome-online-accounts source package in Hirsute: Fix Released Bug description: * Impact The online accounts setting are proposing a facebook item which isn't working * Test case Go to settings -> online account, browse the accounts option proposed, facebook shouldn't be in the list since it doesn't work. * Regression potential The change is to disable the facebook provider using the upstream provided build option. Check that facebook isn't listed anymore but that the other providers still are. Since it's a build option change it could fail to build so check for that as well on launchpad. Since the facebook service currently doesn't consider gnome-online- accounts as a valid client there should be no user with that provider configured. Even if there were since the service isn't working they would see a functional regression. --- Hi i tryed to use gnome-control-center online-accounts to make easy like windows 10 to login to email or add other login so its more easy with ID to use pincode or other ID fingerprint and other. But its look its much issue compared with windows 10 with thunderbird, firefox, and other program. Worst is facebook only little windows with issue with login? ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-online-accounts 3.38.1-1ubuntu1 Uname: Linux 5.12.0-051200-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat May 1 19:38:03 2021 InstallationDate: Installed on 2019-05-07 (725 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gnome-online-accounts UpgradeStatus: Upgraded to hirsute on 2021-04-06 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1926843/+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 1935063] [NEW] gnome-initial-setup: cannot build on RISC-V
Public bug reported: version: 40.2-1ubuntu1 platform: RISC-V gnome-initial-setup cannot be built on RISC-V due to a dependency on libsysmetrics-dev. libsysmetrics-dev is built from source package ubuntu-report. Building of ubuntu-report fails because the Go language does not support -buildmode=c-shared on RISC-V yet. The dependency is due to our patch 0001-Add-Ubuntu-mode-with-special- pages.patch. The report implemented in gis-ubuntu-report-page.c is used to send system info to Canonical. Feasible solutions would be * remove the report completely * disable it for RISC-V Best regards Heinrich ** Affects: gnome-initial-setup (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-initial-setup in Ubuntu. https://bugs.launchpad.net/bugs/1935063 Title: gnome-initial-setup: cannot build on RISC-V Status in gnome-initial-setup package in Ubuntu: New Bug description: version: 40.2-1ubuntu1 platform: RISC-V gnome-initial-setup cannot be built on RISC-V due to a dependency on libsysmetrics-dev. libsysmetrics-dev is built from source package ubuntu-report. Building of ubuntu-report fails because the Go language does not support -buildmode=c-shared on RISC-V yet. The dependency is due to our patch 0001-Add-Ubuntu-mode-with-special- pages.patch. The report implemented in gis-ubuntu-report-page.c is used to send system info to Canonical. Feasible solutions would be * remove the report completely * disable it for RISC-V Best regards Heinrich To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1935063/+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 1934286] Re: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases.
Ok, thanks for the info! I uploaded both libqmi and libmbim to both hirsute and focal queues. Now it needs someone to review the SRUs and accept them (I can poke around). I'll also modify the description to mention the additional testing that the Certification Team will perform on the packages as it will really make the SRU look safer. The more tests performed, the better. Removing ubuntu-sponsors. ** Description changed: [Impact] Some IOT products use wireless modems which can be working only when recent versions of the ModemManager suite are used. The following 2 modems need the ModemManager suite to be upgraded: * Foxconn SDX55 T99W175 5G sub6 PCIE Modem * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem The main fix requested is to add the FCC unlock mechanism for Foxconn modems. * FCC unlock operation for Foxconn modems https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/534/commits * dms: new 'Foxconn Set FCC authentication' command https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/merge_requests/254/commits The minimum versions of the ModemManager suite required to enable the support for the above 2 mentioned modems have been verified: (LP: #1928665) * ModemManager: 1.16.6 * libmbim: 1.24.8 * libqmi : 1.28.6 The ModemManager suite in the Impish release meets the requirements. [Test Plan] = How to Reproduce the Bug = Execute the following commands to list the modems detected by ModemManager in Hirsute and Focal releases: $ mmcli --list-modems No modems were found = Test Procedure = 1. Install the Ubuntu system on the tested hardware The following images will be used to verify the version of the ModemManager suite: * Impish: https://cdimage.ubuntu.com/daily-live/current/impish-desktop-amd64.iso * Hirsute: https://releases.ubuntu.com/21.04/ubuntu-21.04-desktop-amd64.iso * Focal: https://releases.ubuntu.com/focal/ubuntu-20.04.2.0-desktop-amd64.iso 2. Upgrade the kernel and driver ( for Foxconn and Quectel modem ) The kernel needs to get some patches from 5.13 and includes a back ported Quectel driver to support these 2 modems. We have prepared a kernel packages for testing: https://people.canonical.com/~mschiu77/lp1928665/v2/ 3. Install the ModemManager suite ( for Hirsute and Focal releases ) The ModemManager suite will be installed from Impish: $ sudo apt update $ sudo apt install modemmanager/impish $ sudo apt install libqmi-utils/impish 4. Execute the following commands 4.1 Get the run-time environment $ uname -ar $ lsb_release -a $ mmcli -V $ qmicli -V 4.2 Check the status of the ModemManager service $ sudo systemctl status ModemManager.service 4.3 List the detected modems $ mmcli --list-modems 4.4 Check the modem’s status $ mmcli --modem 0 4.5 Install and execute Lenovo’s FCC unlock app ( for Quectel modem only ) $ sudo snap install --devmode --dangerous dpr-wwan_1.0-wwan- test_amd64.snap 4.6 Enable the detected modem $ sudo mmcli --modem 0 --enable 4.7 Check the modem’s status $ mmcli --modem 0 = Analyze the Tested Result = 1. Check if installed packages are working The result of test procedure 4.1 and 4.2 can be used to make sure the installed packages are working. If the Modemmanager.service is active(running), the packages are working. 2. Check if the supported modem can be detected The result of test procedure 4.3 can be used to see if the modem can be detected by ModemManager or not. The supported modems should be listed. 3. Check if the modem can be enabled If the modem can be enabled, the state of the modem in the test procedure 4.7 will be set to be registered. + + = Certification Validation = + + Additionally to the aforementioned test cases, the Certification Team + will perform some coverage testing across supported devices to make sure + the other modems still work as expected. + [Where problems could occur] There is a risk that modems supported in the old versions of ModemManager suite may not be supported in the newer versions. [Other Info] We need to upgrade to these 3 packages (in Impish) at the same time: * ModemManager: 1.16.6 * libmbim: 1.24.8 * libqmi : 1.28.6 To support the mentioned 2 modems, the system needs to use kernels which include specific patches and kernel config options . For ex., there is a patched 5.11 kernel which is working for: https://bugs.launchpad.net/austin/+bug/1928665/comments/7 -- 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/1934286 Title: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases. Status in OEM Priority Project: Confirmed Status in
[Desktop-packages] [Bug 1934286] Re: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases.
** Also affects: libqmi (Ubuntu) Importance: Undecided Status: New ** Also affects: libmbim (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libqmi in Ubuntu. https://bugs.launchpad.net/bugs/1934286 Title: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases. Status in OEM Priority Project: Confirmed Status in libmbim package in Ubuntu: New Status in libqmi package in Ubuntu: New Status in modemmanager package in Ubuntu: New Bug description: [Impact] Some IOT products use wireless modems which can be working only when recent versions of the ModemManager suite are used. The following 2 modems need the ModemManager suite to be upgraded: * Foxconn SDX55 T99W175 5G sub6 PCIE Modem * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem The main fix requested is to add the FCC unlock mechanism for Foxconn modems. * FCC unlock operation for Foxconn modems https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/534/commits * dms: new 'Foxconn Set FCC authentication' command https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/merge_requests/254/commits The minimum versions of the ModemManager suite required to enable the support for the above 2 mentioned modems have been verified: (LP: #1928665) * ModemManager: 1.16.6 * libmbim: 1.24.8 * libqmi : 1.28.6 The ModemManager suite in the Impish release meets the requirements. [Test Plan] = How to Reproduce the Bug = Execute the following commands to list the modems detected by ModemManager in Hirsute and Focal releases: $ mmcli --list-modems No modems were found = Test Procedure = 1. Install the Ubuntu system on the tested hardware The following images will be used to verify the version of the ModemManager suite: * Impish: https://cdimage.ubuntu.com/daily-live/current/impish-desktop-amd64.iso * Hirsute: https://releases.ubuntu.com/21.04/ubuntu-21.04-desktop-amd64.iso * Focal: https://releases.ubuntu.com/focal/ubuntu-20.04.2.0-desktop-amd64.iso 2. Upgrade the kernel and driver ( for Foxconn and Quectel modem ) The kernel needs to get some patches from 5.13 and includes a back ported Quectel driver to support these 2 modems. We have prepared a kernel packages for testing: https://people.canonical.com/~mschiu77/lp1928665/v2/ 3. Install the ModemManager suite ( for Hirsute and Focal releases ) The ModemManager suite will be installed from Impish: $ sudo apt update $ sudo apt install modemmanager/impish $ sudo apt install libqmi-utils/impish 4. Execute the following commands 4.1 Get the run-time environment $ uname -ar $ lsb_release -a $ mmcli -V $ qmicli -V 4.2 Check the status of the ModemManager service $ sudo systemctl status ModemManager.service 4.3 List the detected modems $ mmcli --list-modems 4.4 Check the modem’s status $ mmcli --modem 0 4.5 Install and execute Lenovo’s FCC unlock app ( for Quectel modem only ) $ sudo snap install --devmode --dangerous dpr-wwan_1.0-wwan- test_amd64.snap 4.6 Enable the detected modem $ sudo mmcli --modem 0 --enable 4.7 Check the modem’s status $ mmcli --modem 0 = Analyze the Tested Result = 1. Check if installed packages are working The result of test procedure 4.1 and 4.2 can be used to make sure the installed packages are working. If the Modemmanager.service is active(running), the packages are working. 2. Check if the supported modem can be detected The result of test procedure 4.3 can be used to see if the modem can be detected by ModemManager or not. The supported modems should be listed. 3. Check if the modem can be enabled If the modem can be enabled, the state of the modem in the test procedure 4.7 will be set to be registered. [Where problems could occur] There is a risk that modems supported in the old versions of ModemManager suite may not be supported in the newer versions. [Other Info] We need to upgrade to these 3 packages (in Impish) at the same time: * ModemManager: 1.16.6 * libmbim: 1.24.8 * libqmi : 1.28.6 To support the mentioned 2 modems, the system needs to use kernels which include specific patches and kernel config options . For ex., there is a patched 5.11 kernel which is working for: https://bugs.launchpad.net/austin/+bug/1928665/comments/7 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1934286/+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 1244090] Re: Pressing any global keyboard shortcut causes temporary loss of focus
** Changed in: mutter Status: Confirmed => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1244090 Title: Pressing any global keyboard shortcut causes temporary loss of focus Status in Mutter: Expired Status in compiz package in Ubuntu: Confirmed Status in gnome-settings-daemon package in Ubuntu: Triaged Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in unity-settings-daemon package in Ubuntu: Triaged Status in gnome-settings-daemon package in ALT Linux: Unknown Status in gnome-shell package in Fedora: Confirmed Status in gnome package in openSUSE: Unknown Bug description: When pressing any global keyboard shourtcut (configurable via System settings -> Keyboard -> Shortcuts; i.e. for switching keyboard layout, volume up/down), focus temporary switches from active text input to something else, then restores back shortly. Maybe even active window loses focus, but window frame does not shows this (window header remains to look active). For example: when I press ctrl+shift here to switch keyboard layout, when writing this description, yellow frame disappears from text input box, text caret disappears too; they appear again when releasing ctrl+shift. The same occurs in all other programs, i.e. terminal. It causes serious annoyance, for example in Twitter when losing focus in Reply text box, reply rolls up and I have to click it again with mouse and set caret to correct place each time I switch keyboard layouts. Other key combinations, not only ctrl+shift, also cause this. It is especially annoying when using keyboard layout switch shortcut handled by the same subsystem (media-keys plugin): case SWITCH_INPUT_SOURCE_KEY: case SWITCH_INPUT_SOURCE_BACKWARD_KEY: do_switch_input_source_action (manager, type); break; (Original gnome-settings-daemon, from which unity-settings-daemon was forked, does not use media-keys plugin to switch keyboard layout). -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-session 3.9.90-0ubuntu3 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Thu Oct 24 11:42:19 2013 InstallationDate: Installed on 2013-10-23 (0 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True PackageArchitecture: all SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1244090/+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 1244090]
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org which have not seen updates for a longer time (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version, then please follow https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines and create a new ticket at https://gitlab.gnome.org/GNOME/mutter/-/issues/ Thank you for your understanding and your help. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1244090 Title: Pressing any global keyboard shortcut causes temporary loss of focus Status in Mutter: Expired Status in compiz package in Ubuntu: Confirmed Status in gnome-settings-daemon package in Ubuntu: Triaged Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in unity-settings-daemon package in Ubuntu: Triaged Status in gnome-settings-daemon package in ALT Linux: Unknown Status in gnome-shell package in Fedora: Confirmed Status in gnome package in openSUSE: Unknown Bug description: When pressing any global keyboard shourtcut (configurable via System settings -> Keyboard -> Shortcuts; i.e. for switching keyboard layout, volume up/down), focus temporary switches from active text input to something else, then restores back shortly. Maybe even active window loses focus, but window frame does not shows this (window header remains to look active). For example: when I press ctrl+shift here to switch keyboard layout, when writing this description, yellow frame disappears from text input box, text caret disappears too; they appear again when releasing ctrl+shift. The same occurs in all other programs, i.e. terminal. It causes serious annoyance, for example in Twitter when losing focus in Reply text box, reply rolls up and I have to click it again with mouse and set caret to correct place each time I switch keyboard layouts. Other key combinations, not only ctrl+shift, also cause this. It is especially annoying when using keyboard layout switch shortcut handled by the same subsystem (media-keys plugin): case SWITCH_INPUT_SOURCE_KEY: case SWITCH_INPUT_SOURCE_BACKWARD_KEY: do_switch_input_source_action (manager, type); break; (Original gnome-settings-daemon, from which unity-settings-daemon was forked, does not use media-keys plugin to switch keyboard layout). -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-session 3.9.90-0ubuntu3 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Thu Oct 24 11:42:19 2013 InstallationDate: Installed on 2013-10-23 (0 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True PackageArchitecture: all SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1244090/+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 1935033] [NEW] Long height characters truncated in the bottom of the terminal if font size is 12
Public bug reported:
I have noticed that the last line in the terminal that appears to have
the long height characters like the "|", "[", and "}" have been
truncated by a pixel in the bottom. For example, if I got a bash prompt
in the bottom of the terminal, and I've written such characters, I'll
notice that the above problem occurs.
However, this only happens if the font was set to Ubuntu Mono and the
size was set to 12px. Anything other than that, and the last line looks
normal.
Steps to reproduce:
1. Open the terminal
2. Continuously press Enter until you reach the last line
3. Write the characters that have long height, like "{", "}", and so on.
What is expected to happen:
I expect that these characters appear normal
What actually happened:
These characters appear truncated in the bottom by a pixel or two
lsb_release -rd:
Description:Ubuntu Impish Indri (development branch)
Release:21.10
apt-cache policy gnome-terminal:
gnome-terminal:
Installed: 3.38.1-1ubuntu1
Candidate: 3.38.1-1ubuntu1
Version table:
*** 3.38.1-1ubuntu1 500
500 http://sy.archive.ubuntu.com/ubuntu impish/main amd64 Packages
100 /var/lib/dpkg/status
ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: gnome-terminal 3.38.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21
Uname: Linux 5.11.0-20-generic x86_64
ApportVersion: 2.20.11-0ubuntu67
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Thu Jul 8 14:44:01 2021
InstallationDate: Installed on 2021-02-02 (155 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210123)
SourcePackage: gnome-terminal
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: gnome-terminal (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug impish wayland-session
** Attachment added: "Screenshot from 2021-07-08 14-58-40.png"
https://bugs.launchpad.net/bugs/1935033/+attachment/5509898/+files/Screenshot%20from%202021-07-08%2014-58-40.png
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1935033
Title:
Long height characters truncated in the bottom of the terminal if font
size is 12
Status in gnome-terminal package in Ubuntu:
New
Bug description:
I have noticed that the last line in the terminal that appears to have
the long height characters like the "|", "[", and "}" have been
truncated by a pixel in the bottom. For example, if I got a bash
prompt in the bottom of the terminal, and I've written such
characters, I'll notice that the above problem occurs.
However, this only happens if the font was set to Ubuntu Mono and the
size was set to 12px. Anything other than that, and the last line
looks normal.
Steps to reproduce:
1. Open the terminal
2. Continuously press Enter until you reach the last line
3. Write the characters that have long height, like "{", "}", and so on.
What is expected to happen:
I expect that these characters appear normal
What actually happened:
These characters appear truncated in the bottom by a pixel or two
lsb_release -rd:
Description: Ubuntu Impish Indri (development branch)
Release: 21.10
apt-cache policy gnome-terminal:
gnome-terminal:
Installed: 3.38.1-1ubuntu1
Candidate: 3.38.1-1ubuntu1
Version table:
*** 3.38.1-1ubuntu1 500
500 http://sy.archive.ubuntu.com/ubuntu impish/main amd64 Packages
100 /var/lib/dpkg/status
ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: gnome-terminal 3.38.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21
Uname: Linux 5.11.0-20-generic x86_64
ApportVersion: 2.20.11-0ubuntu67
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Thu Jul 8 14:44:01 2021
InstallationDate: Installed on 2021-02-02 (155 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210123)
SourcePackage: gnome-terminal
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1935033/+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 1481835]
(In reply to Bayram Çiçek from comment #47) > > I don't understand why images handled different in Writer and > Draw/Calc/Impress. > > IMHO, should we get rid of Writer-images and convert them into drawing > objects as like in the Draw? Otherwise, from my point of view, it seems a > bit complicated to group raster images and raster What do you think? >From ODF file format there is no difference. So from my point of view we should get rid of Writer-images. But that is a long way. You see the differences, if you look at the supported services. You can use the "Development Tools" to easily get an overview. >From user point of view the main differences are: Writer-images allow a wrap, which is determined by a user defined polygon. You get the wrap polygon via context menu -> Wrap > Edit Contour. Writer-images have the feature "Image Map". You get the "Image Map" via menu Tools > Image Map. Draw-images have no UI in Writer to crop them (bug 107843). So to get rid of Writer-images it would be necessary to implement the services, which are provided by Writer-images for Draw-images too. Converting a Writer-image to a Draw-image for grouping will work. But I would never do this silently, because it means, that the features of the image will be changed. If an operation in Draw can only be done with a special kind of object, the user gets a warning, that the object will be converted, and an option to agree or cancel. Try command 'Distort' on a star-shape for example. -- 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/1481835 Title: [UPSTREAM] Unable to group raster image(s) with drawing object(s) Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: In Progress Bug description: Steps to reproduce: 1. Create new document in LibreOffice Writer 2. put rester images into document and put on images some drawing objects (arrows, other shapes), text. 3. try to group images with drawing objects. Expected behaviour: User can select and group image(s) with drawing object(s) Actual behaviour: User can not select and group image(s) with drawing object(s) ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libreoffice 1:3.5.7-0ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-61.100~precise1-generic 3.13.11-ckt22 Uname: Linux 3.13.0-61-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.9 Architecture: amd64 Date: Wed Aug 5 18:59:59 2015 InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 (20140204) MarkForUpload: True SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1481835/+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 1934854] Re: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1
>From DpkgTerminalLog.txt: ==> Installing the chromium snap erreur : system does not fully support snapd: cannot mount squashfs image using "squashfs": mount: /tmp/sanity-mountpoint-544566046: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error. -- 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/1934854 Title: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 Status in chromium-browser package in Ubuntu: New Bug description: I think the source of bug is SnapD. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: chromium-browser (not installed) ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 AptOrdering: snapd:amd64: Install snapd:amd64: Configure chromium-browser:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Jul 3 06:48:05 2021 ErrorMessage: new chromium-browser package pre-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-06-09 (28 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: chromium-browser Title: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1934854/+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 1934286] Re: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases.
Yes: * there are no series-specific changes. (just one line in the change log from Impish) * those are essentially straight backports to hirsute and focal I've corrected the libmbim version to be the same as in Impish. Thanks a lot! -- 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/1934286 Title: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases. Status in OEM Priority Project: Confirmed Status in modemmanager package in Ubuntu: New Bug description: [Impact] Some IOT products use wireless modems which can be working only when recent versions of the ModemManager suite are used. The following 2 modems need the ModemManager suite to be upgraded: * Foxconn SDX55 T99W175 5G sub6 PCIE Modem * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem The main fix requested is to add the FCC unlock mechanism for Foxconn modems. * FCC unlock operation for Foxconn modems https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/534/commits * dms: new 'Foxconn Set FCC authentication' command https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/merge_requests/254/commits The minimum versions of the ModemManager suite required to enable the support for the above 2 mentioned modems have been verified: (LP: #1928665) * ModemManager: 1.16.6 * libmbim: 1.24.8 * libqmi : 1.28.6 The ModemManager suite in the Impish release meets the requirements. [Test Plan] = How to Reproduce the Bug = Execute the following commands to list the modems detected by ModemManager in Hirsute and Focal releases: $ mmcli --list-modems No modems were found = Test Procedure = 1. Install the Ubuntu system on the tested hardware The following images will be used to verify the version of the ModemManager suite: * Impish: https://cdimage.ubuntu.com/daily-live/current/impish-desktop-amd64.iso * Hirsute: https://releases.ubuntu.com/21.04/ubuntu-21.04-desktop-amd64.iso * Focal: https://releases.ubuntu.com/focal/ubuntu-20.04.2.0-desktop-amd64.iso 2. Upgrade the kernel and driver ( for Foxconn and Quectel modem ) The kernel needs to get some patches from 5.13 and includes a back ported Quectel driver to support these 2 modems. We have prepared a kernel packages for testing: https://people.canonical.com/~mschiu77/lp1928665/v2/ 3. Install the ModemManager suite ( for Hirsute and Focal releases ) The ModemManager suite will be installed from Impish: $ sudo apt update $ sudo apt install modemmanager/impish $ sudo apt install libqmi-utils/impish 4. Execute the following commands 4.1 Get the run-time environment $ uname -ar $ lsb_release -a $ mmcli -V $ qmicli -V 4.2 Check the status of the ModemManager service $ sudo systemctl status ModemManager.service 4.3 List the detected modems $ mmcli --list-modems 4.4 Check the modem’s status $ mmcli --modem 0 4.5 Install and execute Lenovo’s FCC unlock app ( for Quectel modem only ) $ sudo snap install --devmode --dangerous dpr-wwan_1.0-wwan- test_amd64.snap 4.6 Enable the detected modem $ sudo mmcli --modem 0 --enable 4.7 Check the modem’s status $ mmcli --modem 0 = Analyze the Tested Result = 1. Check if installed packages are working The result of test procedure 4.1 and 4.2 can be used to make sure the installed packages are working. If the Modemmanager.service is active(running), the packages are working. 2. Check if the supported modem can be detected The result of test procedure 4.3 can be used to see if the modem can be detected by ModemManager or not. The supported modems should be listed. 3. Check if the modem can be enabled If the modem can be enabled, the state of the modem in the test procedure 4.7 will be set to be registered. [Where problems could occur] There is a risk that modems supported in the old versions of ModemManager suite may not be supported in the newer versions. [Other Info] We need to upgrade to these 3 packages (in Impish) at the same time: * ModemManager: 1.16.6 * libmbim: 1.24.8 * libqmi : 1.28.6 To support the mentioned 2 modems, the system needs to use kernels which include specific patches and kernel config options . For ex., there is a patched 5.11 kernel which is working for: https://bugs.launchpad.net/austin/+bug/1928665/comments/7 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1934286/+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 1934286] Re: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases.
** Description changed: [Impact] Some IOT products use wireless modems which can be working only when recent versions of the ModemManager suite are used. The following 2 modems need the ModemManager suite to be upgraded: * Foxconn SDX55 T99W175 5G sub6 PCIE Modem * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem The main fix requested is to add the FCC unlock mechanism for Foxconn modems. * FCC unlock operation for Foxconn modems https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/534/commits * dms: new 'Foxconn Set FCC authentication' command https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/merge_requests/254/commits The minimum versions of the ModemManager suite required to enable the support for the above 2 mentioned modems have been verified: (LP: #1928665) * ModemManager: 1.16.6 - * libmbim: 1.24.6 + * libmbim: 1.24.8 * libqmi : 1.28.6 The ModemManager suite in the Impish release meets the requirements. [Test Plan] = How to Reproduce the Bug = Execute the following commands to list the modems detected by ModemManager in Hirsute and Focal releases: $ mmcli --list-modems No modems were found = Test Procedure = 1. Install the Ubuntu system on the tested hardware The following images will be used to verify the version of the ModemManager suite: * Impish: https://cdimage.ubuntu.com/daily-live/current/impish-desktop-amd64.iso * Hirsute: https://releases.ubuntu.com/21.04/ubuntu-21.04-desktop-amd64.iso * Focal: https://releases.ubuntu.com/focal/ubuntu-20.04.2.0-desktop-amd64.iso 2. Upgrade the kernel and driver ( for Foxconn and Quectel modem ) The kernel needs to get some patches from 5.13 and includes a back ported Quectel driver to support these 2 modems. We have prepared a kernel packages for testing: https://people.canonical.com/~mschiu77/lp1928665/v2/ 3. Install the ModemManager suite ( for Hirsute and Focal releases ) The ModemManager suite will be installed from Impish: $ sudo apt update $ sudo apt install modemmanager/impish $ sudo apt install libqmi-utils/impish 4. Execute the following commands 4.1 Get the run-time environment $ uname -ar $ lsb_release -a $ mmcli -V $ qmicli -V 4.2 Check the status of the ModemManager service $ sudo systemctl status ModemManager.service 4.3 List the detected modems $ mmcli --list-modems 4.4 Check the modem’s status $ mmcli --modem 0 4.5 Install and execute Lenovo’s FCC unlock app ( for Quectel modem only ) $ sudo snap install --devmode --dangerous dpr-wwan_1.0-wwan- test_amd64.snap 4.6 Enable the detected modem $ sudo mmcli --modem 0 --enable 4.7 Check the modem’s status $ mmcli --modem 0 = Analyze the Tested Result = 1. Check if installed packages are working The result of test procedure 4.1 and 4.2 can be used to make sure the installed packages are working. If the Modemmanager.service is active(running), the packages are working. 2. Check if the supported modem can be detected The result of test procedure 4.3 can be used to see if the modem can be detected by ModemManager or not. The supported modems should be listed. 3. Check if the modem can be enabled If the modem can be enabled, the state of the modem in the test procedure 4.7 will be set to be registered. [Where problems could occur] There is a risk that modems supported in the old versions of ModemManager suite may not be supported in the newer versions. [Other Info] We need to upgrade to these 3 packages (in Impish) at the same time: * ModemManager: 1.16.6 * libmbim: 1.24.8 * libqmi : 1.28.6 To support the mentioned 2 modems, the system needs to use kernels which include specific patches and kernel config options . For ex., there is a patched 5.11 kernel which is working for: https://bugs.launchpad.net/austin/+bug/1928665/comments/7 -- 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/1934286 Title: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases. Status in OEM Priority Project: Confirmed Status in modemmanager package in Ubuntu: New Bug description: [Impact] Some IOT products use wireless modems which can be working only when recent versions of the ModemManager suite are used. The following 2 modems need the ModemManager suite to be upgraded: * Foxconn SDX55 T99W175 5G sub6 PCIE Modem * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem The main fix requested is to add the FCC unlock mechanism for Foxconn modems. * FCC unlock operation for Foxconn modems https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/534/commits * dms: new 'Foxconn Set FCC
[Desktop-packages] [Bug 1934286] Re: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases.
** Description changed: [Impact] Some IOT products use wireless modems which can be working only when recent versions of the ModemManager suite are used. The following 2 modems need the ModemManager suite to be upgraded: * Foxconn SDX55 T99W175 5G sub6 PCIE Modem - * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem - + * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem + The main fix requested is to add the FCC unlock mechanism for Foxconn modems. * FCC unlock operation for Foxconn modems https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/534/commits * dms: new 'Foxconn Set FCC authentication' command https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/merge_requests/254/commits The minimum versions of the ModemManager suite required to enable the support for the above 2 mentioned modems have been verified: (LP: #1928665) * ModemManager: 1.16.6 * libmbim: 1.24.6 * libqmi : 1.28.6 The ModemManager suite in the Impish release meets the requirements. [Test Plan] = How to Reproduce the Bug = Execute the following commands to list the modems detected by ModemManager in Hirsute and Focal releases: $ mmcli --list-modems No modems were found - = Test Procedure = 1. Install the Ubuntu system on the tested hardware - The following images will be used to verify the version of the ModemManager suite: - * Impish: https://cdimage.ubuntu.com/daily-live/current/impish-desktop-amd64.iso - * Hirsute: https://releases.ubuntu.com/21.04/ubuntu-21.04-desktop-amd64.iso - * Focal: https://releases.ubuntu.com/focal/ubuntu-20.04.2.0-desktop-amd64.iso + The following images will be used to verify the version of the ModemManager suite: + * Impish: https://cdimage.ubuntu.com/daily-live/current/impish-desktop-amd64.iso + * Hirsute: https://releases.ubuntu.com/21.04/ubuntu-21.04-desktop-amd64.iso + * Focal: https://releases.ubuntu.com/focal/ubuntu-20.04.2.0-desktop-amd64.iso 2. Upgrade the kernel and driver ( for Foxconn and Quectel modem ) - The kernel needs to get some patches from 5.13 and includes a back ported Quectel driver to support these 2 modems. - We have prepared a kernel packages for testing: https://people.canonical.com/~mschiu77/lp1928665/v2/ + The kernel needs to get some patches from 5.13 and includes a back ported Quectel driver to support these 2 modems. + We have prepared a kernel packages for testing: https://people.canonical.com/~mschiu77/lp1928665/v2/ 3. Install the ModemManager suite ( for Hirsute and Focal releases ) - The ModemManager suite will be installed from Impish: + The ModemManager suite will be installed from Impish: $ sudo apt update $ sudo apt install modemmanager/impish $ sudo apt install libqmi-utils/impish - 4. Execute the following commands 4.1 Get the run-time environment $ uname -ar $ lsb_release -a $ mmcli -V $ qmicli -V 4.2 Check the status of the ModemManager service $ sudo systemctl status ModemManager.service - 4.3 List the detected modems $ mmcli --list-modems - 4.4 Check the modem’s status $ mmcli --modem 0 - - 4.5 Install and execute Lenovo’s FCC unlock app ( for Quectel modem only ) + 4.5 Install and execute Lenovo’s FCC unlock app ( for Quectel modem only + ) $ sudo snap install --devmode --dangerous dpr-wwan_1.0-wwan- test_amd64.snap - 4.6 Enable the detected modem $ sudo mmcli --modem 0 --enable - 4.7 Check the modem’s status $ mmcli --modem 0 = Analyze the Tested Result = 1. Check if installed packages are working - The result of test procedure 4.1 and 4.2 can be used to make sure the installed packages are working. - If the Modemmanager.service is active(running), the packages are working. + The result of test procedure 4.1 and 4.2 can be used to make sure the installed packages are working. + If the Modemmanager.service is active(running), the packages are working. 2. Check if the supported modem can be detected - The result of test procedure 4.3 can be used to see if the modem can be detected by ModemManager or not. - The supported modems should be listed. + The result of test procedure 4.3 can be used to see if the modem can be detected by ModemManager or not. + The supported modems should be listed. 3. Check if the modem can be enabled - If the modem can be enabled, the state of the modem in the test + If the modem can be enabled, the state of the modem in the test procedure 4.7 will be set to be registered. - [Where problems could occur] There is a risk that modems supported in the old versions of ModemManager suite may not be supported in the newer versions. + [Other Info] - [Other Info] - - We need to upgrade to these 3 packages at the same time: + We need to upgrade to these 3 packages (in Impish) at the same time: * ModemManager:
[Desktop-packages] [Bug 1934564] Re: Ubuntu logo shows as forbidden/missing icon in About
I don't get a forbidden message, or error. I get a DEBIAN logo. Given I like debian, I have no issue with it, however that is not expected, and I bet not intended. Using impish, but my desktop is Lubuntu/LXQt and I'm running it from terminal guiverc@d960-ubu2:/de2900/lubuntu$ gnome-control-center Gtk-Message: 19:46:30.478: Failed to load module "appmenu-gtk-module" (gnome-control-center:1839197): display-cc-panel-WARNING **: 19:46:36.841: Error calling GetCurrentState: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.gnome.Mutter.DisplayConfig" does not exist Gtk-Message: 19:46:43.263: Failed to load module "appmenu-gtk-module" -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1934564 Title: Ubuntu logo shows as forbidden/missing icon in About Status in gnome-control-center package in Ubuntu: Confirmed Bug description: Running the Ubuntu Impish Indri development branch, everything is up to date. For some reason, when I go to the About page, the forbidden sign is shown in place of what's supposed to be a Ubuntu logo. What is expected to happen: The Ubuntu logo shows correctly. What happened: The forbidden sign is shown in the place where it's supposed to show the Ubuntu logo. lsb_release -rd: Description: Ubuntu Impish Indri (development branch) Release: 21.10 apt-cache policy gnome-control-center: gnome-control-center: Installed: 1:40.0-1ubuntu1 Candidate: 1:40.0-1ubuntu1 Version table: *** 1:40.0-1ubuntu1 500 500 http://sy.archive.ubuntu.com/ubuntu impish/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-control-center 1:40.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21 Uname: Linux 5.11.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Jul 3 15:48:49 2021 InstallationDate: Installed on 2021-02-02 (150 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210123) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1934564/+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 1934286] Re: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases.
hm, so I sponsored the modemmanager bits, but seeing the description we still need to get libqmi from impish into hirsute and focal + libmbim from hirsute to focal, right? Should I prepare backports of those as well? -- 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/1934286 Title: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases. Status in OEM Priority Project: Confirmed Status in modemmanager package in Ubuntu: New Bug description: [Impact] Some IOT products use wireless modems which can be working only when recent versions of the ModemManager suite are used. The following 2 modems need the ModemManager suite to be upgraded: * Foxconn SDX55 T99W175 5G sub6 PCIE Modem * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem The main fix requested is to add the FCC unlock mechanism for Foxconn modems. * FCC unlock operation for Foxconn modems https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/534/commits * dms: new 'Foxconn Set FCC authentication' command https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/merge_requests/254/commits The minimum versions of the ModemManager suite required to enable the support for the above 2 mentioned modems have been verified: (LP: #1928665) * ModemManager: 1.16.6 * libmbim: 1.24.6 * libqmi : 1.28.6 The ModemManager suite in the Impish release meets the requirements. [Test Plan] = How to Reproduce the Bug = Execute the following commands to list the modems detected by ModemManager in Hirsute and Focal releases: $ mmcli --list-modems No modems were found = Test Procedure = 1. Install the Ubuntu system on the tested hardware The following images will be used to verify the version of the ModemManager suite: * Impish: https://cdimage.ubuntu.com/daily-live/current/impish-desktop-amd64.iso * Hirsute: https://releases.ubuntu.com/21.04/ubuntu-21.04-desktop-amd64.iso * Focal: https://releases.ubuntu.com/focal/ubuntu-20.04.2.0-desktop-amd64.iso 2. Upgrade the kernel and driver ( for Foxconn and Quectel modem ) The kernel needs to get some patches from 5.13 and includes a back ported Quectel driver to support these 2 modems. We have prepared a kernel packages for testing: https://people.canonical.com/~mschiu77/lp1928665/v2/ 3. Install the ModemManager suite ( for Hirsute and Focal releases ) The ModemManager suite will be installed from Impish: $ sudo apt update $ sudo apt install modemmanager/impish $ sudo apt install libqmi-utils/impish 4. Execute the following commands 4.1 Get the run-time environment $ uname -ar $ lsb_release -a $ mmcli -V $ qmicli -V 4.2 Check the status of the ModemManager service $ sudo systemctl status ModemManager.service 4.3 List the detected modems $ mmcli --list-modems 4.4 Check the modem’s status $ mmcli --modem 0 4.5 Install and execute Lenovo’s FCC unlock app ( for Quectel modem only ) $ sudo snap install --devmode --dangerous dpr-wwan_1.0-wwan- test_amd64.snap 4.6 Enable the detected modem $ sudo mmcli --modem 0 --enable 4.7 Check the modem’s status $ mmcli --modem 0 = Analyze the Tested Result = 1. Check if installed packages are working The result of test procedure 4.1 and 4.2 can be used to make sure the installed packages are working. If the Modemmanager.service is active(running), the packages are working. 2. Check if the supported modem can be detected The result of test procedure 4.3 can be used to see if the modem can be detected by ModemManager or not. The supported modems should be listed. 3. Check if the modem can be enabled If the modem can be enabled, the state of the modem in the test procedure 4.7 will be set to be registered. [Where problems could occur] There is a risk that modems supported in the old versions of ModemManager suite may not be supported in the newer versions. [Other Info] We need to upgrade to these 3 packages at the same time: * ModemManager: 1.16.6 * libmbim: 1.24.6 * libqmi : 1.28.6 To support the mentioned 2 modems, the system needs to use kernels which include specific patches and kernel config options . For ex., there is a patched 5.11 kernel which is working for: https://bugs.launchpad.net/austin/+bug/1928665/comments/7 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1934286/+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 1925320] Autopkgtest regression report (xorg-server/2:1.20.11-1ubuntu1~20.04.2)
All autopkgtests for the newly accepted xorg-server (2:1.20.11-1ubuntu1~20.04.2) for focal have finished running. The following regressions have been reported in tests triggered by the package: gtk+3.0/3.24.20-0ubuntu1 (s390x) notepadqq/2.0.0~beta1-1build1 (armhf) apport/2.20.11-0ubuntu27.18 (amd64) saods9/8.1+repack-1 (amd64) xmobar/0.29.4-2build3 (arm64) bambam/1.0.1+dfsg-1 (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#xorg-server [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1925320 Title: Backport packages for 20.04.3 HWE stack Status in directx-headers package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-12 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in directx-headers source package in Focal: Fix Committed Status in libdrm source package in Focal: Fix Committed Status in llvm-toolchain-12 source package in Focal: Fix Released Status in mesa source package in Focal: Fix Committed Status in xorg-server source package in Focal: Fix Committed Bug description: [Impact] These are needed for 20.04.3 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. [What could go wrong] directx-headers: a new package, nothing can go wrong libdrm: adds some new api, no changes to old stuff llvm-12: a new package, no regression potential on it's own mesa: a new major release, but we'll pull the final stable release of 21.0.x series, so there shouldn't be any regressions left at that point xserver: a new point-release, 1.20.x series is in deep maintenance mode, so there should be little chance of breakage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/1925320/+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 1931547] Autopkgtest regression report (xorg-server/2:1.20.11-1ubuntu1~20.04.2)
All autopkgtests for the newly accepted xorg-server (2:1.20.11-1ubuntu1~20.04.2) for focal have finished running. The following regressions have been reported in tests triggered by the package: gtk+3.0/3.24.20-0ubuntu1 (s390x) notepadqq/2.0.0~beta1-1build1 (armhf) apport/2.20.11-0ubuntu27.18 (amd64) saods9/8.1+repack-1 (amd64) xmobar/0.29.4-2build3 (arm64) bambam/1.0.1+dfsg-1 (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#xorg-server [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1931547 Title: DisplayLink displays are black after Mesa update Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Fix Committed Status in xorg-server source package in Focal: Fix Committed Status in xorg-server source package in Hirsute: Fix Committed Status in xorg-server source package in Impish: Fix Committed Bug description: [Impact] On Mesa versions before 21.0.x glamor_egl_init failed which then (luckily) disabled reverse_prime_offload_mode. But now with the new Mesa the GL_RENDERER has changed and glamor_egl_init succeeds and then enables reverse_prime_offload_mode. This backported commit disables reverse_prime_offload_mode for good for DisplayLink (udl, evdi) devices. [Test case] Update xserver, check that DisplayLink device (udl and/or evdi as available) works fine. [Where things could go wrong] This commit only disables reverse_prime_offload_mode for udl, evdi devices, other devices will not be affected. 'udl' is used by old USB2 based DisplayLink devices that have a native kernel driver 'evdi' is used by newer USB3 based devices that use an out-of-tree driver provided by Displaylink both need the same change, as they are otherwise similar at least evdi devices (as found on some laptop docks) have been tested to work with this -- Please incorporate xorg-server fix for issue: https://gitlab.freedesktop.org/xorg/xserver/-/issues/1183 It was already merged in to xserver master and xserver-1.20-branch branches. https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/681 https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/683 This is reported by our users reports on Ubuntu 20.10 with Xserver-1.20.9 and on Ubuntu 21.04 with XServer-1.20.11 If it is required i am willing to help with anything. To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1931547/+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 1934286] Re: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases.
Thank you for providing the debdiffs! From what I see there are no series-specific changes, right? So those are essentially straight backports to hirsute and focal? Anyway, I treated those as such and sponsored both (with slight changelog adjustments) - they are now in the hirsute and focal Unapproved queues, waiting for SRU review. -- 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/1934286 Title: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases. Status in OEM Priority Project: Confirmed Status in modemmanager package in Ubuntu: New Bug description: [Impact] Some IOT products use wireless modems which can be working only when recent versions of the ModemManager suite are used. The following 2 modems need the ModemManager suite to be upgraded: * Foxconn SDX55 T99W175 5G sub6 PCIE Modem * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem The main fix requested is to add the FCC unlock mechanism for Foxconn modems. * FCC unlock operation for Foxconn modems https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/534/commits * dms: new 'Foxconn Set FCC authentication' command https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/merge_requests/254/commits The minimum versions of the ModemManager suite required to enable the support for the above 2 mentioned modems have been verified: (LP: #1928665) * ModemManager: 1.16.6 * libmbim: 1.24.6 * libqmi : 1.28.6 The ModemManager suite in the Impish release meets the requirements. [Test Plan] = How to Reproduce the Bug = Execute the following commands to list the modems detected by ModemManager in Hirsute and Focal releases: $ mmcli --list-modems No modems were found = Test Procedure = 1. Install the Ubuntu system on the tested hardware The following images will be used to verify the version of the ModemManager suite: * Impish: https://cdimage.ubuntu.com/daily-live/current/impish-desktop-amd64.iso * Hirsute: https://releases.ubuntu.com/21.04/ubuntu-21.04-desktop-amd64.iso * Focal: https://releases.ubuntu.com/focal/ubuntu-20.04.2.0-desktop-amd64.iso 2. Upgrade the kernel and driver ( for Foxconn and Quectel modem ) The kernel needs to get some patches from 5.13 and includes a back ported Quectel driver to support these 2 modems. We have prepared a kernel packages for testing: https://people.canonical.com/~mschiu77/lp1928665/v2/ 3. Install the ModemManager suite ( for Hirsute and Focal releases ) The ModemManager suite will be installed from Impish: $ sudo apt update $ sudo apt install modemmanager/impish $ sudo apt install libqmi-utils/impish 4. Execute the following commands 4.1 Get the run-time environment $ uname -ar $ lsb_release -a $ mmcli -V $ qmicli -V 4.2 Check the status of the ModemManager service $ sudo systemctl status ModemManager.service 4.3 List the detected modems $ mmcli --list-modems 4.4 Check the modem’s status $ mmcli --modem 0 4.5 Install and execute Lenovo’s FCC unlock app ( for Quectel modem only ) $ sudo snap install --devmode --dangerous dpr-wwan_1.0-wwan- test_amd64.snap 4.6 Enable the detected modem $ sudo mmcli --modem 0 --enable 4.7 Check the modem’s status $ mmcli --modem 0 = Analyze the Tested Result = 1. Check if installed packages are working The result of test procedure 4.1 and 4.2 can be used to make sure the installed packages are working. If the Modemmanager.service is active(running), the packages are working. 2. Check if the supported modem can be detected The result of test procedure 4.3 can be used to see if the modem can be detected by ModemManager or not. The supported modems should be listed. 3. Check if the modem can be enabled If the modem can be enabled, the state of the modem in the test procedure 4.7 will be set to be registered. [Where problems could occur] There is a risk that modems supported in the old versions of ModemManager suite may not be supported in the newer versions. [Other Info] We need to upgrade to these 3 packages at the same time: * ModemManager: 1.16.6 * libmbim: 1.24.6 * libqmi : 1.28.6 To support the mentioned 2 modems, the system needs to use kernels which include specific patches and kernel config options . For ex., there is a patched 5.11 kernel which is working for: https://bugs.launchpad.net/austin/+bug/1928665/comments/7 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1934286/+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 1875015] Re: Ubuntu 20.04 and Displaylink is extremely slow
What about focal and hirsute, will it be merged in? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1875015 Title: Ubuntu 20.04 and Displaylink is extremely slow Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Fix Committed Status in xorg-server source package in Focal: In Progress Status in xorg-server source package in Hirsute: In Progress Status in xorg-server source package in Impish: Fix Committed Bug description: Using ubuntu 20.04 on displaylink docking with external monitor is totally slow, unusable. The GUI responds very slow, if you click, the command of the click goes on after about 3 seconds... if you type, all the letters are with the same lag, so it is totally unusable. Was using displaylink without any problem on 19.10 until yesterday, when I upgraded to 20.04. It is terrific. If i plug out the usb for the displaylink docking station, than the speed is back, and the system is ok, if I connect it to the docking station again, everything extremely slow again. Please investigate this asap, as it is unusable on displaylink docking stations. To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1875015/+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 1931547] Re: DisplayLink displays are black after Mesa update
Yes. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1931547 Title: DisplayLink displays are black after Mesa update Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Fix Committed Status in xorg-server source package in Focal: Fix Committed Status in xorg-server source package in Hirsute: Fix Committed Status in xorg-server source package in Impish: Fix Committed Bug description: [Impact] On Mesa versions before 21.0.x glamor_egl_init failed which then (luckily) disabled reverse_prime_offload_mode. But now with the new Mesa the GL_RENDERER has changed and glamor_egl_init succeeds and then enables reverse_prime_offload_mode. This backported commit disables reverse_prime_offload_mode for good for DisplayLink (udl, evdi) devices. [Test case] Update xserver, check that DisplayLink device (udl and/or evdi as available) works fine. [Where things could go wrong] This commit only disables reverse_prime_offload_mode for udl, evdi devices, other devices will not be affected. 'udl' is used by old USB2 based DisplayLink devices that have a native kernel driver 'evdi' is used by newer USB3 based devices that use an out-of-tree driver provided by Displaylink both need the same change, as they are otherwise similar at least evdi devices (as found on some laptop docks) have been tested to work with this -- Please incorporate xorg-server fix for issue: https://gitlab.freedesktop.org/xorg/xserver/-/issues/1183 It was already merged in to xserver master and xserver-1.20-branch branches. https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/681 https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/683 This is reported by our users reports on Ubuntu 20.10 with Xserver-1.20.9 and on Ubuntu 21.04 with XServer-1.20.11 If it is required i am willing to help with anything. To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1931547/+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 1826056] Re: Desktop context: Keep aligned, Organize desktop by name missing
** Tags added: fixed-in-0.19 fixed-upstream -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1826056 Title: Desktop context: Keep aligned, Organize desktop by name missing Status in gnome-shell-extension-desktop-icons: Fix Released Status in gnome-shell-extension-desktop-icons package in Ubuntu: Triaged Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: Fix Committed Bug description: After upgrading from 18.10 to 19.04 the desktop context menu no longer contains the choices: Keep aligned Organize desktop by name These were very useful to me. I would like them to be restored. Ubuntu 19.04, 64bit Gnome 3.32.1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1826056/+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 1898910] Re: gnome-shell crashes with [St:ERROR:../src/st/st-bin.c:206:st_bin_destroy: assertion failed: (priv->child == NULL)] called from DesktopGrid::_backgroundDestroyed()
Hirsute had the fix before impish existed, and they're on the same package version anyway, so fix released in Impish too. ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1898910 Title: gnome-shell crashes with [St:ERROR:../src/st/st- bin.c:206:st_bin_destroy: assertion failed: (priv->child == NULL)] called from DesktopGrid::_backgroundDestroyed() [desktopGrid.js:206] Status in gnome-shell-extension-desktop-icons: Unknown Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell-extension-desktop-icons package in Ubuntu: Fix Released Status in gnome-shell source package in Groovy: Fix Released Status in gnome-shell-extension-desktop-icons source package in Groovy: Fix Released Status in gnome-shell source package in Hirsute: Fix Released Status in gnome-shell-extension-desktop-icons source package in Hirsute: Fix Released Bug description: [Impact] Gnome Shell crashes at random times. https://errors.ubuntu.com/problem/fcc5c581fc0a8c2f8f68314fa383690423a3dc02 [Test Case] None known. [Where problems could occur] The proposed fix is from the stable upstream gnome-shell branch so potential problems could arise from the usual risk of patching stable branches resulting in new regressions. [Other Info] See also bug 1898005 --- Ubuntu on Wayland crashes when you try to change the resolution even if your display supports the Version: 3.38.0-1ubuntu2 Release: 20.10 Groovy Gorilla (development branch) What I expected to happen 1. Login to Wayland 2. Change the resolution 3. Go on with my day What actually happened 1. Login to Wayland 2. Change the resolution 3. Wait a minute to get kicked to the gdm login screen 4. Now I am here. ProblemType: CrashDistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 Uname: Linux 5.8.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 7 12:55:35 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2020-10-07 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1 Signal: 6SourcePackage: gnome-shell StacktraceTop: () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /usr/lib/gnome-shell/libst-1.0.so g_closure_invoke () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1898910/+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 1931547] Re: DisplayLink displays are black after Mesa update
thanks for testing, was this with evdi/udl or both? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1931547 Title: DisplayLink displays are black after Mesa update Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Fix Committed Status in xorg-server source package in Focal: Fix Committed Status in xorg-server source package in Hirsute: Fix Committed Status in xorg-server source package in Impish: Fix Committed Bug description: [Impact] On Mesa versions before 21.0.x glamor_egl_init failed which then (luckily) disabled reverse_prime_offload_mode. But now with the new Mesa the GL_RENDERER has changed and glamor_egl_init succeeds and then enables reverse_prime_offload_mode. This backported commit disables reverse_prime_offload_mode for good for DisplayLink (udl, evdi) devices. [Test case] Update xserver, check that DisplayLink device (udl and/or evdi as available) works fine. [Where things could go wrong] This commit only disables reverse_prime_offload_mode for udl, evdi devices, other devices will not be affected. 'udl' is used by old USB2 based DisplayLink devices that have a native kernel driver 'evdi' is used by newer USB3 based devices that use an out-of-tree driver provided by Displaylink both need the same change, as they are otherwise similar at least evdi devices (as found on some laptop docks) have been tested to work with this -- Please incorporate xorg-server fix for issue: https://gitlab.freedesktop.org/xorg/xserver/-/issues/1183 It was already merged in to xserver master and xserver-1.20-branch branches. https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/681 https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/683 This is reported by our users reports on Ubuntu 20.10 with Xserver-1.20.9 and on Ubuntu 21.04 with XServer-1.20.11 If it is required i am willing to help with anything. To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1931547/+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 1280300] Re: Desktop contents displayed on resume, before lock screen is shown
We're mid 2021 and this security issue is still present. Confirmed on Ubuntu 20.04. Also on Zorin OS 15 (Ubuntu 18.04 based). Besides only getting medium priority, I cannot understand that this medium priority security issue hasn't been assigned, leave alone fixed in nearly 7 years. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1280300 Title: Desktop contents displayed on resume, before lock screen is shown Status in gnome-screensaver package in Ubuntu: Confirmed Bug description: I am running 14.04. When I resume from sleep, the contents of my desktop (including any open windows, emails, etc) are displayed onscreen briefly before the unlock screen is shown. This potentially allows an attacker to view the contents of a locked screen. To reproduce: 1) Suspend a machine, e.g. by closing the lid 2) Resume the machine Expected results: Upon resume, the first thing shown onscreen is the screensaver unlock screen. Actual results: Upon resume, the first thing shown onscreen is the set of open windows that were displayed before the machine was put to sleep. After a second or two, the unlock screen is drawn and you have to enter a password to unlock the machine. This is reproducible on my system. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-screensaver 3.6.1-0ubuntu9 ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Feb 14 09:05:50 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 EcryptfsInUse: Yes GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session session-name 'ubuntu' org.gnome.desktop.session idle-delay uint32 300 InstallationDate: Installed on 2013-12-02 (73 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20130203-13:50 SourcePackage: gnome-screensaver UpgradeStatus: Upgraded to trusty on 2014-02-12 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1280300/+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 1931547] Re: DisplayLink displays are black after Mesa update
I have installed proposed hiruste packege on Ubuntu 21.04. Package works fine, DisplayLink displays are working. ** Tags removed: verification-needed-hirsute ** Tags added: verification-done-hirsute -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1931547 Title: DisplayLink displays are black after Mesa update Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Fix Committed Status in xorg-server source package in Focal: Fix Committed Status in xorg-server source package in Hirsute: Fix Committed Status in xorg-server source package in Impish: Fix Committed Bug description: [Impact] On Mesa versions before 21.0.x glamor_egl_init failed which then (luckily) disabled reverse_prime_offload_mode. But now with the new Mesa the GL_RENDERER has changed and glamor_egl_init succeeds and then enables reverse_prime_offload_mode. This backported commit disables reverse_prime_offload_mode for good for DisplayLink (udl, evdi) devices. [Test case] Update xserver, check that DisplayLink device (udl and/or evdi as available) works fine. [Where things could go wrong] This commit only disables reverse_prime_offload_mode for udl, evdi devices, other devices will not be affected. 'udl' is used by old USB2 based DisplayLink devices that have a native kernel driver 'evdi' is used by newer USB3 based devices that use an out-of-tree driver provided by Displaylink both need the same change, as they are otherwise similar at least evdi devices (as found on some laptop docks) have been tested to work with this -- Please incorporate xorg-server fix for issue: https://gitlab.freedesktop.org/xorg/xserver/-/issues/1183 It was already merged in to xserver master and xserver-1.20-branch branches. https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/681 https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/683 This is reported by our users reports on Ubuntu 20.10 with Xserver-1.20.9 and on Ubuntu 21.04 with XServer-1.20.11 If it is required i am willing to help with anything. To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1931547/+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 1931547] Re: DisplayLink displays are black after Mesa update
I have installed proposed focal package on Pop!_OS 20.10 - derivative of groovy Issue is gone all works fine. Added tag verification-done-focal ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1931547 Title: DisplayLink displays are black after Mesa update Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Fix Committed Status in xorg-server source package in Focal: Fix Committed Status in xorg-server source package in Hirsute: Fix Committed Status in xorg-server source package in Impish: Fix Committed Bug description: [Impact] On Mesa versions before 21.0.x glamor_egl_init failed which then (luckily) disabled reverse_prime_offload_mode. But now with the new Mesa the GL_RENDERER has changed and glamor_egl_init succeeds and then enables reverse_prime_offload_mode. This backported commit disables reverse_prime_offload_mode for good for DisplayLink (udl, evdi) devices. [Test case] Update xserver, check that DisplayLink device (udl and/or evdi as available) works fine. [Where things could go wrong] This commit only disables reverse_prime_offload_mode for udl, evdi devices, other devices will not be affected. 'udl' is used by old USB2 based DisplayLink devices that have a native kernel driver 'evdi' is used by newer USB3 based devices that use an out-of-tree driver provided by Displaylink both need the same change, as they are otherwise similar at least evdi devices (as found on some laptop docks) have been tested to work with this -- Please incorporate xorg-server fix for issue: https://gitlab.freedesktop.org/xorg/xserver/-/issues/1183 It was already merged in to xserver master and xserver-1.20-branch branches. https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/681 https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/683 This is reported by our users reports on Ubuntu 20.10 with Xserver-1.20.9 and on Ubuntu 21.04 with XServer-1.20.11 If it is required i am willing to help with anything. To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1931547/+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 1931547] Autopkgtest regression report (xorg-server/2:1.20.11-1ubuntu1.1)
All autopkgtests for the newly accepted xorg-server (2:1.20.11-1ubuntu1.1) for hirsute have finished running. The following regressions have been reported in tests triggered by the package: libsoup2.4/2.72.0-3 (armhf) aptdaemon/1.1.1+bzr982-0ubuntu36 (amd64, s390x, ppc64el) gscan2pdf/2.11.0-1 (s390x) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/hirsute/update_excuses.html#xorg-server [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1931547 Title: DisplayLink displays are black after Mesa update Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Fix Committed Status in xorg-server source package in Focal: Fix Committed Status in xorg-server source package in Hirsute: Fix Committed Status in xorg-server source package in Impish: Fix Committed Bug description: [Impact] On Mesa versions before 21.0.x glamor_egl_init failed which then (luckily) disabled reverse_prime_offload_mode. But now with the new Mesa the GL_RENDERER has changed and glamor_egl_init succeeds and then enables reverse_prime_offload_mode. This backported commit disables reverse_prime_offload_mode for good for DisplayLink (udl, evdi) devices. [Test case] Update xserver, check that DisplayLink device (udl and/or evdi as available) works fine. [Where things could go wrong] This commit only disables reverse_prime_offload_mode for udl, evdi devices, other devices will not be affected. 'udl' is used by old USB2 based DisplayLink devices that have a native kernel driver 'evdi' is used by newer USB3 based devices that use an out-of-tree driver provided by Displaylink both need the same change, as they are otherwise similar at least evdi devices (as found on some laptop docks) have been tested to work with this -- Please incorporate xorg-server fix for issue: https://gitlab.freedesktop.org/xorg/xserver/-/issues/1183 It was already merged in to xserver master and xserver-1.20-branch branches. https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/681 https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/683 This is reported by our users reports on Ubuntu 20.10 with Xserver-1.20.9 and on Ubuntu 21.04 with XServer-1.20.11 If it is required i am willing to help with anything. To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1931547/+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 1919400] Re: Wayland support is missing, if booted with the monitor turned off
** Tags added: impish ** Summary changed: - Wayland support is missing, if booted with the monitor turned off + Wayland login option is missing if booted with the monitor turned off -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1919400 Title: Wayland login option is missing if booted with the monitor turned off Status in gdm3 package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Bug description: Wayland sessions are missing/not supported, if booted with the monitor turned off. and the system log suggests why: gnome-shell[1007]: Failed to create backend: No GPUs with outputs found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1919400/+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
