[Bug 1951586] Re: Need option to specify wifi regulatory domain
> I wondered if perhaps it this only works on some APs? That is the impression that I get, the country code info is part of the management frames transmitted by the AP, could be unsupported, not configured, or mis-configured. grep wpa may6.txt May 6 09:04:57 box wpa_supplicant[810]: wlan0: WPS-PBC-ACTIVE May 6 09:05:34 box wpa_supplicant[810]: wlan0: Trying to associate with SSID 'BELL188' May 6 09:05:36 box wpa_supplicant[810]: wlan0: Associated with 2c:79:d7:05:5e:0e May 6 09:05:36 box wpa_supplicant[810]: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0 May 6 09:05:36 box wpa_supplicant[810]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=CA May 6 09:05:45 box wpa_supplicant[810]: wlan0: CTRL-EVENT-DISCONNECTED bssid=2c:79:d7:05:5e:0e reason=15 May 6 09:05:45 box wpa_supplicant[810]: wlan0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect May 6 09:05:45 box wpa_supplicant[810]: wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="BELL188" auth_failures=1 duration=10 reason=WRONG_KEY May 6 09:05:45 box wpa_supplicant[810]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD May 6 09:05:45 box wpa_supplicant[810]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=US May 6 09:06:58 box wpa_supplicant[810]: wlan0: Trying to associate with SSID 'BELL188' May 6 09:07:01 box wpa_supplicant[810]: wlan0: Associated with 2c:79:d7:05:5e:0e May 6 09:07:01 box wpa_supplicant[810]: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0 May 6 09:07:01 box wpa_supplicant[810]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=CA May 6 09:07:10 box wpa_supplicant[810]: wlan0: CTRL-EVENT-DISCONNECTED bssid=2c:79:d7:05:5e:0e reason=15 May 6 09:07:10 box wpa_supplicant[810]: wlan0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect May 6 09:07:10 box wpa_supplicant[810]: wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="BELL188" auth_failures=1 duration=10 reason=WRONG_KEY May 6 09:07:10 box wpa_supplicant[810]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD May 6 09:07:10 box wpa_supplicant[810]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=US May 6 09:07:32 box wpa_supplicant[810]: wlan0: Trying to associate with SSID 'BELL188' May 6 09:07:35 box wpa_supplicant[810]: wlan0: Associated with 2c:79:d7:05:5e:0e May 6 09:07:35 box wpa_supplicant[810]: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0 May 6 09:07:35 box wpa_supplicant[810]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=CA May 6 09:07:44 box wpa_supplicant[810]: wlan0: CTRL-EVENT-DISCONNECTED bssid=2c:79:d7:05:5e:0e reason=15 May 6 09:07:44 box wpa_supplicant[810]: wlan0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect May 6 09:07:44 box wpa_supplicant[810]: wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="BELL188" auth_failures=1 duration=10 reason=WRONG_KEY May 6 09:07:44 box wpa_supplicant[810]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD May 6 09:07:44 box wpa_supplicant[810]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=US May 6 09:08:10 box wpa_supplicant[810]: wlan0: Trying to associate with SSID 'BELL188' May 6 09:08:13 box wpa_supplicant[810]: wlan0: Associated with 2c:79:d7:05:5e:0e May 6 09:08:13 box wpa_supplicant[810]: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0 May 6 09:08:13 box wpa_supplicant[810]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=CA May 6 09:08:21 box wpa_supplicant[810]: wlan0: CTRL-EVENT-DISCONNECTED bssid=2c:79:d7:05:5e:0e reason=3 locally_generated=1 May 6 09:08:21 box wpa_supplicant[810]: wlan0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect May 6 09:08:21 box wpa_supplicant[810]: wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="BELL188" auth_failures=1 duration=10 reason=WRONG_KEY May 6 09:08:21 box wpa_supplicant[810]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD May 6 09:08:21 box wpa_supplicant[810]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=US May 6 09:08:28 box wpa_supplicant[810]: wlan0: Trying to associate with SSID 'BELL188' May 6 09:08:31 box wpa_supplicant[810]: wlan0: CTRL-EVENT-DISCONNECTED bssid=2c:79:d7:05:5e:0e reason=3 locally_generated=1 May 6 09:08:31 box wpa_supplicant[810]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD May 6 09:08:31 box wpa_supplicant[810]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=US May 6 09:09:08 box wpa_supplicant[810]: wlan0: Trying to associate with SSID 'SHAW-DB6690' May 6 09:09:11 box wpa_supplicant[810]: wlan0: Associated with 00:fc:8d:db:66:98 May 6 09:09:11 box wpa_supplicant[810]: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0 May 6 09:09:11 box wpa_supplicant[810]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=US May 6 09:09:11 box wpa_supplicant[810]: wlan0: WPA: Key negotiation completed with 00:fc:8d:db:66:98 [PTK=CCMP
[Bug 1951586] Re: Need option to specify wifi regulatory domain
Connection via NetworkManager to AP 2993 May 6 09:55:54 124-u2204-desk NetworkManager[641]: [1651845354.5017] device (wlp2s0): Activation: starting connection '181-rpi4-64bit-raspios-LARGE' (9a51eba2-3723-4750-8a72-aa2e4c723140) 2994 May 6 09:55:54 124-u2204-desk NetworkManager[641]: [1651845354.5083] audit: op="connection-add-activate" uuid="9a51eba2-3723-4750-8a72-aa2e4c723140" name="181-rpi4-64bit-raspios-LARGE" pid=1342 uid=1000 result="success" 2995 May 6 09:55:54 124-u2204-desk NetworkManager[641]: [1651845354.5173] device (wlp2s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') 2996 May 6 09:55:54 124-u2204-desk NetworkManager[641]: [1651845354.5309] device (wlp2s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') 2997 May 6 09:55:54 124-u2204-desk NetworkManager[641]: [1651845354.5364] device (wlp2s0): Activation: (wifi) connection '181-rpi4-64bit-raspios-LARGE' requires no security. No secrets needed. 2998 May 6 09:55:54 124-u2204-desk NetworkManager[641]: [1651845354.5365] Config: added 'ssid' value '181-rpi4-64bit-raspios-LARGE' 2999 May 6 09:55:54 124-u2204-desk NetworkManager[641]: [1651845354.5366] Config: added 'scan_ssid' value '1' 3000 May 6 09:55:54 124-u2204-desk NetworkManager[641]: [1651845354.5366] Config: added 'bgscan' value 'simple:30:-70:86400' 3001 May 6 09:55:54 124-u2204-desk NetworkManager[641]: [1651845354.5367] Config: added 'key_mgmt' value 'NONE' 3002 May 6 09:55:54 124-u2204-desk NetworkManager[641]: [1651845354.5508] device (wlp2s0): supplicant interface state: disconnected -> scanning 3003 May 6 09:55:54 124-u2204-desk NetworkManager[641]: [1651845354.5509] device (p2p-dev-wlp2s0): supplicant management interface state: disconnected -> scanning 3004 May 6 09:55:55 124-u2204-desk wpa_supplicant[683]: wlp2s0: SME: Trying to authenticate with 02:72:82:96:ac:1e (SSID='181-rpi4-64bit-raspios-LARGE' freq=2437 MHz) 3005 May 6 09:55:55 124-u2204-desk kernel: [ 686.915199] wlp2s0: authenticate with 02:72:82:96:ac:1e 3006 May 6 09:55:55 124-u2204-desk kernel: [ 686.919826] wlp2s0: send auth to 02:72:82:96:ac:1e (try 1/3) 3007 May 6 09:55:55 124-u2204-desk kernel: [ 686.922147] wlp2s0: authenticated 3008 May 6 09:55:55 124-u2204-desk wpa_supplicant[683]: wlp2s0: Trying to associate with 02:72:82:96:ac:1e (SSID='181-rpi4-64bit-raspios-LARGE' freq=2437 MHz) 3009 May 6 09:55:55 124-u2204-desk NetworkManager[641]: [1651845355.1109] device (wlp2s0): supplicant interface state: scanning -> authenticating 3010 May 6 09:55:55 124-u2204-desk NetworkManager[641]: [1651845355.] device (p2p-dev-wlp2s0): supplicant management interface state: scanning -> authenticating 3011 May 6 09:55:55 124-u2204-desk kernel: [ 686.929202] wlp2s0: associate with 02:72:82:96:ac:1e (try 1/3) 3012 May 6 09:55:55 124-u2204-desk wpa_supplicant[683]: wlp2s0: Associated with 02:72:82:96:ac:1e 3013 May 6 09:55:55 124-u2204-desk kernel: [ 686.937597] wlp2s0: RX AssocResp from 02:72:82:96:ac:1e (capab=0x401 status=0 aid=1) 3014 May 6 09:55:55 124-u2204-desk kernel: [ 686.938943] wlp2s0: associated 3015 May 6 09:55:55 124-u2204-desk kernel: [ 686.940900] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready 3016 May 6 09:55:55 124-u2204-desk NetworkManager[641]: [1651845355.1276] device (wlp2s0): supplicant interface state: authenticating -> associating 3017 May 6 09:55:55 124-u2204-desk NetworkManager[641]: [1651845355.1277] device (p2p-dev-wlp2s0): supplicant management interface state: authenticating -> associating 3018 May 6 09:55:55 124-u2204-desk wpa_supplicant[683]: wlp2s0: CTRL-EVENT-CONNECTED - Connection to 02:72:82:96:ac:1e completed [id=0 id_str=] 3019 May 6 09:55:55 124-u2204-desk wpa_supplicant[683]: wlp2s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0 3020 May 6 09:55:55 124-u2204-desk wpa_supplicant[683]: wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=US 3021 May 6 09:55:55 124-u2204-desk NetworkManager[641]: [1651845355.1389] device (wlp2s0): supplicant interface state: associating -> completed 3022 May 6 09:55:55 124-u2204-desk NetworkManager[641]: [1651845355.1390] device (wlp2s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "181-rpi4-64bit-raspios-LARGE" 3023 May 6 09:55:55 124-u2204-desk NetworkManager[641]: [1651845355.1391] device (p2p-dev-wlp2s0): supplicant management interface state: associating -> completed 3024 May 6 09:55:55 124-u2204-desk NetworkManager[641]: [1651845355.1457] device (wlp2s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed') 3025 May 6 09:55:55 124-u2204-desk NetworkManager[641]: [1651845355.1504] dhcp4 (wlp2s0): activation: beginning transaction (timeout in 45 seconds) 3026 May 6 09:55:55 124-u2204-desk avahi-daemon[636]: Joining mDNS multicast group on interface wlp2s0.IPv6
[Bug 1971075] Re: external monitor vga port with internal intel graphic not working with ubuntu 20.04 wayland
** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released ** Changed in: linux (Ubuntu) Status: Fix Released => Incomplete ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Jerry Salfian (jsalfian-marketing) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971075 Title: external monitor vga port with internal intel graphic not working with ubuntu 20.04 wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971075] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1971075/+attachment/5585969/+files/acpidump.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971075 Title: external monitor vga port with internal intel graphic not working with ubuntu 20.04 wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971075] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1971075/+attachment/5585967/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971075 Title: external monitor vga port with internal intel graphic not working with ubuntu 20.04 wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971075] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1971075/+attachment/5585968/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971075 Title: external monitor vga port with internal intel graphic not working with ubuntu 20.04 wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971075] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1971075/+attachment/5585964/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971075 Title: external monitor vga port with internal intel graphic not working with ubuntu 20.04 wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971075] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1971075/+attachment/5585966/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971075 Title: external monitor vga port with internal intel graphic not working with ubuntu 20.04 wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971075] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1971075/+attachment/5585965/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971075 Title: external monitor vga port with internal intel graphic not working with ubuntu 20.04 wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971075] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1971075/+attachment/5585962/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971075 Title: external monitor vga port with internal intel graphic not working with ubuntu 20.04 wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971075] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1971075/+attachment/5585963/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971075 Title: external monitor vga port with internal intel graphic not working with ubuntu 20.04 wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971075] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1971075/+attachment/5585960/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971075 Title: external monitor vga port with internal intel graphic not working with ubuntu 20.04 wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971075] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1971075/+attachment/5585961/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971075 Title: external monitor vga port with internal intel graphic not working with ubuntu 20.04 wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971075] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1971075/+attachment/5585959/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971075 Title: external monitor vga port with internal intel graphic not working with ubuntu 20.04 wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971075] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1971075/+attachment/5585958/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971075 Title: external monitor vga port with internal intel graphic not working with ubuntu 20.04 wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971075] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1971075/+attachment/5585957/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971075 Title: external monitor vga port with internal intel graphic not working with ubuntu 20.04 wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971075] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1971075/+attachment/5585955/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971075 Title: external monitor vga port with internal intel graphic not working with ubuntu 20.04 wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971075] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1971075/+attachment/5585956/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971075 Title: external monitor vga port with internal intel graphic not working with ubuntu 20.04 wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971075] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1971075/+attachment/5585954/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971075 Title: external monitor vga port with internal intel graphic not working with ubuntu 20.04 wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971075] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1971075/+attachment/5585953/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971075 Title: external monitor vga port with internal intel graphic not working with ubuntu 20.04 wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971075] Re: external monitor vga port with internal intel graphic not working with ubuntu 20.04 wayland
apport information ** Tags added: apport-collected focal wayland-session ** Description changed: Hello There, I'm using ubuntu desktop for about 12 years Using the LTS released. and using External monitor (Acer G195HOV) vga port connected to my laptop hp2540p. It's working good within ubuntu desktop 16.04 LTS, and "working for a while" after upgrade to ubuntu 20.04 LTS. After the kernel updated to version 5.10 the external monitor stop working Blank screen. FYI: Currently I'm using ubuntu 20.04 with kernel 5.15. jerry@hp-2540p:~$ hostnamectl Static hostname: hp-2540p Icon name: computer-laptop Chassis: laptop Machine ID: de4b56ef6180e8fc7e641c9d5fddb479 Boot ID: fb02c732e3cf4de2bd716259ecfdee56 Operating System: Ubuntu 20.04.4 LTS Kernel: Linux 5.15.0-17-generic Architecture: x86-64 jerry@hp-2540p:~$ echo $XDG_SESSION_TYPE wayland jerry@hp-2540p:~$ sudo lspci -v [sudo] password for jerry: 00:00.0 Host bridge: Intel Corporation Core Processor DRAM Controller (rev 02) Subsystem: Hewlett-Packard Company Core Processor DRAM Controller Flags: bus master, fast devsel, latency 0 Capabilities: [e0] Vendor Specific Information: Len=0c 00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 02) (prog-if 00 [VGA controller]) DeviceName: 32 Subsystem: Hewlett-Packard Company Core Processor Integrated Graphics Controller Flags: bus master, fast devsel, latency 0, IRQ 29 Memory at d000 (64-bit, non-prefetchable) [size=4M] Memory at c000 (64-bit, prefetchable) [size=256M] I/O ports at 5058 [size=8] Expansion ROM at 000c [virtual] [disabled] [size=128K] Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [d0] Power Management version 2 Capabilities: [a4] PCI Advanced Features Kernel driver in use: i915 Kernel modules: i915 00:16.0 Communication controller: Intel Corporation 5 Series/3400 Series Chipset HECI Controller (rev 06) Subsystem: Hewlett-Packard Company 5 Series/3400 Series Chipset HECI Controller Flags: bus master, fast devsel, latency 0, IRQ 30 Memory at d4724000 (64-bit, non-prefetchable) [size=16] Capabilities: [50] Power Management version 3 Capabilities: [8c] MSI: Enable+ Count=1/1 Maskable- 64bit+ Kernel driver in use: mei_me Kernel modules: mei_me 00:16.3 Serial controller: Intel Corporation 5 Series/3400 Series Chipset KT Controller (rev 06) (prog-if 02 [16550]) Subsystem: Hewlett-Packard Company 5 Series/3400 Series Chipset KT Controller Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 17 I/O ports at 5050 [size=8] Memory at d472b000 (32-bit, non-prefetchable) [size=4K] Capabilities: [c8] Power Management version 3 Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+ Kernel driver in use: serial 00:19.0 Ethernet controller: Intel Corporation 82577LM Gigabit Network Connection (rev 05) Subsystem: Hewlett-Packard Company 82577LM Gigabit Network Connection Flags: bus master, fast devsel, latency 0, IRQ 27 Memory at d470 (32-bit, non-prefetchable) [size=128K] Memory at d472a000 (32-bit, non-prefetchable) [size=4K] I/O ports at 5020 [size=32] Capabilities: [c8] Power Management version 2 Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [e0] PCI Advanced Features Kernel driver in use: e1000e Kernel modules: e1000e 00:1a.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05) (prog-if 20 [EHCI]) Subsystem: Hewlett-Packard Company 5 Series/3400 Series Chipset USB2 Enhanced Host Controller Flags: bus master, medium devsel, latency 0, IRQ 16 Memory at d4729000 (32-bit, non-prefetchable) [size=1K] Capabilities: [50] Power Management version 2 Capabilities: [58] Debug port: BAR=1 offset=00a0 Capabilities: [98] PCI Advanced Features Kernel driver in use: ehci-pci 00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 05) Subsystem: Hewlett-Packard Company 5 Series/3400 Series Chipset High Definition Audio Flags: bus master, fast devsel, latency 0, IRQ 32 Memory at d472 (64-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 2 Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00 Capabilities: [100] Virtual Channel Capabilities: [130] Root Complex Link Kernel driver in use: snd
[Bug 1971075] [NEW] external monitor vga port with internal intel graphic not working with ubuntu 20.04 wayland
Public bug reported: Hello There, I'm using ubuntu desktop for about 12 years Using the LTS released. and using External monitor (Acer G195HOV) vga port connected to my laptop hp2540p. It's working good within ubuntu desktop 16.04 LTS, and "working for a while" after upgrade to ubuntu 20.04 LTS. After the kernel updated to version 5.10 the external monitor stop working Blank screen. FYI: Currently I'm using ubuntu 20.04 with kernel 5.15. jerry@hp-2540p:~$ hostnamectl Static hostname: hp-2540p Icon name: computer-laptop Chassis: laptop Machine ID: de4b56ef6180e8fc7e641c9d5fddb479 Boot ID: fb02c732e3cf4de2bd716259ecfdee56 Operating System: Ubuntu 20.04.4 LTS Kernel: Linux 5.15.0-17-generic Architecture: x86-64 jerry@hp-2540p:~$ echo $XDG_SESSION_TYPE wayland jerry@hp-2540p:~$ sudo lspci -v [sudo] password for jerry: 00:00.0 Host bridge: Intel Corporation Core Processor DRAM Controller (rev 02) Subsystem: Hewlett-Packard Company Core Processor DRAM Controller Flags: bus master, fast devsel, latency 0 Capabilities: [e0] Vendor Specific Information: Len=0c 00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 02) (prog-if 00 [VGA controller]) DeviceName: 32 Subsystem: Hewlett-Packard Company Core Processor Integrated Graphics Controller Flags: bus master, fast devsel, latency 0, IRQ 29 Memory at d000 (64-bit, non-prefetchable) [size=4M] Memory at c000 (64-bit, prefetchable) [size=256M] I/O ports at 5058 [size=8] Expansion ROM at 000c [virtual] [disabled] [size=128K] Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [d0] Power Management version 2 Capabilities: [a4] PCI Advanced Features Kernel driver in use: i915 Kernel modules: i915 00:16.0 Communication controller: Intel Corporation 5 Series/3400 Series Chipset HECI Controller (rev 06) Subsystem: Hewlett-Packard Company 5 Series/3400 Series Chipset HECI Controller Flags: bus master, fast devsel, latency 0, IRQ 30 Memory at d4724000 (64-bit, non-prefetchable) [size=16] Capabilities: [50] Power Management version 3 Capabilities: [8c] MSI: Enable+ Count=1/1 Maskable- 64bit+ Kernel driver in use: mei_me Kernel modules: mei_me 00:16.3 Serial controller: Intel Corporation 5 Series/3400 Series Chipset KT Controller (rev 06) (prog-if 02 [16550]) Subsystem: Hewlett-Packard Company 5 Series/3400 Series Chipset KT Controller Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 17 I/O ports at 5050 [size=8] Memory at d472b000 (32-bit, non-prefetchable) [size=4K] Capabilities: [c8] Power Management version 3 Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+ Kernel driver in use: serial 00:19.0 Ethernet controller: Intel Corporation 82577LM Gigabit Network Connection (rev 05) Subsystem: Hewlett-Packard Company 82577LM Gigabit Network Connection Flags: bus master, fast devsel, latency 0, IRQ 27 Memory at d470 (32-bit, non-prefetchable) [size=128K] Memory at d472a000 (32-bit, non-prefetchable) [size=4K] I/O ports at 5020 [size=32] Capabilities: [c8] Power Management version 2 Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [e0] PCI Advanced Features Kernel driver in use: e1000e Kernel modules: e1000e 00:1a.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05) (prog-if 20 [EHCI]) Subsystem: Hewlett-Packard Company 5 Series/3400 Series Chipset USB2 Enhanced Host Controller Flags: bus master, medium devsel, latency 0, IRQ 16 Memory at d4729000 (32-bit, non-prefetchable) [size=1K] Capabilities: [50] Power Management version 2 Capabilities: [58] Debug port: BAR=1 offset=00a0 Capabilities: [98] PCI Advanced Features Kernel driver in use: ehci-pci 00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 05) Subsystem: Hewlett-Packard Company 5 Series/3400 Series Chipset High Definition Audio Flags: bus master, fast devsel, latency 0, IRQ 32 Memory at d472 (64-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 2 Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00 Capabilities: [100] Virtual Channel Capabilities: [130] Root Complex Link Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 (rev 05) (prog-if
[Bug 1969809] [NEW] ua fails if any package removed from server
Public bug reported: I'm using the ua tool (version 27.7~16.04.1). I'm unable to enable the esm-infra service because a couple of the packages that I have installed have been completely removed from the launchpad server. Specifically: deb http://ppa.launchpad.net/jonathonf/ffmpeg-3/ubuntu xenial main deb http://ppa.launchpad.net/jonathonf/python-3.6/ubuntu xenial main When I remove these package definitions from /etc/apt/sources.list.d/ the command succeeds. I've attached a log file that includes this stack trace. Traceback (most recent call last): File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 1629, in wrapper return func(*args, **kwargs) File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 1725, in main return args.action(args, cfg=cfg) File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 480, in action_fix fix_status = security.fix_security_issue_id(cfg, args.security_issue) File "/usr/lib/python3/dist-packages/uaclient/security.py", line 607, in fix_security_issue_id usn_released_pkgs=usn_released_pkgs, File "/usr/lib/python3/dist-packages/uaclient/security.py", line 982, in prompt_for_affected_packages num_pkgs=count, File "/usr/lib/python3/dist-packages/uaclient/security.py", line 872, in _handle_released_package_fixes cfg, binary_pkgs, pocket File "/usr/lib/python3/dist-packages/uaclient/security.py", line 1223, in upgrade_packages_and_attach if not _check_subscription_for_required_service(pocket, cfg): File "/usr/lib/python3/dist-packages/uaclient/security.py", line 1139, in _check_subscription_for_required_service if _prompt_for_enable(cfg, ent.name): File "/usr/lib/python3/dist-packages/uaclient/security.py", line 1118, in _prompt_for_enable cfg, File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 200, in new_f if cmd_args.format == "json" and not cmd_args.assume_yes: AttributeError: 'Namespace' object has no attribute 'format' ** Affects: ubuntu-advantage-tools (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Log file with stack trace" https://bugs.launchpad.net/bugs/1969809/+attachment/5582153/+files/UA-Bug.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969809 Title: ua fails if any package removed from server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1969809/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967037] [NEW] gnome-calculator crash during session login (misclassified?)
Public bug reported: Hi maintainers, It is likely this report is misclassified, but I haven't been able to trace it back to the real source. When I log into a gnome session, I see the following warning in the system log: Mar 29 21:54:01 thinkpad3 dbus-daemon[1476]: [session uid=1000 pid=1476] Activating service name='org.gnome.ControlCenter.SearchProvider' requeste> Mar 29 21:54:01 thinkpad3 dbus-daemon[1476]: [session uid=1000 pid=1476] Activating service name='org.gnome.Nautilus' requested by ':1.37' (uid=10> Mar 29 21:54:01 thinkpad3 dbus-daemon[1476]: [session uid=1000 pid=1476] Activating service name='org.gnome.Calculator.SearchProvider' requested b> Mar 29 21:54:01 thinkpad3 dbus-daemon[1476]: [session uid=1000 pid=1476] Activating service name='org.gnome.Calendar' requested by ':1.37' (uid=10> Mar 29 21:54:01 thinkpad3 dbus-daemon[1476]: [session uid=1000 pid=1476] Activating service name='org.gnome.Characters.BackgroundService' requeste> Mar 29 21:54:01 thinkpad3 dbus-daemon[1476]: [session uid=1000 pid=1476] Activating service name='org.gnome.seahorse.Application' requested by ':1> Mar 29 21:54:01 thinkpad3 dbus-daemon[1476]: [session uid=1000 pid=1476] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-ter> Mar 29 21:54:01 thinkpad3 systemd[1465]: Created slice apps.slice. Mar 29 21:54:01 thinkpad3 systemd[1465]: Created slice apps-org.gnome.Terminal.slice. Mar 29 21:54:01 thinkpad3 systemd[1465]: Starting GNOME Terminal Server... Mar 29 21:54:01 thinkpad3 dbus-daemon[1476]: [session uid=1000 pid=1476] Successfully activated service 'org.gnome.ControlCenter.SearchProvider' Mar 29 21:54:01 thinkpad3 dbus-daemon[1476]: [session uid=1000 pid=1476] Successfully activated service 'org.gnome.seahorse.Application' Mar 29 21:54:01 thinkpad3 dbus-daemon[776]: [system] Activating via systemd: service name='org.freedesktop.timedate1' unit='dbus-org.freedesktop.t> Mar 29 21:54:01 thinkpad3 systemd[1]: Starting Time & Date Service... Mar 29 21:54:01 thinkpad3 dbus-daemon[1476]: [session uid=1000 pid=1476] Successfully activated service 'org.gnome.Characters.BackgroundService' Mar 29 21:54:01 thinkpad3 dbus-daemon[1476]: [session uid=1000 pid=1476] Successfully activated service 'org.gnome.Terminal' Mar 29 21:54:01 thinkpad3 systemd[1465]: Started GNOME Terminal Server. Mar 29 21:54:01 thinkpad3 dbus-daemon[776]: [system] Successfully activated service 'org.freedesktop.timedate1' Mar 29 21:54:01 thinkpad3 systemd[1]: Started Time & Date Service. Mar 29 21:54:01 thinkpad3 dbus-daemon[1476]: [session uid=1000 pid=1476] Successfully activated service 'org.gnome.Calendar' Mar 29 21:54:01 thinkpad3 dbus-daemon[1476]: [session uid=1000 pid=1476] Successfully activated service 'org.gnome.Calculator.SearchProvider' Mar 29 21:54:01 thinkpad3 gnome-calculato[2141]: search-provider.vala:140: Failed to spawn Calculator: Child process killed by signal 9 I'm having trouble tracing what is going on here, other than there appears to be a segfault related to gnome-calculator. The following appears relevant: /usr/share/gnome-shell/search-providers/org.gnome.Calculator-search-provider.ini This may be related to https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1795399 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-calculator 1:3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-105.119-generic 5.4.174 Uname: Linux 5.4.0-105-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Mar 29 21:57:31 2022 InstallationDate: Installed on 2018-12-01 (1214 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-calculator UpgradeStatus: Upgraded to focal on 2021-12-14 (105 days ago) ** Affects: gnome-calculator (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967037 Title: gnome-calculator crash during session login (misclassified?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1967037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965684] [NEW] kubuntu 22.04 installer crash
Public bug reported: installer crashed on installing kubuntu 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubiquity 22.04.7 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.467 CurrentDesktop: KDE Date: Sun Mar 20 16:17:50 2022 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220320.1) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy kubuntu third-party-packages ubiquity-22.04.7 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965684 Title: kubuntu 22.04 installer crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1965684/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954965] Re: Need fwupd in focal to support Quectel's modem(EM120/160) firmware update
The package fwupd v1.7.5-3~20.04.1 in focal-proposed was tested.
This built package v1.7.5-3~20.04.1 can't let the modem's firmware to be
updated via modemmanager.
That is, "fwupdmgr get-devices" does not list the Quectel modem to be firmware
update supported on the tested machine.
The root cause is: the plugin code inside the fwupd is modemmanager version
dependent.
For ex., the following conditional compiled code will not be included if the
installed modemmanager version is less than the required version (> 1.17.1)
while building.
plugins/modem-manager/fu-mm-device.c:
static const MMModemFirmwareUpdateMethod supported_combinations[] = {
MM_MODEM_FIRMWARE_UPDATE_METHOD_FASTBOOT,
MM_MODEM_FIRMWARE_UPDATE_METHOD_QMI_PDC |
MM_MODEM_FIRMWARE_UPDATE_METHOD_FASTBOOT,
#if MM_CHECK_VERSION(1, 17, 1)
MM_MODEM_FIRMWARE_UPDATE_METHOD_MBIM_QDU,
#endif /* MM_CHECK_VERSION(1,17,1) */
#if MM_CHECK_VERSION(1, 17, 2)
MM_MODEM_FIRMWARE_UPDATE_METHOD_FIREHOSE,
#endif
};
The Quectel modem requires the method MM_MODEM_FIRMWARE_UPDATE_METHOD_FIREHOSE
to be supported.
Currently, the latest version of modemmanager in Focal is 1.16.6-2~20.04.1 .
If the modemmanager is upgraded to the required versions, we might
request for a no-change-rebuild SRU in focal.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1954965
Title:
Need fwupd in focal to support Quectel's modem(EM120/160) firmware
update
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1954965/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955500] Re: firefox crashes often
I do still get pretty regular crashes. I will have to check with extensions disabled. Disabling adblocking is pretty painful. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955500 Title: firefox crashes often To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1955500/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954965] Re: Need fwupd in focal to support Quectel's modem(EM120/160) firmware update
I have not found new version of fwupd in focal-proposed. It looks like there is some issued in LP#1949412 so the package is removed ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954965 Title: Need fwupd in focal to support Quectel's modem(EM120/160) firmware update To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1954965/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955797] Re: [SRU] network-manager can’t modify MTU automatically based on what ModemManager exposes for WWAN modems.
** Description changed: [Impact] Some 4G/5G mobile networks(for ex., AT) requires a specific MTU setting, this setting will be exposed by the ModemManager for network- manger to configure the MTU of the modem network interface . - The current modem-manager v1.22.10-1ubuntu2.2 in focal can’t pass + The current network-manager v1.22.10-1ubuntu2.2 in focal can’t pass AT’s modem system certification. [Fix] This upstream patch can resolve this bug: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/499/diffs?commit_id=212758ea05a4c13d65f36b55c90aee7919642631 [Test Plan] 1. Use a Lenovo platform SE30 including 4G Quectel EM160 modem and an AT SIM card in US 2. Enable 4G modem and connect to AT apn $ sudo mmcli -i 0 --pin= $ sudo mmcli --modem 0 --enable $ sudo mmcli -m 0 --simple-connect="pin=,apn=emome" $ sudo nmcli radio wwan on $ sudo nmcli connection add type gsm ifname wwan0p2MBIM con-name mymodem apn emome $ sudo nmcli connection up id mymodem 3. Check if the MTU got from the following results are the same: $ sudo mmcli --bearer 5 | mtu $ ifconfig mhi_mbim0 | grep mtu * Expected result: Both MTUs are the same value 1430 * Actual tested result: Different values (one is 1430 , another is 1500) [Where problems could occur] Very low. This is a simple fix: network-manager gets the MTU from the ModemManager then sets the MTU of the modem interface. [Other info] 1. Network-manager v1.30.0-1ubuntu3 in hirsute has included the fix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955797 Title: [SRU] network-manager can’t modify MTU automatically based on what ModemManager exposes for WWAN modems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1955797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951586] Re: Need option to specify wifi regulatory domain
``` The assumption from the kernel side seems to be that persisting this is "something for the desktop to handle", which seems pretty sensible given that one of the queries in almost any desktop setup (including ours) is "where are you?" from which we derive the timezone but could equally derive the regulatory region (I note we don't currently appear to -- perhaps this bug should affect ubiquity too?). ``` This rings a bell, working from memory with wireshark I think NetworkManager does a double connect, first to grab the country code then the actual wpa_supplicant/dhcp exchange. Dan Williams would be the one to ask. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951586 Title: Need option to specify wifi regulatory domain To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1951586/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951586] Re: Need option to specify wifi regulatory domain
While I have your ear can I suggest adding rng-tools, fake-hwclock, and haveged to the RPi images please. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951586 Title: Need option to specify wifi regulatory domain To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1951586/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951586] Re: Need option to specify wifi regulatory domain
My understanding is that only wpa_supplicant and iw are able to set the regdb country code. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951586 Title: Need option to specify wifi regulatory domain To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1951586/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955797] Re: [SRU] network-manager can’t modify MTU automatically based on what ModemManager exposes for WWAN modems.
** Attachment added: "Verification report" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1955797/+attachment/5556131/+files/SRU%20for%20network-manager%28verify%20report%29%20.pdf ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955797 Title: [SRU] network-manager can’t modify MTU automatically based on what ModemManager exposes for WWAN modems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1955797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955797] Re: [SRU] network-manager can’t modify MTU automatically based on what ModemManager exposes for WWAN modems.
Test passed with Lenovo ThinkEdge SE30(11ND) on Focal: * The version of the packages tested: network-manager: 1.22.10-1ubuntu2. 3 The detail testing procedure and result is provided as the attached file : "SRU for network-manager(verify report).pdf" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955797 Title: [SRU] network-manager can’t modify MTU automatically based on what ModemManager exposes for WWAN modems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1955797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954965] Re: Need fwupd in focal to support Quectel's modem(EM120/160) firmware update
@YC The customer confirmed that fwupd >= 1.7.1 is good enough. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954965 Title: Need fwupd in focal to support Quectel's modem(EM120/160) firmware update To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1954965/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956977] [NEW] ubuntu dock causes gnome-shell keysym warnings
Public bug reported: Hi devs, I was disabling gnome-shell extensions to try to narrow down a different problem and discovered this one. The log snippet below appears from time to time in my logs, but I've never known where it comes from. I had disabled Ubuntu Dock and most other extensions. I didn't like it off and turned it back on while following the log and saw another instance of this. I verified that on my system, activating Dock causes gnome-shell to print these warnings: Jan 10 11:13:43 cerberus gnome-shell[2987]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). Jan 10 11:13:43 cerberus gnome-shell[2987]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). Jan 10 11:13:43 cerberus gnome-shell[2987]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). Jan 10 11:13:43 cerberus gnome-shell[2987]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). Jan 10 11:13:43 cerberus gnome-shell[2987]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). Jan 10 11:13:43 cerberus gnome-shell[2987]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). Jan 10 11:13:43 cerberus gnome-shell[2987]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). Jan 10 11:13:43 cerberus gnome-shell[2987]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). Jan 10 11:13:43 cerberus gnome-shell[2987]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). It may be a gnome-shell bug, but this seems like the starting place to report. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-ubuntu-dock 68ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151 Uname: Linux 5.4.0-91-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jan 10 11:16:41 2022 InstallationDate: Installed on 2020-05-29 (590 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: Upgraded to focal on 2020-11-04 (432 days ago) mtime.conffile..etc.apport.crashdb.conf: 2021-06-21T20:18:54.448530 ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956977 Title: ubuntu dock causes gnome-shell keysym warnings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1956977/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955797] Re: [SRU] network-manager can’t modify MTU automatically based on what ModemManager exposes for WWAN modems.
Hi Lukasz, Carrier network providers use bearer information to carry the MTU setting, this can be received by the modem then exposed to its host system either via NetworkManager's ipv4_config or ipv6_config. I think ipv4_config is the must supported setting in carrier's network, that may be why this upstream patch has not considered ipv6_config. (MTU should be the same(per device) for both ipv4 and ipv6) Our customer has used this patch in the field testing and this patch worked as expected. There should be no concern to get MTU only via ipv4_config. Thanks for highlight this question. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955797 Title: [SRU] network-manager can’t modify MTU automatically based on what ModemManager exposes for WWAN modems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1955797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956714] [NEW] gui took long time to return from blank screen
Public bug reported: I ignored my system for a while, long enough for the screensaver to blank the screen. When I tried to get it to awake ( I don't need to log back in), it seemed to be semihung, showing pretty black screen, but a mouse cursor visible. It did not respond to hitting keys. I tried switching back and forth between VT1 and VT2 to get it to come back to life. Eventually it came back on its own, but it took too long. Here's a chunk of log from the time this happened. There are on the order of 2000 of the "maximum number of pending replies" messages that you see at the end of this log snippet. Jan 06 23:52:41 cerberus gsd-power[2252]: Error setting property 'PowerSaveMode' on interface org.gnome.Mutter.DisplayConfig: Timeout was reached (g-io-error-quark, 24) Jan 06 23:52:51 cerberus gvfsd[2276168]: Error 2: PTP Layer error 02ff: Error getting friendlyname. Jan 06 23:52:51 cerberus gvfsd[2276168]: Error 2: Error 02ff: PTP I/O Error Jan 06 23:52:51 cerberus gnome-shell[2987]: [System monitor] applet enabling done Jan 06 23:52:51 cerberus gnome-shell[2987]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed Jan 06 23:52:51 cerberus gnome-shell[2987]: cr_declaration_parse_list_from_buf: assertion 'parser' failed Jan 06 23:52:51 cerberus gsd-power[3176]: Error setting property 'PowerSaveMode' on interface org.gnome.Mutter.DisplayConfig: Timeout was reached (g-io-error-quark, 24) Jan 06 23:52:51 cerberus gnome-shell[2987]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed Jan 06 23:52:51 cerberus gnome-shell[2987]: cr_declaration_parse_list_from_buf: assertion 'parser' failed Jan 06 23:52:51 cerberus gnome-shell[2987]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed Jan 06 23:52:51 cerberus gnome-shell[2987]: cr_declaration_parse_list_from_buf: assertion 'parser' failed Jan 06 23:52:51 cerberus gnome-shell[2987]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed Jan 06 23:52:51 cerberus gnome-shell[2987]: cr_declaration_parse_list_from_buf: assertion 'parser' failed Jan 06 23:52:51 cerberus gnome-shell[2987]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed Jan 06 23:52:51 cerberus gnome-shell[2987]: cr_declaration_parse_list_from_buf: assertion 'parser' failed Jan 06 23:52:52 cerberus dbus-daemon[1439]: [system] The maximum number of pending replies for ":1.2990" (uid=1000 pid=2987 comm="/usr/bin/gnome-shell " label="unconfined") has been > Jan 06 23:52:52 cerberus dbus-daemon[1439]: [system] The maximum number of pending replies for ":1.2990" (uid=1000 pid=2987 comm="/usr/bin/gnome-shell " label="unconfined") has been > Jan 06 23:52:52 cerberus dbus-daemon[1439]: [system] The maximum number of pending replies for ":1.2990" (uid=1000 pid=2987 comm="/usr/bin/gnome-shell " label="unconfined") has been > Jan 06 23:52:52 cerberus dbus-daemon[1439]: [system] The maximum number of pending replies for ":1.2990" (uid=1000 pid=2987 comm="/usr/bin/gnome-shell " label="unconfined") has been > Jan 06 23:52:52 cerberus dbus-daemon[1439]: [system] The maximum number of pending replies for ":1.2990" (uid=1000 pid=2987 comm="/usr/bin/gnome-shell " label="unconfined") has been > ... Jan 06 23:52:52 cerberus dbus-daemon[1439]: [system] The maximum number of pending replies for ":1.7" (uid=0 pid=1440 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")> Jan 06 23:52:52 cerberus dbus-daemon[1439]: [system] The maximum number of pending replies for ":1.7" (uid=0 pid=1440 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")> Jan 06 23:52:52 cerberus dbus-daemon[1439]: [system] The maximum number of pending replies for ":1.7" (uid=0 pid=1440 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")> Jan 06 23:52:52 cerberus dbus-daemon[1439]: [system] The maximum number of pending replies for ":1.7" (uid=0 pid=1440 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")> Jan 06 23:52:52 cerberus gnome-shell[2987]: Error checking authorization for action id org.freedesktop.bolt.enroll: GDBus.Error:org.freedesktop.DBus.Error.LimitsExceeded: The maximum> Jan 06 23:52:52 cerberus gnome-shell[2987]: Error checking authorization for action id org.freedesktop.packagekit.trigger-offline-update: GDBus.Error:org.freedesktop.DBus.Error.Limit> Jan 06 23:52:52 cerberus dbus-daemon[1439]: [system] The maximum number of pending replies for ":1.7" (uid=0 pid=1440 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")> ... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151 Uname: Linux 5.4.0-91-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 7 00:00:52 2022 DisplayManager: gdm3 InstallationDate: Installed on 2020-05-29 (587 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64
[Bug 1955797] Re: [SRU] network-manager can’t modify MTU automatically based on what ModemManager exposes for WWAN modems.
The .debdiff file “network-manager_1-1.22.10-1ubuntu2.3-focal.debdiff” is attached for focal(20.04). ** Description changed: [Impact] Some 4G/5G mobile networks(for ex., AT) requires a specific MTU setting, this setting will be exposed by the ModemManager for network- manger to configure the MTU of the modem network interface . The current modem-manager v1.22.10-1ubuntu2.2 in focal can’t pass AT’s modem system certification. [Fix] This upstream patch can resolve this bug: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/499/diffs?commit_id=212758ea05a4c13d65f36b55c90aee7919642631 [Test Plan] 1. Use a Lenovo platform SE30 including 4G Quectel EM160 modem and an AT SIM card in US 2. Enable 4G modem and connect to AT apn $ sudo mmcli -i 0 --pin= $ sudo mmcli --modem 0 --enable $ sudo mmcli -m 0 --simple-connect="pin=,apn=emome" $ sudo nmcli radio wwan on $ sudo nmcli connection add type gsm ifname wwan0p2MBIM con-name mymodem apn emome $ sudo nmcli connection up id mymodem 3. Check if the MTU got from the following results are the same: $ sudo mmcli --bearer 5 | mtu $ ifconfig mhi_mbim0 | grep mtu - * Expected result: - Both MTUs are the same value 1430 - * Actual tested result: - Different values (one is 1430 , another is 1500) + * Expected result: + Both MTUs are the same value 1430 + * Actual tested result: + Different values (one is 1430 , another is 1500) [Where problems could occur] Very low. This is a simple fix: network-manager gets the MTU from the ModemManager then sets the MTU of the modem interface. [Other info] - $ lsb_release -rd - Description: Ubuntu 20.04.3 LTS - Release: 20.04 + 1. Network-manager v1.30.0-1ubuntu3 in hirsute has included the fix. ** Patch added: ".debdiff for focal" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1955797/+attachment/5549698/+files/network-manager_1-1.22.10-1ubuntu2.3-focal.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955797 Title: [SRU] network-manager can’t modify MTU automatically based on what ModemManager exposes for WWAN modems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1955797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955797] [NEW] [SRU] network-manager can’t modify MTU automatically based on what ModemManager exposes for WWAN modems.
Public bug reported: [Impact] Some 4G/5G mobile networks(for ex., AT) requires a specific MTU setting, this setting will be exposed by the ModemManager for network- manger to configure the MTU of the modem network interface . The current modem-manager v1.22.10-1ubuntu2.2 in focal can’t pass AT’s modem system certification. [Fix] This upstream patch can resolve this bug: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/499/diffs?commit_id=212758ea05a4c13d65f36b55c90aee7919642631 [Test Plan] 1. Use a Lenovo platform SE30 including 4G Quectel EM160 modem and an AT SIM card in US 2. Enable 4G modem and connect to AT apn $ sudo mmcli -i 0 --pin= $ sudo mmcli --modem 0 --enable $ sudo mmcli -m 0 --simple-connect="pin=,apn=emome" $ sudo nmcli radio wwan on $ sudo nmcli connection add type gsm ifname wwan0p2MBIM con-name mymodem apn emome $ sudo nmcli connection up id mymodem 3. Check if the MTU got from the following results are the same: $ sudo mmcli --bearer 5 | mtu $ ifconfig mhi_mbim0 | grep mtu * Expected result: Both MTUs are the same value 1430 * Actual tested result: Different values (one is 1430 , another is 1500) [Where problems could occur] Very low. This is a simple fix: network-manager gets the MTU from the ModemManager then sets the MTU of the modem interface. [Other info] $ lsb_release -rd Description:Ubuntu 20.04.3 LTS Release:20.04 ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955797 Title: [SRU] network-manager can’t modify MTU automatically based on what ModemManager exposes for WWAN modems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1955797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955500] Re: firefox crashes often
2 more crashes today -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955500 Title: firefox crashes often To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1955500/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862760] Re: Unreliable 802.11ac connection on our raspi images
https://bugs.launchpad.net/netplan/+bug/1951586 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862760 Title: Unreliable 802.11ac connection on our raspi images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1862760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951586] Re: Need option to specify wifi regulatory domain
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1862760 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951586 Title: Need option to specify wifi regulatory domain To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1951586/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955500] [NEW] firefox crashes often
Public bug reported: Recently (since ~2021-12-15) firefox has been crashing a lot, often daily. There's no obvious pattern that I can see. Most recent crash logs: Dec 21 12:37:51 cerberus firefox.desktop[755990]: Sandbox: Unexpected EOF, op 0 flags 0200 path /proc/755990/cgroup Dec 21 12:37:51 cerberus firefox.desktop[756121]: Exiting due to channel error. Dec 21 12:37:51 cerberus firefox.desktop[755809]: Exiting due to channel error. Dec 21 12:37:51 cerberus firefox.desktop[755990]: Exiting due to channel error. ... Dec 21 12:37:51 cerberus firefox.desktop[745228]: [GFX1-]: Receive IPC close with reason=AbnormalShutdown Dec 21 12:37:51 cerberus firefox.desktop[744870]: Exiting due to channel error. ... Previous crash: Dec 20 12:56:53 cerberus kernel: traps: GeckoMain[613052] trap int3 ip:7fa351cc1295 sp:7fff6ba7eea0 error:0 in libglib-2.> Dec 20 12:56:53 cerberus gnome-shell[722119]: Exiting due to channel error. Dec 20 12:56:53 cerberus gnome-shell[722386]: Exiting due to channel error. Dec 20 12:56:53 cerberus gnome-shell[615970]: Exiting due to channel error. Dec 20 12:56:53 cerberus gnome-shell[717612]: Exiting due to channel error. ... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 95.0.1+build2-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151 Uname: Linux 5.4.0-91-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: jlquinn2641 F pulseaudio /dev/snd/controlC0: jlquinn2641 F pulseaudio /dev/snd/controlC2: jlquinn2641 F pulseaudio /dev/snd/controlC1: jlquinn2641 F pulseaudio BuildID: 20211215221728 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Tue Dec 21 13:17:24 2021 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:363 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2020-05-29 (570 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IpRoute: default via 192.168.1.1 dev enp4s0 proto dhcp metric 100 169.254.0.0/16 dev enp4s0 scope link metric 1000 192.168.1.0/24 dev enp4s0 proto kernel scope link src 192.168.1.10 metric 100 MostRecentCrashID: bp-6d5c31fc-1b33-459b-bfab-9d3b20211216 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so Profile1PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:363 Profile1PrefSources: prefs.js Profile1Themes: extensions.sqlite corrupt or missing Profiles: Profile1 - LastVersion=54.0/20170612122310 (Out of date) Profile0 (Default) - LastVersion=95.0.1/20211215221728 (In use) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: Upgraded to focal on 2020-11-04 (412 days ago) dmi.bios.date: 12/16/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X10DAI dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To be filled by O.E.M. dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.2:bd12/16/2019:svnSupermicro:pnX10DAi:pvr123456789:rvnSupermicro:rnX10DAI:rvr1.01:cvnTobefilledbyO.E.M.:ct3:cvrTobefilledbyO.E.M.: dmi.product.family: SMC X10 dmi.product.name: X10DAi dmi.product.sku: 083615D9 dmi.product.version: 123456789 dmi.sys.vendor: Supermicro mtime.conffile..etc.apport.crashdb.conf: 2021-06-21T20:18:54.448530 ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955500 Title: firefox crashes often To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1955500/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955500] Re: firefox crashes often
I have as extensions: Feedbro GNOME Shell Integration (courtesy of ubuntu) Stylus uBlock Origin -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955500 Title: firefox crashes often To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1955500/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946096] Re: Support manual firmware upgrading for Foxconn and Quectel modems.
** Changed in: oem-priority Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946096 Title: Support manual firmware upgrading for Foxconn and Quectel modems. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1901470] Re: [i915] HDMI monitor's native resolution (EDID detailed mode) not available, defaults to 1080p instead
Hi Daniel, Thanks for the help and the quick response. I don't see any marking on the HDMI cable I'm using so I'm guessing it isn't one a high quality one. So, I played around with the refresh rates and got it to work at a lower refresh rate: xrandr --addmode HDMI-2 2560x1440_24.00 xrandr --output HDMI-2 --mode 2560x1440_24.00 xrandr --newmode "2560x1440_24.00" 113.75 2560 2648 2904 3248 1440 1443 1448 1463 -hsync +vsync This ties in with the poor quality cable idea. Thanks again for the assistance, Jerry. On Wed, Dec 15, 2021 at 3:00 AM Daniel van Vugt <1901...@bugs.launchpad.net> wrote: > I'm guessing a common cause of this bug is low quality HDMI cables. If > you're stuck at 1080p then that suggests the cable is only HDMI 1.2. To > achieve 1440p at 60Hz you will need an HDMI 1.4 cable. And to achieve > 2160p (4K) at 60Hz you will need an HDMI 2.0 cable AND a modern GPU to > plug it into. 3K and 5K requirements are somewhere in the middle > depending on the vertical resolution of the monitor. > > > https://en.wikipedia.org/wiki/HDMI#Refresh_frequency_limits_for_standard_video > > If you're shopping for a new monitor then it's best to find one with > DisplayPort (or USB-C) which doesn't have quite as severe limitations as > HDMI does. > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1954840). > https://bugs.launchpad.net/bugs/1901470 > > Title: > [i915] HDMI monitor's native resolution (EDID detailed mode) not > available, defaults to 1080p instead > > Status in linux package in Ubuntu: > Confirmed > Status in linux-hwe-5.11 package in Ubuntu: > Confirmed > > Bug description: > The PG278QR monitor supports 2560x1440. After installing Ubuntu 20.4, > the max resolution presented in the Settings app is 1920x1080, and > this resolution is the one that it uses. Switching between the Nvidia > driver or the Intel driver (laptop has low-power intel gpu too) > doesn't correct the problem. > > Digging in deeper, based on > > https://wiki.ubuntu.com/X/Troubleshooting/Resolution#Problem:__Wrong_resolutions.2C_refresh_rates.2C_or_monitor_specs > > Under Wrong resolutions/refresh rates/or monitor specs, step 3 is to > use get-edid | parse-edid. > > After applying the mode that I wanted manually via xrandr --newmode > and xrandr --addmode, I was able to select the max resolution of the > monitor and works correctly, until reboot. I will add it to my > xorg.conf next. > > Here is information I collected: > > output from xrandr after fresh boot: > > ~$ xrandr > Screen 0: minimum 8 x 8, current 3840 x 1080, maximum 32767 x 32767 > eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x > axis y axis) 344mm x 193mm > 1920x1080 60.01*+ 60.0159.9759.9659.93 > 1680x1050 59.9559.88 > 1600x1024 60.17 > 1400x1050 59.98 > 1600x900 59.9959.9459.9559.82 > 1280x1024 60.02 > 1440x900 59.89 > 1400x900 59.9659.88 > 1280x960 60.00 > 1440x810 60.0059.97 > 1368x768 59.8859.85 > 1360x768 59.8059.96 > 1280x800 59.9959.9759.8159.91 > 1152x864 60.00 > 1280x720 60.0059.9959.8659.74 > 1024x768 60.0460.00 > 960x720 60.00 > 928x696 60.05 > 896x672 60.01 > 1024x576 59.9559.9659.9059.82 > 960x600 59.9360.00 > 960x540 59.9659.9959.6359.82 > 800x600 60.0060.3256.25 > 840x525 60.0159.88 > 864x486 59.9259.57 > 800x512 60.17 > 700x525 59.98 > 800x450 59.9559.82 > 640x512 60.02 > 720x450 59.89 > 700x450 59.9659.88 > 640x480 60.0059.94 > 720x405 59.5158.99 > 684x384 59.8859.85 > 680x384 59.8059.96 > 640x400 59.8859.98 > 576x432 60.06 > 640x360 59.8659.8359.8459.32 > 512x384 60.00 > 512x288 60.0059.92 > 480x270 59.6359.82 > 400x300 60.3256.34 > 432x243 59.9259.57 > 320x240 60.05 > 360x202 59.5159.13 > 320x180 59.8459.32 > HDMI-1-1 connected 1920x1080+1920+0 (normal left inverted right x axis y > axis) 598mm x 336mm > 1920x1080 60.00* 50.0059.94 > 1280x720 60.0050.0059.94 > 1024x768 60.00 > 800x600
[Bug 1954840] [NEW] Unabke to set Display to max resolution supported by Monitor and laptop
Public bug reported: Hi, my secondary display support 2560*1440 but 'Display' in Ubuntu is presenting a max resolution of 2048*1080. The max resolution was working yesterday, I think I performed a update today and it has stopped working after that. Thanks, Jerry, ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Dec 14 19:52:57 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:504a] InstallationDate: Installed on 2021-04-16 (242 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20F5S2BL00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-41-generic root=UUID=5cb08771-ead9-4f2c-9550-4125931d1f4a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/09/2019 dmi.bios.release: 1.45 dmi.bios.vendor: LENOVO dmi.bios.version: R02ET72W (1.45 ) dmi.board.asset.tag: Not Available dmi.board.name: 20F5S2BL00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 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.15 dmi.modalias: dmi:bvnLENOVO:bvrR02ET72W(1.45):bd10/09/2019:br1.45:efr1.15:svnLENOVO:pn20F5S2BL00:pvrThinkPadX260:skuLENOVO_MT_20F5_BU_Think_FM_ThinkPadX260:rvnLENOVO:rn20F5S2BL00:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X260 dmi.product.name: 20F5S2BL00 dmi.product.sku: LENOVO_MT_20F5_BU_Think_FM_ThinkPad X260 dmi.product.version: ThinkPad X260 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954840 Title: Unabke to set Display to max resolution supported by Monitor and laptop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1954840/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946096] Re: Support manual firmware upgrading for Foxconn and Quectel modems.
Regression test results: (1) Test passed with Lenovo T14s (Tiger-2) on Hirsute: * The version of the packages tested: ModemManager: 1.16.6-2~21.04.1 (2) Test passed with Lenovo X13 AMD (Servel-AMD-1) on Focal: * The version of the packages tested: ModemManager: 1.16.6-2~20.04.1 The detail testing procedure and result is provided as the attached file : "RegressionTestReportFor-proposedPackages-1946096.pdf" ** Attachment added: "RegressionTestReportFor-proposedPackages-1946096.pdf" https://bugs.launchpad.net/oem-priority/+bug/1946096/+attachment/5545834/+files/RegressionTestReportFor-proposedPackages-1946096.pdf.pdf ** Tags removed: verification-needed-focal verification-needed-hirsute ** Tags added: verification-done-focal verification-done-hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946096 Title: Support manual firmware upgrading for Foxconn and Quectel modems. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946096] Re: Support manual firmware upgrading for Foxconn and Quectel modems.
(1) Test passed with Lenovo ThinkEdge SE30(11ND) and Lenovo ThinkEdge SE30(11NE) on Hirsute: * The version of the packages tested: ModemManager: 1.16.6-2~21.04.1 (2) Test passed with Lenovo ThinkEdge SE30(11ND) and Lenovo ThinkEdge SE30(11NE) on Focal: * The version of the packages tested: ModemManager: 1.16.6-2~20.04.1 The detail testing procedure and result is provided as the attached file : "TestReportForHirsuteAndFocal-proposed-1946096.pdf" The regression test report will be provided. ** Attachment added: "TestReportForHirsuteAndFocal-proposed-1946096.pdf" https://bugs.launchpad.net/oem-priority/+bug/1946096/+attachment/5545449/+files/TestReportForHirsuteAndFocal-proposed-1946096.pdf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946096 Title: Support manual firmware upgrading for Foxconn and Quectel modems. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946096] Re: Support manual firmware upgrading for Foxconn and Quectel modems.
** Description changed: [Impact] The modem certification requires that different modem firmware is used for different network carrier. This needs the firmware upgrading capability during the modem certification process. The modem manufacture vendors (Foxconn and Quectel) provided utilities to do modem's firmware upgrading manually.(LP#1943774, LP#1943780) These utilities are verified to be working when the recent versions(> v 1.18.2) of ModemManager are used with. To support manual firmware upgrading on the current Focal release which is using ModemManager v 1.16.6, we need to apply some patches from v 1.18.2. The requested upstream patches are listed as below: * for Quectel EM160 4G ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/83ac82470589a3672092a0ba0be855093b1cf5e2 * for Foxconn T99W175 ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/21ae558fe3600c84b3ca7dcd9bf50a3ba576c7c9 **https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/76e700f4fd703f952208993330ab098305c13d6b ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/52bf2c641171ded9e617022f40497c8984520371 ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/33e2b023ef01bea9da37ae2beb192f7d92bce47a ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/f72046701659073fbfa97516e155865647acb154 The firmware upgrading was verified using the patched ModemManager v 1.16.6 with the following 2 modems: * Foxconn SDX55 T99W175 5G sub6 PCIE Modem * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem [Test Plan] 1. Install the Ubuntu image. 2. Boot and login the system. - 3. Prepare the modem’s firmware and install the firmware upgrading application provided by Foxconn and Quectel - 4. Using the firmware upgrading application to upgrade the modem’s firmware - 5. Verify if the modem’s firmware upgrading is successful - 6. Reboot - 7. Verify if the upgraded modem firmware is still working + 3. Verify if the modem is working + 4. Prepare the modem’s firmware and install the firmware upgrading application provided by Foxconn and Quectel + 5. Using the firmware upgrading application to upgrade the modem’s firmware + 6. Verify if the modem’s firmware upgrading is successful + 7. Reboot + 8. Verify if the upgraded modem firmware is still working --- Regression test --- Verify if one USB modem are still working with these patches for PCIe modems. [Where problems could occur] The requested update has 2 parts: 1. Informative 1.1 Provide more information about modems whose drivers use WWAN subsystem in kernel 5.13 1.2 Modem manufacture's private utilities can use this information to do modem's FW upgrading manually 2. Changes are specific to Foxconn and Quectel modems 2.1 Modified code are only used by Foxconn and Quectel modems during their FW upgrading. (matched by vendor_id and product_id) In current Ubuntu's certification records for modem: * No other modem uses WWAN subsystem in kernel 5.13 * Modem's FW update is not supported via ModemManager ( < v1.18 ) There is no certificated modems can do the firmware upgrading flow for the regression test. This update should not affect existing modems. The problem would be limited to these two mentioned modems. Each carrier mapping .conf file is for a specific modem. ModemManager will load one of the carrier mapping conf files via the modem manufacturer’s plugin ( if the PCIe VID & PID is matched by the plugin.) We cannot verify if the carrier mapping is correct. This relies on the manufacturer to provide the correct mapping. The carrier mapping .conf files is verified by modem’s manufacture according to the tested SIM card published by different countries. Modem manufacturer confirmed that the content in the .conf file is absolutely correct. [Other Info] The firmware and the upgrading utilities can be downloaded from the following link: * LP#1943774 for Quectel modems * LP#1943780 for Foxconn modems -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946096 Title: Support manual firmware upgrading for Foxconn and Quectel modems. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946096] Re: Support manual firmware upgrading for Foxconn and Quectel modems.
The .debdiff file “modemmanager_1-1.16.6-2~21.10.1-impish.debdiff” is attached for impish(21.10). ** Patch added: "modemmanager_1-1.16.6-2~21.10.1-impish.debdiff" https://bugs.launchpad.net/oem-priority/+bug/1946096/+attachment/5544543/+files/modemmanager_1-1.16.6-2~21.10.1-impish.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946096 Title: Support manual firmware upgrading for Foxconn and Quectel modems. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946096] Re: Support manual firmware upgrading for Foxconn and Quectel modems.
The "01_modem-quectel.patch" extends the quectel:plugin to provide firmware setting status during the FW upgrading process. EM120/160 PCIe modules have been already supported without this patch. I got the confirmation from Quectel engineers about the above. For the regression test, we found 2 laptops having Quectel USB modems and did the test on these laptops. The Quectel USB modems worked with the patched ModemManager. The regression test report is attached here: "RegressionTestReport_ EM05-CE.pdf". ** Description changed: [Impact] The modem certification requires that different modem firmware is used for different network carrier. This needs the firmware upgrading capability during the modem certification process. The modem manufacture vendors (Foxconn and Quectel) provided utilities to do modem's firmware upgrading manually.(LP#1943774, LP#1943780) These utilities are verified to be working when the recent versions(> v 1.18.2) of ModemManager are used with. To support manual firmware upgrading on the current Focal release which is using ModemManager v 1.16.6, we need to apply some patches from v 1.18.2. The requested upstream patches are listed as below: * for Quectel EM160 4G ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/83ac82470589a3672092a0ba0be855093b1cf5e2 * for Foxconn T99W175 ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/21ae558fe3600c84b3ca7dcd9bf50a3ba576c7c9 **https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/76e700f4fd703f952208993330ab098305c13d6b ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/52bf2c641171ded9e617022f40497c8984520371 ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/33e2b023ef01bea9da37ae2beb192f7d92bce47a ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/f72046701659073fbfa97516e155865647acb154 The firmware upgrading was verified using the patched ModemManager v 1.16.6 with the following 2 modems: * Foxconn SDX55 T99W175 5G sub6 PCIE Modem * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem [Test Plan] 1. Install the Ubuntu image. 2. Boot and login the system. 3. Prepare the modem’s firmware and install the firmware upgrading application provided by Foxconn and Quectel 4. Using the firmware upgrading application to upgrade the modem’s firmware 5. Verify if the modem’s firmware upgrading is successful 6. Reboot 7. Verify if the upgraded modem firmware is still working + --- Regression test --- + + Verify if one USB modem are still working with these patches for PCIe + modems. + [Where problems could occur] The requested update has 2 parts: 1. Informative 1.1 Provide more information about modems whose drivers use WWAN subsystem in kernel 5.13 1.2 Modem manufacture's private utilities can use this information to do modem's FW upgrading manually 2. Changes are specific to Foxconn and Quectel modems 2.1 Modified code are only used by Foxconn and Quectel modems during their FW upgrading. (matched by vendor_id and product_id) In current Ubuntu's certification records for modem: * No other modem uses WWAN subsystem in kernel 5.13 * Modem's FW update is not supported via ModemManager ( < v1.18 ) There is no certificated modems can do the firmware upgrading flow for the regression test. This update should not affect existing modems. The problem would be limited to these two mentioned modems. Each carrier mapping .conf file is for a specific modem. ModemManager will load one of the carrier mapping conf files via the modem manufacturer’s plugin ( if the PCIe VID & PID is matched by the plugin.) We cannot verify if the carrier mapping is correct. This relies on the manufacturer to provide the correct mapping. - The carrier mapping .conf files is verified by modem’s manufacture according to the tested SIM card published by different countries. - Modem manufacturer confirmed that the content in the .conf file is absolutely correct. - + The carrier mapping .conf files is verified by modem’s manufacture according to the tested SIM card published by different countries. + Modem manufacturer confirmed that the content in the .conf file is absolutely correct. [Other Info] The firmware and the upgrading utilities can be downloaded from the following link: * LP#1943774 for Quectel modems * LP#1943780 for Foxconn modems ** Attachment added: "USB modem regression test" https://bugs.launchpad.net/oem-priority/+bug/1946096/+attachment/5544542/+files/RegressionTestReport_%20EM05-CE.pdf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946096 Title: Support manual firmware upgrading for Foxconn and Quectel modems. To manage notifications about this bug go to:
[Bug 1946096] Re: Support manual firmware upgrading for Foxconn and Quectel modems.
Hello, is there anything needs me to provide for moving to the next step? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946096 Title: Support manual firmware upgrading for Foxconn and Quectel modems. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946096] Re: Support manual firmware upgrading for Foxconn and Quectel modems.
[Where problems could occur] is updated ** Description changed: [Impact] The modem certification requires that different modem firmware is used for different network carrier. This needs the firmware upgrading capability during the modem certification process. The modem manufacture vendors (Foxconn and Quectel) provided utilities to do modem's firmware upgrading manually.(LP#1943774, LP#1943780) These utilities are verified to be working when the recent versions(> v 1.18.2) of ModemManager are used with. To support manual firmware upgrading on the current Focal release which is using ModemManager v 1.16.6, we need to apply some patches from v 1.18.2. The requested upstream patches are listed as below: * for Quectel EM160 4G ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/83ac82470589a3672092a0ba0be855093b1cf5e2 * for Foxconn T99W175 ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/21ae558fe3600c84b3ca7dcd9bf50a3ba576c7c9 **https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/76e700f4fd703f952208993330ab098305c13d6b ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/52bf2c641171ded9e617022f40497c8984520371 ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/33e2b023ef01bea9da37ae2beb192f7d92bce47a ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/f72046701659073fbfa97516e155865647acb154 The firmware upgrading was verified using the patched ModemManager v 1.16.6 with the following 2 modems: * Foxconn SDX55 T99W175 5G sub6 PCIE Modem * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem [Test Plan] 1. Install the Ubuntu image. 2. Boot and login the system. 3. Prepare the modem’s firmware and install the firmware upgrading application provided by Foxconn and Quectel 4. Using the firmware upgrading application to upgrade the modem’s firmware 5. Verify if the modem’s firmware upgrading is successful 6. Reboot 7. Verify if the upgraded modem firmware is still working [Where problems could occur] The requested update has 2 parts: 1. Informative -1.1 Provide more information about modems whose drivers use WWAN subsystem in kernel 5.13 -1.2 Modem manufacture's private utilities can use this information to do modem's FW upgrading manually + 1.1 Provide more information about modems whose drivers use WWAN subsystem in kernel 5.13 + 1.2 Modem manufacture's private utilities can use this information to do modem's FW upgrading manually 2. Changes are specific to Foxconn and Quectel modems -2.1 Modified code are only used by Foxconn and Quectel modems during their FW upgrading. (matched by vendor_id and product_id) + 2.1 Modified code are only used by Foxconn and Quectel modems during their FW upgrading. (matched by vendor_id and product_id) In current Ubuntu's certification records for modem: * No other modem uses WWAN subsystem in kernel 5.13 * Modem's FW update is not supported via ModemManager ( < v1.18 ) There is no certificated modems can do the firmware upgrading flow for the regression test. This update should not affect existing modems. + The problem would be limited to these two mentioned modems. + Each carrier mapping .conf file is for a specific modem. + ModemManager will load one of the carrier mapping conf files via the modem manufacturer’s plugin ( if the PCIe VID & PID is matched by the plugin.) + We cannot verify if the carrier mapping is correct. This relies on the manufacturer to provide the correct mapping. + + The carrier mapping .conf files is verified by modem’s manufacture according to the tested SIM card published by different countries. + Modem manufacturer confirmed that the content in the .conf file is absolutely correct. + + [Other Info] The firmware and the upgrading utilities can be downloaded from the following link: * LP#1943774 for Quectel modems * LP#1943780 for Foxconn modems -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946096 Title: Support manual firmware upgrading for Foxconn and Quectel modems. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946096] Re: Support manual firmware upgrading for Foxconn and Quectel modems.
[Where problems could occur] is updated ** Description changed: [Impact] The modem certification requires that different modem firmware is used for different network carrier. This needs the firmware upgrading capability during the modem certification process. The modem manufacture vendors (Foxconn and Quectel) provided utilities to do modem's firmware upgrading manually.(LP#1943774, LP#1943780) These utilities are verified to be working when the recent versions(> v 1.18.2) of ModemManager are used with. To support manual firmware upgrading on the current Focal release which is using ModemManager v 1.16.6, we need to apply some patches from v 1.18.2. The requested upstream patches are listed as below: * for Quectel EM160 4G ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/83ac82470589a3672092a0ba0be855093b1cf5e2 * for Foxconn T99W175 ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/21ae558fe3600c84b3ca7dcd9bf50a3ba576c7c9 **https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/76e700f4fd703f952208993330ab098305c13d6b ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/52bf2c641171ded9e617022f40497c8984520371 ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/33e2b023ef01bea9da37ae2beb192f7d92bce47a ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/f72046701659073fbfa97516e155865647acb154 The firmware upgrading was verified using the patched ModemManager v 1.16.6 with the following 2 modems: * Foxconn SDX55 T99W175 5G sub6 PCIE Modem * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem [Test Plan] 1. Install the Ubuntu image. 2. Boot and login the system. 3. Prepare the modem’s firmware and install the firmware upgrading application provided by Foxconn and Quectel 4. Using the firmware upgrading application to upgrade the modem’s firmware 5. Verify if the modem’s firmware upgrading is successful 6. Reboot 7. Verify if the upgraded modem firmware is still working [Where problems could occur] - The requested upstream patches are for these 2 specific modems. - This should not affect existing generic functions and other modems. + The requested update has 2 parts: + + 1. Informative +1.1 Provide more information about modems whose drivers use WWAN subsystem in kernel 5.13 +1.2 Modem manufacture's private utilities can use this information to do modem's FW upgrading manually + + 2. Changes are specific to Foxconn and Quectel modems +2.1 Modified code are only used by Foxconn and Quectel modems during their FW upgrading. (matched by vendor_id and product_id) + + In current Ubuntu's certification records for modem: + * No other modem uses WWAN subsystem in kernel 5.13 + * Modem's FW update is not supported via ModemManager ( < v1.18 ) + + There is no certificated modems can do the firmware upgrading flow for the regression test. + This update should not affect existing modems. [Other Info] The firmware and the upgrading utilities can be downloaded from the following link: * LP#1943774 for Quectel modems * LP#1943780 for Foxconn modems -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946096 Title: Support manual firmware upgrading for Foxconn and Quectel modems. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946096] Re: Support manual firmware upgrading for Foxconn and Quectel modems.
By investigating the mentioned patches directly, the existing behavior should not be changed: * The patch for Quectel EM160 4G There is only one patch, all changes are for the Quectel modems. * Patches for Foxconn T99W175 There are 5 patches, (patch#1): Modify the command line tool to get additional scan report for WWAN subsystem (patch#2): Move methods between 2 files (patch#3): Add more 15 seconds wait for the firmware upgrading (patch#4): Rename an existed carrier mapping configuration file for Foxconn modem (patch#5): Add a new carrier mapping configuration file for Foxconn modem From the code review, it's clear that changes only affect Foxconn and Quectel modems. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946096 Title: Support manual firmware upgrading for Foxconn and Quectel modems. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946096] Re: Support manual firmware upgrading for Foxconn and Quectel modems.
Yes, (3) is not expected to change existing behavior. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946096 Title: Support manual firmware upgrading for Foxconn and Quectel modems. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946096] Re: Support manual firmware upgrading for Foxconn and Quectel modems.
These patches are used for newer Foxconn/Quectel modems : * whose drivers are using the WWAN subsystem in the kernel 5.13. ( this OEM project uses customized kernel ) * communicated to the ModemManager service via the MBIM protocol These patches will not be used if the modem can't meet the above requirements. After checking Ubuntu certificated modems, there is no modem can meet these 2 requirement to do the regression test. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946096 Title: Support manual firmware upgrading for Foxconn and Quectel modems. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946096] Re: Support manual firmware upgrading for Foxconn and Quectel modems.
Applying these changes should have no risk: * These changes are only for specific modems.(Foxconn and Quecktel) * These changes are used when the platform's vendors do the firmware upgrading for specific modems "manually". We can try to find other modems then provide the regression test report later. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946096 Title: Support manual firmware upgrading for Foxconn and Quectel modems. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946096] Re: Support manual firmware upgrading for Foxconn and Quectel modems.
** Description changed: [Impact] + + The modem certification requires that different modem firmware is used for different network carrier. + This needs the firmware upgrading capability during the modem certification process. The modem manufacture vendors (Foxconn and Quectel) provided utilities to do modem's firmware upgrading manually.(LP#1943774, LP#1943780) These utilities are verified to be working when the recent versions(> v 1.18.2) of ModemManager are used with. To support manual firmware upgrading on the current Focal release which is using ModemManager v 1.16.6, we need to apply some patches from v 1.18.2. The requested upstream patches are listed as below: * for Quectel EM160 4G ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/83ac82470589a3672092a0ba0be855093b1cf5e2 * for Foxconn T99W175 ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/21ae558fe3600c84b3ca7dcd9bf50a3ba576c7c9 **https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/76e700f4fd703f952208993330ab098305c13d6b ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/52bf2c641171ded9e617022f40497c8984520371 ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/33e2b023ef01bea9da37ae2beb192f7d92bce47a ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/f72046701659073fbfa97516e155865647acb154 The firmware upgrading was verified using the patched ModemManager v 1.16.6 with the following 2 modems: * Foxconn SDX55 T99W175 5G sub6 PCIE Modem * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem [Test Plan] 1. Install the Ubuntu image. 2. Boot and login the system. 3. Prepare the modem’s firmware and install the firmware upgrading application provided by Foxconn and Quectel 4. Using the firmware upgrading application to upgrade the modem’s firmware 5. Verify if the modem’s firmware upgrading is successful 6. Reboot 7. Verify if the upgraded modem firmware is still working [Where problems could occur] The requested upstream patches are for these 2 specific modems. This should not affect existing generic functions and other modems. [Other Info] The firmware and the upgrading utilities can be downloaded from the following link: * LP#1943774 for Quectel modems * LP#1943780 for Foxconn modems -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946096 Title: Support manual firmware upgrading for Foxconn and Quectel modems. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946096] Re: Support manual firmware upgrading for Foxconn and Quectel modems.
The .debdiff file “modemmanager_1-1.16.6-2~21.04.1-hirsute.debdiff” is attached for hirsute(21.04). The pre-built package : https://launchpad.net/~jerry-lee- tpe/+archive/ubuntu/packages/+packages ** Patch added: "modemmanager_1-1.16.6-2~21.04.1-hirsute.debdiff" https://bugs.launchpad.net/oem-priority/+bug/1946096/+attachment/5534867/+files/modemmanager_1-1.16.6-2~21.04.1-hirsute.debdiff ** Patch removed: "modemmanager_1-1.16.6-3-hirsute.debdiff" https://bugs.launchpad.net/oem-priority/+bug/1946096/+attachment/5530707/+files/modemmanager_1-1.16.6-3~hirsute.debdiff ** Patch removed: "modemmanager_1-1.16.6-3-focal.debdiff" https://bugs.launchpad.net/oem-priority/+bug/1946096/+attachment/5530706/+files/modemmanager_1-1.16.6-3-focal.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946096 Title: Support manual firmware upgrading for Foxconn and Quectel modems. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946096] Re: Support manual firmware upgrading for Foxconn and Quectel modems.
The .debdiff file “modemmanager_1-1.16.6-2~20.04.1-focal.debdiff” is attached for focal(20.04). The pre-built package : https://launchpad.net/~jerry-lee- tpe/+archive/ubuntu/packages/+packages ** Patch added: "modemmanager_1-1.16.6-2~20.04.1-focal.debdiff" https://bugs.launchpad.net/oem-priority/+bug/1946096/+attachment/5534868/+files/modemmanager_1-1.16.6-2~20.04.1-focal.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946096 Title: Support manual firmware upgrading for Foxconn and Quectel modems. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946096] Re: Support manual firmware upgrading for Foxconn and Quectel modems.
** Description changed: [Impact] - The following 2 modems need the ModemManager v1.16.6 suite to be patched from v1.18.2 to fix some problems(LP#1943774, LP#1943780): - * Foxconn SDX55 T99W175 5G sub6 PCIE Modem - * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem + The modem manufacture vendors (Foxconn and Quectel) provided utilities to do modem's firmware upgrading manually.(LP#1943774, LP#1943780) + These utilities are verified to be working when the recent versions(> v 1.18.2) of ModemManager are used with. + To support manual firmware upgrading on the current Focal release which is using ModemManager v 1.16.6, we need to apply some patches from v 1.18.2. The requested upstream patches are listed as below: * for Quectel EM160 4G - ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/83ac82470589a3672092a0ba0be855093b1cf5e2 + ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/83ac82470589a3672092a0ba0be855093b1cf5e2 * for Foxconn T99W175 - ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/21ae558fe3600c84b3ca7dcd9bf50a3ba576c7c9 - **https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/76e700f4fd703f952208993330ab098305c13d6b - ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/52bf2c641171ded9e617022f40497c8984520371 - ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/33e2b023ef01bea9da37ae2beb192f7d92bce47a - ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/f72046701659073fbfa97516e155865647acb154 + ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/21ae558fe3600c84b3ca7dcd9bf50a3ba576c7c9 + **https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/76e700f4fd703f952208993330ab098305c13d6b + ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/52bf2c641171ded9e617022f40497c8984520371 + ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/33e2b023ef01bea9da37ae2beb192f7d92bce47a + ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/f72046701659073fbfa97516e155865647acb154 + The firmware upgrading was verified using the patched ModemManager v 1.16.6 with the following 2 modems: + * Foxconn SDX55 T99W175 5G sub6 PCIE Modem + * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem [Test Plan] 1. Install the Ubuntu image. 2. Boot and login the system. 3. Prepare the modem’s firmware and install the firmware upgrading application provided by Foxconn and Quectel - 4. Using the firmware upgrading application to upgrade the modem’s firmware + 4. Using the firmware upgrading application to upgrade the modem’s firmware 5. Verify if the modem’s firmware upgrading is successful - 6. Reboot + 6. Reboot 7. Verify if the upgraded modem firmware is still working - [Where problems could occur] - The requested upstream patches are for these 2 specific modems and the status information. + The requested upstream patches are for these 2 specific modems. This should not affect existing generic functions and other modems. - [Other Info] - The firmware and the upgrading application can be downloaded from the following link: + The firmware and the upgrading utilities can be downloaded from the following link: * LP#1943774 for Quectel modems * LP#1943780 for Foxconn modems -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946096 Title: Support manual firmware upgrading for Foxconn and Quectel modems. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946096] Re: Support manual firmware upgrading for Foxconn and Quectel modems.
** Summary changed: - Apply upstream patches to fix problems for Foxconn and Quectel modems. + Support manual firmware upgrading for Foxconn and Quectel modems. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946096 Title: Support manual firmware upgrading for Foxconn and Quectel modems. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946096] Re: Apply upstream patches to fix problems for Foxconn and Quectel modems.
Hi SRU team, Please help to check the status of this case which looks stuck at some steps. Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946096 Title: Apply upstream patches to fix problems for Foxconn and Quectel modems. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946143] Re: Apply upstream patches to display 5G NSA status
Hi,
The libqmi packages from the {impish, hirsute, focal}-proposed channels
wrere verified.
The 5G status information can be displayed using the package from the
-proposed channel.
The detail testing report is attached as "Test Report for
LP#1946143.pdf".
Thanks
** Attachment added: "Test Report for LP#1946143.pdf"
https://bugs.launchpad.net/oem-priority/+bug/1946143/+attachment/5534488/+files/Test%20Report%20for%20LP%231946143.pdf
** Tags removed: verification-needed verification-needed-focal
verification-needed-hirsute verification-needed-impish
** Tags added: verification-done verification-done-focal
verification-done-hirsute verification-done-impish
** Tags removed: verification-done verification-done-focal
verification-done-hirsute verification-done-impish
** Tags added: verification-needed verification-needed-focal
verification-needed-hirsute verification-needed-impish
** Tags removed: verification-needed-focal verification-needed-hirsute
verification-needed-impish
** Tags added: verification-done-focal verification-done-hirsute
verification-done-impish
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946143
Title:
Apply upstream patches to display 5G NSA status
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1946143/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803856] Re: Access to Samsung fails in file manager
Ubuntu 20.04 fails to access an older Samsung phone properly for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803856 Title: Access to Samsung fails in file manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmtp/+bug/1803856/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946143] Re: Apply upstream patches to display 5G NSA status
Hi Sebastien, Thanks for your help. I ave not found the packages are ready in *-proposed channels yet. Can you help to check it? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946143 Title: Apply upstream patches to display 5G NSA status To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946096] Re: Apply upstream patches to fix problems for Foxconn and Quectel modems.
Hi Sebastien, I verified this new package from impish-proposed : * The version of the packages tested: ModemManager: 1.16.6-2ubuntu1 * The test report is attached as "TestReport_impish- proposed_1946096.pdf". Besides, I ave not found the packages are ready in hirsute-proposed and focal-proposed yet. Can you help to check it? Thanks ** Attachment added: "TestReport_impish-proposed_1946096.pdf" https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1946096/+attachment/5532306/+files/TestReport_impish-proposed_1946096.pdf ** Tags added: verification-done-impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946096 Title: Apply upstream patches to fix problems for Foxconn and Quectel modems. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946096] Re: Apply upstream patches to fix problems for Foxconn and Quectel modems.
** Changed in: oem-priority Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946096 Title: Apply upstream patches to fix problems for Foxconn and Quectel modems. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946143] Re: Apply upstream patches to display 5G NSA status
** Changed in: oem-priority Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946143 Title: Apply upstream patches to display 5G NSA status To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946143] Re: Apply upstream patches to display 5G NSA status
The .debdiff file “libqmi_1-1.28.6-2-impish.debdiff” is attached for impish(22.04). ** Patch added: "libqmi_1-1.28.6-2-impish.debdiff" https://bugs.launchpad.net/ubuntu/+source/libqmi/+bug/1946143/+attachment/5531016/+files/libqmi_1-1.28.6-2-impish.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946143 Title: Apply upstream patches to display 5G NSA status To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946096] Re: Apply upstream patches to fix problems for Foxconn and Quectel modems.
The .debdiff file “modemmanager_1-1.16.6-3-impish.debdiff” is attached for impish(22.04). The pre-built package : https://launchpad.net/~jerry-lee- tpe/+archive/ubuntu/packages/+packages ** Patch added: "modemmanager_1-1.16.6-3-impish.debdiff" https://bugs.launchpad.net/oem-priority/+bug/1946096/+attachment/5531015/+files/modemmanager_1-1.16.6-3-impish.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946096 Title: Apply upstream patches to fix problems for Foxconn and Quectel modems. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946143] Re: Apply upstream patches to display 5G NSA status
** Also affects: libqmi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946143 Title: Apply upstream patches to display 5G NSA status To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946096] Re: Apply upstream patches to fix problems for Foxconn and Quectel modems.
** Changed in: oem-priority Assignee: (unassigned) => Jerry Lee (jerry-lee-tpe) ** Changed in: oem-priority Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946096 Title: Apply upstream patches to fix problems for Foxconn and Quectel modems. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946143] [NEW] Apply upstream patches to display 5G NSA status
Public bug reported: [Impact] The 5G NSA status can not be displayed in the libqmi version 1.28.6-1. (LP#1937012) The 5G NSA status is supported in the libqmi version 1.30.2. The requested upstream patches are listed as below: * 5G NSA status patches https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/commit/29905223c5ae6e5e4ef9246dd9dd4d01b2819d9a * qmicli,nas: flag as 'n/a' the 5G NSA signal quality if not connected https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/commit/b05df7b658f9cfb4c5e74a3e07913de689914a8f [Test Plan] 1. Install the Ubuntu image. 2. Boot and login the system. 3. Verify if the field “5G NSA Available: ” can be displayed via executing: $ sudo qmicli --device=/dev/wwan0p2MBIM --device-open-proxy --nas-get-system-info ... 5G NSA Available: 'no' ... [Where problems could occur] The requested upstream patches are for displaying the status information of 5G NSA network. This should not affect existing generic functions. [Other Info] The latest version of libqmi suit can display the 5G NSA status. ** Affects: oem-priority Importance: Critical Assignee: Jerry Lee (jerry-lee-tpe) Status: New ** Affects: libqmi (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority ** Package changed: libqmi (Ubuntu) => oem-priority -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946143 Title: Apply upstream patches to display 5G NSA status To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946096] Re: Apply upstream patches to fix problems for Foxconn and Quectel modems.
The .debdiff file “modemmanager_1-1.16.6-3-hirsute.debdiff” is attached for hirsute(21.04). The pre-built package : https://launchpad.net/~jerry-lee- tpe/+archive/ubuntu/packages/+packages ** Patch added: "modemmanager_1-1.16.6-3-hirsute.debdiff" https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1946096/+attachment/5530707/+files/modemmanager_1-1.16.6-3~hirsute.debdiff ** Package changed: modemmanager (Ubuntu) => oem-priority ** Also affects: modemmanager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946096 Title: Apply upstream patches to fix problems for Foxconn and Quectel modems. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946096] Re: Apply upstream patches to fix problems for Foxconn and Quectel modems.
The .debdiff file “modemmanager_1-1.16.6-3-focal.debdiff” is attached for focal(20.04). The pre-built package : https://launchpad.net/~jerry-lee- tpe/+archive/ubuntu/packages/+packages ** Patch added: "modemmanager_1-1.16.6-3-focal.debdiff" https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1946096/+attachment/5530706/+files/modemmanager_1-1.16.6-3-focal.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946096 Title: Apply upstream patches to fix problems for Foxconn and Quectel modems. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946096] [NEW] Apply upstream patches to fix problems for Foxconn and Quectel modems.
Public bug reported: [Impact] The following 2 modems need the ModemManager v1.16.6 suite to be patched from v1.18.2 to fix some problems(LP#1943774, LP#1943780): * Foxconn SDX55 T99W175 5G sub6 PCIE Modem * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem The requested upstream patches are listed as below: * for Quectel EM160 4G ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/83ac82470589a3672092a0ba0be855093b1cf5e2 * for Foxconn T99W175 ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/21ae558fe3600c84b3ca7dcd9bf50a3ba576c7c9 **https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/76e700f4fd703f952208993330ab098305c13d6b ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/52bf2c641171ded9e617022f40497c8984520371 ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/33e2b023ef01bea9da37ae2beb192f7d92bce47a ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/f72046701659073fbfa97516e155865647acb154 [Test Plan] 1. Install the Ubuntu image. 2. Boot and login the system. 3. Prepare the modem’s firmware and install the firmware upgrading application provided by Foxconn and Quectel 4. Using the firmware upgrading application to upgrade the modem’s firmware 5. Verify if the modem’s firmware upgrading is successful 6. Reboot 7. Verify if the upgraded modem firmware is still working [Where problems could occur] The requested upstream patches are for these 2 specific modems and the status information. This should not affect existing generic functions and other modems. [Other Info] The firmware and the upgrading application can be downloaded from the following link: * LP#1943774 for Quectel modems * LP#1943780 for Foxconn modems ** Affects: modemmanager (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946096 Title: Apply upstream patches to fix problems for Foxconn and Quectel modems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1946096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943506] Re: package does not run on clean install of Impish
*** This bug is a duplicate of bug 1937993 *** https://bugs.launchpad.net/bugs/1937993 ** This bug has been marked a duplicate of bug 1937993 font-manager crashed with signal 5 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943506 Title: package does not run on clean install of Impish To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/font-manager/+bug/1943506/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934286] Re: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases.
** Changed in: oem-priority Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1934286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934286] Re: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases.
BTW, the Lenovo's FCC unlock snap is ready for testing. https://snapcraft.io/lenovo-wwan-dpr -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1934286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934286] Re: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases.
We have verified the packages on hirsute-proposed: * The version of the packages tested: ModemManager: 1.16.6 libmbim: 1.24.8 libqmi: 1.28.6 * There are 2 different modems tested and passed the testing: (1) DW5820e [413C:81D9] (2) DW5821e [413C:81D7] ** Tags removed: verification-needed-hirsute ** Tags added: verification-done-hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1934286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940377] Re: The WWAN - Huawei Technologies Co., Ltd. [12d1:15c1] does not work after install Ubuntu Hirsute.
@Gabriel Because this modem passed the test using Focal, can you help to test the following cases for comparison? (1) Using Hirsute The ModemManager is replaced from the -proposed channel The default kernel in Hirsute is replaced with Focal’s kernel (2) Using Focal The ModemManager is replaced from the -proposed channel The default kernel in Focal is replaced with Hirsute’s kernel If (1) passed, no need to test (2) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940377 Title: The WWAN - Huawei Technologies Co., Ltd. [12d1:15c1] does not work after install Ubuntu Hirsute. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1940377/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940377] Re: The WWAN - Huawei Technologies Co., Ltd. [12d1:15c1] does not work after install Ubuntu Hirsute.
Can we get the results fro the following commands: $ lspci $ sudo mmcli --list-modems $ sudo mmcli --modem 0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940377 Title: The WWAN - Huawei Technologies Co., Ltd. [12d1:15c1] does not work after install Ubuntu Hirsute. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1940377/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934286] Re: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases.
The resource is tight so that the plan is to complete the Hirsute verification before Aug. 23. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1934286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934286] Re: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases.
We are arranging resource to do the coverage test for hirsute-proposed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1934286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901829] Re: thunderbird fails to open, xml parse error
I see this issue in 20.04 but it interfere with starting thunderbird. I'm using en-US. jlquinn@cerberus:~/Videos/summits$ lsb_release -a; uname -a; apt-cache policy thunderbird No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS Release:20.04 Codename: focal Linux cerberus 5.4.0-80-generic #90-Ubuntu SMP Fri Jul 9 22:49:44 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux thunderbird: Installed: 1:78.11.0+build1-0ubuntu0.20.04.2 Candidate: 1:78.11.0+build1-0ubuntu0.20.04.2 Version table: *** 1:78.11.0+build1-0ubuntu0.20.04.2 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 1:68.7.0+build1-0ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901829 Title: thunderbird fails to open, xml parse error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1901829/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934286] Re: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases.
We have verified the packages on focal-proposed: * The version of the packages tested: ModemManager: 1.16.6 libmbim: 1.24.8 libqmi: 1.28.6 * The Mobile broadband/WWAN test cases in checkbox have been performed on the packages. There are 6 different modems tested and the reports can be downloaded: (1) https://certification.canonical.com/hardware/202010-28320/submission/223095/ (2) https://certification.canonical.com/hardware/201601-20490/submission/223615/ (3) https://certification.canonical.com/hardware/201601-20490/submission/223629/ (4) https://certification.canonical.com/hardware/202010-28324/submission/223136/ (5) https://certification.canonical.com/hardware/202103-28860/submission/224158/ (6) https://certification.canonical.com/hardware/202103-28860/submission/224158/ * There is a stress test plan performed on the system installing packaes: (1) https://certification.canonical.com/hardware/202010-28324/submission/223167/ ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1934286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1937993] Re: font-manager crashed with signal 5
https://code.launchpad.net/~font-manager/+archive/ubuntu/staging https://github.com/FontManager/font-manager#ubuntu-personal-package-archive Not meant to discourage anyone from reporting bugs which affect all Ubuntu users, that's definitely a good thing to do. Just wanted to make sure you were aware of the option. Also make sure to purge any existing packages, manager, viewer, common, extensions, etc. before switching between the two. Though I think they're compatible at this point, better to be safe. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1937993 Title: font-manager crashed with signal 5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/font-manager/+bug/1937993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1937993] Re: font-manager crashed with signal 5
@alexmurray You can sidestep this issue by using the PPA, which is always up to date. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1937993 Title: font-manager crashed with signal 5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/font-manager/+bug/1937993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1935901] Re: Braswell video locks up under gnome-shell
Hi, there's a crash report mentioned on this page: https://errors.ubuntu.com/user/241a8d330b8560e5d29b49b2d8df1a9340834364d1e9930a70caae16e29bf446d33032781384b132361e219d11002feddb39eb224ef4a8725b7f4651d988de57 but I don't have permission to follow the link to the actual crash report. I originally tried using this box with X11, but I could lock up the screen regularly. So I tried running under wayland, which seems to be more stable for this machine. The above crash report is from kodi- wayland. When I look at what's running, I see Xwayland, which I assume is wayland running with the x layer on top? When I log in after a restart (too many of them), I have gnome on wayland chosen. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1935901 Title: Braswell video locks up under gnome-shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1935901/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1935901] Re: Braswell video locks up under gnome-shell
** Attachment added: "lspci.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1935901/+attachment/5511461/+files/lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1935901 Title: Braswell video locks up under gnome-shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1935901/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934286] Re: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases.
The snap "dpr-wwan_1.0-wwan-test_amd64.snap" is provided by Lenovo (not published yet), it will be published in the Snap store for Lenovo's system to use it. (it recognizes Lenovo' system then do the FCC unlocking) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1934286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934286] Re: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases.
Hi Brian, I can't find the modemmanage from the focal-proposed channel to be upgraded. https://people.canonical.com/~ubuntu-archive/pending-sru.html shows it is in "Dependency wait". Please help to check it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1934286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1935901] Re: video locks up under gnome-shell
It seems to happen intermittently but when it does, I typically can't get back control at the console. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1935901 Title: video locks up under gnome-shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1935901/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1935901] [NEW] video locks up under gnome-shell
Public bug reported: I get a blank screen with a mouse cursor. Cursor doesn't respond to mouse inputs. System doesn't respond to keyboard inputs. I can still ssh in from another machine. I see the following in the journal: Jul 13 01:55:14 jenks gnome-shell[1403]: libinput error: client bug: timer event3 debounce: scheduled expiry is in the past (-442ms> Jul 13 01:55:14 jenks gnome-shell[1403]: libinput error: client bug: timer event3 debounce short: scheduled expiry is in the past (> Jul 13 01:57:07 jenks gnome-shell[1403]: Failed to post KMS update: drmModePageFlip on CRTC 93 failed: No space left on device ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 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 CasperMD5CheckResult: skip Date: Tue Jul 13 02:06:08 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-06-29 (14 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1935901 Title: video locks up under gnome-shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1935901/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934286] Re: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases.
Hi Brian, This is a debdiff for libmbim applicable to Focal(1.22.0-2). The maintainer scripts (libmbim-proxy.postinst, libmbim-proxy.postrm) are added to keep mbim-proxy in both places. I built this in pbuilder and it builds successfully, and I installed it, the patch works as intended. ** Patch added: "libmbim_1.24.8-1~20.04.02-focal.debdiff" https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1934286/+attachment/5510464/+files/libmbim_1.24.8-1~20.04.02-focal.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1934286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1935760] Re: video locks up under kodi
Video lockup is reproducible. This may not be a kernel issue. Switching to wayland display server doesn't lock up this way. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1935760 Title: video locks up under kodi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1935760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
