[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1858387] Re: LibreOffice Calc used all the memory with CPU overloaded when import a txt file into Calc
Additional Notes: The bug may related to the bug report: https://bugs.documentfoundation.org/show_bug.cgi?id=120796 Everything goes fine after it was changed from .txt to .csv. ** Bug watch added: Document Foundation Bugzilla #120796 https://bugs.documentfoundation.org/show_bug.cgi?id=120796 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1858387 Title: LibreOffice Calc used all the memory with CPU overloaded when import a txt file into Calc Status in libreoffice package in Ubuntu: New Bug description: The situation found when I try to covert a txt file into Calc file by libreoffice. The preview looks all fine, all the tabs and texts were well arranged in the preview. However, when the button "ok" was pressed, libreoffice use all the memory and CPU, even the txt file only has 4.7 kB with only 74 rows and 7 columns. It use all memory (10 GB) in the conversion. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libreoffice-core 1:6.0.7-0ubuntu0.18.04.10 ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jan 6 13:41:32 2020 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin InstallationDate: Installed on 2018-04-29 (616 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) SourcePackage: libreoffice UpgradeStatus: Upgraded to bionic on 2019-12-20 (16 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1858387/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1858387] [NEW] LibreOffice Calc used all the memory with CPU overloaded when import a txt file into Calc
Public bug reported: The situation found when I try to covert a txt file into Calc file by libreoffice. The preview looks all fine, all the tabs and texts were well arranged in the preview. However, when the button "ok" was pressed, libreoffice use all the memory and CPU, even the txt file only has 4.7 kB with only 74 rows and 7 columns. It use all memory (10 GB) in the conversion. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libreoffice-core 1:6.0.7-0ubuntu0.18.04.10 ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jan 6 13:41:32 2020 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin InstallationDate: Installed on 2018-04-29 (616 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) SourcePackage: libreoffice UpgradeStatus: Upgraded to bionic on 2019-12-20 (16 days ago) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1858387 Title: LibreOffice Calc used all the memory with CPU overloaded when import a txt file into Calc Status in libreoffice package in Ubuntu: New Bug description: The situation found when I try to covert a txt file into Calc file by libreoffice. The preview looks all fine, all the tabs and texts were well arranged in the preview. However, when the button "ok" was pressed, libreoffice use all the memory and CPU, even the txt file only has 4.7 kB with only 74 rows and 7 columns. It use all memory (10 GB) in the conversion. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libreoffice-core 1:6.0.7-0ubuntu0.18.04.10 ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jan 6 13:41:32 2020 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin InstallationDate: Installed on 2018-04-29 (616 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) SourcePackage: libreoffice UpgradeStatus: Upgraded to bionic on 2019-12-20 (16 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1858387/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 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 Desktop Packages, which is subscribed to gnome-control-center 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1850780] Re: Right click often activates the first action
[Expired for firefox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: firefox (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1850780 Title: Right click often activates the first action Status in firefox package in Ubuntu: Expired Bug description: I'm having an issue on elementary OS (based on Ubuntu 18.04) every time that I right click, I also activate the right click menu. setting `ui.context_menus.after_mouseup` to true in about:config seems to fix the issue for me. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1850780/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1850912] Re: ALSA audio not working any more (with snap package)
[Expired for chromium-browser (Ubuntu) because there has been no activity for 60 days.] ** Changed in: chromium-browser (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1850912 Title: ALSA audio not working any more (with snap package) Status in chromium-browser package in Ubuntu: Expired Bug description: After upgrading from Ubuntu 19.04 to Ubuntu 19.10, audio in chromium browser stopped working, presumably this is related to chromium now being a snap package: Description: Ubuntu 19.10 Release: 19.10 Package: chromium-browser Architecture: amd64 Version: 77.0.3865.120-0ubuntu1~snap1 Note that I don't use pulseaudio or any other audio server on my system, it's supposed to use ALSA directly. In .xsession-errors I see: ALSA lib conf.c:3916:(snd_config_update_r) Cannot access file /usr/share/alsa/alsa.conf ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM default [2536:2536:1031/194827.989956:ERROR:alsa_util.cc(204)] PcmOpen: default,No such file or directory ALSA lib conf.c:3916:(snd_config_update_r) Cannot access file /usr/share/alsa/alsa.conf ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM plug:default [2536:2536:1031/194827.990132:ERROR:alsa_util.cc(204)] PcmOpen: plug:default,No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1850912/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1792085] Re: MTP not working/very slow on Bionic
I was able to fix this on Ubuntu 18.04 (bionic), which comes with libmtp-common=1.1.13 by installing a newer version of libmtp 1.1.16. Now Ubuntu transfers huge numbers of songs between my phone and laptop by simply drag-and-drop in Nautilus. sudo apt install build-essential pkg-config wget libusb-1.0-0-dev libusb-dev wget http://downloads.sourceforge.net/project/libmtp/libmtp/1.1.16/libmtp-1.1.16.tar.gz tar xzf libmtp-1.1.16.tar.gz cd libmtp-1.1.16 ./configure make sudo make install I didn't even have to uninstall the old version, and also no need for android-file-transfer or jmtpfs. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1792085 Title: MTP not working/very slow on Bionic Status in libmtp: New Status in gvfs package in Ubuntu: Incomplete Bug description: Hi, unfortunately (for me) MTP android devices no more work on Ubuntu 18.04. I have used MTP on 16.04 without problems, but on 18.04 it does not work. When I connect my Android devices (Samsung A5 and Samsung J3) and I try to list directories with many files (e.g. /DCIM/Camera) the window hangs until I disconnect the device. Same issue if I try to post the command "ls /var/run/1000/gvfs/". I have installed Ubuntu 18.04 on two different machines - an older HP laptop and a recent DELL laptop - and the issue is present on the all of them. I suspect a defect on the "libmtp". I tried many alternative solutions suggested by the net (e.g. jmtpfs and so on) but anyone worked. That's all! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gvfs-fuse 1.36.1-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 12 06:20:07 2018 LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libmtp/+bug/1792085/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 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 Desktop Packages, which is subscribed to gnome-control-center 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1858336] Re: [qxl] Xorg crashed with assertion failure in DRIMoveBuffersHelper
Please report the issue to the upstream developers here: https://gitlab.freedesktop.org/groups/xorg/-/issues and then tell us the new issue ID. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server 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 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1858336/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 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 Desktop 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
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1157043] Re: kvm guest xorg endless loop at startup
Thank you for reporting this bug to Ubuntu. Ubuntu 13.04 (raring) reached end-of-life on January 27, 2014. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: xserver-xorg-video-qxl (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-qxl in Ubuntu. https://bugs.launchpad.net/bugs/1157043 Title: kvm guest xorg endless loop at startup Status in xserver-xorg-video-qxl package in Ubuntu: Won't Fix Bug description: on raring, configuring a kvm guest with qxl make xorg restarting in an endless loop on the guest machine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-qxl/+bug/1157043/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1858332] Re: entire UI froze ctrl + alt +f2 no response
If the GUI is frozen but the mouse moves then this means it is the gnome-shell process that has frozen or crashed. The mouse can still move because that is done by Xorg. ... 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. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1858332 Title: entire UI froze ctrl + alt +f2 no response Status in gnome-shell package in Ubuntu: Incomplete Bug description: Entire system froze only mouse moved left click no response right click no response keyboard not responding could not access terminal via ctrl + alt +f2 or ctrl + alt + sys rq etc. here's the video https://www.youtube.com/watch?v=byaYLD9zyMU ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 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 CurrentDesktop: ubuntu:GNOME Date: Sun Jan 5 15:22:24 2020 DisplayManager: gdm3 InstallationDate: Installed on 2015-08-23 (1595 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-10-23 (74 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1858332/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1858332] Re: entire UI froze ctrl + alt +f2 no response
The the GUI is frozen but the mouse moves then this means it is the gnome-shell process that has frozen or crashed. The mouse can still move because that is done by Xorg. ... 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. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1858332 Title: entire UI froze ctrl + alt +f2 no response Status in gnome-shell package in Ubuntu: Incomplete Bug description: Entire system froze only mouse moved left click no response right click no response keyboard not responding could not access terminal via ctrl + alt +f2 or ctrl + alt + sys rq etc. here's the video https://www.youtube.com/watch?v=byaYLD9zyMU ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 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 CurrentDesktop: ubuntu:GNOME Date: Sun Jan 5 15:22:24 2020 DisplayManager: gdm3 InstallationDate: Installed on 2015-08-23 (1595 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-10-23 (74 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1858332/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1543192] Re: Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError("no screens found") from dix_main()
** Description changed:
https://errors.ubuntu.com/problem/4de849dfec89af168af9cda3318221a2a654e530
+ https://errors.ubuntu.com/problem/4c203db78dea0a68c29cbd981d4abbd4aef31851
---
No idea what happened.
ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: xserver-xorg-core 2:1.17.3-2ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
Uname: Linux 4.4.0-2-generic x86_64
.tmp.unity.support.test.0:
ApportVersion: 2.19.4-0ubuntu2
Architecture: amd64
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CrashCounter: 1
Date: Mon Feb 8 17:07:23 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExecutablePath: /usr/lib/xorg/Xorg
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation 2nd Generation Core Processor Family Integrated Graphics
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics
Controller [17aa:21da]
InstallationDate: Installed on 2015-04-30 (283 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: LENOVO 429149G
ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
ProcEnviron:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic
root=UUID=457973fc-512e-4b6a-b65b-85f15fa85b7b ro console=tty1 console=ttyS0
panic=-1
Signal: 6
SourcePackage: xorg-server
StacktraceTop:
OsAbort ()
?? ()
FatalError ()
?? ()
__libc_start_main (main=0x557f8180ff00, argc=11, argv=0x7fffc9e34fd8,
init=, fini=, rtld_fini=,
stack_end=0x7fffc9e34fc8) at libc-start.c:289
SystemImageInfo: Error: command ['system-image-cli', '-i'] failed with exit
code 2:
Title: Xorg crashed with SIGABRT in OsAbort()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 05/18/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 8DET46WW (1.16 )
dmi.board.asset.tag: Not Available
dmi.board.name: 429149G
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias:
dmi:bvnLENOVO:bvr8DET46WW(1.16):bd05/18/2011:svnLENOVO:pn429149G:pvrThinkPadX220:rvnLENOVO:rn429149G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 429149G
dmi.product.version: ThinkPad X220
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.2+16.04.20151211-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.66-2
version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.1-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.1-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20160127-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1
xserver.bootTime: Mon Feb 8 17:08:14 2016
xserver.configfile: default
xserver.errors: systemd-logind: failed to get session: PID 9847 does not
belong to any known session
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
product id 728
vendor LGD
xserver.version: 2:1.17.3-2ubuntu2
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1543192
Title:
Xorg crashed with SIGABRT in OsAbort() from AbortServer() from
FatalError("no screens found") from dix_main()
Status in xorg-server package in Ubuntu:
Confirmed
Bug description:
https://errors.ubuntu.com/problem/4de849dfec89af168af9cda3318221a2a654e530
https://errors.ubuntu.com/problem/4c203db78dea0a68c29cbd981d4abbd4aef31851
---
No idea what happened.
ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: xserver-xorg-core 2:1.17.3-2ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
Uname: Linux 4.4.0-2-generic x86_64
.tmp.unity.support.test.0:
ApportVersion: 2.19.4-0ubuntu2
Architecture: amd64
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CrashCounter: 1
Date: Mon Feb 8 17:07:23 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExecutablePath: /usr/lib/xorg/Xorg
[Desktop-packages] [Bug 1858290] Re: Move the Show applications button to the left edge when dock position is at the bottom
** Bug watch added: github.com/micheleg/dash-to-dock/issues #689 https://github.com/micheleg/dash-to-dock/issues/689 ** Also affects: dash-to-dock via https://github.com/micheleg/dash-to-dock/issues/689 Importance: Unknown Status: Unknown ** Project changed: dash-to-dock => ubuntu-dock ** Project changed: ubuntu-dock => dash-to-dock ** Project changed: dash-to-dock => ubuntu-dock ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided => Wishlist ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1858290 Title: Move the Show applications button to the left edge when dock position is at the bottom Status in ubuntu-dock: Unknown Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Triaged Bug description: Please, consider moving the Show applications button by-default to left edge when dock position on screen is set to bottom. It was originally discussed in upstream (dashtodock) ticket, however it was decided that the behavior won't be changed in upstream. Instead, it should be changed in ubuntu-dock. See the original upstream ticket: https://github.com/micheleg/dash-to- dock/issues/689 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-dock/+bug/1858290/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1858351] Re: Xorg crashed with SIGABRT in raise() from abort() from OsAbort() from AbortServer() from FatalError()
*** This bug is a duplicate of bug 1543192 ***
https://bugs.launchpad.net/bugs/1543192
** Summary changed:
- /usr/lib/xorg/Xorg:6:raise:abort:OsAbort:AbortServer:FatalError
+ Xorg crashed with SIGABRT in raise() from abort() from OsAbort() from
AbortServer() from FatalError()
** Summary changed:
- Xorg crashed with SIGABRT in raise() from abort() from OsAbort() from
AbortServer() from FatalError()
+ Xorg crashed with SIGABRT in raise() from abort() from OsAbort() from
AbortServer() from FatalError("no screens found")
** This bug has been marked a duplicate of bug 1543192
Xorg crashed with SIGABRT in OsAbort() from AbortServer() from
FatalError("no screens found") from dix_main()
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1858351
Title:
Xorg crashed with SIGABRT in raise() from abort() from OsAbort() from
AbortServer() from FatalError("no screens found")
Status in xorg-server package in Ubuntu:
New
Bug description:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
xorg-server. This problem was most recently seen with package version
2:1.20.5+git20191008-0ubuntu1, the problem page at
https://errors.ubuntu.com/problem/4c203db78dea0a68c29cbd981d4abbd4aef31851
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/xorg-server/+bug/1858351/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 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 Desktop 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:
[Desktop-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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 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 Desktop 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 version.xserver-xorg-core:
[Desktop-packages] [Bug 1858120] Re: Graphical corruption Intel HD Graphics 630 when using Firefox nightly in Wayland mode
If the problem really was mutter#655 then this would be a duplicate of bug 1844222. But you seem to have the fix for that already (mutter 3.34.2) so it sounds like this is not mutter#655. Can you please provide a screenshot or photo of the issue? ** Bug watch added: Mozilla Bugzilla #1604948 https://bugzilla.mozilla.org/show_bug.cgi?id=1604948 ** Also affects: firefox via https://bugzilla.mozilla.org/show_bug.cgi?id=1604948 Importance: Unknown Status: Unknown ** Project changed: gnome-shell => ubuntu ** No longer affects: ubuntu ** Also affects: firefox (Ubuntu) Importance: Undecided Status: New ** Package changed: gnome-shell (Ubuntu) => mutter (Ubuntu) ** Changed in: firefox (Ubuntu) Status: New => Incomplete ** Changed in: mutter (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1858120 Title: Graphical corruption Intel HD Graphics 630 when using Firefox nightly in Wayland mode Status in Mozilla Firefox: Unknown Status in firefox package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: Also tracked in: https://bugzilla.mozilla.org/show_bug.cgi?id=1604948 Once every few starts of Firefox on my machine ends up corrupting the display of my Wayland session badly - what looks like a lot of stray marks on my display are seen overlaid on top of all windows, not just Firefox. Logging out and logging back in resolves the issue, but there is a chance that it recurs on next launch. Steps to reproduce: 1. Start Gnome session in Wayland mode. 2. Start Firefox Nightly with MOZ_ENABLE_WAYLAND=1 What happens: Various issues, including "unknown" application appearing in task switcher, stray marks on screen, and dead/inactive windows that persist over other windows even when switching virtual desktops. Response from Firefox bugzilla says: This is likely a bug in GS 3.34, fixed by https://gitlab.gnome.org/GNOME/mutter/merge_requests/924 and https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/815, included in 3.34.2 which should arrive soon in Ubuntu 19.10. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-01 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191230) Package: gnome-shell 3.34.1+git20191024-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: mutter-common 3.34.2-2ubuntu1 Tags: focal wayland-session Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1858120/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 691232] Re: bluetooth pairing erroneously prompts for PIN
Thank you for reporting this bug to Ubuntu. Ubuntu 10.10 (maverick) reached end-of-life on April 10, 2012. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: gnome-bluetooth (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/691232 Title: bluetooth pairing erroneously prompts for PIN Status in gnome-bluetooth package in Ubuntu: Won't Fix Bug description: Binary package hint: gconf In Ubuntu 10:10: I'm trying to pair a microsoft 6000 bluetooth keyboard. After I enter the confirmation code, 99% of the time I'm then prompted with a dialog saying the device wants to pair with the system and would I enter a PIN. I have tried every option on the PIN menu and none of them result in a working keyboard :( Once in a great while, I do not get prompted for the PIN and then the keyboard will work ok. Under Ubuntu 9.x, I was not prompted for a PIN. THe pairing simply "worked" the first time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/691232/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852870] Re: core dumps when installing mono-devel in ppc64le/ubuntu:18.04
This does not occur when using podman 1.4.4, must be a nuance of Docker 1.13.1. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mono in Ubuntu. https://bugs.launchpad.net/bugs/1852870 Title: core dumps when installing mono-devel in ppc64le/ubuntu:18.04 Status in mono package in Ubuntu: New Bug description: (moderators: this is a resubmit since my browser generated an error when I tried to submit before, please delete if this ends up being a duplicate) When installing 'mono-devel' from the default repositories of ppc64le/ubuntu:18.04 with apt, core dumps are generated with no obvious errors in the terminal's output. I have not noticed this behavior with other packages deployed via apt (however, I have not ruled out it being a dependency of mono-devel causing them). These core dumps do not occur in the x86-64 version of ubuntu:18.04. Mono runtime appears to be functioning despite evidence something went wrong during package deployment. Attached is the terminal output and commands to reproduce in Docker. # lsb_release -rd Description: Ubuntu 18.04.3 LTS Release: 18.04 # apt-cache policy mono-devel mono-devel: Installed: 4.6.2.7+dfsg-1ubuntu1 Candidate: 4.6.2.7+dfsg-1ubuntu1 Version table: *** 4.6.2.7+dfsg-1ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports bionic/universe ppc64el Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mono/+bug/1852870/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1856846] Re: Gnome Xorg sessions fail to start with LDAP users (but Wayland or local users work)
Thanks. It appears this is a simple Xorg crash: Jan 02 08:09:39 ektorp /usr/lib/gdm3/gdm-x-session[4553]: (EE) Jan 02 08:09:39 ektorp /usr/lib/gdm3/gdm-x-session[4553]: (EE) Backtrace: Jan 02 08:09:39 ektorp /usr/lib/gdm3/gdm-x-session[4553]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x55e75e46d7d9] Jan 02 08:09:39 ektorp /usr/lib/gdm3/gdm-x-session[4553]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x50) [0x7f98acf708df] Jan 02 08:09:39 ektorp /usr/lib/gdm3/gdm-x-session[4553]: (EE) 2: /usr/lib/xorg/modules/drivers/modesetting_drv.so (_init+0x6501) [0x7f98aa25b251] Jan 02 08:09:39 ektorp /usr/lib/gdm3/gdm-x-session[4553]: (EE) 3: /usr/lib/xorg/Xorg (xf86RandR12Init+0x394) [0x55e75e38cae4] Jan 02 08:09:39 ektorp /usr/lib/gdm3/gdm-x-session[4553]: (EE) 4: /usr/lib/xorg/Xorg (xf86CrtcScreenInit+0x2b) [0x55e75e37f58b] Jan 02 08:09:39 ektorp /usr/lib/gdm3/gdm-x-session[4553]: (EE) 5: /usr/lib/xorg/modules/drivers/modesetting_drv.so (_init+0x3d0e) [0x7f98aa255eee] Jan 02 08:09:39 ektorp /usr/lib/gdm3/gdm-x-session[4553]: (EE) 6: /usr/lib/xorg/Xorg (AddScreen+0xd7) [0x55e75e3107e7] Jan 02 08:09:39 ektorp /usr/lib/gdm3/gdm-x-session[4553]: (EE) 7: /usr/lib/xorg/Xorg (InitOutput+0x3ce) [0x55e75e350c0e] Jan 02 08:09:39 ektorp /usr/lib/gdm3/gdm-x-session[4553]: (EE) 8: /usr/lib/xorg/Xorg (InitFonts+0x1dd) [0x55e75e31438d] Jan 02 08:09:39 ektorp /usr/lib/gdm3/gdm-x-session[4553]: (EE) 9: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xe7) [0x7f98acb8eb97] Jan 02 08:09:39 ektorp /usr/lib/gdm3/gdm-x-session[4553]: (EE) 10: /usr/lib/xorg/Xorg (_start+0x2a) [0x55e75e2fe1ea] Jan 02 08:09:39 ektorp /usr/lib/gdm3/gdm-x-session[4553]: (EE) Jan 02 08:09:39 ektorp /usr/lib/gdm3/gdm-x-session[4553]: (EE) Segmentation fault at address 0x30 Jan 02 08:09:39 ektorp /usr/lib/gdm3/gdm-x-session[4553]: (EE) Jan 02 08:09:39 ektorp /usr/lib/gdm3/gdm-x-session[4553]: Fatal server error: Jan 02 08:09:39 ektorp /usr/lib/gdm3/gdm-x-session[4553]: (EE) Caught signal 11 (Segmentation fault). Server aborting ** Package changed: gdm3 (Ubuntu) => xorg-server (Ubuntu) ** No longer affects: gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1856846 Title: Gnome Xorg sessions fail to start with LDAP users (but Wayland or local users work) Status in xorg-server package in Ubuntu: Incomplete Bug description: When trying to login to Gnome with an remote user from an LDAP (LDAP is available and connectable when in GDM) using X11, GDM loops around three to five times before actually granting access to the desktop. This does not happen when a) Wayland is used instead of X11 or, b) the LDAP server is not reachable during login, using X11, or c) a local user is logged in instead, using X11 The LDAP connection is established using the Univention Domain Join Client: https://launchpad.net/~univention- dev/+archive/ubuntu/ppa?field.series_filter=bionic Do you require additional information? Release: Description: Ubuntu 18.04.3 LTS Release: 18.04 GDM3: gdm3: Installed: 3.28.3-0ubuntu18.04.4 Candidate: 3.28.3-0ubuntu18.04.4 Version table: *** 3.28.3-0ubuntu18.04.4 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 3.28.0-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1856846/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1856846] Re: Gnome Xorg sessions fail to start with LDAP users (but Wayland or local users work)
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. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1856846 Title: Gnome Xorg sessions fail to start with LDAP users (but Wayland or local users work) Status in xorg-server package in Ubuntu: Incomplete Bug description: When trying to login to Gnome with an remote user from an LDAP (LDAP is available and connectable when in GDM) using X11, GDM loops around three to five times before actually granting access to the desktop. This does not happen when a) Wayland is used instead of X11 or, b) the LDAP server is not reachable during login, using X11, or c) a local user is logged in instead, using X11 The LDAP connection is established using the Univention Domain Join Client: https://launchpad.net/~univention- dev/+archive/ubuntu/ppa?field.series_filter=bionic Do you require additional information? Release: Description: Ubuntu 18.04.3 LTS Release: 18.04 GDM3: gdm3: Installed: 3.28.3-0ubuntu18.04.4 Candidate: 3.28.3-0ubuntu18.04.4 Version table: *** 3.28.3-0ubuntu18.04.4 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 3.28.0-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1856846/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857660] Re: The offending signal was destroy on Gjs_ExtensionRow
** No longer affects: netspeed (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1857660 Title: The offending signal was destroy on Gjs_ExtensionRow Status in gnome-shell package in Ubuntu: Incomplete Bug description: 1) Ubuntu 19.10 2) GNOME Shell 3.34.1 3) no error. 4) error in log app. Dec 25 2:57:16 PM gnome-shell-ext: The offending signal was destroy on Gjs_ExtensionRow 0x561b4774bee0. Dec 25 2:57:16 PM gnome-shell-ext: The offending signal was destroy on Gjs_ExtensionRow 0x561b4774bee0. Dec 25 2:57:16 PM gnome-shell-ext: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Dec 25 2:57:16 PM gnome-shell-ext: The offending signal was destroy on Gjs_ExtensionRow 0x561b4774bbe0. Dec 25 2:57:16 PM gnome-shell-ext: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Dec 25 2:57:16 PM gnome-shell-ext: The offending signal was destroy on Gjs_ExtensionRow 0x561b4774b5e0. Dec 25 2:57:16 PM gnome-shell-ext: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Dec 25 2:57:16 PM gnome-shell-ext: The offending signal was destroy on Gjs_ExtensionRow 0x561b4774b2e0. Dec 25 2:57:16 PM gnome-shell-ext: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Dec 25 2:57:16 PM gnome-shell: == Stack trace for context 0x561b46fae1a0 == Dec 25 2:57:16 PM gnome-shell-ext: The offending signal was destroy on Gjs_ExtensionRow 0x561b4774b8e0. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1857660/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846090] Re: Asus UX580GD (GDX1505:00 27C6:01F1) Touchpad (LCD) screen support
Sounds like it's maybe connected to a hardware multiplexer ("mux"). I
don't have experience with such systems, but you might find it useful to
look at these:
https://wiki.archlinux.org/index.php/Hybrid_graphics
\https://01.org/linuxgraphics/gfx-docs/drm/gpu/vga-switcheroo.html
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1846090
Title:
Asus UX580GD (GDX1505:00 27C6:01F1) Touchpad (LCD) screen support
Status in linux package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
Confirmed
Status in xorg-server package in Ubuntu:
Confirmed
Bug description:
Ubuntu does not support asus zenbook pro UX580GD screenpad (touchpad
and screen - all in one)
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
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
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory:
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57
CDT 2019
GCC version: gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: XFCE
Date: Tue Oct 1 00:53:26 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
nvidia, 435.21, 5.0.0-29-generic, x86_64: installed
virtualbox, 5.2.32, 5.0.0-29-generic, x86_64: installed
DpkgLog:
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Device [1043:1021]
Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile]
[1043:180e]
InstallationDate: Installed on 2019-09-27 (3 days ago)
InstallationMedia: Xubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64
(20190805)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 13d3:5755 IMC Networks
Bus 001 Device 004: ID 8087:0aaa Intel Corp.
Bus 001 Device 003: ID 04f3:2544 Elan Microelectronics Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. ZenBook Pro 15 UX550GDX_UX580GD
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic
root=UUID=4fba8275-1f29-4ddc-8a1c-e239d3b76c14 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/09/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX550GDX.302
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX550GDX
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrUX550GDX.302:bd10/09/2018:svnASUSTeKCOMPUTERINC.:pnZenBookPro15UX550GDX_UX580GD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550GDX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: ZenBook Pro
dmi.product.name: ZenBook Pro 15 UX550GDX_UX580GD
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER 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.2
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.2
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846090/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1796928] Re: Fast Double-tap Treated as Single Click
** Bug watch added: gitlab.freedesktop.org/libinput/libinput/issues #158 https://gitlab.freedesktop.org/libinput/libinput/issues/158 ** Also affects: libinput via https://gitlab.freedesktop.org/libinput/libinput/issues/158 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libinput in Ubuntu. https://bugs.launchpad.net/bugs/1796928 Title: Fast Double-tap Treated as Single Click Status in libinput: Unknown Status in libinput package in Ubuntu: Fix Released Bug description: https://gitlab.freedesktop.org/libinput/libinput/issues/158 --- Fast double-taps get treated as a single click. Behavior is present in Ubuntu 18.04 (libinput 1.10.4-1) but not in 17.10 (libinput 1.8.2-1ubuntu2). Still present in 18.10 daily downloaded 2018.10.08 (libinput 1.12.0-1). I think this is similar to https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1762536 with different hardware. I'm trying to run Ubuntu 18.04 in a VMware Fusion guest on a Macbook host. If I double-tap the trackpad fast, it gets treated as a single- click in Ubuntu. If I double-tap slow (but not too slow) it gets treated as a double-click. Hitting the narrow window is hard! This makes it tough to run X in a VM on a Macbook. I suspect that the host hardware+software delivers a synthesized double-click to the guest, and that the time between the clicks is very small. evemu-record shows two "VirtualPS/2 VMware Virtual Mouse" devices and a "VMware VMware Virtual USB Mouse". Capture of the first of these is attached. It looks to me like the second tap comes 8 ms after the first, and I'm betting that is treated as bounce. Bug report also created at https://bugs.freedesktop.org/show_bug.cgi?id=108306 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2018-10-09 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: VMware, Inc. VMware Virtual Platform Package: libinput (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=a0e790b4-4632-4de9-aa52-4dff4fc9fe4f ro find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US quiet ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Tags: bionic ubuntu Uname: Linux 4.15.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/19/2017 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/19/2017:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 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/libinput/+bug/1796928/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 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 Desktop
Packages, which is subscribed to gnome-terminal 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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1858368] [NEW] single-day events on 1st of month show on all days of preceding month
Public bug reported: Single-day events on 1st of month show on all days of preceding month. For example, someone's birthday on April 1 will show up (in the month view) as being a month-long event during all of March. I am using a NextCloud calendar. The events look OK on the NextCloud web-based calendar, on my iphone, and on Mac's Calendar.app. Those same events appear fine in the week view... they are not stretched into the previous month. Alan Porter ubuntu-launch...@kr4jb.net ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-calendar 3.34.2-1 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 CurrentDesktop: ubuntu:GNOME Date: Sun Jan 5 17:24:56 2020 InstallationDate: Installed on 2019-12-30 (5 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: gnome-calendar UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-calendar (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan third-party-packages ** Attachment added: "Month view showing April Fools Day on every day in March." https://bugs.launchpad.net/bugs/1858368/+attachment/5317797/+files/Screenshot%20from%202020-01-05%2017-32-23.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1858368 Title: single-day events on 1st of month show on all days of preceding month Status in gnome-calendar package in Ubuntu: New Bug description: Single-day events on 1st of month show on all days of preceding month. For example, someone's birthday on April 1 will show up (in the month view) as being a month-long event during all of March. I am using a NextCloud calendar. The events look OK on the NextCloud web-based calendar, on my iphone, and on Mac's Calendar.app. Those same events appear fine in the week view... they are not stretched into the previous month. Alan Porter ubuntu-launch...@kr4jb.net ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-calendar 3.34.2-1 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 CurrentDesktop: ubuntu:GNOME Date: Sun Jan 5 17:24:56 2020 InstallationDate: Installed on 2019-12-30 (5 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: gnome-calendar UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1858368/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1858355] [NEW] /usr/lib/gnome-settings-daemon/gsd-print-notifications:free(): invalid pointer
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-settings-daemon. This problem was most recently seen with package version 3.34.1-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/3d7933d46e17d4d2ab4cdba47c09ba3f0cb34cf5 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: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: bionic cosmic disco eoan focal kylin-18.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1858355 Title: /usr/lib/gnome-settings-daemon/gsd-print-notifications:free(): invalid pointer Status in gnome-settings-daemon package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-settings-daemon. This problem was most recently seen with package version 3.34.1-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/3d7933d46e17d4d2ab4cdba47c09ba3f0cb34cf5 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/gnome-settings-daemon/+bug/1858355/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1858358] [NEW] /usr/lib/chromium-browser/chromium-browser:11:DeliberatelyTerminateToRecoverFromHang:Run:RunTask:DoWorkImpl:DoSomeWork
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding chromium-browser. This problem was most recently seen with package version 79.0.3945.79-0ubuntu0.19.04.3, the problem page at https://errors.ubuntu.com/problem/6680604da16ad0f8c6e99d38750aa7352fb22264 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: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: bionic disco xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1858358 Title: /usr/lib/chromium-browser/chromium- browser:11:DeliberatelyTerminateToRecoverFromHang:Run:RunTask:DoWorkImpl:DoSomeWork Status in chromium-browser package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding chromium-browser. This problem was most recently seen with package version 79.0.3945.79-0ubuntu0.19.04.3, the problem page at https://errors.ubuntu.com/problem/6680604da16ad0f8c6e99d38750aa7352fb22264 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/chromium-browser/+bug/1858358/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1858362] [NEW] /usr/bin/nautilus:11:tcache_get:__GI___libc_malloc:g_malloc:g_source_set_callback:g_task_attach_source
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:3.34.1-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/d27a750c5eaf7972c99c001fbb86cb2e6500594f 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: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: bionic eoan focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1858362 Title: /usr/bin/nautilus:11:tcache_get:__GI___libc_malloc:g_malloc:g_source_set_callback:g_task_attach_source Status in nautilus package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:3.34.1-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/d27a750c5eaf7972c99c001fbb86cb2e6500594f 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/nautilus/+bug/1858362/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1858359] [NEW] /usr/bin/gjs-console:5:gjs_array_from_carray_internal:gjs_value_from_explicit_array:gjs_callback_closure:ffi_closure_unix64_inner:ffi_closure_unix64
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gjs. This problem was most recently seen with package version 1.58.1-1, the problem page at https://errors.ubuntu.com/problem/897036aa239708c7e78ec460a8bc7c9571d61b3a 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: gjs (Ubuntu) Importance: Undecided Status: New ** Tags: bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1858359 Title: /usr/bin/gjs- console:5:gjs_array_from_carray_internal:gjs_value_from_explicit_array:gjs_callback_closure:ffi_closure_unix64_inner:ffi_closure_unix64 Status in gjs package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gjs. This problem was most recently seen with package version 1.58.1-1, the problem page at https://errors.ubuntu.com/problem/897036aa239708c7e78ec460a8bc7c9571d61b3a 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/gjs/+bug/1858359/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1858361] [NEW] /usr/lib/tracker/tracker-store:11:tracker_writeback_transact:tracker_store_on_statements_committed:_tracker_store_on_statements_committed_tracker_commit_callback
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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1858351] [NEW] /usr/lib/xorg/Xorg:6:raise:abort:OsAbort:AbortServer:FatalError
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding xorg-server. This problem was most recently seen with package version 2:1.20.5+git20191008-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/4c203db78dea0a68c29cbd981d4abbd4aef31851 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: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags: artful bionic cosmic disco eoan kylin-19.04 xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1858351 Title: /usr/lib/xorg/Xorg:6:raise:abort:OsAbort:AbortServer:FatalError Status in xorg-server package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding xorg-server. This problem was most recently seen with package version 2:1.20.5+git20191008-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/4c203db78dea0a68c29cbd981d4abbd4aef31851 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/xorg-server/+bug/1858351/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1858364] [NEW] /usr/bin/nautilus-desktop:ERROR:../src/nautilus-file.c:729:nautilus_file_get_internal: assertion failed: (location != NULL)
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:3.26.4-0ubuntu9, the problem page at https://errors.ubuntu.com/problem/8625807832947f023e918eb923eaac89cd468993 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: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: bionic cosmic disco kylin-18.04 kylin-18.10 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1858364 Title: /usr/bin/nautilus-desktop:ERROR:../src/nautilus- file.c:729:nautilus_file_get_internal: assertion failed: (location != NULL) Status in nautilus package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:3.26.4-0ubuntu9, the problem page at https://errors.ubuntu.com/problem/8625807832947f023e918eb923eaac89cd468993 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/nautilus/+bug/1858364/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1858349] [NEW] EAP-MSCHAPv2 support
Public bug reported: There is a patch available via this link. https://w3logistics.com/blog/archives/438-EAP-MSCHAPv2-for-pppd-2-4-7.html Adding support for EAP-MSCHAPv2 to this would be very helpful for sstp- client project to connect to an Azure instance. ** Affects: ppp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ppp in Ubuntu. https://bugs.launchpad.net/bugs/1858349 Title: EAP-MSCHAPv2 support Status in ppp package in Ubuntu: New Bug description: There is a patch available via this link. https://w3logistics.com/blog/archives/438-EAP-MSCHAPv2-for-pppd-2-4-7.html Adding support for EAP-MSCHAPv2 to this would be very helpful for sstp-client project to connect to an Azure instance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ppp/+bug/1858349/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1828697] Re: Volume and brightness OSD make full-screen video flicker once they disappear
** Bug watch added: gitlab.gnome.org/GNOME/mutter/issues #997 https://gitlab.gnome.org/GNOME/mutter/issues/997 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/issues/997 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1828697 Title: Volume and brightness OSD make full-screen video flicker once they disappear Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: Confirmed Bug description: Steps: 1. Open a video in Totem, MPV or YouTube 2. Make the video full-screen 3. Press the keyboard keys to change volume or brightness to show an OSD 4. Notice the video flicker ONCE the OSD disappears (as if it destroys the graphics behind it for a second) 5. Keep trying to show an OSD, changing volume or brightness, until you see the bug because sometimes it doesn't happen the first time and not consistently ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3+git20190124-0ubuntu18.04.2 ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-18-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun May 12 00:14:04 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-11-29 (163 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1828697/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 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 Desktop
Packages, which is subscribed to gnome-terminal 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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1795703] Re: Ubuntu Dock gets replaced with a standard GNOME one after a while
I get this quite regularly, thanks to the participants of this for the work around, very useful. But this is definitely still a problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1795703 Title: Ubuntu Dock gets replaced with a standard GNOME one after a while Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: I don't reboot my desktop and don't hibernate it, it just works for multiple days in a row without a reboot. I only turn off the monitor when I go out. Sometimes, after a while, when I turn on the monitor, Ubuntu's Dock is no longer there and what I get is the GNOME Dock which is hidden and can be seen by pressing "Super" (which shows all windows as well). This is annoying. Not sure if related, but here's what I've found in the journalctl logs: https://gist.github.com/k-bx/3a11b3ae34531a0dd2eb9cdaac97cf6c > JS ERROR: TypeError: this._workspaceIsolation is undefined ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell-extension-ubuntu-dock 0.9.1ubuntu18.04.1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 2 19:32:07 2018 InstallationDate: Installed on 2018-08-30 (32 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1795703/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 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 Desktop 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)
[Desktop-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 Desktop 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 1,
[Desktop-packages] [Bug 1858333] [NEW] Firefox sync not working, error in _fetchTokenForUser
Public bug reported: Following info from about:sync-log ``` 1578230581042 Sync.LogManager DEBUG Flushing file log 1578230581043 FirefoxAccounts DEBUG FxAccountsProfileClient: Requested profile 1578230581043 FirefoxAccounts DEBUG getOAuthToken enter 1578230581047 FirefoxAccounts TRACE getCachedToken returning cached token 1578230581047 FirefoxAccounts DEBUG getOAuthToken returning a cached token 1578230581049 Services.Common.RESTRequest DEBUG GET request to https://profile.accounts.firefox.com/v1/profile 1578230581057 Sync.LogManager DEBUG Log cleanup threshold time: 1577366581057 1578230581075 Sync.LogManager DEBUG Done deleting files. 1578230581790 Services.Common.RESTRequest DEBUG GET https://profile.accounts.firefox.com/v1/profile 304 1578231744394 FirefoxAccounts INFOPolling device commands. 1578231744395 Sync.ServiceDEBUG User-Agent: Firefox/71.0 (Linux x86_64) FxSync/1.73.0.20191205184924.desktop 1578231744395 Sync.ServiceINFOStarting sync at 2020-01-05 15:42:24 in browser session h18F_qHAu8gm 1578231744395 Sync.ServiceDEBUG In sync: should login. 1578231744395 Sync.ServiceINFOUser logged in successfully - verifying login. 1578231744396 Sync.BrowserIDManager DEBUG unlockAndVerifyAuthState already has (or can fetch) sync keys 1578231744396 Sync.Status DEBUG Status.login: error.login.reason.network => success.status_ok 1578231744396 Sync.Status DEBUG Status.service: error.login.failed => error.login.failed 1578231744396 Sync.ServiceDEBUG Fetching unlocked auth state returned success.status_ok 1578231744396 Sync.BrowserIDManager INFOGetting keys 1578231744396 FirefoxAccounts INFOMigrating kB to derived keys. 1578231744401 Services.Common.RESTRequest DEBUG GET request to https://api.accounts.firefox.com/v1/account/device/commands?index=0 1578231744402 Sync.BrowserIDManager ERROR Non-authentication error in _fetchTokenForUser: Error: Can't change uid(resource://gre/modules/FxAccountsStorage.jsm:227:13) JS Stack trace: updateaccountd...@fxaccountsstorage.jsm:227:13 1578231744402 Sync.Status DEBUG Status.login: success.status_ok => error.login.reason.network 1578231744402 Sync.Status DEBUG Status.service: error.login.failed => error.login.failed 1578231744402 Sync.BrowserIDManager INFOFailed to fetch the cluster URL: Error: Can't change uid(resource://gre/modules/FxAccountsStorage.jsm:227:13) JS Stack trace: updateaccountd...@fxaccountsstorage.jsm:227:13 1578231744403 Sync.ServiceDEBUG verifyLogin failed: Error: Can't change uid(resource://gre/modules/FxAccountsStorage.jsm:227:13) JS Stack trace: updateaccountd...@fxaccountsstorage.jsm:227:13 1578231744403 Sync.Status DEBUG Status.login: error.login.reason.network => error.login.reason.network 1578231744403 Sync.Status DEBUG Status.service: error.login.failed => error.login.failed 1578231744403 Sync.ErrorHandler ERROR Sync encountered a login error 1578231744403 Sync.SyncScheduler DEBUG Clearing sync triggers and the global score. 1578231744404 Sync.SyncScheduler DEBUG Next sync in 360 ms. (why=schedule) 1578231744405 Sync.ServiceDEBUG Exception calling WrappedLock: Error: Login failed: error.login.reason.network(resource://services-sync/service.js:1041:15) JS Stack trace: onnot...@service.js:1041:15 1578231744405 Sync.ServiceDEBUG Not syncing: login returned false. ``` ``` 15:51 $ lsb_release -rd Description:Ubuntu 18.04.3 LTS Release:18.04 ``` ``` 15:54 $ apt-cache policy firefox firefox: Installed: 71.0+build5-0ubuntu0.18.04.1 Candidate: 71.0+build5-0ubuntu0.18.04.1 Version table: *** 71.0+build5-0ubuntu0.18.04.1 500 500 http://il.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 59.0.2+build1-0ubuntu1 500 500 http://il.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ``` ** Affects: firefox (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1858333 Title: Firefox sync not working, error in _fetchTokenForUser Status in firefox package in Ubuntu: New Bug description: Following info from about:sync-log ``` 1578230581042 Sync.LogManager DEBUG Flushing file log 1578230581043 FirefoxAccounts DEBUG FxAccountsProfileClient: Requested profile 1578230581043 FirefoxAccounts DEBUG getOAuthToken enter 1578230581047 FirefoxAccounts TRACE getCachedToken returning cached token 1578230581047 FirefoxAccounts DEBUG getOAuthToken returning a cached token 1578230581049 Services.Common.RESTRequest DEBUG GET request to
[Desktop-packages] [Bug 1858332] [NEW] entire UI froze ctrl + alt +f2 no response
Public bug reported: Entire system froze only mouse moved left click no response right click no response keyboard not responding could not access terminal via ctrl + alt +f2 or ctrl + alt + sys rq etc. here's the video https://www.youtube.com/watch?v=byaYLD9zyMU ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 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 CurrentDesktop: ubuntu:GNOME Date: Sun Jan 5 15:22:24 2020 DisplayManager: gdm3 InstallationDate: Installed on 2015-08-23 (1595 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-10-23 (74 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1858332 Title: entire UI froze ctrl + alt +f2 no response Status in gnome-shell package in Ubuntu: New Bug description: Entire system froze only mouse moved left click no response right click no response keyboard not responding could not access terminal via ctrl + alt +f2 or ctrl + alt + sys rq etc. here's the video https://www.youtube.com/watch?v=byaYLD9zyMU ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 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 CurrentDesktop: ubuntu:GNOME Date: Sun Jan 5 15:22:24 2020 DisplayManager: gdm3 InstallationDate: Installed on 2015-08-23 (1595 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-10-23 (74 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1858332/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1294689] Re: Firefox doesn't use dolphin to open download directory
Using Kubuntu 19.10 with KDE 5.17 (via backports) with Firefox 71. This seems to be the case to me as well. Won't open Dolphin from download. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1294689 Title: Firefox doesn't use dolphin to open download directory Status in firefox package in Ubuntu: Confirmed Bug description: Under KDE, if from the download screen I ask to open the folder, I get a strange application, called files, to be spawned to browse the directory, instead of the more natural Dolphin. I am using Kubuntu. How to reproduce: 1. Start Firefox under KDE 2. Download any file from the Internet 3. Open the Download page 4. Within the downloaded file entry, click on the small "folder" icon on the right and wait a little bit Expected result: Dolphin file system browser to be started Actual result: A programm called "files" from GNOME environment is started. Most of the icons in the program are missing as I am running KDE from Kubuntu. This happens 100% of the times. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: firefox 28.0+build2-0ubuntu0.13.10.1 ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4 Uname: Linux 3.11.0-18-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: enzo 2229 F pulseaudio /dev/snd/controlC0: enzo 2229 F pulseaudio BuildID: 20140317233501 Channel: Unavailable Date: Wed Mar 19 15:33:07 2014 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2014-03-16 (3 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) IpRoute: default via 192.168.254.254 dev eth0 proto static 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 192.168.254.0/24 dev eth0 proto kernel scope link src 192.168.254.42 metric 1 IwConfig: eth0 no wireless extensions. lono wireless extensions. virbr0no wireless extensions. Locales: extensions.sqlite corrupt or missing MarkForUpload: True Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=28.0/20140317233501 (In use) RfKill: RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/06/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0803 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P6X58D-E dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0803:bd08/06/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6X58D-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1294689/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1853199] Re: Ctrl + c (copy) anywhere some times crashes gnome session
Crashed few times today and yesterday, /var/crash is empty :( -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1853199 Title: Ctrl + c (copy) anywhere some times crashes gnome session Status in gnome-shell package in Ubuntu: Incomplete Bug description: Copy text anwyhere (browser, terminal) crashes user session and shows login screen. It may take few login attempts to actually login back. I have HDMI Tv attached to a Shuttle pc with Intel graphics. Box is always ON but tv is ON amd OFF as needed. Every time I turn tv ON and try to do something and use ctrl + c it would restart gnome session. After login it seem to work fine and ctrl+c does not break anything. Then the next day the similar thing happens. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-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: Tue Nov 19 20:55:37 2019 DistUpgraded: 2019-10-26 19:58:25,451 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer HD Graphics 630 [1297:4057] InstallationDate: Installed on 2019-07-21 (121 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 05e3:0718 Genesys Logic, Inc. IDE/SATA Adapter Bus 001 Device 002: ID 413c:2107 Dell Computer Corp. Dell USB Entry Keyboard Bus 001 Device 003: ID 25a7:2402 2.4G 2.4G Wireless Device Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Shuttle Inc. XH270 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=UUID=381b92c2-4c86-47ab-a37b-6e1f7a708bf7 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-10-26 (24 days ago) dmi.bios.date: 01/09/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.02 dmi.board.asset.tag: Default string dmi.board.name: FH270 dmi.board.vendor: Shuttle Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.02:bd01/09/2018:svnShuttleInc.:pnXH270:pvr1.0:rvnShuttleInc.:rnFH270:rvr1.0:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: X dmi.product.name: XH270 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Shuttle 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/+source/gnome-shell/+bug/1853199/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1855736] Re: Duplicity fails to start
With version 0.8.09-0ubuntu0ppa1535-ubuntu19.10.1 (eoan) deja-dup now seems to start to work as a normal user, but I need to backup some root stuff, and when run under sudo or pkexec I get the following immediately: Traceback (innermost last): File "/usr/bin/duplicity", line 101, in with_tempdir(main) File "/usr/bin/duplicity", line 87, in with_tempdir fn() File "/usr/lib/python3/dist-packages/duplicity/dup_main.py", line 1525, in main action = commandline.ProcessCommandLine(sys.argv[1:]) File "/usr/lib/python3/dist-packages/duplicity/commandline.py", line 1172, in ProcessCommandLine globals.backend = backend.get_backend(args[0]) File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 225, in get_backend obj = get_backend_object(url_string) File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 211, in get_backend_object return factory(pu) File "/usr/lib/python3/dist-packages/duplicity/backends/giobackend.py", line 82, in __init__ ensure_dbus() File "/usr/lib/python3/dist-packages/duplicity/backends/giobackend.py", line 38, in ensure_dbus lines = output.decode(u'utf8').split(u'\n') AttributeError: 'str' object has no attribute 'decode' -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1855736 Title: Duplicity fails to start Status in Duplicity: Fix Committed Status in duplicity package in Ubuntu: Fix Committed Bug description: I am on 19.10. Duplicity crashes as soon as I try to start a backup, as below. It was running fine on 19.04. Traceback (innermost last): File "/usr/bin/duplicity", line 107, in with_tempdir(main) File "/usr/bin/duplicity", line 93, in with_tempdir fn() File "/usr/lib/python3/dist-packages/duplicity/dup_main.py", line 1522, in main action = commandline.ProcessCommandLine(sys.argv[1:]) File "/usr/lib/python3/dist-packages/duplicity/commandline.py", line 1200, in ProcessCommandLine globals.backend = backend.get_backend(args[0]) File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 225, in get_backend obj = get_backend_object(url_string) File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 211, in get_backend_object return factory(pu) File "/usr/lib/python3/dist-packages/duplicity/backends/giobackend.py", line 81, in __init__ ensure_dbus() File "/usr/lib/python3/dist-packages/duplicity/backends/giobackend.py", line 37, in ensure_dbus lines = output.split(u'\n') TypeError: a bytes-like object is required, not 'str' To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1855736/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1782703] Re: Unable to download updates from "extensions.gnome.org"
I also get this on a fresh install of Ubuntu 19.10 on one of the two machines I use (laptop with wifi is fine, desktop with wired connection is buggy, I used the same USB for install). My internet connection is fine, but some of the websites I want to get on are blocked (e.g. mobile banking, lastpass, etc.) on the affected desktop. I had minor issues on the laptop but changed them by switching the repositories. No such luck on the desktop. The network icon has a question mark over it, but when I open the network dialog, it says Wired Connected -1000Mb/s. I get this error message persistently in my Ubuntu Software: Unable to download updates from "extensions.gnome.org": failed to download https://extensions.gnome.org//static/extensions.json: Cannot resolve hostname I changed mirrors from local (cz) to general Ubuntu, installed gnome-extensions directly in terminal, ran sudo apt-get update&& sudo apt-get upgrade. All software is reported updated, but the error is persistent as well as the website blocking. Any ideas? Release:19.10 adela@bohumil-desktop:~$ apt-cache policy gnome-software gnome-software: Installed: 3.30.6-2ubuntu10.19.10.0 Candidate: 3.30.6-2ubuntu10.19.10.0 Version table: *** 3.30.6-2ubuntu10.19.10.0 500 500 http://archive.ubuntu.com/ubuntu eoan-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.30.6-2ubuntu10 500 500 http://archive.ubuntu.com/ubuntu eoan/main amd64 Packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1782703 Title: Unable to download updates from "extensions.gnome.org" Status in gnome-software package in Ubuntu: Confirmed Bug description: Occasionally, upon launching Ubuntu Software (GNOME Software), a small error popup appears noting that it is unable to download updates from extensions.gnome.org. The full message is as follows: # Unable to download updates from "extensions.gnome.org":[*/*/*/source /shell-extensions/*] failed to download https://extensions.gnome.org//static/extensions.json: Connection terminated unexpectedly This doesn't cause a crash of any sort, and doesn't seem to hamper any of the normal abilities of Ubuntu Software on the surface, but may have some other effects I am unaware of. `lsb_release -rd` is as follows: # Description:Ubuntu 18.04 LTS # Release:18.04 `apt-cache policy gnome-software` is as follows: # gnome-software: Installed: 3.28.1-0ubuntu4.18.04.1 Candidate: 3.28.1-0ubuntu4.18.04.1 Version table: *** 3.28.1-0ubuntu4.18.04.1 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.28.1-0ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Further system information is available here: https://paste.ubuntu.com/p/bbFnJNbRCy/ ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-software 3.28.1-0ubuntu4.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jul 19 23:07:23 2018 InstallationDate: Installed on 2018-07-20 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.28.1-0ubuntu4.18.04.1 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1782703/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
