[Touch-packages] [Bug 1845046] Re: Bluetooth headphones default to low quality headset mode and fail to switch to A2DP when selected
** Description changed: - Whenever I turn on my headphones theyll connect to my computer but im + [Impact] + + Whenever I turn on my headphones they'll connect to my computer but I'm able to hear the input audio from my microphone and low quality output audio. I have to disconnect the headphones in the bluetooth devices and reconnect for it to fix the problem. - ProblemType: Bug - DistroRelease: Ubuntu 18.04 - Package: pulseaudio 1:11.1-1ubuntu7.2 - ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 - Uname: Linux 5.0.0-29-generic x86_64 - NonfreeKernelModules: nvidia_modeset nvidia - ApportVersion: 2.20.9-0ubuntu7.7 - Architecture: amd64 - AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC1: litleck1398 F pulseaudio - /dev/snd/controlC0: litleck1398 F pulseaudio - CurrentDesktop: ubuntu:GNOME - Date: Mon Sep 23 17:07:59 2019 - InstallationDate: Installed on 2019-09-22 (0 days ago) - InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) - ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash - SourcePackage: pulseaudio - Symptom: audio - Symptom_Card: WH-1000XM3 - Symptom_Type: High background noise, or volume is too low - Title: [WH-1000XM3, playback] Background noise or low volume - UpgradeStatus: No upgrade log present (probably fresh install) - dmi.bios.date: 02/12/2019 - dmi.bios.vendor: Alienware - dmi.bios.version: 1.0.19 - dmi.board.name: 01NYPT - dmi.board.vendor: Alienware - dmi.board.version: A00 - dmi.chassis.type: 3 - dmi.chassis.vendor: Alienware - dmi.chassis.version: Not Specified - dmi.modalias: dmi:bvnAlienware:bvr1.0.19:bd02/12/2019:svnAlienware:pnAlienwareAuroraR5:pvr1.0.19:rvnAlienware:rn01NYPT:rvrA00:cvnAlienware:ct3:cvrNotSpecified: - dmi.product.family: Alienware - dmi.product.name: Alienware Aurora R5 - dmi.product.sku: 0729 - dmi.product.version: 1.0.19 - dmi.sys.vendor: Alienware + [Test Case] + + 0. Set up your Bluetooth headphones with Ubuntu. + 1. Turn off the headphones. + 2. Turn on the headphones. + 3. In Settings>Sound verify they have reconnected in A2DP mode (stereo, high quality, no microphone support). + + [Regression Potential] + + Low. Only the headset code path is affected and the fix has already been + released for some time in BlueZ 5.51 onward. -- 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/1845046 Title: Bluetooth headphones default to low quality headset mode and fail to switch to A2DP when selected Status in bluez package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Invalid Status in bluez source package in Bionic: Triaged Status in bluez source package in Eoan: Fix Committed Status in bluez source package in Focal: Fix Released Bug description: [Impact] Whenever I turn on my headphones they'll connect to my computer but I'm able to hear the input audio from my microphone and low quality output audio. I have to disconnect the headphones in the bluetooth devices and reconnect for it to fix the problem. [Test Case] 0. Set up your Bluetooth headphones with Ubuntu. 1. Turn off the headphones. 2. Turn on the headphones. 3. In Settings>Sound verify they have reconnected in A2DP mode (stereo, high quality, no microphone support). [Regression Potential] Low. Only the headset code path is affected and the fix has already been released for some time in BlueZ 5.51 onward. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1845046/+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 1845046] Re: Bluetooth headphones default to low quality headset mode and fail to switch to A2DP when selected
Patch for Ubuntu 19.10 ** Patch added: "bluez_5.50-0ubuntu5.debdiff" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1845046/+attachment/5317845/+files/bluez_5.50-0ubuntu5.debdiff ** Changed in: bluez (Ubuntu Eoan) Status: Triaged => Fix Committed -- 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/1845046 Title: Bluetooth headphones default to low quality headset mode and fail to switch to A2DP when selected Status in bluez package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Invalid Status in bluez source package in Bionic: Triaged Status in bluez source package in Eoan: Fix Committed Status in bluez source package in Focal: Fix Released Bug description: Whenever I turn on my headphones theyll connect to my computer but im able to hear the input audio from my microphone and low quality output audio. I have to disconnect the headphones in the bluetooth devices and reconnect for it to fix the problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: litleck1398 F pulseaudio /dev/snd/controlC0: litleck1398 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Sep 23 17:07:59 2019 InstallationDate: Installed on 2019-09-22 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: WH-1000XM3 Symptom_Type: High background noise, or volume is too low Title: [WH-1000XM3, playback] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2019 dmi.bios.vendor: Alienware dmi.bios.version: 1.0.19 dmi.board.name: 01NYPT dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.0.19:bd02/12/2019:svnAlienware:pnAlienwareAuroraR5:pvr1.0.19:rvnAlienware:rn01NYPT:rvrA00:cvnAlienware:ct3:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware Aurora R5 dmi.product.sku: 0729 dmi.product.version: 1.0.19 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1845046/+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 1845046] Re: Bluetooth headphones/speaker such as Sony WH-1000XM3 default to low quality headset mode and fails to switch to A2DP when selected
** No longer affects: gnome-control-center (Ubuntu) ** Also affects: pulseaudio (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: bluez (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: bluez (Ubuntu Eoan) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: bluez (Ubuntu Eoan) Importance: Undecided => High ** Changed in: bluez (Ubuntu Eoan) Status: New => Triaged ** Also affects: pulseaudio (Ubuntu Focal) Importance: High Status: Invalid ** Also affects: bluez (Ubuntu Focal) Importance: High Status: Fix Released ** No longer affects: pulseaudio (Ubuntu Eoan) ** No longer affects: pulseaudio (Ubuntu Focal) ** Summary changed: - Bluetooth headphones/speaker such as Sony WH-1000XM3 default to low quality headset mode and fails to switch to A2DP when selected + Bluetooth headphones default to low quality headset mode and fails to switch to A2DP when selected ** Summary changed: - Bluetooth headphones default to low quality headset mode and fails to switch to A2DP when selected + Bluetooth headphones default to low quality headset mode and fail to switch to A2DP when selected -- 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/1845046 Title: Bluetooth headphones default to low quality headset mode and fail to switch to A2DP when selected Status in bluez package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Invalid Status in bluez source package in Bionic: Triaged Status in bluez source package in Eoan: Triaged Status in bluez source package in Focal: Fix Released Bug description: Whenever I turn on my headphones theyll connect to my computer but im able to hear the input audio from my microphone and low quality output audio. I have to disconnect the headphones in the bluetooth devices and reconnect for it to fix the problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: litleck1398 F pulseaudio /dev/snd/controlC0: litleck1398 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Sep 23 17:07:59 2019 InstallationDate: Installed on 2019-09-22 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: WH-1000XM3 Symptom_Type: High background noise, or volume is too low Title: [WH-1000XM3, playback] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2019 dmi.bios.vendor: Alienware dmi.bios.version: 1.0.19 dmi.board.name: 01NYPT dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.0.19:bd02/12/2019:svnAlienware:pnAlienwareAuroraR5:pvr1.0.19:rvnAlienware:rn01NYPT:rvrA00:cvnAlienware:ct3:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware Aurora R5 dmi.product.sku: 0729 dmi.product.version: 1.0.19 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1845046/+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 1850762] Re: stub-resolver no longer optional, systemd dns broken
[Expired for systemd (Ubuntu) because there has been no activity for 60 days.] ** Changed in: systemd (Ubuntu) Status: Incomplete => Expired -- 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/1850762 Title: stub-resolver no longer optional, systemd dns broken Status in systemd package in Ubuntu: Expired Bug description: systemd name resolution is broken in professional setups. https://askubuntu.com/a/974482 used to provide a solution, simply ignore stub-resolution (which is broken) and fall back to the normal name resolution as configured (e.g. through dhcp). this solution does not seem to be available after upgrading to ubuntu 19.10 - there is no clean resolv.conf left. please advise as to how systemd name resolution through its local service can be disabled now (as it is broken). Thanks $ lsb_release -rd Description: Ubuntu 19.10 Release: 19.10 $ apt-cache policy systemd systemd: Installed: 242-7ubuntu3 Candidate: 242-7ubuntu3 Version table: *** 242-7ubuntu3 500 500 http://de.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status I expected my computer to resolve names (it used to do so after the workaround for the systemd bug) It does not resolve all names anymore (and the old workaround doesn't work anymore). ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: systemd 242-7ubuntu3 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 CurrentDesktop: MATE Date: Thu Oct 31 10:02:05 2019 InstallationDate: Installed on 2019-04-10 (203 days ago) InstallationMedia: Ubuntu-MATE 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) MachineType: LENOVO 20L8S29W00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=fddb227e-dc5d-4f78-b605-443eeb5bf5c9 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to eoan on 2019-10-24 (6 days ago) dmi.bios.date: 09/13/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET49W (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L8S29W00 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN22ET49W(1.26):bd09/13/2018:svnLENOVO:pn20L8S29W00:pvrThinkPadT480s:rvnLENOVO:rn20L8S29W00:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480s dmi.product.name: 20L8S29W00 dmi.product.sku: LENOVO_MT_20L8_BU_Think_FM_ThinkPad T480s dmi.product.version: ThinkPad T480s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1850762/+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 1845046] Re: Bluetooth headphones/speaker such as Sony WH-1000XM3 default to low quality headset mode and fails to switch to A2DP when selected
** Also affects: pulseaudio (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: gnome-control-center (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: bluez (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: bluez (Ubuntu Bionic) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: bluez (Ubuntu Bionic) Importance: Undecided => High ** Changed in: bluez (Ubuntu Bionic) Status: New => Triaged ** No longer affects: gnome-control-center (Ubuntu Bionic) ** No longer affects: pulseaudio (Ubuntu Bionic) ** No longer affects: pulseaudio -- 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/1845046 Title: Bluetooth headphones/speaker such as Sony WH-1000XM3 default to low quality headset mode and fails to switch to A2DP when selected Status in bluez package in Ubuntu: Fix Released Status in gnome-control-center package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Invalid Status in bluez source package in Bionic: Triaged Bug description: Whenever I turn on my headphones theyll connect to my computer but im able to hear the input audio from my microphone and low quality output audio. I have to disconnect the headphones in the bluetooth devices and reconnect for it to fix the problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: litleck1398 F pulseaudio /dev/snd/controlC0: litleck1398 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Sep 23 17:07:59 2019 InstallationDate: Installed on 2019-09-22 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: WH-1000XM3 Symptom_Type: High background noise, or volume is too low Title: [WH-1000XM3, playback] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2019 dmi.bios.vendor: Alienware dmi.bios.version: 1.0.19 dmi.board.name: 01NYPT dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.0.19:bd02/12/2019:svnAlienware:pnAlienwareAuroraR5:pvr1.0.19:rvnAlienware:rn01NYPT:rvrA00:cvnAlienware:ct3:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware Aurora R5 dmi.product.sku: 0729 dmi.product.version: 1.0.19 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1845046/+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 1858338] Re: Keyboard unresponsive after suspend and resume (19.10)
When you say the trackpad still works, can you also click on things and get them to respond? If you get a response to the trackpad then this is probably a keyboard bug to be assigned to the kernel. If you get no response from the trackpad and can only move the cursor then this is probably a gnome- shell crash under Xorg. Since you seem to have the 'wayland-session' tag here already I will assume the former... ** Package changed: xorg (Ubuntu) => linux (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/1858338 Title: Keyboard unresponsive after suspend and resume (19.10) Status in linux package in Ubuntu: New Bug description: Since two to three weeks, my keyboard sometimes becomes unresponsive after wake up from resume. Often it is associated with an @ sign on black background, when the machine is resumed. After that I am back in the desktop. Trackpad and everything works, but the keyboard doesn't. This is on a 2009 macbook pro running uptodate 19.10. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair wl ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jan 5 16:30:10 2020 DistUpgraded: 2019-10-06 16:30:12,792 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.3.0-23-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.3.0-24-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation C79 [GeForce 9400M] [10de:0863] (rev b1) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. C79 [GeForce 9400M] [106b:00b9] InstallationDate: Installed on 2019-01-12 (358 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Apple Inc. MacBookPro5,5 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=595c74ec-799d-4c25-bc8d-f06155d59f97 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to eoan on 2019-10-06 (91 days ago) dmi.bios.date: 06/15/09 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP55.88Z.00AC.B03.0906151708 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F2268AC8 dmi.board.vendor: Apple Inc. dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F2268AC8 dmi.modalias: dmi:bvnAppleInc.:bvrMBP55.88Z.00AC.B03.0906151708:bd06/15/09:svnAppleInc.:pnMacBookPro5,5:pvr1.0:rvnAppleInc.:rnMac-F2268AC8:rvr:cvnAppleInc.:ct10:cvrMac-F2268AC8: dmi.product.family: MacBook dmi.product.name: MacBookPro5,5 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858338/+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 1858336] Re: Xorg crashed with assertion failure in DRIMoveBuffersHelper
It looks like the recurring problem here is indeed just Xorg: [ 604.230] (EE) Backtrace: [ 604.230] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x5576c3d8facc] [ 604.231] (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7f6767b6359f] [ 604.231] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) [0x7f67679a13eb] [ 604.232] (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) [0x7f6767980899] [ 604.232] (EE) unw_get_proc_name failed: no unwind info found [-10] [ 604.232] (EE) 4: /lib/x86_64-linux-gnu/libc.so.6 (?+0x0) [0x7f676798075a] [ 604.232] (EE) 5: /lib/x86_64-linux-gnu/libc.so.6 (__assert_fail+0x46) [0x7f6767992006] [ 604.232] (EE) 6: /usr/lib/xorg/Xorg (DRIMoveBuffersHelper+0xc15) [0x5576c3d5aaa5] [ 604.232] (EE) 7: /usr/lib/xorg/Xorg (DRI2Authenticate+0xa2) [0x5576c3d5c0f2] [ 604.233] (EE) 8: /usr/lib/xorg/Xorg (DRI2GetParam+0x944) [0x5576c3d5d4b4] [ 604.233] (EE) 9: /usr/lib/xorg/Xorg (SendErrorToClient+0x354) [0x5576c3c2ef44] [ 604.233] (EE) 10: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x5576c3c32fd4] [ 604.233] (EE) 11: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7f67679821e3] [ 604.233] (EE) 12: /usr/lib/xorg/Xorg (_start+0x2e) [0x5576c3c1ca1e] ** Summary changed: - Login loops with GNOME Boxes on Xorg + Xorg crashed with assertion failure in DRIMoveBuffersHelper ** Summary changed: - Xorg crashed with assertion failure in DRIMoveBuffersHelper + [qxl] Xorg crashed with assertion failure in DRIMoveBuffersHelper ** Package changed: xorg (Ubuntu) => xserver-xorg-video-qxl (Ubuntu) ** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New -- 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/1858336 Title: [qxl] Xorg crashed with assertion failure in DRIMoveBuffersHelper Status in xorg-server package in Ubuntu: New Status in xserver-xorg-video-qxl package in Ubuntu: New Bug description: After doing a normal installation with erasing the disk in GNOME Boxes, I cannot log into the Ubuntu Xorg session. Wayland works fine, but this still isn't a workaround if the user wants to use Xorg for any given reason. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jan 5 10:21:36 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100] InstallationDate: Installed on 2020-01-05 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200104) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 002: ID 08e6:4433 Gemalto (was Gemplus) GemPC433-Swap Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Chip/SmartCard, Driver=, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=3faaad6a-d32e-4d07-877f-3ef17831e142 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: ?-20191223_100556-anatol dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr?-20191223_100556-anatol:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-4.2 dmi.sys.vendor: QEMU version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
[Touch-packages] [Bug 1858253] Re: Outdated package causing nvidia driver to fail.
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). Thanks! ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete ** Package changed: xorg (Debian) => debian ** Package changed: debian => mir ** No longer affects: mir -- 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/1858253 Title: Outdated package causing nvidia driver to fail. Status in Ubuntu: Incomplete Bug description: https://devtalk.nvidia.com/default/topic/1017185/linux/problem-with- resume-from-suspend-ubuntu-16-04-gt-940mx-/post/5415871/#5415871 https://ubuntu.pl/forum/viewtopic.php?f=145=184690=1033087#p1033075 [ 124.546] Build Operating System: Linux 4.4.0-148-generic x86_64 Ubuntu [ 124.547] Current Operating System: Linux lsd-K56CB 5.0.0-37-generic #40~18.04.1-Ubuntu SMP Thu Nov 14 12:06:39 UTC 2019 x86_64 Linux Mint 19.3 Tricia \n \l To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1858253/+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 1858200] Re: pulseaudio produces garbage on HDMI after 19.10
The other thing that changed in this area between 19.04 and 19.10 was the kernel, so we need to rule that out first before pursuing PulseAudio. Please try installing kernel 5.0.0 which is more like what was in Ubuntu 19.04: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.0/ Then run 'uname -a' to confirm the older kernel is active. Does the bug still occur there? ** 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/1858200 Title: pulseaudio produces garbage on HDMI after 19.10 Status in pulseaudio package in Ubuntu: Incomplete Bug description: After upgrading from 19.04 to 19.10, the sound output to HDMI is garbage. The sound is great on local output, on bluetooth headphones, etc. But when outputting to a HDMI TV it is garbage. I tried different users with the same problem. If I boot on Windows, the output is fine, which discards any physical problem, cables and TV as the source of the problem. I did delete any user pulseaudio configuration (and tried as a different one). I purged all system wide configuration and reinstalled the default pulseaudio configs with: apt-get -o DPkg::options::=--force-confmiss --reinstall install pulseaudio On 19.04 and before this problem did not happen at all. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1 Uname: Linux 5.4.5-050405-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: raul 4850 F pulseaudio /dev/snd/controlC0: raul 4850 F pulseaudio CurrentDesktop: KDE Date: Fri Jan 3 09:33:11 2020 InstallationDate: Installed on 2014-05-12 (2062 days ago) InstallationMedia: Error: [Errno 13] Permission denied: '/var/log/installer/media-info' SourcePackage: pulseaudio UpgradeStatus: Upgraded to eoan on 2019-11-17 (46 days ago) dmi.bios.date: 02/22/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.12 dmi.board.asset.tag: Tag 12345 dmi.board.name: P870KM_KM1 dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd02/22/2017:svnNotebook:pnP870KM_KM1:pvrNotApplicable:rvnNotebook:rnP870KM_KM1:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: P870KM_KM1 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook modified.conffile..etc.pulse.default.pa: [modified] modified.conffile..etc.pulse.system.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2019-12-22T00:17:51.785216 mtime.conffile..etc.pulse.system.pa: 2019-12-22T00:16:08.693216 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1858200/+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 1858181] Re: System freeze with bluetooth mouse plugin, 19.10
** Summary changed: - Xorg freeze with bluetooth mouse plugin, 19.10 + System freeze with bluetooth mouse plugin, 19.10 ** Package changed: xorg (Ubuntu) => linux (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/1858181 Title: System freeze with bluetooth mouse plugin, 19.10 Status in linux package in Ubuntu: Confirmed Bug description: Release: 19.10 Xorg Version: 1:7.7_19ubuntu12 Problem: After powering on my computer, grub's menu shows the options for starting Ubuntu, advanced Ubuntu options, etc. If I have my bluetooth mouse receiver plugged into the usb port, the menu freezes and a hard reboot is necessary as I cannot move my cursor; however, this continues only as long as the receiver is plugged in. Once it is removed and a hard reboot is done (reboot necessary to unfreeze), the menu allows me to select "Ubuntu" and access the OS. Plugging back in in the OS lets me use the mouse without problem, but relapses if I restart/shut down. Environment Details: New HP Spectre x360, 15-inch, freshly wiped from Windows 10 Home and installed with Ubuntu 19.10 Eoan Ermine after failing to dual-boot. My boot order in HP's bios is by usb drive first followed by the system boot option, the order of which does not seem to have an effect on the problem. The mouse is a Jelly Comb 2.4GHz wireless rechargeable mouse (not sure if important). There is no legacy mode, and safeboot is currently disabled; however, the parity of the option has not affected the problem. The mouse is solely what seems to cause the issue. I plan on testing with other USB dongles for debugging if you want more data on if it's all wireless mice, all usb dongles or what have you. Steps to replicate: 0 Put wireless mouse receiver in USB slot (Spectre has only 1 so test all of them) 1 Turn on computer with ubuntu 2 Try to select any option on the grub menu. Should be frozen and unresponsive 3 Unplugging mouse should not affect frozen state 4 Restart computer with free USB slots 5 Grub should be responsive ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..3b.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:3b:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jan 3 01:51:02 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-18-generic, x86_64: installed nvidia, 435.21, 5.3.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:863f] Subsystem: Hewlett-Packard Company GP108M [GeForce MX250] [103c:863f] InstallationDate: Installed on 2020-01-03 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: HP HP Spectre x360 Convertible 15t-df100 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/25/2019 dmi.bios.vendor: AMI dmi.bios.version: F.10 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 863F dmi.board.vendor: HP dmi.board.version: 54.13 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.10:bd07/25/2019:svnHP:pnHPSpectrex360Convertible15t-df100:pvr:rvnHP:rn863F:rvr54.13:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 15t-df100 dmi.product.sku: 5ZV31AV dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
[Touch-packages] [Bug 1858164] Re: libpulse-dev needs a rebuild for libpulse0-1:11.1-1ubuntu7.5 on bionic-updates
It seems this is a side effect of a mistake made in the release and subsequent withdrawal of update 1:11.1-1ubuntu7.5. So it's not a bug in the code but is a problem people will encounter with Ubuntu updates... This should automatically correct itself with the re-release of 1:11.1-1ubuntu7.5. In the meantime you can manually install whichever set of packages you need from either: 1:11.1-1ubuntu7.4: https://launchpad.net/ubuntu/+source/pulseaudio/1:11.1-1ubuntu7.4/+build/17893827 1:11.1-1ubuntu7.5: https://launchpad.net/ubuntu/+source/pulseaudio/1:11.1-1ubuntu7.5/+build/18146190 ** Changed in: pulseaudio (Ubuntu) Status: Confirmed => Fix Committed -- 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/1858164 Title: libpulse-dev needs a rebuild for libpulse0-1:11.1-1ubuntu7.5 on bionic-updates Status in pulseaudio package in Ubuntu: Fix Committed Bug description: 1) The release of Ubuntu you are using: $ lsb_release -rd Description: Ubuntu 18.04.3 LTS Release: 18.04 2) The version of the package you are using: $ dpkg -l | grep libpulse ii libpulse-mainloop-glib0:amd64 1:11.1-1ubuntu7.5 amd64PulseAudio client libraries (glib support) ii libpulse0:amd64 1:11.1-1ubuntu7.5 amd64PulseAudio client libraries ii libpulse0:i3861:11.1-1ubuntu7.5 i386 PulseAudio client libraries ii libpulsedsp:amd64 1:11.1-1ubuntu7.5 amd64PulseAudio OSS pre-load library 3) What you expected to happen "sudo apt install libpulse-dev" should installed libpulse-dev. 4) What happened instead $ sudo apt install libpulse-dev Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies. libpulse-dev : Depends: libpulse0 (= 1:11.1-1ubuntu7.4) but 1:11.1-1ubuntu7.5 is to be installed Depends: libpulse-mainloop-glib0 (= 1:11.1-1ubuntu7.4) but 1:11.1-1ubuntu7.5 is to be installed E: Unable to correct problems, you have held broken packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1858164/+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 1858164] Re: libpulse-dev needs a rebuild for libpulse0-1:11.1-1ubuntu7.5 on bionic-updates
There is no problem in the source code which says:
Package: libpulse-dev
Section: libdevel
Architecture: any
Multi-Arch: same
Depends: ${misc:Depends},
libpulse0 (= ${binary:Version}),
** Tags added: bionic
--
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/1858164
Title:
libpulse-dev needs a rebuild for libpulse0-1:11.1-1ubuntu7.5 on
bionic-updates
Status in pulseaudio package in Ubuntu:
Fix Committed
Bug description:
1) The release of Ubuntu you are using:
$ lsb_release -rd
Description: Ubuntu 18.04.3 LTS
Release: 18.04
2) The version of the package you are using:
$ dpkg -l | grep libpulse
ii libpulse-mainloop-glib0:amd64 1:11.1-1ubuntu7.5
amd64PulseAudio client libraries (glib support)
ii libpulse0:amd64 1:11.1-1ubuntu7.5
amd64PulseAudio client libraries
ii libpulse0:i3861:11.1-1ubuntu7.5
i386 PulseAudio client libraries
ii libpulsedsp:amd64 1:11.1-1ubuntu7.5
amd64PulseAudio OSS pre-load library
3) What you expected to happen
"sudo apt install libpulse-dev" should installed libpulse-dev.
4) What happened instead
$ sudo apt install libpulse-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies.
libpulse-dev : Depends: libpulse0 (= 1:11.1-1ubuntu7.4) but
1:11.1-1ubuntu7.5 is to be installed
Depends: libpulse-mainloop-glib0 (= 1:11.1-1ubuntu7.4) but
1:11.1-1ubuntu7.5 is to be installed
E: Unable to correct problems, you have held broken packages.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1858164/+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 1858194] Re: lost session when hibernate (reset session)
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- 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/1858194 Title: lost session when hibernate (reset session) Status in xorg-server package in Ubuntu: Incomplete Bug description: When I switch between my desk (with a docking station and an extra screen) and standalone position (PC alone without connection with any device), my computer reset X session and loose all the working session. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] est un dossier: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 410.48 Thu Sep 6 06:36:33 CDT 2018 GCC version: gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1) .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Jan 3 10:36:33 2020 DistUpgraded: 2018-12-07 12:13:28,435 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 410.48, 4.15.0-70-generic, x86_64: installed nvidia, 410.48, 4.15.0-72-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07b0] NVIDIA Corporation GM206GLM [Quadro M2200 Mobile] [10de:1436] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GM206GLM [Quadro M2200 Mobile] [1028:07b0] InstallationDate: Installed on 2018-06-12 (569 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Precision 7520 ProcEnviron: PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic root=UUID=a13fc76a-0a74-4653-8ab7-ca7342579d56 ro acpi_rev_override acpi_rev_override acpi_rev_override acpi_rev_override quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-12-07 (391 days ago) dmi.bios.date: 05/30/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.1 dmi.board.name: 0GC6C7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.1:bd05/30/2019:svnDellInc.:pnPrecision7520:pvr:rvnDellInc.:rn0GC6C7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 7520 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to:
[Touch-packages] [Bug 1858093] Re: Display Driver Issue
Please be careful to only report one issue per bug report. It's OK to open multiple bug reports. Which issue would you like this bug to be about? ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/1858093 Title: Display Driver Issue Status in Ubuntu: Incomplete Bug description: Not able to Suspend/Hibernate and facing issues in brightness controlling. Also screen don't turn off once it is locked. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jan 2 17:30:41 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:096a] InstallationDate: Installed on 2019-12-25 (7 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:671e Microdia Bus 001 Device 002: ID 27c6:5301 Bus 001 Device 004: ID 0cf3:e009 Atheros Communications, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Vostro 3590 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic root=UUID=d0ddd98e-6672-461c-bb96-25092a84666e ro quiet splash acpi_backlight=vendor vt.handoff=1 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.0 dmi.board.name: 0MNRJY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.0:bd06/25/2019:svnDellInc.:pnVostro3590:pvr:rvnDellInc.:rn0MNRJY:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 3590 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1858093/+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 1858035] Re: [arrandale] Xorg freeze (Ubuntu 19.10 stuck on splash screen)
We would like to see the system log from a frozen boot. To get that we need to look at a negative boot ID. Please reproduce the freeze again and then on the very next boot which doesn't freeze run: journalctl -b-1 > prevboot.txt Then send us the file 'prevboot.txt'. ** Summary changed: - Xorg freeze (Ubuntu 19.10 stuck on splash screen) + [arrandale] Xorg freeze (Ubuntu 19.10 stuck on splash screen) ** Changed in: xorg (Ubuntu) Status: New => Incomplete ** Package changed: xorg (Ubuntu) => ubuntu ** Summary changed: - [arrandale] Xorg freeze (Ubuntu 19.10 stuck on splash screen) + [arrandale] Graphics freeze (Ubuntu 19.10 stuck on splash screen) -- 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/1858035 Title: [arrandale] Graphics freeze (Ubuntu 19.10 stuck on splash screen) Status in Ubuntu: Incomplete Bug description: Yesterday I had just installed Ubuntu 19.10 and after my third or fourth reboot it would not start, it just got stuck on the splash screen. I didn't know what to do, but I still had the USB from which I had installed Ubuntu, so I plugged it in and booted up from the USB, and then I pressed the shutdown button, and before it shut down Ubuntu asked me to remove the installation media and press OK, I did, the laptop shut down, and now I booted up my laptop as usual, not from the USB, and this time it did not get stuck on the splash screen. So I left it at that, but just now, I booted up my laptop,and again it got stuck again, and so again I did the boot up from the USB, shut down, remove USB, and reboot as usual from the laptops HDD. Now it works again. This problem seems to happen on a random basis. I hope this helps to solve this problem. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jan 1 18:58:18 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Continuously GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Core Processor Integrated Graphics Controller [1028:0410] InstallationDate: Installed on 2019-12-30 (2 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Latitude E4310 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=6e8b1021-3bce-4fb7-a48b-eb93e408c4d4 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0XG3JF dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd05/12/2017:svnDellInc.:pnLatitudeE4310:pvr0001:rvnDellInc.:rn0XG3JF:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E4310 dmi.product.version: 0001 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1858035/+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 1847570] Re: PulseAudio automatically switches to HDMI sound output on login
The fix for 19.10 is queued and on the way: https://launchpad.net/ubuntu/eoan/+queue?queue_state=1 -- 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/1847570 Title: PulseAudio automatically switches to HDMI sound output on login Status in PulseAudio: New Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Eoan: Triaged Status in pulseaudio source package in Focal: Fix Released Bug description: [Impact] On my freshly installed eoan system I have two output devices: - HDMI/DisplayPort 2 - GK208 ... - Line Out - Family 17h ... When I login into the system pulseaudio always select the "wrong" one (HDMI) and I need to go to gnome-settings/Sound/Output Device and switch to "line out". This applies to every login/logout not just reboots. [Test Case] 0. Plug in a monitor that supports HDMI audio (one that appears in your Settings>Sound) 1. Log out and in again. Verify the default audio device in Settings is still speakers or headphones. Not the monitor's HDMI audio device. [Regression Potential] Low. The fix proposed just reverts to the same code used in PulseAudio 12 and earlier. It has also been released and verified on focal already. [Workaround] Comment out: load-module module-switch-on-port-available load-module module-switch-on-connect from /etc/pulse/default.pa To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1847570/+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 1858141] Re: "Advanced" tab is missing from Print dialog in Qt5 applications
Well, thanks anyway for looking into it. It's disappointing, but I can totally understand why this won't be backported if the patch is that complex and touches that many other packages. I'll just use the workaround until I get the updated Qt stack in 20.04. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1858141 Title: "Advanced" tab is missing from Print dialog in Qt5 applications Status in qtbase-opensource-src package in Ubuntu: Fix Released Status in qtbase-opensource-src source package in Bionic: Won't Fix Bug description: Please backport Qt patch 213391 to qtbase-opensource-src in Bionic: https://codereview.qt-project.org/#/c/213391/ [Impact] On Kubuntu 18.04 (bionic), any applications using Qt5 are unable to fully configure printers from within the "Print..." dialog because the "Advanced" tab is no longer present. Settings shown here will differ by printer, but this includes important settings such as paper type (plain, glossy, photo, etc.), print resolution, and ink usage strategies. Gwenview and Okular are notable affected applications. GTK applications are unaffected and do show the advanced options provided by the printer driver. As a workaround for Qt5 applications, the printer *default* advanced settings can be successfully accessed and changed from within the "Printers" section of Plasma's "System Settings", but this is cumbersome, unintuitive, and is not the intended way of interacting with these settings on a per-print-job basis. [Additional Information] This was identified as a bug in Qt5 upstream: https://bugreports.qt.io/browse/QTBUG-54464 The bug was fixed upstream in Qt 5.11, but Bionic is stable on Qt 5.9. I'd like to request that this patch be backported to Bionic, please. [Regression Potential] OpenSUSE has already backported this patch to their Qt 5.9 stable branch, so there is precedent for this patch being low risk: https://build.opensuse.org/package/view_file/KDE:Qt:5.9/libqt5-qtbase/0010-Reintroduce-the-Advanced-tab-in-the-QPrintProperties.patch?expand=1 Software Versions: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.3 LTS Release:18.04 Codename: bionic $ apt-cache policy libqt5printsupport5 libqt5printsupport5: Installed: 5.9.5+dfsg-0ubuntu2.4 Candidate: 5.9.5+dfsg-0ubuntu2.4 Version table: *** 5.9.5+dfsg-0ubuntu2.4 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 5.9.5+dfsg-0ubuntu2.1 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 5.9.5+dfsg-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1858141/+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 1816271] Re: [regression] No sound on ThinkPad T530 until activity at headphone jack(in or out/in) after about 14Feb19
This bug is closed so if you still experience problems then please open a new bug by running: ubuntu-bug 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/1816271 Title: [regression] No sound on ThinkPad T530 until activity at headphone jack(in or out/in) after about 14Feb19 Status in pulseaudio package in Ubuntu: Invalid Bug description: 19.04,kern 4.19.0-13 just took update and now does not recognize soundcard or something plugged in to headphones jack. pulled bug. Now if I unplug headphones and plug back in, it wakes up and recognizes it and works fine. I thought I had this prob a few days ago and restored back to the 10th, and updated all but alsa and worked fine. This morning I checked and a bunch of alsa stuff was no longer showing in updates, took everything, and worked fine. Just took updates (Software Updater), and checked speakers and no go. When this happened, it also would not allow sound to HDTV via HDMI, no matter what. Just tested and was able to get sound via hdmi, but remember, I have already "woken it up" by unplugging and plugging headphones (actually sony vaio computer speakers) ThinkPad T530-2394-3J8, i5-3380M 2.9GHz, Dual boot (BIOS/MBR): Grub, Ubuntu 19.04dev / Win7 Pro x64 . 8GB(15GB/s), Sammy 250GB SSD. Fast! I expected sound to recognize soundcard/speakers. It did not until I unplug/replug headphones. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gstreamer1.0-plugins-good 1.15.1-1ubuntu2 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Feb 16 19:20:26 2019 InstallationDate: Installed on 2019-02-09 (7 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gst-plugins-good1.0 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kris 1512 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-02-09 (8 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) Package: pulseaudio 1:12.2-2ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Tags: disco Uname: Linux 4.19.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/23/2018 dmi.bios.vendor: LENOVO dmi.bios.version: G4ETB4WW (2.74 ) dmi.board.asset.tag: Not Available dmi.board.name: 23943J8 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG4ETB4WW(2.74):bd11/23/2018:svnLENOVO:pn23943J8:pvrThinkPadT530:rvnLENOVO:rn23943J8:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T530 dmi.product.name: 23943J8 dmi.product.sku: LENOVO_MT_2394 dmi.product.version: ThinkPad T530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1816271/+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
Re: [Touch-packages] [Bug 1833479] Re: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs
Can this package get updated to 1.9.13, or at least patched in time for 20.04? The security exploitability of this bug may be low, but the impact on affected users is high. It causes hard to debug, random crashes of other programs (e g. Kodi) that are scanning ALSA devices when the jack daemon isn't even started. On Wed, Nov 20, 2019, 10:40 PM Teeedubb <1833...@bugs.launchpad.net> wrote: > Hi, > > I am experiencing the same issue with Kodi 18.5 and Xubuntu 19.10 with > similar stack traces to joe-yasi. Is there anyway to install the updated > package via Ubuntu updates? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1833479 > > Title: > libjack-jackd2-0 double close on a failure to connect to jackd which > causes crashes in multithreaded programs > > Status in jackd2 package in Ubuntu: > Confirmed > Status in jackd2 package in Debian: > Confirmed > > Bug description: > After upgrading to Ubuntu 19.04, I started experiencing sporadic > crashes in kodi when turning my AV receiver on. Ubuntu 19.04 upgraded > alsa-plugins to 1.1.8. For alsa-plugins >= 1.1.7, the ALSA jack plugin > is enabled by default in /etc/alsa/conf.d/50-jack.conf. > > The crashes are caused by a race condition when kodi's audio engine > thread is enumerating the ALSA sound devices, and the udev thread is > enumerating the udev devices triggered by the sound device add from > turning the AVR on. > > When enumerating the ALSA jack plugin device, it tries to connect to > connect to jackd. Since I don't have jackd installed, it fails to > connect. libjack closes the socket on error, and then closes it again > in it's cleanup code. Since it's closing the same file descriptor > twice, it interacts with other threads that have potentially opened > file descriptors, and causes the crash. > > This same bug could potentially affect other multi-threaded programs > that enumerate ALSA devices. > > Fix committed upstream: > > https://github.com/jackaudio/jack2/commit/dad4b5702782eef3bd66e3c3f4fefaaae3571208 > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1833479/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1833479 Title: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs Status in jackd2 package in Ubuntu: Confirmed Status in jackd2 package in Debian: Confirmed Bug description: After upgrading to Ubuntu 19.04, I started experiencing sporadic crashes in kodi when turning my AV receiver on. Ubuntu 19.04 upgraded alsa-plugins to 1.1.8. For alsa-plugins >= 1.1.7, the ALSA jack plugin is enabled by default in /etc/alsa/conf.d/50-jack.conf. The crashes are caused by a race condition when kodi's audio engine thread is enumerating the ALSA sound devices, and the udev thread is enumerating the udev devices triggered by the sound device add from turning the AVR on. When enumerating the ALSA jack plugin device, it tries to connect to connect to jackd. Since I don't have jackd installed, it fails to connect. libjack closes the socket on error, and then closes it again in it's cleanup code. Since it's closing the same file descriptor twice, it interacts with other threads that have potentially opened file descriptors, and causes the crash. This same bug could potentially affect other multi-threaded programs that enumerate ALSA devices. Fix committed upstream: https://github.com/jackaudio/jack2/commit/dad4b5702782eef3bd66e3c3f4fefaaae3571208 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1833479/+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 1685754] Re: gnome-terminal unduly forces umask=0022
Sven, here are the workaround steps (as root) :
1) Create the folder '/etc/systemd/user/gnome-terminal-server.service.d' (with
usual mode 755).
2) In this newly created folder, create the 'umask.conf' file with following
content :
[Service]
UMask=
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1685754
Title:
gnome-terminal unduly forces umask=0022
Status in gedit:
Invalid
Status in gnome-session:
New
Status in GNOME Terminal:
Confirmed
Status in Nautilus:
Confirmed
Status in dbus package in Ubuntu:
Confirmed
Status in gnome-terminal package in Ubuntu:
Confirmed
Bug description:
In order to set the default umask of my users to 027 or 007, I
followed the instructions provided in 'man pam_umask' :
In the 'gecos' field of '/etc/passwd', I have inserted 'umask=027' or
'umask=007' (for myself).
Then, MOST graphical applications systematically run with the correct
umask.
In particular, when I press Alt-F2, run 'xterm sh' and type 'umask',
it systematically displays 0007.
But when I press Alt-F2, run 'gnome-terminal -e sh' and type 'umask',
it systematically displays 0022.
That is BAD, and is a security issue.
Workaround : Inside the newly created '/etc/profile.d/umask.sh', and in each
'~/.bashrc', add following content :
UMASK="$(grep -o "^$USER:.*,umask=0[0-7]*" /etc/passwd)"
if [ "$UMASK" ]; then
umask "${UMASK#$USER:*,umask=}"
fi
In fact, 'gnome-terminal' MUST NOT force umask=022, but keep umask unchanged.
Thank you in advance for a quick correction.
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: gnome-terminal 3.20.2-1ubuntu8
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CurrentDesktop: X-Cinnamon
Date: Mon Apr 24 08:36:58 2017
InstallationDate: Installed on 2017-03-28 (26 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
SourcePackage: gnome-terminal
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/gedit/+bug/1685754/+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 1858293] Re: Missing repeated characters
Question Answers: 1. Windows 10 laptop core i7 Microsoft Windows [Version 10.0.17763.914] 2. TERM=xterm 3. write(1, "\33[?1049h\33[22;0;0t\33[1;47r\33(B\33[m\33[4l\33[?7h\33[39;49m\33[?1h\33=", 54) = 54 write(1, "\33[?1h\33=", 7) = 7 write(1, "\33[?1h\33=", 7) = 7 write(1, "\33[?25l", 6) = 6 write(1, "\33[39;49m\33(B\33[m\33[H\33[2J", 21) = 21 write(1, "\33(B\33[0;7m GNU nano 2.9.3 \33[53bNew Buffer \33[63b \33[1;144H", 56) = 56 write(1, "\33(B\33[m", 6) = 6 write(1, "\r\33[46d", 6)= 6 write(1, "\33(B\33[0;7m^G\33(B\33[m Get Help \33(B\33[0;7m^O\33(B\33[m Write Out\33(B\33[0;7m^W\33(B\33[m Where Is \33(B\33[0;7m^K\33(B\33[m Cut Text \33(B\33[0;7m^J\33(B\33[m Justify\33[81G", 154) = 154 write(1, "\33(B\33[0;7m^C\33(B\33[m Cur Pos\33[97G", 30) = 30 write(1, "\33(B\33[0;7mM-U\33(B\33[m Undo\33[46;113H", 32) = 32 write(1, "\33(B\33[0;7mM-A\33(B\33[m Mark Text \33(B\33[0;7mM-]\33(B\33[m To Bracket\r\33[47d", 66) = 66 write(1, "\33(B\33[0;7m^X\33(B\33[m Exit\33[47;17H", 30) = 30 write(1, "\33(B\33[0;7m^R\33(B\33[m Read File\33(B\33[0;7m^\\\33(B\33[m Replace\33[49G", 61) = 61 write(1, "\33(B\33[0;7m^U\33(B\33[m Uncut Text \33(B\33[0;7m^T\33(B\33[m To Spell \33(B\33[0;7m^_\33(B\33[m Go To Line \33(B\33[0;7mM-E\33(B\33[m Redo\33[47;113H", 125) = 125 write(1, "\33(B\33[0;7mM-6\33(B\33[m Copy Text \33(B\33[0;7mM-W\33(B\33[m WhereIs Next\r\33[45d", 68) = 68 write(1, "\33[3d", 4) = 4 write(1, "\33[39;49m\33(B\33[m", 14)= 14 write(1, "\33[?12l\33[?25h", 12)= 12 write(1, "\33[?25l", 6) = 6 write(1, "\33[1;136H", 8) = 8 write(1, "\33(B\33[0;7mModified", 17) = 17 write(1, "\33(B\33[m", 6) = 6 write(1, "\r\33[3d", 5) = 5 write(1, "#\33[9G", 5) = 5 write(1, "+-\33[7b+\33[25G", 12)= 12 write(1, "+-\33[7b+\33[41G", 12)= 12 write(1, "+-\33[7b+\33[57G", 12)= 12 write(1, "+-\33[7b+\r\33[4d", 12) = 12 write(1, "#\33[9G", 5) = 5 write(1, "|\33[4;18H", 8) = 8 write(1, "|\33[25G", 6) = 6 write(1, "|\33[4;34H", 8) = 8 write(1, "|\33[41G", 6) = 6 write(1, "|\33[4;50H", 8) = 8 write(1, "|\33[57G", 6) = 6 write(1, "|\33[4;66H", 8) = 8 write(1, "|\r\33[5d", 6)= 6 write(1, "# >CLK->|\33[5;18H", 16) = 16 write(1, "|>CLK->|\33[5;34H", 15) = 15 write(1, "|>CLK->|\33[5;50H", 15) = 15 write(1, "|>CLK->|\33[5;66H", 15) = 15 write(1, "|>CLK->\r\33[6d", 12) = 12 write(1, "# >CS ->|\33[6;18H", 16) = 16 write(1, "|>CS ->|\33[6;34H", 15) = 15 write(1, "|>CS ->|\33[6;50H", 15) = 15 write(1, "|>CS ->|\33[6;66H", 15) = 15 write(1, "|>CS ->\r\33[7d", 12) = 12 write(1, "# >DIN->|\33[7;18H", 16) = 16 write(1, "|>DIN->|\33[7;34H", 15) = 15 write(1, "|>DIN->|\33[7;50H", 15) = 15 write(1, "|>DIN->|\33[7;66H", 15) = 15 write(1, "|>DIN->\r\33[8d", 12) = 12 write(1, "#\33[9G", 5) = 5 write(1, "|\33[8;18H", 8) = 8 write(1, "|\33[25G", 6) = 6 write(1, "|\33[8;34H", 8) = 8 write(1, "|\33[41G", 6) = 6 write(1, "|\33[8;50H", 8) = 8 write(1, "|\33[57G", 6) = 6 write(1, "|\33[8;66H", 8) = 8 write(1, "|\r\33[9d", 6)= 6 write(1, "#\33[9G", 5) = 5 write(1, "+-\33[7b+\33[25G", 12)= 12 write(1, "+-\33[7b+\33[41G", 12)= 12 write(1, "+-\33[7b+\33[57G", 12)= 12 write(1, "+-\33[7b+", 7)= 7 write(1, "\33[?12l\33[?25h", 12)= 12 write(1, "\33[?25l", 6) = 6 write(1, "\r\33[45d", 6)= 6 write(1, "\33(B\33[0;7mSave modified buffer? (Answering \"No\" will DISCARD changes.) \33[82b \33[46;1H", 84) = 84 write(1, " Y\33(B\33[m Yes\33[K\r\33[47d", 21) = 21 write(1, "\33(B\33[0;7m N\33(B\33[m No \33[47;18H", 30) = 30 write(1, "\33(B\33[0;7mC\33(B\33[m Cancel\33[K\33[45;63H", 34) = 34 write(1, "\33[?12l\33[?25h", 12)= 12 write(1, "\33[?25l", 6) = 6 write(1, "\r", 1) = 1 write(1, "\33[J\33[47;145H", 12)= 12 write(1, "\33[?12l\33[?25h", 12)= 12 write(1, "\33[47;1H\33[?1049l\33[23;0;0t\r\33[?1l\33>", 32) = 32 +++ exited with 0 +++ 4. I am putty'd in on machine 1 and ssh into machine 2, open nano, paste the example and issue is still there. 5. I have not "built" a nano4-7 on the machine. But I can try tomorrow if you still need me to do so. Just let me know. 6. I do not have access to a 19.10 machine Thanks. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nano in Ubuntu. https://bugs.launchpad.net/bugs/1858293 Title: Missing repeated
[Touch-packages] [Bug 1858361] [NEW] /usr/lib/tracker/tracker-store:11:tracker_writeback_transact:tracker_store_on_statements_committed:_tracker_store_on_statements_committed_tracker_commit_callback:t
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding tracker. This problem was most recently seen with package version 2.3.1-1, the problem page at https://errors.ubuntu.com/problem/ae2e8393101fd16b6c88d15f22ec43828be91c66 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: tracker (Ubuntu) Importance: Undecided Status: New ** Tags: disco eoan focal kylin-19.10 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1858361 Title: /usr/lib/tracker/tracker- store:11:tracker_writeback_transact:tracker_store_on_statements_committed:_tracker_store_on_statements_committed_tracker_commit_callback:tracker_data_commit_transaction:update_sparql Status in tracker package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding tracker. This problem was most recently seen with package version 2.3.1-1, the problem page at https://errors.ubuntu.com/problem/ae2e8393101fd16b6c88d15f22ec43828be91c66 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1858361/+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 1858360] [NEW] /usr/libexec/evolution-calendar-factory:11:tcache_get:__GI___libc_malloc:pvl_newlist:icalcomponent_new_impl:icalcomponent_new
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding evolution-data-server. This problem was most recently seen with package version 3.34.1-1build1, the problem page at https://errors.ubuntu.com/problem/1fe5b6b206c2db7112df2b401761c7188a1ddab2 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: evolution-data-server (Ubuntu) Importance: Undecided Status: New ** Tags: eoan focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1858360 Title: /usr/libexec/evolution-calendar- factory:11:tcache_get:__GI___libc_malloc:pvl_newlist:icalcomponent_new_impl:icalcomponent_new Status in evolution-data-server package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding evolution-data-server. This problem was most recently seen with package version 3.34.1-1build1, the problem page at https://errors.ubuntu.com/problem/1fe5b6b206c2db7112df2b401761c7188a1ddab2 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1858360/+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 1853825] Re: ^W ^G ^X fails to redisplay the text being edited
Any chance that this patch can get released into Eoan? It is an upstream patch. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nano in Ubuntu. https://bugs.launchpad.net/bugs/1853825 Title: ^W ^G ^X fails to redisplay the text being edited Status in nano package in Ubuntu: New Bug description: There is a silly display bug in nano-4.3 (https://savannah.gnu.org/bugs/?57295): when opening some file (for example, 'nano README') and typing the sequence Ctrl+W Ctrl+G Ctrl+X, the Search help text stays on the screen whereas the text of the README file should be redisplayed. Attached upstream patch fixes this. Please apply to Eoan. (It could be applied to Focal too, but nano-4.6 will be out within a week, so it's probably not worth the effort.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nano/+bug/1853825/+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 1572807] Re: /bin/nano:*** Error in `nano': double free or corruption (!prev): ADDR ***
As the patch for bug #1641592 has been released to Xenial, it means that this bug has been fixed too. ** Changed in: nano (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nano in Ubuntu. https://bugs.launchpad.net/bugs/1572807 Title: /bin/nano:*** Error in `nano': double free or corruption (!prev): ADDR *** Status in nano package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding nano. This problem was most recently seen with version 2.5.3-2, the problem page at https://errors.ubuntu.com/problem/7dd7f74a72fca06513544d8af66b623efa15b26c contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nano/+bug/1572807/+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 1685754] Re: gnome-terminal unduly forces umask=0022
is there now a solution that works under Ubuntu 19.10?
/etc/systemd/user/gnome-terminal-server.service.d/umask.conf
The path from "gnome-terminal-server.service.d" does not exist here at
all.
The problem should be solved after such a long time :-( Is there a
plan how the problem can be solved?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1685754
Title:
gnome-terminal unduly forces umask=0022
Status in gedit:
Invalid
Status in gnome-session:
New
Status in GNOME Terminal:
Confirmed
Status in Nautilus:
Confirmed
Status in dbus package in Ubuntu:
Confirmed
Status in gnome-terminal package in Ubuntu:
Confirmed
Bug description:
In order to set the default umask of my users to 027 or 007, I
followed the instructions provided in 'man pam_umask' :
In the 'gecos' field of '/etc/passwd', I have inserted 'umask=027' or
'umask=007' (for myself).
Then, MOST graphical applications systematically run with the correct
umask.
In particular, when I press Alt-F2, run 'xterm sh' and type 'umask',
it systematically displays 0007.
But when I press Alt-F2, run 'gnome-terminal -e sh' and type 'umask',
it systematically displays 0022.
That is BAD, and is a security issue.
Workaround : Inside the newly created '/etc/profile.d/umask.sh', and in each
'~/.bashrc', add following content :
UMASK="$(grep -o "^$USER:.*,umask=0[0-7]*" /etc/passwd)"
if [ "$UMASK" ]; then
umask "${UMASK#$USER:*,umask=}"
fi
In fact, 'gnome-terminal' MUST NOT force umask=022, but keep umask unchanged.
Thank you in advance for a quick correction.
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: gnome-terminal 3.20.2-1ubuntu8
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CurrentDesktop: X-Cinnamon
Date: Mon Apr 24 08:36:58 2017
InstallationDate: Installed on 2017-03-28 (26 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
SourcePackage: gnome-terminal
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/gedit/+bug/1685754/+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 1858338] [NEW] Keyboard unresponsive after suspend and resume (19.10)
Public bug reported: Since two to three weeks, my keyboard sometimes becomes unresponsive after wake up from resume. Often it is associated with an @ sign on black background, when the machine is resumed. After that I am back in the desktop. Trackpad and everything works, but the keyboard doesn't. This is on a 2009 macbook pro running uptodate 19.10. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair wl ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jan 5 16:30:10 2020 DistUpgraded: 2019-10-06 16:30:12,792 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.3.0-23-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.3.0-24-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation C79 [GeForce 9400M] [10de:0863] (rev b1) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. C79 [GeForce 9400M] [106b:00b9] InstallationDate: Installed on 2019-01-12 (358 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Apple Inc. MacBookPro5,5 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=595c74ec-799d-4c25-bc8d-f06155d59f97 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to eoan on 2019-10-06 (91 days ago) dmi.bios.date: 06/15/09 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP55.88Z.00AC.B03.0906151708 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F2268AC8 dmi.board.vendor: Apple Inc. dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F2268AC8 dmi.modalias: dmi:bvnAppleInc.:bvrMBP55.88Z.00AC.B03.0906151708:bd06/15/09:svnAppleInc.:pnMacBookPro5,5:pvr1.0:rvnAppleInc.:rnMac-F2268AC8:rvr:cvnAppleInc.:ct10:cvrMac-F2268AC8: dmi.product.family: MacBook dmi.product.name: MacBookPro5,5 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ubuntu wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1858338 Title: Keyboard unresponsive after suspend and resume (19.10) Status in xorg package in Ubuntu: New Bug description: Since two to three weeks, my keyboard sometimes becomes unresponsive after wake up from resume. Often it is associated with an @ sign on black background, when the machine is resumed. After that I am back in the desktop. Trackpad and everything works, but the keyboard doesn't. This is on a 2009 macbook pro running uptodate 19.10. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair wl ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jan 5 16:30:10 2020 DistUpgraded: 2019-10-06 16:30:12,792 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.3.0-23-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.3.0-24-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation C79 [GeForce 9400M] [10de:0863] (rev b1) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. C79 [GeForce 9400M] [106b:00b9] InstallationDate: Installed on 2019-01-12 (358 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
[Touch-packages] [Bug 1858336] [NEW] Login loops with GNOME Boxes on Xorg
Public bug reported: After doing a normal installation with erasing the disk in GNOME Boxes, I cannot log into the Ubuntu Xorg session. Wayland works fine, but this still isn't a workaround if the user wants to use Xorg for any given reason. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jan 5 10:21:36 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100] InstallationDate: Installed on 2020-01-05 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200104) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 002: ID 08e6:4433 Gemalto (was Gemplus) GemPC433-Swap Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Chip/SmartCard, Driver=, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=3faaad6a-d32e-4d07-877f-3ef17831e142 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: ?-20191223_100556-anatol dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr?-20191223_100556-anatol:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-4.2 dmi.sys.vendor: QEMU version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal regression reproducible ubuntu wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1858336 Title: Login loops with GNOME Boxes on Xorg Status in xorg package in Ubuntu: New Bug description: After doing a normal installation with erasing the disk in GNOME Boxes, I cannot log into the Ubuntu Xorg session. Wayland works fine, but this still isn't a workaround if the user wants to use Xorg for any given reason. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jan 5 10:21:36 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100] InstallationDate: Installed on 2020-01-05 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200104) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 002: ID 08e6:4433 Gemalto (was Gemplus) GemPC433-Swap Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev
[Touch-packages] [Bug 1858293] Re: Missing repeated characters
Thanks for reporting. Please answer the following questions. 1) From what kind of machine are you putty'ing into your Ubuntu 18.04 machines? 2) When putty'ed in, what is the output of 'env | grep TERM'? 3) When putty'ed in, please run 'strace -ewrite -s2000 /bin/nano --ignore 2>TRAIL', paste your seven-line example into nano, then press ^X N, and attach the resultant TRAIL file here. 4) When ssh'ing in from a regular GNU/Linux machine (from an xterm or from a Linux console) to your Ubuntu 18.04 machines, do you observe the same problem? 5) If you build the latest nano-4.7 on one of your 18.04 machines, does the problem still occur when putty'ing in and running nano-4.7? 6) When you putty into an Ubuntu 19.10 machine (if you can find one), does the problem occur there too? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nano in Ubuntu. https://bugs.launchpad.net/bugs/1858293 Title: Missing repeated characters Status in nano package in Ubuntu: New Bug description: Nano 2.9.3 Ubuntu 18.04.3 LTS - Linux 4.14.157-171 armv7l ARMv7 Processor rev 3 (v7l) Ubuntu 18.04.3 LTS - Linux 4.9.196-63 aarch64 Amlogic S922X rev a (4 A73 + 2 A53) This issue is repeatable on more than 6 each different machines of the above configurations. I am using ssh via Putty to log in via terminal screen. I am using nano defaults. I have not changed anything nor do I open with any arguments. I use nano and it's not associated with any extension. It behaves the same for all files, even no extension files. Nano is not changing the file, it's just not displaying correctly. The characters are there and they save properly, they're just not visible on the terminal screen. Using WinSCP presents no issues as I am using my local Windows text editor. If I use vi to view the file there are no problems. If I use cat to view the file there are no problems. If I use tail to view the file there are no problems I do not experience this issue on: Nano 2.5.3 Ubuntu 16.04.6 LTS - Linux 4.14.5-92 armv7l ARMv7 Processor rev 3 (v7l) If I take any file that has repeat characters such as: - ||| Nano 2.9.3 will not display all of the continuous repeat characters in the row. For example: Copy and paste is displayed as: # <-- But end of line is correct If I copy that line from the file in nano editor and paste it into another non nano editor I get: # as the paste result This is the same for all different repeated characters. If I keyboard type ## nano will display it until nano is closed and then the same file is reopened. Then it's same as above, one # but end of line is correct. Pasting: # ++ ++ ++ ++ # || || || || # >CLK->||>CLK->||>CLK->||>CLK->||>CLK-> # >CS ->||>CS ->||>CS ->||>CS ->||>CS -> # >DIN->||>DIN->||>DIN->||>DIN->||>DIN-> # || || || || # ++ ++ ++ ++ into nano results in displayed: # +-+ +-+ +-+ +-+ # | | | | | | | | # >CLK->| |>CLK->| |>CLK->| |>CLK->| |>CLK-> # >CS ->| |>CS ->| |>CS ->| |>CS ->| |>CS -> # >DIN->| |>DIN->| |>DIN->| |>DIN->| |>DIN-> # | | | | | | | | # +-+ +-+ +-+ +-+ while nano is still open. Close the file and view in cat, vi or tail and it is show properly.. Pasting: # ++ ++ ++ ++ # || || || || # >CLK->||>CLK->||>CLK->||>CLK->||>CLK-> # >CS ->||>CS ->||>CS ->||>CS ->||>CS -> # >DIN->||>DIN->||>DIN->||>DIN->||>DIN-> # || || || || # ++ ++ ++ ++ using vi editor then save file and open file in nano results in: # +-+ +-+ +-+ +-+ # | | | | | | | | # >CLK->| |>CLK->| |>CLK->| |>CLK->| |>CLK-> # >CS ->| |>CS ->| |>CS ->| |>CS ->| |>CS -> # >DIN->| |>DIN->| |>DIN->| |>DIN->| |>DIN-> # | | | | | | | | # +-+ +-+ +-+ +-+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nano/+bug/1858293/+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 1558899] Re: Recent recipe version of FreeFont were failed to build
** Branch unlinked: lp:~vcs-imports-ii/freefont/trunk -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-freefont in Ubuntu. https://bugs.launchpad.net/bugs/1558899 Title: Recent recipe version of FreeFont were failed to build Status in fonts-freefont package in Ubuntu: New Bug description: Since 2016-03-16, recipe builds of FreeFont were failed to build when I try to download from here: https://code.launchpad.net/~dns/+recipe/freefont To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-freefont/+bug/1558899/+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
