[Touch-packages] [Bug 2042710] [NEW] Can't enter cryptsetup password on MacBook Pro 2017 (MacBookPro14, 1) due to missing kernel modules in initramfs
Public bug reported: I have a MacBook Pro 2017 (MacBookPro14,1) with an encrypted root partition, which I decrypt via passphrase during boot, at the "Please unlock disk nvme0n1p4_crypt" prompt. Using 23.04 "Lunar" this worked fine. However after upgrading to 23.10 "Mantic", the built-in keyboard doesn't work for entering the passphrase. Quickest workaround: plug in a USB keyboard for entering the passphrase. Workaround: add the following modules to "/etc/initramfs-tools/modules": spi_pxa2xx_platform intel_lpss_pci ... then "sudo update-initramfs -u". I found that both kernel modules were required to get the keyboard recognised in initramfs. I did a bit of digging into what changed for 23.10. It could potentially (?) be commit 2df78bbb143884b9601a32608e12e43d40ccb0b0 "Do not install ARM/RISCV specific modules on other architectures". I had a look into how dracut handles it. Turns out that they specifically include "spi_pxa2xx_platform" after reporting a similar bug report in Fedora: https://bugzilla.redhat.com/show_bug.cgi?id=2166209 I don't know how (if?) they handle the 2nd module, "intel_lpss_pci". Anyway, I don't need an immediate fix since the workaround works for me. Just posting this for further investigation, and for any other MacBook Pro users in the same situation. Thanks for working on Ubuntu, I think you're all amazing! ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2042710 Title: Can't enter cryptsetup password on MacBook Pro 2017 (MacBookPro14,1) due to missing kernel modules in initramfs Status in initramfs-tools package in Ubuntu: New Bug description: I have a MacBook Pro 2017 (MacBookPro14,1) with an encrypted root partition, which I decrypt via passphrase during boot, at the "Please unlock disk nvme0n1p4_crypt" prompt. Using 23.04 "Lunar" this worked fine. However after upgrading to 23.10 "Mantic", the built-in keyboard doesn't work for entering the passphrase. Quickest workaround: plug in a USB keyboard for entering the passphrase. Workaround: add the following modules to "/etc/initramfs- tools/modules": spi_pxa2xx_platform intel_lpss_pci ... then "sudo update-initramfs -u". I found that both kernel modules were required to get the keyboard recognised in initramfs. I did a bit of digging into what changed for 23.10. It could potentially (?) be commit 2df78bbb143884b9601a32608e12e43d40ccb0b0 "Do not install ARM/RISCV specific modules on other architectures". I had a look into how dracut handles it. Turns out that they specifically include "spi_pxa2xx_platform" after reporting a similar bug report in Fedora: https://bugzilla.redhat.com/show_bug.cgi?id=2166209 I don't know how (if?) they handle the 2nd module, "intel_lpss_pci". Anyway, I don't need an immediate fix since the workaround works for me. Just posting this for further investigation, and for any other MacBook Pro users in the same situation. Thanks for working on Ubuntu, I think you're all amazing! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2042710/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2042711] [NEW] Weird "system restart required" screen placement
Public bug reported:
After upgrading from 23.04 to 23.10 it now appears that what I assume to
be the front-end of apt displays a button at the top with what looks
like a WORLD HEALTH ORGANIZATION logo.
The only indicator that this is related to apt is only when hovering the
mouse cursor over any portion of this blue button will say that a reboot
is required.
I have this problem on 2 systems with the same exact upgrade history
path.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog:
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: MATE
Date: Sat Nov 4 00:15:10 2023
DistUpgraded: 2023-10-13 19:39:05,380 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
virtualbox/7.0.10, 6.5.0-10-generic, x86_64: installed
virtualbox/7.0.10, 6.5.0-9-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / RX
540X/550/550X] [1002:699f] (rev c7) (prog-if 00 [VGA controller])
Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon
540/540X/550/550X / RX 540X/550/550X] [1002:0b04]
InstallationDate: Installed on 2023-04-14 (203 days ago)
InstallationMedia: Ubuntu-MATE 22.10 "Kinetic Kudu" - Release amd64 (20221018)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=/dev/mapper/vgubuntu--mate-root ro ipv6.disable=1 pcie_aspm=off
ipv6.disable=1 pcie_aspm=off
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to mantic on 2023-10-13 (21 days ago)
dmi.bios.date: 03/13/2023
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 6063
dmi.board.asset.tag: Default string
dmi.board.name: TUF X470-PLUS GAMING
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr6063:bd03/13/2023:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFX470-PLUSGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1
** Affects: xorg (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug mantic ubuntu
** Attachment added: "That thing at the top now always appear when a new kernel
was installed and that a reboot is pending."
https://bugs.launchpad.net/bugs/2042711/+attachment/5715799/+files/Screenshot%20at%202023-10-26%2018-06-20.png
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2042711
Title:
Weird "system restart required" screen placement
Status in xorg package in Ubuntu:
New
Bug description:
After upgrading from 23.04 to 23.10 it now appears that what I assume
to be the front-end of apt displays a button at the top with what
looks like a WORLD HEALTH ORGANIZATION logo.
The only indicator that this is related to apt is only when hovering
the mouse cursor over any portion of this blue button will say that a
reboot is required.
I have this problem on 2 systems with the same exact upgrade history
path.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog:
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: MATE
Date: Sat Nov 4 00:15:10 2023
DistUpgraded: 2023-10-13 19:39:05,380 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
virtualbox/7.0.10, 6.5.0-10-generic, x86_64: installed
virtualbox/7.0.10, 6.5.0-9-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO
[Touch-packages] [Bug 2042708] Re: Monitor preferences isn't fluid after 3rd monitor plugged in
** Attachment added: "Is this a bug or is this a feature? Notice how the size
of everything (object monitor and font size) Decreased?"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2042708/+attachment/5715798/+files/trimon-3.png
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2042708
Title:
Monitor preferences isn't fluid after 3rd monitor plugged in
Status in xorg package in Ubuntu:
New
Bug description:
I have just upgraded from dual monitors by adding one up now up to
three.
Detecting the monitor went ok. However recalibration messed up my
screen positions.
Another issue is that when attempting to recreate physical setup under
"monitor preferences" isn't very friendly. Read: you need to battle
with it.
By "battle with it" I mean that you cannot just choose any monitor and
flip it over per it's physical position. In my case I was able to
replicate my setup after having dragged the right-most monitor instead
of the center one. As moving the center one brought hell in the
interface.
By "hell in the interface" I mean that the flow of the monitors wasn't
easy. It is impossible to simply drag and drop the monitor wherever
but instead it will move down into some impossible position and REFUSE
to go back up, or worst, to it's original place.
Before plugging in the 3rd monitor I had a full workspace displayed in
the regular left/right format.
After plugging in my 3rd monitor that workspace had been separated and
broken. So instead of dragging the mouse from the left monitor to the
right one as regularly I had to access it from the left side.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: MATE
Date: Fri Nov 3 23:47:50 2023
DistUpgraded: 2023-10-13 19:39:05,380 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
virtualbox/7.0.10, 6.5.0-10-generic, x86_64: installed
virtualbox/7.0.10, 6.5.0-9-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X /
RX 540X/550/550X] [1002:699f] (rev c7) (prog-if 00 [VGA controller])
Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon
540/540X/550/550X / RX 540X/550/550X] [1002:0b04]
InstallationDate: Installed on 2023-04-14 (203 days ago)
InstallationMedia: Ubuntu-MATE 22.10 "Kinetic Kudu" - Release amd64 (20221018)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=/dev/mapper/vgubuntu--mate-root ro ipv6.disable=1 pcie_aspm=off
ipv6.disable=1 pcie_aspm=off
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to mantic on 2023-10-13 (21 days ago)
dmi.bios.date: 03/13/2023
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 6063
dmi.board.asset.tag: Default string
dmi.board.name: TUF X470-PLUS GAMING
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr6063:bd03/13/2023:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFX470-PLUSGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
modified.conffile..etc.cron.daily.apport: [deleted]
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2042708/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help :
[Touch-packages] [Bug 2042708] Re: Monitor preferences isn't fluid after 3rd monitor plugged in
** Attachment added: "After much work I was able to finally bring a screen down
a fix the way those screens were set"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2042708/+attachment/5715797/+files/trimon-2.png
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2042708
Title:
Monitor preferences isn't fluid after 3rd monitor plugged in
Status in xorg package in Ubuntu:
New
Bug description:
I have just upgraded from dual monitors by adding one up now up to
three.
Detecting the monitor went ok. However recalibration messed up my
screen positions.
Another issue is that when attempting to recreate physical setup under
"monitor preferences" isn't very friendly. Read: you need to battle
with it.
By "battle with it" I mean that you cannot just choose any monitor and
flip it over per it's physical position. In my case I was able to
replicate my setup after having dragged the right-most monitor instead
of the center one. As moving the center one brought hell in the
interface.
By "hell in the interface" I mean that the flow of the monitors wasn't
easy. It is impossible to simply drag and drop the monitor wherever
but instead it will move down into some impossible position and REFUSE
to go back up, or worst, to it's original place.
Before plugging in the 3rd monitor I had a full workspace displayed in
the regular left/right format.
After plugging in my 3rd monitor that workspace had been separated and
broken. So instead of dragging the mouse from the left monitor to the
right one as regularly I had to access it from the left side.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: MATE
Date: Fri Nov 3 23:47:50 2023
DistUpgraded: 2023-10-13 19:39:05,380 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
virtualbox/7.0.10, 6.5.0-10-generic, x86_64: installed
virtualbox/7.0.10, 6.5.0-9-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X /
RX 540X/550/550X] [1002:699f] (rev c7) (prog-if 00 [VGA controller])
Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon
540/540X/550/550X / RX 540X/550/550X] [1002:0b04]
InstallationDate: Installed on 2023-04-14 (203 days ago)
InstallationMedia: Ubuntu-MATE 22.10 "Kinetic Kudu" - Release amd64 (20221018)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=/dev/mapper/vgubuntu--mate-root ro ipv6.disable=1 pcie_aspm=off
ipv6.disable=1 pcie_aspm=off
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to mantic on 2023-10-13 (21 days ago)
dmi.bios.date: 03/13/2023
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 6063
dmi.board.asset.tag: Default string
dmi.board.name: TUF X470-PLUS GAMING
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr6063:bd03/13/2023:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFX470-PLUSGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
modified.conffile..etc.cron.daily.apport: [deleted]
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2042708/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2042708] Re: Monitor preferences isn't fluid after 3rd monitor plugged in
Since I know some of you like to watch here is what it looks like when I
screen captured from left to right.
** Attachment added: "trimon-1.png"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2042708/+attachment/5715796/+files/trimon-1.png
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2042708
Title:
Monitor preferences isn't fluid after 3rd monitor plugged in
Status in xorg package in Ubuntu:
New
Bug description:
I have just upgraded from dual monitors by adding one up now up to
three.
Detecting the monitor went ok. However recalibration messed up my
screen positions.
Another issue is that when attempting to recreate physical setup under
"monitor preferences" isn't very friendly. Read: you need to battle
with it.
By "battle with it" I mean that you cannot just choose any monitor and
flip it over per it's physical position. In my case I was able to
replicate my setup after having dragged the right-most monitor instead
of the center one. As moving the center one brought hell in the
interface.
By "hell in the interface" I mean that the flow of the monitors wasn't
easy. It is impossible to simply drag and drop the monitor wherever
but instead it will move down into some impossible position and REFUSE
to go back up, or worst, to it's original place.
Before plugging in the 3rd monitor I had a full workspace displayed in
the regular left/right format.
After plugging in my 3rd monitor that workspace had been separated and
broken. So instead of dragging the mouse from the left monitor to the
right one as regularly I had to access it from the left side.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: MATE
Date: Fri Nov 3 23:47:50 2023
DistUpgraded: 2023-10-13 19:39:05,380 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
virtualbox/7.0.10, 6.5.0-10-generic, x86_64: installed
virtualbox/7.0.10, 6.5.0-9-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X /
RX 540X/550/550X] [1002:699f] (rev c7) (prog-if 00 [VGA controller])
Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon
540/540X/550/550X / RX 540X/550/550X] [1002:0b04]
InstallationDate: Installed on 2023-04-14 (203 days ago)
InstallationMedia: Ubuntu-MATE 22.10 "Kinetic Kudu" - Release amd64 (20221018)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=/dev/mapper/vgubuntu--mate-root ro ipv6.disable=1 pcie_aspm=off
ipv6.disable=1 pcie_aspm=off
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to mantic on 2023-10-13 (21 days ago)
dmi.bios.date: 03/13/2023
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 6063
dmi.board.asset.tag: Default string
dmi.board.name: TUF X470-PLUS GAMING
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr6063:bd03/13/2023:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFX470-PLUSGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
modified.conffile..etc.cron.daily.apport: [deleted]
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2042708/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help :
[Touch-packages] [Bug 2042708] Re: Monitor preferences isn't fluid after 3rd monitor plugged in
Before plugging in this 3rd monitor both of my screens (the ones in red
and blue colors) were close to another without any green space in
between them.
Of course in order to reach the spawned desktop in between any of those
monitors I need to drag the mouse quite a long road before it reaches as
we can see from the amount of green spacing in between them.
** Attachment added: "trimon-0.png"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2042708/+attachment/5715795/+files/trimon-0.png
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2042708
Title:
Monitor preferences isn't fluid after 3rd monitor plugged in
Status in xorg package in Ubuntu:
New
Bug description:
I have just upgraded from dual monitors by adding one up now up to
three.
Detecting the monitor went ok. However recalibration messed up my
screen positions.
Another issue is that when attempting to recreate physical setup under
"monitor preferences" isn't very friendly. Read: you need to battle
with it.
By "battle with it" I mean that you cannot just choose any monitor and
flip it over per it's physical position. In my case I was able to
replicate my setup after having dragged the right-most monitor instead
of the center one. As moving the center one brought hell in the
interface.
By "hell in the interface" I mean that the flow of the monitors wasn't
easy. It is impossible to simply drag and drop the monitor wherever
but instead it will move down into some impossible position and REFUSE
to go back up, or worst, to it's original place.
Before plugging in the 3rd monitor I had a full workspace displayed in
the regular left/right format.
After plugging in my 3rd monitor that workspace had been separated and
broken. So instead of dragging the mouse from the left monitor to the
right one as regularly I had to access it from the left side.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: MATE
Date: Fri Nov 3 23:47:50 2023
DistUpgraded: 2023-10-13 19:39:05,380 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
virtualbox/7.0.10, 6.5.0-10-generic, x86_64: installed
virtualbox/7.0.10, 6.5.0-9-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X /
RX 540X/550/550X] [1002:699f] (rev c7) (prog-if 00 [VGA controller])
Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon
540/540X/550/550X / RX 540X/550/550X] [1002:0b04]
InstallationDate: Installed on 2023-04-14 (203 days ago)
InstallationMedia: Ubuntu-MATE 22.10 "Kinetic Kudu" - Release amd64 (20221018)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=/dev/mapper/vgubuntu--mate-root ro ipv6.disable=1 pcie_aspm=off
ipv6.disable=1 pcie_aspm=off
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to mantic on 2023-10-13 (21 days ago)
dmi.bios.date: 03/13/2023
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 6063
dmi.board.asset.tag: Default string
dmi.board.name: TUF X470-PLUS GAMING
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr6063:bd03/13/2023:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFX470-PLUSGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
modified.conffile..etc.cron.daily.apport: [deleted]
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
[Touch-packages] [Bug 2042708] [NEW] Monitor preferences isn't fluid after 3rd monitor plugged in
Public bug reported:
I have just upgraded from dual monitors by adding one up now up to
three.
Detecting the monitor went ok. However recalibration messed up my screen
positions.
Another issue is that when attempting to recreate physical setup under
"monitor preferences" isn't very friendly. Read: you need to battle with
it.
By "battle with it" I mean that you cannot just choose any monitor and
flip it over per it's physical position. In my case I was able to
replicate my setup after having dragged the right-most monitor instead
of the center one. As moving the center one brought hell in the
interface.
By "hell in the interface" I mean that the flow of the monitors wasn't
easy. It is impossible to simply drag and drop the monitor wherever but
instead it will move down into some impossible position and REFUSE to go
back up, or worst, to it's original place.
Before plugging in the 3rd monitor I had a full workspace displayed in
the regular left/right format.
After plugging in my 3rd monitor that workspace had been separated and
broken. So instead of dragging the mouse from the left monitor to the
right one as regularly I had to access it from the left side.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: MATE
Date: Fri Nov 3 23:47:50 2023
DistUpgraded: 2023-10-13 19:39:05,380 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
virtualbox/7.0.10, 6.5.0-10-generic, x86_64: installed
virtualbox/7.0.10, 6.5.0-9-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / RX
540X/550/550X] [1002:699f] (rev c7) (prog-if 00 [VGA controller])
Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon
540/540X/550/550X / RX 540X/550/550X] [1002:0b04]
InstallationDate: Installed on 2023-04-14 (203 days ago)
InstallationMedia: Ubuntu-MATE 22.10 "Kinetic Kudu" - Release amd64 (20221018)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=/dev/mapper/vgubuntu--mate-root ro ipv6.disable=1 pcie_aspm=off
ipv6.disable=1 pcie_aspm=off
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to mantic on 2023-10-13 (21 days ago)
dmi.bios.date: 03/13/2023
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 6063
dmi.board.asset.tag: Default string
dmi.board.name: TUF X470-PLUS GAMING
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr6063:bd03/13/2023:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFX470-PLUSGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
modified.conffile..etc.cron.daily.apport: [deleted]
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1
** Affects: xorg (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug mantic ubuntu
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2042708
Title:
Monitor preferences isn't fluid after 3rd monitor plugged in
Status in xorg package in Ubuntu:
New
Bug description:
I have just upgraded from dual monitors by adding one up now up to
three.
Detecting the monitor went ok. However recalibration messed up my
screen positions.
Another issue is that when attempting to recreate physical setup under
"monitor preferences" isn't very friendly. Read: you need to battle
with it.
By "battle with it" I mean that you cannot just choose any monitor and
flip it over per it's physical position. In my case I was able to
replicate my setup after having dragged the right-most monitor instead
of the center one. As moving the
[Touch-packages] [Bug 2042680] Re: lsb_release shows incorrect Ubuntu version
> The issue here is that the base-files package for Ubuntu Noble Desktop for Raspberry PI has not been updated to 24.04. Um... no? $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=24.04 DISTRIB_CODENAME=noble DISTRIB_DESCRIPTION="Ubuntu Noble Numbat (development branch)" $ apt policy base-files base-files: Installed: 13ubuntu4 Candidate: 13ubuntu4 Version table: *** 13ubuntu4 500 500 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages 100 /var/lib/dpkg/status $ What was the full URL of the image you used? ** Changed in: base-files (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/2042680 Title: lsb_release shows incorrect Ubuntu version Status in base-files package in Ubuntu: Incomplete Bug description: Testing Ubuntu Noble Desktop for Raspberry PI daily ISO dated 03-11-2023 After installing and rebooting running lsb_release -a shows version 23.10 not 24.04 ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: lsb-release 12.0-2 ProcVersionSignature: Ubuntu 6.5.0-1006.8-raspi 6.5.3 Uname: Linux 6.5.0-1006-raspi aarch64 ApportVersion: 2.27.0-0ubuntu5 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Nov 3 16:24:14 2023 Dependencies: PackageArchitecture: all ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: lsb-release-minimal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2042680/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2040657] Re: bluez does not detect Logitech Pebble M350, no option to connect
Thank you Daniel! Over the week I upgraded my laptop to Mantic, so can
no longer test for Jammy.
I still can't discover my logitech mice in Mantic, so maybe still the
same situation.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2040657
Title:
bluez does not detect Logitech Pebble M350, no option to connect
Status in bluez package in Ubuntu:
Incomplete
Bug description:
I lost the proprietary USB dongle and decided I wanted to try
bluetooth with this particular mouse. I am able to connect with
bluetooth on Windows 11, but the device doesn't even show up in
`bluetoothctl scan on`.
This is seen on Jammy with bluez 5.64-0ubuntu1
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-03-06 (242 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
NonfreeKernelModules: zfs
Package: bluez 5.68-0ubuntu1
PackageArchitecture: amd64
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/usr/bin/zsh
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Tags: mantic wayland-session
Uname: Linux 6.5.0-10-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-10-31 (3 days ago)
UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sbuild
sudo
_MarkForUpload: True
dmi.bios.date: 07/18/2023
dmi.bios.release: 1.58
dmi.bios.vendor: LENOVO
dmi.bios.version: N2HET75W (1.58 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20QDUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.25
dmi.modalias:
dmi:bvnLENOVO:bvrN2HET75W(1.58):bd07/18/2023:br1.58:efr1.25:svnLENOVO:pn20QDUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDUS:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QD_BU_Think_FM_ThinkPadX1Carbon7th:
dmi.product.family: ThinkPad X1 Carbon 7th
dmi.product.name: 20QDUS
dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
dmi.product.version: ThinkPad X1 Carbon 7th
dmi.sys.vendor: LENOVO
hciconfig:
hci0:Type: Primary Bus: USB
BD Address: D0:AB:D5:BB:40:FD ACL MTU: 1021:4 SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY
RX bytes:21473 acl:0 sco:0 events:2871 errors:0
TX bytes:692880 acl:0 sco:0 commands:2838 errors:0
mtime.conffile..etc.bluetooth.main.conf: 2023-08-16T12:28:27.725767
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2040657/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2040657] acpidump.txt
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/2040657/+attachment/5715734/+files/acpidump.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2040657
Title:
bluez does not detect Logitech Pebble M350, no option to connect
Status in bluez package in Ubuntu:
Incomplete
Bug description:
I lost the proprietary USB dongle and decided I wanted to try
bluetooth with this particular mouse. I am able to connect with
bluetooth on Windows 11, but the device doesn't even show up in
`bluetoothctl scan on`.
This is seen on Jammy with bluez 5.64-0ubuntu1
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-03-06 (242 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
NonfreeKernelModules: zfs
Package: bluez 5.68-0ubuntu1
PackageArchitecture: amd64
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/usr/bin/zsh
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Tags: mantic wayland-session
Uname: Linux 6.5.0-10-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-10-31 (3 days ago)
UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sbuild
sudo
_MarkForUpload: True
dmi.bios.date: 07/18/2023
dmi.bios.release: 1.58
dmi.bios.vendor: LENOVO
dmi.bios.version: N2HET75W (1.58 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20QDUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.25
dmi.modalias:
dmi:bvnLENOVO:bvrN2HET75W(1.58):bd07/18/2023:br1.58:efr1.25:svnLENOVO:pn20QDUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDUS:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QD_BU_Think_FM_ThinkPadX1Carbon7th:
dmi.product.family: ThinkPad X1 Carbon 7th
dmi.product.name: 20QDUS
dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
dmi.product.version: ThinkPad X1 Carbon 7th
dmi.sys.vendor: LENOVO
hciconfig:
hci0:Type: Primary Bus: USB
BD Address: D0:AB:D5:BB:40:FD ACL MTU: 1021:4 SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY
RX bytes:21473 acl:0 sco:0 events:2871 errors:0
TX bytes:692880 acl:0 sco:0 commands:2838 errors:0
mtime.conffile..etc.bluetooth.main.conf: 2023-08-16T12:28:27.725767
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2040657/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2040657] modified.conffile..etc.bluetooth.main.conf.txt
apport information
** Attachment added: "modified.conffile..etc.bluetooth.main.conf.txt"
https://bugs.launchpad.net/bugs/2040657/+attachment/5715736/+files/modified.conffile..etc.bluetooth.main.conf.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2040657
Title:
bluez does not detect Logitech Pebble M350, no option to connect
Status in bluez package in Ubuntu:
Incomplete
Bug description:
I lost the proprietary USB dongle and decided I wanted to try
bluetooth with this particular mouse. I am able to connect with
bluetooth on Windows 11, but the device doesn't even show up in
`bluetoothctl scan on`.
This is seen on Jammy with bluez 5.64-0ubuntu1
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-03-06 (242 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
NonfreeKernelModules: zfs
Package: bluez 5.68-0ubuntu1
PackageArchitecture: amd64
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/usr/bin/zsh
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Tags: mantic wayland-session
Uname: Linux 6.5.0-10-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-10-31 (3 days ago)
UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sbuild
sudo
_MarkForUpload: True
dmi.bios.date: 07/18/2023
dmi.bios.release: 1.58
dmi.bios.vendor: LENOVO
dmi.bios.version: N2HET75W (1.58 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20QDUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.25
dmi.modalias:
dmi:bvnLENOVO:bvrN2HET75W(1.58):bd07/18/2023:br1.58:efr1.25:svnLENOVO:pn20QDUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDUS:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QD_BU_Think_FM_ThinkPadX1Carbon7th:
dmi.product.family: ThinkPad X1 Carbon 7th
dmi.product.name: 20QDUS
dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
dmi.product.version: ThinkPad X1 Carbon 7th
dmi.sys.vendor: LENOVO
hciconfig:
hci0:Type: Primary Bus: USB
BD Address: D0:AB:D5:BB:40:FD ACL MTU: 1021:4 SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY
RX bytes:21473 acl:0 sco:0 events:2871 errors:0
TX bytes:692880 acl:0 sco:0 commands:2838 errors:0
mtime.conffile..etc.bluetooth.main.conf: 2023-08-16T12:28:27.725767
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2040657/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2040657] syslog.txt
apport information
** Attachment added: "syslog.txt"
https://bugs.launchpad.net/bugs/2040657/+attachment/5715738/+files/syslog.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2040657
Title:
bluez does not detect Logitech Pebble M350, no option to connect
Status in bluez package in Ubuntu:
Incomplete
Bug description:
I lost the proprietary USB dongle and decided I wanted to try
bluetooth with this particular mouse. I am able to connect with
bluetooth on Windows 11, but the device doesn't even show up in
`bluetoothctl scan on`.
This is seen on Jammy with bluez 5.64-0ubuntu1
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-03-06 (242 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
NonfreeKernelModules: zfs
Package: bluez 5.68-0ubuntu1
PackageArchitecture: amd64
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/usr/bin/zsh
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Tags: mantic wayland-session
Uname: Linux 6.5.0-10-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-10-31 (3 days ago)
UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sbuild
sudo
_MarkForUpload: True
dmi.bios.date: 07/18/2023
dmi.bios.release: 1.58
dmi.bios.vendor: LENOVO
dmi.bios.version: N2HET75W (1.58 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20QDUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.25
dmi.modalias:
dmi:bvnLENOVO:bvrN2HET75W(1.58):bd07/18/2023:br1.58:efr1.25:svnLENOVO:pn20QDUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDUS:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QD_BU_Think_FM_ThinkPadX1Carbon7th:
dmi.product.family: ThinkPad X1 Carbon 7th
dmi.product.name: 20QDUS
dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
dmi.product.version: ThinkPad X1 Carbon 7th
dmi.sys.vendor: LENOVO
hciconfig:
hci0:Type: Primary Bus: USB
BD Address: D0:AB:D5:BB:40:FD ACL MTU: 1021:4 SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY
RX bytes:21473 acl:0 sco:0 events:2871 errors:0
TX bytes:692880 acl:0 sco:0 commands:2838 errors:0
mtime.conffile..etc.bluetooth.main.conf: 2023-08-16T12:28:27.725767
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2040657/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2040657] rfkill.txt
apport information
** Attachment added: "rfkill.txt"
https://bugs.launchpad.net/bugs/2040657/+attachment/5715737/+files/rfkill.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2040657
Title:
bluez does not detect Logitech Pebble M350, no option to connect
Status in bluez package in Ubuntu:
Incomplete
Bug description:
I lost the proprietary USB dongle and decided I wanted to try
bluetooth with this particular mouse. I am able to connect with
bluetooth on Windows 11, but the device doesn't even show up in
`bluetoothctl scan on`.
This is seen on Jammy with bluez 5.64-0ubuntu1
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-03-06 (242 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
NonfreeKernelModules: zfs
Package: bluez 5.68-0ubuntu1
PackageArchitecture: amd64
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/usr/bin/zsh
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Tags: mantic wayland-session
Uname: Linux 6.5.0-10-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-10-31 (3 days ago)
UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sbuild
sudo
_MarkForUpload: True
dmi.bios.date: 07/18/2023
dmi.bios.release: 1.58
dmi.bios.vendor: LENOVO
dmi.bios.version: N2HET75W (1.58 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20QDUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.25
dmi.modalias:
dmi:bvnLENOVO:bvrN2HET75W(1.58):bd07/18/2023:br1.58:efr1.25:svnLENOVO:pn20QDUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDUS:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QD_BU_Think_FM_ThinkPadX1Carbon7th:
dmi.product.family: ThinkPad X1 Carbon 7th
dmi.product.name: 20QDUS
dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
dmi.product.version: ThinkPad X1 Carbon 7th
dmi.sys.vendor: LENOVO
hciconfig:
hci0:Type: Primary Bus: USB
BD Address: D0:AB:D5:BB:40:FD ACL MTU: 1021:4 SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY
RX bytes:21473 acl:0 sco:0 events:2871 errors:0
TX bytes:692880 acl:0 sco:0 commands:2838 errors:0
mtime.conffile..etc.bluetooth.main.conf: 2023-08-16T12:28:27.725767
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2040657/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2040657] UdevDb.txt
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/2040657/+attachment/5715733/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2040657
Title:
bluez does not detect Logitech Pebble M350, no option to connect
Status in bluez package in Ubuntu:
Incomplete
Bug description:
I lost the proprietary USB dongle and decided I wanted to try
bluetooth with this particular mouse. I am able to connect with
bluetooth on Windows 11, but the device doesn't even show up in
`bluetoothctl scan on`.
This is seen on Jammy with bluez 5.64-0ubuntu1
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-03-06 (242 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
NonfreeKernelModules: zfs
Package: bluez 5.68-0ubuntu1
PackageArchitecture: amd64
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/usr/bin/zsh
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Tags: mantic wayland-session
Uname: Linux 6.5.0-10-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-10-31 (3 days ago)
UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sbuild
sudo
_MarkForUpload: True
dmi.bios.date: 07/18/2023
dmi.bios.release: 1.58
dmi.bios.vendor: LENOVO
dmi.bios.version: N2HET75W (1.58 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20QDUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.25
dmi.modalias:
dmi:bvnLENOVO:bvrN2HET75W(1.58):bd07/18/2023:br1.58:efr1.25:svnLENOVO:pn20QDUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDUS:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QD_BU_Think_FM_ThinkPadX1Carbon7th:
dmi.product.family: ThinkPad X1 Carbon 7th
dmi.product.name: 20QDUS
dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
dmi.product.version: ThinkPad X1 Carbon 7th
dmi.sys.vendor: LENOVO
hciconfig:
hci0:Type: Primary Bus: USB
BD Address: D0:AB:D5:BB:40:FD ACL MTU: 1021:4 SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY
RX bytes:21473 acl:0 sco:0 events:2871 errors:0
TX bytes:692880 acl:0 sco:0 commands:2838 errors:0
mtime.conffile..etc.bluetooth.main.conf: 2023-08-16T12:28:27.725767
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2040657/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2040657] getfacl.txt
apport information
** Attachment added: "getfacl.txt"
https://bugs.launchpad.net/bugs/2040657/+attachment/5715735/+files/getfacl.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2040657
Title:
bluez does not detect Logitech Pebble M350, no option to connect
Status in bluez package in Ubuntu:
Incomplete
Bug description:
I lost the proprietary USB dongle and decided I wanted to try
bluetooth with this particular mouse. I am able to connect with
bluetooth on Windows 11, but the device doesn't even show up in
`bluetoothctl scan on`.
This is seen on Jammy with bluez 5.64-0ubuntu1
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-03-06 (242 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
NonfreeKernelModules: zfs
Package: bluez 5.68-0ubuntu1
PackageArchitecture: amd64
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/usr/bin/zsh
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Tags: mantic wayland-session
Uname: Linux 6.5.0-10-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-10-31 (3 days ago)
UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sbuild
sudo
_MarkForUpload: True
dmi.bios.date: 07/18/2023
dmi.bios.release: 1.58
dmi.bios.vendor: LENOVO
dmi.bios.version: N2HET75W (1.58 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20QDUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.25
dmi.modalias:
dmi:bvnLENOVO:bvrN2HET75W(1.58):bd07/18/2023:br1.58:efr1.25:svnLENOVO:pn20QDUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDUS:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QD_BU_Think_FM_ThinkPadX1Carbon7th:
dmi.product.family: ThinkPad X1 Carbon 7th
dmi.product.name: 20QDUS
dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
dmi.product.version: ThinkPad X1 Carbon 7th
dmi.sys.vendor: LENOVO
hciconfig:
hci0:Type: Primary Bus: USB
BD Address: D0:AB:D5:BB:40:FD ACL MTU: 1021:4 SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY
RX bytes:21473 acl:0 sco:0 events:2871 errors:0
TX bytes:692880 acl:0 sco:0 commands:2838 errors:0
mtime.conffile..etc.bluetooth.main.conf: 2023-08-16T12:28:27.725767
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2040657/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2040657] ProcModules.txt
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/2040657/+attachment/5715732/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2040657
Title:
bluez does not detect Logitech Pebble M350, no option to connect
Status in bluez package in Ubuntu:
Incomplete
Bug description:
I lost the proprietary USB dongle and decided I wanted to try
bluetooth with this particular mouse. I am able to connect with
bluetooth on Windows 11, but the device doesn't even show up in
`bluetoothctl scan on`.
This is seen on Jammy with bluez 5.64-0ubuntu1
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-03-06 (242 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
NonfreeKernelModules: zfs
Package: bluez 5.68-0ubuntu1
PackageArchitecture: amd64
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/usr/bin/zsh
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Tags: mantic wayland-session
Uname: Linux 6.5.0-10-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-10-31 (3 days ago)
UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sbuild
sudo
_MarkForUpload: True
dmi.bios.date: 07/18/2023
dmi.bios.release: 1.58
dmi.bios.vendor: LENOVO
dmi.bios.version: N2HET75W (1.58 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20QDUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.25
dmi.modalias:
dmi:bvnLENOVO:bvrN2HET75W(1.58):bd07/18/2023:br1.58:efr1.25:svnLENOVO:pn20QDUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDUS:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QD_BU_Think_FM_ThinkPadX1Carbon7th:
dmi.product.family: ThinkPad X1 Carbon 7th
dmi.product.name: 20QDUS
dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
dmi.product.version: ThinkPad X1 Carbon 7th
dmi.sys.vendor: LENOVO
hciconfig:
hci0:Type: Primary Bus: USB
BD Address: D0:AB:D5:BB:40:FD ACL MTU: 1021:4 SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY
RX bytes:21473 acl:0 sco:0 events:2871 errors:0
TX bytes:692880 acl:0 sco:0 commands:2838 errors:0
mtime.conffile..etc.bluetooth.main.conf: 2023-08-16T12:28:27.725767
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2040657/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2040657] ProcCpuinfoMinimal.txt
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/2040657/+attachment/5715730/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2040657
Title:
bluez does not detect Logitech Pebble M350, no option to connect
Status in bluez package in Ubuntu:
Incomplete
Bug description:
I lost the proprietary USB dongle and decided I wanted to try
bluetooth with this particular mouse. I am able to connect with
bluetooth on Windows 11, but the device doesn't even show up in
`bluetoothctl scan on`.
This is seen on Jammy with bluez 5.64-0ubuntu1
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-03-06 (242 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
NonfreeKernelModules: zfs
Package: bluez 5.68-0ubuntu1
PackageArchitecture: amd64
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/usr/bin/zsh
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Tags: mantic wayland-session
Uname: Linux 6.5.0-10-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-10-31 (3 days ago)
UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sbuild
sudo
_MarkForUpload: True
dmi.bios.date: 07/18/2023
dmi.bios.release: 1.58
dmi.bios.vendor: LENOVO
dmi.bios.version: N2HET75W (1.58 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20QDUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.25
dmi.modalias:
dmi:bvnLENOVO:bvrN2HET75W(1.58):bd07/18/2023:br1.58:efr1.25:svnLENOVO:pn20QDUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDUS:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QD_BU_Think_FM_ThinkPadX1Carbon7th:
dmi.product.family: ThinkPad X1 Carbon 7th
dmi.product.name: 20QDUS
dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
dmi.product.version: ThinkPad X1 Carbon 7th
dmi.sys.vendor: LENOVO
hciconfig:
hci0:Type: Primary Bus: USB
BD Address: D0:AB:D5:BB:40:FD ACL MTU: 1021:4 SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY
RX bytes:21473 acl:0 sco:0 events:2871 errors:0
TX bytes:692880 acl:0 sco:0 commands:2838 errors:0
mtime.conffile..etc.bluetooth.main.conf: 2023-08-16T12:28:27.725767
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2040657/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2040657] ProcCpuinfo.txt
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/2040657/+attachment/5715729/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2040657
Title:
bluez does not detect Logitech Pebble M350, no option to connect
Status in bluez package in Ubuntu:
Incomplete
Bug description:
I lost the proprietary USB dongle and decided I wanted to try
bluetooth with this particular mouse. I am able to connect with
bluetooth on Windows 11, but the device doesn't even show up in
`bluetoothctl scan on`.
This is seen on Jammy with bluez 5.64-0ubuntu1
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-03-06 (242 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
NonfreeKernelModules: zfs
Package: bluez 5.68-0ubuntu1
PackageArchitecture: amd64
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/usr/bin/zsh
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Tags: mantic wayland-session
Uname: Linux 6.5.0-10-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-10-31 (3 days ago)
UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sbuild
sudo
_MarkForUpload: True
dmi.bios.date: 07/18/2023
dmi.bios.release: 1.58
dmi.bios.vendor: LENOVO
dmi.bios.version: N2HET75W (1.58 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20QDUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.25
dmi.modalias:
dmi:bvnLENOVO:bvrN2HET75W(1.58):bd07/18/2023:br1.58:efr1.25:svnLENOVO:pn20QDUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDUS:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QD_BU_Think_FM_ThinkPadX1Carbon7th:
dmi.product.family: ThinkPad X1 Carbon 7th
dmi.product.name: 20QDUS
dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
dmi.product.version: ThinkPad X1 Carbon 7th
dmi.sys.vendor: LENOVO
hciconfig:
hci0:Type: Primary Bus: USB
BD Address: D0:AB:D5:BB:40:FD ACL MTU: 1021:4 SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY
RX bytes:21473 acl:0 sco:0 events:2871 errors:0
TX bytes:692880 acl:0 sco:0 commands:2838 errors:0
mtime.conffile..etc.bluetooth.main.conf: 2023-08-16T12:28:27.725767
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2040657/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2040657] ProcInterrupts.txt
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/2040657/+attachment/5715731/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2040657
Title:
bluez does not detect Logitech Pebble M350, no option to connect
Status in bluez package in Ubuntu:
Incomplete
Bug description:
I lost the proprietary USB dongle and decided I wanted to try
bluetooth with this particular mouse. I am able to connect with
bluetooth on Windows 11, but the device doesn't even show up in
`bluetoothctl scan on`.
This is seen on Jammy with bluez 5.64-0ubuntu1
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-03-06 (242 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
NonfreeKernelModules: zfs
Package: bluez 5.68-0ubuntu1
PackageArchitecture: amd64
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/usr/bin/zsh
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Tags: mantic wayland-session
Uname: Linux 6.5.0-10-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-10-31 (3 days ago)
UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sbuild
sudo
_MarkForUpload: True
dmi.bios.date: 07/18/2023
dmi.bios.release: 1.58
dmi.bios.vendor: LENOVO
dmi.bios.version: N2HET75W (1.58 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20QDUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.25
dmi.modalias:
dmi:bvnLENOVO:bvrN2HET75W(1.58):bd07/18/2023:br1.58:efr1.25:svnLENOVO:pn20QDUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDUS:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QD_BU_Think_FM_ThinkPadX1Carbon7th:
dmi.product.family: ThinkPad X1 Carbon 7th
dmi.product.name: 20QDUS
dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
dmi.product.version: ThinkPad X1 Carbon 7th
dmi.sys.vendor: LENOVO
hciconfig:
hci0:Type: Primary Bus: USB
BD Address: D0:AB:D5:BB:40:FD ACL MTU: 1021:4 SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY
RX bytes:21473 acl:0 sco:0 events:2871 errors:0
TX bytes:692880 acl:0 sco:0 commands:2838 errors:0
mtime.conffile..etc.bluetooth.main.conf: 2023-08-16T12:28:27.725767
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2040657/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2040657] Lsusb-v.txt
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/2040657/+attachment/5715728/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2040657
Title:
bluez does not detect Logitech Pebble M350, no option to connect
Status in bluez package in Ubuntu:
Incomplete
Bug description:
I lost the proprietary USB dongle and decided I wanted to try
bluetooth with this particular mouse. I am able to connect with
bluetooth on Windows 11, but the device doesn't even show up in
`bluetoothctl scan on`.
This is seen on Jammy with bluez 5.64-0ubuntu1
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-03-06 (242 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
NonfreeKernelModules: zfs
Package: bluez 5.68-0ubuntu1
PackageArchitecture: amd64
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/usr/bin/zsh
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Tags: mantic wayland-session
Uname: Linux 6.5.0-10-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-10-31 (3 days ago)
UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sbuild
sudo
_MarkForUpload: True
dmi.bios.date: 07/18/2023
dmi.bios.release: 1.58
dmi.bios.vendor: LENOVO
dmi.bios.version: N2HET75W (1.58 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20QDUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.25
dmi.modalias:
dmi:bvnLENOVO:bvrN2HET75W(1.58):bd07/18/2023:br1.58:efr1.25:svnLENOVO:pn20QDUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDUS:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QD_BU_Think_FM_ThinkPadX1Carbon7th:
dmi.product.family: ThinkPad X1 Carbon 7th
dmi.product.name: 20QDUS
dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
dmi.product.version: ThinkPad X1 Carbon 7th
dmi.sys.vendor: LENOVO
hciconfig:
hci0:Type: Primary Bus: USB
BD Address: D0:AB:D5:BB:40:FD ACL MTU: 1021:4 SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY
RX bytes:21473 acl:0 sco:0 events:2871 errors:0
TX bytes:692880 acl:0 sco:0 commands:2838 errors:0
mtime.conffile..etc.bluetooth.main.conf: 2023-08-16T12:28:27.725767
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2040657/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2040657] Lsusb.txt
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/2040657/+attachment/5715726/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2040657
Title:
bluez does not detect Logitech Pebble M350, no option to connect
Status in bluez package in Ubuntu:
Incomplete
Bug description:
I lost the proprietary USB dongle and decided I wanted to try
bluetooth with this particular mouse. I am able to connect with
bluetooth on Windows 11, but the device doesn't even show up in
`bluetoothctl scan on`.
This is seen on Jammy with bluez 5.64-0ubuntu1
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-03-06 (242 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
NonfreeKernelModules: zfs
Package: bluez 5.68-0ubuntu1
PackageArchitecture: amd64
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/usr/bin/zsh
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Tags: mantic wayland-session
Uname: Linux 6.5.0-10-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-10-31 (3 days ago)
UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sbuild
sudo
_MarkForUpload: True
dmi.bios.date: 07/18/2023
dmi.bios.release: 1.58
dmi.bios.vendor: LENOVO
dmi.bios.version: N2HET75W (1.58 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20QDUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.25
dmi.modalias:
dmi:bvnLENOVO:bvrN2HET75W(1.58):bd07/18/2023:br1.58:efr1.25:svnLENOVO:pn20QDUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDUS:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QD_BU_Think_FM_ThinkPadX1Carbon7th:
dmi.product.family: ThinkPad X1 Carbon 7th
dmi.product.name: 20QDUS
dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
dmi.product.version: ThinkPad X1 Carbon 7th
dmi.sys.vendor: LENOVO
hciconfig:
hci0:Type: Primary Bus: USB
BD Address: D0:AB:D5:BB:40:FD ACL MTU: 1021:4 SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY
RX bytes:21473 acl:0 sco:0 events:2871 errors:0
TX bytes:692880 acl:0 sco:0 commands:2838 errors:0
mtime.conffile..etc.bluetooth.main.conf: 2023-08-16T12:28:27.725767
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2040657/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2040657] Lsusb-t.txt
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/2040657/+attachment/5715727/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2040657
Title:
bluez does not detect Logitech Pebble M350, no option to connect
Status in bluez package in Ubuntu:
Incomplete
Bug description:
I lost the proprietary USB dongle and decided I wanted to try
bluetooth with this particular mouse. I am able to connect with
bluetooth on Windows 11, but the device doesn't even show up in
`bluetoothctl scan on`.
This is seen on Jammy with bluez 5.64-0ubuntu1
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-03-06 (242 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
NonfreeKernelModules: zfs
Package: bluez 5.68-0ubuntu1
PackageArchitecture: amd64
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/usr/bin/zsh
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Tags: mantic wayland-session
Uname: Linux 6.5.0-10-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-10-31 (3 days ago)
UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sbuild
sudo
_MarkForUpload: True
dmi.bios.date: 07/18/2023
dmi.bios.release: 1.58
dmi.bios.vendor: LENOVO
dmi.bios.version: N2HET75W (1.58 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20QDUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.25
dmi.modalias:
dmi:bvnLENOVO:bvrN2HET75W(1.58):bd07/18/2023:br1.58:efr1.25:svnLENOVO:pn20QDUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDUS:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QD_BU_Think_FM_ThinkPadX1Carbon7th:
dmi.product.family: ThinkPad X1 Carbon 7th
dmi.product.name: 20QDUS
dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
dmi.product.version: ThinkPad X1 Carbon 7th
dmi.sys.vendor: LENOVO
hciconfig:
hci0:Type: Primary Bus: USB
BD Address: D0:AB:D5:BB:40:FD ACL MTU: 1021:4 SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY
RX bytes:21473 acl:0 sco:0 events:2871 errors:0
TX bytes:692880 acl:0 sco:0 commands:2838 errors:0
mtime.conffile..etc.bluetooth.main.conf: 2023-08-16T12:28:27.725767
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2040657/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2040657] Lspci-vt.txt
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/2040657/+attachment/5715725/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2040657
Title:
bluez does not detect Logitech Pebble M350, no option to connect
Status in bluez package in Ubuntu:
Incomplete
Bug description:
I lost the proprietary USB dongle and decided I wanted to try
bluetooth with this particular mouse. I am able to connect with
bluetooth on Windows 11, but the device doesn't even show up in
`bluetoothctl scan on`.
This is seen on Jammy with bluez 5.64-0ubuntu1
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-03-06 (242 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
NonfreeKernelModules: zfs
Package: bluez 5.68-0ubuntu1
PackageArchitecture: amd64
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/usr/bin/zsh
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Tags: mantic wayland-session
Uname: Linux 6.5.0-10-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-10-31 (3 days ago)
UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sbuild
sudo
_MarkForUpload: True
dmi.bios.date: 07/18/2023
dmi.bios.release: 1.58
dmi.bios.vendor: LENOVO
dmi.bios.version: N2HET75W (1.58 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20QDUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.25
dmi.modalias:
dmi:bvnLENOVO:bvrN2HET75W(1.58):bd07/18/2023:br1.58:efr1.25:svnLENOVO:pn20QDUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDUS:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QD_BU_Think_FM_ThinkPadX1Carbon7th:
dmi.product.family: ThinkPad X1 Carbon 7th
dmi.product.name: 20QDUS
dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
dmi.product.version: ThinkPad X1 Carbon 7th
dmi.sys.vendor: LENOVO
hciconfig:
hci0:Type: Primary Bus: USB
BD Address: D0:AB:D5:BB:40:FD ACL MTU: 1021:4 SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY
RX bytes:21473 acl:0 sco:0 events:2871 errors:0
TX bytes:692880 acl:0 sco:0 commands:2838 errors:0
mtime.conffile..etc.bluetooth.main.conf: 2023-08-16T12:28:27.725767
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2040657/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2040657] Dependencies.txt
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/2040657/+attachment/5715723/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2040657
Title:
bluez does not detect Logitech Pebble M350, no option to connect
Status in bluez package in Ubuntu:
Incomplete
Bug description:
I lost the proprietary USB dongle and decided I wanted to try
bluetooth with this particular mouse. I am able to connect with
bluetooth on Windows 11, but the device doesn't even show up in
`bluetoothctl scan on`.
This is seen on Jammy with bluez 5.64-0ubuntu1
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-03-06 (242 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
NonfreeKernelModules: zfs
Package: bluez 5.68-0ubuntu1
PackageArchitecture: amd64
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/usr/bin/zsh
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Tags: mantic wayland-session
Uname: Linux 6.5.0-10-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-10-31 (3 days ago)
UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sbuild
sudo
_MarkForUpload: True
dmi.bios.date: 07/18/2023
dmi.bios.release: 1.58
dmi.bios.vendor: LENOVO
dmi.bios.version: N2HET75W (1.58 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20QDUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.25
dmi.modalias:
dmi:bvnLENOVO:bvrN2HET75W(1.58):bd07/18/2023:br1.58:efr1.25:svnLENOVO:pn20QDUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDUS:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QD_BU_Think_FM_ThinkPadX1Carbon7th:
dmi.product.family: ThinkPad X1 Carbon 7th
dmi.product.name: 20QDUS
dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
dmi.product.version: ThinkPad X1 Carbon 7th
dmi.sys.vendor: LENOVO
hciconfig:
hci0:Type: Primary Bus: USB
BD Address: D0:AB:D5:BB:40:FD ACL MTU: 1021:4 SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY
RX bytes:21473 acl:0 sco:0 events:2871 errors:0
TX bytes:692880 acl:0 sco:0 commands:2838 errors:0
mtime.conffile..etc.bluetooth.main.conf: 2023-08-16T12:28:27.725767
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2040657/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2040657] Re: bluez does not detect Logitech Pebble M350, no option to connect
apport information
** Tags added: apport-collected mantic wayland-session
** Description changed:
I lost the proprietary USB dongle and decided I wanted to try bluetooth
with this particular mouse. I am able to connect with bluetooth on
Windows 11, but the device doesn't even show up in `bluetoothctl scan
on`.
This is seen on Jammy with bluez 5.64-0ubuntu1
+ ---
+ ProblemType: Bug
+ ApportVersion: 2.27.0-0ubuntu5
+ Architecture: amd64
+ CasperMD5CheckResult: pass
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 23.10
+ InstallationDate: Installed on 2023-03-06 (242 days ago)
+ InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
+ InterestingModules: rfcomm bnep btusb bluetooth
+ MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
+ NonfreeKernelModules: zfs
+ Package: bluez 5.68-0ubuntu1
+ PackageArchitecture: amd64
+ ProcEnviron:
+ LANG=en_US.UTF-8
+ PATH=(custom, no user)
+ SHELL=/usr/bin/zsh
+ TERM=xterm-256color
+ XDG_RUNTIME_DIR=
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
+ Tags: mantic wayland-session
+ Uname: Linux 6.5.0-10-generic x86_64
+ UpgradeStatus: Upgraded to mantic on 2023-10-31 (3 days ago)
+ UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sbuild
sudo
+ _MarkForUpload: True
+ dmi.bios.date: 07/18/2023
+ dmi.bios.release: 1.58
+ dmi.bios.vendor: LENOVO
+ dmi.bios.version: N2HET75W (1.58 )
+ dmi.board.asset.tag: Not Available
+ dmi.board.name: 20QDUS
+ dmi.board.vendor: LENOVO
+ dmi.board.version: SDK0J40709 WIN
+ dmi.chassis.asset.tag: No Asset Information
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: LENOVO
+ dmi.chassis.version: None
+ dmi.ec.firmware.release: 1.25
+ dmi.modalias:
dmi:bvnLENOVO:bvrN2HET75W(1.58):bd07/18/2023:br1.58:efr1.25:svnLENOVO:pn20QDUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDUS:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QD_BU_Think_FM_ThinkPadX1Carbon7th:
+ dmi.product.family: ThinkPad X1 Carbon 7th
+ dmi.product.name: 20QDUS
+ dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
+ dmi.product.version: ThinkPad X1 Carbon 7th
+ dmi.sys.vendor: LENOVO
+ hciconfig:
+ hci0:Type: Primary Bus: USB
+ BD Address: D0:AB:D5:BB:40:FD ACL MTU: 1021:4 SCO MTU: 96:6
+ UP RUNNING PSCAN ISCAN INQUIRY
+ RX bytes:21473 acl:0 sco:0 events:2871 errors:0
+ TX bytes:692880 acl:0 sco:0 commands:2838 errors:0
+ mtime.conffile..etc.bluetooth.main.conf: 2023-08-16T12:28:27.725767
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/2040657/+attachment/5715722/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2040657
Title:
bluez does not detect Logitech Pebble M350, no option to connect
Status in bluez package in Ubuntu:
Incomplete
Bug description:
I lost the proprietary USB dongle and decided I wanted to try
bluetooth with this particular mouse. I am able to connect with
bluetooth on Windows 11, but the device doesn't even show up in
`bluetoothctl scan on`.
This is seen on Jammy with bluez 5.64-0ubuntu1
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-03-06 (242 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
NonfreeKernelModules: zfs
Package: bluez 5.68-0ubuntu1
PackageArchitecture: amd64
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/usr/bin/zsh
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Tags: mantic wayland-session
Uname: Linux 6.5.0-10-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-10-31 (3 days ago)
UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sbuild
sudo
_MarkForUpload: True
dmi.bios.date: 07/18/2023
dmi.bios.release: 1.58
dmi.bios.vendor: LENOVO
dmi.bios.version: N2HET75W (1.58 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20QDUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.25
dmi.modalias:
[Touch-packages] [Bug 2040657] Lspci.txt
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/2040657/+attachment/5715724/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2040657
Title:
bluez does not detect Logitech Pebble M350, no option to connect
Status in bluez package in Ubuntu:
Incomplete
Bug description:
I lost the proprietary USB dongle and decided I wanted to try
bluetooth with this particular mouse. I am able to connect with
bluetooth on Windows 11, but the device doesn't even show up in
`bluetoothctl scan on`.
This is seen on Jammy with bluez 5.64-0ubuntu1
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-03-06 (242 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
NonfreeKernelModules: zfs
Package: bluez 5.68-0ubuntu1
PackageArchitecture: amd64
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/usr/bin/zsh
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Tags: mantic wayland-session
Uname: Linux 6.5.0-10-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-10-31 (3 days ago)
UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sbuild
sudo
_MarkForUpload: True
dmi.bios.date: 07/18/2023
dmi.bios.release: 1.58
dmi.bios.vendor: LENOVO
dmi.bios.version: N2HET75W (1.58 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20QDUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.25
dmi.modalias:
dmi:bvnLENOVO:bvrN2HET75W(1.58):bd07/18/2023:br1.58:efr1.25:svnLENOVO:pn20QDUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDUS:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QD_BU_Think_FM_ThinkPadX1Carbon7th:
dmi.product.family: ThinkPad X1 Carbon 7th
dmi.product.name: 20QDUS
dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
dmi.product.version: ThinkPad X1 Carbon 7th
dmi.sys.vendor: LENOVO
hciconfig:
hci0:Type: Primary Bus: USB
BD Address: D0:AB:D5:BB:40:FD ACL MTU: 1021:4 SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY
RX bytes:21473 acl:0 sco:0 events:2871 errors:0
TX bytes:692880 acl:0 sco:0 commands:2838 errors:0
mtime.conffile..etc.bluetooth.main.conf: 2023-08-16T12:28:27.725767
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2040657/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2042587] Re: jammy's version breaks existing dhcp scripts with relay
Thanks for taking the time to report this bug Timo! Do you have steps for how you setup dnsmasq so it can be more easy to reproduce your issue? ** Changed in: dnsmasq (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/2042587 Title: jammy's version breaks existing dhcp scripts with relay Status in dnsmasq package in Ubuntu: Incomplete Bug description: When upgrading from focal to jammy, existing dnsmasq dhcp-scripts stopped working in an environment where a DHCP relay is in use. Instead of the expected client IP address, the script gets the _relay_ IP address as an argument. From dnsmasq documentation for --dhcp- script: > The arguments to the process are "add", "old" or "del", the MAC address of the host (or DUID for IPv6) , the IP address, and the hostname, if known. I believe the change has been inadverently made in upstream commit 527c3c7d0d3bb4bf5fad699f10cf0d1a45a54692 (https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=blobdiff;f=src/helper.c;h=02340a01c00031db0cc682c8a4a279cfc1db574e;hp=d81de9622e6d484a264496b2cd3638b4e15e9677;hb=527c3c7d0d3bb4bf5fad699f10cf0d1a45a54692;hpb=fcb4dcaf7cc8a86ac2533b933161b6455f75bf8f) as the commit message only speaks about inet_ntoa replacement and not the behavioral change it also introduces (previously the relay address was only set to the environment variable, now it effectively overrides the prevoiusly set client's IP address). dnsmasq 2.86-1.1ubuntu0.3 / Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/2042587/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2042680] Re: lsb_release shows incorrect Ubuntu version
** Package changed: lsb-release-minimal (Ubuntu) => base-files (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/2042680 Title: lsb_release shows incorrect Ubuntu version Status in base-files package in Ubuntu: New Bug description: Testing Ubuntu Noble Desktop for Raspberry PI daily ISO dated 03-11-2023 After installing and rebooting running lsb_release -a shows version 23.10 not 24.04 ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: lsb-release 12.0-2 ProcVersionSignature: Ubuntu 6.5.0-1006.8-raspi 6.5.3 Uname: Linux 6.5.0-1006-raspi aarch64 ApportVersion: 2.27.0-0ubuntu5 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Nov 3 16:24:14 2023 Dependencies: PackageArchitecture: all ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: lsb-release-minimal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2042680/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2042680] [NEW] lsb_release shows incorrect Ubuntu version
You have been subscribed to a public bug: Testing Ubuntu Noble Desktop for Raspberry PI daily ISO dated 03-11-2023 After installing and rebooting running lsb_release -a shows version 23.10 not 24.04 ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: lsb-release 12.0-2 ProcVersionSignature: Ubuntu 6.5.0-1006.8-raspi 6.5.3 Uname: Linux 6.5.0-1006-raspi aarch64 ApportVersion: 2.27.0-0ubuntu5 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Nov 3 16:24:14 2023 Dependencies: PackageArchitecture: all ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: lsb-release-minimal UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: base-files (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 iso-testing mantic wayland-session -- lsb_release shows incorrect Ubuntu version https://bugs.launchpad.net/bugs/2042680 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2025339] Re: FDE image fails to run e2fsck
Also, given that this is the second time this kind of thing has happened, perhaps it is appropriate to add a dep8 test to ensure that the compatibility "level" of the default has not regressed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/2025339 Title: FDE image fails to run e2fsck Status in e2fsprogs package in Ubuntu: Fix Released Status in e2fsprogs source package in Lunar: In Progress Status in e2fsprogs package in Debian: Unknown Bug description: After installation of the FDE image, the system fails to boot due to e2fsck failing with: Jun 21 12:48:19 ubuntu systemd-fsck[268]: /dev/vda2 has unsupported feature(s): FEATURE_C12 this means that Jammy fsck fails against mantic created ext4 which is not great Seems this is orphan_file feature / orphan_present Also need to check if grub2 supports this as it is RO_INCOMPAT feature. [Fix] This SRU is disabling 2 features (orphan_file and metadata_csum_seed) from ext4 to generate filesystems compatible with older series. Fixes come from debian (fixing #1031622, #1030939). This is only disabling the feature by default. One can still generate a filesystem with this feature by explicitly listing them when invoking mkfs.ext4. [Impact] See LP: #2028564. Generating a filesystem on lunar with e2fsprogs will use the orphan_file feature. This will prevent a jammy (or older) based OS from modifying this filesystem (in particular resize it at first boot). [ Test Plan ] On lunar, generate a filesystem and check the orphan_file feature is enabled: $ dd if=/dev/zero of=test.img bs=100M count=1 $ mkfs.ext4 test.img $ # Then check the orphan_file feature is enabled $ dumpe2fs test.img | grep orphan Move this .img file to a jammy based machine, and try using resize2fs on it: $ resize2fs -d -f -M test.img resize2fs 1.46.5 (30-Dec-2021) resize2fs: Filesystem has unsupported feature(s) (test.img) [Where problems could occur] Some users on Lunar may currently rely on this feature to be enabled by default. This can still be enabled explicitly when calling mkfs.ext4 but the default behavior will be changed. The orphan_file feature aims at improving performances when dealing with deleted files or directories. So if we disable this by default, I think it should only impact performances of generated filesystems and probably not break anything else. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/2025339/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2025339] Re: FDE image fails to run e2fsck
(in the development release) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/2025339 Title: FDE image fails to run e2fsck Status in e2fsprogs package in Ubuntu: Fix Released Status in e2fsprogs source package in Lunar: In Progress Status in e2fsprogs package in Debian: Unknown Bug description: After installation of the FDE image, the system fails to boot due to e2fsck failing with: Jun 21 12:48:19 ubuntu systemd-fsck[268]: /dev/vda2 has unsupported feature(s): FEATURE_C12 this means that Jammy fsck fails against mantic created ext4 which is not great Seems this is orphan_file feature / orphan_present Also need to check if grub2 supports this as it is RO_INCOMPAT feature. [Fix] This SRU is disabling 2 features (orphan_file and metadata_csum_seed) from ext4 to generate filesystems compatible with older series. Fixes come from debian (fixing #1031622, #1030939). This is only disabling the feature by default. One can still generate a filesystem with this feature by explicitly listing them when invoking mkfs.ext4. [Impact] See LP: #2028564. Generating a filesystem on lunar with e2fsprogs will use the orphan_file feature. This will prevent a jammy (or older) based OS from modifying this filesystem (in particular resize it at first boot). [ Test Plan ] On lunar, generate a filesystem and check the orphan_file feature is enabled: $ dd if=/dev/zero of=test.img bs=100M count=1 $ mkfs.ext4 test.img $ # Then check the orphan_file feature is enabled $ dumpe2fs test.img | grep orphan Move this .img file to a jammy based machine, and try using resize2fs on it: $ resize2fs -d -f -M test.img resize2fs 1.46.5 (30-Dec-2021) resize2fs: Filesystem has unsupported feature(s) (test.img) [Where problems could occur] Some users on Lunar may currently rely on this feature to be enabled by default. This can still be enabled explicitly when calling mkfs.ext4 but the default behavior will be changed. The orphan_file feature aims at improving performances when dealing with deleted files or directories. So if we disable this by default, I think it should only impact performances of generated filesystems and probably not break anything else. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/2025339/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2025339] Re: FDE image fails to run e2fsck
> So if we disable this by default, I think it should only impact performances of generated filesystems and probably not break anything else. This sounds like it could be insignificant, or a major performance regression in some use cases. It's not clear which. Presumably orphan_file was introduced for a practical performance reason. Please provide a proper analysis of the risk of performance regression here, and a documented reason why this cannot simply be worked around by adjusting how mke2fs is called (or by adjusting its configuration) in the use cases which require it, before proposing this fix for SRU. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/2025339 Title: FDE image fails to run e2fsck Status in e2fsprogs package in Ubuntu: Fix Released Status in e2fsprogs source package in Lunar: In Progress Status in e2fsprogs package in Debian: Unknown Bug description: After installation of the FDE image, the system fails to boot due to e2fsck failing with: Jun 21 12:48:19 ubuntu systemd-fsck[268]: /dev/vda2 has unsupported feature(s): FEATURE_C12 this means that Jammy fsck fails against mantic created ext4 which is not great Seems this is orphan_file feature / orphan_present Also need to check if grub2 supports this as it is RO_INCOMPAT feature. [Fix] This SRU is disabling 2 features (orphan_file and metadata_csum_seed) from ext4 to generate filesystems compatible with older series. Fixes come from debian (fixing #1031622, #1030939). This is only disabling the feature by default. One can still generate a filesystem with this feature by explicitly listing them when invoking mkfs.ext4. [Impact] See LP: #2028564. Generating a filesystem on lunar with e2fsprogs will use the orphan_file feature. This will prevent a jammy (or older) based OS from modifying this filesystem (in particular resize it at first boot). [ Test Plan ] On lunar, generate a filesystem and check the orphan_file feature is enabled: $ dd if=/dev/zero of=test.img bs=100M count=1 $ mkfs.ext4 test.img $ # Then check the orphan_file feature is enabled $ dumpe2fs test.img | grep orphan Move this .img file to a jammy based machine, and try using resize2fs on it: $ resize2fs -d -f -M test.img resize2fs 1.46.5 (30-Dec-2021) resize2fs: Filesystem has unsupported feature(s) (test.img) [Where problems could occur] Some users on Lunar may currently rely on this feature to be enabled by default. This can still be enabled explicitly when calling mkfs.ext4 but the default behavior will be changed. The orphan_file feature aims at improving performances when dealing with deleted files or directories. So if we disable this by default, I think it should only impact performances of generated filesystems and probably not break anything else. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/2025339/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2002043] Re: Python extension modules get built using wrong compiler flags with python2
I just want to check if there are any updates with this bug?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python2.7 in Ubuntu.
https://bugs.launchpad.net/bugs/2002043
Title:
Python extension modules get built using wrong compiler flags with
python2
Status in python2.7 package in Ubuntu:
In Progress
Status in python2.7 source package in Bionic:
Won't Fix
Status in python2.7 source package in Focal:
Won't Fix
Status in python2.7 source package in Jammy:
Won't Fix
Status in python2.7 source package in Kinetic:
Won't Fix
Status in python2.7 source package in Lunar:
Won't Fix
Status in python2.7 source package in Mantic:
Won't Fix
Bug description:
Compiling a Python extension using Python2 (Python 2.7.18) is making
use of wrong compiler flags, hence dropping required optimizations
when required. This is happening only when python2 is installed from
Ubuntu's repositories. By default, Python's distutils module uses
compiler and linker flags used to compile Python itself to be used to
compile extensions.
Steps to reproduce:
1) On Ubuntu 20.04, install python2 using apt package manager.
2) After successful installation, verify the CFLAGS variable from sysconfig
module. On my machine, the output is
Python 2.7.18 (default, Jul 1 2022, 12:27:04)
[GCC 9.4.0] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import sysconfig
>>> sysconfig.get_config_var('CFLAGS')
'-fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes
-Wdate-time -D_FORTIFY_SOURCE=2 -g
-fdebug-prefix-map=/build/python2.7-vvQ8AI/python2.7-2.7.18=.
-fstack-protector-strong -Wformat -Werror=format-security '
3) Build a test extension module using python2 and verify the compilation
flags.
python2 setup.py build_ext --inplace
Output from below command is not matching with our expected above CFLAGS.
aarch64-linux-gnu-gcc -pthread -fno-strict-aliasing -Wdate-time
-D_FORTIFY_SOURCE=2 -g
-fdebug-prefix-map=/build/python2.7-vvQ8AI/python2.7-2.7.18=.
-fstack-protector-strong -Wformat -Werror=format-security -fPIC
-I/usr/include/python2.7 -c testmodule.c -o
build/temp.linux-aarch64-2.7/testmodule.o
On further investigation, it looks like Ubuntu's specific patch applied on
libpython2.7-stdlib package is altering the original upstream implementation of
distutils/sysconfig.py code.
Package - https://packages.ubuntu.com/focal/libpython2.7-stdlib
Patch -
http://archive.ubuntu.com/ubuntu/pool/universe/p/python2.7/python2.7_2.7.18-1~20.04.3.diff.gz
Below is the code block which is causing the issue, where the presence of
configure_cflags is modifying cflags. This code is result of ubuntu's patch and
doesn't come directly from upstream python implementation.
File - /usr/lib/python2.7/distutils/sysconfig.py
Part of code block:
elif configure_cflags:
cflags = ' '.join(str(x) for x in (basecflags, configure_cflags,
extra_cflags) if x)
ldshared = ldshared + ' ' + configure_cflags
I don't see problem on Python3 though we have extra code added from patch
there as well. Patch used on python3, is not modifying the cflags completely
and instead appending new flags to cflags.
On python3 (tested on Ubuntu 20.04)
File - /usr/lib/python3.8/distutils/sysconfig.py
Part of code block which doesn't alter cflags completely
elif configure_cflags:
cflags = cflags + ' ' + configure_cflags
ldshared = ldshared + ' ' + configure_cflags
Request to update the python2 patch to behave similar to what is been done on
python3.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/2002043/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037281] Re: Shutdown when triggering daemon-reload eary in boot
Just adding a comment on how to reproduce the bug, because I have lost a day trying to figure it out again. This fails only when not using secure boot because the device mapper state is kept from initrd to main boot. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2037281 Title: Shutdown when triggering daemon-reload eary in boot Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: New Status in systemd source package in Jammy: New Bug description: In Ubuntu Core 20, and Ubuntu Core 22, we are encountering an issue where if a service, started earlier than devices are processed by udev, does `systemctl daemon-reload`, the system shuts down. This is due to devices for mounted filesystem temporarily taken dead, which pulls most units down. This was fixed by upstream in https://github.com/systemd/systemd/pull/23218. But this was not backported to the versions used by Ubuntu packages for focal and jammy. The needed commit from that PR is the one with message `core/device: ignore DEVICE_FOUND_UDEV bit on switching root`. This patch applies to 245.4-4ubuntu3.22 (focal) without rebasing needed. And I suppose it does also for jammy. I have manually tested the fix with Ubuntu Core 20, and this fixes our issue. We would like this patch to be backported to focal-updates and jammy- updates. Thank you in advance. [ Impact ] If a user adds a service that calls `systemctl daemon-reload`, and if this service is started before systemd-udevd. And if the initrd is systemd (the case of Ubuntu Core), then most service will be stopped or cancel, and the machine will mostly shutdown everything and hang. The fix has been backported down to 250 upstream. It is already on kinetic and later. The fix only affects systems where systemd is used in initrd. [ Test Plan ] On Ubuntu Core 20 (with Core 22 kernel) or on Ubuntu Core 22. Or on any system that uses systemd in initrd. Add a systemd service that calls `systemctl daemon-reload`. The service should have `DefaultDependencies=no` in order to start as soon as possible and be enabled. Restart the machine. If fix is not applied, after the service is started, most of units with be shutdown, and the system will be unusable. [ Where problems could occur ] This should affect systems with systemd in initrd. There are risks on systems that have an udev rule in initrd not present in the main system. There are risks on systems that use db_persist in initrd where the device can potentially get dead state. Though this does not seem to happen on Ubuntu Core 22, even though we use db_persist for dev mapper devices. Regression is upstream bug #23429. Commits named "core/device: device_coldplug(): don't set DEVICE_DEAD" and "core/device: do not downgrade device state if it is already enumerated" could be applied as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2037281/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2025339] Re: FDE image fails to run e2fsck
** No longer affects: e2fsprogs (Ubuntu Jammy) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/2025339 Title: FDE image fails to run e2fsck Status in e2fsprogs package in Ubuntu: Fix Released Status in e2fsprogs source package in Lunar: In Progress Status in e2fsprogs package in Debian: Unknown Bug description: After installation of the FDE image, the system fails to boot due to e2fsck failing with: Jun 21 12:48:19 ubuntu systemd-fsck[268]: /dev/vda2 has unsupported feature(s): FEATURE_C12 this means that Jammy fsck fails against mantic created ext4 which is not great Seems this is orphan_file feature / orphan_present Also need to check if grub2 supports this as it is RO_INCOMPAT feature. [Fix] This SRU is disabling 2 features (orphan_file and metadata_csum_seed) from ext4 to generate filesystems compatible with older series. Fixes come from debian (fixing #1031622, #1030939). This is only disabling the feature by default. One can still generate a filesystem with this feature by explicitly listing them when invoking mkfs.ext4. [Impact] See LP: #2028564. Generating a filesystem on lunar with e2fsprogs will use the orphan_file feature. This will prevent a jammy (or older) based OS from modifying this filesystem (in particular resize it at first boot). [ Test Plan ] On lunar, generate a filesystem and check the orphan_file feature is enabled: $ dd if=/dev/zero of=test.img bs=100M count=1 $ mkfs.ext4 test.img $ # Then check the orphan_file feature is enabled $ dumpe2fs test.img | grep orphan Move this .img file to a jammy based machine, and try using resize2fs on it: $ resize2fs -d -f -M test.img resize2fs 1.46.5 (30-Dec-2021) resize2fs: Filesystem has unsupported feature(s) (test.img) [Where problems could occur] Some users on Lunar may currently rely on this feature to be enabled by default. This can still be enabled explicitly when calling mkfs.ext4 but the default behavior will be changed. The orphan_file feature aims at improving performances when dealing with deleted files or directories. So if we disable this by default, I think it should only impact performances of generated filesystems and probably not break anything else. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/2025339/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2042054] Re: 22.04.3, zen 4 7840, screen turn white exception
From the upstream bug this is caused by PSR, so it's not a mesa issue. ** No longer affects: mesa (Ubuntu) ** No longer affects: mesa (Ubuntu Jammy) ** No longer affects: mesa (Ubuntu Lunar) ** No longer affects: mesa (Ubuntu Mantic) ** No longer affects: mesa (Ubuntu Noble) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2042054 Title: 22.04.3, zen 4 7840, screen turn white exception Status in Linux: New Status in linux package in Ubuntu: New Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: New Status in linux-oem-6.5 source package in Jammy: New Status in linux source package in Lunar: New Status in linux-oem-6.5 source package in Lunar: Invalid Status in linux source package in Mantic: New Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: New Status in linux-oem-6.5 source package in Noble: Invalid Bug description: My screen suddenly turned completely white, then only the bottom half was white, but I can still operate the application window. When moving the application window, the bottom half of the screen turns the Ubuntu theme color. Only lock and unlock the screen or turn off the screen can fix the situation. There are some photo about the exception attached. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-1006.6-oem 6.5.3 Uname: Linux 6.5.0-1006-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Oct 31 12:26:24 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15bf] (rev c7) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3818] InstallationDate: Installed on 2023-10-30 (1 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: LENOVO 83AM ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-1006-oem root=UUID=ef93c72f-6025-43c4-820e-64cc8b1a9028 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/08/2023 dmi.bios.release: 1.27 dmi.bios.vendor: LENOVO dmi.bios.version: MKCN27WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76479 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: XiaoXinPro 14 APH8 dmi.ec.firmware.release: 1.27 dmi.modalias: dmi:bvnLENOVO:bvrMKCN27WW:bd09/08/2023:br1.27:efr1.27:svnLENOVO:pn83AM:pvrXiaoXinPro14APH8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76479WIN:cvnLENOVO:ct10:cvrXiaoXinPro14APH8:skuLENOVO_MT_83AM_BU_idea_FM_XiaoXinPro14APH8: dmi.product.family: XiaoXinPro 14 APH8 dmi.product.name: 83AM dmi.product.sku: LENOVO_MT_83AM_BU_idea_FM_XiaoXinPro 14 APH8 dmi.product.version: XiaoXinPro 14 APH8 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2042054/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2040051] Re: systemd-networkd-wait-online terminates with "Could not create manager: Invalid argument"
root@h12345678:~ # cat /proc/cmdline quiet root@h12345678:~ # uname -a Linux h12345678.my-hoster.tld 4.15.0 #1 SMP Wed Jul 12 12:00:44 MSK 2023 x86_64 x86_64 x86_64 GNU/Linux Please note that my hoster uses OpenVZ with a shared kernel across guest OSes. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2040051 Title: systemd-networkd-wait-online terminates with "Could not create manager: Invalid argument" Status in systemd package in Ubuntu: New Bug description: # lsb_release -rd No LSB modules are available. Description:Ubuntu 23.10 Release:23.10 # aptitude show systemd Package: systemd Version: 253.5-1ubuntu6 State: installed systemd-networkd-wait-online terminates with "Could not create manager: Invalid argument". This lets the corresponding service (systemd-networkd-wait- online.service) fail as well. The error also appears when one directly invokes /lib/systemd/systemd-networkd-wait-online from a shell. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2040051/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2039328] Re: Update ubuntu-meta with promotions done between last ubuntu-meta build & release
** Changed in: ubuntu-meta (Ubuntu Noble) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2039328 Title: Update ubuntu-meta with promotions done between last ubuntu-meta build & release Status in ubuntu-meta package in Ubuntu: Fix Committed Status in ubuntu-meta source package in Mantic: Confirmed Status in ubuntu-meta source package in Noble: Fix Committed Bug description: [ Impact ] * ubuntu-seeds were changed since last meta update * to ensure correct upgrades; regenerate ubuntu-meta with contents / changes done before release [ Test Plan ] * Check that arm64 upgrades of ubuntu-desktop-minimal from lunar to mantic install newly recommended packages. [ Where problems could occur ] * This is automatically generated change based on ubuntu-seeds commit [1]. * Theoretically, regressions would occur if new desktop-minimal-recommends dependencies on arm64 (flash-kernel, protection-domain-mapper, qrtr-tools): - have issues on install during release-upgrade; - have issues on regular system usage (after installed). [ Other Info ] * ubuntu-meta was not uploaded during final freeze, to prevent rebuilding all images as changes affect arm64 only, which is a brand new release image * protection-domain-mapper [2] and qrtr [3] moved from universe to main in Mantic. * flash-kernel is/was already in main. [1] https://git.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/+git/ubuntu/commit/?id=afe820cd49514896e96d02303298ed873d8d7f8a [2] https://launchpad.net/ubuntu/+source/protection-domain-mapper/1.0-4ubuntu2/+publishinghistory [3] https://launchpad.net/ubuntu/+source/qrtr/1.0-2ubuntu1/+publishinghistory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2039328/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2023322] Re: GTK internal browser does not render with Nvidia drivers
Spinning forever sounds like a different problem from failing to render, perhaps? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/2023322 Title: GTK internal browser does not render with Nvidia drivers Status in Webkit: Confirmed Status in gnome-control-center package in Ubuntu: Invalid Status in gnome-online-accounts package in Ubuntu: Invalid Status in webkit2gtk package in Ubuntu: Fix Released Status in yelp package in Ubuntu: Invalid Status in webkit2gtk package in Debian: Fix Released Bug description: When I go into Settings > Online Accounts > Google, I get to the prompt for email address, once in a while it stops accepting input there. But often I can get to the password screen. Once I do, I can't type anything or paste anything. This is a fresh install of Ubuntu 23.04 and I have installed all updates. Nothing in /var/crash Jun 08 11:15:59 CCW-HAL systemd[3523]: vte-spawn-8b4a59a3-a060-4bdd-92e6-285656bdb9a2.scope: Consumed 3.448s CPU time. Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:29 CCW-HAL systemd[3523]: Started app-gnome-org.gnome.Terminal-10924.scope - Application launched by gnome-shell. Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.167' (uid=1000 pid=10927 comm="/usr/bin/gnome-terminal.real" label="unconfined") Jun 08 11:16:29 CCW-HAL systemd[3523]: Starting gnome-terminal-server.service - GNOME Terminal Server... Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] Successfully activated service 'org.gnome.Terminal' Jun 08 11:16:29 CCW-HAL systemd[3523]: Started gnome-terminal-server.service - GNOME Terminal Server. Jun 08 11:16:29 CCW-HAL systemd[3523]: Started vte-spawn-9cee1911-372a-4bb4-8b57-694984e43990.scope - VTE child process 10955 launched by gnome-terminal-server process 10931. Jun 08 11:16:49 CCW-HAL gnome-control-c[8079]: Error showing account: Child process exited with code 1 Jun 08 11:16:53 CCW-HAL gnome-online-accounts-panel.desktop[9764]: GLib-GIO: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3)GLib-GIO: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’GLib: unsetenv() is not thread-safe and should not be used after threads are createdGLib-GIO: _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’GoaBackend: Loading all providers: GoaBackend: - googleGoaBackend: - owncloudGoaBackend: - windows_liveGoaBackend: - exchangeGoaBackend: - lastfmGoaBackend: - imap_smtpGoaBackend: - kerberosGoaBackend: activated kerberos providerGLib-GIO: _g_io_module_get_default: Found default implementation gnutls (GTlsBackendGnutls) for ‘gio-tls-backend’Failed to create account: Dialog was dismissed Jun 08 11:16:53 CCW-HAL xdg-desktop-por[3907]: Realtime error: Could not map pid: Could not determine pid namespace: Could not find instance-id in process's /.flatpak-info Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0) Jun 08 11:17:01 CCW-HAL CRON[11094]: (root) CMD (cd / && run-parts --report /etc/cron.hourly) Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session closed for user root Jun 08 11:17:06 CCW-HAL kernel: WebKitWebProces[11026]: segfault at 55bd22ad9adc ip 55bd22ad9adc sp 7ffd1f6adbe8 error 14 likely on CPU 2 (core 2, socket 0) Jun 08 11:17:06 CCW-HAL kernel: Code: Unable to access opcode bytes at 0x55bd22ad9ab2. Jun 08 11:17:36 CCW-HAL gnome-shell[3803]: Window manager warning: WM_TRANSIENT_FOR window 0x3a02767 for 0x3a02778 window override-redirect is an override-redirect window and this is not correct according to the standard, so we'll fallback to the first non-override-redirect window 0x3a006dc. Jun 08 11:17:42 CCW-HAL systemd[1]: Starting systemd-tmpfiles-clean.service - Cleanup of Temporary Directories... Jun 08 11:17:42 CCW-HAL systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully. Jun 08 11:17:42 CCW-HAL systemd[1]: Finished systemd-tmpfiles-clean.service - Cleanup of Temporary Directories. Jun 08 11:17:42 CCW-HAL systemd[1]: run-credentials-systemd\x2dtmpfiles\x2dclean.service.mount: Deactivated successfully. Jun 08 11:18:10 CCW-HAL gnome-shell[3803]: Window manager warning: WM_TRANSIENT_FOR window 0x3a029e2 for 0x3a029f0 window override-redirect is an
[Touch-packages] [Bug 2040108] Re: error "contains an invalid sample specification."
I use pipewire + pipewire-pulse where sound card is, on the client side i use pulseaudio -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/2040108 Title: error "contains an invalid sample specification." Status in pulseaudio package in Ubuntu: Incomplete Bug description: After upgrade network audio stop working. On the client side in log i see: "CA0132 Sound Core3D [Sound Blaster Recon3D / Z-Series' contains an invalid sample specification." Microphone sink work, but playback not. I tried as client ubuntu 23.04 and 23.10, so I suppose issue in zeroconf-publish Just specifying env PULSE_SERVER play sound fine. Also will be great if zeroconf-publish can filter what to export, at least disable microphone. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: pulseaudio-module-zeroconf 1:16.1+dfsg1-2ubuntu4 Uname: Linux 6.2.16-060216-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vova 1822 F wireplumber /dev/snd/controlC2: vova 1822 F wireplumber /dev/snd/controlC1: vova 1822 F wireplumber /dev/snd/seq:vova 1820 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sun Oct 22 17:04:30 2023 InstallationDate: Installed on 2023-04-01 (204 days ago) InstallationMedia: Kubuntu 23.04 "Lunar Lobster" - Daily amd64 (20230401) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to mantic on 2023-10-15 (7 days ago) dmi.bios.date: 08/09/2023 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: FEb dmi.board.asset.tag: Default string dmi.board.name: B550 AORUS ELITE V2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrFEb:bd08/09/2023:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB550AORUSELITEV2:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB550AORUSELITEV2:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: B550 MB dmi.product.name: B550 AORUS ELITE V2 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2040108/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2040108] Re: error "contains an invalid sample specification."
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Please also ensure that you include the release and flavour of Ubuntu that you are using. Thank you! ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/2040108 Title: error "contains an invalid sample specification." Status in pulseaudio package in Ubuntu: Incomplete Bug description: After upgrade network audio stop working. On the client side in log i see: "CA0132 Sound Core3D [Sound Blaster Recon3D / Z-Series' contains an invalid sample specification." Microphone sink work, but playback not. I tried as client ubuntu 23.04 and 23.10, so I suppose issue in zeroconf-publish Just specifying env PULSE_SERVER play sound fine. Also will be great if zeroconf-publish can filter what to export, at least disable microphone. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: pulseaudio-module-zeroconf 1:16.1+dfsg1-2ubuntu4 Uname: Linux 6.2.16-060216-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vova 1822 F wireplumber /dev/snd/controlC2: vova 1822 F wireplumber /dev/snd/controlC1: vova 1822 F wireplumber /dev/snd/seq:vova 1820 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sun Oct 22 17:04:30 2023 InstallationDate: Installed on 2023-04-01 (204 days ago) InstallationMedia: Kubuntu 23.04 "Lunar Lobster" - Daily amd64 (20230401) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to mantic on 2023-10-15 (7 days ago) dmi.bios.date: 08/09/2023 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: FEb dmi.board.asset.tag: Default string dmi.board.name: B550 AORUS ELITE V2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrFEb:bd08/09/2023:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB550AORUSELITEV2:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB550AORUSELITEV2:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: B550 MB dmi.product.name: B550 AORUS ELITE V2 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2040108/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2040108] Re: error "contains an invalid sample specification."
Do you use pulseaudio or pipewire? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/2040108 Title: error "contains an invalid sample specification." Status in pulseaudio package in Ubuntu: Incomplete Bug description: After upgrade network audio stop working. On the client side in log i see: "CA0132 Sound Core3D [Sound Blaster Recon3D / Z-Series' contains an invalid sample specification." Microphone sink work, but playback not. I tried as client ubuntu 23.04 and 23.10, so I suppose issue in zeroconf-publish Just specifying env PULSE_SERVER play sound fine. Also will be great if zeroconf-publish can filter what to export, at least disable microphone. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: pulseaudio-module-zeroconf 1:16.1+dfsg1-2ubuntu4 Uname: Linux 6.2.16-060216-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vova 1822 F wireplumber /dev/snd/controlC2: vova 1822 F wireplumber /dev/snd/controlC1: vova 1822 F wireplumber /dev/snd/seq:vova 1820 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sun Oct 22 17:04:30 2023 InstallationDate: Installed on 2023-04-01 (204 days ago) InstallationMedia: Kubuntu 23.04 "Lunar Lobster" - Daily amd64 (20230401) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to mantic on 2023-10-15 (7 days ago) dmi.bios.date: 08/09/2023 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: FEb dmi.board.asset.tag: Default string dmi.board.name: B550 AORUS ELITE V2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrFEb:bd08/09/2023:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB550AORUSELITEV2:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB550AORUSELITEV2:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: B550 MB dmi.product.name: B550 AORUS ELITE V2 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2040108/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
