[Touch-packages] [Bug 313149] Re: deluge produces zombie browser process when launched through about window
** Changed in: python Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-defaults in Ubuntu. https://bugs.launchpad.net/bugs/313149 Title: deluge produces zombie browser process when launched through about window Status in Deluge: Won't Fix Status in Python: Incomplete Status in deluge package in Ubuntu: Invalid Status in python-defaults package in Ubuntu: Triaged Bug description: Binary package hint: deluge-torrent when a new browser process is started by clicking on the link in the about window, it is not harvested after it exits. it is remaining in the process list as zombie/defunct until deluge exits too. deluge-torrent 0.5.9.3-1 ubuntu 8.10 To manage notifications about this bug go to: https://bugs.launchpad.net/deluge/+bug/313149/+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 1945527] Re: Update tzdata to version 2021a-2
This was fixed for xenial/esm with tzdata 2021a-2ubuntu0.16.04+esm1 and for trusty/esm with tzdata 2021a-2ubuntu0.14.04+esm1. Thanks Brian, for preparing these updates! ** Changed in: tzdata (Ubuntu Xenial) Status: New => Fix Released ** Also affects: tzdata (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: tzdata (Ubuntu Trusty) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1945527 Title: Update tzdata to version 2021a-2 Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Trusty: Fix Released Status in tzdata source package in Xenial: Fix Released Status in tzdata source package in Bionic: Fix Released Status in tzdata source package in Focal: Fix Released Status in tzdata source package in Hirsute: Fix Released Bug description: New upstream version affecting the following timestamp: $region/$timezone = Pacific/Apia Verification is done with 'zdump'. The first timezone that gets changed in the updated package is dumped with 'zdump -v $region/$timezone_that_changed' (this needs to be greped for in /usr/share/zoneinfo/). [For example: 'zdump -v Pacific/Apia'.] This is compared to the same output after the updated package got installed. If those are different the verification is considered done. [Test Case for all releases] 1) zdump -v Pacific/Apia | grep 2021 For releases with ICU timezone data verification is done using the following with dates before and after the change: [Test Case for releases >= 20.04 LTS] 1) sudo apt-get install python3-icu 2) python3 -c 'from datetime import datetime; from icu import ICUtzinfo, TimeZone; tz = ICUtzinfo(TimeZone.createTimeZone('Pacific/Apia')); print(str(tz.utcoffset(datetime(2021, 9, 27' Additionally, an upstream update of tzdata removed the 'old' SystemV timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and earlier releases. Subsequently, these should be checked for using the following: [Test Case for releases <= 20.04 LTS] diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | cut -d' ' -f2-) Nothing should be returned by the above command. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1945527/+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 1948364] [NEW] Static IP set in /etc/network/interfaces sometimes doesn't set properly after reboot
Public bug reported: I use ubuntu20.04 and set static IP 192.168.11.22 in /etc/network/interfaces. Most time it could work but sometimes the IP changed to 192.168.11.105, which same to be a DHCP IP. I checked the syslog and journalctl, find that eth0 same to disconnect and be re- configured by dhcilent.: Oct 22 10:10:03 sv-host NetworkManager[502]: [1634868603.0490] device (eth0): link disconnected (calling deferred action) Oct 22 10:10:03 sv-host NetworkManager[502]: [1634868603.0498] device (eth0): state change: activated -> unavailable (reason 'carrier-changed') [100 20 40] But I don't know which lead eth0 disconnect. Why eth0 doesn't get static IP but DHCP IP when it reconnected? ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Attachment added: "journalctl log about static IP" https://bugs.launchpad.net/bugs/1948364/+attachment/5534988/+files/Static_IP_loss_2021-10-22_10-27-30.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1948364 Title: Static IP set in /etc/network/interfaces sometimes doesn't set properly after reboot Status in network-manager package in Ubuntu: New Bug description: I use ubuntu20.04 and set static IP 192.168.11.22 in /etc/network/interfaces. Most time it could work but sometimes the IP changed to 192.168.11.105, which same to be a DHCP IP. I checked the syslog and journalctl, find that eth0 same to disconnect and be re- configured by dhcilent.: Oct 22 10:10:03 sv-host NetworkManager[502]: [1634868603.0490] device (eth0): link disconnected (calling deferred action) Oct 22 10:10:03 sv-host NetworkManager[502]: [1634868603.0498] device (eth0): state change: activated -> unavailable (reason 'carrier-changed') [100 20 40] But I don't know which lead eth0 disconnect. Why eth0 doesn't get static IP but DHCP IP when it reconnected? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1948364/+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 413278]
thank you guys for sharing your tips. https://www.depannage-auto- dijon.com -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to eglibc in Ubuntu. https://bugs.launchpad.net/bugs/413278 Title: stack protector guard value does not lead with a NULL byte Status in GLibC: Fix Released Status in eglibc package in Ubuntu: Fix Released Status in glibc package in Ubuntu: Invalid Status in eglibc source package in Jaunty: Invalid Status in glibc source package in Jaunty: Fix Released Status in eglibc source package in Karmic: Fix Released Status in glibc source package in Karmic: Invalid Bug description: IMPACT: stack protections are weakened due to strcpy function being able to write the stack guard (since it does not start with a zero byte). ADDRESSED: correctly implement leading zero, as done in Karmic. DISCUSSION: regression potential is low, since the patch is isolated and well tested. TEST CASE: $ bzr branch lp:~ubuntu-bugcontrol/qa-regression-testing/master qa-regression-testing $ cd qa-regression-testing/scripts $ ./test-glibc-security.py -v Build helper tools ... (9.10) ok glibc heap protection ... ok sprintf not pre-truncated with -D_FORTIFY_SOURCE=2 ... ok glibc pointer obfuscation ... ok Password hashes ... (sha512) ok Stack guard exists ... ok Stack guard leads with zero byte ... FAIL Stack guard is randomized ... ok == FAIL: Stack guard leads with zero byte -- Traceback (most recent call last): File "./test-glibc-security.py", line 170, in test_81_stack_guard_leads_zero self.assertEqual(one.startswith('00 '), expected, one) AssertionError: 62 55 59 69 cd 20 39 80 -- Ran 8 tests in 0.145s FAILED (failures=1) expected outcome: 0 failures. ProblemType: Bug Architecture: amd64 Date: Thu Aug 13 13:59:02 2009 Dependencies: findutils 4.4.2-1 gcc-4.4-base 4.4.1-1ubuntu3 libc6 2.10.1-0ubuntu6 libgcc1 1:4.4.1-1ubuntu3 DistroRelease: Ubuntu 9.10 Package: libc6 2.10.1-0ubuntu6 ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-5.24-generic SourcePackage: eglibc Uname: Linux 2.6.31-5-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/glibc/+bug/413278/+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 1948357] Re: sshd have no USER_LOGOUT audit event
first report here: https://listman.redhat.com/archives/linux- audit/2021-October/msg00069.html -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1948357 Title: sshd have no USER_LOGOUT audit event Status in openssh package in Ubuntu: New Bug description: ubuntu 18.04 lizj@FNSTPC:~$ sudo aureport -e -i --summary | grep USER 43241 USER_END 16946 USER_START 16718 USER_ACCT 658 USER_AUTH 543 USER_CMD 255 USER_LOGIN 9 USER_ROLE_CHANGE 5 USER_ERR 2 USER_CHAUTHTOK 1 ADD_USER lizj@FNSTPC:~/.local/bin$ dpkg -l | grep openssh ii openssh-client1:7.6p1-4ubuntu0.5 amd64secure shell (SSH) client, for secure access to remote machines ii openssh-server1:7.6p1-4ubuntu0.5 amd64secure shell (SSH) server, for secure access from remote machines ii openssh-sftp-server 1:7.6p1-4ubuntu0.5 amd64secure shell (SSH) sftp server module, for SFTP access from remote machines lizj@FNSTPC:~/.local/bin$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.6 LTS Release: 18.04 Codename: bionic while in my fedora 33 host, it includes USER_LOGOUT as below fedora 33 [root@iaas-rpma linux]# aureport -e -i --summary | grep USER 7356 CRYPTO_KEY_USER 2103 USER_START 1649 USER_END 1268 USER_ACCT 1108 USER_ROLE_CHANGE 1029 USER_AUTH 895 USER_LOGIN 789 USER_LOGOUT 60 USER_CMD 14 USER_ERR 3 USER_MGMT 3 USER_CHAUTHTOK 1 ADD_USER [root@iaas-rpma ~]# rpm -qa | grep openssh openssh-8.4p1-1.1.fc33.x86_64 openssh-clients-8.4p1-1.1.fc33.x86_64 openssh-server-8.4p1-1.1.fc33.x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1948357/+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 1948357] [NEW] sshd have no USER_LOGOUT audit event
Public bug reported: ubuntu 18.04 lizj@FNSTPC:~$ sudo aureport -e -i --summary | grep USER 43241 USER_END 16946 USER_START 16718 USER_ACCT 658 USER_AUTH 543 USER_CMD 255 USER_LOGIN 9 USER_ROLE_CHANGE 5 USER_ERR 2 USER_CHAUTHTOK 1 ADD_USER lizj@FNSTPC:~/.local/bin$ dpkg -l | grep openssh ii openssh-client1:7.6p1-4ubuntu0.5 amd64secure shell (SSH) client, for secure access to remote machines ii openssh-server1:7.6p1-4ubuntu0.5 amd64secure shell (SSH) server, for secure access from remote machines ii openssh-sftp-server 1:7.6p1-4ubuntu0.5 amd64secure shell (SSH) sftp server module, for SFTP access from remote machines lizj@FNSTPC:~/.local/bin$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.6 LTS Release:18.04 Codename: bionic while in my fedora 33 host, it includes USER_LOGOUT as below fedora 33 [root@iaas-rpma linux]# aureport -e -i --summary | grep USER 7356 CRYPTO_KEY_USER 2103 USER_START 1649 USER_END 1268 USER_ACCT 1108 USER_ROLE_CHANGE 1029 USER_AUTH 895 USER_LOGIN 789 USER_LOGOUT 60 USER_CMD 14 USER_ERR 3 USER_MGMT 3 USER_CHAUTHTOK 1 ADD_USER [root@iaas-rpma ~]# rpm -qa | grep openssh openssh-8.4p1-1.1.fc33.x86_64 openssh-clients-8.4p1-1.1.fc33.x86_64 openssh-server-8.4p1-1.1.fc33.x86_64 ** Affects: openssh (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1948357 Title: sshd have no USER_LOGOUT audit event Status in openssh package in Ubuntu: New Bug description: ubuntu 18.04 lizj@FNSTPC:~$ sudo aureport -e -i --summary | grep USER 43241 USER_END 16946 USER_START 16718 USER_ACCT 658 USER_AUTH 543 USER_CMD 255 USER_LOGIN 9 USER_ROLE_CHANGE 5 USER_ERR 2 USER_CHAUTHTOK 1 ADD_USER lizj@FNSTPC:~/.local/bin$ dpkg -l | grep openssh ii openssh-client1:7.6p1-4ubuntu0.5 amd64secure shell (SSH) client, for secure access to remote machines ii openssh-server1:7.6p1-4ubuntu0.5 amd64secure shell (SSH) server, for secure access from remote machines ii openssh-sftp-server 1:7.6p1-4ubuntu0.5 amd64secure shell (SSH) sftp server module, for SFTP access from remote machines lizj@FNSTPC:~/.local/bin$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.6 LTS Release: 18.04 Codename: bionic while in my fedora 33 host, it includes USER_LOGOUT as below fedora 33 [root@iaas-rpma linux]# aureport -e -i --summary | grep USER 7356 CRYPTO_KEY_USER 2103 USER_START 1649 USER_END 1268 USER_ACCT 1108 USER_ROLE_CHANGE 1029 USER_AUTH 895 USER_LOGIN 789 USER_LOGOUT 60 USER_CMD 14 USER_ERR 3 USER_MGMT 3 USER_CHAUTHTOK 1 ADD_USER [root@iaas-rpma ~]# rpm -qa | grep openssh openssh-8.4p1-1.1.fc33.x86_64 openssh-clients-8.4p1-1.1.fc33.x86_64 openssh-server-8.4p1-1.1.fc33.x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1948357/+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 1948005] Re: Dell 6000 dock freeze and restart since october 19.
** Summary changed: - Dell 6000 freeze and restart since october 19. + Dell 6000 dock freeze and restart since october 19. ** Package changed: xorg (Ubuntu) => linux-oem-5.10 (Ubuntu) ** Tags added: regression-update ** Tags added: displaylink evdi ** Summary changed: - Dell 6000 dock freeze and restart since october 19. + Dell 6000 dock freeze and restart since October 19. -- 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/1948005 Title: Dell 6000 dock freeze and restart since October 19. Status in linux-oem-5.10 package in Ubuntu: New Bug description: Ramdomly my external display (conected via HDMI over a dell 6000 displaylink port) stop working, gone black, and then restart. Buy I notice that all devices conected to dell 6000 stop working. It happens since october 19 ubuntu auto update. I need this continue working as it was before that update. Description: Ubuntu 20.04.3 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68 Uname: Linux 5.10.0-1050-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 21 08:16:15 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: evdi, 1.9.1, 5.10.0-1049-oem, x86_64: installed evdi, 1.9.1, 5.10.0-1050-oem, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:8a56] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0a29] InstallationDate: Installed on 2021-08-18 (63 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. Vostro 3401 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1050-oem root=UUID=d63f71be-78d3-412a-95ce-c1fd7fc0b432 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/31/2021 dmi.bios.release: 1.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.name: 0790WT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd05/31/2021:br1.6:svnDellInc.:pnVostro3401:pvr:sku0A29:rvnDellInc.:rn0790WT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 3401 dmi.product.sku: 0A29 dmi.sys.vendor: Dell Inc. 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.3 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.10/+bug/1948005/+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 1948339] Re: Logon screen can be bypassed using various shortcuts
Your daughter does good work :) Thanks ** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1948339 Title: Logon screen can be bypassed using various shortcuts Status in Ubuntu MATE: New Status in arctica-greeter package in Ubuntu: New Status in lightdm package in Ubuntu: New Status in mate-settings-daemon package in Ubuntu: New Bug description: Hi, my little daughter discovered a logon screen bypass in Ubuntu Mate 21.10 after hitting the keyboard for a while. It turns out that several keyboard shortcuts are allowed while Ubuntu Mate is locked (arctica-greeter): - Mod4 + S (mate-search-tool) - Mod4 + E (Open Caja / File Explorer) - CTRL + Shift + Esc (mate-system-monitor) - PRNT (Screenshot) All of the mentioned shortcuts could be used to spawn a file explorer (Caja) or various other binaries as user "lightdm", who owns the logon screen. Although an interactive terminal like mate-terminal, xterm, lxterm etc. could not be opened directly, there are various options to run commands as the lightdm user, for example by creating a shell script using "caja", and execute it directly using the GUI. I've attached Proof-of-Concept GIFs for all shortcuts mentioned above. There might be additional shortcuts that could be used to achieve the same, however I'm not aware about every shortcut that is configured, but I suppose that the root cause is located somewhere in arctica- greeter, rather than within every single binary launched by shortcuts. The bug was reproduced on a fresh installation of Ubuntu Mate 21.10. I haven't tested other versions of Ubuntu Mate yet. Please find additional version details below: $ apt-cache policy lightdm lightdm: Installed: 1.30.0-0ubuntu4 Candidate: 1.30.0-0ubuntu4 Version table: *** 1.30.0-0ubuntu4 500 500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy arctica-greeter arctica-greeter: Installed: 0.99.1.5-2nmu1 Candidate: 0.99.1.5-2nmu1 Version table: *** 0.99.1.5-2nmu1 500 500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages 100 /var/lib/dpkg/status Thanks, Basti To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1948339/+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 1948346] Re: package libnih1 1.0.3-6ubuntu2 failed to install/upgrade: package libnih1:amd64 (1.0.3-12) with field 'Multi-Arch: no' is not co-installable with libnih1 which has m
Easy to fix: sudo apt purge libnih1:i386 libnih-dbus1:i386 && sudo apt upgrade -y -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnih in Ubuntu. https://bugs.launchpad.net/bugs/1948346 Title: package libnih1 1.0.3-6ubuntu2 failed to install/upgrade: package libnih1:amd64 (1.0.3-12) with field 'Multi-Arch: no' is not co- installable with libnih1 which has multiple installed instances Status in libnih package in Ubuntu: New Bug description: Errors were encountered while processing: /tmp/apt-dpkg-install-S93V5u/404-libnih-dbus1_1.0.3-12_amd64.deb /tmp/apt-dpkg-install-S93V5u/405-libnih1_1.0.3-12_amd64.deb Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 21.10 Package: libnih1 1.0.3-6ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-37.41-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Oct 21 18:10:42 2021 DuplicateSignature: package:libnih1:1.0.3-6ubuntu2 Unpacking libnetaddr-ip-perl (4.079+dfsg-1build6) over (4.079+dfsg-1build5) ... dpkg: error processing archive /tmp/apt-dpkg-install-S93V5u/404-libnih-dbus1_1.0.3-12_amd64.deb (--unpack): package libnih-dbus1:amd64 (1.0.3-12) with field 'Multi-Arch: no' is not co-installable with libnih-dbus1 which has multiple installed instances ErrorMessage: package libnih1:amd64 (1.0.3-12) with field 'Multi-Arch: no' is not co-installable with libnih1 which has multiple installed instances Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1build1 PythonDetails: /usr/bin/python3.9, Python 3.9.7, python-is-python3, 3.9.2-1 RelatedPackageVersions: dpkg 1.20.9ubuntu2 apt 2.3.9 SourcePackage: libnih Title: package libnih1 1.0.3-6ubuntu2 failed to install/upgrade: package libnih1:amd64 (1.0.3-12) with field 'Multi-Arch: no' is not co-installable with libnih1 which has multiple installed instances UpgradeStatus: Upgraded to impish on 2021-10-21 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnih/+bug/1948346/+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 1948346] [NEW] package libnih1 1.0.3-6ubuntu2 failed to install/upgrade: package libnih1:amd64 (1.0.3-12) with field 'Multi-Arch: no' is not co-installable with libnih1 which has
Public bug reported: Errors were encountered while processing: /tmp/apt-dpkg-install-S93V5u/404-libnih-dbus1_1.0.3-12_amd64.deb /tmp/apt-dpkg-install-S93V5u/405-libnih1_1.0.3-12_amd64.deb Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 21.10 Package: libnih1 1.0.3-6ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-37.41-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Oct 21 18:10:42 2021 DuplicateSignature: package:libnih1:1.0.3-6ubuntu2 Unpacking libnetaddr-ip-perl (4.079+dfsg-1build6) over (4.079+dfsg-1build5) ... dpkg: error processing archive /tmp/apt-dpkg-install-S93V5u/404-libnih-dbus1_1.0.3-12_amd64.deb (--unpack): package libnih-dbus1:amd64 (1.0.3-12) with field 'Multi-Arch: no' is not co-installable with libnih-dbus1 which has multiple installed instances ErrorMessage: package libnih1:amd64 (1.0.3-12) with field 'Multi-Arch: no' is not co-installable with libnih1 which has multiple installed instances Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1build1 PythonDetails: /usr/bin/python3.9, Python 3.9.7, python-is-python3, 3.9.2-1 RelatedPackageVersions: dpkg 1.20.9ubuntu2 apt 2.3.9 SourcePackage: libnih Title: package libnih1 1.0.3-6ubuntu2 failed to install/upgrade: package libnih1:amd64 (1.0.3-12) with field 'Multi-Arch: no' is not co-installable with libnih1 which has multiple installed instances UpgradeStatus: Upgraded to impish on 2021-10-21 (0 days ago) ** Affects: libnih (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package impish need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnih in Ubuntu. https://bugs.launchpad.net/bugs/1948346 Title: package libnih1 1.0.3-6ubuntu2 failed to install/upgrade: package libnih1:amd64 (1.0.3-12) with field 'Multi-Arch: no' is not co- installable with libnih1 which has multiple installed instances Status in libnih package in Ubuntu: New Bug description: Errors were encountered while processing: /tmp/apt-dpkg-install-S93V5u/404-libnih-dbus1_1.0.3-12_amd64.deb /tmp/apt-dpkg-install-S93V5u/405-libnih1_1.0.3-12_amd64.deb Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 21.10 Package: libnih1 1.0.3-6ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-37.41-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Oct 21 18:10:42 2021 DuplicateSignature: package:libnih1:1.0.3-6ubuntu2 Unpacking libnetaddr-ip-perl (4.079+dfsg-1build6) over (4.079+dfsg-1build5) ... dpkg: error processing archive /tmp/apt-dpkg-install-S93V5u/404-libnih-dbus1_1.0.3-12_amd64.deb (--unpack): package libnih-dbus1:amd64 (1.0.3-12) with field 'Multi-Arch: no' is not co-installable with libnih-dbus1 which has multiple installed instances ErrorMessage: package libnih1:amd64 (1.0.3-12) with field 'Multi-Arch: no' is not co-installable with libnih1 which has multiple installed instances Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1build1 PythonDetails: /usr/bin/python3.9, Python 3.9.7, python-is-python3, 3.9.2-1 RelatedPackageVersions: dpkg 1.20.9ubuntu2 apt 2.3.9 SourcePackage: libnih Title: package libnih1 1.0.3-6ubuntu2 failed to install/upgrade: package libnih1:amd64 (1.0.3-12) with field 'Multi-Arch: no' is not co-installable with libnih1 which has multiple installed instances UpgradeStatus: Upgraded to impish on 2021-10-21 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnih/+bug/1948346/+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 1947920] Re: tracker-miner-f 100% CPU and slows system down
No problems all done: https://gitlab.gnome.org/GNOME/tracker/-/issues/334 ** Bug watch added: gitlab.gnome.org/GNOME/tracker/-/issues #334 https://gitlab.gnome.org/GNOME/tracker/-/issues/334 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1947920 Title: tracker-miner-f 100% CPU and slows system down Status in tracker package in Ubuntu: New Bug description: tracker-miner-f has been using 100% CPU and my system making it almost unresponsive. This happens around once a month or so when I boot up. It sometimes lasts for a number of days (or a number of resets) until the system becomes responsive again. The command "tracker status" always shows the same thing: "Estimated less than one second left" although it appears that everything is already indexed because the file and folder counts do not increase. Even so tracker-miner-f is still showing 100% CPU inspiron@Inspiron-7348:~$ tracker status Currently indexed: 101154 files, 16046 folders Remaining space on database partition: 160.5 GB (64.11%) Data is still being indexed: Estimated less than one second left inspiron@Inspiron-7348:~$ tracker status Currently indexed: 101155 files, 16045 folders Remaining space on database partition: 161.1 GB (64.31%) Data is still being indexed: Estimated 01h 19m 03s left ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: tracker 2.3.6-0ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Oct 21 08:25:58 2021 InstallationDate: Installed on 2021-06-28 (114 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: tracker UpgradeStatus: No upgrade log present (probably fresh install) UPDATE I have now reset the tracker and it seems to be going through and indexing everything again. tracker reset --hard Now tracker-miner-f has re-indexed everything and tracker-extract and tracker-store are running. UPDATE 2 The tracker reset completed indexing everything and the went into idle state. However when rebooting, tracker-miner-f went to 100% CPU once again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1947920/+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 1947800] Re: /usr/share/apport/whoopsie-upload-all:zlib.error:/usr/share/apport/whoopsie-upload-all@196:collect_info:process_report:add_gdb_info:gdb_command:write:read:readinto:r
** Also affects: apport (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: apport (Ubuntu Impish) Importance: Undecided Status: New ** Tags removed: rls-ii-incoming -- 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/1947800 Title: /usr/share/apport/whoopsie-upload- all:zlib.error:/usr/share/apport/whoopsie-upload- all@196:collect_info:process_report:add_gdb_info:gdb_command:write:read:readinto:read Status in apport package in Ubuntu: New Status in apport source package in Impish: New Status in apport source package in Jammy: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.11-0ubuntu70, the problem page at https://errors.ubuntu.com/problem/7120f8aebdf09e9dca39196d035eec234071e800 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1947800/+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 1947800] Re: /usr/share/apport/whoopsie-upload-all:zlib.error:/usr/share/apport/whoopsie-upload-all@196:collect_info:process_report:add_gdb_info:gdb_command:write:read:readinto:r
** Tags added: fr-1816 -- 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/1947800 Title: /usr/share/apport/whoopsie-upload- all:zlib.error:/usr/share/apport/whoopsie-upload- all@196:collect_info:process_report:add_gdb_info:gdb_command:write:read:readinto:read Status in apport package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.11-0ubuntu70, the problem page at https://errors.ubuntu.com/problem/7120f8aebdf09e9dca39196d035eec234071e800 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1947800/+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 1946481] Re: GNOME Control Center cannot connect to ModemManager with "org.freedesktop.DBus.Error.AccessDenied"
** Attachment added: "Running as normal user" https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1946481/+attachment/5534920/+files/Capture%20d%E2%80%99%C3%A9cran%20de%202021-10-21%2015-19-34.png -- 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/1946481 Title: GNOME Control Center cannot connect to ModemManager with "org.freedesktop.DBus.Error.AccessDenied" Status in modemmanager package in Ubuntu: New Bug description: Upgraded my laptop (ThinkPad P14s Gen2) from 21.04 to 21.10, trying to get access to Modem Manager fails with: > error: couldn't create manager: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied This was working on 21.04. STR: - Open Settings, go to "Network" OR - mmcli -m 0 Running mmcli as root workaround the problem, but I'm not able to use network applet to connect my modem. > $ id uid=1000(alex) gid=1000(alex) groupes=1000(alex),4(adm),6(disk),20(dialout),24(cdrom),27(sudo),30(dip),44(video),46(plugdev),107(lpadmin),124(sambashare),137(libvirtd),155(docker) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1946481/+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 1946481] Re: GNOME Control Center cannot connect to ModemManager with "org.freedesktop.DBus.Error.AccessDenied"
Running GNOME Control Center as root (not a good idea, I know), clearly gets the ModemManager connection to work. ** Attachment added: "GNOME Control Center (root)" https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1946481/+attachment/5534919/+files/Capture%20d%E2%80%99%C3%A9cran%20de%202021-10-21%2015-19-24.png -- 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/1946481 Title: GNOME Control Center cannot connect to ModemManager with "org.freedesktop.DBus.Error.AccessDenied" Status in modemmanager package in Ubuntu: New Bug description: Upgraded my laptop (ThinkPad P14s Gen2) from 21.04 to 21.10, trying to get access to Modem Manager fails with: > error: couldn't create manager: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied This was working on 21.04. STR: - Open Settings, go to "Network" OR - mmcli -m 0 Running mmcli as root workaround the problem, but I'm not able to use network applet to connect my modem. > $ id uid=1000(alex) gid=1000(alex) groupes=1000(alex),4(adm),6(disk),20(dialout),24(cdrom),27(sudo),30(dip),44(video),46(plugdev),107(lpadmin),124(sambashare),137(libvirtd),155(docker) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1946481/+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 1945969] Re: Update Vala to 0.52.6 in Impish
** Changed in: libunity (Ubuntu Impish) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libunity in Ubuntu. https://bugs.launchpad.net/bugs/1945969 Title: Update Vala to 0.52.6 in Impish Status in libunity package in Ubuntu: Fix Released Status in vala package in Ubuntu: Fix Released Status in libunity source package in Impish: Won't Fix Status in vala source package in Impish: Fix Released Bug description: The 0.52.x series is receiving further bug fix releases for GNOME 40.x. See https://wiki.gnome.org/Projects/Vala Upstream changes since 0.52.5: Vala 0.52.6 === * Various improvements and bug fixes: - codegen: + Fix property access inside opaque compact class + Add type declaration for implicit temporary local variable - vala: + Warn about unsupported cast to void and drop it [#1070] + Don't restrict element type of GLib.Array [#1227] + Multi-dimensional params-array not allowed [#1230] + Accept NullType as generic type argument + Set source references of created DataType instances in OCE - valadoc: Correctly format background of inline @link's [#1226] * Bindings: - gio-2.0: Unhide a few usable symbols which are marked not introspectable [#1222] - gio-2.0: Backport fixes from 0.54.2 - glib-2.0: Current constants in GLib.Math are part of glib.h [#1220] - glib-2.0: Add RefString since 2.58 [#723] - gtk4: Backport fixes from 0.54.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1945969/+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 1946096] Re: Support manual firmware upgrading for Foxconn and Quectel modems.
Sponsored both the focal and hirsute versions. -- 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/1946096 Title: Support manual firmware upgrading for Foxconn and Quectel modems. Status in OEM Priority Project: In Progress Status in modemmanager package in Ubuntu: Fix Committed Bug description: [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 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946096/+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 1948005] Re: Dell 6000 freeze and restart since october 19.
** Package changed: ubuntu => xorg (Ubuntu) -- 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/1948005 Title: Dell 6000 freeze and restart since october 19. Status in xorg package in Ubuntu: New Bug description: Ramdomly my external display (conected via HDMI over a dell 6000 displaylink port) stop working, gone black, and then restart. Buy I notice that all devices conected to dell 6000 stop working. It happens since october 19 ubuntu auto update. I need this continue working as it was before that update. Description: Ubuntu 20.04.3 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68 Uname: Linux 5.10.0-1050-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 21 08:16:15 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: evdi, 1.9.1, 5.10.0-1049-oem, x86_64: installed evdi, 1.9.1, 5.10.0-1050-oem, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:8a56] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0a29] InstallationDate: Installed on 2021-08-18 (63 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. Vostro 3401 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1050-oem root=UUID=d63f71be-78d3-412a-95ce-c1fd7fc0b432 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/31/2021 dmi.bios.release: 1.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.name: 0790WT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd05/31/2021:br1.6:svnDellInc.:pnVostro3401:pvr:sku0A29:rvnDellInc.:rn0790WT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 3401 dmi.product.sku: 0A29 dmi.sys.vendor: Dell Inc. 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.3 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1948005/+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 1948005] [NEW] Dell 6000 freeze and restart since october 19.
You have been subscribed to a public bug: Ramdomly my external display (conected via HDMI over a dell 6000 displaylink port) stop working, gone black, and then restart. Buy I notice that all devices conected to dell 6000 stop working. It happens since october 19 ubuntu auto update. I need this continue working as it was before that update. Description:Ubuntu 20.04.3 LTS Release:20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68 Uname: Linux 5.10.0-1050-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 21 08:16:15 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: evdi, 1.9.1, 5.10.0-1049-oem, x86_64: installed evdi, 1.9.1, 5.10.0-1050-oem, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:8a56] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0a29] InstallationDate: Installed on 2021-08-18 (63 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. Vostro 3401 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1050-oem root=UUID=d63f71be-78d3-412a-95ce-c1fd7fc0b432 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/31/2021 dmi.bios.release: 1.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.name: 0790WT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd05/31/2021:br1.6:svnDellInc.:pnVostro3401:pvr:sku0A29:rvnDellInc.:rn0790WT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 3401 dmi.product.sku: 0A29 dmi.sys.vendor: Dell Inc. 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.3 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 false-gpu-hang focal freeze ubuntu -- Dell 6000 freeze and restart since october 19. https://bugs.launchpad.net/bugs/1948005 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- 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 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 Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1946096 Title: Support manual firmware upgrading for Foxconn and Quectel modems. Status in OEM Priority Project: In Progress Status in modemmanager package in Ubuntu: Fix Committed Bug description: [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
[Touch-packages] [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 Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1946096 Title: Support manual firmware upgrading for Foxconn and Quectel modems. Status in OEM Priority Project: In Progress Status in modemmanager package in Ubuntu: Fix Committed Bug description: [Impact] 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 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946096/+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 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 Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1946096 Title: Support manual firmware upgrading for Foxconn and Quectel modems. Status in OEM Priority Project: In Progress Status in modemmanager package in Ubuntu: Fix Committed Bug description: [Impact] 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 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946096/+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 1906120] Re: NetworkManager: error -111 disaptching events on DHCPv4 lease renewal
I think this issue https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/486 might provide a fix. See also https://bugzilla.redhat.com/show_bug.cgi?id=1829178 where they mention the fix has been backported to 1.22.12. Any chance the Focal package could be upgraded to include that patch level? FWIW we've had the same issue as described on several machines (same network) when upgrading to Focal; installing the Groovy NM package (1.26.2) rebuilt from source for Focal seems to have fixed it. ** Bug watch added: Red Hat Bugzilla #1829178 https://bugzilla.redhat.com/show_bug.cgi?id=1829178 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1906120 Title: NetworkManager: error -111 disaptching events on DHCPv4 lease renewal Status in network-manager package in Ubuntu: New Bug description: Ubuntu 20.04.1 running on armv7 (IFC6410) Occasional network interruption with the following message in journal: Nov 28 12:03:16 drako NetworkManager[4094]: [1606582996.3983] device[dabf59d236aff82b] (enp1s0): activation-stage: complete activate_stage5_ip_config_result_6,v6 (id 51751) Nov 28 12:03:16 drako NetworkManager[4094]: [1606582996.4026] device[dabf59d236aff82b] (enp1s0): ip6-config: update (commit=0, new-config=0x803e6140) Nov 28 12:03:18 drako NetworkManager[4094]: [1606582998.8611] dhcp4 (enp1s0): error -111 dispatching events Nov 28 12:03:18 drako NetworkManager[4094]: [1606582998.8614] dhcp4 (enp1s0): state changed extended -> fail Nov 28 12:03:18 drako NetworkManager[4094]: [1606582998.8622] device (enp1s0): DHCPv4: trying to acquire a new lease within 90 seconds Nov 28 12:04:49 drako NetworkManager[4094]: [1606583089.4023] device (enp1s0): DHCPv4: grace period expired the ipv4 connection is then cut (the interface looses ipc4 address and the ipv4 routes are purged) until NetworkManager is restarted. The networkmanager-dispatcher.service doesn't indicate any error: Nov 28 06:04:05 drako systemd[1]: Started Network Manager Script Dispatcher Service. Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: new request (2 scripts) Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: CONNECTION_DBUS_PATH=/org/freedesktop/NetworkManager/Settings/1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: CONNECTION_FILENAME=/etc/NetworkManager/system-connections/Wired Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: CONNECTION_UUID=fe299e22-2b52-43ff-9a60-fa385e239f41 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: CONNECTION_ID=Wired Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DEVICE_IFACE=enp1s0 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DEVICE_IP_IFACE=enp1s0 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: IP4_NUM_ADDRESSES=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: IP4_NUM_ROUTES=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: IP6_NUM_ROUTES=3 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_DHCP_LEASE_TIME=28800 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_EXPIRY=1606590245 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_BROADCAST_ADDRESS=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_DOMAIN_NAME=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_DOMAIN_NAME_SERVERS=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_DOMAIN_SEARCH=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_HOST_NAME=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_INTERFACE_MTU=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_MS_CLASSLESS_STATIC_ROUTES=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_NIS_DOMAIN=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_NIS_SERVERS=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_NTP_SERVERS=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_RFC3442_CLASSLESS_STATIC_ROUTE
[Touch-packages] [Bug 1948002] [NEW] software-properties-gtk crashes
Public bug reported: When I try to run "Software and updates" from launcher, nothing happens, try to do so in terminal, there is a report: @ubuntux:~$ software-properties-gtk ERROR:dbus.proxies:Introspect error on :1.175:/: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying Traceback (most recent call last): File "/usr/bin/software-properties-gtk", line 100, in app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, file=file) File "/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py", line 211, in __init__ self.backend.Reload(); File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 72, in __call__ return self._proxy_method(*args, **keywords) File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 141, in __call__ return self._connection.call_blocking(self._named_service, File "/usr/lib/python3/dist-packages/dbus/connection.py", line 652, in call_blocking reply_message = self.send_message_with_reply_and_block( dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name :1.175 was not provided by any .service files Ubuntu 20.04.3 LTS ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1948002 Title: software-properties-gtk crashes Status in software-properties package in Ubuntu: New Bug description: When I try to run "Software and updates" from launcher, nothing happens, try to do so in terminal, there is a report: @ubuntux:~$ software-properties-gtk ERROR:dbus.proxies:Introspect error on :1.175:/: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying Traceback (most recent call last): File "/usr/bin/software-properties-gtk", line 100, in app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, file=file) File "/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py", line 211, in __init__ self.backend.Reload(); File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 72, in __call__ return self._proxy_method(*args, **keywords) File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 141, in __call__ return self._connection.call_blocking(self._named_service, File "/usr/lib/python3/dist-packages/dbus/connection.py", line 652, in call_blocking reply_message = self.send_message_with_reply_and_block( dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name :1.175 was not provided by any .service files Ubuntu 20.04.3 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1948002/+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 1018204] Re:
** Changed in: libxml2 (Fedora) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxml2 in Ubuntu. https://bugs.launchpad.net/bugs/1018204 Title: http://googlechromereleases.blogspot.com/2012/06/stable-channel- update_26.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1018204/+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 1947970] Re: Xorg freeze
> so I am planning to go back to the original Ubuntu drivers Please do that and then open a new bug. We can't support all the custom graphics packages you have installed from PPAs. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Invalid ** Tags added: radeon ** Summary changed: - Xorg freeze + [radeon] Graphics freeze -- 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/1947970 Title: [radeon] Graphics freeze Status in Ubuntu: Invalid Bug description: I know I am using non-standard drivers right now, but that was only after I first experienced the problem. I also already replaced the video card TURKS->JUNIPER, but the problem is the same. Later mesa drivers seem to make the problem worse, so I am planning to go back to the original Ubuntu drivers. They too had the problem and made me try other drivers. The problem seems to occur after 'some other error, like network errors', so suspect to me is PCI bus stuff. More logs and info available. I also reported the problem to the mesa team, but thought Ubuntu might want to help, as I guess Caonical wants to offer a stable Linux. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-89.100-generic 5.4.143 Uname: Linux 5.4.0-89-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: LXQt Date: Thu Oct 21 15:32:19 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.4.0-88-generic, x86_64: installed virtualbox, 6.1.16, 5.4.0-89-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Since a couple weeks or more GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Juniper PRO [Radeon HD 6750] [1002:68bf] (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Juniper PRO [Radeon HD 6750] [1002:] InstallationDate: Installed on 2020-11-05 (349 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: MSI MS-7817 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-89-generic root=UUID=223bdcf0-4c35-4422-bf23-522ebd0ff1ff ro SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. dmi.bios.date: 03/30/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-P33 (MS-7817) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.9:bd03/30/2015:svnMSI:pnMS-7817:pvr1.0:rvnMSI:rnH81M-P33(MS-7817):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7817 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-1~kisak~f version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.4~kisak1~f 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1947970/+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 1947970] Re: Xorg freeze
** Package changed: ubuntu => xorg (Ubuntu) -- 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/1947970 Title: [radeon] Graphics freeze Status in Ubuntu: Invalid Bug description: I know I am using non-standard drivers right now, but that was only after I first experienced the problem. I also already replaced the video card TURKS->JUNIPER, but the problem is the same. Later mesa drivers seem to make the problem worse, so I am planning to go back to the original Ubuntu drivers. They too had the problem and made me try other drivers. The problem seems to occur after 'some other error, like network errors', so suspect to me is PCI bus stuff. More logs and info available. I also reported the problem to the mesa team, but thought Ubuntu might want to help, as I guess Caonical wants to offer a stable Linux. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-89.100-generic 5.4.143 Uname: Linux 5.4.0-89-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: LXQt Date: Thu Oct 21 15:32:19 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.4.0-88-generic, x86_64: installed virtualbox, 6.1.16, 5.4.0-89-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Since a couple weeks or more GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Juniper PRO [Radeon HD 6750] [1002:68bf] (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Juniper PRO [Radeon HD 6750] [1002:] InstallationDate: Installed on 2020-11-05 (349 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: MSI MS-7817 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-89-generic root=UUID=223bdcf0-4c35-4422-bf23-522ebd0ff1ff ro SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. dmi.bios.date: 03/30/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-P33 (MS-7817) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.9:bd03/30/2015:svnMSI:pnMS-7817:pvr1.0:rvnMSI:rnH81M-P33(MS-7817):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7817 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-1~kisak~f version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.4~kisak1~f 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1947970/+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 1947970] [NEW] Xorg freeze
You have been subscribed to a public bug: I know I am using non-standard drivers right now, but that was only after I first experienced the problem. I also already replaced the video card TURKS->JUNIPER, but the problem is the same. Later mesa drivers seem to make the problem worse, so I am planning to go back to the original Ubuntu drivers. They too had the problem and made me try other drivers. The problem seems to occur after 'some other error, like network errors', so suspect to me is PCI bus stuff. More logs and info available. I also reported the problem to the mesa team, but thought Ubuntu might want to help, as I guess Caonical wants to offer a stable Linux. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-89.100-generic 5.4.143 Uname: Linux 5.4.0-89-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: LXQt Date: Thu Oct 21 15:32:19 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.4.0-88-generic, x86_64: installed virtualbox, 6.1.16, 5.4.0-89-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Since a couple weeks or more GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Juniper PRO [Radeon HD 6750] [1002:68bf] (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Juniper PRO [Radeon HD 6750] [1002:] InstallationDate: Installed on 2020-11-05 (349 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: MSI MS-7817 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-89-generic root=UUID=223bdcf0-4c35-4422-bf23-522ebd0ff1ff ro SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. dmi.bios.date: 03/30/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-P33 (MS-7817) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.9:bd03/30/2015:svnMSI:pnMS-7817:pvr1.0:rvnMSI:rnH81M-P33(MS-7817):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7817 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-1~kisak~f version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.4~kisak1~f 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 freeze third-party-packages ubuntu -- Xorg freeze https://bugs.launchpad.net/bugs/1947970 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- 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 1947920] Re: tracker-miner-f 100% CPU and slows system down
Thank you for your bug report, could you perhaps report it directly upstream on https://gitlab.gnome.org/GNOME/tracker/issues ? ** Changed in: tracker (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1947920 Title: tracker-miner-f 100% CPU and slows system down Status in tracker package in Ubuntu: New Bug description: tracker-miner-f has been using 100% CPU and my system making it almost unresponsive. This happens around once a month or so when I boot up. It sometimes lasts for a number of days (or a number of resets) until the system becomes responsive again. The command "tracker status" always shows the same thing: "Estimated less than one second left" although it appears that everything is already indexed because the file and folder counts do not increase. Even so tracker-miner-f is still showing 100% CPU inspiron@Inspiron-7348:~$ tracker status Currently indexed: 101154 files, 16046 folders Remaining space on database partition: 160.5 GB (64.11%) Data is still being indexed: Estimated less than one second left inspiron@Inspiron-7348:~$ tracker status Currently indexed: 101155 files, 16045 folders Remaining space on database partition: 161.1 GB (64.31%) Data is still being indexed: Estimated 01h 19m 03s left ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: tracker 2.3.6-0ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Oct 21 08:25:58 2021 InstallationDate: Installed on 2021-06-28 (114 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: tracker UpgradeStatus: No upgrade log present (probably fresh install) UPDATE I have now reset the tracker and it seems to be going through and indexing everything again. tracker reset --hard Now tracker-miner-f has re-indexed everything and tracker-extract and tracker-store are running. UPDATE 2 The tracker reset completed indexing everything and the went into idle state. However when rebooting, tracker-miner-f went to 100% CPU once again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1947920/+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 1662620] Re: "ip addr add" permits illegal labels
Thanks Chris for having a look. > On the other hand, from the bug it looks like if you *don't* mix valid and > invalid labels > then everything actually works? So this would potentially be breaking > currently working setups? Yes while having that echoing in my head for a while I think you are right. We would have the chance to disrupt working setups, so I beg your pardon and would step back marking it won't fix. ** Changed in: iproute2 (Ubuntu Bionic) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1662620 Title: "ip addr add" permits illegal labels Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Bionic: Won't Fix Bug description: [Impact] * The filter on label names does not match the intention by upstream nor the description in the man page * Fix by backporting upstream fix that strengthens the check [Test Plan] Bad case: root@b:~# ip addr add 1.1.1.1 label test1 dev eth0 "dev" (eth0) must match "label" (test1). root@b:~# ip addr add 1.1.1.1 label eth0-test dev eth0 root@b:~# ip addr show dev eth0 | grep test inet 1.1.1.1/32 scope global eth0-test With the fix it should look like: root@i:~# ip addr add 1.1.1.1 label test1 dev eth0 "label" (test1) must match "dev" (eth0) or be prefixed by "dev" with a colon. root@i:~# ip addr add 1.1.1.1 label eth0-test dev eth0 "label" (eth0-test) must match "dev" (eth0) or be prefixed by "dev" with a colon. root@i:~# ip addr show dev eth0 | grep test [Where problems could occur] * While the fix indeed "corrects" behavior I must say that if someone relied on the non-intended behavior it would now break e.g. his scripting or automation. [Other Info] * It was too easy to fix and too long dormant to ignore it further, but if the SRU team says this is too much regression risk relative to the gain we will mark it Won't Fix based on that decision. --- ip-address(8) manpage states: label NAME Each address may be tagged with a label string. In order to preserve compatibility with Linux-2.0 net aliases, this string must coincide with the name of the device or must be prefixed with the device name followed by colon. But you can omit the colon, "ip addr add" is ONLY checking the label is prefixed with the device: # ip addr add 1.1.1.1 label test1 dev eth0 "dev" (eth0) must match "label" (test1). # ip addr add 1.1.1.2 label eth0-test2 dev eth0 # ip addr add 1.1.1.3 label eth0:test3 dev eth0 Now ifconfig becomes confused about eth0-test2: # ifconfig eth0-test2 eth0-test2: error fetching interface information: Device not found # ifconfig eth0:test3 eth0:test3 Link encap:Ethernet HWaddr b0:d5:cc:fe:1d:7c inet addr:1.1.1.3 Bcast:0.0.0.0 Mask:255.255.255.255 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Interrupt:171 And daemons like ntpd also log errors about the interface with the illegal label: ntpd[7570]: eth0-test3: getting interface flags: No such device ## => many of this error per minute until: ntpd[7570]: Too many errors. Shutting up. So, I think ip addr show disallow adding address with illegal (as stated by his own documentation) labels, it must also check for the colon following the dev name. Version: 4.3.0-1ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1662620/+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