[Touch-packages] [Bug 1969291] [NEW] apport-collect & ubuntu-bug failing to switch to firefox
Public bug reported: In attempting to file a bug report on Lubuntu jammy ISO (QA-test installed yesterday using ISO 2020-04-15) -- guiverc@dc7700-2re:~$ apport-collect 1969290 The authorization page: (https://launchpad.net/+authorize-token?oauth_token=6K7rwSbKHlbLWmkK65sj&allow_permission=DESKTOP_INTEGRATION) should be opening in your browser. Use your browser to authorize this program to access Launchpad on your behalf. Waiting to hear from Launchpad about your decision... /usr/bin/xdg-open: 882: firefox: not found /usr/bin/xdg-open: 882: firefox: not found xdg-open: no method available for opening 'https://launchpad.net/+authorize-token?oauth_token=6K7rwSbKHlbLWmkK65sj&allow_permission=DESKTOP_INTEGRATION' --- On attempting to file using `ubuntu-bug apport` --- guiverc@dc7700-2re:~$ ubuntu-bug apport *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. . *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (5.0 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): s *** Uploading problem information The collected information is being sent to the bug tracking system. This might take a few minutes. 96% *** To continue, you must visit the following URL: https://bugs.launchpad.net/ubuntu/+source/apport/+filebug/02e65c1c-bdf7-11ec-a167-40a8f03099c8? You can launch a browser now, or copy this URL into a browser on another computer. Choices: 1: Launch a browser now C: Cancel Please choose (1/C): 1 /usr/bin/xdg-open: 882: firefox: not found /usr/bin/xdg-open: 882: firefox: not found xdg-open: no method available for opening 'https://bugs.launchpad.net/ubuntu/+source/apport/+filebug/02e65c1c-bdf7-11ec-a167-40a8f03099c8?' --- ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apport 2.20.11-0ubuntu82 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Sun Apr 17 12:34:57 2022 InstallationDate: Installed on 2022-04-16 (0 days ago) InstallationMedia: Lubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220415) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1969291 Title: apport-collect & ubuntu-bug failing to switch to firefox Status in apport package in Ubuntu: New Bug description: In attempting to file a bug report on Lubuntu jammy ISO (QA-test installed yesterday using ISO 2020-04-15) -- guiverc@dc7700-2re:~$ apport-collect 1969290 The authorization page: (https://launchpad.net/+authorize-token?oauth_token=6K7rwSbKHlbLWmkK65sj&allow_permission=DESKTOP_INTEGRATION) should be opening in your browser. Use your browser to authorize this program to access Launchpad on your behalf. Waiting to hear from Launchpad ab
[Touch-packages] [Bug 1969289] [NEW] Secondary display does not work
Public bug reported: Secondary display does not work ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 16 20:29:43 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:06fd] InstallationDate: Installed on 2022-04-14 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220409) MachineType: Dell Inc. Inspiron 13-7359 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=3b34bc2c-2f64-49d2-9734-d6ff9a9d3b14 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/06/2016 dmi.bios.release: 1.12 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.12.00 dmi.board.name: 0X1DP8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.12.00:bd09/06/2016:br1.12:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0X1DP8:rvrA00:cvnDellInc.:ct9:cvr:sku06FD: dmi.product.name: Inspiron 13-7359 dmi.product.sku: 06FD dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1969289 Title: Secondary display does not work Status in xorg package in Ubuntu: New Bug description: Secondary display does not work ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 16 20:29:43 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:06fd] InstallationDate: Installed on 2022-04-14 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220409) MachineType: Dell Inc. Inspiron 13-7359 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=3b34bc2c-2f64-49d2-9734-d6ff9a9d3b14 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/06/2016 dmi.bios.release: 1.12 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.12.00 dmi.board.name: 0X1DP8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.12.00:bd09/06/2016:br1.12:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0X1DP8:rvrA00:cvnDellInc.:ct9:cvr:sku06FD: dmi.product.name: Inspiron 13-7359 dmi.product.sku: 06FD dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1969289/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.ne
[Touch-packages] [Bug 1958720] Re: python3-yaml and python3-six are not co-installable with python-is-python2 in jammy
I verified that this is fixed when upgrading from Focal to Jammy. Method: lxc launch ubuntu:focal test lxc exec test bash apt -y update && apt -y full-upgrade apt -y install python-is-python2 do-release-upgrade -d do-release-upgrade does suggest removing python-is-python2 as obsolete after the upgrade. However if you say no (the default) then the package remains. Thanks Rolf for the report and the fix. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to six in Ubuntu. https://bugs.launchpad.net/bugs/1958720 Title: python3-yaml and python3-six are not co-installable with python-is- python2 in jammy Status in pyyaml package in Ubuntu: Fix Released Status in six package in Ubuntu: Fix Released Bug description: The packages python3-yaml and python-is-python2 are not co-installable in jammy and I believe they should be. This currently prevents me from upgrading one of my machines from focal to jammy. Further analysis with the help of Stefano Rivera revealed that what- is-python no longer produces a python-is-python2 package and the changelog hints at that being intentional. Jammy still has a python2 package, though. python3-yaml in jammy breaks on python (<2.7.18). The python-is- python2 package in focal is version 2.7.17-4 and in impish it is 2.7.18-9 and thus will be forcefully removed when going to jammy. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pyyaml/+bug/1958720/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1965439] Re: software-properties-qt can no longer launch when called by pkexec
A kludge workaround this issue is to run the command: sudo software- properties-qt --open-tab=x (where x is 0, 1, 2, 3, or 4 [the 'tab' number]) from a konsole session. It at least allows one to access software-properties. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1965439 Title: software-properties-qt can no longer launch when called by pkexec Status in kubuntu-settings package in Ubuntu: In Progress Status in policykit-1 package in Ubuntu: Confirmed Status in software-properties package in Ubuntu: Confirmed Status in ubuntustudio-default-settings package in Ubuntu: In Progress Status in kubuntu-settings source package in Jammy: In Progress Status in policykit-1 source package in Jammy: Confirmed Status in software-properties source package in Jammy: Confirmed Status in ubuntustudio-default-settings source package in Jammy: In Progress Bug description: See description below. As the driver manager is done inside software- properties-qt, it's basically the same bug, but now it's affected by something we can't exactly get into the mechanism of: plasma- discover's "Software Sources" link. Earlier description: The driver manager for both Ubuntu Studio and Kubuntu can no longer launch due to some updated security measures in PolicyKit. The original behavior was that systemsettings would open /usr/bin/ubuntustudio-driver-manager (or /usr/bin/kubuntu-driver- manger) via pkexec, which would then open software-settings-qt. Unfortunately, the new behavior does not act correctly to pkexec and pkexec does not see the user as available in the sudoers file. The only way around this was to pass "export DISPLAY=:0" inside the appropriate driver manager executable with the command "sudo software- properties-qt". The KCM itself needs to execute the driver-manager via xterm, which then prompts for a password. It's ugly, but it works. I will attach a debdiff for the kubuntu-settings package. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntustudio-default-settings 22.04.19 [modified: usr/share/sddm/themes/ubuntustudio/theme.conf] ProcVersionSignature: Ubuntu 5.15.0-22.22-lowlatency 5.15.19 Uname: Linux 5.15.0-22-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Mar 17 12:19:44 2022 InstallationDate: Installed on 2021-03-20 (361 days ago) InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 (20210320) PackageArchitecture: all SourcePackage: ubuntustudio-default-settings UpgradeStatus: Upgraded to jammy on 2021-11-07 (130 days ago) modified.conffile..etc.skel..local.share.konsole.Profile: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-settings/+bug/1965439/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1926256] Re: Pasted text in the terminal is always highlighted and selected
Still a problem for Ubuntu MATE 22.04 LTS. Please fix it on distro level. You break UX. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1926256 Title: Pasted text in the terminal is always highlighted and selected Status in bash package in Ubuntu: Invalid Status in gnome-terminal package in Ubuntu: Invalid Status in mate-terminal package in Ubuntu: Invalid Status in readline package in Ubuntu: Confirmed Status in vte2.91 package in Ubuntu: Invalid Bug description: Steps to reproduce: 1. Have Ubuntu 21.04 installed 2. Launch terminal 3a. Execute some command, select this command to copy it, then paste command 3b. Paste some command from clipboard to terminal Expected result: * pasted command is not highlighted and is not selected Actual result: * pasted command is selected and highlighted ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: mate-terminal 1.24.1-1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Tue Apr 27 09:43:56 2021 InstallationDate: Installed on 2021-04-23 (3 days ago) InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: mate-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1926256/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1965219] Re: gnome lock screen does not permit reentering password
It's seemingly much less bad if I disable suspend when plugged into power, and maybe the remaining problems come from plugging in power before resume. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1965219 Title: gnome lock screen does not permit reentering password Status in gnome-shell package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Bug description: Initially, only the mouse works in the gnome lock screen, without any way to get a password prompt. It's likely only happening when returning from suspend with lid open. It's possible to ssh into the machine or to press Fn+Ctrl+Alt+F?? and login without gnome. After this, Fn+Ctrl+Alt+F1 brings up a purple ubuntu login screen, but then after login you simply return to the lock screen with no working keyboard. I never found any method to force unlock from ssh or another vt though, so this always still required a reboot, or killing all of gnome. I've randomly tried some solutions from https://askubuntu.com/questions/1242110/after-upgrading-to- ubuntu-20-04-lockscreen-not-working including reinstalling many gnome components. After this, the behavior initially disappeared by returning from suspend merely took a long time, like 30 seconds or 1 minute. It's possible the delay stems from memory size, but a previous identical lenovo x1 had no such problems. I've now a worse problem just a few hours later where unsuspend went directly to a purple ubuntu login screen, but neither the mouse nor keyboard worked. I've not yet been able to test ssh on this problem. It's possibly all connected to recent firmware upgrades, so I'm happy to try downgrading the firmware, but I've not found any instructions on doing so, or even identifying the firmware upgrade log. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.14.0-1027.30-oem 5.14.21 Uname: Linux 5.14.0-1027-oem 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: Thu Mar 17 03:44:49 2022 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20210412-218+sutton-newell-focal-amd64+X00 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Within the last week or two GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:22d5] InstallationDate: Installed on 2021-04-15 (335 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20210412-22:07 MachineType: LENOVO 20XWCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1027-oem root=UUID=6a411137-06bb-4de1-be93-c2fcd4f44a5a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2021 dmi.bios.release: 1.51 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET75W (1.51 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XWCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.32:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9: dmi.product.family: ThinkPad X1 Carbon Gen 9 dmi.product.name: 20XWCTO1WW dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9 dmi.product.version: ThinkPad X1 Carbon Gen 9 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+
[Touch-packages] [Bug 1969115] Re: Update glib to 2.72.1
This bug was fixed in the package glib2.0 - 2.72.1-1 --- glib2.0 (2.72.1-1) unstable; urgency=medium [ Jeremy Bicha ] * New upstream release (LP: #1969115) - Includes workaround for meson #1008382 * Add patch to recognize GNOME Console as a terminal app * Refresh patch * debian/libglib2.0-0.symbols: Add new symbol [ Johannes Schauer Marin Rodrigues ] * debian/libglib2.0-0.postinst.in: only run clean-up-unmanaged-libraries on upgrades and not on new installations (Closes: #1008096) -- Jeremy Bicha Thu, 14 Apr 2022 09:35:23 -0400 ** Changed in: glib2.0 (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1969115 Title: Update glib to 2.72.1 Status in glib2.0 package in Ubuntu: Fix Released Bug description: Impact -- glib has a new bugfix release as part of their GNOME 42 series https://gitlab.gnome.org/GNOME/glib/-/blob/glib-2-72/NEWS Test Case - Ensure that the autopkgtests complete successfully. The autopkgtests run installed tests. Where Problems Could Occur -- This is believed to be part of the GNOME micro-release exception. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1969115/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 827151] Re: Annoying log message "DIGEST-MD5 common mech free"
** Changed in: cyrus-sasl2 Status: Confirmed => Fix Released ** Changed in: cyrus-sasl2 (Debian) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/827151 Title: Annoying log message "DIGEST-MD5 common mech free" Status in Cyrus-sasl2: Fix Released Status in cyrus-sasl2 package in Ubuntu: Triaged Status in cyrus-sasl2 source package in Trusty: Won't Fix Status in cyrus-sasl2 source package in Xenial: Incomplete Status in cyrus-sasl2 source package in Yakkety: Fix Released Status in cyrus-sasl2 source package in Focal: Triaged Status in cyrus-sasl2 package in Debian: Fix Released Bug description: I recently updated the libsasl2-modules to 2.1.24~rc1.dfsg1+cvs2011-05-23-4ubuntu1 in oneiric. That triggered the bug also described in Debian here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631932 The annoying message is logged in auth.log. In my case, it is associated with svnserve: svnserve: DIGEST-MD5 common mech free I'm not exactly sure what action triggers the message, but I can investigate more if required. $ lsb_release -rd Description:Ubuntu oneiric (development branch) Release:11.10 To manage notifications about this bug go to: https://bugs.launchpad.net/cyrus-sasl2/+bug/827151/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1969241] Re: Network issue no IPv6 using Sierra Wireless EM7421 and mbim
apport information ** Tags added: apport-collected jammy third-party-packages ** Description changed: Network issue no IPv6 using Sierra Wireless EM7421 and mbim Description:Ubuntu Jammy Jellyfish Release:22.04 Linux 5.15.0-25-generic I need to connect via GSM to Internet using IPv6. IPv6 not present in config. Internet connect works with IPv4 although issues seem to exist. EXPECTATION: IPv6 shall work properly like the EM7455 with same card in very similar machine, Ubuntu. IPv6 shall work properly like in Linux-Mint 20.3 on this machine, this setup. All using the same driver=cdc_mbim ENVIRONMENT: - SIM is working properly, - EM7421 latest firmware applied, - EM7421 capable doing IPv6 with this setup (according to spec + test with Win10 + works with Linux Mint); "package" not understood, sorry. ModemManager probably? ASSUMPTIONs: - Missing IPv6 is a wrong config / bug in software / communication issue. - IPv6 communication can be enabled by adjustment rather than by code changes in cdc_mbim or redesign of SierraW. EM7421 device. - Some enhancement / fix can enable IPv6 communication. REMARK: Linux-Mint 20.3 una is capable of running the 'EM7421' in proper IPv6 "mode" (kernel 5.4.0-107-generic). It uses driver=cdc_mbim as well. It shows other issues like missing provision of additional DNS server data, EUI64 state and the like. THE ISSUE and details: Actually no IPv6 available at all (IPv6 is expected to work / no IPv6 is a big issue for our work): 3: wwan0: mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000 link/ether 6a:05:2c:26:95:58 brd ff:ff:ff:ff:ff:ff inet 10.34.85.36/29 brd 10.34.85.39 scope global noprefixroute wwan0 This is the Sierra Wireless GSM-Modem (working): sudo mbimcli --device=/dev/cdc-wdm0 --query-device-caps [/dev/cdc-wdm0] Device capabilities retrieved: Device type: 'remote' Cellular class: 'gsm' Voice class: 'no-voice' SIM class: 'removable' Data class: 'umts, hsdpa, hsupa, lte' SMS caps: 'pdu-receive, pdu-send' Ctrl caps: 'reg-manual' Max sessions: '8' Custom data class: 'unknown' Device ID: '356706140353162' Firmware info: 'SWI9X50C_01.14.03.00' Hardware info: 'EM7421' Attempt to start modem via mbim: pre: sudo service network-manager stop sudo systemctl disable ModemManager then Report sudo mbim-network /dev/cdc-wdm0 start Profile at '/etc/mbim-network.conf' not found... Querying subscriber ready status 'mbimcli -d /dev/cdc-wdm0 --query-subscriber-ready-status --no-close'... [/dev/cdc-wdm0] Subscriber ready status retrieved: Ready state: 'initialized' Subscriber ID: '262011905110762' SIM ICCID: '8949021788157884' Ready info: 'none' Telephone numbers: (1) '+491604282867' [/dev/cdc-wdm0] Session not closed: TRID: '3' Querying registration state 'mbimcli -d /dev/cdc-wdm0 --query-registration-state --no-open=3 --no-close'... [/dev/cdc-wdm0] Registration status: Network error: 'unknown' Register state: 'home' Register mode: 'automatic' Available data classes: 'lte' Current cellular class: 'gsm' Provider ID: '26201' Provider name: 'Telekom.de' Roaming text: 'unknown' Registration flags: 'packet-service-automatic-attach' [/dev/cdc-wdm0] Session not closed: TRID: '4' Attaching to packet service with 'mbimcli -d /dev/cdc-wdm0 --attach-packet-service --no-open=4 --no-close'... [/dev/cdc-wdm0] Successfully attached to packet service [/dev/cdc-wdm0] Packet service status: Network error: 'unknown' Packet service state: 'attached' Available data classes: 'lte' Uplink speed: '15000 bps' Downlink speed: '3 bps' [/dev/cdc-wdm0] Session not closed: TRID: '5' Starting network with 'mbimcli -d /dev/cdc-wdm0 --connect=apn='' --no-open=5 --no-close'... Network started successfully Saving state at /tmp/mbim-network-state-cdc-wdm0... (TRID: 7) status reported by ip a : 3: wwan0: mtu 1500 qdisc fq_codel state DOWN group default qlen 1000 link/ether 86:a6:1f:1a:ce:30 brd ff:ff:ff:ff:ff:ff try to bring it up: sudo ip link set dev wwan0 up (no error reported) new status reported by ip a : 3: wwan0: mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000 link/ether 86:a6:1f:1a:ce:30 brd ff:ff:ff:ff:ff:ff (All SIM / telephony / GSM data above is real; please handle with care) lshw reporting on USB and the like *-usb:2 description: USB controller product: Tiger Lake-LP USB 3.2 Gen 2x1 xHCI Host Controller vendor: Intel Corporation physical id: 14 bus info: pci@:00:14.0 version: 20 width: 64 bits clock: 33MHz capabilities: pm msi xhci bus_master cap_list configuration: drive
[Touch-packages] [Bug 1969241] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1969241/+attachment/5581065/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1969241 Title: Network issue no IPv6 using Sierra Wireless EM7421 and mbim Status in libmbim package in Ubuntu: New Status in modemmanager package in Ubuntu: New Bug description: Network issue no IPv6 using Sierra Wireless EM7421 and mbim Description:Ubuntu Jammy Jellyfish Release:22.04 Linux 5.15.0-25-generic I need to connect via GSM to Internet using IPv6. IPv6 not present in config. Internet connect works with IPv4 although issues seem to exist. EXPECTATION: IPv6 shall work properly like the EM7455 with same card in very similar machine, Ubuntu. IPv6 shall work properly like in Linux-Mint 20.3 on this machine, this setup. All using the same driver=cdc_mbim ENVIRONMENT: - SIM is working properly, - EM7421 latest firmware applied, - EM7421 capable doing IPv6 with this setup (according to spec + test with Win10 + works with Linux Mint); "package" not understood, sorry. ModemManager probably? ASSUMPTIONs: - Missing IPv6 is a wrong config / bug in software / communication issue. - IPv6 communication can be enabled by adjustment rather than by code changes in cdc_mbim or redesign of SierraW. EM7421 device. - Some enhancement / fix can enable IPv6 communication. REMARK: Linux-Mint 20.3 una is capable of running the 'EM7421' in proper IPv6 "mode" (kernel 5.4.0-107-generic). It uses driver=cdc_mbim as well. It shows other issues like missing provision of additional DNS server data, EUI64 state and the like. THE ISSUE and details: Actually no IPv6 available at all (IPv6 is expected to work / no IPv6 is a big issue for our work): 3: wwan0: mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000 link/ether 6a:05:2c:26:95:58 brd ff:ff:ff:ff:ff:ff inet 10.34.85.36/29 brd 10.34.85.39 scope global noprefixroute wwan0 This is the Sierra Wireless GSM-Modem (working): sudo mbimcli --device=/dev/cdc-wdm0 --query-device-caps [/dev/cdc-wdm0] Device capabilities retrieved: Device type: 'remote' Cellular class: 'gsm' Voice class: 'no-voice' SIM class: 'removable' Data class: 'umts, hsdpa, hsupa, lte' SMS caps: 'pdu-receive, pdu-send' Ctrl caps: 'reg-manual' Max sessions: '8' Custom data class: 'unknown' Device ID: '356706140353162' Firmware info: 'SWI9X50C_01.14.03.00' Hardware info: 'EM7421' Attempt to start modem via mbim: pre: sudo service network-manager stop sudo systemctl disable ModemManager then Report sudo mbim-network /dev/cdc-wdm0 start Profile at '/etc/mbim-network.conf' not found... Querying subscriber ready status 'mbimcli -d /dev/cdc-wdm0 --query-subscriber-ready-status --no-close'... [/dev/cdc-wdm0] Subscriber ready status retrieved: Ready state: 'initialized' Subscriber ID: '262011905110762' SIM ICCID: '8949021788157884' Ready info: 'none' Telephone numbers: (1) '+491604282867' [/dev/cdc-wdm0] Session not closed: TRID: '3' Querying registration state 'mbimcli -d /dev/cdc-wdm0 --query-registration-state --no-open=3 --no-close'... [/dev/cdc-wdm0] Registration status: Network error: 'unknown' Register state: 'home' Register mode: 'automatic' Available data classes: 'lte' Current cellular class: 'gsm' Provider ID: '26201' Provider name: 'Telekom.de' Roaming text: 'unknown' Registration flags: 'packet-service-automatic-attach' [/dev/cdc-wdm0] Session not closed: TRID: '4' Attaching to packet service with 'mbimcli -d /dev/cdc-wdm0 --attach-packet-service --no-open=4 --no-close'... [/dev/cdc-wdm0] Successfully attached to packet service [/dev/cdc-wdm0] Packet service status: Network error: 'unknown' Packet service state: 'attached' Available data classes: 'lte' Uplink speed: '15000 bps' Downlink speed: '3 bps' [/dev/cdc-wdm0] Session not closed: TRID: '5' Starting network with 'mbimcli -d /dev/cdc-wdm0 --connect=apn='' --no-open=5 --no-close'... Network started successfully Saving state at /tmp/mbim-network-state-cdc-wdm0... (TRID: 7) status reported by ip a : 3: wwan0: mtu 1500 qdisc fq_codel state DOWN group default qlen 1000 link/ether 86:a6:1f:1a:ce:30 brd ff:ff:ff:ff:ff:ff try to bring it up: sudo ip link set dev wwan0 up (no error reported) new status reported by ip a : 3: wwan0: mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000 link/ether 86:a6:1f:1a:ce:30 brd ff:ff:ff:ff:ff:ff (All SIM / telephony / GSM data above is real; please handle with care) lshw reporting on USB and the like *-usb:2 description: USB
[Touch-packages] [Bug 1969241] Re: Network issue no IPv6 using Sierra Wireless EM7421 and mbim
** Description changed: Network issue no IPv6 using Sierra Wireless EM7421 and mbim Description:Ubuntu Jammy Jellyfish Release:22.04 Linux 5.15.0-25-generic I need to connect via GSM to Internet using IPv6. IPv6 not present in config. Internet connect works with IPv4 although issues seem to exist. EXPECTATION: IPv6 shall work properly like the EM7455 with same card in very similar machine, Ubuntu. IPv6 shall work properly like in Linux-Mint 20.3 on this machine, this setup. All using the same driver=cdc_mbim ENVIRONMENT: - SIM is working properly, - EM7421 latest firmware applied, - EM7421 capable doing IPv6 with this setup (according to spec + test with Win10); - "package" unknown, sorry. ModemManager probably? + - SIM is working properly, + - EM7421 latest firmware applied, + - EM7421 capable doing IPv6 with this setup (according to spec + test with Win10 + works with Linux Mint); - ASSUMPTION: - Missing IPv6 is a wrong config / bug in software. - IPv6 communication can be enabled. - Some enhancement / fix can enable IPv6 communication. + "package" not understood, sorry. ModemManager probably? + + ASSUMPTIONs: + - Missing IPv6 is a wrong config / bug in software / communication issue. + - IPv6 communication can be enabled. + - Some enhancement / fix can enable IPv6 communication. REMARK: Linux-Mint 20.3 una is capable of running the 'EM7421' in proper IPv6 "mode" (kernel 5.4.0-107-generic). - It uses driver=cdc_mbim as well + It uses driver=cdc_mbim as well. It shows other issues like missing provision of additional DNS server data, EUI64 state and the like. details: Actually no IPv6 available at all (IPv6 is expected to work): 3: wwan0: mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000 link/ether 6a:05:2c:26:95:58 brd ff:ff:ff:ff:ff:ff inet 10.34.85.36/29 brd 10.34.85.39 scope global noprefixroute wwan0 This is the Sierra Wireless GSM-Modem (working): sudo mbimcli --device=/dev/cdc-wdm0 --query-device-caps [/dev/cdc-wdm0] Device capabilities retrieved: Device type: 'remote' Cellular class: 'gsm' Voice class: 'no-voice' SIM class: 'removable' Data class: 'umts, hsdpa, hsupa, lte' SMS caps: 'pdu-receive, pdu-send' Ctrl caps: 'reg-manual' Max sessions: '8' Custom data class: 'unknown' Device ID: '356706140353162' Firmware info: 'SWI9X50C_01.14.03.00' Hardware info: 'EM7421' Attempt to start modem via mbim: pre: sudo service network-manager stop sudo systemctl disable ModemManager then Report sudo mbim-network /dev/cdc-wdm0 start Profile at '/etc/mbim-network.conf' not found... Querying subscriber ready status 'mbimcli -d /dev/cdc-wdm0 --query-subscriber-ready-status --no-close'... [/dev/cdc-wdm0] Subscriber ready status retrieved: Ready state: 'initialized' Subscriber ID: '262011905110762' SIM ICCID: '8949021788157884' Ready info: 'none' Telephone numbers: (1) '+491604282867' [/dev/cdc-wdm0] Session not closed: TRID: '3' Querying registration state 'mbimcli -d /dev/cdc-wdm0 --query-registration-state --no-open=3 --no-close'... [/dev/cdc-wdm0] Registration status: Network error: 'unknown' Register state: 'home' Register mode: 'automatic' Available data classes: 'lte' Current cellular class: 'gsm' Provider ID: '26201' Provider name: 'Telekom.de' Roaming text: 'unknown' Registration flags: 'packet-service-automatic-attach' [/dev/cdc-wdm0] Session not closed: TRID: '4' Attaching to packet service with 'mbimcli -d /dev/cdc-wdm0 --attach-packet-service --no-open=4 --no-close'... [/dev/cdc-wdm0] Successfully attached to packet service [/dev/cdc-wdm0] Packet service status: Network error: 'unknown' Packet service state: 'attached' Available data classes: 'lte' Uplink speed: '15000 bps' Downlink speed: '3 bps' [/dev/cdc-wdm0] Session not closed: TRID: '5' Starting network with 'mbimcli -d /dev/cdc-wdm0 --connect=apn='' --no-open=5 --no-close'... Network started successfully Saving state at /tmp/mbim-network-state-cdc-wdm0... (TRID: 7) status reported by ip a : 3: wwan0: mtu 1500 qdisc fq_codel state DOWN group default qlen 1000 link/ether 86:a6:1f:1a:ce:30 brd ff:ff:ff:ff:ff:ff try to bring it up: sudo ip link set dev wwan0 up (no error reported) new status reported by ip a : 3: wwan0: mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000 link/ether 86:a6:1f:1a:ce:30 brd ff:ff:ff:ff:ff:ff (All SIM / telephony / GSM data above is real; please handle with care) lshw reporting on USB and the like *-usb:2 description: USB controller product: Tiger Lake-LP USB 3.2 Gen 2x1 xHCI Host Controller vendor: Intel Corporation physical id: 14 bus info: pci@:00:14.0 versio
[Touch-packages] [Bug 1969241] Re: Network issue no IPv6 using Sierra Wireless EM7421 and mbim
** Description changed: Network issue no IPv6 using Sierra Wireless EM7421 and mbim Description:Ubuntu Jammy Jellyfish Release:22.04 Linux 5.15.0-25-generic I need to connect via GSM to Internet using IPv6. IPv6 not present in config. Internet connect works with IPv4 although issues seem to exist. EXPECTATION: - IPv6 shall work properly like the EM7455 with same card in very similar machine, Ubuntu. - IPv6 shall work properly like in Linux-Mint 20.3 on this machine, this setup. + IPv6 shall work properly like the EM7455 with same card in very similar machine, Ubuntu. + IPv6 shall work properly like in Linux-Mint 20.3 on this machine, this setup. All using the same driver=cdc_mbim ENVIRONMENT: SIM is working properly, EM7421 latest firmware applied, EM7421 capable doing IPv6 with this setup (according to spec + test with Win10); "package" unknown, sorry. ModemManager probably? ASSUMPTION: Missing IPv6 is a wrong config / bug in software. IPv6 communication can be enabled. Some enhancement / fix can enable IPv6 communication. REMARK: Linux-Mint 20.3 una is capable of running the 'EM7421' in proper IPv6 "mode" (kernel 5.4.0-107-generic). It uses driver=cdc_mbim as well details: Actually no IPv6 available at all (IPv6 is expected to work): 3: wwan0: mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000 link/ether 6a:05:2c:26:95:58 brd ff:ff:ff:ff:ff:ff inet 10.34.85.36/29 brd 10.34.85.39 scope global noprefixroute wwan0 This is the Sierra Wireless GSM-Modem (working): sudo mbimcli --device=/dev/cdc-wdm0 --query-device-caps [/dev/cdc-wdm0] Device capabilities retrieved: Device type: 'remote' Cellular class: 'gsm' Voice class: 'no-voice' SIM class: 'removable' Data class: 'umts, hsdpa, hsupa, lte' SMS caps: 'pdu-receive, pdu-send' Ctrl caps: 'reg-manual' Max sessions: '8' Custom data class: 'unknown' Device ID: '356706140353162' Firmware info: 'SWI9X50C_01.14.03.00' Hardware info: 'EM7421' Attempt to start modem via mbim: pre: sudo service network-manager stop sudo systemctl disable ModemManager then Report sudo mbim-network /dev/cdc-wdm0 start Profile at '/etc/mbim-network.conf' not found... Querying subscriber ready status 'mbimcli -d /dev/cdc-wdm0 --query-subscriber-ready-status --no-close'... [/dev/cdc-wdm0] Subscriber ready status retrieved: Ready state: 'initialized' Subscriber ID: '262011905110762' SIM ICCID: '8949021788157884' Ready info: 'none' Telephone numbers: (1) '+491604282867' [/dev/cdc-wdm0] Session not closed: TRID: '3' Querying registration state 'mbimcli -d /dev/cdc-wdm0 --query-registration-state --no-open=3 --no-close'... [/dev/cdc-wdm0] Registration status: Network error: 'unknown' Register state: 'home' Register mode: 'automatic' Available data classes: 'lte' Current cellular class: 'gsm' Provider ID: '26201' Provider name: 'Telekom.de' Roaming text: 'unknown' Registration flags: 'packet-service-automatic-attach' [/dev/cdc-wdm0] Session not closed: TRID: '4' Attaching to packet service with 'mbimcli -d /dev/cdc-wdm0 --attach-packet-service --no-open=4 --no-close'... [/dev/cdc-wdm0] Successfully attached to packet service [/dev/cdc-wdm0] Packet service status: Network error: 'unknown' Packet service state: 'attached' Available data classes: 'lte' Uplink speed: '15000 bps' Downlink speed: '3 bps' [/dev/cdc-wdm0] Session not closed: TRID: '5' Starting network with 'mbimcli -d /dev/cdc-wdm0 --connect=apn='' --no-open=5 --no-close'... Network started successfully Saving state at /tmp/mbim-network-state-cdc-wdm0... (TRID: 7) status reported by ip a : 3: wwan0: mtu 1500 qdisc fq_codel state DOWN group default qlen 1000 link/ether 86:a6:1f:1a:ce:30 brd ff:ff:ff:ff:ff:ff try to bring it up: sudo ip link set dev wwan0 up (no error reported) new status reported by ip a : 3: wwan0: mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000 link/ether 86:a6:1f:1a:ce:30 brd ff:ff:ff:ff:ff:ff (All SIM / telephony / GSM data above is real; please handle with care) lshw reporting on USB and the like *-usb:2 description: USB controller product: Tiger Lake-LP USB 3.2 Gen 2x1 xHCI Host Controller vendor: Intel Corporation physical id: 14 bus info: pci@:00:14.0 version: 20 width: 64 bits clock: 33MHz capabilities: pm msi xhci bus_master cap_list configuration: driver=xhci_hcd latency=0 resources: irq:155 memory:5c42-5c42 *-usbhost:0 product: xHCI Host Controller vendor: Linux 5.15.0-25-generic xhci-hcd
[Touch-packages] [Bug 1969241] Re: Network issue no IPv6 using Sierra Wireless EM7421 and mbim
** Description changed: Network issue no IPv6 using Sierra Wireless EM7421 and mbim Description:Ubuntu Jammy Jellyfish Release:22.04 Linux 5.15.0-25-generic I need to connect via GSM to Internet using IPv6. IPv6 not present in config. Internet connect works with IPv4 although issues seem to exist. EXPECTATION: - IPv6 shall work properly like the EM7455 with same card in very similar machine, Ubuntu. Using the same driver=cdc_mbim + IPv6 shall work properly like the EM7455 with same card in very similar machine, Ubuntu. + IPv6 shall work properly like in Linux-Mint 20.3 on this machine, this setup. + All using the same driver=cdc_mbim ENVIRONMENT: SIM is working properly, EM7421 latest firmware applied, EM7421 capable doing IPv6 with this setup (according to spec + test with Win10); - "package" unknown, sorry. + "package" unknown, sorry. ModemManager probably? ASSUMPTION: Missing IPv6 is a wrong config / bug in software. IPv6 communication can be enabled. Some enhancement / fix can enable IPv6 communication. - REMARK: - Linux-Mint 20.3 una is capable of running the 'EM7421' in proper IPv6 "mode" (kernel 5.4.0-107-generic). + REMARK: + Linux-Mint 20.3 una is capable of running the 'EM7421' in proper IPv6 "mode" (kernel 5.4.0-107-generic). It uses driver=cdc_mbim as well details: Actually no IPv6 available at all (IPv6 is expected to work): 3: wwan0: mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000 link/ether 6a:05:2c:26:95:58 brd ff:ff:ff:ff:ff:ff inet 10.34.85.36/29 brd 10.34.85.39 scope global noprefixroute wwan0 This is the Sierra Wireless GSM-Modem (working): sudo mbimcli --device=/dev/cdc-wdm0 --query-device-caps [/dev/cdc-wdm0] Device capabilities retrieved: Device type: 'remote' Cellular class: 'gsm' Voice class: 'no-voice' SIM class: 'removable' Data class: 'umts, hsdpa, hsupa, lte' SMS caps: 'pdu-receive, pdu-send' Ctrl caps: 'reg-manual' Max sessions: '8' Custom data class: 'unknown' Device ID: '356706140353162' Firmware info: 'SWI9X50C_01.14.03.00' Hardware info: 'EM7421' Attempt to start modem via mbim: pre: sudo service network-manager stop sudo systemctl disable ModemManager then Report sudo mbim-network /dev/cdc-wdm0 start Profile at '/etc/mbim-network.conf' not found... Querying subscriber ready status 'mbimcli -d /dev/cdc-wdm0 --query-subscriber-ready-status --no-close'... [/dev/cdc-wdm0] Subscriber ready status retrieved: Ready state: 'initialized' Subscriber ID: '262011905110762' SIM ICCID: '8949021788157884' Ready info: 'none' Telephone numbers: (1) '+491604282867' [/dev/cdc-wdm0] Session not closed: TRID: '3' Querying registration state 'mbimcli -d /dev/cdc-wdm0 --query-registration-state --no-open=3 --no-close'... [/dev/cdc-wdm0] Registration status: Network error: 'unknown' Register state: 'home' Register mode: 'automatic' Available data classes: 'lte' Current cellular class: 'gsm' Provider ID: '26201' Provider name: 'Telekom.de' Roaming text: 'unknown' Registration flags: 'packet-service-automatic-attach' [/dev/cdc-wdm0] Session not closed: TRID: '4' Attaching to packet service with 'mbimcli -d /dev/cdc-wdm0 --attach-packet-service --no-open=4 --no-close'... [/dev/cdc-wdm0] Successfully attached to packet service [/dev/cdc-wdm0] Packet service status: Network error: 'unknown' Packet service state: 'attached' Available data classes: 'lte' Uplink speed: '15000 bps' Downlink speed: '3 bps' [/dev/cdc-wdm0] Session not closed: TRID: '5' Starting network with 'mbimcli -d /dev/cdc-wdm0 --connect=apn='' --no-open=5 --no-close'... Network started successfully Saving state at /tmp/mbim-network-state-cdc-wdm0... (TRID: 7) status reported by ip a : 3: wwan0: mtu 1500 qdisc fq_codel state DOWN group default qlen 1000 link/ether 86:a6:1f:1a:ce:30 brd ff:ff:ff:ff:ff:ff try to bring it up: sudo ip link set dev wwan0 up (no error reported) new status reported by ip a : 3: wwan0: mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000 link/ether 86:a6:1f:1a:ce:30 brd ff:ff:ff:ff:ff:ff (All SIM / telephony / GSM data above is real; please handle with care) lshw reporting on USB and the like *-usb:2 description: USB controller product: Tiger Lake-LP USB 3.2 Gen 2x1 xHCI Host Controller vendor: Intel Corporation physical id: 14 bus info: pci@:00:14.0 version: 20 width: 64 bits clock: 33MHz capabilities: pm msi xhci bus_master cap_list configuration: driver=xhci_hcd latency=0 resources: irq:155 memory:5c42-5c42 *-usbhost:0 product:
[Touch-packages] [Bug 1969241] [NEW] Network issue no IPv6 using Sierra Wireless EM7421 and mbim
You have been subscribed to a public bug: Network issue no IPv6 using Sierra Wireless EM7421 and mbim Description:Ubuntu Jammy Jellyfish Release:22.04 Linux 5.15.0-25-generic I need to connect via GSM to Internet using IPv6. IPv6 not present in config. Internet connect works with IPv4 although issues seem to exist. EXPECTATION: IPv6 shall work properly like the EM7455 with same card in very similar machine, Ubuntu. IPv6 shall work properly like in Linux-Mint 20.3 on this machine, this setup. All using the same driver=cdc_mbim ENVIRONMENT: SIM is working properly, EM7421 latest firmware applied, EM7421 capable doing IPv6 with this setup (according to spec + test with Win10); "package" unknown, sorry. ModemManager probably? ASSUMPTION: Missing IPv6 is a wrong config / bug in software. IPv6 communication can be enabled. Some enhancement / fix can enable IPv6 communication. REMARK: Linux-Mint 20.3 una is capable of running the 'EM7421' in proper IPv6 "mode" (kernel 5.4.0-107-generic). It uses driver=cdc_mbim as well details: Actually no IPv6 available at all (IPv6 is expected to work): 3: wwan0: mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000 link/ether 6a:05:2c:26:95:58 brd ff:ff:ff:ff:ff:ff inet 10.34.85.36/29 brd 10.34.85.39 scope global noprefixroute wwan0 This is the Sierra Wireless GSM-Modem (working): sudo mbimcli --device=/dev/cdc-wdm0 --query-device-caps [/dev/cdc-wdm0] Device capabilities retrieved: Device type: 'remote' Cellular class: 'gsm' Voice class: 'no-voice' SIM class: 'removable' Data class: 'umts, hsdpa, hsupa, lte' SMS caps: 'pdu-receive, pdu-send' Ctrl caps: 'reg-manual' Max sessions: '8' Custom data class: 'unknown' Device ID: '356706140353162' Firmware info: 'SWI9X50C_01.14.03.00' Hardware info: 'EM7421' Attempt to start modem via mbim: pre: sudo service network-manager stop sudo systemctl disable ModemManager then Report sudo mbim-network /dev/cdc-wdm0 start Profile at '/etc/mbim-network.conf' not found... Querying subscriber ready status 'mbimcli -d /dev/cdc-wdm0 --query-subscriber-ready-status --no-close'... [/dev/cdc-wdm0] Subscriber ready status retrieved: Ready state: 'initialized' Subscriber ID: '262011905110762' SIM ICCID: '8949021788157884' Ready info: 'none' Telephone numbers: (1) '+491604282867' [/dev/cdc-wdm0] Session not closed: TRID: '3' Querying registration state 'mbimcli -d /dev/cdc-wdm0 --query-registration-state --no-open=3 --no-close'... [/dev/cdc-wdm0] Registration status: Network error: 'unknown' Register state: 'home' Register mode: 'automatic' Available data classes: 'lte' Current cellular class: 'gsm' Provider ID: '26201' Provider name: 'Telekom.de' Roaming text: 'unknown' Registration flags: 'packet-service-automatic-attach' [/dev/cdc-wdm0] Session not closed: TRID: '4' Attaching to packet service with 'mbimcli -d /dev/cdc-wdm0 --attach-packet-service --no-open=4 --no-close'... [/dev/cdc-wdm0] Successfully attached to packet service [/dev/cdc-wdm0] Packet service status: Network error: 'unknown' Packet service state: 'attached' Available data classes: 'lte' Uplink speed: '15000 bps' Downlink speed: '3 bps' [/dev/cdc-wdm0] Session not closed: TRID: '5' Starting network with 'mbimcli -d /dev/cdc-wdm0 --connect=apn='' --no-open=5 --no-close'... Network started successfully Saving state at /tmp/mbim-network-state-cdc-wdm0... (TRID: 7) status reported by ip a : 3: wwan0: mtu 1500 qdisc fq_codel state DOWN group default qlen 1000 link/ether 86:a6:1f:1a:ce:30 brd ff:ff:ff:ff:ff:ff try to bring it up: sudo ip link set dev wwan0 up (no error reported) new status reported by ip a : 3: wwan0: mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000 link/ether 86:a6:1f:1a:ce:30 brd ff:ff:ff:ff:ff:ff (All SIM / telephony / GSM data above is real; please handle with care) lshw reporting on USB and the like *-usb:2 description: USB controller product: Tiger Lake-LP USB 3.2 Gen 2x1 xHCI Host Controller vendor: Intel Corporation physical id: 14 bus info: pci@:00:14.0 version: 20 width: 64 bits clock: 33MHz capabilities: pm msi xhci bus_master cap_list configuration: driver=xhci_hcd latency=0 resources: irq:155 memory:5c42-5c42 *-usbhost:0 product: xHCI Host Controller vendor: Linux 5.15.0-25-generic xhci-hcd physical id: 0 bus info: usb@3 logical name: usb3 version: 5.15 capabilities: usb-2.00 configuration: driver=hub slots=12 speed=480Mbit/s *-usb:0 description: Communication device product: EM7421 vendor: Sierra Wireless