[Bug 2080578] [NEW] package chromium-browser 1:111.0.5563.8-0ubuntu1~ppa1~22.04.1 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status
Public bug reported: GUys, this was the worst upgrade process ever. It took several hours of tending and clicking. keep replace, keep replace...How the heck am I supposed to know how to reply to that when I don't even know what the files doI got to the last stretch and it aborted. pityfulll ProblemType: Package DistroRelease: Ubuntu 24.04 Package: chromium-browser 1:111.0.5563.8-0ubuntu1~ppa1~22.04.1 ProcVersionSignature: Ubuntu 6.8.0-40.40~22.04.3-generic 6.8.12 Uname: Linux 6.8.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Sep 12 13:52:37 2024 ErrorMessage: new chromium-browser package pre-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-05-20 (482 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu2 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.22.6ubuntu6.1 apt 2.7.14build2 SourcePackage: chromium-browser Title: package chromium-browser 1:111.0.5563.8-0ubuntu1~ppa1~22.04.1 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to noble on 2024-09-12 (0 days ago) modified.conffile..etc.default.chromium-browser: [deleted] mtime.conffile..etc.init.d.apport: 2024-07-22T07:59:07 ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080578 Title: package chromium-browser 1:111.0.5563.8-0ubuntu1~ppa1~22.04.1 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2080578/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078991] [NEW] Kernel Panic During Server Installer
Public bug reported: https://imgur.com/a/OC4r25x Hyper-V fresh install 2GB RAM 150GB SSD Secure boot offline Snapshots disabled Problem statement: during fresh install, multiple times, the system became very sluggish and then crashed, reported error then showed kernel panic. There was no particular root cause other than the amount of time passed since initially starting the installer, it could crash anywhere in the wizard, it was more related to chronological time, of about 15-20 minutes at the above specs. Expected behavior: System should never kernel panic during install. ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078991 Title: Kernel Panic During Server Installer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2078991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898014] Re: Unnecessary dependency on mailx
There's an addititional problem though: to make mod_evasive send mails properly it should be using mailx -t, but that'd most likely break alternatives. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898014 Title: Unnecessary dependency on mailx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libapache-mod-evasive/+bug/1898014/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1167449] Re: Add support for instagram
i have also faced the same Kind of issue on my client's website kindly visit: https://www.honistahub.com/honista-mod-apk/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1167449 Title: Add support for instagram To manage notifications about this bug go to: https://bugs.launchpad.net/account-plugins/+bug/1167449/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055114] Re: fail2ban is broken in 24.04 Noble
I understand there are workarounds, but it would be very helpful if this bug was resolved before Ubuntu 23.10 (Mantic Minotaur) reaches End of Life on July 11, 2024. After which, those of us running interim releases, will need to upgrade to the 24.04 Noble release. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055114 Title: fail2ban is broken in 24.04 Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fail2ban/+bug/2055114/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070166] Re: tablet screen rotation doesn't work as expected
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2070166 Title: tablet screen rotation doesn't work as expected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iio-sensor-proxy/+bug/2070166/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064628] Re: openafs-modules-dkms FTBFS wrt Linux 6.8
I can confirm that installing the version in noble-proposed fixes the issue for me root@mirror04:~# apt-get install openafs-modules-dkms/noble-proposed Reading package lists... Done Building dependency tree... Done Reading state information... Done Selected version '1.8.10-2.1ubuntu3.1' (Ubuntu:24.04/noble-proposed [all]) for 'openafs-modules-dkms' Recommended packages: openafs-client The following NEW packages will be installed: openafs-modules-dkms 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 961 kB of archives. After this operation, 7175 kB of additional disk space will be used. Get:1 http://archive.ubuntu.com/ubuntu noble-proposed/universe amd64 openafs-modules-dkms all 1.8.10-2.1ubuntu3.1 [961 kB] Fetched 961 kB in 0s (2303 kB/s) debconf: delaying package configuration, since apt-utils is not installed Selecting previously unselected package openafs-modules-dkms. (Reading database ... 79412 files and directories currently installed.) Preparing to unpack .../openafs-modules-dkms_1.8.10-2.1ubuntu3.1_all.deb ... Unpacking openafs-modules-dkms (1.8.10-2.1ubuntu3.1) ... Setting up openafs-modules-dkms (1.8.10-2.1ubuntu3.1) ... debconf: unable to initialize frontend: Dialog
[Bug 2066897] Re: IFLA_DPLL_PIN is not aligned with upstream value
** Tags removed: verification-needed-jammy-linux-bluefield ** Tags added: verification-done-jammy-linux-bluefield -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066897 Title: IFLA_DPLL_PIN is not aligned with upstream value To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2066897/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065664] Re: Need more patches to support DPLL and syncE on Bluefield 5.15 kernel
** Tags removed: verification-needed-jammy-linux-bluefield ** Tags added: verification-done-jammy-linux-bluefield -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065664 Title: Need more patches to support DPLL and syncE on Bluefield 5.15 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2065664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065664] Re: Need more patches to support DPLL and syncE on Bluefield 5.15 kernel
** Description changed:
* intro
Synchronous Ethernet, or SyncE, is an ITU-T standard for computer networking
that facilitates the transference of clock signals over the Ethernet physical
layer. It is used to pass timing from node to node and is particularly
important for mobile networks.
The DPLL subsystem in the Linux kernel provides a general interface for
configuring devices that use any kind of Digital PLL. This subsystem is
designed to manage the clock signal synchronization of a device with an
external clock signal.
* Explain the bug(s)
- Bug 2053155 already backported some patches to Jammy from upstream,
- there are still some more patches need to be backported.
+ Bug 2053155 already backported some patches from upstream, there are
+ still some more patches need to be backported.
- fb7418bb4be2 netlink: add variable-length / auto integers
- a41451e75eb7 dpll: indent DPLL option type by a tab
- 2a99978e5907 dpll: sanitize possible null pointer dereference in
dpll_pin_parent_pin_set()
- 3c046e92c9b6 dpll: Fix potential msg memleak when genlmsg_put_reply failed
- dd366aad1384 dpll: fix dpll_pin_on_pin_register() for multiple parent pins
- fba896fa9970 dpll: check that pin is registered in __dpll_pin_unregister()
- 6182f400aec3 dpll: fix register pin with unregistered parent pin
- 9f8ed94364c4 dpll: fix dpll_xa_ref_*_del() for multiple registrations
- 215250dfdc9e dpll: spec: use proper enum for pin capabilities attribute
- 5bb45ebc5a89 dpll: move all dpll<>netdev helpers to dpll code
- 2d9edf8f70a7 dpll: fix build failure due to rcu_dereference_check() on
unknown type
- f3dde9bca353 dpll: rely on rcu for netdev_dpll_pin()
- 026d1e21c67d tools: ynl: fix header guards
- 6fe1a583e415 tools: ynl: allow user to pass enum string instead of scalar
value
- 32250d2551d7 dpll: fix possible deadlock during netlink dump operation
- 1f79359d7433 tools: ynl: include dpll and mptcp_pm in C codegen
- c36d6945b5d0 dpll: extend lock_status_get() op by status error and expose to
user
- 3a0a12237480 dpll: extend uapi by lock status error attribute
- b4301f76c6b8 dpll: move xa_erase() call in to match dpll_pin_alloc() error
path order
- ed03a6c933da dpll: fix userspace availability of pins
- b2f4256312fc dpll: fix pin dump crash for rebound module
- 0329c8e419f7 dpll: fix broken error path in dpll_pin_alloc(..)
- b849fe83c180 dpll: expose fractional frequency offset value to user
- 1783b665ccc1 dpll: allocate pin ids in cycle
+ 3424040 dpll: indent DPLL option type by a tab
+ f710345 dpll: sanitize possible null pointer dereference in
dpll_pin_parent_pin_set()
+ 040437d dpll: Fix potential msg memleak when genlmsg_put_reply failed
+ b45ed4c dpll: fix dpll_pin_on_pin_register() for multiple parent pins
+ 55a0add dpll: check that pin is registered in __dpll_pin_unregister()
+ 540c388 dpll: fix register pin with unregistered parent pin
+ b933eea dpll: fix dpll_xa_ref_*_del() for multiple registrations
+ 0408c3f dpll: spec: use proper enum for pin capabilities attribute
+ b1368d3 dpll: move all dpll<>netdev helpers to dpll code
+ 9c18583 dpll: fix build failure due to rcu_dereference_check() on unknown type
+ ba55508 dpll: rely on rcu for netdev_dpll_pin()
+ 56be959 tools: ynl: fix header guards
+ 7a59a12 tools: ynl: allow user to pass enum string instead of scalar value
+ 8472117 dpll: fix possible deadlock during netlink dump operation
+ 7ee732e tools: ynl: include dpll and mptcp_pm in C codegen
+ 71931b4 dpll: extend lock_status_get() op by status error and expose to user
+ 2369137 dpll: extend uapi by lock status error attribute
+ f57230e dpll: move xa_erase() call in to match dpll_pin_alloc() error path
order
+ 5ba255b dpll: fix userspace availability of pins
+ ec378a6 dpll: fix pin dump crash for rebound module
+ b2c8844 dpll: fix broken error path in dpll_pin_alloc(..)
+ b6e349a dpll: expose fractional frequency offset value to user
+ 4e5e5e0 dpll: allocate pin ids in cycle
+ a690bc9 netlink: add variable-length / auto integers
+ aaeef43 netlink: allow be16 and be32 types in all uint policy checks
+ abf0f7e netlink: introduce bigendian integer types
+ 0e036c0 netlink: hide validation union fields from kdoc
+ b5091c1 netfilter: nft_payload: reject out-of-range attributes via policy
+ 0bf4c03 netlink: introduce NLA_POLICY_MAX_BE
* Brief explanation of fixes
Basic function of DPLL is not full supported. Still need backported
relevant patches.
* How to test
$ sudo ./tools/net/ynl/cli.py --spec Documentation/netlink/specs/dpll.yaml \
--dump device-get
ex:
root@bfqa-dell013-roy-oob:~/mlnx-ofa_kernel-4.0# /root/tools-net/ynl/cli.py
--spec ~/netlink/specs/dpll.yaml --dump device-get
[{'clock-id': 5237736944144095348,
'id': 0,
'lock-status': 'unlocked',
'mode': 'manual',
'mode-supported': ['manual'],
'module-name': 'mlx5_core',
'type': 'eec'}]
$ sudo ./tools/net/ynl/cli.py --spec Documentation/netlink/specs/dpll.yaml \
--do pin-get
[Bug 2065664] Re: Need more patches to support DPLL and syncE on Bluefield 5.15 kernel
** Description changed:
* intro
Synchronous Ethernet, or SyncE, is an ITU-T standard for computer networking
that facilitates the transference of clock signals over the Ethernet physical
layer. It is used to pass timing from node to node and is particularly
important for mobile networks.
The DPLL subsystem in the Linux kernel provides a general interface for
configuring devices that use any kind of Digital PLL. This subsystem is
designed to manage the clock signal synchronization of a device with an
external clock signal.
* Explain the bug(s)
- Bug 2053155 already backported some patches from upstream, there are
- still some more patches need to be backported.
+ Bug 2053155 already backported some patches to Jammy from upstream,
+ there are still some more patches need to be backported.
fb7418bb4be2 netlink: add variable-length / auto integers
a41451e75eb7 dpll: indent DPLL option type by a tab
2a99978e5907 dpll: sanitize possible null pointer dereference in
dpll_pin_parent_pin_set()
3c046e92c9b6 dpll: Fix potential msg memleak when genlmsg_put_reply failed
dd366aad1384 dpll: fix dpll_pin_on_pin_register() for multiple parent pins
fba896fa9970 dpll: check that pin is registered in __dpll_pin_unregister()
6182f400aec3 dpll: fix register pin with unregistered parent pin
9f8ed94364c4 dpll: fix dpll_xa_ref_*_del() for multiple registrations
215250dfdc9e dpll: spec: use proper enum for pin capabilities attribute
5bb45ebc5a89 dpll: move all dpll<>netdev helpers to dpll code
2d9edf8f70a7 dpll: fix build failure due to rcu_dereference_check() on
unknown type
f3dde9bca353 dpll: rely on rcu for netdev_dpll_pin()
026d1e21c67d tools: ynl: fix header guards
6fe1a583e415 tools: ynl: allow user to pass enum string instead of scalar
value
32250d2551d7 dpll: fix possible deadlock during netlink dump operation
1f79359d7433 tools: ynl: include dpll and mptcp_pm in C codegen
c36d6945b5d0 dpll: extend lock_status_get() op by status error and expose to
user
3a0a12237480 dpll: extend uapi by lock status error attribute
b4301f76c6b8 dpll: move xa_erase() call in to match dpll_pin_alloc() error
path order
ed03a6c933da dpll: fix userspace availability of pins
b2f4256312fc dpll: fix pin dump crash for rebound module
0329c8e419f7 dpll: fix broken error path in dpll_pin_alloc(..)
b849fe83c180 dpll: expose fractional frequency offset value to user
1783b665ccc1 dpll: allocate pin ids in cycle
* Brief explanation of fixes
Basic function of DPLL is not full supported. Still need backported
relevant patches.
* How to test
$ sudo ./tools/net/ynl/cli.py --spec Documentation/netlink/specs/dpll.yaml \
--dump device-get
ex:
root@bfqa-dell013-roy-oob:~/mlnx-ofa_kernel-4.0# /root/tools-net/ynl/cli.py
--spec ~/netlink/specs/dpll.yaml --dump device-get
[{'clock-id': 5237736944144095348,
- 'id': 0,
- 'lock-status': 'unlocked',
- 'mode': 'manual',
- 'mode-supported': ['manual'],
- 'module-name': 'mlx5_core',
- 'type': 'eec'}]
+ 'id': 0,
+ 'lock-status': 'unlocked',
+ 'mode': 'manual',
+ 'mode-supported': ['manual'],
+ 'module-name': 'mlx5_core',
+ 'type': 'eec'}]
$ sudo ./tools/net/ynl/cli.py --spec Documentation/netlink/specs/dpll.yaml \
--do pin-get
ex:
root@bfqa-dell013-roy-oob:~# /root/tools-net/ynl/cli.py --spec
~/netlink/specs/dpll.yaml --dump pin-get
[{'capabilities': 4,
- 'clock-id': 5237736944144095348,
- 'id': 0,
- 'module-name': 'mlx5_core',
- 'parent-device': [{'direction': 'input',
- 'parent-id': 0,
- 'state': 'disconnected'}],
- 'phase-adjust-max': 0,
- 'phase-adjust-min': 0,
- 'type': 'synce-eth-port'},
- {'capabilities': 4,
- 'clock-id': 5237736944144095348,
- 'id': 1,
- 'module-name': 'mlx5_core',
- 'parent-device': [{'direction': 'input',
- 'parent-id': 0,
- 'state': 'disconnected'}],
- 'phase-adjust-max': 0,
- 'phase-adjust-min': 0,
- 'type': 'synce-eth-port'}]
+ 'clock-id': 5237736944144095348,
+ 'id': 0,
+ 'module-name': 'mlx5_core',
+ 'parent-device': [{'direction': 'input',
+ 'parent-id': 0,
+ 'state': 'disconnected'}],
+ 'phase-adjust-max': 0,
+ 'phase-adjust-min': 0,
+ 'type': 'synce-eth-port'},
+ {'capabilities': 4,
+ 'clock-id': 5237736944144095348,
+ 'id': 1,
+ 'module-name': 'mlx5_core',
+ 'parent-device': [{'direction': 'input',
+ 'parent-id': 0,
+ 'state': 'disconnected'}],
+ 'phase-adjust-max': 0,
+ 'phase-adjust-min': 0,
+ 'type': 'synce-eth-port'}]
* detect whether your device supports DPLL/SyncE
root@bfqa-dell013-roy-oob:~/linux-bluefield-jammy# mlxreg -d 03:00.0
--reg_name MCAM --get -i "access_reg_group=2,feature_group=0"
Field Name | Data
===
access_reg_group | 0x0002
feature_group | 0x
[Bug 2066897] Re: IFLA_DPLL_PIN is not aligned with upstream value
** Description changed: * Introduction - DPLL pin was exposed in upstream and backed into Bluefield kernel. But since there are some other value was not needed in Bluefield kernel, they are not in current Bluefield kernel. This may cause the value of IFLA_DPLL_PIN value be not same as upstream and break user application. + DPLL pin was exposed in upstream and backported into Bluefield 5.15 kernel (Jammy). But since there are some other value was not needed in Bluefield kernel, they are not in current Bluefield kernel. This may cause the value of IFLA_DPLL_PIN value be not same as upstream and break user application. * Explain the bug(s) IFLA_DPLL_PIN is defined in if_link.h as an enum element. The following elements before IFLA_DPLL_PIN are not needed by Bluefield kernel. - IFLA_GRO_MAX_SIZE, - IFLA_TSO_MAX_SIZE, - IFLA_TSO_MAX_SEGS, - IFLA_ALLMULTI, /* Allmulti count: > 0 means acts ALLMULTI */ - IFLA_DEVLINK_PORT, - IFLA_GSO_IPV4_MAX_SIZE, - IFLA_GRO_IPV4_MAX_SIZE, + IFLA_GRO_MAX_SIZE, + IFLA_TSO_MAX_SIZE, + IFLA_TSO_MAX_SEGS, + IFLA_ALLMULTI, /* Allmulti count: > 0 means acts ALLMULTI */ + IFLA_DEVLINK_PORT, + IFLA_GSO_IPV4_MAX_SIZE, + IFLA_GRO_IPV4_MAX_SIZE, These missing elements will cause the value of IFLA_DPLL_PIN to be 58 in Bluefield kernel while it is 65 in upstream. This inconsistent value may break userspace applications. ~/synced/build# ./synced -i p0 -t 2 -v Config file does not exist at default path (/etc/synced/synced.conf), using default values. -- SyncED v1.1.20.g0c2006cfeba5-1 - + Config file: /etc/synced/synced.conf Log file: /var/log/synced.log Log file size limit: 500 MB Wait to restore time: 2 seconds -- NOTICE [18/05/2024 00:19:15.078629]: NOTICE [18/05/2024 00:19:15.078717]: SyncED is initializing... NOTICE [18/05/2024 00:19:15.078728]: NOTICE [18/05/2024 00:19:15.078739]: Adding Provider: NOTICE [18/05/2024 00:19:15.078745]: Name: 'p0' NOTICE [18/05/2024 00:19:15.078751]: Priority: 1 NOTICE [18/05/2024 00:19:15.078757]: Backend: DPLL no IFLA_DPLL_PIN * Brief explanation of fixes Becasue these missing elements are not needed in Bluefield kernel. A possible fix is to set the IFLA_DPLL_PIN to 65. * How to test ~/synced/build# ./synced -i p0 -t 2 -v Config file does not exist at default path (/etc/synced/synced.conf), using default values. -- SyncED v1.1.20.g0c2006cfeba5-1 - + Config file: /etc/synced/synced.conf Log file: /var/log/synced.log Log file size limit: 500 MB Wait to restore time: 2 seconds -- NOTICE [21/05/2024 10:07:29.097788]: NOTICE [21/05/2024 10:07:29.098014]: SyncED is initializing... NOTICE [21/05/2024 10:07:29.098036]: NOTICE [21/05/2024 10:07:29.098050]: Adding Provider: NOTICE [21/05/2024 10:07:29.098068]: Name: 'p0' NOTICE [21/05/2024 10:07:29.098076]: Priority: 1 NOTICE [21/05/2024 10:07:29.098082]: Backend: DPLL NOTICE [21/05/2024 10:07:29.098236]: DPLL pin ID: 0 NOTICE [21/05/2024 10:07:29.098375]: DPLL device ID: 0 NOTICE [21/05/2024 10:07:29.138093]: network_option: 1 NOTICE [21/05/2024 10:07:29.138139]: local_clock_QL: QL_EEC1 [1] NOTICE [21/05/2024 10:07:29.138149]: local_ssm_code: 0xb NOTICE [21/05/2024 10:07:29.138156]: local_enhanced_ssm_code: 0xff NOTICE [21/05/2024 10:07:29.138162]: local_clock_ID: 0x48b02dfffea60fdc NOTICE [21/05/2024 10:07:29.138343]: DPLL pin ID: 0 NOTICE [21/05/2024 10:07:29.138495]: DPLL device ID: 0 NOTICE [21/05/2024 10:07:29.138585]: Adding it to Group #0 NOTICE [21/05/2024 10:07:29.138809]: NOTICE [21/05/2024 10:07:29.138833]: Active groups: NOTICE [21/05/2024 10:07:29.138840]: SyncE Group #0: NOTICE [21/05/2024 10:07:29.138847]: network_option = 1 NOTICE [21/05/2024 10:07:29.138854]: local_clock_QL = QL_EEC1 [1] NOTICE [21/05/2024 10:07:29.138861]: local_clock_ID = 0x48b02dfffea60fdc NOTICE [21/05/2024 10:07:29.138867]: local_clock_interface = p0 NOTICE [21/05/2024 10:07:29.138873]: SyncE Provider Interfaces = NOTICE [21/05/2024 10:07:29.138879]: p0 [Priority 1] NOTICE [21/05/2024 10:07:29.138885]: NOTICE [21/05/2024 10:07:29.138977]: Group #0: The device is in FREE_RUNNING mode. INFO [21/05/2024 10:07:29.139384]: SyncE Group #0: is in FREE_RUNNING mode. INFO [21/05/2024 10:07:30.139749]: SyncE Group #0: is in FREE_RUNNING mode. INFO [21/05/2024 10:07:31.140004]: SyncE Group #0: is in FREE_RUNNING mode. INFO [21/05/2024 10:07:32.140266]: SyncE Group #0: is in FREE_RUNNING mode. INFO [21/
[Bug 2066897] [NEW] IFLA_DPLL_PIN is not aligned with upstream value
Public bug reported: * Introduction DPLL pin was exposed in upstream and backed into Bluefield kernel. But since there are some other value was not needed in Bluefield kernel, they are not in current Bluefield kernel. This may cause the value of IFLA_DPLL_PIN value be not same as upstream and break user application. * Explain the bug(s) IFLA_DPLL_PIN is defined in if_link.h as an enum element. The following elements before IFLA_DPLL_PIN are not needed by Bluefield kernel. IFLA_GRO_MAX_SIZE, IFLA_TSO_MAX_SIZE, IFLA_TSO_MAX_SEGS, IFLA_ALLMULTI, /* Allmulti count: > 0 means acts ALLMULTI */ IFLA_DEVLINK_PORT, IFLA_GSO_IPV4_MAX_SIZE, IFLA_GRO_IPV4_MAX_SIZE, These missing elements will cause the value of IFLA_DPLL_PIN to be 58 in Bluefield kernel while it is 65 in upstream. This inconsistent value may break userspace applications. ~/synced/build# ./synced -i p0 -t 2 -v Config file does not exist at default path (/etc/synced/synced.conf), using default values. -- SyncED v1.1.20.g0c2006cfeba5-1 Config file: /etc/synced/synced.conf Log file: /var/log/synced.log Log file size limit: 500 MB Wait to restore time: 2 seconds -- NOTICE [18/05/2024 00:19:15.078629]: NOTICE [18/05/2024 00:19:15.078717]: SyncED is initializing... NOTICE [18/05/2024 00:19:15.078728]: NOTICE [18/05/2024 00:19:15.078739]: Adding Provider: NOTICE [18/05/2024 00:19:15.078745]: Name: 'p0' NOTICE [18/05/2024 00:19:15.078751]: Priority: 1 NOTICE [18/05/2024 00:19:15.078757]: Backend: DPLL no IFLA_DPLL_PIN * Brief explanation of fixes Becasue these missing elements are not needed in Bluefield kernel. A possible fix is to set the IFLA_DPLL_PIN to 65. * How to test ~/synced/build# ./synced -i p0 -t 2 -v Config file does not exist at default path (/etc/synced/synced.conf), using default values. -- SyncED v1.1.20.g0c2006cfeba5-1 Config file: /etc/synced/synced.conf Log file: /var/log/synced.log Log file size limit: 500 MB Wait to restore time: 2 seconds -- NOTICE [21/05/2024 10:07:29.097788]: NOTICE [21/05/2024 10:07:29.098014]: SyncED is initializing... NOTICE [21/05/2024 10:07:29.098036]: NOTICE [21/05/2024 10:07:29.098050]: Adding Provider: NOTICE [21/05/2024 10:07:29.098068]: Name: 'p0' NOTICE [21/05/2024 10:07:29.098076]: Priority: 1 NOTICE [21/05/2024 10:07:29.098082]: Backend: DPLL NOTICE [21/05/2024 10:07:29.098236]: DPLL pin ID: 0 NOTICE [21/05/2024 10:07:29.098375]: DPLL device ID: 0 NOTICE [21/05/2024 10:07:29.138093]: network_option: 1 NOTICE [21/05/2024 10:07:29.138139]: local_clock_QL: QL_EEC1 [1] NOTICE [21/05/2024 10:07:29.138149]: local_ssm_code: 0xb NOTICE [21/05/2024 10:07:29.138156]: local_enhanced_ssm_code: 0xff NOTICE [21/05/2024 10:07:29.138162]: local_clock_ID: 0x48b02dfffea60fdc NOTICE [21/05/2024 10:07:29.138343]: DPLL pin ID: 0 NOTICE [21/05/2024 10:07:29.138495]: DPLL device ID: 0 NOTICE [21/05/2024 10:07:29.138585]: Adding it to Group #0 NOTICE [21/05/2024 10:07:29.138809]: NOTICE [21/05/2024 10:07:29.138833]: Active groups: NOTICE [21/05/2024 10:07:29.138840]: SyncE Group #0: NOTICE [21/05/2024 10:07:29.138847]: network_option = 1 NOTICE [21/05/2024 10:07:29.138854]: local_clock_QL = QL_EEC1 [1] NOTICE [21/05/2024 10:07:29.138861]: local_clock_ID = 0x48b02dfffea60fdc NOTICE [21/05/2024 10:07:29.138867]: local_clock_interface = p0 NOTICE [21/05/2024 10:07:29.138873]: SyncE Provider Interfaces = NOTICE [21/05/2024 10:07:29.138879]: p0 [Priority 1] NOTICE [21/05/2024 10:07:29.138885]: NOTICE [21/05/2024 10:07:29.138977]: Group #0: The device is in FREE_RUNNING mode. INFO [21/05/2024 10:07:29.139384]: SyncE Group #0: is in FREE_RUNNING mode. INFO [21/05/2024 10:07:30.139749]: SyncE Group #0: is in FREE_RUNNING mode. INFO [21/05/2024 10:07:31.140004]: SyncE Group #0: is in FREE_RUNNING mode. INFO [21/05/2024 10:07:32.140266]: SyncE Group #0: is in FREE_RUNNING mode. INFO [21/05/2024 10:07:33.140534]: SyncE Group #0: is in FREE_RUNNING mode. CRITICAL [21/05/2024 10:07:34.139681]: Group #0: Provider p0: ESMC Signal was lost! INFO [21/05/2024 10:07:34.139873]: Group #0: Provider p0: source info changed: From: QL=QL_DNU [0], source_clock_id=0x0, mixed_eec_eeec=0, partial_chain=0, num_cascaded_e_eecs=0, num_of_cascaded_eecs=0 To: QL=QL_FAILED [-1], source_clock_id=0x0, mixed_eec_eeec=0, partial_chain=0, num_cascaded_e_eecs=0, num_of_cascaded_eecs=0 INFO [21/05/2024 10:07:34.140985]: SyncE Group #0: is in FREE_RUNNING mode. INFO [21/05/2024 10:07:35.141271]: SyncE Group #0: is in FREE_RUNNING mode. INFO [21/05/2024 10:07:36.141562]: SyncE Group #0: is
[Bug 2065664] [NEW] Need more patches to support DPLL and syncE on Bluefield 5.15 kernel
Public bug reported:
* intro
Synchronous Ethernet, or SyncE, is an ITU-T standard for computer networking
that facilitates the transference of clock signals over the Ethernet physical
layer. It is used to pass timing from node to node and is particularly
important for mobile networks.
The DPLL subsystem in the Linux kernel provides a general interface for
configuring devices that use any kind of Digital PLL. This subsystem is
designed to manage the clock signal synchronization of a device with an
external clock signal.
* Explain the bug(s)
Bug 2053155 already backported some patches from upstream, there are
still some more patches need to be backported.
fb7418bb4be2 netlink: add variable-length / auto integers
a41451e75eb7 dpll: indent DPLL option type by a tab
2a99978e5907 dpll: sanitize possible null pointer dereference in
dpll_pin_parent_pin_set()
3c046e92c9b6 dpll: Fix potential msg memleak when genlmsg_put_reply failed
dd366aad1384 dpll: fix dpll_pin_on_pin_register() for multiple parent pins
fba896fa9970 dpll: check that pin is registered in __dpll_pin_unregister()
6182f400aec3 dpll: fix register pin with unregistered parent pin
9f8ed94364c4 dpll: fix dpll_xa_ref_*_del() for multiple registrations
215250dfdc9e dpll: spec: use proper enum for pin capabilities attribute
5bb45ebc5a89 dpll: move all dpll<>netdev helpers to dpll code
2d9edf8f70a7 dpll: fix build failure due to rcu_dereference_check() on unknown
type
f3dde9bca353 dpll: rely on rcu for netdev_dpll_pin()
026d1e21c67d tools: ynl: fix header guards
6fe1a583e415 tools: ynl: allow user to pass enum string instead of scalar value
32250d2551d7 dpll: fix possible deadlock during netlink dump operation
1f79359d7433 tools: ynl: include dpll and mptcp_pm in C codegen
c36d6945b5d0 dpll: extend lock_status_get() op by status error and expose to
user
3a0a12237480 dpll: extend uapi by lock status error attribute
b4301f76c6b8 dpll: move xa_erase() call in to match dpll_pin_alloc() error path
order
ed03a6c933da dpll: fix userspace availability of pins
b2f4256312fc dpll: fix pin dump crash for rebound module
0329c8e419f7 dpll: fix broken error path in dpll_pin_alloc(..)
b849fe83c180 dpll: expose fractional frequency offset value to user
1783b665ccc1 dpll: allocate pin ids in cycle
* Brief explanation of fixes
Basic function of DPLL is not full supported. Still need backported
relevant patches.
* How to test
$ sudo ./tools/net/ynl/cli.py --spec Documentation/netlink/specs/dpll.yaml \
--dump device-get
ex:
root@bfqa-dell013-roy-oob:~/mlnx-ofa_kernel-4.0# /root/tools-net/ynl/cli.py
--spec ~/netlink/specs/dpll.yaml --dump device-get
[{'clock-id': 5237736944144095348,
'id': 0,
'lock-status': 'unlocked',
'mode': 'manual',
'mode-supported': ['manual'],
'module-name': 'mlx5_core',
'type': 'eec'}]
$ sudo ./tools/net/ynl/cli.py --spec Documentation/netlink/specs/dpll.yaml \
--do pin-get
ex:
root@bfqa-dell013-roy-oob:~# /root/tools-net/ynl/cli.py --spec
~/netlink/specs/dpll.yaml --dump pin-get
[{'capabilities': 4,
'clock-id': 5237736944144095348,
'id': 0,
'module-name': 'mlx5_core',
'parent-device': [{'direction': 'input',
'parent-id': 0,
'state': 'disconnected'}],
'phase-adjust-max': 0,
'phase-adjust-min': 0,
'type': 'synce-eth-port'},
{'capabilities': 4,
'clock-id': 5237736944144095348,
'id': 1,
'module-name': 'mlx5_core',
'parent-device': [{'direction': 'input',
'parent-id': 0,
'state': 'disconnected'}],
'phase-adjust-max': 0,
'phase-adjust-min': 0,
'type': 'synce-eth-port'}]
* detect whether your device supports DPLL/SyncE
root@bfqa-dell013-roy-oob:~/linux-bluefield-jammy# mlxreg -d 03:00.0 --reg_name
MCAM --get -i "access_reg_group=2,feature_group=0"
Field Name | Data
===
access_reg_group | 0x0002
feature_group | 0x
mng_access_reg_cap_mask[0] | 0x0004
mng_access_reg_cap_mask[1] | 0x0060 --> must see 6
** Affects: linux-bluefield (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2065664
Title:
Need more patches to support DPLL and syncE on Bluefield 5.15 kernel
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2065664/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062131] Re: block probing crashed with ValueError - Invalid dep_id (disk-nbd0) not in storage config - PXE Install
** Also affects: subiquity (Ubuntu) Importance: Undecided Status: New ** No longer affects: subiquity (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062131 Title: block probing crashed with ValueError - Invalid dep_id (disk-nbd0) not in storage config - PXE Install To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/2062131/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1575053] Re: Please move the "$HOME/snap" directory to a less obtrusive location
The only really sensible use case for Snaps, if any, is packaging software that will never make it into an official repository, like some 3rd party software, e.g. MS-Office suite, or Photoshop. Servers use docker or podman to deploy services. But what ever you do, please sort out the mess with snap. Allow if not user control as to where things go, then at a system wide level, or failing that just at least pick sensible defaults for your hardwired locations: ~/snap -> ~/.local/snap /snap -> /usr/snap etc Hide snap specific loopback mounts in df. Snap is currently a mess and just sorting this one ticket would probably stop quite a bit of the pushback you are getting on Snap. Obviously there are many other things wrong with snap as stated elsewhere, but actioning this one, not terribly difficult ticket would bring big dividends to user perception. It's been 8 years for this ticket! I think this speaks volumes in terms of the level of support that end users are going to get on snap going forward. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575053 Title: Please move the "$HOME/snap" directory to a less obtrusive location To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1575053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059961] Re: genetlink: fix single op policy dump when do is present
** Tags removed: verification-needed-jammy-linux-bluefield ** Tags added: verification-done-jammy-linux-bluefield -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059961 Title: genetlink: fix single op policy dump when do is present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2059961/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2053155] Re: Add DPLL and syncE support
** Tags removed: verification-needed-jammy-linux-bluefield ** Tags added: verification-done-jammy-linux-bluefield -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2053155 Title: Add DPLL and syncE support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2053155/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056364] Re: Add test script for DPLL
** Tags removed: verification-needed-jammy-linux-bluefield ** Tags added: verification-done-jammy-linux-bluefield -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056364 Title: Add test script for DPLL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2056364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056718] Re: openvswitch gentling validation warning: missing .resv_start_op
** Tags removed: verification-needed-jammy-linux-bluefield ** Tags added: verification-done-jammy-linux-bluefield -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056718 Title: openvswitch gentling validation warning: missing .resv_start_op To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2056718/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058098] Re: Gpodder doesn't start anymore on Ubuntu 24.04 problem with Python 3.12 - ModuleNotFoundError: No module named 'imp'
A patched version 3.11.3-2 tested against Python 3.12 (in Debian unstable) has been uploaded to Debian: https://tracker.debian.org/news/1512534/accepted-gpodder-3113-2-source- into-unstable/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058098 Title: Gpodder doesn't start anymore on Ubuntu 24.04 problem with Python 3.12 - ModuleNotFoundError: No module named 'imp' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/loupe/+bug/2058098/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972683] Re: After changing GRUB_DISTRIBUTOR variable grub uses wrong grub.cfg file
This seems to be a duplicate of 1242417. However the fix applied for that bug didn't fix the underlying problem but instead created a workaround that was sufficient for the case that led to the bug. It does not fix the situation reported here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972683 Title: After changing GRUB_DISTRIBUTOR variable grub uses wrong grub.cfg file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1972683/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972683] [NEW] After changing GRUB_DISTRIBUTOR variable grub uses wrong grub.cfg file
Public bug reported: An ubuntu system has files in a folder within /boot/efi/EFI and an EFI variable both of whose names are given by the GRUB_DISTRIBUTOR variable in /etc/default/grub. By default this is set to "ubuntu". I wish to have two ubuntu systems on the same machine so on one of them at least need to change GRUB_DISTRIBUTOR to something else. In the past I have done this with two systems "main" and "backup". This worked fine using grub-efi-amd64. I have recently tried this on a new system using grub-efi-amd64-signed and ended up with an unbootable system. After some investigation it turns out that whatever folder within /boot/efi/EFI you boot from it always uses grub.cfg from /boot/efi/EFI/ubuntu. I can now recreate this at will in virtualbox. To exhibit this do the following steps: Do a fresh install of ubuntu in virtualbox. Check for existence of /boot/efi/EFI/ubuntu, that an EFI entry is shown by efibootmgr and that the system reboots. Change the value of GRUB_DISTRIBUTOR in /etc/default/grub to "test". Run dpkg-reconfigure grub-efi-amd64-signed to trigger grub-install. Check for existence of /boot/efi/EFI/test, that a test EFI entry is shown by efibootmgr. Change nextboot to the test entry and check that the system reboots. Rename grub.cfg from /boot/efi/EFI/test and reboot from the test entry. Boot should fail, but it doesn't. Restore the test grub.cfg and rename the grub.cfg in /boot/efi/EFI/ubuntu. Reboot from the test entry. This should work OK but it fails. This indicates that even when booting from /boot/efi/EFI/test grub is using the config file in /boot/efi/EFI/ubuntu ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: grub-efi-amd64-signed 1.180+2.06-2ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Mon May 9 15:59:26 2022 InstallationDate: Installed on 2022-04-26 (12 days ago) InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: grub2-signed UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub2-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972683 Title: After changing GRUB_DISTRIBUTOR variable grub uses wrong grub.cfg file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1972683/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893957] Re: Ubuntu 20.04 guest aborts on graphical login following recent upgrade
This should probably be closed now. I am currently running 22.04 guests on 20.04 host and everything working OK. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893957 Title: Ubuntu 20.04 guest aborts on graphical login following recent upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1893957/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1466150] Re: grub-install breaks when ESP is on raid
Just experimented with a "clean" Ubuntu system that had grub-efi- amd64-signed. To get the prompt for the efi partitions I had to call dpkg-reconfigure shim-signed. After that it seemed to work OK. I wish I knew where all this was documented. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1466150 Title: grub-install breaks when ESP is on raid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1466150/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971165] Re: Upgrade from 20.04 to 22.04 failed due to efi partition naming
I've now managed to recreate this in a checkpointed virtual machine. The last few lines from do-release-upgrade are: Updating repository information Hit http://gb.archive.ubuntu.com/ubuntu jammy InRelease Hit http://gb.archive.ubuntu.com/ubuntu jammy-updates InRelease Hit http://gb.archive.ubuntu.com/ubuntu jammy-backports InRelease Hit http://security.ubuntu.com/ubuntu jammy-security InRelease Fetched 0 B in 0s (0 B/s) Checking package manager Reading package lists... Done Building dependency tree Reading state information... Done Calculating the changes Calculating the changes EFI System Partition (ESP) not usable Your EFI System Partition (ESP) is not mounted at /boot/efi. Please ensure that it is properly configured and try again. There is code in /usr/lib/python3/dist- packages/DistUpgrade/DistUpgradeController.py that matches this message but I put some diagnostic messages in this file and they weren't displayed which confuses me a bit. However that might just be my faulty understanding of how python works. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971165 Title: Upgrade from 20.04 to 22.04 failed due to efi partition naming To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1971165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971165] [NEW] Upgrade from 20.04 to 22.04 failed due to efi partition naming
Public bug reported: I recently upgraded a Ubuntu Budgie system from 20.04 to 22.04 the upgrade worked fine apart from one problem. The original system had two EFI partitions mounted at /boot/efia & /boot/efib. Grub is quite happy with this and updates both. However do-release-upgrade failed early on because EFI wasn't mounted at /boot/efi. I changed the mount points and reran do-release-upgrade and everything worked fine, including installing grub to both EFI partitions. The evidence collected by report-bug may be of little use because it comes from the upgraded system, not the original. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.10 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: Budgie:GNOME Date: Mon May 2 15:56:37 2022 InstallationDate: Installed on 2020-09-08 (600 days ago) InstallationMedia: Ubuntu-Budgie 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to jammy on 2022-05-02 (0 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971165 Title: Upgrade from 20.04 to 22.04 failed due to efi partition naming To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1971165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970153] [NEW] python3-mako depends on pkg-resources
Public bug reported: I would have thought pkg-resources/setuptools would be part of the transitive dependencies, but both are missing. See https://github.com/mxe/mxe/commit/3b61050dabf8b3fb0fae9e373ebb88205758ced0#r71983265 ** Affects: mako (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970153 Title: python3-mako depends on pkg-resources To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mako/+bug/1970153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1473527] Re: module ssh-authkey-fingerprints fails Input/output error: /dev/console
I just hit this today (Nutanix AHV) cloud-init also. From "/var/log/cloud-init.log". 2022-03-16 16:25:18,764 - util.py[WARNING]: Running module ssh-authkey-fingerprints () failed 2022-03-16 16:25:18,764 - util.py[DEBUG]: Running module ssh-authkey-fingerprints () failed Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/cloudinit/util.py", line 371, in multi_log wfh.flush() OSError: [Errno 5] Input/output error # cat /lib/systemd/system/cloud-final.service | grep StandardOutput StandardOutput=journal+console # echo > /dev/console bash: echo: write error: Input/output error During handling of the above exception, another exception occurred: OSError: [Errno 5] Input/output error [root@ubuntu-template log]# dmesg | grep console [0.00] Command line: BOOT_IMAGE=(hd0,msdos1)/boot/vmlinuz-4.18.0-358.el8.x86_64 root=UUID=395b9844-e404-4857-afbb-c6edccaf72f3 ro console=ttyS0,115200n8 no_timer_check net.ifnames=0 crashkernel=auto [0.00] Kernel command line: BOOT_IMAGE=(hd0,msdos1)/boot/vmlinuz-4.18.0-358.el8.x86_64 root=UUID=395b9844-e404-4857-afbb-c6edccaf72f3 ro console=ttyS0,115200n8 no_timer_check net.ifnames=0 crashkernel=auto [0.001000] printk: console [ttyS0] enabled [4.191049] bochs-drm :00:02.0: vgaarb: deactivate vga console -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1473527 Title: module ssh-authkey-fingerprints fails Input/output error: /dev/console To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1473527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961982] [NEW] mint 20.1 and 20.3 fuck up drivers
Public bug reported: newer kernels in both versions mess with TBS DVBTV card drivers.. this is piss poor service i have not been able to rebuild working drivers since so called upgrade ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961982 Title: mint 20.1 and 20.3 fuck up drivers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944727] Re: Screen shot leaves HP printer in non-working state
Re-installing the printer using the CUPS browser interface solved the issue. There seem to be some difference between this method and using the Ubuntu Settings tool. Issue is resolved. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944727 Title: Screen shot leaves HP printer in non-working state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1944727/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1956094] Re: deborphan guess-work removes too many files
On 31/12/2021 21:53, Andreas Tille wrote: > [...] > Sorry, but I do not understand the problem. What config files are you > talking about? What is "upgrade-system"? I'm using the command > `deborphan` itself just to learn what package might be a potential > candidate for removal. From time to time I'm using > > apt purge `deborphan` > > but well, that's users responsibility. To learn what is really a "bug" > we need more information that this quoted mail. Hi, Andreas. The Debian/Ubuntu "upgrade-system" package automates updating the APT package list, installing updated packages and removing 'orphaned' packages. It is very convenient for unattended upgrades of multiple computers because it can either be run interactively, or without a controlling terminal. The "upgrade-system" config file is: /etc/upgrade-system.conf By default, "upgrade-system" allows "deborphan to 'guess' which packages to remove: ORPHANOPTS="--guess-all --libdevel" This removes too many packages that are installed by "med-bio-dev' in particular, so I edited the config file to stop "deborphan" guessing: ORPHANOPTS="--no-guess-all --libdevel" It appears that a recent upgrade unconditionally overwrote my edited "upgrade-system.conf", which resulted in most of the packages installed by "med-bio-dev" being removed from five of my bioinformatics servers. Yes, it is a user's responsibility to check but I was caught out by it recently so I posted a bug report because I thought other people might also have the same problem when using "upgrade-system" with defaults. The "upgrade-system" package is very convenient, but the default settings allow "deborphan" to guess what to remove. In my experience, that often results in "deborphan" removing packages that are needed. Happy New Year :-) Tony. -- Minke Informatics Limited, Registered in Scotland - Company No. SC419028 Registered Office: 3 Donview, Bridge of Alford, AB33 8QJ, Scotland (UK) tel. +44(0)19755 63548http://minke-informatics.co.uk mob. +44(0)7985 078324mailto:tony.tra...@minke-informatics.co.uk -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956094 Title: deborphan guess-work removes too many files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upgrade-system/+bug/1956094/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1956094] Re: deborphan guess-work removes too many files
On 31/12/2021 12:23, Martin-Éric Racine wrote: > Those defaults work for the majority of people. > > Settings can be changed as desired by editing the configuration file. > > ** Changed in: upgrade-system (Ubuntu) > Status: New => Won't Fix Hi, Marin. I *have* edited the configuration file, but the "deborphan" default has just caused a lot of damage on multiple systems where I use "upgrade-system" it appears to have overwritten my edited config files during a recent upgrade and, as I reported, "deborphan" removed a large number of packages from five of my servers where I have installed "med-bio" and "med-bio-dev" from the Debian-Med project. I edited the config file after initially running "upgrade-system" precisely because of this. I'm surprised that nobody else has been bitten by this bug! Bye, Tony. -- Minke Informatics Limited, Registered in Scotland - Company No. SC419028 Registered Office: 3 Donview, Bridge of Alford, AB33 8QJ, Scotland (UK) tel. +44(0)19755 63548http://minke-informatics.co.uk mob. +44(0)7985 078324mailto:tony.tra...@minke-informatics.co.uk -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956094 Title: deborphan guess-work removes too many files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upgrade-system/+bug/1956094/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956094] [NEW] deborphan guess-work removes too many files
Public bug reported: The "upgrade-system" utility makes keeping Ubuntu/Debian systems up-to- date very easy, but the default settings for "deborphan" result in too many packages being removed. This can be avoided by changing the default: diff -Naur upgrade-system.conf upgrade-system.conf.dist --- upgrade-system.conf 2021-04-11 17:57:29.23560 +0100 +++ upgrade-system.conf.dist2012-08-13 05:46:22.0 +0100 @@ -7,6 +7,6 @@ UPGRADEOPTS="--fix-broken --purge --show-upgraded dist-upgrade" # See deborphan(1) -ORPHANOPTS="--no-guess-all --libdevel" +ORPHANOPTS="--guess-all --libdevel" #EOF ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: upgrade-system 1.7.3.1 ProcVersionSignature: Ubuntu 5.11.0-43.47~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-43-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Aptdaemon: Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Fri Dec 31 12:05:29 2021 InstallationDate: Installed on 2020-05-02 (607 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: upgrade-system UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.upgrade-system.conf: 2021-04-11T17:57:29.23 ** Affects: upgrade-system (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956094 Title: deborphan guess-work removes too many files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upgrade-system/+bug/1956094/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939455] Re: Upgrading from 20.0.4-2ubuntu1 to 21.0.3-0ubuntu0.2~20.04.1 breaks vlc video output
For the benefit of others I had a similar problem with Kaffeine 2.0.18 on Lubuntu 20.04.3, no video with DVB-T broadcast and only audio working. The upgrade to 21.0.3 broke a system that was stable for about a year. Also Kaffeine will crash changing channels. Running Kaffeine from command prompt shows unable to decode video messages type messages. Finally tracked down this ticket and down leveling to 20.0.4 solved problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939455 Title: Upgrading from 20.0.4-2ubuntu1 to 21.0.3-0ubuntu0.2~20.04.1 breaks vlc video output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1939455/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953687] Re: Samba connected network devices no longer appear in "Windows Network" folder of Nautilus.
Sorry Paride $ aptitude install samba=2:4.13.5+dfsg-2ubuntu2 didn't work due to unmet dependencies for other samba components. However I notice that an update to Samba today has solved the problem and I can access Windows Shares and my backups work OK. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953687 Title: Samba connected network devices no longer appear in "Windows Network" folder of Nautilus. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1953687/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953687] Re: Samba connected network devices no longer appear in "Windows Network" folder of Nautilus.
Sorry Paride $ aptitude install samba=2:4.13.5+dfsg-2ubuntu2 didn't work due to unmet dependencies for other samba components. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953687 Title: Samba connected network devices no longer appear in "Windows Network" folder of Nautilus. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1953687/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1830914] Re: software-properties-gtk does not run at all!
I ran into the same problem, I think, today and had to also reinstall python3-urllib3 before it would work again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1830914 Title: software-properties-gtk does not run at all! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1830914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953687] Re: Samba connected network devices no longer appear in "Windows Network" folder of Nautilus.
I can get to the NAS using its IP address so Déjà Dup must be using the Widows shares. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953687 Title: Samba connected network devices no longer appear in "Windows Network" folder of Nautilus. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1953687/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953687] Re: Samba connected network devices no longer appear in "Windows Network" folder of Nautilus.
I seem to have the same problem as you have. I marked mine as a duplicate of yours as Paride is woking on yours. I have found that it affects my backups as they get saved on my NAS. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953687 Title: Samba connected network devices no longer appear in "Windows Network" folder of Nautilus. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1953687/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953629] Re: Failied to mount Windows share: Invalid argument
*** This bug is a duplicate of bug 1953687 *** https://bugs.launchpad.net/bugs/1953687 ** This bug has been marked a duplicate of bug 1953687 Samba connected network devices no longer appear in "Windows Network" folder of Nautilus. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953629 Title: Failied to mount Windows share: Invalid argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1953629/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953629] Re: Failied to mount Windows share: Invalid argument
** Description changed: When trying to access my NAS using Files or to do a backup which saves on my NAS I get this error message. - Failied to mount Windows share: Invalid argument + Failed to mount Windows share: Invalid argument - I would expect access my NAS. + I would expect access to my NAS. I am using Ubuntu version 21.10 Note that /etc/samba/smb.conf was updated yesterday. samba: - Installed: 2:4.13.14+dfsg-0ubuntu0.21.10.3 - Candidate: 2:4.13.14+dfsg-0ubuntu0.21.10.3 - Version table: - *** 2:4.13.14+dfsg-0ubuntu0.21.10.3 500 - 500 http://gb.archive.ubuntu.com/ubuntu impish-updates/main amd64 Packages - 500 http://security.ubuntu.com/ubuntu impish-security/main amd64 Packages - 100 /var/lib/dpkg/status - 2:4.13.5+dfsg-2ubuntu2 500 - 500 http://gb.archive.ubuntu.com/ubuntu impish/main amd64 Packages + Installed: 2:4.13.14+dfsg-0ubuntu0.21.10.3 + Candidate: 2:4.13.14+dfsg-0ubuntu0.21.10.3 + Version table: + *** 2:4.13.14+dfsg-0ubuntu0.21.10.3 500 + 500 http://gb.archive.ubuntu.com/ubuntu impish-updates/main amd64 Packages + 500 http://security.ubuntu.com/ubuntu impish-security/main amd64 Packages + 100 /var/lib/dpkg/status + 2:4.13.5+dfsg-2ubuntu2 500 + 500 http://gb.archive.ubuntu.com/ubuntu impish/main amd64 Packages NOTE: Previously when I had the same problem, I added client min protocol = NT1 to smb.conf but it has not cured this problem. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: udisks2 2.9.4-1 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.core.rules 70-snap.simplenote.rules 70-snap.qr-code-generator-desktop.rules 70-snap.snap-store.rules 70-snap.chromium.rules 70-snap.easy-openvpn.rules 70-snap.gnome-system-monitor.rules 70-snap.canonical-livepatch.rules 70-snap.firefox.rules Date: Wed Dec 8 14:16:35 2021 InstallationDate: Installed on 2015-06-21 (2362 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: LENOVO 90BX0018UK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=2e321d15-1961-4c45-b1ce-7662ab1eee40 ro quiet splash vt.handoff=7 SourcePackage: udisks2 Symptom: storage Title: No permission to access files on storage device UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/29/2014 dmi.bios.release: 1.68 dmi.bios.vendor: LENOVO dmi.bios.version: O07KT44AUS dmi.board.name: Aptio CRB dmi.board.vendor: LENOVO dmi.board.version: SDK0F82993 WIN dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrO07KT44AUS:bd08/29/2014:br1.68:svnLENOVO:pn90BX0018UK:pvrLenovoE50-00:rvnLENOVO:rnAptioCRB:rvrSDK0F82993WIN:cvnLENOVO:ct3:cvrNone:skuLENOVO_PN_LenovoE50-00: dmi.product.family: IdeaCentre dmi.product.name: 90BX0018UK dmi.product.sku: LENOVO_PN_Lenovo E50-00 dmi.product.version: Lenovo E50-00 dmi.sys.vendor: LENOVO -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953629 Title: Failied to mount Windows share: Invalid argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1953629/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953629] [NEW] Failied to mount Windows share: Invalid argument
Public bug reported: When trying to access my NAS using Files or to do a backup which saves on my NAS I get this error message. Failied to mount Windows share: Invalid argument I would expect access my NAS. I am using Ubuntu version 21.10 Note that /etc/samba/smb.conf was updated yesterday. samba: Installed: 2:4.13.14+dfsg-0ubuntu0.21.10.3 Candidate: 2:4.13.14+dfsg-0ubuntu0.21.10.3 Version table: *** 2:4.13.14+dfsg-0ubuntu0.21.10.3 500 500 http://gb.archive.ubuntu.com/ubuntu impish-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu impish-security/main amd64 Packages 100 /var/lib/dpkg/status 2:4.13.5+dfsg-2ubuntu2 500 500 http://gb.archive.ubuntu.com/ubuntu impish/main amd64 Packages NOTE: Previously when I had the same problem, I added client min protocol = NT1 to smb.conf but it has not cured this problem. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: udisks2 2.9.4-1 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.core.rules 70-snap.simplenote.rules 70-snap.qr-code-generator-desktop.rules 70-snap.snap-store.rules 70-snap.chromium.rules 70-snap.easy-openvpn.rules 70-snap.gnome-system-monitor.rules 70-snap.canonical-livepatch.rules 70-snap.firefox.rules Date: Wed Dec 8 14:16:35 2021 InstallationDate: Installed on 2015-06-21 (2362 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: LENOVO 90BX0018UK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=2e321d15-1961-4c45-b1ce-7662ab1eee40 ro quiet splash vt.handoff=7 SourcePackage: udisks2 Symptom: storage Title: No permission to access files on storage device UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/29/2014 dmi.bios.release: 1.68 dmi.bios.vendor: LENOVO dmi.bios.version: O07KT44AUS dmi.board.name: Aptio CRB dmi.board.vendor: LENOVO dmi.board.version: SDK0F82993 WIN dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrO07KT44AUS:bd08/29/2014:br1.68:svnLENOVO:pn90BX0018UK:pvrLenovoE50-00:rvnLENOVO:rnAptioCRB:rvrSDK0F82993WIN:cvnLENOVO:ct3:cvrNone:skuLENOVO_PN_LenovoE50-00: dmi.product.family: IdeaCentre dmi.product.name: 90BX0018UK dmi.product.sku: LENOVO_PN_Lenovo E50-00 dmi.product.version: Lenovo E50-00 dmi.sys.vendor: LENOVO ** Affects: samba (Ubuntu) Importance: Undecided Status: New ** Affects: udisks2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish wayland-session ** Also affects: samba (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953629 Title: Failied to mount Windows share: Invalid argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1953629/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951756] [NEW] 317
Public bug reported: flatpak document portal session opened no listed reason for deployment or operation ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: flatpak (not installed) ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-40-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Nov 21 18:44:30 2021 InstallationDate: Installed on 2020-04-01 (599 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: flatpak UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: flatpak (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951756 Title: 317 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/1951756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951707] [NEW] install crashed
Public bug reported: install just crashed i dont know why ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15.17 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.445.1 Date: Sun Nov 21 09:45:52 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15.17 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951707 Title: install crashed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1951707/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951596] Re: rmlint --gui (aka "Shredder") does not find any files
This is the error running rmlint with the default 16 PB value: ajt@pilot:~$ rmlint --no-with-color -T duplicates --see-symlinks --partial-hidden -c sh:handler=remove --hardlinked --crossdev --size 1-18446744073709551615 --max-depth 512 -o json -c json:oneline /home/ajt/Documents/Work/Minke ERROR: cannot parse --size: Max is smaller than min. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951596 Title: rmlint --gui (aka "Shredder") does not find any files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rmlint/+bug/1951596/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951596] [NEW] rmlint --gui (aka "Shredder") does not find any files
Public bug reported:
There is a bug in the default max file size of 16 Petabytes in
"Shredder" being interpreted as a negative number and causing an error
exit when "rmlint" is run by the GUI when the selected folder is
scanned. In addition, simply changing the Units from e.g. Petabyte to
Gigabyte does not enable the "Apply" button, which is only enabled by
changing the default value of 16 to e.g. 1.
Another error occurs because the /tmp/app.log file is not removed on
exit from the "Shredder" GUI. If a previous user created this log file
it can't be overwritten or removed if the s't'icky-bit is set on the
/tmp directory. Including the PID in the app.log filename would avoid
the problem and allow concurrent instances of "Shredder" to write to
"$$app.log".
The following logs captured from a CLI invocation of "Shredder"
illustrate how the negative max size problem can be fixed by changing
the default values, but the /tmp/app.log problem remains:
ajt@pilot:~$ rmlint --gui
--- Logging error ---
Traceback (most recent call last):
File "/usr/lib/python3.8/logging/handlers.py", line 69, in emit
if self.shouldRollover(record):
File "/usr/lib/python3.8/logging/handlers.py", line 183, in shouldRollover
self.stream = self._open()
File "/usr/lib/python3.8/logging/__init__.py", line 1176, in _open
return open(self.baseFilename, self.mode, encoding=self.encoding)
PermissionError: [Errno 13] Permission denied: '/tmp/app.log'
Call stack:
File "/tmp/.shredder-bootstrap.py.EE1CD1", line 19, in
File "/usr/lib/python3/dist-packages/shredder/__init__.py", line 42, in
run_gui
ROOT_LOGGER.info('Starting up.')
Message: 'Starting up.'
Arguments: ()
13:55:33 ⚐ INFO root:42: Starting up.
--- Logging error ---
Traceback (most recent call last):
File "/usr/lib/python3.8/logging/handlers.py", line 69, in emit
if self.shouldRollover(record):
File "/usr/lib/python3.8/logging/handlers.py", line 183, in shouldRollover
self.stream = self._open()
File "/usr/lib/python3.8/logging/__init__.py", line 1176, in _open
return open(self.baseFilename, self.mode, encoding=self.encoding)
PermissionError: [Errno 13] Permission denied: '/tmp/app.log'
Call stack:
File "/tmp/.shredder-bootstrap.py.EE1CD1", line 19, in
File "/usr/lib/python3/dist-packages/shredder/__init__.py", line 43, in
run_gui
sys.exit(APP.run([sys.argv[0]]))
File "/usr/lib/python3/dist-packages/gi/overrides/Gio.py", line 44, in run
return Gio.Application.run(self, *args, **kwargs)
File "/usr/lib/python3/dist-packages/shredder/application.py", line 102, in
do_startup
LOGGER.info('Loading resources from: ' + resource_file)
Message: 'Loading resources from:
/usr/lib/python3/dist-packages/shredder/resources/shredder.gresource'
Arguments: ()
13:55:33 ⚐ INFO application:102: Loading resources from:
/usr/lib/python3/dist-packages/shredder/resources/shredder.gresource
--- Logging error ---
Traceback (most recent call last):
File "/usr/lib/python3.8/logging/handlers.py", line 69, in emit
if self.shouldRollover(record):
File "/usr/lib/python3.8/logging/handlers.py", line 183, in shouldRollover
self.stream = self._open()
File "/usr/lib/python3.8/logging/__init__.py", line 1176, in _open
return open(self.baseFilename, self.mode, encoding=self.encoding)
PermissionError: [Errno 13] Permission denied: '/tmp/app.log'
Call stack:
File "/tmp/.shredder-bootstrap.py.EE1CD1", line 19, in
File "/usr/lib/python3/dist-packages/shredder/__init__.py", line 43, in
run_gui
sys.exit(APP.run([sys.argv[0]]))
File "/usr/lib/python3/dist-packages/gi/overrides/Gio.py", line 44, in run
return Gio.Application.run(self, *args, **kwargs)
File "/usr/lib/python3/dist-packages/shredder/application.py", line 148, in
do_startup
LOGGER.debug('Instancing views.')
Message: 'Instancing views.'
Arguments: ()
13:55:33 ⚙ DEBUGapplication:148: Instancing views.
--- Logging error ---
Traceback (most recent call last):
File "/usr/lib/python3.8/logging/handlers.py", line 69, in emit
if self.shouldRollover(record):
File "/usr/lib/python3.8/logging/handlers.py", line 183, in shouldRollover
self.stream = self._open()
File "/usr/lib/python3.8/logging/__init__.py", line 1176, in _open
return open(self.baseFilename, self.mode, encoding=self.encoding)
PermissionError: [Errno 13] Permission denied: '/tmp/app.log'
Call stack:
File "/tmp/.shredder-bootstrap.py.EE1CD1", line 19, in
File "/usr/lib/python3/dist-packages/shredder/__init__.py", line 43, in
run_gui
sys.exit(APP.run([sys.argv[0]]))
File "/usr/lib/python3/dist-packages/gi/overrides/Gio.py", line 44, in run
return Gio.Application.run(self, *args, **kwargs)
File "/usr/lib/python3/dist-packages/shredder/application.py", line 150, in
do_startup
self.win.views.add_view(LocationView(self), 'locations')
File "/usr/lib/python3/dist-packages/shredder/views/locations.py", line 290,
in __init__
self.load_entries_from_disk(entrie
[Bug 1943564] Re: [SRU] Backport xrt 202020.2.8.743-0ubuntu1 to focal
** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943564 Title: [SRU] Backport xrt 202020.2.8.743-0ubuntu1 to focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xrt/+bug/1943564/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933609] Re: Locking screen crashes X/Wayland with nouveau when multiple monitors are plugged in
I am seeing a similar issue with a second monitor plugged in. I am using nouveau and it crashes the X server and logs me out. I have attached a log of what happened. This is NOT connected with a screen lock, it happens randomly. Display is: *-display description: VGA compatible controller product: GK107GLM [Quadro K1100M] vendor: NVIDIA Corporation physical id: 0 bus info: pci@:01:00.0 version: a1 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress vga_controller bus_master cap_list rom configuration: driver=nouveau latency=0 resources: irq:37 memory:d100-d1ff memory:7000-7fff memory:8000-81ff ioport:5000(size=128) memory:c-d ** Attachment added: "The text file shows the nouveau error and the X server crashing." https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1933609/+attachment/5536495/+files/CrashLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933609 Title: Locking screen crashes X/Wayland with nouveau when multiple monitors are plugged in To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1933609/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943564] Re: [SRU] Backport xrt 202020.2.8.743-0ubuntu1 to focal
Hi @Alfonso - how do I change it? I don't see see/understand how. Let me know and I'll fix it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943564 Title: [SRU] Backport xrt 202020.2.8.743-0ubuntu1 to focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xrt/+bug/1943564/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943564] Re: [SRU] Backport xrt 202020.2.8.743-0ubuntu1 to focal
I verified this. I had a little bit of trouble getting focal-proposed working but once I did I was able to update xrt-embedded and I saw everything work properly from there. I saw the Xilinx platform ICD in the proper location and clinfo began showing the platform IDs properly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943564 Title: [SRU] Backport xrt 202020.2.8.743-0ubuntu1 to focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xrt/+bug/1943564/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1941752]
*** Bug 443651 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1941752 Title: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable To manage notifications about this bug go to: https://bugs.launchpad.net/gwenview/+bug/1941752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1941752]
*** Bug 443069 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1941752 Title: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable To manage notifications about this bug go to: https://bugs.launchpad.net/gwenview/+bug/1941752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944727] Re: Screen shot leaves HP printer in non-working state
Here's an example file that produces the issue. ** Attachment added: "This file only print once on my HP printer" https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1944727/+attachment/5527367/+files/Print-once.odt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944727 Title: Screen shot leaves HP printer in non-working state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1944727/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944727] [NEW] Screen shot leaves HP printer in non-working state
Public bug reported: This is a weird bug and difficult to debug. However: I have Ubuntu 21.04 fully updated as of 2021-09-23. Printing something that has been captured by gnome-screenshot will print fine with my HP Color Laserjet Pro M477fdw printer. However, it will leave the printer in a state where any subsequent print will fail, regardless of document or machine. Even printing from a Macbook Air will fail. The printer reports any subsequent file to be printed as corrupt and nothing comes out. The only way to recover from this state is to power-cycle the printer. This ONLY happen with screenshots. It happens BOTH when the screenshot has been pasted into Libre Office, and when the screenshot has been saved to a .png and printed from Image Viewer. This issue does however NOT happen on my CANON Pro 100 inkjet printer. So blame the printer, yes, but I have not been able to repeat it without gnome-screenshot. It's the common factor. Before Ubuntu 21.04 the default screen capture program was different, or at least it looked different, but previously I had no problem. I have been running Ubuntu with this printer for many years. Summary: I can only print screenshots once. I expect to be able to print two screen shots in sequence without requiring to power cycle the printer in between. I can upload an example file (that only print once) if required. ** Affects: gnome-screenshot (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944727 Title: Screen shot leaves HP printer in non-working state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1944727/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943348] [NEW] none
Public bug reported: none too ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15.10 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckMismatches: ./pool/main/g/gcc-9/libstdc++-9-dev_9.3.0-17ubuntu1~20.04_amd64.deb CasperMD5CheckResult: skip CasperVersion: 1.445.1 CurrentDesktop: ubuntu:GNOME Date: Sat Sep 11 18:05:41 2021 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity LiveMediaBuild: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15.10 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943348 Title: none To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1943348/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894407] Re: linux-tools: can perf be linked against libbfd, maybe statically?
I've prepared a patch that uses a single long-running instance of addr2line for each dso, instead of one per address request. It dramatically speeds up e.g. `perf script` operation (I don't know if it solves OP's problem but it could be relevant!). Discussion on linux-perf-users mailing list: https://lore.kernel.org/linux-perf- users/20210910102307.2055484-1-to...@leastfixedpoint.com/ Background: https://eighty-twenty.org/2021/09/09/perf-addr2line-speed- improvement -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894407 Title: linux-tools: can perf be linked against libbfd, maybe statically? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1872210] Re: thick black window borders on "x2go" remote MATE session
On 20/08/2021 22:08, carlosLang wrote: > Same happens to me, using X2GO, connecting to Ubuntu 20.04 in WSL2. > > This worked for me: > Control Center > Look and Feel > Mate Teak > Windows > Window Manager > Select: Marco (no composition) > > It removes the thick border, leaving a very thin one. > Hi, Carlos. Great, that works for me too - Problem solved. Thanks, Tony. -- Minke Informatics Limited, Registered in Scotland - Company No. SC419028 Registered Office: 3 Donview, Bridge of Alford, AB33 8QJ, Scotland (UK) tel. +44(0)19755 63548http://minke-informatics.co.uk mob. +44(0)7985 078324mailto:tony.tra...@minke-informatics.co.uk -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872210 Title: thick black window borders on "x2go" remote MATE session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1872210/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940731] [NEW] I installed Ubuntu 20.04 LTS today and my laptop touchpad is suddenly not working. But it seems to be fine while I use windows on the same laptop.
Public bug reported: cat /proc/bus/input/devices I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab83 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input3 U: Uniq= H: Handlers=sysrq kbd event3 leds B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0003 Vendor=046d Product=c542 Version=0111 N: Name="Logitech Wireless Receiver Mouse" P: Phys=usb-:00:14.0-9/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-9/1-9:1.0/0003:046D:C542.0001/input/input4 U: Uniq= H: Handlers=mouse0 event4 B: PROP=0 B: EV=17 B: KEY=1f 0 0 0 0 B: REL=903 B: MSC=10 I: Bus=0019 Vendor= Product= Version= N: Name="Ideapad extra buttons" P: Phys=ideapad/input0 S: Sysfs=/devices/pci:00/:00:1f.0/PNP0C09:00/VPC2004:00/input/input5 U: Uniq= H: Handlers=rfkill kbd event5 B: PROP=0 B: EV=13 B: KEY=81000800100c03 4430 0 2 B: MSC=10 I: Bus=0003 Vendor=174f Product=1176 Version=0028 N: Name="Integrated Camera: Integrated C" P: Phys=usb-:00:14.0-5/button S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/input/input6 U: Uniq= H: Handlers=kbd event6 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input7 U: Uniq= H: Handlers=kbd event7 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Mic" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input8 U: Uniq= H: Handlers=event8 B: PROP=0 B: EV=21 B: SW=10 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Headphone" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input9 U: Uniq= H: Handlers=event9 B: PROP=0 B: EV=21 B: SW=4 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=3" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input10 U: Uniq= H: Handlers=event10 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=7" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input11 U: Uniq= H: Handlers=event11 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=8" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input12 U: Uniq= H: Handlers=event12 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=9" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input13 U: Uniq= H: Handlers=event13 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=10" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input14 U: Uniq= H: Handlers=event14 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=11" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input15 U: Uniq= H: Handlers=event15 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=12" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input16 U: Uniq= H: Handlers=event16 B: PROP=0 B: EV=21 B: SW=140 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-27-generic 5.11.0-27.29~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Aug 21 10:56:31 2021 InstallationDate: Installed on 2021-08-21 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.11 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubu
[Bug 1938809] [NEW] package lxd (not installed) failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 1
Public bug reported: During do-release-upgrade from Ubuntu 18.0.4 (most recent) to Ubuntu 20.04.2 LTS During the release upgrade, LXD was upgrading to the snap version 4.16 while I was originally using the dpkg 3.x. It looks like the upgrade for LXD worked correctly, but lxd-tools couldn't be upgraded because it was looking for lxd (>= 1:0.9) which is no longer installed (because now it's a snap). ProblemType: Package DistroRelease: Ubuntu 20.04 ProcVersionSignature: Ubuntu 4.15.0-151.157-generic 4.15.18 Uname: Linux 4.15.0-151-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Aug 3 14:01:00 2021 ErrorMessage: new lxd package pre-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-02-17 (533 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 Snap: lxd 4.16 (latest/stable) Title: package lxd (not installed) failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2021-08-03 (0 days ago) ** Affects: lxd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal uec-images -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938809 Title: package lxd (not installed) failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1938809/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1936669] Re: Software Update won't install version 21.04
I have now upgraded to 21.04, and all seems OK. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1936669 Title: Software Update won't install version 21.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1936669/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1937073] [NEW] package libtsan0:amd64 11.1.0-1ubuntu1~21.04 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
Public bug reported: error reported during system update ProblemType: Package DistroRelease: Ubuntu 21.04 Package: libtsan0:amd64 11.1.0-1ubuntu1~21.04 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Jul 21 12:54:05 2021 DuplicateSignature: package:libtsan0:amd64:11.1.0-1ubuntu1~21.04 Setting up libnvidia-ifr1-460:i386 (460.91.03-0ubuntu0.21.04.1) ... dpkg: error processing package libtsan0:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2021-04-23 (89 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Python3Details: /usr/bin/python3.9, Python 3.9.5, python3-minimal, 3.9.4-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.9ubuntu1 apt 2.2.3 SourcePackage: gcc-11 Title: package libtsan0:amd64 11.1.0-1ubuntu1~21.04 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gcc-11 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1937073 Title: package libtsan0:amd64 11.1.0-1ubuntu1~21.04 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-11/+bug/1937073/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1936669] Re: Software Update won't install version 21.04
I ran apt-get install dh-python this removed python-is-python2 and upgraded dh-python apt-cache policy dh-python now shows dh-python: Installed: 4.20200925 Candidate: 4.20200925 Version table: *** 4.20200925 500 500 http://gb.archive.ubuntu.com/ubuntu groovy/universe amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu groovy/universe i386 Packages 100 /var/lib/dpkg/status I then used apt-get install python and was told to install python-is-python2, which I did. This removed dh-python. I will now try to upgrade to 21.04, when I can -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1936669 Title: Software Update won't install version 21.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1936669/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1936669] Re: Software Update won't install version 21.04
I ran apt-get install dh-python this removed python-is-python2 and upgraded dh-python apt-cache policy dh-python now shows dh-python: Installed: 4.20200925 Candidate: 4.20200925 Version table: *** 4.20200925 500 500 http://gb.archive.ubuntu.com/ubuntu groovy/universe amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu groovy/universe i386 Packages 100 /var/lib/dpkg/status When I can, I will now see if I can upgrade to 21.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1936669 Title: Software Update won't install version 21.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1936669/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1936669] Re: Software Update won't install version 21.04
It shows: dh-python: Installed: 4.20191017ubuntu7 Candidate: 4.20200925 Version table: 4.20200925 500 500 http://gb.archive.ubuntu.com/ubuntu groovy/universe amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu groovy/universe i386 Packages *** 4.20191017ubuntu7 100 100 /var/lib/dpkg/status -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1936669 Title: Software Update won't install version 21.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1936669/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1936669] Re: Software Update won't install version 21.04
Thanks for your message Brian. do-release-upgrade reports: Checking for a new Ubuntu release Please install all available updates for your release before upgrading. Then returns to the prompt. If I then run apt-get update apt-get upgrade apt-get dist-upgrade I get nothing except the message that dh-python is being kept back. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1936669 Title: Software Update won't install version 21.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1936669/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1936669] Re: Software Update won't install version 21.04
Thanks for your message Brian. do-release-upgrade reports: Checking for a new Ubuntu release Please install all available updates for your release before upgrading. Then returns to the prompt. If I then run apt-get update apt-get upgrade apt-get dist-upgrade I get nothing except the message that dh-python is being kept back. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1936669 Title: Software Update won't install version 21.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1936669/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1936669] Re: Software Update won't install version 21.04
running the commands: apt-get update apt-get upgrade apt-get dist-upgrade also do not upgrade to 21.04. The last two commands report that dh-python has been kept back. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1936669 Title: Software Update won't install version 21.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1936669/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1936669] [NEW] Software Update won't install version 21.04
Public bug reported: Every time my system installs new software it tells me that a new version (21.04) of Ubuntu is available to update from my current version 20.10. There is a Upgrade button for me to press. I expect it to call the Upgrade routine to install version 21.04. Instead, nothing happens. ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1936669 Title: Software Update won't install version 21.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1936669/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933118] Re: Screen freeze
And it occurred a second time, just a few minutes after I posted the previous message. in case it is useful, I attach the output from dmesg created while the UI was frozen, also the Xorg.log and another copy of the output from journalctl -b-1 > prevboot.txt Again the freeze corresponded with a movement of the USB external mouse. ** Attachment added: "zip contains dmesg, Xorg.0.log and prevboot.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1933118/+attachment/5506992/+files/info.zip -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933118 Title: Screen freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1933118/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933118] Re: Screen freeze
As requested I am adding the output from journalctl -b-1 > prevboot.txt Just to add some further info: * I reinstalled my Ubuntu system yesterday back to the same version (my wifi and bluetooth were not working and I could find no way to get them back, so this freeze has happened with a standard install of 20.04 LTS downloaded and installed yesterday afternoon and otherwise is working normally. * The freeze happened immediately after I installed and used Microsoft Teams (64 bit). That might be a coincidence. * The freeze often happens as I move the mouse from my external monitor to my main (laptop) screen. ** Attachment added: "This is the output from journalctl -b-1 > prevboot.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1933118/+attachment/5506986/+files/prevboot.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933118 Title: Screen freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1933118/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933118] Re: Screen freeze
1. Look in /var/crash for crash files There are files in /var/crash but dated June 15 2021, one from _usr_lib_slack_slack and one from _opt_google_chrome_chrome. Nothing from 21 June (yesterday) when the issue last happened. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID There is nothing recent reported on that page. The most recent reports correspond to the Slack (https://errors.ubuntu.com/oops/0b7133f8-cdfb-11eb-9cf8-fa163ee63de6) and Chrome (https://errors.ubuntu.com/oops/1277eade-cdfb-11eb-a58b-fa163e983629) issues from June 15. There is an older gnome-shell error dated 2021-05-21 16:05 with this link: https://errors.ubuntu.com/oops/3373e2ec-ba4b- 11eb-9041-fa163e102db1 and also an even earlier gnome-shell error dated 2021-03-23 14:03 with this link https://errors.ubuntu.com/oops/0bcaf4d6-8be6-11eb-93be-fa163e6cac46 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. I have applied that work around and will follow that advice. * Next time the problem happens, wait 10 seconds, reboot and then run: The next time the issue happens i will attach the output from journalctl. * Check the 'Extensions' app to ensure you don't have any extensions other than the three Ubuntu extensions The only three extensions reported are "Desktop Icons", "Ubuntu AppIndicators", and "Ubuntu Dock" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933118 Title: Screen freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1933118/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933199] [NEW] Mainline builds for v5.10.37 to v5.10.45 contain packages for v5.11.0
Public bug reported: On the mainline kernel server, all folders for kernels v5.10.37 to v5.10.45 contain packages for kernel v5.11.0. https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.10.37/ ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: build kernel mainline ** Attachment added: "v5.10.45 page with links for v5.11.0" https://bugs.launchpad.net/bugs/1933199/+attachment/5506192/+files/Selection_009.png ** Description changed: - On the mainline PPA server, all folders for kernels v5.10.37 to v5.10.45 - contain packages for kernel v5.11.0! + On the mainline kernel server, all folders for kernels v5.10.37 to + v5.10.45 contain packages for kernel v5.11.0. https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.10.37/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933199 Title: Mainline builds for v5.10.37 to v5.10.45 contain packages for v5.11.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933199/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933118] [NEW] Xorg freeze
Public bug reported: This bug appears to be a deadlock of some kind. It most often happens when I move the mouse (external USB mouse), but it has once happened when I left the computer logged in but idle and has sometimes happened in video conferences. When the problem occurs, the mouse cursor still moves and any audio continues being audible for a while, but the UI is frozen and unresponsive. The fan gets very loud as if the computer is doing a lot of work. If I try the 'REISUB' method of shutting down, it usually does not work. If I remote log in and do a shutdown, it takes several minutes to actually shut down - as if waiting for some process to time out. I haven't any obvious errors for this bug, and i don't know where to look for possible error messages. It is possible that if there is a deadlock, there is no error message, unless shutting down causes the process to generate an error message. The bug happens very often, sometimes several times a week. If you could tell me what commands to run when the problem occurs in order to gather more information, I can remote login and run those commands. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.143 Fri Mar 12 07:24:47 UTC 2021 GCC version: ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jun 21 15:14:30 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: v4l2loopback, 0.12.3, 5.8.0-53-generic, x86_64: installed v4l2loopback, 0.12.3, 5.8.0-55-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Since before I upgraded GraphicsCard: NVIDIA Corporation GK107GLM [Quadro K1100M] [10de:0ff6] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GK107GLM [Quadro K1100M] [103c:2256] InstallationDate: Installed on 2021-01-11 (161 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Hewlett-Packard HP ZBook 17 G2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-55-generic root=UUID=62a0870e-1f83-43a4-a2ff-864901a24fb6 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/23/2015 dmi.bios.release: 1.12 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: M70 Ver. 01.12 dmi.board.name: 2255 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 03.10 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.ec.firmware.release: 3.16 dmi.modalias: dmi:bvnHewlett-Packard:bvrM70Ver.01.12:bd09/23/2015:br1.12:efr3.16:svnHewlett-Packard:pnHPZBook17G2:pvrA3009DD10203:rvnHewlett-Packard:rn2255:rvrKBCVersion03.10:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP ZBook 17 G2 dmi.product.sku: G6Z41AV dmi.product.version: A3009DD10203 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal freeze possible-manual-nvidia-install third-party-packages ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933118 Title: Xorg freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1933118/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885530] Re: password doesn't leave dots on being entered
I had faced this issue as mentioned in the askubuntu. Here is the bug report I had generated using `ubuntu-bug sddm`. Let me know if there is something else need to be done. ** Attachment added: "Bug report" https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/1885530/+attachment/5504745/+files/apport.sddm.fws6f4ha.apport -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885530 Title: password doesn't leave dots on being entered To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/1885530/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880359] Re: "Malformed output discovered from systemd list-unit-files"
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-1753 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-10691 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-1738 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-1736 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880359 Title: "Malformed output discovered from systemd list-unit-files" To manage notifications about this bug go to: https://bugs.launchpad.net/ansible/+bug/1880359/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880359] Re: "Malformed output discovered from systemd list-unit-files"
** Also affects: ansible via https://github.com/DataDog/ansible-datadog/issues/274 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880359 Title: "Malformed output discovered from systemd list-unit-files" To manage notifications about this bug go to: https://bugs.launchpad.net/ansible/+bug/1880359/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880359] Re: "Malformed output discovered from systemd list-unit-files"
The fix version is 2.9.8, not 2.9.7 Upstream commit: https://github.com/ansible/ansible/commit/bd4fdb1ca23fb043789042074f3f9fa4fb07fbf1 Upstream PR: https://github.com/ansible/ansible/pull/68211 This is particularly bad on Focal systems managing other Focal systems, and affects DataDog playbooks in particular: https://github.com/DataDog/ansible-datadog/issues/274 Please could you upload a 2.9.8 package to focal? ** Bug watch added: github.com/DataDog/ansible-datadog/issues #274 https://github.com/DataDog/ansible-datadog/issues/274 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880359 Title: "Malformed output discovered from systemd list-unit-files" To manage notifications about this bug go to: https://bugs.launchpad.net/ansible/+bug/1880359/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926819] Re: Empty MOTD on up-to-date systems (includes fix)
There is still value in a "you are fully up to date" message, and I would expect such a behaviour change to be optional. This has not been announced and I find myself unable to opt out. Offering users more choice is great, but, I have no choices here. That doesn't sit right. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926819 Title: Empty MOTD on up-to-date systems (includes fix) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1926819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927190] [NEW] I can't upgrade my Ubuntu 18.04 to 20.04
Public bug reported: I tried several times to upgrade distribution Ubuntu 18.04 (LTS) to Ubuntu 20.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.44 ProcVersionSignature: Ubuntu 4.15.0-136.140-generic 4.15.18 Uname: Linux 4.15.0-136-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_4_15_0_136_140_generic_76 ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 CrashDB: ubuntu Date: Wed May 5 08:59:40 2021 InstallationDate: Installed on 2014-06-27 (2503 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2021-05-05 (0 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927190 Title: I can't upgrade my Ubuntu 18.04 to 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1927190/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1915704] Re: Specific pointing device disappear/disconnect when standby
Could it be that the Sunplus Innovation Technology Inc. Optical Mouse is the one with wrote Trust on the backside ? This one looks like "made in China", that's why I ask. Those are used to imitate everything. I think my brother might have said the mouse he has is a real one and the other, an imitation of it. That would also explain why it's the only one reacting like this. I have got no trouble at all since I use the Logitech mouse (I mistaken it for one from Microsoft) again. *Besides that, I would like to ask your help about something.* I installed Ubuntu Server 20.10 "Groovy" I installed as a graphic interface and window manager: Lightdm & Cinnamon At the open of the lock screen when the computer starts I can see a "old-fashion" window with username and password. But when I'm logged on, and the screen locks after some time, another style of lock screen appears. It has to fill-text-boxes for username and password directly on a glass transparent, showing the background image. *My question is, how do I get the same lock screen to appear at boot logon ?* *Actual system détails:* *OS:* Ubuntu Cinnamon 20.10 x86_64 *Kernel:* 5.8.0-50-generic *Packages:* 2513 (dpkg), 8 (snap) *Shell:* bash 5.0.17 *Resolution:* 1920x1080, 1600x900 *DE:* Cinnamon 4.6.7 *WM:* Mutter (Muffin) *Theme:* Eleganse-dark (Adapta-Nokto) *Theme:* Adwaita-dark [GTK2/3] *Icons:* Vinyl [GTK2/3] *Terminal:* gnome-terminal *CPU:* Intel i7-10700K (16) @ 5.100GHz *GPU:* NVIDIA GeForce GT 740 *GPU:* Intel Device 9bc5 *Memory:* 3046MiB / 15591MiB *~$ ls -l /usr/share/xsessions/* total 24 -rw-r--r-- 1 root root 268 fév 10 21:50 cinnamon2d.desktop -rw-r--r-- 1 root root 155 fév 10 21:50 cinnamon.desktop -rw-r--r-- 1 root root 180 oct 7 2020 Lubuntu.desktop -rw-r--r-- 1 root root 2266 jun 4 2020 lxqt.desktop -rw-r--r-- 1 root root 198 mar 11 00:07 openbox.desktop -rw-r--r-- 1 root root 242 sep 17 2020 unity.desktop *I would also like to get rid of those I'm not using.* I'm trying to find out what's the best configuration for my own needs in all this variety of choices. The point is I need only server software, no desktop tools, except for system management and configuration like Gedit or Gimp. I use my own browser, so no need for the Firefox neider Office package because I've all those with Google. At top of that, I'm a gamer, and intend to make more users choose Ubuntu to do so. To resume: I've a media server and gaming station at the same time, with local area support for SMB, DLNA, iPXE gdm3 is heavy, gave me less trouble with Steam. I had problems with snaps applications accessing rights. Where gnome apps worked fine. It was more heavy to run and already updated to Hirsute that wasn't compatible with some of my needs in 32bit for Steam. It seems they want to stop 32bit developpement in order to give priority to 64bit. So I reinstalled Groovy like I wrote before. lightdm seems a little buggy at the installation of Steam, but it works at the end. I presume it was because of the display manager not installed like it should at first run. I would like how to get control over the display manager and desktop interface running on my Ubuntu Server base. *Maybe you can help me resolve this without reinstalling.* ___ MARTIN BERBEL, Tony GSM: +32 (0) 477 / 33.12.48 -- Le lun. 3 mai 2021 à 04:50, Daniel van Vugt <1915...@bugs.launchpad.net> a écrit : > ** Changed in: linux (Ubuntu) >Status: Expired => Invalid > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1915704 > > Title: > Specific pointing device disappear/disconnect when standby > > Status in linux package in Ubuntu: > Invalid > > Bug description: > Ubuntu 20.10 groovy (x86-64) > Cinnamon 4.6.7 > Kernel 5.8.0-43-generic > > I installed Ubuntu while using a Microsft mise. > This one works great with no problem. The buttons are old and used out, > so I changed it with a Trust with RGB. The Trust mouse seems disconnected > when going to standby (need keyboard, since mouse seems disconnected to > show password prompt). > > The only way to get the mouse back to work, is to disconnect and > reconnect it. > > What's narrow in this, is that I've tried again with the old pointing > device (from Microsoft), and this one still is recognised in standby, > and I'm able to click to open the password prompt. > > I've read this repport: > https://bugs.launchpad.net/ubuntu/+bug/1573454 > > But it seems not totaly the same, since I've the problem with a > pointer and not the other one. > > ProblemType: Bug > DistroRelease: Ubuntu 20.10 > Package: xorg 1:7.7+19ub
Re: [Bug 1915704] Re: Specific pointing device disappear/disconnect when standby
Hi, Sorry for this late return, but I changed the OS version in order to see if it's better with ubuntu server and cinnamon desktop on it, instead of desktop gnome + cinnamon. And indeed, it's a lot better ones installed. It wasn't a bug. It seems I have some power peaks that are made by my refrigerator when turning on. My computer reacted to it only with these RGB mice, where it wrote Trust on it, but it could be an imitation of a Trust mouse. I've tried several different mices, and only the RGB one gave this trouble. Maybe because of this RGB in it, it uses more power and calls the surge to it. It's narrow. I've no other inconvenience due to this power issue in my little appartement. Because of that I was thinking about buying an UPS, but it's really expensive to have one for the power supply I use on my PC (750W) So I think it will do for now with no RGB mouse ;) ___ MARTIN BERBEL, Tony GSM: +32 (0) 477 / 33.12.48 LinkedIn: https://be.linkedin.com/in/tony-martin-berbel Facebook: https://www.facebook.com/Wingarmac -- Le lun. 22 févr. 2021 à 07:20, Daniel van Vugt <1915...@bugs.launchpad.net> a écrit : > Thanks for the bug report. > > Firstly, if you have 'tlp' installed then please uninstall it because it > can cause problems like this. > > Secondly, you mention 'Microsoft' and 'Trust' mice in the bug > description but your logs only ever seem to show: > > * Logitech USB Optical Mouse > * Sunplus Innovation Technology Inc. Optical Mouse > > So I would like to understand which is the one you call the 'Trust' > mouse. While the 'Trust' mouse is plugged in, please run: > > lsusb > lsusb2.txt > > and attach the resulting text file here. > > > ** Package changed: xorg (Ubuntu) => linux (Ubuntu) > > ** Changed in: linux (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1915704 > > Title: > Specific pointing device disappear/disconnect when standby > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > Ubuntu 20.10 groovy (x86-64) > Cinnamon 4.6.7 > Kernel 5.8.0-43-generic > > I installed Ubuntu while using a Microsft mise. > This one works great with no problem. The buttons are old and used out, > so I changed it with a Trust with RGB. The Trust mouse seems disconnected > when going to standby (need keyboard, since mouse seems disconnected to > show password prompt). > > The only way to get the mouse back to work, is to disconnect and > reconnect it. > > What's narrow in this, is that I've tried again with the old pointing > device (from Microsoft), and this one still is recognised in standby, > and I'm able to click to open the password prompt. > > I've read this repport: > https://bugs.launchpad.net/ubuntu/+bug/1573454 > > But it seems not totaly the same, since I've the problem with a > pointer and not the other one. > > ProblemType: Bug > DistroRelease: Ubuntu 20.10 > Package: xorg 1:7.7+19ubuntu15 > ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18 > Uname: Linux 5.8.0-43-generic x86_64 > NonfreeKernelModules: nvidia_modeset nvidia > .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] est un dossier: > '/proc/driver/nvidia/capabilities/gpu0' > .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] est un dossier: > '/proc/driver/nvidia/capabilities/mig' > .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] est un dossier: > '/proc/driver/nvidia/gpus/:01:00.0' > .proc.driver.nvidia.registry: Binary: "" > .proc.driver.nvidia.suspend: suspend hibernate resume > .proc.driver.nvidia.suspend_depth: default modeset uvm > .proc.driver.nvidia.version: >NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.32.03 Sun Dec 27 > 19:00:34 UTC 2020 >GCC version: gcc version 10.2.0 (Ubuntu 10.2.0-13ubuntu1) > ApportVersion: 2.20.11-0ubuntu50.5 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' > CasperMD5CheckResult: skip > CompositorRunning: None > CurrentDesktop: X-Cinnamon > Date: Mon Feb 15 12:07:10 2021 > DistUpgraded: Fresh install > DistroCodename: groovy > DistroVariant: ubuntu > DkmsStatus: nvidia, 460.32.03, 5.8.0-43-generic, x86_64: installed > ExtraDebuggingInterest: Yes > GraphicsCard: >NVIDIA Corporation GK107 [GeForce GTX 650] [10de:0fc6] (rev a1) > (prog-if 00 [VGA controller]) >
[Bug 1924802] Re: sysdemd-shim not working
I have used the fix in https://askubuntu.com/questions/838491/dpkg- divert-error-rename-involves-overwriting-error-after-upgrading- from-16-04/838673#838673. I hope it cures the problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924802 Title: sysdemd-shim not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924802/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924802] Re: sysdemd-shim not working
I have re-run the command on the correct computer, which is an ASUS 32-bit 1015PEM eeepc. I hope you can sort out the reports. (The wrong computer was the LENOVO E50-00) ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924802 Title: sysdemd-shim not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924802/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924802] Re: sysdemd-shim not working
My apologies, I ran the apport-collect command on the wrong computer. I added this bug because the distribution update program told me to file a bug report -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924802 Title: sysdemd-shim not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924802/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924802] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1924802/+attachment/5489079/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924802 Title: sysdemd-shim not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924802/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924802] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1924802/+attachment/5489077/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924802 Title: sysdemd-shim not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924802/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924802] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1924802/+attachment/5489071/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924802 Title: sysdemd-shim not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924802/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924802] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1924802/+attachment/5489076/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924802 Title: sysdemd-shim not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924802/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924802] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1924802/+attachment/5489081/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924802 Title: sysdemd-shim not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924802/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924802] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1924802/+attachment/5489068/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924802 Title: sysdemd-shim not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924802/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924802] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1924802/+attachment/5489075/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924802 Title: sysdemd-shim not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924802/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924802] Re: sysdemd-shim not working
apport information ** Tags added: bionic ** Description changed: Having updated from 16.04 to 18.04 sysdemd-shim is not working --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tony 2940 F pulseaudio /dev/snd/controlC0: tony 2940 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 HibernationDevice: RESUME=UUID=212a98a0-7b07-45e6-a8e5-ead03b54d027 InstallationDate: Installed on 2015-06-21 (2126 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: LENOVO 90BX0018UK Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=2e321d15-1961-4c45-b1ce-7662ab1eee40 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.190.3 Tags: groovy Uname: Linux 5.8.0-50-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-23 (175 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/29/2014 dmi.bios.release: 1.68 dmi.bios.vendor: LENOVO dmi.bios.version: O07KT44AUS dmi.board.name: Aptio CRB dmi.board.vendor: LENOVO dmi.board.version: SDK0F82993 WIN dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrO07KT44AUS:bd08/29/2014:br1.68:svnLENOVO:pn90BX0018UK:pvrLenovoE50-00:rvnLENOVO:rnAptioCRB:rvrSDK0F82993WIN:cvnLENOVO:ct3:cvrNone: dmi.product.family: IdeaCentre dmi.product.name: 90BX0018UK dmi.product.sku: LENOVO_PN_Lenovo E50-00 dmi.product.version: Lenovo E50-00 dmi.sys.vendor: LENOVO + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.23 + Architecture: i386 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: tony 1617 F pulseaudio + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 18.04 + HibernationDevice: RESUME=UUID=fcc3dc2b-0a3b-4dcf-98d9-b1f03b2c812e + InstallationDate: Installed on 2012-04-27 (3276 days ago) + InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) + MachineType: ASUSTeK Computer INC. 1015PEM + NonfreeKernelModules: wl + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-142-generic root=UUID=abf837ae-032d-4686-8803-27a1376ee9c5 ro quiet splash vt.handoff=1 + ProcVersionSignature: Ubuntu 4.15.0-142.146-generic 4.15.18 + RelatedPackageVersions: + linux-restricted-modules-4.15.0-142-generic N/A + linux-backports-modules-4.15.0-142-generic N/A + linux-firmware 1.173.20 + Tags: bionic + Uname: Linux 4.15.0-142-generic i686 + UpgradeStatus: Upgraded to bionic on 2021-04-16 (0 days ago) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 10/06/2010 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 0801 + dmi.board.asset.tag: To Be Filled By O.E.M. + dmi.board.name: 1015PE + dmi.board.vendor: ASUSTeK Computer INC. + dmi.board.version: x.xx + dmi.chassis.asset.tag: 0x + dmi.chassis.type: 10 + dmi.chassis.vendor: ASUSTeK Computer INC. + dmi.chassis.version: x.x + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0801:bd10/06/2010:svnASUSTeKComputerINC.:pn1015PEM:pvrx.x:rvnASUSTeKComputerINC.:rn1015PE:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x: + dmi.product.family: Eee PC + dmi.product.name: 1015PEM + dmi.product.version: x.x + dmi.sys.vendor: ASUSTeK Computer INC. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1924802/+attachment/5489067/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924802 Title: sysdemd-shim not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924802/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924802] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1924802/+attachment/5489080/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924802 Title: sysdemd-shim not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924802/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924802] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1924802/+attachment/5489078/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924802 Title: sysdemd-shim not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924802/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924802] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1924802/+attachment/5489074/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924802 Title: sysdemd-shim not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924802/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924802] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1924802/+attachment/5489073/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924802 Title: sysdemd-shim not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924802/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924802] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1924802/+attachment/5489072/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924802 Title: sysdemd-shim not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924802/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924802] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1924802/+attachment/5489070/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924802 Title: sysdemd-shim not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924802/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924802] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1924802/+attachment/5489069/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924802 Title: sysdemd-shim not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924802/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
