[Touch-packages] [Bug 2018160] [NEW] gnome-shell crashes when top right panel touched on touchscreen
Public bug reported: Version: ubuntu 23.04 Package: gnome-shell: Installed: 44.0-2ubuntu3 Candidate: 44.0-2ubuntu3 Version table: *** 44.0-2ubuntu3 500 500 http://archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status What I expected: I expected the wifi/bluetooth/dark... menu (in the upper right hand corner) to popup when I touched it on my touchscreen (clicking with a mouse or touchpad works fine, touchscreen press does not). This works as intended on Ubuntu 22.04.2 LTS. What happened: The menu popped up as intended, but 2 seconds later it disappeared, along with the top gnome shell panel (presumably it crashed). A few seconds later the gnome panel restores but without the menu. Running applications (such as firefox) don't seem to be affected. Running on an Asus Vivobook 14 (touchscreen). Tried using both safe mode and proprietary graphic mode with same result. Earlier versions of gnome seem to work fine. Same problem happens in Fedora too. Willing to do additional testing. Really wanna get this working. Thanks ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CasperVersion: 1.480 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 29 18:06:49 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. TigerLake-LP GT2 [Iris Xe Graphics] [1043:13d2] LiveMediaBuild: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop TP470EA_TP470EA ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz nomodeset layerfs-path=minimal.standard.live.squashfs --- quiet splash SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: TP470EA.311 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: TP470EA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrTP470EA.311:bd07/22/2021:br5.19:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopTP470EA_TP470EA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP470EA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku: dmi.product.family: VivoBook Flip dmi.product.name: VivoBook_ASUSLaptop TP470EA_TP470EA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug crash lunar ubuntu ** Attachment added: "The panel when opened properly" https://bugs.launchpad.net/bugs/2018160/+attachment/5669663/+files/Screenshot%20from%202023-04-29%2018-31-58.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2018160 Title: gnome-shell crashes when top right panel touched on touchscreen Status in xorg package in Ubuntu: New Bug description: Version: ubuntu 23.04 Package: gnome-shell: Installed: 44.0-2ubuntu3 Candidate: 44.0-2ubuntu3 Version table: *** 44.0-2ubuntu3 500 500 http://archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status What I expected: I expected the wifi/bluetooth/dark... menu (in the upper right hand corner) to popup when I touched it on my touchscreen (clicking with a mouse or touchpad works fine, touchscreen press does not). This works as intended on Ubuntu 22.04.2 LTS. What happened: The menu popped up as intended, but 2 seconds later it disappeared, along with the top gnome shell panel (presumably it crashed). A few seconds later the gnome panel restores but without
[Touch-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
@61, yes. I had tried it and it works. It also has mSBC support - https://github.com/Arkq/bluez-alsa/issues/29, but the author himself admits that mSBC support is buggy and is not being developed. I could get it to work, but the audio was very choppy. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
@63 - your headset likely doesn't support mSBC (16 KHz), only CVSD (8KHz) in HFP/HSP mode. If that is the case, any fix - using a USB soundcard as you did, or a software fix (which this page is tracking) isn't gonna help. If it does support mSBC, 1Mii B10, and Avantree Leaf, Creative BT-W3 should be able to give decent quality audio. The definition of 'decent' varies of course. Most people in this age and time wouldn't be happy with 8 KHz (else, this page wouldn't exist), but mSBC is decent enough for most people, at least for typical voice calls. You can check the sampling frequency used very easily using Audacity > Record a few seconds using the mic in question > Analyze > Plot Spectrum. Note that Audacity plots in log scale for freq by default. If the highest freq component is just below 4 KHz, it is using CVSD @ 8 KHz sampling, and your headset is the likely culprit. If the highest component is 8 KHz, it is using mSBC @ 16 KHz. If you think that is not good enough, your options are limited. You can use FastStream (FS) which is supported only by a limited number of headsets, as well as by dongles such as Leaf, 1Mii B10, Creative BT-W2. No OS afaik supports it, so you can't use the dongle. Many devices have buggy implementations of FS. AptX LL also supposedly has bidirectional audio support, but the voiceback part is not supported by any device that I know of. ** Bug watch added: github.com/Arkq/bluez-alsa/issues #29 https://github.com/Arkq/bluez-alsa/issues/29 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions -- Mailing list: https://launchpad.net/~
[Touch-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
@ gyhor, I am pretty sure you got a faulty 1Mii B10. It doesnt get past enumeration, so it is not a compatibility issue. You also mention that it was tried on different systems and didn't work. Time to get it replaced. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
@ #47 Creative Labs BT-W3 supports mSBC (https://sg.creative.com/p/speakers/creative-bt-w3). I had checked with them before buying one. Tried pairing it with Jabra Talk 15, as well as Avantree Clipper Pro, and I can confirm that it works. Tried plotting the spectrum of the recorded audio using Audacity to confirm. Affirmative. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1574243] Re: Unable to adjust screen backlight on login screen on Macbook Pro (early 2015)
** Attachment removed: "CurrentDmesg.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1574243/+attachment/4645251/+files/CurrentDmesg.txt ** Attachment removed: "XorgLog.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1574243/+attachment/4645265/+files/XorgLog.txt ** Attachment removed: "XorgLogOld.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1574243/+attachment/4645266/+files/XorgLogOld.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1574243 Title: Unable to adjust screen backlight on login screen on Macbook Pro (early 2015) Status in xorg package in Ubuntu: New Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Fresh install of 16.04. 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center Don't know. The guide to identify the package told me all login screen issues were "LightDM". ubuntu-bug told me that package was not installed. 3) What you expected to happen To be able to adjust screen backlight brightness with the dedicated hardware buttons on the login screen, in order to be able log in. This works as expected whenever I'm logged in. 4) What happened instead I had to log in from an almost black login screen with no backlight. I believe this bug was present in 15.10 as well. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-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 CurrentDesktop: Unity Date: Sun Apr 24 13:58:00 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:162b] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Broadwell-U Integrated Graphics [106b:013f] InstallationDate: Installed on 2016-04-24 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Apple Inc. MacBookPro12,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed root=UUID=dd7fd213-44e3-45de-afe3-efd8c5825c1e ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/11/2016 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0167.B16.1602111810 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B16.1602111810:bd02/11/2016:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sun Apr 24 02:40:40 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 41002 vendor APP xserver.version: 2:1.18.3-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1574243/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1890202] Re: Xorg freeze
... Starting Restore /etc/resolv.conf if the system crashed before the ppp link was shut down... Starting System Logging Service... Starting Secure Boot updates for DB and DBX... Starting Snap Daemon... Starting Switcheroo Control Proxy service... Starting Login Service... Starting Thermal Daemon Service... Starting Disk Manager... Starting WPA supplicant... [ OK ] Finished Detect the available GPUs and deal with any system changes. [ OK ] Finished Restore /etc/resolv.conf if the system crashed before the ppp link was shut down. [ OK ] Finished GRUB failed boot detection. [ OK ] Started System Logging Service. [ OK ] Finished Secure Boot updates for DB and DBX. [ OK ] Finished Remove Stale Online ext4 Metadata Check Snapshots. [ OK ] Started Bluetooth service. [ OK ] Reached target Bluetooth. [ OK ] Started Avahi mDNS/DNS-SD Stack. [ OK ] Started Make remote CUPS printers available locally. [ OK ] Started WPA supplicant. [ OK ] Started Network Manager. [ OK ] Reached target Network. Starting Network Manager Wait Online... Starting OpenVPN service... Starting Permit User Sessions... [ OK ] Started Thermal Daemon Service. [ OK ] Finished OpenVPN service. [ OK ] Finished Permit User Sessions. [ OK ] Started Switcheroo Control Proxy service. Starting Save/Restore Sound Card State... Starting GNOME Display Manager... Starting Hold until boot process finishes up... [ OK ] Started IIO Sensor Proxy service. Starting Hostname Service... [ OK ] Finished Save/Restore Sound Card State. [ OK ] Reached target Sound Card. [ OK ] Started GNOME Display Manager. [ OK ] Started Authorization Manager. Starting Modem Manager... [ OK ] Started Accounts Service. [ OK ] Started Dispatcher daemon for systemd-networkd. [ OK ] Started Disk Manager. [ OK ] Started Modem Manager. [ OK ] Started Snap Daemon. Starting Wait until snapd is fully seeded... [ OK ] Started Hostname Service. Starting Network Manager Script Dispatcher Service... [ OK ] Started Network Manager Script Dispatcher Service. [ OK ] Started Login Service. [ OK ] Started Unattended Upgrades Shutdown. [ OK ] Started LSB: automatic crash report generation. [ OK ] Started LSB: Record successful boot for GRUB. [ OK ] Created slice User Slice of UID 125. Starting User Runtime Directory /run/user/125... [ OK ] Finished User Runtime Directory /run/user/125. Starting User Manager for UID 125... [ OK ] Started User Manager for UID 125. [ OK ] Started Session c1 of user gdm. Starting Daemon for power management... Starting RealtimeKit Scheduling Policy Service... [ OK ] Started RealtimeKit Scheduling Policy Service. [ OK ] Started Daemon for power management. Starting Locale Service... [ OK ] Started Locale Service. Starting Location Lookup Service... Starting PackageKit Daemon... [ OK ] Started Location Lookup Service. [ OK ] Started PackageKit Daemon. Starting Fingerprint Authentication Daemon... Mounting Mount unit for snapd, revision 7264... [ OK ] Started Fingerprint Authentication Daemon. [ OK ] Mounted Mount unit for snapd, revision 7264. Starting Manage, Install and Generate Color Profiles... [ OK ] Stopped Snap Daemon. Starting Snap Daemon... [ OK ] Started Snap Daemon. Mounting Mount unit for core18, revision 1705... [ OK ] Mounted Mount unit for core18, revision 1705. Mounting Mount unit for gnome-3-34-1804, revision 24... [ OK ] Mounted Mount unit for gnome-3-34-1804, revision 24. Mounting Mount unit for gtk-common-themes, revision 1506... [ OK ] Mounted Mount unit for gtk-common-themes, revision 1506. Mounting Mount unit for snap-store, revision 433... [ OK ] Mounted Mount unit for snap-store, revision 433. [ OK ] Finished Wait until snapd is fully seeded. [ OK ] Reached target Sleep. Starting Suspend... [ OK ] Finished Suspend. [ OK ] Stopped target Sleep. [ OK ] Reached target Suspend. [ OK ] Stopped target Suspend. Starting Network Manager Script Dispatcher Service... [ OK ] Started Network Manager Script Dispatcher Service. [ OK ] Reached target Sleep. Starting Suspend... Mon Aug 03 17:11:51 EDT 2020 [ OK ] Started Show Plymouth Boot Screen. [ OK ] Started Forward Password Requests to Plymouth Directory Watch. [ OK ] Reached target Local Encrypted Volumes. [ OK ] Mounted Mount unit for core18, revision 1705. [ OK ] Mounted Mount unit for gnome-3-34-1804, revision 24. [ OK ] Mounted Mount unit for snap-store, revision 433. [ OK ] Mounted Mount unit for snapd, revision 7264. [ OK ] Mounted Mount unit for gtk-common-themes, revision 1506. [ OK ] Started Journal Service
[Touch-packages] [Bug 1890202] [NEW] Xorg freeze
Public bug reported: Plymouth never returns from startup. Startup takes intermittently long periods of time. someuser@someuser-l01:~$ systemd-analyze blame | cat 25.226s accounts-daemon.service 25.173s udisks2.service 25.150s gpu-manager.service 25.149s networkd-dispatcher.service 25.129s snapd.service 25.125s systemd-logind.service 25.092s ModemManager.service 25.079s iio-sensor-proxy.service 3.787s plymouth-quit-wait.service 1.856s upower.service 427ms dev-nvme0n1p2.device 356ms dev-loop1.device 350ms dev-loop2.device 313ms dev-loop3.device 312ms dev-loop4.device 229ms systemd-resolved.service 207ms systemd-rfkill.service 168ms rtkit-daemon.service 132ms snap-snap\x2dstore-433.mount 131ms snap-snapd-7264.mount 130ms snap-gtk\x2dcommon\x2dthemes-1506.mount 115ms systemd-timesyncd.service 114ms avahi-daemon.service 96ms polkit.service 94ms snap-core18-1705.mount 93ms snap-gnome\x2d3\x2d34\x2d1804-24.mount 92ms apport.service 92ms systemd-udev-trigger.service 90ms e2scrub_reap.service 84ms dev-loop0.device 75ms systemd-journald.service 73ms switcheroo-control.service 71ms user@1000.service 70ms swapfile.swap 69ms keyboard-setup.service 68ms thermald.service 68ms grub-common.service 67ms wpa_supplicant.service 63ms user@125.service 57ms systemd-udevd.service 46ms kerneloops.service 43ms apparmor.service 41ms grub-initrd-fallback.service 41ms alsa-restore.service 41ms rsyslog.service 37ms secureboot-db.service 35ms systemd-journal-flush.service 35ms systemd-fsck@dev-disk-by\x2duuid-9979\x2d84D8.service 33ms openvpn.service 33ms snapd.seeded.service 32ms systemd-backlight@backlight:intel_backlight.service 32ms systemd-backlight@leds:dell::kbd_backlight.service 31ms systemd-update-utmp-runlevel.service 30ms bluetooth.service 30ms systemd-user-sessions.service 29ms gdm.service 29ms snapd.apparmor.service 28ms packagekit.service 27ms plymouth-start.service 25ms pppd-dns.service 25ms systemd-tmpfiles-setup.service 20ms systemd-modules-load.service 20ms NetworkManager.service 15ms colord.service 12ms plymouth-read-write.service 10ms modprobe@drm.service 10ms dev-hugepages.mount 9ms setvtrgb.service 9ms systemd-sysctl.service 9ms dev-mqueue.mount 9ms systemd-random-seed.service 9ms systemd-sysusers.service 9ms systemd-tmpfiles-setup-dev.service 9ms sys-kernel-debug.mount 8ms boot-efi.mount 8ms sys-kernel-tracing.mount 8ms user-runtime-dir@1000.service 8ms systemd-remount-fs.service 8ms systemd-update-utmp.service 7ms user-runtime-dir@125.service 6ms kmod-static-nodes.service 6ms console-setup.service 3ms sys-fs-fuse-connections.mount 3ms sys-kernel-config.mount 2ms ufw.service 1ms snapd.socket Only able to boot if I interrupt plymouth, and manually wait out systemd targets. When booted with multiple screens, constant graphical corruption and distortion is seen. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Aug 3 17:28:16 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 630 [1028:080d] Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Polaris 22 XL [Radeon RX Vega M GL] [1002:694e] InstallationDate: Installed on 2020-08-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. XPS 15 9575 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.4.0-42-generic root=UUID=ea1ef229-ef86-4657-909b-498914de360e ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/10/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 0C32VW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd10/10/2018:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 vers
[Touch-packages] [Bug 1576559] Re: Refused to switch profile to headset_head_unit: Not connected
Have the same issue in Ubuntu 18.04.2 LTS. In pavucontrol or in blueman-applet: If select A2DP sound works; If select HSP/HFP sound/mic do not work. bluetoothctl output: Name: Jabra Elite 65t Alias: Jabra Elite 65t Class: 0x00240404 Icon: audio-card Paired: yes Trusted: yes Blocked: no Connected: yes LegacyPairing: no UUID: Vendor specific (-deca-fade-deca-deafdecacaff) UUID: Serial Port (1101--1000-8000-00805f9b34fb) UUID: Headset (1108--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: Handsfree (111e--1000-8000-00805f9b34fb) UUID: Phonebook Access Server (112f--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) Modalias: bluetooth:v0067p247Ed020E -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1576559 Title: Refused to switch profile to headset_head_unit: Not connected Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm trying to connect a bluetooth-speaker-with-microphone (Mi Bluetooth Speaker) to Ubuntu. It works well as an A2DP sync, but can't use it as a headset with microphone. The device doesn't list in the "Input Devices" by default, and using the sound settings to change the profile of the device to HSP/HFP results in this log message: W: [pulseaudio] module-bluez5-device.c: Refused to switch profile to headset_head_unit: Not connected I'm running Ubuntu 16.04 LTS. I did an upgrade from Ubuntu 15.10. pulseaudio: Installed: 1:8.0-0ubuntu3 bluez: Installed: 5.37-0ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1576559/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 938751] Re: Images are washed out or colors are skewed in some apps
EOG also applies fullscreen profiles to image! Notice most of preinstalled color profiles in Settings->Devices->Color does not support whole screen correction (they are marked with bulb icon). So this is normal application behavior to apply system-wide color profile to image. But when fullscreen profile selected, it used firstly in EOG for certain image and secondly by the system for final correction. In my case screen has noticeable bluish cast, so ICC does significant color shift to compensate it. But when applied twice, it makes images yellowish in EOG. While Gimp and Shotwell display colors correctly. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/938751 Title: Images are washed out or colors are skewed in some apps Status in Eye of GNOME: New Status in chromium-browser package in Ubuntu: Confirmed Status in colord package in Ubuntu: Confirmed Status in eog package in Ubuntu: Confirmed Bug description: Images are washed out or colors are skewed in some apps, notably Chrome/Chromium and Image Viewer (eog). Workaround: Settings > Devices > Colour > and disable or remove your monitor's colour profile To manage notifications about this bug go to: https://bugs.launchpad.net/eog/+bug/938751/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1825761] Re: package systemd:i386 229-4ubuntu21.21 failed to install/upgrade: el subproceso instalado el script pre-removal devolvió el código de salida de error 1
Yes. Although the truth is that I have already managed to install the 64-bit version of systemd. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1825761 Title: package systemd:i386 229-4ubuntu21.21 failed to install/upgrade: el subproceso instalado el script pre-removal devolvió el código de salida de error 1 Status in systemd package in Ubuntu: Incomplete Bug description: Crossgrade ProblemType: Package DistroRelease: Ubuntu 16.04 Package: systemd:i386 229-4ubuntu21.21 ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Sun Apr 21 05:37:04 2019 DpkgTerminalLog: Desinstalando systemd:i386 (229-4ubuntu21.21) ... systemd is the active init system, please switch to another before removing systemd. dpkg: error al procesar el paquete systemd:i386 (--remove): el subproceso instalado el script pre-removal devolvió el código de salida de error 1 ErrorMessage: el subproceso instalado el script pre-removal devolvió el código de salida de error 1 InstallationDate: Installed on 2015-03-04 (1509 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) PackageArchitecture: i386 RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.31 SourcePackage: systemd Title: package systemd:i386 229-4ubuntu21.21 failed to install/upgrade: el subproceso instalado el script pre-removal devolvió el código de salida de error 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1825761/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1825761] [NEW] package systemd:i386 229-4ubuntu21.21 failed to install/upgrade: el subproceso instalado el script pre-removal devolvió el código de salida de error 1
Public bug reported: Crossgrade ProblemType: Package DistroRelease: Ubuntu 16.04 Package: systemd:i386 229-4ubuntu21.21 ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Sun Apr 21 05:37:04 2019 DpkgTerminalLog: Desinstalando systemd:i386 (229-4ubuntu21.21) ... systemd is the active init system, please switch to another before removing systemd. dpkg: error al procesar el paquete systemd:i386 (--remove): el subproceso instalado el script pre-removal devolvió el código de salida de error 1 ErrorMessage: el subproceso instalado el script pre-removal devolvió el código de salida de error 1 InstallationDate: Installed on 2015-03-04 (1509 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) PackageArchitecture: i386 RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.31 SourcePackage: systemd Title: package systemd:i386 229-4ubuntu21.21 failed to install/upgrade: el subproceso instalado el script pre-removal devolvió el código de salida de error 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1825761 Title: package systemd:i386 229-4ubuntu21.21 failed to install/upgrade: el subproceso instalado el script pre-removal devolvió el código de salida de error 1 Status in systemd package in Ubuntu: New Bug description: Crossgrade ProblemType: Package DistroRelease: Ubuntu 16.04 Package: systemd:i386 229-4ubuntu21.21 ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Sun Apr 21 05:37:04 2019 DpkgTerminalLog: Desinstalando systemd:i386 (229-4ubuntu21.21) ... systemd is the active init system, please switch to another before removing systemd. dpkg: error al procesar el paquete systemd:i386 (--remove): el subproceso instalado el script pre-removal devolvió el código de salida de error 1 ErrorMessage: el subproceso instalado el script pre-removal devolvió el código de salida de error 1 InstallationDate: Installed on 2015-03-04 (1509 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) PackageArchitecture: i386 RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.31 SourcePackage: systemd Title: package systemd:i386 229-4ubuntu21.21 failed to install/upgrade: el subproceso instalado el script pre-removal devolvió el código de salida de error 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1825761/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1825763] [NEW] package coreutils:i386 (not installed) failed to install/upgrade: el subproceso instalado el script post-removal devolvió el código de salida de error 127
Public bug reported: Crossgrade ProblemType: Package DistroRelease: Ubuntu 16.04 Package: coreutils:i386 (not installed) ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Sun Apr 21 18:02:47 2019 DpkgTerminalLog: Desinstalando coreutils:i386 (8.25-2ubuntu3~16.04) ... /var/lib/dpkg/info/coreutils.postrm: 5: /var/lib/dpkg/info/coreutils.postrm: rm: not found dpkg: error al procesar el paquete coreutils:i386 (--remove): el subproceso instalado el script post-removal devolvió el código de salida de error 127 ErrorMessage: el subproceso instalado el script post-removal devolvió el código de salida de error 127 InstallationDate: Installed on 2015-03-04 (1509 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.31 SourcePackage: coreutils Title: package coreutils:i386 (not installed) failed to install/upgrade: el subproceso instalado el script post-removal devolvió el código de salida de error 127 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: coreutils (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1825763 Title: package coreutils:i386 (not installed) failed to install/upgrade: el subproceso instalado el script post-removal devolvió el código de salida de error 127 Status in coreutils package in Ubuntu: New Bug description: Crossgrade ProblemType: Package DistroRelease: Ubuntu 16.04 Package: coreutils:i386 (not installed) ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Sun Apr 21 18:02:47 2019 DpkgTerminalLog: Desinstalando coreutils:i386 (8.25-2ubuntu3~16.04) ... /var/lib/dpkg/info/coreutils.postrm: 5: /var/lib/dpkg/info/coreutils.postrm: rm: not found dpkg: error al procesar el paquete coreutils:i386 (--remove): el subproceso instalado el script post-removal devolvió el código de salida de error 127 ErrorMessage: el subproceso instalado el script post-removal devolvió el código de salida de error 127 InstallationDate: Installed on 2015-03-04 (1509 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.31 SourcePackage: coreutils Title: package coreutils:i386 (not installed) failed to install/upgrade: el subproceso instalado el script post-removal devolvió el código de salida de error 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1825763/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1759836] Re: systemd-udevd consumes 100% of CPU
Do you see lines like the next one in your journal? systemd-udevd[512]: Process 'hid2hci --method=dell --devpath=/devices/pci:00/:00:1a.0/usb3/3-1/3-1.2/3-1.2:1.0' failed with exit code 1. I count more than 200 of that line per second in the journal and my Dell Inspiron (older model) registers temperatures of over 100C! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1759836 Title: systemd-udevd consumes 100% of CPU Status in systemd package in Ubuntu: Confirmed Bug description: The systemd-udevd proccess consumes 100% of a thread everytime, but i'm not noticing any difference in my computer. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 29 08:52:54 2018 InstallationDate: Installed on 2018-03-05 (23 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304) MachineType: Dell Inc. Inspiron N5010 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 08R0GW dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A12 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12: dmi.product.name: Inspiron N5010 dmi.product.version: A12 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1759836/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1561278] Re: internal sound card not detected HP X2
alsa-info output: http://www.alsa- project.org/db/?f=12cbba27e12cc27ede2a9934df4f3a1ce12ff545 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1561278 Title: internal sound card not detected HP X2 Status in alsa-driver package in Ubuntu: Confirmed Bug description: HP Pavilion X2 - No sound card detected. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Wed Mar 23 18:18:32 2016 InstallationDate: Installed on 2016-03-18 (5 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/11/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 813E dmi.board.vendor: HP dmi.board.version: 34.10 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.04:bd09/11/2015:svnHP:pnHPPavilionx2Detachable:pvrType1ProductConfigId:rvnHP:rn813E:rvr34.10:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion x2 Detachable dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1561278/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1561278] Re: internal sound card not detected HP X2
Have the same issue with Ubuntu 17.10 $ uname -a Linux raiaHPx2 4.13.0-39-generic #44-Ubuntu SMP Thu Apr 5 14:25:01 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux "aplay -l" gives the following $aplay -l List of PLAYBACK Hardware Devices card 0: Audio [Intel HDMI/DP LPE Audio], device 0: HdmiLpeAudio [Intel HDMI/DP LPE Audio] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: Audio [Intel HDMI/DP LPE Audio], device 1: HdmiLpeAudio [Intel HDMI/DP LPE Audio] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: Audio [Intel HDMI/DP LPE Audio], device 2: HdmiLpeAudio [Intel HDMI/DP LPE Audio] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: bytcrrt5640 [bytcr-rt5640], device 0: Baytrail Audio (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: bytcrrt5640 [bytcr-rt5640], device 1: Deep-Buffer Audio (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 Attempted to solve with following the directions here with dkms https://wiki.ubuntu.com/Audio/UpgradingAlsa/DKMS but did not fix the no sound issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1561278 Title: internal sound card not detected HP X2 Status in alsa-driver package in Ubuntu: Confirmed Bug description: HP Pavilion X2 - No sound card detected. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Wed Mar 23 18:18:32 2016 InstallationDate: Installed on 2016-03-18 (5 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/11/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 813E dmi.board.vendor: HP dmi.board.version: 34.10 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.04:bd09/11/2015:svnHP:pnHPPavilionx2Detachable:pvrType1ProductConfigId:rvnHP:rn813E:rvr34.10:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion x2 Detachable dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1561278/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1720519] Re: KDE/Kubuntu: Module "module-switch-on-connect" should be loaded once at most. Refusing to load.
After upgrading from 17.04 to 17.10 I also had this issue with error: > pulseaudio[6267]: Module "module-switch-on-connect" should be loaded once at most. Refusing to load. Fixed like in #4 by commenting load-module module-switch-on-connect out of /etc/pulse/default.pa Have not tried any plug-in-devices to see if this fix affects their usage. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1720519 Title: KDE/Kubuntu: Module "module-switch-on-connect" should be loaded once at most. Refusing to load. Status in PulseAudio: Confirmed Status in pulseaudio package in Ubuntu: Triaged Bug description: Pulseaudio daemon does not start after the update to Kubuntu 17.10 beta2, because the module fails to load although it is there. From 'pulseaudio -vv' E: [pulseaudio] module.c: Module "module-switch-on-connect" should be loaded once at most. Refusing to load. E: [pulseaudio] main.c: Module load failed. E: [pulseaudio] main.c: Failed to initialize daemon. PS sorry I am not a seasoned bug reporter. Let me know if I can provide more info. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: ben2809 F...m chrome /dev/snd/controlC0: ben2809 F chrome /dev/snd/timer: ben2809 f chrome CurrentDesktop: KDE Date: Sat Sep 30 11:20:55 2017 InstallationDate: Installed on 2017-04-07 (175 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to artful on 2017-09-30 (0 days ago) dmi.bios.date: 10/29/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: B150M-ITX dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd10/29/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1720519/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1731674] [NEW] Can't rotate the screen
Public bug reported: I have recently installed Ubuntu 17.10. After I logged in, the screen rotated sideways. I tried "xrandr -o normal", but it didn't work. What should I do? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Nov 11 19:44:03 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-11 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Hewlett-Packard HP Pavilion 17 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/19/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.43 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 22C7 dmi.board.vendor: Hewlett-Packard dmi.board.version: 90.41 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.43:bd08/19/2015:svnHewlett-Packard:pnHPPavilion17NotebookPC:pvr096E100800405F0620180:rvnHewlett-Packard:rn22C7:rvr90.41:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion 17 Notebook PC dmi.product.version: 096E100800405F0620180 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful ubuntu wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1731674 Title: Can't rotate the screen Status in xorg package in Ubuntu: New Bug description: I have recently installed Ubuntu 17.10. After I logged in, the screen rotated sideways. I tried "xrandr -o normal", but it didn't work. What should I do? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Nov 11 19:44:03 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-11 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Hewlett-Packard HP Pavilion 17 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/19/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.43 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 22C7 dmi.board.vendor: Hewlett-Packard dmi.board.version: 90.41 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.43:bd08/19/2015:svnHewlett-Packard:pnHPPavilion17NotebookPC:pvr096E100800405F0620180:rvnHewlett-Packard:rn22C7:rvr90.41:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion 17 Notebook PC dmi.product.version: 096E100800405F0620180 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 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/+source/xorg/+bug/1731674/+subscriptions -- Mailing
[Touch-packages] [Bug 1577197] Re: Pulseaudio bluez5-util.c: TryAcquire() failed - Operation Not Authorized
confirm issue on UBUNTU 16.04 with pulseaudio 8.0 Vahid Mardani's script is a valid temporary workaround by running it every time the bug appear -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1577197 Title: Pulseaudio bluez5-util.c: TryAcquire() failed - Operation Not Authorized Status in bluez package in Ubuntu: Confirmed Status in indicator-sound package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Confirmed Bug description: Pulseaudio outright stops audio via Bluetooth after sleep or prolonged period of time. Only restart fixes the issue. This started early 2016 in 15.10. Issue is discussed here as well http://askubuntu.com/questions/763539/bluetooth-speaker-no-sound-in-ubuntu-16-04 and mentioned in other unrelated bugs. Ubuntu Xenial 16.04 LTS The log below: May 1 17:18:07 jalexoidmobile pulseaudio[2884]: [pulseaudio] module-bluez5-device.c: Default profile not connected, selecting off profile May 1 17:18:07 jalexoidmobile bluetoothd[7349]: /org/bluez/hci0/dev_00_02_3C_05_99_F2/fd4: fd(35) ready May 1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Supervising 3 threads of 1 processes of 1 users. May 1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Successfully made thread 10967 of process 2884 (n/a) owned by '1000' RT at priority 5. May 1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Supervising 4 threads of 1 processes of 1 users. May 1 17:18:07 jalexoidmobile pulseaudio[2884]: [pulseaudio] bluez5-util.c: Transport TryAcquire() failed for transport /org/bluez/hci0/dev_00_02_3C_05_99_F2/fd4 (Operation Not Authorized) May 1 17:18:07 jalexoidmobile kernel: [20583.032442] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input24 May 1 17:18:19 jalexoidmobile pulseaudio[2884]: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 006: ID 04f2:b2da Chicony Electronics Co., Ltd thinkpad t430s camera Bus 001 Device 008: ID 0a5c:21e6 Broadcom Corp. BCM20702 Bluetooth 4.0 [ThinkPad] Bus 001 Device 004: ID 147e:2020 Upek TouchChip Fingerprint Coprocessor (WBF advanced mode) Bus 001 Device 003: ID 17ef:1003 Lenovo Integrated Smart Card Reader Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub [20388.983474] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [20389.070114] usb 1-1.4: New USB device found, idVendor=0a5c, idProduct=21e6 [20389.070120] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [20389.070122] usb 1-1.4: Product: BCM20702A0 [20389.070124] usb 1-1.4: Manufacturer: Broadcom Corp [20389.070126] usb 1-1.4: SerialNumber: 446D578686DD [20389.076232] Bluetooth: hci0: BCM: chip id 63 [20389.092220] Bluetooth: hci0: BCM20702A [20389.093225] Bluetooth: hci0: BCM20702A1 (001.002.014) build [20389.551476] wlan0: authenticate with a0:63:91:2f:3f:ed [20389.554391] wlan0: send auth to a0:63:91:2f:3f:ed (try 1/3) [20389.557790] wlan0: authenticated [20389.558339] wlan0: associate with a0:63:91:2f:3f:ed (try 1/3) [20389.562209] wlan0: RX AssocResp from a0:63:91:2f:3f:ed (capab=0x1411 status=0 aid=2) [20389.581260] wlan0: associated [20389.581369] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [20389.830185] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1669 [20389.846186] Bluetooth: hci0: Broadcom Bluetooth Device [20418.269466] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input23 [20583.032442] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input24 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1577197/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1574120] Re: Notebook doesn't suspend when lid is closed after update to 16.04
confirmed "HandleLidSwitchDocked=suspend" worked for me. hp pavilion g6 Close lid, suspended and opening lid unsuspended automatially. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1574120 Title: Notebook doesn't suspend when lid is closed after update to 16.04 Status in systemd package in Ubuntu: Confirmed Bug description: My notebook does not suspend after upgrading from 15.10 to 16.04. According to system settings the notebook should suspend when lid is closed but actually this does not happen. Instead it continues to run as if nothing had happened. With the previous versions of ubuntu (14.04-15.10) everything worked fine. My System: HP Pavilion dv7. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: acpi (not installed) ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Apr 23 23:11:15 2016 InstallationDate: Installed on 2015-10-29 (176 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: acpi UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1574120/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1547196] Re: Removal of revert_scalable_fonts_metric.patch causes ugliness in Claws-Mail
Same in Eclipse. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to freetype in Ubuntu. https://bugs.launchpad.net/bugs/1547196 Title: Removal of revert_scalable_fonts_metric.patch causes ugliness in Claws-Mail Status in freetype package in Ubuntu: Confirmed Status in freetype package in Debian: New Bug description: This is mostly a tracking bug for this discussion on ubuntu-devel: https://lists.ubuntu.com/archives/ubuntu- devel/2016-February/039224.html The following precise-era patch was recently removed from freetype: http://bazaar.launchpad.net/~ubuntu- branches/ubuntu/wily/freetype/wily/view/head:/debian/patches- freetype/revert_scalable_fonts_metric.patch which caused a number of visual effects in various applications. In Emacs, the lines get vertically closer so that more lines are visible on screen. This is subtle and doesn't look too bad otherwise. However, in Claws-Mail several negative effects were noticed. The lines in the Summary window are more squished together and the characters appear squished too. This is with Sans 10 font. This is less readable. In the Message window it's worse. There I use Ubuntu Mono 14. The problem isn't the vertical spacing, but the horizontal spacing. Now there is more space between characters and that actually makes the window less readable. I will contact the upstream Claws mailing list to see if they have any thoughts. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libfreetype6 2.6.1-0.1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1 Uname: Linux 4.4.0-6-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Thu Feb 18 14:34:57 2016 Dependencies: gcc-6-base 6-20160217-0ubuntu1 libc6 2.21-0ubuntu6 libgcc1 1:6-20160217-0ubuntu1 libpng12-0 1.2.54-1ubuntu1 zlib1g 1:1.2.8.dfsg-2ubuntu4 EcryptfsInUse: Yes InstallationDate: Installed on 2016-01-22 (27 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117) SourcePackage: freetype UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freetype/+bug/1547196/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1589046] Re: Monospace font scaling changed between 15.10 and 16.04
Hard to say, applying back revert_scalable_fonts_metric.patch is helping, but it still is different than 15.10... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-dejavu in Ubuntu. https://bugs.launchpad.net/bugs/1589046 Title: Monospace font scaling changed between 15.10 and 16.04 Status in fonts-dejavu package in Ubuntu: Confirmed Bug description: Verified booting system from live CD. Scaling of monospace font(or window with monospace font inside) has changed. In 16.04 the same monospace fond is smaller - visible in geany and Eclipse (see screenshot). Font is DejavuSansMono 10 (default ubuntu monospace font) in both cases . I think the scaling of same font should not change. Here you can find the screenshots: http://askubuntu.com/questions/781430/font-or-windows-scaling-changed-between-15-10-and-16-04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-dejavu/+bug/1589046/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1547374] Re: "Monospace Regular 8" became wider
I believe this is the same problem: https://bugs.launchpad.net/ubuntu/+source/fonts-dejavu/+bug/1589046 For me disable font hinting did not make font looks same as in 15.10. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1547374 Title: "Monospace Regular 8" became wider Status in fontconfig package in Ubuntu: Confirmed Bug description: I've been using gnome-terminal with "Monospace Regular 8" for years, which always had a 6x13 px font size (the same size as xterm, just nicer antialiasing). With yesterday's update in Xenial, it became wider: 7x13 px each cell (and less pleasing to my eyes). The neighbor sizes "Monospace Regular 7" is 5px wide, "Monospace Regular 9" is 7px wide just as "Monospace Regular 8", only taller. So it doesn't make sense for me for "Monospace Regular 8" to be 7px wide instead of 6px in between the two neighboring sizes as it used to be. (No clue which package is the culprit, sorry.) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: fontconfig 2.11.1-0ubuntu7 ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1 Uname: Linux 4.4.0-6-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Fri Feb 19 09:11:41 2016 InstallationDate: Installed on 2012-05-30 (1359 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) SourcePackage: fontconfig UpgradeStatus: Upgraded to xenial on 2016-02-13 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1547374/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1589046] Re: Monospace font scaling changed between 15.10 and 16.04
Any update on this, or maybe only I am affected with that? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-dejavu in Ubuntu. https://bugs.launchpad.net/bugs/1589046 Title: Monospace font scaling changed between 15.10 and 16.04 Status in fonts-dejavu package in Ubuntu: New Bug description: Verified booting system from live CD. Scaling of monospace font(or window with monospace font inside) has changed. In 16.04 the same monospace fond is smaller - visible in geany and Eclipse (see screenshot). Font is DejavuSansMono 10 (default ubuntu monospace font) in both cases . I think the scaling of same font should not change. Here you can find the screenshots: http://askubuntu.com/questions/781430/font-or-windows-scaling-changed-between-15-10-and-16-04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-dejavu/+bug/1589046/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1589046] Re: Monospace font scaling changed between 15.10 and 16.04
Maybe this is the same: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1547374 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-dejavu in Ubuntu. https://bugs.launchpad.net/bugs/1589046 Title: Monospace font scaling changed between 15.10 and 16.04 Status in fonts-dejavu package in Ubuntu: New Bug description: Verified booting system from live CD. Scaling of monospace font(or window with monospace font inside) has changed. In 16.04 the same monospace fond is smaller - visible in geany and Eclipse (see screenshot). Font is DejavuSansMono 10 (default ubuntu monospace font) in both cases . I think the scaling of same font should not change. Here you can find the screenshots: http://askubuntu.com/questions/781430/font-or-windows-scaling-changed-between-15-10-and-16-04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-dejavu/+bug/1589046/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1589046] Re: Monospace font scaling changed between 15.10 and 16.04
** Package changed: ubuntu => fonts-dejavu (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-dejavu in Ubuntu. https://bugs.launchpad.net/bugs/1589046 Title: Monospace font scaling changed between 15.10 and 16.04 Status in fonts-dejavu package in Ubuntu: New Bug description: Verified booting system from live CD. Scaling of monospace font(or window with monospace font inside) has changed. In 16.04 the same monospace fond is smaller - visible in geany and Eclipse (see screenshot). Font is DejavuSansMono 10 (default ubuntu monospace font) in both cases . I think the scaling of same font should not change. Here you can find the screenshots: http://askubuntu.com/questions/781430/font-or-windows-scaling-changed-between-15-10-and-16-04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-dejavu/+bug/1589046/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1540088] Re: NetworkManager crashes after upgrade, preventing nm-applet to show
great, i confirm that workaround worked for me, thanks -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1540088 Title: NetworkManager crashes after upgrade, preventing nm-applet to show Status in network-manager package in Ubuntu: Confirmed Bug description: After the last upgrade of Ubuntu 14.04.3 LTS , NetworkManager keeps crashing. after `sudo service network-manager start` I get the following output in dmesg: [2016-01-31 14:28:47] traps: NetworkManager[11040] general protection ip:469fee sp:7ffc6879aa00 error:0 in NetworkManager[40+10d000] [2016-01-31 14:28:47] init: network-manager main process (11040) killed by SEGV signal [2016-01-31 14:28:47] init: network-manager main process ended, respawning [2016-01-31 14:28:47] traps: NetworkManager[11049] general protection ip:469fee sp:7ffecca7d9d0 error:0 in NetworkManager[40+10d000] [2016-01-31 14:28:47] init: network-manager main process (11049) killed by SEGV signal [2016-01-31 14:28:47] init: network-manager main process ended, respawning [2016-01-31 14:28:47] traps: NetworkManager[11062] general protection ip:469fee sp:7ffc218a9f50 error:0 in NetworkManager[40+10d000] [2016-01-31 14:28:47] init: network-manager main process (11062) killed by SEGV signal [2016-01-31 14:28:47] init: network-manager main process ended, respawning [2016-01-31 14:28:47] traps: NetworkManager[11076] general protection ip:469fee sp:7fff7f128270 error:0 in NetworkManager[40+10d000] [2016-01-31 14:28:47] init: network-manager main process (11076) killed by SEGV signal [2016-01-31 14:28:47] init: network-manager main process ended, respawning [2016-01-31 14:28:47] traps: NetworkManager[11088] general protection ip:469fee sp:7fff66528f90 error:0 in NetworkManager[40+10d000] [2016-01-31 14:28:47] init: network-manager main process (11088) killed by SEGV signal [2016-01-31 14:28:47] init: network-manager main process ended, respawning [2016-01-31 14:28:47] traps: NetworkManager[11092] general protection ip:469fee sp:7fffab819070 error:0 in NetworkManager[40+10d000] [2016-01-31 14:28:47] init: network-manager main process (11092) killed by SEGV signal [2016-01-31 14:28:47] init: network-manager main process ended, respawning [2016-01-31 14:28:47] traps: NetworkManager[11096] general protection ip:469fee sp:7ffe7aa91c20 error:0 in NetworkManager[40+10d000] [2016-01-31 14:28:47] init: network-manager main process (11096) killed by SEGV signal [2016-01-31 14:28:47] init: network-manager main process ended, respawning [2016-01-31 14:28:47] traps: NetworkManager[11100] general protection ip:469fee sp:7ffedfe81460 error:0 in NetworkManager[40+10d000] [2016-01-31 14:28:47] init: network-manager main process (11100) killed by SEGV signal [2016-01-31 14:28:47] init: network-manager main process ended, respawning [2016-01-31 14:28:47] traps: NetworkManager[11104] general protection ip:469fee sp:7ffdc475f140 error:0 in NetworkManager[40+10d000] [2016-01-31 14:28:47] init: network-manager main process (11104) killed by SEGV signal [2016-01-31 14:28:47] init: network-manager main process ended, respawning [2016-01-31 14:28:47] traps: NetworkManager[11108] general protection ip:469fee sp:7ffdeb437010 error:0 in NetworkManager[40+10d000] [2016-01-31 14:28:47] init: network-manager main process (11108) killed by SEGV signal [2016-01-31 14:28:47] init: network-manager main process ended, respawning [2016-01-31 14:28:47] init: network-manager main process (2) killed by SEGV signal [2016-01-31 14:28:47] init: network-manager respawning too fast, stopped This problem prevents me to see nm-applet, and makes me unable to connect to WiFi network. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1540088/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1540088] Re: NetworkManager crashes after upgrade, preventing nm-applet to show
yes, manually like in 2004... i'm having a bad time explaining this to my little daughter -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1540088 Title: NetworkManager crashes after upgrade, preventing nm-applet to show Status in network-manager package in Ubuntu: Confirmed Bug description: After the last upgrade of Ubuntu 14.04.3 LTS , NetworkManager keeps crashing. after `sudo service network-manager start` I get the following output in dmesg: [2016-01-31 14:28:47] traps: NetworkManager[11040] general protection ip:469fee sp:7ffc6879aa00 error:0 in NetworkManager[40+10d000] [2016-01-31 14:28:47] init: network-manager main process (11040) killed by SEGV signal [2016-01-31 14:28:47] init: network-manager main process ended, respawning [2016-01-31 14:28:47] traps: NetworkManager[11049] general protection ip:469fee sp:7ffecca7d9d0 error:0 in NetworkManager[40+10d000] [2016-01-31 14:28:47] init: network-manager main process (11049) killed by SEGV signal [2016-01-31 14:28:47] init: network-manager main process ended, respawning [2016-01-31 14:28:47] traps: NetworkManager[11062] general protection ip:469fee sp:7ffc218a9f50 error:0 in NetworkManager[40+10d000] [2016-01-31 14:28:47] init: network-manager main process (11062) killed by SEGV signal [2016-01-31 14:28:47] init: network-manager main process ended, respawning [2016-01-31 14:28:47] traps: NetworkManager[11076] general protection ip:469fee sp:7fff7f128270 error:0 in NetworkManager[40+10d000] [2016-01-31 14:28:47] init: network-manager main process (11076) killed by SEGV signal [2016-01-31 14:28:47] init: network-manager main process ended, respawning [2016-01-31 14:28:47] traps: NetworkManager[11088] general protection ip:469fee sp:7fff66528f90 error:0 in NetworkManager[40+10d000] [2016-01-31 14:28:47] init: network-manager main process (11088) killed by SEGV signal [2016-01-31 14:28:47] init: network-manager main process ended, respawning [2016-01-31 14:28:47] traps: NetworkManager[11092] general protection ip:469fee sp:7fffab819070 error:0 in NetworkManager[40+10d000] [2016-01-31 14:28:47] init: network-manager main process (11092) killed by SEGV signal [2016-01-31 14:28:47] init: network-manager main process ended, respawning [2016-01-31 14:28:47] traps: NetworkManager[11096] general protection ip:469fee sp:7ffe7aa91c20 error:0 in NetworkManager[40+10d000] [2016-01-31 14:28:47] init: network-manager main process (11096) killed by SEGV signal [2016-01-31 14:28:47] init: network-manager main process ended, respawning [2016-01-31 14:28:47] traps: NetworkManager[11100] general protection ip:469fee sp:7ffedfe81460 error:0 in NetworkManager[40+10d000] [2016-01-31 14:28:47] init: network-manager main process (11100) killed by SEGV signal [2016-01-31 14:28:47] init: network-manager main process ended, respawning [2016-01-31 14:28:47] traps: NetworkManager[11104] general protection ip:469fee sp:7ffdc475f140 error:0 in NetworkManager[40+10d000] [2016-01-31 14:28:47] init: network-manager main process (11104) killed by SEGV signal [2016-01-31 14:28:47] init: network-manager main process ended, respawning [2016-01-31 14:28:47] traps: NetworkManager[11108] general protection ip:469fee sp:7ffdeb437010 error:0 in NetworkManager[40+10d000] [2016-01-31 14:28:47] init: network-manager main process (11108) killed by SEGV signal [2016-01-31 14:28:47] init: network-manager main process ended, respawning [2016-01-31 14:28:47] init: network-manager main process (2) killed by SEGV signal [2016-01-31 14:28:47] init: network-manager respawning too fast, stopped This problem prevents me to see nm-applet, and makes me unable to connect to WiFi network. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1540088/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1525310] Re: virsh with apparmor misconfigures libvirt-UUID files during snapshot
This bug also appears in Ubuntu 15.10 $ apt-cache policy apparmor apparmor: Installed: 2.10-0ubuntu6 Candidate: 2.10-0ubuntu6 Version table: *** 2.10-0ubuntu6 0 500 http://us.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy libvirt-bin libvirt-bin: Installed: 1.2.16-2ubuntu11.15.10.1 Candidate: 1.2.16-2ubuntu11.15.10.1 Version table: *** 1.2.16-2ubuntu11.15.10.1 0 500 http://us.archive.ubuntu.com/ubuntu/ wily-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.2.16-2ubuntu11 0 500 http://us.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1525310 Title: virsh with apparmor misconfigures libvirt-UUID files during snapshot Status in apparmor package in Ubuntu: New Bug description: Reproducible: Yes, every time. Background: When you create a virtual machine (VM) under KVM/Qemu in Ubuntu, apparmor files are created as: /etc/apparmor.d/libvirt/libvirt- and /etc/apparmor.d/libvirt/libvirt-.files And in the file /etc/apparmor.d/libvirt/libvirt-.files there is the line "PATH_to_BLOCK_DEVICE" rw, where PATH_to_BLOCK_DEVICE is the full path name of the image. ( E.g. something like /var/lib/libvirtd/images/asdf.qcow2) and is the UUID of the VM container. The problem: When creating a shapshot of a running VM under KVM/Qemu you run the command $ sudo virsh snapshot-create-as DOMAIN_NAME DESCRIPTION --no- metadata --disk-only --atomic which creates a new file and stops writing to the old VM block device. However: the old PATH_to_BLOCK_DEVICE in /etc/apparmor.d/libvirt /libvirt-UUID.files is deleted and replaced with the new block device info BEFORE virsh is done creating the snapshot. So you get the error error: internal error: unable to execute QEMU command 'transaction': Could not open 'PATH_to_BLOCK_DEVICE': Could not open 'PATH_to_BLOCK_DEVICE': Permission denied: Permission denied and in /var/log/syslog you get the error: type=1400 audit(1449752104.054:539): apparmor="DENIED" operation="open" profile="libvirt-" name="PATH_to_BLOCK_DEVICE" pid=8710 comm="qemu-system-x86" requested_mask="r" denied_mask="r" fsuid=106 ouid=106 When you look now at /etc/apparmor.d/libvirt/libvirt-.files you find that the line that was there "PATH_to_BLOCK_DEVICE" rw, has been replaced with "PATH_to_BLOCK_DEVICE.DESCRIPTION" rw, but you need BOTH LINES. in order for the command "virsh snapshot- create-as" to work. (or at least have the old file have read permissions) - Workarounds: 1. Disable apparmor for libvirtd or 2. Change /etc/apparmor.d/libvirt/libvirt- to look like this -- # # This profile is for the domain whose UUID matches this file. # #include profile libvirt-UUID { #include #include "PATH_to_BLOCK_DEVICE*" rw, } --- ( So if the old line was "/var/lib/libvirtd/images/asdf.qcow2" rw, , the line you can add would read something like this "/var/lib/libvirtd/images/asdf*" rw, ) Details on server: # lsb_release -rd Description:Ubuntu 14.04.3 LTS Release:14.04 # apt-cache policy apparmor apparmor: Installed: 2.8.95~2430-0ubuntu5.3 Candidate: 2.8.95~2430-0ubuntu5.3 Version table: *** 2.8.95~2430-0ubuntu5.3 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 2.8.95~2430-0ubuntu5.1 0 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 2.8.95~2430-0ubuntu5 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages # apt-cache policy libvirt-bin libvirt-bin: Installed: 1.2.2-0ubuntu13.1.14 Candidate: 1.2.2-0ubuntu13.1.14 Version table: *** 1.2.2-0ubuntu13.1.14 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.2.2-0ubuntu13.1.7 0 500 http://security.u buntu.com/ubuntu/ trusty-security/main amd64 Packages 1.2.2-0ubuntu13 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages - Apologies if this is the wrong place to submit this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1525310/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1525310] [NEW] virsh with apparmor misconfigures libvirt-UUID files during snapshot
Public bug reported: Reproducible: Yes, every time. Background: When you create a virtual machine (VM) under KVM/Qemu in Ubuntu, apparmor files are created as: /etc/apparmor.d/libvirt/libvirt- and /etc/apparmor.d/libvirt/libvirt-.files And in the file /etc/apparmor.d/libvirt/libvirt-.files there is the line "PATH_to_BLOCK_DEVICE" rw, where PATH_to_BLOCK_DEVICE is the full path name of the image. ( E.g. something like /var/lib/libvirtd/images/asdf.qcow2) and is the UUID of the VM container. The problem: When creating a shapshot of a running VM under KVM/Qemu you run the command $ sudo virsh snapshot-create-as DOMAIN_NAME DESCRIPTION --no- metadata --disk-only --atomic which creates a new file and stops writing to the old VM block device. However: the old PATH_to_BLOCK_DEVICE in /etc/apparmor.d/libvirt /libvirt-UUID.files is deleted and replaced with the new block device info BEFORE virsh is done creating the snapshot. So you get the error error: internal error: unable to execute QEMU command 'transaction': Could not open 'PATH_to_BLOCK_DEVICE': Could not open 'PATH_to_BLOCK_DEVICE': Permission denied: Permission denied and in /var/log/syslog you get the error: type=1400 audit(1449752104.054:539): apparmor="DENIED" operation="open" profile="libvirt-" name="PATH_to_BLOCK_DEVICE" pid=8710 comm ="qemu-system-x86" requested_mask="r" denied_mask="r" fsuid=106 ouid=106 When you look now at /etc/apparmor.d/libvirt/libvirt-.files you find that the line that was there "PATH_to_BLOCK_DEVICE" rw, has been replaced with "PATH_to_BLOCK_DEVICE.DESCRIPTION" rw, but you need BOTH LINES. in order for the command "virsh snapshot- create-as" to work. (or at least have the old file have read permissions) - Workarounds: 1. Disable apparmor for libvirtd or 2. Change /etc/apparmor.d/libvirt/libvirt- to look like this -- # # This profile is for the domain whose UUID matches this file. # #include profile libvirt-UUID { #include #include "PATH_to_BLOCK_DEVICE*" rw, } --- ( So if the old line was "/var/lib/libvirtd/images/asdf.qcow2" rw, , the line you can add would read something like this "/var/lib/libvirtd/images/asdf*" rw, ) Details on server: # lsb_release -rd Description:Ubuntu 14.04.3 LTS Release:14.04 # apt-cache policy apparmor apparmor: Installed: 2.8.95~2430-0ubuntu5.3 Candidate: 2.8.95~2430-0ubuntu5.3 Version table: *** 2.8.95~2430-0ubuntu5.3 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 2.8.95~2430-0ubuntu5.1 0 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 2.8.95~2430-0ubuntu5 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages # apt-cache policy libvirt-bin libvirt-bin: Installed: 1.2.2-0ubuntu13.1.14 Candidate: 1.2.2-0ubuntu13.1.14 Version table: *** 1.2.2-0ubuntu13.1.14 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.2.2-0ubuntu13.1.7 0 500 http://security.u buntu.com/ubuntu/ trusty-security/main amd64 Packages 1.2.2-0ubuntu13 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages - Apologies if this is the wrong place to submit this bug. ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Summary changed: - virsh with apparmor misconfigures libvirtd-UUID files during snapshot + virsh with apparmor misconfigures libvirt-UUID files during snapshot -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1525310 Title: virsh with apparmor misconfigures libvirt-UUID files during snapshot Status in apparmor package in Ubuntu: New Bug description: Reproducible: Yes, every time. Background: When you create a virtual machine (VM) under KVM/Qemu in Ubuntu, apparmor files are created as: /etc/apparmor.d/libvirt/libvirt- and /etc/apparmor.d/libvirt/libvirt-.files And in the file /etc/apparmor.d/libvirt/libvirt-.files there is the line "PATH_to_BLOCK_DEVICE" rw, where PATH_to_BLOCK_DEVICE is the full path name of the image. ( E.g. something like /var/lib/libvirtd/images/asdf.qcow2) and is the UUID of the VM container. The problem: When creating a shapshot of a running VM under KVM/Qemu you run the command $ sudo virsh snapshot-create-as DOMAIN_NAME DESCRIPTION --no- metadata --disk-only --atomic which creates a new file and stops writing to the old VM block device. However: the old PATH_to_BLOCK_DEVICE in /etc/apparmor.d/libvirt /libvirt-UUID.files is deleted and replaced with the new block device info BEFORE virsh is done creating the snapshot. So you get the error error: internal error: unable to execute QEMU
[Touch-packages] [Bug 1525310] Re: virsh with apparmor misconfigures libvirt-UUID files during snapshot
** Description changed: Reproducible: Yes, every time. Background: When you create a virtual machine (VM) under KVM/Qemu in Ubuntu, apparmor files are created as: /etc/apparmor.d/libvirt/libvirt- - and + and /etc/apparmor.d/libvirt/libvirt-.files And in the file /etc/apparmor.d/libvirt/libvirt-.files there is the line - "PATH_to_BLOCK_DEVICE" rw, + "PATH_to_BLOCK_DEVICE" rw, - where PATH_to_BLOCK_DEVICE is the full path name of the image. ( E.g. something like /var/lib/libvirtd/images/asdf.qcow2) - and is the UUID of the VM container. + where PATH_to_BLOCK_DEVICE is the full path name of the image. ( E.g. something like /var/lib/libvirtd/images/asdf.qcow2) + and is the UUID of the VM container. The problem: When creating a shapshot of a running VM under KVM/Qemu you run the command $ sudo virsh snapshot-create-as DOMAIN_NAME DESCRIPTION --no- metadata --disk-only --atomic which creates a new file and stops writing to the old VM block device. However: the old PATH_to_BLOCK_DEVICE in /etc/apparmor.d/libvirt /libvirt-UUID.files is deleted and replaced with the new block device info BEFORE virsh is done creating the snapshot. So you get the error error: internal error: unable to execute QEMU command 'transaction': Could not open 'PATH_to_BLOCK_DEVICE': Could not open 'PATH_to_BLOCK_DEVICE': Permission denied: Permission denied and in /var/log/syslog you get the error: type=1400 audit(1449752104.054:539): apparmor="DENIED" operation="open" profile="libvirt-" name="PATH_to_BLOCK_DEVICE" pid=8710 comm ="qemu-system-x86" requested_mask="r" denied_mask="r" fsuid=106 ouid=106 + When you look now at /etc/apparmor.d/libvirt/libvirt-.files you + find that the line that was there - When you look now at /etc/apparmor.d/libvirt/libvirt-.files you find that the line that was there + "PATH_to_BLOCK_DEVICE" rw, - "PATH_to_BLOCK_DEVICE" rw, + has been replaced with + "PATH_to_BLOCK_DEVICE.DESCRIPTION" rw, - has been replaced with - - "PATH_to_BLOCK_DEVICE.DESCRIPTION" rw, - - - but you need BOTH LINES. in order for the command "virsh snapshot-create-as" to work. (or at least have the old file have read permissions) + but you need BOTH LINES. in order for the command "virsh snapshot- + create-as" to work. (or at least have the old file have read + permissions) - Workarounds: 1. Disable apparmor for libvirtd - or + or 2. Change /etc/apparmor.d/libvirt/libvirt- to look like this + -- # # This profile is for the domain whose UUID matches this file. - # - + # + #include - + profile libvirt-UUID { - #include - #include - - "PATH_to_BLOCK_DEVICE*" rw, - } + #include + #include + + "PATH_to_BLOCK_DEVICE*" rw, + } --- + ( + So if the old line was + "/var/lib/libvirtd/images/asdf.qcow2" rw, + , the line you can add would read something like this + + "/var/lib/libvirtd/images/asdf*" rw, + + ) + Details on server: # lsb_release -rd Description:Ubuntu 14.04.3 LTS Release:14.04 - # apt-cache policy apparmor apparmor: - Installed: 2.8.95~2430-0ubuntu5.3 - Candidate: 2.8.95~2430-0ubuntu5.3 - Version table: - *** 2.8.95~2430-0ubuntu5.3 0 - 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages - 100 /var/lib/dpkg/status - 2.8.95~2430-0ubuntu5.1 0 - 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages - 2.8.95~2430-0ubuntu5 0 - 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages + Installed: 2.8.95~2430-0ubuntu5.3 + Candidate: 2.8.95~2430-0ubuntu5.3 + Version table: + *** 2.8.95~2430-0ubuntu5.3 0 + 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages + 100 /var/lib/dpkg/status + 2.8.95~2430-0ubuntu5.1 0 + 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages + 2.8.95~2430-0ubuntu5 0 + 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages # apt-cache policy libvirt-bin libvirt-bin: - Installed: 1.2.2-0ubuntu13.1.14 - Candidate: 1.2.2-0ubuntu13.1.14 - Version table: - *** 1.2.2-0ubuntu13.1.14 0 - 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages - 100 /var/lib/dpkg/status - 1.2.2-0ubuntu13.1.7 0 - 500 http://security.u buntu.com/ubuntu/ trusty-security/main amd64 Packages - 1.2.2-0ubuntu13 0 - 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages - + Installed: 1.2.2-0ubuntu13.1.14 + Candidate: 1.2.2-0ubuntu13.1.14 + Version table: + *** 1.2.2-0ubuntu13.1.14 0 + 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages + 100 /var/lib/dpkg/status + 1.2.2-0ubuntu13.1.7 0 + 500