[Desktop-packages] [Bug 2046116] [NEW] bluetooth device connected but not recognised as output device
Public bug reported: bluetooth device connected but not recognised as output device ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1.1 ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Dec 11 15:28:00 2023 InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 81EK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-37-generic root=UUID=6f698382-a806-46af-9a4b-472e96795c6f ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2018 dmi.bios.release: 1.28 dmi.bios.vendor: LENOVO dmi.bios.version: 7QCN28WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 530-14IKB dmi.ec.firmware.release: 1.28 dmi.modalias: dmi:bvnLENOVO:bvr7QCN28WW:bd08/02/2018:br1.28:efr1.28:svnLENOVO:pn81EK:pvrLenovoYOGA530-14IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA530-14IKB:skuLENOVO_MT_81EK_BU_idea_FM_YOGA530-14IKB: dmi.product.family: YOGA 530-14IKB dmi.product.name: 81EK dmi.product.sku: LENOVO_MT_81EK_BU_idea_FM_YOGA 530-14IKB dmi.product.version: Lenovo YOGA 530-14IKB dmi.sys.vendor: LENOVO hciconfig: hci0: Type: Primary Bus: USB BD Address: 0C:54:15:91:FA:4F ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:83770 acl:295 sco:0 events:4208 errors:0 TX bytes:879445 acl:1667 sco:0 commands:1184 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2046116 Title: bluetooth device connected but not recognised as output device Status in bluez package in Ubuntu: New Bug description: bluetooth device connected but not recognised as output device ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1.1 ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Dec 11 15:28:00 2023 InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 81EK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-37-generic root=UUID=6f698382-a806-46af-9a4b-472e96795c6f ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2018 dmi.bios.release: 1.28 dmi.bios.vendor: LENOVO dmi.bios.version: 7QCN28WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 530-14IKB dmi.ec.firmware.release: 1.28 dmi.modalias: dmi:bvnLENOVO:bvr7QCN28WW:bd08/02/2018:br1.28:efr1.28:svnLENOVO:pn81EK:pvrLenovoYOGA530-14IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA530-14IKB:skuLENOVO_MT_81EK_BU_idea_FM_YOGA530-14IKB: dmi.product.family: YOGA 530-14IKB dmi.product.name: 81EK dmi.product.sku: LENOVO_MT_81EK_BU_idea_FM_YOGA 530-14IKB dmi.product.version: Lenovo YOGA 530-14IKB dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 0C:54:15:91:FA:4F ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:83770 acl:295 sco:0 events:4208 errors:0 TX bytes:879445 acl:1667 sco:0 commands:1184 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2046116/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2035076] Re: Can't enter capital accented letters with Caps Lock on Wayland
> Jeremie, you also have to pass "-t mantic-proposed" in the apt command line. Ok, I've updated the packages to version 45.2 and now I can enter capital accented letters ÒÀÙÈÉÌ as expected. Thank you very much, great job! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2035076 Title: Can't enter capital accented letters with Caps Lock on Wayland Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Mantic: Fix Committed Status in mutter package in Fedora: Unknown Bug description: Impact -- Capital accented letters can't be entered using CAPS LOCK in the Wayland session Test Case - Open a terminal and install basic French support: sudo apt install language-pack-gnome-fr Open the Settings app. In the sidebar, click Keyboard Click +, choose French (France), then choose the French (AZERTY) keyboard Close the Settings app In the top right of the screen, click en and switch the keyboard layout to French (AZERTY) In the text editor, type é (this is the number 2 key on a US English keyboard). Now, press the Caps Lock key to enable Caps Lock. Press the same key. You should get É What Could Go Wrong --- This fix is included in mutter 45.2 so see the master bug for this upstream update: LP: #2043000 Original bug report --- Most programs don't recognize Italian accented capital letters. When "Caps Lock" is on àèìòù should be written as ÀÈÌÒÙ... but for some reasons they are not capitalized. I've noticed that everything works fine using the Live session which still uses X11 session. It looks there's no problem with programs that use xwayland like Gimp and MarkText. WORKAROUND === In "Settings -> Keyboard" it's possible to set a "compose key". For example I've selected the [Super left] key. If I want to compose È I press and immediately release each key: [Super left] + [E] + [Alt Gr] + ['] If you want É: [Super left] + [E] + ['] Do the same for the other vowels. === ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-text-editor 45~beta-1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 11 11:48:41 2023 InstallationDate: Installed on 2023-09-07 (4 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230906.3) ProcEnviron: LANG=it_IT.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-text-editor UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2035076/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2046084] Re: [Regression] HID gamepad stopped working in 5.68-0ubuntu1.1
Hello, I was able to find a similar issue on the bluez github here (https://github.com/bluez/bluez/issues/673) and after investigating a bit further, I am able to get things working on the current update from Canonical if I pair the device using bluetoothctl instead of with blueman. Instructions on how to do that are in this (https://github.com/bluez/bluez/issues/673#issuecomment-1849132576) comment. I think that this might be an issue with how blueman handles authentication with gamepad devices, not with how bluez does. ** Bug watch added: github.com/bluez/bluez/issues #673 https://github.com/bluez/bluez/issues/673 ** Package changed: bluez (Ubuntu) => blueman (Ubuntu) ** Summary changed: - [Regression] HID gamepad stopped working in 5.68-0ubuntu1.1 + [Regression] HID gamepad stopped working when paired with blueman on bluez 5.68-0ubuntu1.1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2046084 Title: [Regression] HID gamepad stopped working when paired with blueman on bluez 5.68-0ubuntu1.1 Status in blueman package in Ubuntu: New Bug description: Hello, I updated from 5.68-0ubuntu1 to 5.68-0ubuntu1.1 and my bluetooth gamepad (8bitdo Pro 2) stopped working. It no longer was detected by various emulator software or by jstest-gtk. It stopped showing up in /dev/input/ as well. Here are the logs that I get on connection with the broken (new) version: Dec 10 13:12:23 laptop bluetoothd[6317]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down Dec 10 13:12:43 laptop bluetoothd[6317]: profiles/input/device.c:ioctl_is_connected() Can't get HIDP connection info Dec 10 13:12:45 laptop bluetoothd[6317]: profiles/input/device.c:hidp_add_connection() Rejected connection from !bonded device E4:17:DE:AD:BE:EF Here are the logs that I get on connection with the old (working) version: Dec 10 13:37:17 laptop bluetoothd[7736]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down Dec 10 13:38:30 laptop bluetoothd[7736]: profiles/input/device.c:ioctl_is_connected() Can't get HIDP connection info I think that the indicator of issues (or at least a red herring) is the "Rejected connection from !bonded device" line in the broken output. I've redacted my MAC address obviously. I think that two packages are involved with this and I am not quite sure where exactly the bug lives. I think that both the "bluez" and "bluez-obexd" packages are involved. If I mix the versions between these two, I get various different behaviors: bluez-obexd 1.1 and bluez 1.1 = broken behavior bluez-obexd 1 and bluez 1.1 = broken behavior bluez-obexd 1 and bluez 1 = working behavior bluez-obexd 1.1 and bluez 1 = unable to connect bluetooth device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/blueman/+bug/2046084/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2039328] Re: Update ubuntu-meta with promotions done between last ubuntu-meta build & release
Verification done on mantic-proposed. On arm64 with ubuntu-desktop-minimal installed, running do-release-upgrade from lunar to mantic (with mantic-proposed enabled and pinning setup) does install `protection-domain-mapper` and `qrtr-tools` (`flash-kernel` already installed). Test Steps: --- Part 1) - launch aws arm64 instance with Ubuntu 22.04/jammy Part 2) - do-release-upgrade to 22.10/lunar - install ubuntu-desktop-minimal - enable lunar-proposed (converted to mantic-proposed in do-release-upgrade later) Part 3) - set pin priority for mantic-proposed/ubuntu-desktop-minimal - do-release-upgrade to 23.04/mantic Details: --- Start on Jammy: $ lsb_release -cs jammy $ dpkg --print-architecture arm64 $ uname -m aarch64 $ sudo apt update && sudo apt -y dist-upgrade && sudo reboot Upgrade to Lunar: $ sudo sed -i 's/^Prompt=.*/Prompt=normal/' -i /etc/update-manager/release-upgrades $ do-release-upgrade Checking for a new Ubuntu release = Welcome to Ubuntu 23.04 'Lunar Lobster' = ... $ lsb_release -cs No LSB modules are available. lunar Prepare for testing: $ sudo apt install -y ubuntu-desktop-minimal Test/Before: (only 1 out of 3 packages installed) $ dpkg -s flash-kernel protection-domain-mapper qrtr-tools | grep -e Package: -e Version: dpkg-query: package 'protection-domain-mapper' is not installed and no information is available dpkg-query: package 'qrtr-tools' is not installed and no information is available Use dpkg --info (= dpkg-deb --info) to examine archive files. Package: flash-kernel Version: 3.106ubuntu14 Enable -proposed: $ sudo add-apt-repository -yp proposed cat
[Desktop-packages] [Bug 2046084] [NEW] [Regression] HID gamepad stopped working in 5.68-0ubuntu1.1
Public bug reported: Hello, I updated from 5.68-0ubuntu1 to 5.68-0ubuntu1.1 and my bluetooth gamepad (8bitdo Pro 2) stopped working. It no longer was detected by various emulator software or by jstest-gtk. It stopped showing up in /dev/input/ as well. Here are the logs that I get on connection with the broken (new) version: Dec 10 13:12:23 laptop bluetoothd[6317]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down Dec 10 13:12:43 laptop bluetoothd[6317]: profiles/input/device.c:ioctl_is_connected() Can't get HIDP connection info Dec 10 13:12:45 laptop bluetoothd[6317]: profiles/input/device.c:hidp_add_connection() Rejected connection from !bonded device E4:17:DE:AD:BE:EF Here are the logs that I get on connection with the old (working) version: Dec 10 13:37:17 laptop bluetoothd[7736]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down Dec 10 13:38:30 laptop bluetoothd[7736]: profiles/input/device.c:ioctl_is_connected() Can't get HIDP connection info I think that the indicator of issues (or at least a red herring) is the "Rejected connection from !bonded device" line in the broken output. I've redacted my MAC address obviously. I think that two packages are involved with this and I am not quite sure where exactly the bug lives. I think that both the "bluez" and "bluez- obexd" packages are involved. If I mix the versions between these two, I get various different behaviors: bluez-obexd 1.1 and bluez 1.1 = broken behavior bluez-obexd 1 and bluez 1.1 = broken behavior bluez-obexd 1 and bluez 1 = working behavior bluez-obexd 1.1 and bluez 1 = unable to connect bluetooth device ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Description changed: Hello, I updated from 5.68-0ubuntu1 to 5.68-0ubuntu1.1 and my bluetooth gamepad (8bitdo Pro 2) stopped working. It no longer was detected by various emulator software or by jstest-gtk. It stopped showing up in /dev/input/ as well. Here are the logs that I get on connection with the broken (new) version: Dec 10 13:12:23 laptop bluetoothd[6317]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down Dec 10 13:12:43 laptop bluetoothd[6317]: profiles/input/device.c:ioctl_is_connected() Can't get HIDP connection info Dec 10 13:12:45 laptop bluetoothd[6317]: profiles/input/device.c:hidp_add_connection() Rejected connection from !bonded device E4:17:DE:AD:BE:EF - - Here are the logs that I get on connection with the old (working) version: + Here are the logs that I get on connection with the old (working) + version: Dec 10 13:37:17 laptop bluetoothd[7736]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down Dec 10 13:38:30 laptop bluetoothd[7736]: profiles/input/device.c:ioctl_is_connected() Can't get HIDP connection info - - I think that the indicator of issues (or at least a red herring) is the "Rejected connection from !bonded device" line in the broken output. I've redacted my MAC address obviously. + I think that the indicator of issues (or at least a red herring) is the + "Rejected connection from !bonded device" line in the broken output. + I've redacted my MAC address obviously. I think that two packages are involved with this and I am not quite sure where exactly the bug lives. I think that both the "bluez" and "bluez- obexd" packages are involved. If I mix the versions between these two, I get various different behaviors: bluez-obexd 1.1 and bluez 1.1 = broken behavior bluez-obexd 1 and bluez 1.1 = broken behavior bluez-obexd 1 and bluez 1 = working behavior - bluez-obex 1.1 and bluez 1 = unable to connect bluetooth device + bluez-obexd 1.1 and bluez 1 = unable to connect bluetooth device -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2046084 Title: [Regression] HID gamepad stopped working in 5.68-0ubuntu1.1 Status in bluez package in Ubuntu: New Bug description: Hello, I updated from 5.68-0ubuntu1 to 5.68-0ubuntu1.1 and my bluetooth gamepad (8bitdo Pro 2) stopped working. It no longer was detected by various emulator software or by jstest-gtk. It stopped showing up in /dev/input/ as well. Here are the logs that I get on connection with the broken (new) version: Dec 10 13:12:23 laptop bluetoothd[6317]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down Dec 10 13:12:43 laptop bluetoothd[6317]: profiles/input/device.c:ioctl_is_connected() Can't get HIDP connection info Dec 10 13:12:45 laptop bluetoothd[6317]: profiles/input/device.c:hidp_add_connection() Rejected connection from !bonded device E4:17:DE:AD:BE:EF Here are the logs that I get on connection with the old (working) version: Dec 10 13:37:17 laptop
[Desktop-packages] [Bug 2035076] Re: Can't enter capital accented letters with Caps Lock on Wayland
> I wanted to test the updated version of mutter so a couple of days ago I > enabled the `proposed` > repository, but I didn't receive any updates. Jeremie, you also have to pass "-t mantic-proposed" in the apt command line. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2035076 Title: Can't enter capital accented letters with Caps Lock on Wayland Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Mantic: Fix Committed Status in mutter package in Fedora: Unknown Bug description: Impact -- Capital accented letters can't be entered using CAPS LOCK in the Wayland session Test Case - Open a terminal and install basic French support: sudo apt install language-pack-gnome-fr Open the Settings app. In the sidebar, click Keyboard Click +, choose French (France), then choose the French (AZERTY) keyboard Close the Settings app In the top right of the screen, click en and switch the keyboard layout to French (AZERTY) In the text editor, type é (this is the number 2 key on a US English keyboard). Now, press the Caps Lock key to enable Caps Lock. Press the same key. You should get É What Could Go Wrong --- This fix is included in mutter 45.2 so see the master bug for this upstream update: LP: #2043000 Original bug report --- Most programs don't recognize Italian accented capital letters. When "Caps Lock" is on àèìòù should be written as ÀÈÌÒÙ... but for some reasons they are not capitalized. I've noticed that everything works fine using the Live session which still uses X11 session. It looks there's no problem with programs that use xwayland like Gimp and MarkText. WORKAROUND === In "Settings -> Keyboard" it's possible to set a "compose key". For example I've selected the [Super left] key. If I want to compose È I press and immediately release each key: [Super left] + [E] + [Alt Gr] + ['] If you want É: [Super left] + [E] + ['] Do the same for the other vowels. === ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-text-editor 45~beta-1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 11 11:48:41 2023 InstallationDate: Installed on 2023-09-07 (4 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230906.3) ProcEnviron: LANG=it_IT.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-text-editor UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2035076/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2046076] Re: cursor dissapears when I type
** Package changed: ubuntu => xorg (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2046076
Title:
cursor dissapears when I type
Status in xorg package in Ubuntu:
New
Bug description:
I'm using version Ubuntu 23.10 (gnome), and when I type in the default
terminal the cursor dissapears when I'm typing and I have the cursor
placed on the terminal window, this also happens when Im using
IntellyJ IDEA community
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..29.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.129.03 Thu Oct 19
18:56:32 UTC 2023
GCC version:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Dec 10 18:35:58 2023
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
NVIDIA Corporation TU116 [GeForce GTX 1660 SUPER] [10de:21c4] (rev a1)
(prog-if 00 [VGA controller])
Subsystem: ZOTAC International (MCO) Ltd. TU116 [GeForce GTX 1660 SUPER]
[19da:5527]
InstallationDate: Installed on 2023-12-10 (0 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-14-generic
root=UUID=655899b5-3bf1-4977-87ff-935d66071b9b ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/08/2020
dmi.bios.release: 5.14
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.40
dmi.board.asset.tag: 229200
dmi.board.name: A320M-A PRO (MS-7C51)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 1.0
dmi.chassis.asset.tag: 229200
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr1.40:bd12/08/2020:br5.14:svnMegaport:pn229200:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnA320M-APRO(MS-7C51):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:sku34:
dmi.product.family: 229200
dmi.product.name: 229200
dmi.product.sku: 34
dmi.product.version: 1.0
dmi.sys.vendor: Megaport
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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/2046076/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2046076] [NEW] cursor dissapears when I type
You have been subscribed to a public bug:
I'm using version Ubuntu 23.10 (gnome), and when I type in the default
terminal the cursor dissapears when I'm typing and I have the cursor
placed on the terminal window, this also happens when Im using IntellyJ
IDEA community
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..29.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.129.03 Thu Oct 19
18:56:32 UTC 2023
GCC version:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Dec 10 18:35:58 2023
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
NVIDIA Corporation TU116 [GeForce GTX 1660 SUPER] [10de:21c4] (rev a1)
(prog-if 00 [VGA controller])
Subsystem: ZOTAC International (MCO) Ltd. TU116 [GeForce GTX 1660 SUPER]
[19da:5527]
InstallationDate: Installed on 2023-12-10 (0 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-14-generic
root=UUID=655899b5-3bf1-4977-87ff-935d66071b9b ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/08/2020
dmi.bios.release: 5.14
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.40
dmi.board.asset.tag: 229200
dmi.board.name: A320M-A PRO (MS-7C51)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 1.0
dmi.chassis.asset.tag: 229200
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr1.40:bd12/08/2020:br5.14:svnMegaport:pn229200:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnA320M-APRO(MS-7C51):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:sku34:
dmi.product.family: 229200
dmi.product.name: 229200
dmi.product.sku: 34
dmi.product.version: 1.0
dmi.sys.vendor: Megaport
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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
--
cursor dissapears when I type
https://bugs.launchpad.net/bugs/2046076
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2046074] [NEW] The monitor screen appears black when connecting the PC through the sound bar to the monitor
Public bug reported: When I connect the laptop to the sound bar hdmi and the sound bar to the monitor, it tries to connect and Ubuntu detects it, but nothing appears on the screen. My HDMI works as it should, tested directly when it's connected to the monitor. I have tried on a laptop other than my computer with Windows to test if it is something of the sound bar and it works perfectly without problems. Don't really know what package should be interfering here. Mesa? Mutter? MSI laptop. CPU: AMD Ryzen 7 Series 4000 GPU: AMD Radeon RX 5600m RAM: 16GB NVM: 1TB. OS: Ubuntu 23.10 ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: mutter (not installed) Uname: Linux 6.6.5-060605-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Dec 10 17:39:27 2023 InstallationDate: Installed on 2023-10-13 (58 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011) ProcEnviron: LANG=es_ES.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2046074 Title: The monitor screen appears black when connecting the PC through the sound bar to the monitor Status in mutter package in Ubuntu: New Bug description: When I connect the laptop to the sound bar hdmi and the sound bar to the monitor, it tries to connect and Ubuntu detects it, but nothing appears on the screen. My HDMI works as it should, tested directly when it's connected to the monitor. I have tried on a laptop other than my computer with Windows to test if it is something of the sound bar and it works perfectly without problems. Don't really know what package should be interfering here. Mesa? Mutter? MSI laptop. CPU: AMD Ryzen 7 Series 4000 GPU: AMD Radeon RX 5600m RAM: 16GB NVM: 1TB. OS: Ubuntu 23.10 ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: mutter (not installed) Uname: Linux 6.6.5-060605-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Dec 10 17:39:27 2023 InstallationDate: Installed on 2023-10-13 (58 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011) ProcEnviron: LANG=es_ES.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2046074/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2043027] Re: Wacom Intuos S stop working after upgrading to Ubuntu 23.10
Hello again, I'm the original poster, and first things first: thanks to
everyone involved.
I apologize, as I'm not sure how to upgrade my Mutter to version 45.2.
I've only been fully immersed in Linux for the past year and have never
encountered this kind of issue before. I've already activated non-
published updates (mantic-proposed) and nothing happens.
If someone could provide me with guidance or related documentation, I'm
willing to perform any tests you may need.
I'm particularly into in this fix because I require it for my work with
Krita (I've reinstalled Ubuntu 22.04 these days to be able to work and
reupdated to 23.10 just to check this)
Thanks!
** Attachment added: "Captura desde 2023-12-10 17-08-38.png"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2043027/+attachment/5727957/+files/Captura%20desde%202023-12-10%2017-08-38.png
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2043027
Title:
Wacom Intuos S stop working after upgrading to Ubuntu 23.10
Status in mutter package in Ubuntu:
Fix Released
Status in mutter source package in Mantic:
Fix Committed
Bug description:
Impact
--
Clicking does not work correctly with Wacom tablets in the Ubuntu/GNOME X11
sessions
Test Case
-
One of the people affected by this issue will verify whether their Wacom
tablet is working noticably better with the upgraded Mutter packages
What Could Go Wrong
---
The fix for this issue is included in upstream's mutter 45.2 release so
please see bug 2043000 as the master bug for this upgrade
Original Bug Report
---
Tablet seems to work until I open Krita (as I could read on Internet, it may
be related with Qt Apps).
When Krita is open, mouse movement works ok with the tablet, but when
it comes to click action it doesn't work and any further action with
mouse is not captured (even outside Krita!).
To regain control of the mouse I have to Alt+Tab and then I can click
again.
Some details that may be handy:
- I've got two monitors
- Maybe Qt apps related
- My graphic card is nVidia GTX 1060 6Gb, driver used nvidia-driver-535
Thanks for your effort. I love Ubuntu!
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
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..06.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.129.03 Thu Oct 19
18:56:32 UTC 2023
GCC version:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Nov 8 17:20:34 2023
DistUpgraded: 2023-11-08 00:54:28,961 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
nvidia/535.129.03, 6.2.0-36-generic, x86_64: installed (WARNING! Diff
between built and installed module!) (WARNING! Diff between built and installed
module!) (WARNING! Diff between built and installed module!) (WARNING! Diff
between built and installed module!) (WARNING! Diff between built and installed
module!)
nvidia/535.129.03, 6.5.0-10-generic, x86_64: installed (WARNING! Diff
between built and installed module!) (WARNING! Diff between built and installed
module!) (WARNING! Diff between built and installed module!) (WARNING! Diff
between built and installed module!) (WARNING! Diff between built and installed
module!)
virtualbox/7.0.10, 6.2.0-36-generic, x86_64: installed
virtualbox/7.0.10, 6.5.0-10-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1)
(prog-if 00 [VGA controller])
Subsystem: ZOTAC International (MCO) Ltd. GP106 [GeForce GTX 1060 6GB]
[19da:1438]
InstallationDate: Installed on 2022-04-09 (578 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=es_ES.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic
root=UUID=9dd904a0-11bb-40fa-9fe8-2f10449a416c ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
[Desktop-packages] [Bug 2026611] Re: package nvidia-340 340.108-0ubuntu5.20.04.2 failed to install/upgrade: installed nvidia-340 package post-installation script subprocess returned error exit status
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/2026611 Title: package nvidia-340 340.108-0ubuntu5.20.04.2 failed to install/upgrade: installed nvidia-340 package post-installation script subprocess returned error exit status 10 Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Bug description: Processing triggers for libgdk-pixbuf2.0-0:amd64 (2.40.0+dfsg-3ubuntu0.4) ... Processing triggers for sgml-base (1.29.1) ... Errors were encountered while processing: nvidia-340 Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 340.108-0ubuntu5.20.04.2 ProcVersionSignature: Ubuntu 4.15.0-213.224-generic 4.15.18 Uname: Linux 4.15.0-213-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Jul 8 00:47:33 2023 ErrorMessage: installed nvidia-340 package post-installation script subprocess returned error exit status 10 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: nvidia-graphics-drivers-340 Title: package nvidia-340 340.108-0ubuntu5.20.04.2 failed to install/upgrade: installed nvidia-340 package post-installation script subprocess returned error exit status 10 UpgradeStatus: Upgraded to focal on 2023-07-08 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/2026611/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2046066] [NEW] package sgml-base 1.31 failed to install/upgrade: triggers looping, abandoned
Public bug reported: upgrading from 22.04 to 23.04 produced this error. ProblemType: Package DistroRelease: Ubuntu 23.04 Package: sgml-base 1.31 ProcVersionSignature: Ubuntu 6.2.0-37.38-generic 6.2.16 Uname: Linux 6.2.0-37-generic x86_64 ApportVersion: 2.26.1-0ubuntu2.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Sun Dec 10 13:49:43 2023 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2023-11-21 (18 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageArchitecture: all Python3Details: /usr/bin/python3.11, Python 3.11.7, python3-minimal, 3.11.2-1 PythonDetails: /usr/bin/python3.11, Python 3.11.7, python-is-python3, 3.11.1-3 RelatedPackageVersions: dpkg 1.21.21ubuntu1 apt 2.6.0ubuntu0.1 SourcePackage: sgml-base Title: package sgml-base 1.31 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: sgml-base (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package lunar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sgml-base in Ubuntu. https://bugs.launchpad.net/bugs/2046066 Title: package sgml-base 1.31 failed to install/upgrade: triggers looping, abandoned Status in sgml-base package in Ubuntu: New Bug description: upgrading from 22.04 to 23.04 produced this error. ProblemType: Package DistroRelease: Ubuntu 23.04 Package: sgml-base 1.31 ProcVersionSignature: Ubuntu 6.2.0-37.38-generic 6.2.16 Uname: Linux 6.2.0-37-generic x86_64 ApportVersion: 2.26.1-0ubuntu2.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Sun Dec 10 13:49:43 2023 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2023-11-21 (18 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageArchitecture: all Python3Details: /usr/bin/python3.11, Python 3.11.7, python3-minimal, 3.11.2-1 PythonDetails: /usr/bin/python3.11, Python 3.11.7, python-is-python3, 3.11.1-3 RelatedPackageVersions: dpkg 1.21.21ubuntu1 apt 2.6.0ubuntu0.1 SourcePackage: sgml-base Title: package sgml-base 1.31 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sgml-base/+bug/2046066/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
