[Touch-packages] [Bug 1774915] Re: Video freezes and stutters when using totem (audio continues fine)
One more thing: Wayland sessions might perform better, so please try mpv in a Wayland session. Unfortunately Totem probably won't work there (bug 1770725). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1774915 Title: Video freezes and stutters when using totem (audio continues fine) Status in gnome-shell package in Ubuntu: Incomplete Status in gstreamer1.0 package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: Advised to file a bug report after posting on "Call for testing: Video playback in 18.04". Running 18.04 LTS as fresh install (not upgraded from previous version - older version still installed in separate partition). Xorg session. System: HP Pavillion DV7 (lm726av) - Intel Core i7 2630 processor, integrated Intel video Playing any local video file (regardless of video format - flv, mp4, avi), the video will randomly lag in playback. Audio is not affected, it plays back correctly. Very occasional lags in browsers (Firefox and Chrome) on pages with a lot of active graphics (flash or HTML5). Browser lags significantly improved after installing synaptic driver for touchpad operation (I have no idea why this would affect video playback - I simply note that it happened). I can pick a random video on YouTube and watch it in Firefox or Chrome without lag (even full-screen). However, if I grab a local copy of the video (using, for instance, Clipgrab) and play it using Totem, I get lag. I was also advised to try using mpv - I still get lag in mpv, although not as pronounced. tracy@tracy-hp:~$ sudo apt-cache policy totem [sudo] password for tracy: totem: Installed: 3.26.0-0ubuntu6 Candidate: 3.26.0-0ubuntu6 Version table: *** 3.26.0-0ubuntu6 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status I was also asked to include output of lspci -k - shown below: tracy@tracy-hp:~$ lspci -k 00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family DRAM Controller 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port (rev 09) Kernel driver in use: pcieport Kernel modules: shpchp 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family Integrated Graphics Controller Kernel driver in use: i915 Kernel modules: i915 00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04) Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family MEI Controller Kernel driver in use: mei_me Kernel modules: mei_me 00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05) Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family USB Enhanced Host Controller Kernel driver in use: ehci-pci 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05) Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family High Definition Audio Controller Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5) Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (rev b5) Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 3 (rev b5) Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 (rev b5) Kernel driver in use: pcieport Kernel modules: shpchp 00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05) Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family USB Enhanced Host Controller Kernel driver in use: ehci-pci 00:1f.0 ISA bridge: Intel Corporation HM65 Express Chipset Family LPC Controller (rev 05) Subsystem: Hewlett-Packard Company HM65 Express Chipset Family LPC Controller Kernel driver in use: lpc_ich Kernel modules: lpc_ich 00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset
[Touch-packages] [Bug 1775337] Re: 18.04 Headphones detected, but not switched on automatically after startup
I'm not even sure it's pulseaudio, just picked a word I knew ubuntu sound is related to. could be alsa, pulseaudio, or neither. I really don't know. ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => New ** Bug watch added: freedesktop.org Bugzilla #106834 https://bugs.freedesktop.org/show_bug.cgi?id=106834 -- 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/1775337 Title: 18.04 Headphones detected, but not switched on automatically after startup Status in pulseaudio package in Ubuntu: New Bug description: Been this way since at least 15. Plug in your headphones, boot up your laptop. No sound. Speakers and headphones are disabled. Super annoying, you have to unplug and re- plug, and go through the stupid dialogue of "what are you trying to plug in?" which has no memory, and no defaults. Please, please, please, fix this Ubuntu team! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom1369 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Jun 6 02:28:13 2018 InstallationDate: Installed on 2018-04-26 (41 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/28/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.1 dmi.board.name: 0JHP5H dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.1:bd03/28/2018:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn0JHP5H:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.sys.vendor: Dell Inc. modified.conffile..etc.xdg.autostart.pulseaudio.desktop: [modified] mtime.conffile..etc.xdg.autostart.pulseaudio.desktop: 2018-05-26T14:25:02.708160 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1775337/+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 1775337] Re: 18.04 Headphones detected, but not switched on automatically after startup
https://bugs.freedesktop.org/show_bug.cgi?id=106834 but this feels wrong. -- 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/1775337 Title: 18.04 Headphones detected, but not switched on automatically after startup Status in pulseaudio package in Ubuntu: New Bug description: Been this way since at least 15. Plug in your headphones, boot up your laptop. No sound. Speakers and headphones are disabled. Super annoying, you have to unplug and re- plug, and go through the stupid dialogue of "what are you trying to plug in?" which has no memory, and no defaults. Please, please, please, fix this Ubuntu team! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom1369 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Jun 6 02:28:13 2018 InstallationDate: Installed on 2018-04-26 (41 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/28/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.1 dmi.board.name: 0JHP5H dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.1:bd03/28/2018:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn0JHP5H:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.sys.vendor: Dell Inc. modified.conffile..etc.xdg.autostart.pulseaudio.desktop: [modified] mtime.conffile..etc.xdg.autostart.pulseaudio.desktop: 2018-05-26T14:25:02.708160 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1775337/+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 1772859] Comment bridged from LTC Bugzilla
--- Comment From abhir...@in.ibm.com 2018-06-06 03:26 EDT--- Team, We understand Network Manager is good for desktop but not servers. But given the stability NetworkManager is bringing in and ease of use across different operating systems, i assume users are not restricted not to use NetworkManager for servers. The reason being we going with network manager as explained is to reuse the code for all distros. Note : Netplan is not present/installed in our ubuntu. So by default we are expecting network manager to work. root@57fb2571ae8a:~# ls -l /etc | grep netplan root@57fb2571ae8a:~# If we need to start using netplan, probably we have to re-write the code to configure yaml files which can be understood by netplan. So as a workaround, we would like to understand why network manager is failing to manage the devices? This is definitely to do with open issue, https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1638842 Let me know if more data is needed for analysis, 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/1772859 Title: Network Manager is not able to manage the devices on Ubuntu 18.04 Status in Ubuntu on IBM z Systems: Invalid Status in network-manager package in Ubuntu: Invalid Bug description: NetworkManager is not able to manage the devices on latest Ubuntu(18.04) ---uname output--- Linux (none) 4.15.0-12-generic #13-Ubuntu SMP Wed Mar 7 21:36:36 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = z14 s390 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. Install the latest Ubuntu(18.04) with Network Manager(1.10.4). 2. Configure a network device and login to the partition through ssh. 3. Now you can see the following output root@(none):~# nmcli d s DEVICE TYPE STATE CONNECTION eth0ethernet unmanaged -- eth1ethernet unmanaged -- lo loopback unmanaged -- Userspace tool common name: 1.10.6-2ubuntu1: amd64 arm64 armhf i386 ppc64el s390x The userspace tool has the following bit modes: 64-bit Userspace rpm: NetworkManager --version 1.10.4 Userspace tool obtained from project website: na Some more information about the issue: Network device has been configured manually after the image is up from Support Element(SE): - znetconf -a - cat /sys/bus/ccwgroup/drivers/qeth//if_name - ifconfig netmask 255.255.255.0 - route add default gw - SSH service has been configured This helped us to login to the Lpar. In Lpar - output of znetconf -c Device IDs TypeCard Type CHPID Drv. Name State - 0.0.1a80,0.0.1a81,0.0.1a82 1731/01 OSD_10GIG A8 qeth eth0 online 0.0.1810,0.0.1811,0.0.1812 1731/01 OSD_1000 D0 qeth eth1 online - output of nmcli c s root@(none):~# nmcli c s NAME UUID TYPE DEVICE - output of nmcli d s root@(none):~# nmcli d s DEVICE TYPE STATE CONNECTION eth0ethernet unmanaged -- eth1ethernet unmanaged -- lo loopback unmanaged -- * The above output shows that devices are not managed by nmcli After some investigation we found couple of suggestions like 1. Ubuntu(version <17.04): Creating an empty file(/etc/NetworkManager/conf.d/10-globally-managed-devices.conf) and restarting NM, solved the issue. 2. Ubuntu(version 17.10): Copying the said file(10-globally-managed-devices.conf) from /usr/lib to /etc/ and modifying the "unmanaged-devices" to none, resolved the issue. * link for reference: https://bugs.launchpad.net/ubuntu/+source /network-manager/+bug/1638842 For the latest version(18.04), none of the above solutions worked. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1772859/+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 1775337] Re: 18.04 Headphones detected, but not switched on automatically after startup
Definitely been lots of existing reports of this problem. For example, https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1583801 also at least 3 of the same problem on AskUbuntu. -- 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/1775337 Title: 18.04 Headphones detected, but not switched on automatically after startup Status in pulseaudio package in Ubuntu: New Bug description: Been this way since at least 15. Plug in your headphones, boot up your laptop. No sound. Speakers and headphones are disabled. Super annoying, you have to unplug and re- plug, and go through the stupid dialogue of "what are you trying to plug in?" which has no memory, and no defaults. Please, please, please, fix this Ubuntu team! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom1369 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Jun 6 02:28:13 2018 InstallationDate: Installed on 2018-04-26 (41 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/28/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.1 dmi.board.name: 0JHP5H dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.1:bd03/28/2018:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn0JHP5H:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.sys.vendor: Dell Inc. modified.conffile..etc.xdg.autostart.pulseaudio.desktop: [modified] mtime.conffile..etc.xdg.autostart.pulseaudio.desktop: 2018-05-26T14:25:02.708160 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1775337/+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 1765923] Re: Nvidia driver leads to black screen on bionic 18.04 SDDM LightDM bug?
I upgraded from 17.04 to this, and can't get to a desktop now. Really regretting using ubuntu, yet again. This is a dell xps 15 9550, I finally had to try an upgrade due to various weird issues with 17.04 still, but at least it worked vs. now. Might try nouveau as recommended. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1765923 Title: Nvidia driver leads to black screen on bionic 18.04 SDDM LightDM bug? Status in apt package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in sddm package in Ubuntu: Confirmed Bug description: Using the April 19th daily build of Kubuntu 18.04 I installed the Nvidia drivers via the following command. sudo ubuntu-drivers autoinstall The install process proceeds fine and after a logout process I get a black screen. I tried this on the April 17th daily build of bionic and a reboot also results in a black screen. The following is a question which was submitted by a Ubuntu 17.10 user: QUOTE After I installed latest Nvidia driver-390 and tried to boot after shutting down once I faced a black screen problem. since, I'm a noob but something related to nvidia drivers couldn't be started. Then I followed https://askubuntu.com/a/968692/802490 While following these instructions re-installing of nvidia drivers failed. The only things that worked is purging the drivers and changing "WaylandEnable=false" in (/etc/gdm3/custom.conf). Now, I want to re-install nvidia drivers again but I'm afraid that this will lead to that problem again. Can anyone help in re-installing the driver such that I won't face that problem? END QUOTE THE WORK AROUND Use Ctrl-Alt-f6 to get to a login prompt. Login run "startx" The x server will start and Nvidia drivers will function. THE PROBLEM When I try to run SDDM I get an error (Which I will try to copy down to add to this bug when I am on a different computer than the one I am reporting the bug about.). Installing lightDM does not work... it installs but is either will not run or will not actually start a x session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1765923/+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 1775337] Re: 18.04 Headphones detected, but not switched on automatically after startup
I can't find any existing reports of this problem. Please report it to the PulseAudio developers here: https://bugs.freedesktop.org/enter_bug.cgi?product=PulseAudio and then send us a link to the new bug. ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1775337 Title: 18.04 Headphones detected, but not switched on automatically after startup Status in pulseaudio package in Ubuntu: Incomplete Bug description: Been this way since at least 15. Plug in your headphones, boot up your laptop. No sound. Speakers and headphones are disabled. Super annoying, you have to unplug and re- plug, and go through the stupid dialogue of "what are you trying to plug in?" which has no memory, and no defaults. Please, please, please, fix this Ubuntu team! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom1369 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Jun 6 02:28:13 2018 InstallationDate: Installed on 2018-04-26 (41 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/28/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.1 dmi.board.name: 0JHP5H dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.1:bd03/28/2018:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn0JHP5H:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.sys.vendor: Dell Inc. modified.conffile..etc.xdg.autostart.pulseaudio.desktop: [modified] mtime.conffile..etc.xdg.autostart.pulseaudio.desktop: 2018-05-26T14:25:02.708160 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1775337/+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 1583801] Re: No sound via headphones (headset) when Ubuntu boots with them plugged in
** Bug watch added: freedesktop.org Bugzilla #106834 https://bugs.freedesktop.org/show_bug.cgi?id=106834 ** Also affects: pulseaudio via https://bugs.freedesktop.org/show_bug.cgi?id=106834 Importance: Unknown Status: Unknown ** Tags added: bionic ** Changed in: pulseaudio (Ubuntu) Importance: Undecided => Medium -- 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/1583801 Title: No sound via headphones (headset) when Ubuntu boots with them plugged in Status in PulseAudio: Unknown Status in alsa-driver package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: The bug is twofold, first when computer boots if the headset (headphones with built-in mic, one audio jack) is plugged in, then there is no sound (via headphones or otherwise). If you plug headphones out and back in, then it usually works as expected. The second scenario is the same, except that plugging out and back in again doesn't help. In that case, I just restart the laptop, then plug them back in again and it works. In all cases, microphone works. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crunch 3248 F pulseaudio CurrentDesktop: Unity Date: Thu May 19 22:13:20 2016 InstallationDate: Installed on 2016-05-07 (12 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crunch 3248 F pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_Type: No sound at all Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1583801/+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 1583801] Re: No sound via headphones (headset) when Ubuntu boots with them plugged in
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (Ubuntu) Status: New => Confirmed -- 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/1583801 Title: No sound via headphones (headset) when Ubuntu boots with them plugged in Status in PulseAudio: Unknown Status in alsa-driver package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: The bug is twofold, first when computer boots if the headset (headphones with built-in mic, one audio jack) is plugged in, then there is no sound (via headphones or otherwise). If you plug headphones out and back in, then it usually works as expected. The second scenario is the same, except that plugging out and back in again doesn't help. In that case, I just restart the laptop, then plug them back in again and it works. In all cases, microphone works. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crunch 3248 F pulseaudio CurrentDesktop: Unity Date: Thu May 19 22:13:20 2016 InstallationDate: Installed on 2016-05-07 (12 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crunch 3248 F pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_Type: No sound at all Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1583801/+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 1246981] Re: Bluetooth mouse fails to re-connect after sleep.
** Tags added: bionic -- 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/1246981 Title: Bluetooth mouse fails to re-connect after sleep. Status in bluez package in Ubuntu: Confirmed Bug description: This exact harware was working faultlessly in 13.04. Since re- installing at 13.10 the mouse consistently failes to reconnect after the device either hybernates or ever goes to screen saver sleep. I have to remove the dive and re-add it each time (which works well). There are other issues with the bluetooth stack as well in that I have not found any way to use bluetooth tethering to my mobile which again worked well and was easy to configure in 13.04 Peter. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: bluetooth 4.101-0ubuntu8b1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Fri Nov 1 16:44:37 2013 InstallationDate: Installed on 2013-10-19 (13 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: bnep rfcomm btusb bluetooth MachineType: Dell Inc. Latitude E6530 MarkForUpload: True PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=8283de78-9264-42bf-a8b4-25643fa1475f ro quiet splash SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/13/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 07Y85M dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd12/13/2012:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6530 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 20:16:D8:9C:38:E5 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN ISCAN RX bytes:1817731 acl:117432 sco:0 events:5271 errors:0 TX bytes:37955 acl:131 sco:0 commands:5096 errors:0 syslog: Nov 1 14:50:19 pnunn-Latitude-E6530 bluetoothd[1015]: Discovery session 0x7f6489f7b450 with :1.582 activated Nov 1 14:50:25 pnunn-Latitude-E6530 bluetoothd[1015]: Unknown command complete for opcode 37 Nov 1 14:50:28 pnunn-Latitude-E6530 bluetoothd[1015]: Stopping discovery Nov 1 14:50:36 pnunn-Latitude-E6530 kernel: [60934.211132] input: Microsoft Bluetooth Notebook Mouse 5000 as /devices/pci:00/:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/bluetooth/hci0/hci0:11/input29 Nov 1 14:50:36 pnunn-Latitude-E6530 kernel: [60934.211646] hid-generic 0005:045E:0700.000C: input,hidraw3: BLUETOOTH HID v1.00 Mouse [Microsoft Bluetooth Notebook Mouse 5000] on 20:16:d8:9c:38:e5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1246981/+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 1583801] Re: No sound via headphones (headset) when Ubuntu boots with them plugged in
** Also affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- 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/1583801 Title: No sound via headphones (headset) when Ubuntu boots with them plugged in Status in PulseAudio: Unknown Status in alsa-driver package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: The bug is twofold, first when computer boots if the headset (headphones with built-in mic, one audio jack) is plugged in, then there is no sound (via headphones or otherwise). If you plug headphones out and back in, then it usually works as expected. The second scenario is the same, except that plugging out and back in again doesn't help. In that case, I just restart the laptop, then plug them back in again and it works. In all cases, microphone works. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crunch 3248 F pulseaudio CurrentDesktop: Unity Date: Thu May 19 22:13:20 2016 InstallationDate: Installed on 2016-05-07 (12 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crunch 3248 F pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_Type: No sound at all Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1583801/+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 1646029] Re: bluetooth stopped working on upgrade to 16.10
Thank you for reporting this bug to Ubuntu. Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: bluez (Ubuntu) Status: New => Invalid -- 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/1646029 Title: bluetooth stopped working on upgrade to 16.10 Status in bluez package in Ubuntu: Invalid Bug description: prior had working system in 16.04 had installed sudo apt-get pulseaudio-module-bluetooth sudo apt-get install pulseaudio pulseaudio-module-bluetooth pavucontrol bluez-firmware sudo apt-get install pulseaudio-module-bluetooth for use with bluetooth headset ad2p and it was working well. Upgrade and the bluetooth using usb dongle stopped working syslog == Nov 30 08:30:21 betelgeuse pulseaudio[1927]: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. Nov 30 09:01:00 betelgeuse pulseaudio[1927]: message repeated 3 times: [ [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended.] Nov 30 09:05:45 betelgeuse systemd[1]: Starting Daily apt activities... Nov 30 09:05:46 betelgeuse systemd[1]: Started Daily apt activities. Nov 30 09:05:46 betelgeuse systemd[1]: apt-daily.timer: Adding 7h 32min 41.100513s random time. Nov 30 09:05:46 betelgeuse systemd[1]: apt-daily.timer: Adding 2h 14min 40.439253s random time. Nov 30 09:10:37 betelgeuse pulseaudio[1927]: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. Nov 30 09:10:37 betelgeuse pulseaudio[1927]: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. Nov 30 09:17:01 betelgeuse CRON[18210]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Nov 30 09:17:29 betelgeuse pulseaudio[1927]: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. Nov 30 09:34:18 betelgeuse pulseaudio[1927]: message repeated 3 times: [ [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended.] Nov 30 10:17:01 betelgeuse CRON[18428]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Nov 30 10:45:18 betelgeuse pulseaudio[1927]: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. Nov 30 10:45:18 betelgeuse pulseaudio[1927]: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. Nov 30 11:17:01 betelgeuse CRON[18635]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Nov 30 11:42:44 betelgeuse pulseaudio[1927]: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. Nov 30 11:42:44 betelgeuse pulseaudio[1927]: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended dpkg.log 2016-11-23 19:37:07 startup archives unpack 2016-11-23 19:37:07 upgrade bluez:amd64 5.37-0ubuntu5 5.41-0ubuntu3 2016-11-23 19:37:07 status half-configured bluez:amd64 5.37-0ubuntu5 2016-11-23 19:37:07 status unpacked bluez:amd64 5.37-0ubuntu5 2016-11-23 19:37:07 status half-installed bluez:amd64 5.37-0ubuntu5 2016-11-23 19:41:58 startup packages remove 2016-11-23 19:41:58 status installed pulseaudio-module-x11:amd64 1:8.0-0ubuntu3 2016-11-23 19:41:59 remove pulseaudio-module-x11:amd64 1:8.0-0ubuntu3 2016-11-23 19:41:59 status half-configured pulseaudio-module-x11:amd64 1:8.0-0ubuntu3 2016-11-23 19:41:59 status half-installed pulseaudio-module-x11:amd64 1:8.0-0ubuntu3 2016-11-23 19:41:59 status config-files pulseaudio-module-x11:amd64 1:8.0-0ubuntu3 2016-11-23 19:41:59 status config-files pulseaudio-module-x11:amd64 1:8.0-0ubuntu3 2016-11-23 19:41:59 status config-files pulseaudio-module-x11:amd64 1:8.0-0ubuntu3 2016-11-23 19:41:59 status not-installed pulseaudio-module-x11:amd64 2016-11-23 19:41:59 startup archives unpack 2016-11-23 19:42:09 upgrade pulseaudio-module-zeroconf:amd64 1:8.0-0ubuntu3 1:9.0-2ubuntu2.1 2016-11-23 19:42:09 status half-configured pulseaudio-module-zeroconf:amd64 1:8.0-0ubuntu3 2016-11-23 19:42:10 status unpacked pulseaudio-module-zeroconf:amd64 1:8.0-0ubuntu3 2016-11-23 19:42:10 status half-installed pulseaudio-module-zeroconf:amd64 1:8.0-0ubuntu3 2016-11-23 19:42:10 status half-installed pulseaudio-module-zeroconf:amd64 1:8.0-0ubuntu3 2016-11-23 19:42:10 status unpacked pulseaudio-module-zeroconf:amd64 1:9.0-2ubuntu2.1 2016-11-23 19:42:10 status unpacked pulseaudio-module-zeroconf:amd64 1:9.0-2ubuntu2.1 2016-11-23 19:42:
[Touch-packages] [Bug 1775187] rfkill.txt
apport information ** Attachment added: "rfkill.txt" https://bugs.launchpad.net/bugs/1775187/+attachment/5149225/+files/rfkill.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1775187 Title: bluetooth headset gets imitatively disconnected Status in bluez package in Ubuntu: Incomplete Bug description: I upgraded from artful to bionic (just run apt update && apt upgrade and rebooted before testing the below) and since then my sennheiser pxc550 was immediately disconnected after a connect. Jun 05 15:18:49 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] backend-native.c: Device doesnt exist for /org/bluez/hci0/dev_00_16_94_22_21_D8 Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Headset Voice gateway replied with an error: org.bluez.Error.InvalidArguments, Unable to handle new connection Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:52 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:18:53 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:53 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:55 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:19:07 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:23 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:39 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) [...same message a few more time until I had a new version installed ...] I since then applied the patch from https://bugzilla.redhat.com/show_bug.cgi?id=1534857 -> https://marc.info/?l=linux-bluetooth&m=151801178209679&q=raw to bluez (apt source bluez -> patch -> dpkg-buildpackage ... > sudo dpkg -i ../*.deb) and now my headset works again. --- ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-11-09 (209 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20FWCTO1WW Package: bluez 5.48-0ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-22-generic root=UUID=128d75b0-64fc-468a-95fc-0aaf631bf4fe ro rootflags=subvol=@ quiet splash cgroup_enable=memory swapaccount=1 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Tags: third-party-packages bionic Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bluetooth cdrom dip docker lpadmin plugdev sambashare sudo systemd-journal wireshark _MarkForUpload: True 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: 20FWCTO1WW 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:pn20FWCTO1WW:pvrThinkPadT460p:rvnLENOVO:rn20FWCTO1WW:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FWCTO1WW dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: E4:A7:A0:14:18:46 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:4394393 acl:135 sco:0 events:618416 errors:0 TX bytes:524957211 acl:614106 sco:0 commands:2823 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1775187/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to :
[Touch-packages] [Bug 1772632] Re: Backport packages for 16.04.5 HWE stack
** Changed in: xserver-xorg-video-amdgpu (Ubuntu) Status: New => Invalid ** Changed in: xserver-xorg-video-ati (Ubuntu) Status: New => Invalid ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1772632 Title: Backport packages for 16.04.5 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-6.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in xorg-server-hwe-16.04 package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu package in Ubuntu: Invalid Status in xserver-xorg-video-ati package in Ubuntu: Invalid Status in xserver-xorg-video-intel package in Ubuntu: Invalid Status in libclc source package in Xenial: New Status in libdrm source package in Xenial: New Status in llvm-toolchain-6.0 source package in Xenial: New Status in mesa source package in Xenial: New Status in xorg-server-hwe-16.04 source package in Xenial: New Status in xserver-xorg-video-amdgpu source package in Xenial: New Status in xserver-xorg-video-ati source package in Xenial: New Status in xserver-xorg-video-intel source package in Xenial: New Bug description: [Impact] *** hwe-16.04 refresh for 16.04.5 *** A minor update, only xserver sync, some driver updates plus a newer Mesa. Mesa needs llvm-toolchain-6.0 and libclc, libdrm, updates. [Test case] upgrade from/to stock & old hwe stack, test desktop usage [Regression potential] libdrm: Slim to none, changes from 2.4.83 to 2.4.91 - amdgpu: new pci-ids, bugfixes - intel: new pci-ids - drm: some new ioctl's - exynos, etnaviv, freedreno, android: fixes, new stuff llvm-toolchain-6.0: None, a new package libclc: I'd say none, very little has changed, added support for llvm-6 is the main reason for this slightly newer snapshot xorg-server: Slim, it's an upstream bugfix release, changes from 1.19.5 to 1.19.6+git include: - security fixes - backported bugfixes to glamor, modesetting driver, xwayland etc mesa: New major release plus a few bugfix updates after that. Regressions at this point are less likely. Upstream is tested by Intel CI system for instance. And we're already testing it via a ppa on OEM systems for 16.04.5. Tracking bug for the bugfix release (bionic) is bug 1772607 [Other info] build order: [libdrm, llvm-toolchain-6.0], [libclc, xorg-server], mesa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1772632/+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 1767292] Re: The bluetooth mouse cannot connect after sleep mode.
*** This bug is a duplicate of bug 1246981 *** https://bugs.launchpad.net/bugs/1246981 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1246981, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Package changed: alsa-driver (Ubuntu) => bluez (Ubuntu) ** This bug has been marked a duplicate of bug 1246981 Bluetooth mouse fails to re-connect after sleep. -- 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/1767292 Title: The bluetooth mouse cannot connect after sleep mode. Status in bluez package in Ubuntu: Confirmed Bug description: The bluetooth mouse cannot connect after sleep mode. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: giacomo1998 F pulseaudio CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME Date: Fri Apr 27 09:49:41 2018 InstallationDate: Installed on 2017-04-13 (378 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: Upgraded to bionic on 2018-04-13 (13 days ago) dmi.bios.date: 07/27/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R08ET43W (1.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FU001PMC 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:bvrR08ET43W(1.17):bd07/27/2016:svnLENOVO:pn20FU001PMC:pvrThinkPadL460:rvnLENOVO:rn20FU001PMC:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L460 dmi.product.name: 20FU001PMC dmi.product.version: ThinkPad L460 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1767292/+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 1775350] Re: package python3-problem-report 2.20.7-0ubuntu3.9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1775350 Title: package python3-problem-report 2.20.7-0ubuntu3.9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139 Status in apport package in Ubuntu: New Bug description: i think it s something connected to launch vlc and totem together. i dont think it s nothing serious 'due it happens only when i m playing something ( video or audio doesnt matter at all ) on vlc and totem player. Tnx. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: python3-problem-report 2.20.7-0ubuntu3.9 ProcVersionSignature: Ubuntu 4.13.0-43.48-generic 4.13.16 Uname: Linux 4.13.0-43-generic x86_64 ApportLog: ERROR: apport (pid 8975) Wed Jun 6 10:09:33 2018: called for pid 3927, signal 11, core limit 0, dump mode 1 ERROR: apport (pid 8975) Wed Jun 6 10:09:33 2018: executable: /usr/bin/vlc (command line "/usr/bin/vlc --started-from-file /home/shukty/Videos/Pendulum\ -\ Crush\ (Official\ Video)-8mYd2X_9rrs.mkv") ERROR: apport (pid 8975) Wed Jun 6 10:09:33 2018: debug: session gdbus call: (true,) ERROR: apport (pid 8975) Wed Jun 6 10:09:43 2018: wrote report /var/crash/_usr_bin_vlc.1000.crash ApportVersion: 2.20.7-0ubuntu3.9 Architecture: amd64 CrashReports: 640:1000:122:18044809:2018-06-06 10:09:42.522929668 +0200:2018-06-06 10:09:43.522929668 +0200:/var/crash/_usr_bin_vlc.1000.crash 600:0:122:107372:2018-06-04 15:08:55.800413608 +0200:2018-06-04 15:08:56.800413608 +0200:/var/crash/python3-problem-report.0.crash 640:1000:122:6856032:2020-11-09 04:13:15.499161243 +0100:2020-11-09 04:13:16.499161243 +0100:/var/crash/_usr_bin_nautilus-desktop.1000.crash 640:0:122:379385:2018-06-05 09:40:32.451522103 +0200:2018-06-05 09:40:32.147522104 +0200:/var/crash/_usr_sbin_cupsd.0.crash 640:1000:122:4040060:2018-06-05 19:10:59.283614397 +0200:2018-06-05 19:11:00.283614397 +0200:/var/crash/_usr_bin_totem-video-thumbnailer.1000.crash Date: Mon Jun 4 15:08:56 2018 Dependencies: DuplicateSignature: package:python3-problem-report:2.20.7-0ubuntu3.9 Setting up python3-problem-report (2.20.7-0ubuntu3.9) ... Segmentation fault dpkg: error processing package python3-problem-report (--configure): subprocess installed post-installation script returned error exit status 139 ErrorMessage: subprocess installed post-installation script returned error exit status 139 InstallationDate: Installed on 2017-09-21 (257 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: apport Title: package python3-problem-report 2.20.7-0ubuntu3.9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139 UpgradeStatus: Upgraded to artful on 2017-10-28 (221 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1775350/+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 1775350] [NEW] package python3-problem-report 2.20.7-0ubuntu3.9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139
Public bug reported: i think it s something connected to launch vlc and totem together. i dont think it s nothing serious 'due it happens only when i m playing something ( video or audio doesnt matter at all ) on vlc and totem player. Tnx. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: python3-problem-report 2.20.7-0ubuntu3.9 ProcVersionSignature: Ubuntu 4.13.0-43.48-generic 4.13.16 Uname: Linux 4.13.0-43-generic x86_64 ApportLog: ERROR: apport (pid 8975) Wed Jun 6 10:09:33 2018: called for pid 3927, signal 11, core limit 0, dump mode 1 ERROR: apport (pid 8975) Wed Jun 6 10:09:33 2018: executable: /usr/bin/vlc (command line "/usr/bin/vlc --started-from-file /home/shukty/Videos/Pendulum\ -\ Crush\ (Official\ Video)-8mYd2X_9rrs.mkv") ERROR: apport (pid 8975) Wed Jun 6 10:09:33 2018: debug: session gdbus call: (true,) ERROR: apport (pid 8975) Wed Jun 6 10:09:43 2018: wrote report /var/crash/_usr_bin_vlc.1000.crash ApportVersion: 2.20.7-0ubuntu3.9 Architecture: amd64 CrashReports: 640:1000:122:18044809:2018-06-06 10:09:42.522929668 +0200:2018-06-06 10:09:43.522929668 +0200:/var/crash/_usr_bin_vlc.1000.crash 600:0:122:107372:2018-06-04 15:08:55.800413608 +0200:2018-06-04 15:08:56.800413608 +0200:/var/crash/python3-problem-report.0.crash 640:1000:122:6856032:2020-11-09 04:13:15.499161243 +0100:2020-11-09 04:13:16.499161243 +0100:/var/crash/_usr_bin_nautilus-desktop.1000.crash 640:0:122:379385:2018-06-05 09:40:32.451522103 +0200:2018-06-05 09:40:32.147522104 +0200:/var/crash/_usr_sbin_cupsd.0.crash 640:1000:122:4040060:2018-06-05 19:10:59.283614397 +0200:2018-06-05 19:11:00.283614397 +0200:/var/crash/_usr_bin_totem-video-thumbnailer.1000.crash Date: Mon Jun 4 15:08:56 2018 Dependencies: DuplicateSignature: package:python3-problem-report:2.20.7-0ubuntu3.9 Setting up python3-problem-report (2.20.7-0ubuntu3.9) ... Segmentation fault dpkg: error processing package python3-problem-report (--configure): subprocess installed post-installation script returned error exit status 139 ErrorMessage: subprocess installed post-installation script returned error exit status 139 InstallationDate: Installed on 2017-09-21 (257 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: apport Title: package python3-problem-report 2.20.7-0ubuntu3.9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139 UpgradeStatus: Upgraded to artful on 2017-10-28 (221 days ago) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package artful -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1775350 Title: package python3-problem-report 2.20.7-0ubuntu3.9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139 Status in apport package in Ubuntu: New Bug description: i think it s something connected to launch vlc and totem together. i dont think it s nothing serious 'due it happens only when i m playing something ( video or audio doesnt matter at all ) on vlc and totem player. Tnx. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: python3-problem-report 2.20.7-0ubuntu3.9 ProcVersionSignature: Ubuntu 4.13.0-43.48-generic 4.13.16 Uname: Linux 4.13.0-43-generic x86_64 ApportLog: ERROR: apport (pid 8975) Wed Jun 6 10:09:33 2018: called for pid 3927, signal 11, core limit 0, dump mode 1 ERROR: apport (pid 8975) Wed Jun 6 10:09:33 2018: executable: /usr/bin/vlc (command line "/usr/bin/vlc --started-from-file /home/shukty/Videos/Pendulum\ -\ Crush\ (Official\ Video)-8mYd2X_9rrs.mkv") ERROR: apport (pid 8975) Wed Jun 6 10:09:33 2018: debug: session gdbus call: (true,) ERROR: apport (pid 8975) Wed Jun 6 10:09:43 2018: wrote report /var/crash/_usr_bin_vlc.1000.crash ApportVersion: 2.20.7-0ubuntu3.9 Architecture: amd64 CrashReports: 640:1000:122:18044809:2018-06-06 10:09:42.522929668 +0200:2018-06-06 10:09:43.522929668 +0200:/var/crash/_usr_bin_vlc.1000.crash 600:0:122:107372:2018-06-04 15:08:55.800413608 +0200:2018-06-04 15:08:56.800413608 +0200:/var/crash/python3-problem-report.0.crash 640:1000:122:6856032:2020-11-09 04:13:15.499161243 +0100:2020-11-09 04:13:16.499161243 +0100:/var/crash/_usr_bin_nautilus-desktop.1000.crash 640:0:122:379385:2018-06-05 09:40:32.451522103 +0200:2018-06-05 09:40:32.147522104 +0200:/var/crash/_usr_sbin_cupsd.0.crash 640:1000:122:4040060:2018-06-05 19:10:59.283614397 +0200:2018-06-05 19:11:00.283614397 +0200:/var/crash/_usr_bin_totem-video-thu
[Touch-packages] [Bug 1768232] Re: [HP Compaq dx2080 Microtower PC] Stuck at Ubuntu 18.04 logo while booting after installing
*** This bug is a duplicate of bug 1727356 *** https://bugs.launchpad.net/bugs/1727356 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1727356, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** Changed in: mutter (Ubuntu) Status: Fix Released => Confirmed ** This bug has been marked a duplicate of bug 1727356 Wayland sessions (including the login screen itself) don't start up on older Intel GPUs. -- 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/1768232 Title: [HP Compaq dx2080 Microtower PC] Stuck at Ubuntu 18.04 logo while booting after installing Status in mutter package in Ubuntu: Confirmed Bug description: My system stuck at ubuntu logo while booting. This issue occurred only after installing it, not when I choose 'Try without Installing'. This doesn't happen in 16.04.4. xrandr xrandr: Failed to get size of gamma for output default Screen 0: minimum 1024 x 768, current 1024 x 768, maximum 1024 x 768 default connected primary 1024x768+0+0 0mm x 0mm 1024x768 76.00* Output of sudo lshw -c display *-display UNCLAIMED description: VGA compatible controller product: 82945G/GZ Integrated Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 02 width: 32 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list configuration: latency=0 resources: memory:e200-e207 ioport:c000(size=8) memory:d000-dfff memory:e208-e20b memory:c-d WORKAROUND: Using the following kernel boot parameter allows me to boot but the maximum resolution is limited to 1024x768: nomodeset WORKAROUND: Edit the file /etc/gdm3/custom.conf and change: #WaylandEnable=false to: WaylandEnable=false ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 1 17:16:20 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 82945G/GZ Integrated Graphics Controller [103c:302a] InstallationDate: Installed on 2018-05-01 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Hewlett-Packard HP dx2080 MT(KS826PA) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=7ec4f610-9b62-44f3-867d-01abd93de14d ro quiet splash nomodeset vt.handoff=1 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) XorgConf: Section "Device" Identifier "Intel Graphics" Driver "intel" Option "AccelMethod" "uxa" EndSection dmi.bios.date: 11/28/2007 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: V1.03 dmi.board.name: 0AD8h dmi.board.vendor: Board Manufacturer dmi.chassis.asset.tag: INA8100LFY dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrV1.03:bd11/28/2007:svnHewlett-Packard:pnHPdx2080MT(KS826PA):pvr:rvnBoardManufacturer:rn0AD8h:rvr:cvnHewlett-Packard:ct3:cvr: dmi.product.name: HP dx2080 MT(KS826PA) dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91+git1804271336.50426f~oibaf~b version.libgl1-mesa-dri: libgl1-mesa-dri 18.2~git1804301930.1c5f4f~oibaf~b version.libgl1-mesa-glx: libgl1-mesa-glx 18.2~git1804301930.1c5f4f~oibaf~b version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-
[Touch-packages] [Bug 1767124] Re: bluetoothd crashed with SIGILL in agent_get() from adapter_register()
I can't find any other reports of this crash globally. But also the stack in comment #3 may be wrong. Please upgrade to Ubuntu 18.04 if you can. Otherwise there is little we can do (also because the upstream BlueZ developers won't want to help while you're on an old version). -- 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/1767124 Title: bluetoothd crashed with SIGILL in agent_get() from adapter_register() Status in bluez package in Ubuntu: New Bug description: systemctl status bluetooth.service ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: failed (Result: core-dump) since Don 2018-04-26 16:16:36 CEST; 2min 25s ago Docs: man:bluetoothd(8) Process: 1458 ExecStart=/usr/lib/bluetooth/bluetoothd (code=dumped, signal=ILL) Main PID: 1458 (code=dumped, signal=ILL) Status: "Running" Apr 26 16:16:35 tiger systemd[1]: Starting Bluetooth service... Apr 26 16:16:35 tiger bluetoothd[1458]: Bluetooth daemon 5.37 Apr 26 16:16:35 tiger systemd[1]: Started Bluetooth service. Apr 26 16:16:35 tiger bluetoothd[1458]: Starting SDP server Apr 26 16:16:35 tiger bluetoothd[1458]: Bluetooth management interface 1.14 initialized Apr 26 16:16:36 tiger systemd[1]: bluetooth.service: Main process exited, code=dumped, status=4/ILL Apr 26 16:16:36 tiger systemd[1]: bluetooth.service: Unit entered failed state. Apr 26 16:16:36 tiger systemd[1]: bluetooth.service: Failed with result 'core-dump'. Apr 26 16:16:36 tiger systemd[1]: bluetooth.service: Start request repeated too quickly. Apr 26 16:16:36 tiger systemd[1]: Failed to start Bluetooth service. sudo gdb /usr/lib/bluetooth/bluetoothd ... Program received signal SIGILL, Illegal instruction. agent_get (owner=owner@entry=0x0) at src/agent.c:267 267 src/agent.c: Datei oder Verzeichnis nicht gefunden. (gdb) bt #0 agent_get (owner=owner@entry=0x0) at src/agent.c:267 #1 0x555d861b in adapter_register (adapter=0x5587fed0) at src/adapter.c:7434 #2 read_info_complete (status=, length=, param=, user_data=0x5587fed0) at src/adapter.c:7897 #3 0x55602656 in request_complete (mgmt=mgmt@entry=0x55879ef0, status=, opcode=opcode@entry=4, index=index@entry=0, length=length@entry=280, param=0x55879f79) at src/shared/mgmt.c:261 #4 0x5560311c in can_read_data (io=, user_data=0x55879ef0) at src/shared/mgmt.c:353 #5 0x5560ee25 in watch_callback (channel=, cond=, user_data=) at src/shared/io-glib.c:170 #6 0x77b1004a in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x77b103f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x77b10712 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x5557009d in main (argc=1, argv=0x7fffe658) at src/main.c:687 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1767124/+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 1775187] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1775187/+attachment/5149215/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1775187 Title: bluetooth headset gets imitatively disconnected Status in bluez package in Ubuntu: Incomplete Bug description: I upgraded from artful to bionic (just run apt update && apt upgrade and rebooted before testing the below) and since then my sennheiser pxc550 was immediately disconnected after a connect. Jun 05 15:18:49 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] backend-native.c: Device doesnt exist for /org/bluez/hci0/dev_00_16_94_22_21_D8 Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Headset Voice gateway replied with an error: org.bluez.Error.InvalidArguments, Unable to handle new connection Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:52 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:18:53 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:53 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:55 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:19:07 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:23 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:39 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) [...same message a few more time until I had a new version installed ...] I since then applied the patch from https://bugzilla.redhat.com/show_bug.cgi?id=1534857 -> https://marc.info/?l=linux-bluetooth&m=151801178209679&q=raw to bluez (apt source bluez -> patch -> dpkg-buildpackage ... > sudo dpkg -i ../*.deb) and now my headset works again. --- ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-11-09 (209 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20FWCTO1WW Package: bluez 5.48-0ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-22-generic root=UUID=128d75b0-64fc-468a-95fc-0aaf631bf4fe ro rootflags=subvol=@ quiet splash cgroup_enable=memory swapaccount=1 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Tags: third-party-packages bionic Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bluetooth cdrom dip docker lpadmin plugdev sambashare sudo systemd-journal wireshark _MarkForUpload: True 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: 20FWCTO1WW 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:pn20FWCTO1WW:pvrThinkPadT460p:rvnLENOVO:rn20FWCTO1WW:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FWCTO1WW dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: E4:A7:A0:14:18:46 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:4394393 acl:135 sco:0 events:618416 errors:0 TX bytes:524957211 acl:614106 sco:0 commands:2823 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1775187/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages P
[Touch-packages] [Bug 1775187] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1775187/+attachment/5149221/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1775187 Title: bluetooth headset gets imitatively disconnected Status in bluez package in Ubuntu: Incomplete Bug description: I upgraded from artful to bionic (just run apt update && apt upgrade and rebooted before testing the below) and since then my sennheiser pxc550 was immediately disconnected after a connect. Jun 05 15:18:49 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] backend-native.c: Device doesnt exist for /org/bluez/hci0/dev_00_16_94_22_21_D8 Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Headset Voice gateway replied with an error: org.bluez.Error.InvalidArguments, Unable to handle new connection Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:52 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:18:53 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:53 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:55 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:19:07 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:23 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:39 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) [...same message a few more time until I had a new version installed ...] I since then applied the patch from https://bugzilla.redhat.com/show_bug.cgi?id=1534857 -> https://marc.info/?l=linux-bluetooth&m=151801178209679&q=raw to bluez (apt source bluez -> patch -> dpkg-buildpackage ... > sudo dpkg -i ../*.deb) and now my headset works again. --- ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-11-09 (209 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20FWCTO1WW Package: bluez 5.48-0ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-22-generic root=UUID=128d75b0-64fc-468a-95fc-0aaf631bf4fe ro rootflags=subvol=@ quiet splash cgroup_enable=memory swapaccount=1 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Tags: third-party-packages bionic Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bluetooth cdrom dip docker lpadmin plugdev sambashare sudo systemd-journal wireshark _MarkForUpload: True 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: 20FWCTO1WW 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:pn20FWCTO1WW:pvrThinkPadT460p:rvnLENOVO:rn20FWCTO1WW:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FWCTO1WW dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: E4:A7:A0:14:18:46 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:4394393 acl:135 sco:0 events:618416 errors:0 TX bytes:524957211 acl:614106 sco:0 commands:2823 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1775187/+subscriptions -- Mailing list: https://launchpad.net/~touch-packag
[Touch-packages] [Bug 1775187] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1775187/+attachment/5149222/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1775187 Title: bluetooth headset gets imitatively disconnected Status in bluez package in Ubuntu: Incomplete Bug description: I upgraded from artful to bionic (just run apt update && apt upgrade and rebooted before testing the below) and since then my sennheiser pxc550 was immediately disconnected after a connect. Jun 05 15:18:49 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] backend-native.c: Device doesnt exist for /org/bluez/hci0/dev_00_16_94_22_21_D8 Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Headset Voice gateway replied with an error: org.bluez.Error.InvalidArguments, Unable to handle new connection Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:52 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:18:53 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:53 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:55 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:19:07 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:23 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:39 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) [...same message a few more time until I had a new version installed ...] I since then applied the patch from https://bugzilla.redhat.com/show_bug.cgi?id=1534857 -> https://marc.info/?l=linux-bluetooth&m=151801178209679&q=raw to bluez (apt source bluez -> patch -> dpkg-buildpackage ... > sudo dpkg -i ../*.deb) and now my headset works again. --- ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-11-09 (209 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20FWCTO1WW Package: bluez 5.48-0ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-22-generic root=UUID=128d75b0-64fc-468a-95fc-0aaf631bf4fe ro rootflags=subvol=@ quiet splash cgroup_enable=memory swapaccount=1 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Tags: third-party-packages bionic Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bluetooth cdrom dip docker lpadmin plugdev sambashare sudo systemd-journal wireshark _MarkForUpload: True 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: 20FWCTO1WW 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:pn20FWCTO1WW:pvrThinkPadT460p:rvnLENOVO:rn20FWCTO1WW:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FWCTO1WW dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: E4:A7:A0:14:18:46 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:4394393 acl:135 sco:0 events:618416 errors:0 TX bytes:524957211 acl:614106 sco:0 commands:2823 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1775187/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Pos
[Touch-packages] [Bug 1775187] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1775187/+attachment/5149218/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1775187 Title: bluetooth headset gets imitatively disconnected Status in bluez package in Ubuntu: Incomplete Bug description: I upgraded from artful to bionic (just run apt update && apt upgrade and rebooted before testing the below) and since then my sennheiser pxc550 was immediately disconnected after a connect. Jun 05 15:18:49 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] backend-native.c: Device doesnt exist for /org/bluez/hci0/dev_00_16_94_22_21_D8 Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Headset Voice gateway replied with an error: org.bluez.Error.InvalidArguments, Unable to handle new connection Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:52 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:18:53 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:53 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:55 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:19:07 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:23 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:39 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) [...same message a few more time until I had a new version installed ...] I since then applied the patch from https://bugzilla.redhat.com/show_bug.cgi?id=1534857 -> https://marc.info/?l=linux-bluetooth&m=151801178209679&q=raw to bluez (apt source bluez -> patch -> dpkg-buildpackage ... > sudo dpkg -i ../*.deb) and now my headset works again. --- ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-11-09 (209 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20FWCTO1WW Package: bluez 5.48-0ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-22-generic root=UUID=128d75b0-64fc-468a-95fc-0aaf631bf4fe ro rootflags=subvol=@ quiet splash cgroup_enable=memory swapaccount=1 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Tags: third-party-packages bionic Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bluetooth cdrom dip docker lpadmin plugdev sambashare sudo systemd-journal wireshark _MarkForUpload: True 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: 20FWCTO1WW 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:pn20FWCTO1WW:pvrThinkPadT460p:rvnLENOVO:rn20FWCTO1WW:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FWCTO1WW dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: E4:A7:A0:14:18:46 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:4394393 acl:135 sco:0 events:618416 errors:0 TX bytes:524957211 acl:614106 sco:0 commands:2823 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1775187/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Pos
[Touch-packages] [Bug 1775187] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1775187/+attachment/5149217/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1775187 Title: bluetooth headset gets imitatively disconnected Status in bluez package in Ubuntu: Incomplete Bug description: I upgraded from artful to bionic (just run apt update && apt upgrade and rebooted before testing the below) and since then my sennheiser pxc550 was immediately disconnected after a connect. Jun 05 15:18:49 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] backend-native.c: Device doesnt exist for /org/bluez/hci0/dev_00_16_94_22_21_D8 Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Headset Voice gateway replied with an error: org.bluez.Error.InvalidArguments, Unable to handle new connection Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:52 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:18:53 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:53 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:55 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:19:07 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:23 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:39 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) [...same message a few more time until I had a new version installed ...] I since then applied the patch from https://bugzilla.redhat.com/show_bug.cgi?id=1534857 -> https://marc.info/?l=linux-bluetooth&m=151801178209679&q=raw to bluez (apt source bluez -> patch -> dpkg-buildpackage ... > sudo dpkg -i ../*.deb) and now my headset works again. --- ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-11-09 (209 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20FWCTO1WW Package: bluez 5.48-0ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-22-generic root=UUID=128d75b0-64fc-468a-95fc-0aaf631bf4fe ro rootflags=subvol=@ quiet splash cgroup_enable=memory swapaccount=1 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Tags: third-party-packages bionic Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bluetooth cdrom dip docker lpadmin plugdev sambashare sudo systemd-journal wireshark _MarkForUpload: True 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: 20FWCTO1WW 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:pn20FWCTO1WW:pvrThinkPadT460p:rvnLENOVO:rn20FWCTO1WW:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FWCTO1WW dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: E4:A7:A0:14:18:46 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:4394393 acl:135 sco:0 events:618416 errors:0 TX bytes:524957211 acl:614106 sco:0 commands:2823 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1775187/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : to
[Touch-packages] [Bug 1583801] Re: No sound via headphones (headset) when Ubuntu boots with them plugged in
** Changed in: pulseaudio Status: Unknown => Confirmed ** Changed in: pulseaudio Importance: Unknown => Medium -- 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/1583801 Title: No sound via headphones (headset) when Ubuntu boots with them plugged in Status in PulseAudio: Confirmed Status in alsa-driver package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: The bug is twofold, first when computer boots if the headset (headphones with built-in mic, one audio jack) is plugged in, then there is no sound (via headphones or otherwise). If you plug headphones out and back in, then it usually works as expected. The second scenario is the same, except that plugging out and back in again doesn't help. In that case, I just restart the laptop, then plug them back in again and it works. In all cases, microphone works. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crunch 3248 F pulseaudio CurrentDesktop: Unity Date: Thu May 19 22:13:20 2016 InstallationDate: Installed on 2016-05-07 (12 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crunch 3248 F pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_Type: No sound at all Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1583801/+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 1775187] getfacl.txt
apport information ** Attachment added: "getfacl.txt" https://bugs.launchpad.net/bugs/1775187/+attachment/5149224/+files/getfacl.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1775187 Title: bluetooth headset gets imitatively disconnected Status in bluez package in Ubuntu: Incomplete Bug description: I upgraded from artful to bionic (just run apt update && apt upgrade and rebooted before testing the below) and since then my sennheiser pxc550 was immediately disconnected after a connect. Jun 05 15:18:49 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] backend-native.c: Device doesnt exist for /org/bluez/hci0/dev_00_16_94_22_21_D8 Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Headset Voice gateway replied with an error: org.bluez.Error.InvalidArguments, Unable to handle new connection Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:52 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:18:53 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:53 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:55 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:19:07 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:23 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:39 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) [...same message a few more time until I had a new version installed ...] I since then applied the patch from https://bugzilla.redhat.com/show_bug.cgi?id=1534857 -> https://marc.info/?l=linux-bluetooth&m=151801178209679&q=raw to bluez (apt source bluez -> patch -> dpkg-buildpackage ... > sudo dpkg -i ../*.deb) and now my headset works again. --- ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-11-09 (209 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20FWCTO1WW Package: bluez 5.48-0ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-22-generic root=UUID=128d75b0-64fc-468a-95fc-0aaf631bf4fe ro rootflags=subvol=@ quiet splash cgroup_enable=memory swapaccount=1 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Tags: third-party-packages bionic Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bluetooth cdrom dip docker lpadmin plugdev sambashare sudo systemd-journal wireshark _MarkForUpload: True 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: 20FWCTO1WW 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:pn20FWCTO1WW:pvrThinkPadT460p:rvnLENOVO:rn20FWCTO1WW:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FWCTO1WW dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: E4:A7:A0:14:18:46 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:4394393 acl:135 sco:0 events:618416 errors:0 TX bytes:524957211 acl:614106 sco:0 commands:2823 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1775187/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to
[Touch-packages] [Bug 1775187] Re: bluetooth headset gets imitatively disconnected
apport information ** Tags added: apport-collected bionic third-party-packages ** Description changed: I upgraded from artful to bionic (just run apt update && apt upgrade and rebooted before testing the below) and since then my sennheiser pxc550 was immediately disconnected after a connect. Jun 05 15:18:49 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] backend-native.c: Device doesnt exist for /org/bluez/hci0/dev_00_16_94_22_21_D8 Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Headset Voice gateway replied with an error: org.bluez.Error.InvalidArguments, Unable to handle new connection Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:52 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:18:53 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:53 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:55 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:19:07 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:23 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:39 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) [...same message a few more time until I had a new version installed ...] I since then applied the patch from https://bugzilla.redhat.com/show_bug.cgi?id=1534857 -> https://marc.info/?l=linux-bluetooth&m=151801178209679&q=raw to bluez (apt source bluez -> patch -> dpkg-buildpackage ... > sudo dpkg -i ../*.deb) and now my headset works again. + --- + ApportVersion: 2.20.9-0ubuntu7.1 + Architecture: amd64 + CurrentDesktop: GNOME + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2017-11-09 (209 days ago) + InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) + InterestingModules: rfcomm bnep btusb bluetooth + MachineType: LENOVO 20FWCTO1WW + Package: bluez 5.48-0ubuntu3 + PackageArchitecture: amd64 + ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-22-generic root=UUID=128d75b0-64fc-468a-95fc-0aaf631bf4fe ro rootflags=subvol=@ quiet splash cgroup_enable=memory swapaccount=1 vt.handoff=1 + ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 + Tags: third-party-packages bionic + Uname: Linux 4.15.0-22-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm bluetooth cdrom dip docker lpadmin plugdev sambashare sudo systemd-journal wireshark + _MarkForUpload: True + 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: 20FWCTO1WW + 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:pn20FWCTO1WW:pvrThinkPadT460p:rvnLENOVO:rn20FWCTO1WW:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: + dmi.product.family: ThinkPad T460p + dmi.product.name: 20FWCTO1WW + dmi.product.version: ThinkPad T460p + dmi.sys.vendor: LENOVO + hciconfig: + hci0:Type: Primary Bus: USB + BD Address: E4:A7:A0:14:18:46 ACL MTU: 1021:4 SCO MTU: 96:6 + UP RUNNING PSCAN ISCAN + RX bytes:4394393 acl:135 sco:0 events:618416 errors:0 + TX bytes:524957211 acl:614106 sco:0 commands:2823 errors:0 ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1775187/+attachment/5149214/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1775187 Title: bluetooth headset gets imitatively disconnected Status in bluez package in Ubuntu: Incomplete Bug description: I upgraded from artful to bionic (just run apt update && apt upgrade and rebooted befo
[Touch-packages] [Bug 1775187] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1775187/+attachment/5149216/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1775187 Title: bluetooth headset gets imitatively disconnected Status in bluez package in Ubuntu: Incomplete Bug description: I upgraded from artful to bionic (just run apt update && apt upgrade and rebooted before testing the below) and since then my sennheiser pxc550 was immediately disconnected after a connect. Jun 05 15:18:49 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] backend-native.c: Device doesnt exist for /org/bluez/hci0/dev_00_16_94_22_21_D8 Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Headset Voice gateway replied with an error: org.bluez.Error.InvalidArguments, Unable to handle new connection Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:52 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:18:53 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:53 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:55 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:19:07 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:23 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:39 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) [...same message a few more time until I had a new version installed ...] I since then applied the patch from https://bugzilla.redhat.com/show_bug.cgi?id=1534857 -> https://marc.info/?l=linux-bluetooth&m=151801178209679&q=raw to bluez (apt source bluez -> patch -> dpkg-buildpackage ... > sudo dpkg -i ../*.deb) and now my headset works again. --- ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-11-09 (209 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20FWCTO1WW Package: bluez 5.48-0ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-22-generic root=UUID=128d75b0-64fc-468a-95fc-0aaf631bf4fe ro rootflags=subvol=@ quiet splash cgroup_enable=memory swapaccount=1 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Tags: third-party-packages bionic Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bluetooth cdrom dip docker lpadmin plugdev sambashare sudo systemd-journal wireshark _MarkForUpload: True 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: 20FWCTO1WW 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:pn20FWCTO1WW:pvrThinkPadT460p:rvnLENOVO:rn20FWCTO1WW:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FWCTO1WW dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: E4:A7:A0:14:18:46 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:4394393 acl:135 sco:0 events:618416 errors:0 TX bytes:524957211 acl:614106 sco:0 commands:2823 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1775187/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : to
[Touch-packages] [Bug 1775187] Re: bluetooth headset gets imitatively disconnected
** Changed in: bluez (Ubuntu) Status: Incomplete => New -- 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/1775187 Title: bluetooth headset gets imitatively disconnected Status in bluez package in Ubuntu: New Bug description: I upgraded from artful to bionic (just run apt update && apt upgrade and rebooted before testing the below) and since then my sennheiser pxc550 was immediately disconnected after a connect. Jun 05 15:18:49 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] backend-native.c: Device doesnt exist for /org/bluez/hci0/dev_00_16_94_22_21_D8 Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Headset Voice gateway replied with an error: org.bluez.Error.InvalidArguments, Unable to handle new connection Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:52 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:18:53 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:53 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:55 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:19:07 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:23 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:39 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) [...same message a few more time until I had a new version installed ...] I since then applied the patch from https://bugzilla.redhat.com/show_bug.cgi?id=1534857 -> https://marc.info/?l=linux-bluetooth&m=151801178209679&q=raw to bluez (apt source bluez -> patch -> dpkg-buildpackage ... > sudo dpkg -i ../*.deb) and now my headset works again. --- ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-11-09 (209 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20FWCTO1WW Package: bluez 5.48-0ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-22-generic root=UUID=128d75b0-64fc-468a-95fc-0aaf631bf4fe ro rootflags=subvol=@ quiet splash cgroup_enable=memory swapaccount=1 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Tags: third-party-packages bionic Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bluetooth cdrom dip docker lpadmin plugdev sambashare sudo systemd-journal wireshark _MarkForUpload: True 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: 20FWCTO1WW 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:pn20FWCTO1WW:pvrThinkPadT460p:rvnLENOVO:rn20FWCTO1WW:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FWCTO1WW dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: E4:A7:A0:14:18:46 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:4394393 acl:135 sco:0 events:618416 errors:0 TX bytes:524957211 acl:614106 sco:0 commands:2823 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1775187/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-p
[Touch-packages] [Bug 1768232] Re: [HP Compaq dx2080 Microtower PC] Stuck at Ubuntu 18.04 logo while booting after installing
** Changed in: xorg (Ubuntu) Status: Incomplete => Fix Released -- 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/1768232 Title: [HP Compaq dx2080 Microtower PC] Stuck at Ubuntu 18.04 logo while booting after installing Status in xorg package in Ubuntu: Fix Released Bug description: My system stuck at ubuntu logo while booting. This issue occurred only after installing it, not when I choose 'Try without Installing'. This doesn't happen in 16.04.4. xrandr xrandr: Failed to get size of gamma for output default Screen 0: minimum 1024 x 768, current 1024 x 768, maximum 1024 x 768 default connected primary 1024x768+0+0 0mm x 0mm 1024x768 76.00* Output of sudo lshw -c display *-display UNCLAIMED description: VGA compatible controller product: 82945G/GZ Integrated Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 02 width: 32 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list configuration: latency=0 resources: memory:e200-e207 ioport:c000(size=8) memory:d000-dfff memory:e208-e20b memory:c-d WORKAROUND: Using the following kernel boot parameter allows me to boot but the maximum resolution is limited to 1024x768: nomodeset WORKAROUND: Edit the file /etc/gdm3/custom.conf and change: #WaylandEnable=false to: WaylandEnable=false ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 1 17:16:20 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 82945G/GZ Integrated Graphics Controller [103c:302a] InstallationDate: Installed on 2018-05-01 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Hewlett-Packard HP dx2080 MT(KS826PA) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=7ec4f610-9b62-44f3-867d-01abd93de14d ro quiet splash nomodeset vt.handoff=1 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) XorgConf: Section "Device" Identifier "Intel Graphics" Driver "intel" Option "AccelMethod" "uxa" EndSection dmi.bios.date: 11/28/2007 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: V1.03 dmi.board.name: 0AD8h dmi.board.vendor: Board Manufacturer dmi.chassis.asset.tag: INA8100LFY dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrV1.03:bd11/28/2007:svnHewlett-Packard:pnHPdx2080MT(KS826PA):pvr:rvnBoardManufacturer:rn0AD8h:rvr:cvnHewlett-Packard:ct3:cvr: dmi.product.name: HP dx2080 MT(KS826PA) dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91+git1804271336.50426f~oibaf~b version.libgl1-mesa-dri: libgl1-mesa-dri 18.2~git1804301930.1c5f4f~oibaf~b version.libgl1-mesa-glx: libgl1-mesa-glx 18.2~git1804301930.1c5f4f~oibaf~b version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1768232/+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 1775187] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1775187/+attachment/5149219/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1775187 Title: bluetooth headset gets imitatively disconnected Status in bluez package in Ubuntu: Incomplete Bug description: I upgraded from artful to bionic (just run apt update && apt upgrade and rebooted before testing the below) and since then my sennheiser pxc550 was immediately disconnected after a connect. Jun 05 15:18:49 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] backend-native.c: Device doesnt exist for /org/bluez/hci0/dev_00_16_94_22_21_D8 Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Headset Voice gateway replied with an error: org.bluez.Error.InvalidArguments, Unable to handle new connection Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:52 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:18:53 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:53 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:55 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:19:07 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:23 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:39 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) [...same message a few more time until I had a new version installed ...] I since then applied the patch from https://bugzilla.redhat.com/show_bug.cgi?id=1534857 -> https://marc.info/?l=linux-bluetooth&m=151801178209679&q=raw to bluez (apt source bluez -> patch -> dpkg-buildpackage ... > sudo dpkg -i ../*.deb) and now my headset works again. --- ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-11-09 (209 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20FWCTO1WW Package: bluez 5.48-0ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-22-generic root=UUID=128d75b0-64fc-468a-95fc-0aaf631bf4fe ro rootflags=subvol=@ quiet splash cgroup_enable=memory swapaccount=1 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Tags: third-party-packages bionic Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bluetooth cdrom dip docker lpadmin plugdev sambashare sudo systemd-journal wireshark _MarkForUpload: True 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: 20FWCTO1WW 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:pn20FWCTO1WW:pvrThinkPadT460p:rvnLENOVO:rn20FWCTO1WW:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FWCTO1WW dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: E4:A7:A0:14:18:46 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:4394393 acl:135 sco:0 events:618416 errors:0 TX bytes:524957211 acl:614106 sco:0 commands:2823 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1775187/+subscriptions -- Mailing list: https://launchpad.net/~touc
[Touch-packages] [Bug 1775187] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1775187/+attachment/5149223/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1775187 Title: bluetooth headset gets imitatively disconnected Status in bluez package in Ubuntu: Incomplete Bug description: I upgraded from artful to bionic (just run apt update && apt upgrade and rebooted before testing the below) and since then my sennheiser pxc550 was immediately disconnected after a connect. Jun 05 15:18:49 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] backend-native.c: Device doesnt exist for /org/bluez/hci0/dev_00_16_94_22_21_D8 Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Headset Voice gateway replied with an error: org.bluez.Error.InvalidArguments, Unable to handle new connection Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:52 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:18:53 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:53 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:55 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:19:07 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:23 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:39 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) [...same message a few more time until I had a new version installed ...] I since then applied the patch from https://bugzilla.redhat.com/show_bug.cgi?id=1534857 -> https://marc.info/?l=linux-bluetooth&m=151801178209679&q=raw to bluez (apt source bluez -> patch -> dpkg-buildpackage ... > sudo dpkg -i ../*.deb) and now my headset works again. --- ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-11-09 (209 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20FWCTO1WW Package: bluez 5.48-0ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-22-generic root=UUID=128d75b0-64fc-468a-95fc-0aaf631bf4fe ro rootflags=subvol=@ quiet splash cgroup_enable=memory swapaccount=1 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Tags: third-party-packages bionic Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bluetooth cdrom dip docker lpadmin plugdev sambashare sudo systemd-journal wireshark _MarkForUpload: True 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: 20FWCTO1WW 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:pn20FWCTO1WW:pvrThinkPadT460p:rvnLENOVO:rn20FWCTO1WW:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FWCTO1WW dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: E4:A7:A0:14:18:46 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:4394393 acl:135 sco:0 events:618416 errors:0 TX bytes:524957211 acl:614106 sco:0 commands:2823 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1775187/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to :
[Touch-packages] [Bug 1775187] syslog.txt
apport information ** Attachment added: "syslog.txt" https://bugs.launchpad.net/bugs/1775187/+attachment/5149226/+files/syslog.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1775187 Title: bluetooth headset gets imitatively disconnected Status in bluez package in Ubuntu: Incomplete Bug description: I upgraded from artful to bionic (just run apt update && apt upgrade and rebooted before testing the below) and since then my sennheiser pxc550 was immediately disconnected after a connect. Jun 05 15:18:49 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] backend-native.c: Device doesnt exist for /org/bluez/hci0/dev_00_16_94_22_21_D8 Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Headset Voice gateway replied with an error: org.bluez.Error.InvalidArguments, Unable to handle new connection Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:52 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:18:53 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:53 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:55 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:19:07 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:23 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:39 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) [...same message a few more time until I had a new version installed ...] I since then applied the patch from https://bugzilla.redhat.com/show_bug.cgi?id=1534857 -> https://marc.info/?l=linux-bluetooth&m=151801178209679&q=raw to bluez (apt source bluez -> patch -> dpkg-buildpackage ... > sudo dpkg -i ../*.deb) and now my headset works again. --- ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-11-09 (209 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20FWCTO1WW Package: bluez 5.48-0ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-22-generic root=UUID=128d75b0-64fc-468a-95fc-0aaf631bf4fe ro rootflags=subvol=@ quiet splash cgroup_enable=memory swapaccount=1 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Tags: third-party-packages bionic Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bluetooth cdrom dip docker lpadmin plugdev sambashare sudo systemd-journal wireshark _MarkForUpload: True 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: 20FWCTO1WW 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:pn20FWCTO1WW:pvrThinkPadT460p:rvnLENOVO:rn20FWCTO1WW:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FWCTO1WW dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: E4:A7:A0:14:18:46 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:4394393 acl:135 sco:0 events:618416 errors:0 TX bytes:524957211 acl:614106 sco:0 commands:2823 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1775187/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to :
[Touch-packages] [Bug 1775337] Re: 18.04 Headphones detected, but not switched on automatically after startup
*** This bug is a duplicate of bug 1583801 *** https://bugs.launchpad.net/bugs/1583801 Good find. Let's use bug 1583801 and your upstream bug will be linked to that. It's still required. ** This bug has been marked a duplicate of bug 1583801 No sound via headphones (headset) when Ubuntu boots with them plugged in -- 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/1775337 Title: 18.04 Headphones detected, but not switched on automatically after startup Status in pulseaudio package in Ubuntu: New Bug description: Been this way since at least 15. Plug in your headphones, boot up your laptop. No sound. Speakers and headphones are disabled. Super annoying, you have to unplug and re- plug, and go through the stupid dialogue of "what are you trying to plug in?" which has no memory, and no defaults. Please, please, please, fix this Ubuntu team! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom1369 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Jun 6 02:28:13 2018 InstallationDate: Installed on 2018-04-26 (41 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/28/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.1 dmi.board.name: 0JHP5H dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.1:bd03/28/2018:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn0JHP5H:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.sys.vendor: Dell Inc. modified.conffile..etc.xdg.autostart.pulseaudio.desktop: [modified] mtime.conffile..etc.xdg.autostart.pulseaudio.desktop: 2018-05-26T14:25:02.708160 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1775337/+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 1775187] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1775187/+attachment/5149220/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1775187 Title: bluetooth headset gets imitatively disconnected Status in bluez package in Ubuntu: Incomplete Bug description: I upgraded from artful to bionic (just run apt update && apt upgrade and rebooted before testing the below) and since then my sennheiser pxc550 was immediately disconnected after a connect. Jun 05 15:18:49 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] backend-native.c: Device doesnt exist for /org/bluez/hci0/dev_00_16_94_22_21_D8 Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Headset Voice gateway replied with an error: org.bluez.Error.InvalidArguments, Unable to handle new connection Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:52 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:18:53 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:53 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:55 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:19:07 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:23 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:39 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) [...same message a few more time until I had a new version installed ...] I since then applied the patch from https://bugzilla.redhat.com/show_bug.cgi?id=1534857 -> https://marc.info/?l=linux-bluetooth&m=151801178209679&q=raw to bluez (apt source bluez -> patch -> dpkg-buildpackage ... > sudo dpkg -i ../*.deb) and now my headset works again. --- ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-11-09 (209 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20FWCTO1WW Package: bluez 5.48-0ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-22-generic root=UUID=128d75b0-64fc-468a-95fc-0aaf631bf4fe ro rootflags=subvol=@ quiet splash cgroup_enable=memory swapaccount=1 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Tags: third-party-packages bionic Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bluetooth cdrom dip docker lpadmin plugdev sambashare sudo systemd-journal wireshark _MarkForUpload: True 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: 20FWCTO1WW 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:pn20FWCTO1WW:pvrThinkPadT460p:rvnLENOVO:rn20FWCTO1WW:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FWCTO1WW dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: E4:A7:A0:14:18:46 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:4394393 acl:135 sco:0 events:618416 errors:0 TX bytes:524957211 acl:614106 sco:0 commands:2823 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1775187/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Pos
[Touch-packages] [Bug 1759961] Re: Update to 5.50 (mostly bug-fix release)
** Attachment added: "bluez_5.50-0ubuntu1.dsc" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1759961/+attachment/5149240/+files/bluez_5.50-0ubuntu1.dsc ** Summary changed: - Update to 5.50 (mostly bug-fix release) + Update to bluez 5.50 (mostly bug-fix release) ** Tags added: bluez-5.50 -- 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/1759961 Title: Update to bluez 5.50 (mostly bug-fix release) Status in bluez package in Ubuntu: In Progress Bug description: From upstream: http://www.bluez.org/release-of-bluez-5-49/ Release of BlueZ 5.49 This is mostly a bug fix release, with fixes to features such as AVCTP, OBEX, GATT and Mesh. There are however some notable new features also, such as improved heartbeat management support in meshctl as well as a new experimental ConnectDevice D-Bus method on the Adapter interface, which can be used for quick device object creation for testing purpose or when information about the device has been received over some Out-of-Band channel. Upstream changelog: https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/ChangeLog ver 5.49: Fix issue with configuring discoverable advertising flag. Fix issue with bearer selection and single mode controllers. Fix issue with Connect and ConnectProfile returning in progress. Fix issue with missing Paired property change when not bonded. Fix issue with storage for controllers without public address. Fix issue with handling AVCTP disconnecting the channel queue. Fix issue with not clearing connectable setting on power off. Fix issue with creating multiple mgmt socket instances. Fix issue with GATT server and BR/EDR only devices. Fix issue with InterfaceAdded event ordering. Add support for generic ConnectDevice method call. Add support for Mesh heartbeat client functionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1759961/+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 1755250] Re: backport statx syscall whitelist fix
This is indeed pretty important for some use-cases so we should try to come up with a reasonable solution. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1755250 Title: backport statx syscall whitelist fix Status in docker.io package in Ubuntu: New Status in libseccomp package in Ubuntu: New Bug description: Hello maintainer, The docker version 17.03 (bionic) in ubuntu doesn't allow the statx syscall which is needed to build qt >=5.10 applications: https://github.com/docker/for-linux/issues/208#issuecomment-372400859 Could this fix be backported in the ubuntu package ? https://github.com/moby/moby/pull/36417 regards, xan. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1755250/+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 1759961] Re: Update to 5.50 (mostly bug-fix release)
** Attachment added: "bluez_5.50-0ubuntu1.debian.tar.xz" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1759961/+attachment/5149239/+files/bluez_5.50-0ubuntu1.debian.tar.xz -- 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/1759961 Title: Update to bluez 5.50 (mostly bug-fix release) Status in bluez package in Ubuntu: In Progress Bug description: From upstream: http://www.bluez.org/release-of-bluez-5-49/ Release of BlueZ 5.49 This is mostly a bug fix release, with fixes to features such as AVCTP, OBEX, GATT and Mesh. There are however some notable new features also, such as improved heartbeat management support in meshctl as well as a new experimental ConnectDevice D-Bus method on the Adapter interface, which can be used for quick device object creation for testing purpose or when information about the device has been received over some Out-of-Band channel. Upstream changelog: https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/ChangeLog ver 5.49: Fix issue with configuring discoverable advertising flag. Fix issue with bearer selection and single mode controllers. Fix issue with Connect and ConnectProfile returning in progress. Fix issue with missing Paired property change when not bonded. Fix issue with storage for controllers without public address. Fix issue with handling AVCTP disconnecting the channel queue. Fix issue with not clearing connectable setting on power off. Fix issue with creating multiple mgmt socket instances. Fix issue with GATT server and BR/EDR only devices. Fix issue with InterfaceAdded event ordering. Add support for generic ConnectDevice method call. Add support for Mesh heartbeat client functionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1759961/+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 1759961] Re: Update to 5.50 (mostly bug-fix release)
** Attachment added: "bluez_5.50.orig.tar.xz" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1759961/+attachment/5149238/+files/bluez_5.50.orig.tar.xz -- 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/1759961 Title: Update to bluez 5.50 (mostly bug-fix release) Status in bluez package in Ubuntu: In Progress Bug description: From upstream: http://www.bluez.org/release-of-bluez-5-49/ Release of BlueZ 5.49 This is mostly a bug fix release, with fixes to features such as AVCTP, OBEX, GATT and Mesh. There are however some notable new features also, such as improved heartbeat management support in meshctl as well as a new experimental ConnectDevice D-Bus method on the Adapter interface, which can be used for quick device object creation for testing purpose or when information about the device has been received over some Out-of-Band channel. Upstream changelog: https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/ChangeLog ver 5.49: Fix issue with configuring discoverable advertising flag. Fix issue with bearer selection and single mode controllers. Fix issue with Connect and ConnectProfile returning in progress. Fix issue with missing Paired property change when not bonded. Fix issue with storage for controllers without public address. Fix issue with handling AVCTP disconnecting the channel queue. Fix issue with not clearing connectable setting on power off. Fix issue with creating multiple mgmt socket instances. Fix issue with GATT server and BR/EDR only devices. Fix issue with InterfaceAdded event ordering. Add support for generic ConnectDevice method call. Add support for Mesh heartbeat client functionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1759961/+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 1738838] Re: Bluetooth icon shows "Off" and the only option given below it is "Turn Off"
Maybe it's https://bugzilla.gnome.org/show_bug.cgi?id=789110 ? ** Bug watch added: GNOME Bug Tracker #789110 https://bugzilla.gnome.org/show_bug.cgi?id=789110 ** Bug watch added: GNOME Bug Tracker #789110 https://bugzilla.gnome.org/show_bug.cgi?id=789110 ** Changed in: gnome-bluetooth Importance: Medium => Unknown ** Changed in: gnome-bluetooth Status: Fix Released => Unknown ** No longer affects: bluez (Ubuntu) ** Also affects: gnome-shell via https://bugzilla.gnome.org/show_bug.cgi?id=789110 Importance: Unknown Status: Unknown ** No longer affects: gnome-control-center (Ubuntu) -- 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/1738838 Title: Bluetooth icon shows "Off" and the only option given below it is "Turn Off" Status in GNOME Bluetooth: Unknown Status in GNOME Shell: Unknown Status in gnome-bluetooth package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: See video. I have installed bluetooth, blueman, bluez but it makes no difference to a broken interface to control bluetooth under Gnome 17.10, as shown in the attached video. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: bluetooth 5.46-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 17 22:32:30 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-18 (30 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) InterestingModules: bnep btusb bluetooth MachineType: LENOVO 20BXCTO1WW PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic.efi.signed root=UUID=02bd5120-a925-442c-a0dd-1cce59920632 ro quiet splash psmouse.synaptics_intertouch=0 vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/06/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JBET54WW (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET54WW(1.19):bd11/06/2015:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450s dmi.product.name: 20BXCTO1WW dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO hciconfig: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-bluetooth/+bug/1738838/+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 1775018] Comment bridged from LTC Bugzilla
--- Comment From patrick.ste...@de.ibm.com 2018-06-06 05:16 EDT--- > Is this upstreamed already? What is the upstream commit id? As i said in #1, openssl upstream/master and 1.1.0 backports are not affected. The bug was introduced with the 1.0.2 backport (of upstream commit 96530eea93d27e536f4e93956256cf8dcda7d469). > An explanation of the effects of the bug on users Using openssl tls 1.2 with aes-gcm cipher-suites on s390 can lead to unexpected authentication failures. > justification for backporting the fix to the stable release Fix unexpected authentication failures when using openssl tls 1.2 with aes-gcm cipher-suites on s390. > In addition, it is helpful, but not required, to include an explanation of how the upload fixes this bug After openssl 1.0.2 most data structures were made opaque. Backporting to 1.0.2 means reversing this process. In case of this backport, accidentially the wrong structure member was assessed in one place in the s390 platform-specific aes-gcm tls code path. The uploaded fixes this bug by accessing the right structure member. > detailed instructions how to reproduce the bug > these should allow someone who is not familiar with the affected package to > reproduce the bug and verify that the updated package fixes the problem. Apply original backport patches to openssl 1.0.2 source. Build and run the test suite (make test). Observe test case failure when testing aes- gcm cipher suites. Apply the uploaded fix and repeat. Observe the test suite pass. > [Regression Potential] ... I dont see any risk for regression regarding this fix. > Specifically how to test/excercise this code path? As noted above, the openssl test suite exercises this code path (at least with high probability i.e., i hit the problem at 5/5 runs). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1775018 Title: Fix for openssl 1.0.2 backport Status in Ubuntu on IBM z Systems: Triaged Status in openssl package in Ubuntu: New Bug description: This is a fix for this feature's backport to openssl 1.0.2 ( 1.1.0 and upstream code are not affected ). Original LP ticket : https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1743750 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1775018/+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 1775369] [NEW] package libssl1.0.0:i386 1.0.2g-1ubuntu4.12 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
Public bug reported: Occured while dist upgrade 14.04 lts to 16.04 lts ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libssl1.0.0:i386 1.0.2g-1ubuntu4.12 ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128 Uname: Linux 4.4.0-127-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Wed Jun 6 09:40:01 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2016-02-17 (840 days ago) InstallationMedia: Ubuntu-GNOME 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: i386 RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: openssl Title: package libssl1.0.0:i386 1.0.2g-1ubuntu4.12 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: Upgraded to xenial on 2017-12-01 (186 days ago) ** Affects: openssl (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 openssl in Ubuntu. https://bugs.launchpad.net/bugs/1775369 Title: package libssl1.0.0:i386 1.0.2g-1ubuntu4.12 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 Status in openssl package in Ubuntu: New Bug description: Occured while dist upgrade 14.04 lts to 16.04 lts ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libssl1.0.0:i386 1.0.2g-1ubuntu4.12 ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128 Uname: Linux 4.4.0-127-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Wed Jun 6 09:40:01 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2016-02-17 (840 days ago) InstallationMedia: Ubuntu-GNOME 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: i386 RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: openssl Title: package libssl1.0.0:i386 1.0.2g-1ubuntu4.12 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: Upgraded to xenial on 2017-12-01 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1775369/+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 1688575] Update Released
The verification of the Stable Release Update for openldap has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1688575 Title: Segmentation fault on a slave slapd (sync replication with kerberos authentication) Status in openldap: Fix Released Status in openldap package in Ubuntu: Fix Released Status in openldap source package in Xenial: Fix Released Bug description: [Impact] Concurrent SASL authentications could trigger a segfault. This was observed by the bug reporter during replication from a master to a slave, and can be reproduced with a test program. The fix is applied upstream, see comment #13. [Test Case] * Create a fresh xenial VM or container and login. Update the apt repositories: sudo apt update * Create a local directory and cd into it: mkdir test && cd test * Download the test attachments from this bug: Makefile, sasltest.c and testscript: wget https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1688575/+attachment/5139678/+files/Makefile https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1688575/+attachment/5139679/+files/sasltest.c https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1688575/+attachment/5139680/+files/testscript * Build with $ apt install libsasl2-dev libldap2-dev $ make * Execute the testscript with sudo once. It shall fail at the very end with a core dump: sudo sh ./testscript (...) sasltest: sasltest.c:70: bind_thread: Assertion `rc == LDAP_SUCCESS' failed. Aborted (core dumped) * Export this var: export LDAPSASL_SECPROPS=none * Run the actual test script a few more times to confirm the crasH: $ ./sasltest rc = -6 (Unknown authentication method) sasltest: sasltest.c:70: bind_thread: Assertion `rc == LDAP_SUCCESS' failed. rc = -6 (Unknown authentication method) sasltest: sasltest.c:70: bind_thread: Assertion `rc == LDAP_SUCCESS' failed. rc = -6 (Unknown authentication method) sasltest: sasltest.c:70: bind_thread: Assertion `rc == LDAP_SUCCESS' failed. Aborted (core dumped) * Install the updated packages from proposed * Run ./sasltest again. Make sure the LDAPSASL_SECPROPS var is still exported: $ echo $LDAPSASL_SECPROPS none $ ./sasltest $ This time the test completes without crashing. [Regression Potential] This is SASL authentication, and with kerberos nonetheless (in the case of the bug reporter). I suspect not many people deploy this due to its complexity. The ones that have such a setup, however, tend to know what they are doing, so if they say the problem is fixed for them, I believe it is. About this particular change, it's committed upstream and also in debian, and @rtandy was kind enough to provide a sample test script that exhibits the problem. [Other Info] Since the fix is applied upstream and in Debian, there shouldn't be additional surprises here. [Original description] I have a slapd problem on a freshly installed 16.04 machine: slapd[17107]: segfault at 1a ip 7f3c12c79f55 sp 7f3c03c2d080 error 4 in libsasl2.so.2.0.25[7f3c12c72000+19000] I'm using the server as Slave LDAP-Server and sync replication with kerberos authentication. The service either starts and runs successfully or it fails with segmentation fault or 100% CPU. Maybe an useful info, I'm replicating two databases. When I deactivate syncrepl for one of them (doesn't matter which one) the problem is not occuring. Linux xxx 4.4.0-75-generic #96-Ubuntu SMP Thu Apr 20 09:56:33 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux slapd 2.4.42+dfsg-2ubuntu3.1 libsasl2-2:amd64 2.1.26.dfsg1-14build1 libsasl2-modules:amd64 2.1.26.dfsg1-14build1 libsasl2-modules-gssapi-mit:amd64 2.1.26.dfsg1-14build1 GDB debug: Starting program: /usr/sbin/slapd -h "ldap:/// ldaps:/// ldapi:///" -u openldap -g openldap -f /etc/ldap/slapd.conf -d 256 [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 590c82ab @(#) $OpenLDAP: slapd (Ubuntu) (May 11 2016 16:12:05) $ buildd@lgw01-10:/build/openldap-mF7Kfq/openldap-2.4.42+dfsg/debian/build/servers/slapd 590c82ab slapd starting [New Thread 0x7f2e96b7b700 (LWP 42139)] [New Thread 0x7f2e9637a700 (LWP 42140)] [New Thread 0x7f2e95b79700 (LWP 42141)] [New Thread 0x7f2e95378700 (LWP 42142)] [New Thread 0x7f2e94b77700 (LWP 42143)] 590c82ba slap_client_connect: URI=ldap://xxx ldap_sasl_interactive_bind_s
[Touch-packages] [Bug 1688575] Re: Segmentation fault on a slave slapd (sync replication with kerberos authentication)
This bug was fixed in the package openldap - 2.4.42+dfsg-2ubuntu3.3 --- openldap (2.4.42+dfsg-2ubuntu3.3) xenial; urgency=medium [ Ryan Tandy ] * d/p/ITS-8648-check-result-of-ldap_int_initialize-in-ldap.patch, d/p/ITS-8648-init-SASL-library-in-global-init.patch: Import upstream patches to fix memory corruption caused by calling sasl_client_init() multiple times and possibly concurrently. (ITS#8648) (LP: #1688575) -- Andreas Hasenack Tue, 22 May 2018 10:54:12 -0300 ** Changed in: openldap (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1688575 Title: Segmentation fault on a slave slapd (sync replication with kerberos authentication) Status in openldap: Fix Released Status in openldap package in Ubuntu: Fix Released Status in openldap source package in Xenial: Fix Released Bug description: [Impact] Concurrent SASL authentications could trigger a segfault. This was observed by the bug reporter during replication from a master to a slave, and can be reproduced with a test program. The fix is applied upstream, see comment #13. [Test Case] * Create a fresh xenial VM or container and login. Update the apt repositories: sudo apt update * Create a local directory and cd into it: mkdir test && cd test * Download the test attachments from this bug: Makefile, sasltest.c and testscript: wget https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1688575/+attachment/5139678/+files/Makefile https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1688575/+attachment/5139679/+files/sasltest.c https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1688575/+attachment/5139680/+files/testscript * Build with $ apt install libsasl2-dev libldap2-dev $ make * Execute the testscript with sudo once. It shall fail at the very end with a core dump: sudo sh ./testscript (...) sasltest: sasltest.c:70: bind_thread: Assertion `rc == LDAP_SUCCESS' failed. Aborted (core dumped) * Export this var: export LDAPSASL_SECPROPS=none * Run the actual test script a few more times to confirm the crasH: $ ./sasltest rc = -6 (Unknown authentication method) sasltest: sasltest.c:70: bind_thread: Assertion `rc == LDAP_SUCCESS' failed. rc = -6 (Unknown authentication method) sasltest: sasltest.c:70: bind_thread: Assertion `rc == LDAP_SUCCESS' failed. rc = -6 (Unknown authentication method) sasltest: sasltest.c:70: bind_thread: Assertion `rc == LDAP_SUCCESS' failed. Aborted (core dumped) * Install the updated packages from proposed * Run ./sasltest again. Make sure the LDAPSASL_SECPROPS var is still exported: $ echo $LDAPSASL_SECPROPS none $ ./sasltest $ This time the test completes without crashing. [Regression Potential] This is SASL authentication, and with kerberos nonetheless (in the case of the bug reporter). I suspect not many people deploy this due to its complexity. The ones that have such a setup, however, tend to know what they are doing, so if they say the problem is fixed for them, I believe it is. About this particular change, it's committed upstream and also in debian, and @rtandy was kind enough to provide a sample test script that exhibits the problem. [Other Info] Since the fix is applied upstream and in Debian, there shouldn't be additional surprises here. [Original description] I have a slapd problem on a freshly installed 16.04 machine: slapd[17107]: segfault at 1a ip 7f3c12c79f55 sp 7f3c03c2d080 error 4 in libsasl2.so.2.0.25[7f3c12c72000+19000] I'm using the server as Slave LDAP-Server and sync replication with kerberos authentication. The service either starts and runs successfully or it fails with segmentation fault or 100% CPU. Maybe an useful info, I'm replicating two databases. When I deactivate syncrepl for one of them (doesn't matter which one) the problem is not occuring. Linux xxx 4.4.0-75-generic #96-Ubuntu SMP Thu Apr 20 09:56:33 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux slapd 2.4.42+dfsg-2ubuntu3.1 libsasl2-2:amd64 2.1.26.dfsg1-14build1 libsasl2-modules:amd64 2.1.26.dfsg1-14build1 libsasl2-modules-gssapi-mit:amd64 2.1.26.dfsg1-14build1 GDB debug: Starting program: /usr/sbin/slapd -h "ldap:/// ldaps:/// ldapi:///" -u openldap -g openldap -f /etc/ldap/slapd.conf -d 256 [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 590c82ab @(#) $OpenLDAP: slapd (Ubuntu) (May 11 2016 16:12:05) $ buildd@lgw01-10:/build/openldap-mF7Kfq/openldap-2.4.42+dfsg/debian/build/servers/slapd 590c82ab slapd starting [New Thread 0x7f2e96b7b700 (LWP 42139)] [New Thread 0x7f2e9637a700 (LWP 42140)] [New Thread 0x7f2e95b79700 (LWP 42141)] [New Thread 0x7f2e95378700 (LWP
[Touch-packages] [Bug 1775380] Re: package lvm2 2.02.176-4.1ubuntu3 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1775380 Title: package lvm2 2.02.176-4.1ubuntu3 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1 Status in lvm2 package in Ubuntu: New Bug description: Failed to restart lvm2-lvmetad.service: Unit lvm2-lvmetad.socket is masked. invoke-rc.d: initscript lvm2-lvmetad, action "restart" failed. ● lvm2-lvmetad.service - LVM2 metadata daemon Loaded: loaded (/lib/systemd/system/lvm2-lvmetad.service; static; vendor preset: enabled) Active: inactive (dead) Docs: man:lvmetad(8) dpkg: error processing package lvm2 (--configure): installed lvm2 package post-installation script subprocess returned error exit status 1 Processing triggers for initramfs-tools (0.130ubuntu3) ... update-initramfs: Generating /boot/initrd.img-4.15.0-22-generic Errors were encountered while processing: lvm2 E: Sub-process /usr/bin/dpkg returned an error code (1) all time that I try to update or remove or install something receive error like above ProblemType: Package DistroRelease: Ubuntu 18.04 Package: lvm2 2.02.176-4.1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 AptOrdering: NULL: ConfigurePending Architecture: amd64 Date: Wed Jun 6 13:19:37 2018 ErrorMessage: installed lvm2 package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: lvm2 Title: package lvm2 2.02.176-4.1ubuntu3 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1775380/+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 1775380] [NEW] package lvm2 2.02.176-4.1ubuntu3 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1
Public bug reported: Failed to restart lvm2-lvmetad.service: Unit lvm2-lvmetad.socket is masked. invoke-rc.d: initscript lvm2-lvmetad, action "restart" failed. ● lvm2-lvmetad.service - LVM2 metadata daemon Loaded: loaded (/lib/systemd/system/lvm2-lvmetad.service; static; vendor preset: enabled) Active: inactive (dead) Docs: man:lvmetad(8) dpkg: error processing package lvm2 (--configure): installed lvm2 package post-installation script subprocess returned error exit status 1 Processing triggers for initramfs-tools (0.130ubuntu3) ... update-initramfs: Generating /boot/initrd.img-4.15.0-22-generic Errors were encountered while processing: lvm2 E: Sub-process /usr/bin/dpkg returned an error code (1) all time that I try to update or remove or install something receive error like above ProblemType: Package DistroRelease: Ubuntu 18.04 Package: lvm2 2.02.176-4.1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 AptOrdering: NULL: ConfigurePending Architecture: amd64 Date: Wed Jun 6 13:19:37 2018 ErrorMessage: installed lvm2 package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: lvm2 Title: package lvm2 2.02.176-4.1ubuntu3 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lvm2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1775380 Title: package lvm2 2.02.176-4.1ubuntu3 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1 Status in lvm2 package in Ubuntu: New Bug description: Failed to restart lvm2-lvmetad.service: Unit lvm2-lvmetad.socket is masked. invoke-rc.d: initscript lvm2-lvmetad, action "restart" failed. ● lvm2-lvmetad.service - LVM2 metadata daemon Loaded: loaded (/lib/systemd/system/lvm2-lvmetad.service; static; vendor preset: enabled) Active: inactive (dead) Docs: man:lvmetad(8) dpkg: error processing package lvm2 (--configure): installed lvm2 package post-installation script subprocess returned error exit status 1 Processing triggers for initramfs-tools (0.130ubuntu3) ... update-initramfs: Generating /boot/initrd.img-4.15.0-22-generic Errors were encountered while processing: lvm2 E: Sub-process /usr/bin/dpkg returned an error code (1) all time that I try to update or remove or install something receive error like above ProblemType: Package DistroRelease: Ubuntu 18.04 Package: lvm2 2.02.176-4.1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 AptOrdering: NULL: ConfigurePending Architecture: amd64 Date: Wed Jun 6 13:19:37 2018 ErrorMessage: installed lvm2 package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: lvm2 Title: package lvm2 2.02.176-4.1ubuntu3 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1775380/+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 1773045] Re: Radiance/gtk-3.20/gtk-main.css attempts to import nonexistent gnome-builder.css
In /usr/share/themes/Radiance/gtk-3.20/apps create the link
sudo ln -s gedit.css gnome-builder.css
I did not see any difference in gedit, but the error message disappears.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1773045
Title:
Radiance/gtk-3.20/gtk-main.css attempts to import nonexistent gnome-
builder.css
Status in Ubuntu theme:
New
Status in ubuntu-themes package in Ubuntu:
Confirmed
Bug description:
The file /usr/share/themes/Radiance/gtk-3.20/gtk-main.css contains the
line
@import url("apps/gnome-builder.css");
But this file does not exist in this package or any other, as far as I
can tell from apt-file. This triggers an annoying warning when
running various applications (e.g. evince):
(evince:12714): Gtk-WARNING **: 18:41:45.136: Theme parsing error:
gtk-main.css:73:38: Failed to import: Error opening file
/usr/share/themes/Radiance/gtk-3.20/apps/gnome-builder.css: No such
file or directory
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: light-themes 16.10+18.04.20180421.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Wed May 23 18:58:41 2018
PackageArchitecture: all
SourcePackage: ubuntu-themes
UpgradeStatus: Upgraded to bionic on 2018-05-23 (1 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1773045/+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 1775392] [NEW] at-spi-bus-launcher makes Xorg crash when resuming from suspend
Public bug reported: If at-spi2-core is installed, when resuming from suspend messages like these are logged in systemd journal: at-spi-bus-launcher[31720]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0" at-spi-bus-launcher[31720]: after 8065 requests (8065 known processed) with 0 events remaining. The number of requests vary, it can reach more than 15000. Depending on the number of requests, the Xorg server crashes with SIGBUS. Depending on the exact moment Xorg crashes, when lightdm manages to recover, it shows a login greeter, or worst case scenario, it can't recover, a black screen is shown and the desptop session doesn't start. It took me a long time to discover the cause. The visible symptom was: once in a while when resuming from suspend, I got a login greeter instead of an unlock greeter, or a black screen which forced me to power down. Investigating, I found out that whenever that happened, there was a Xorg core left behind. Looking at the journal messages before the crash, there was always that flood of at-spi2-core requests. So I uninstalled at-spi2-core and Xorg never crashed anymore. This is a quite severe bug, which makes it impossible to use at- spi2-core. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: at-spi2-core (not installed) ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Jun 6 09:10:12 2018 InstallationDate: Installed on 2018-04-28 (38 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: at-spi2-core UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: at-spi2-core (Ubuntu) Importance: Undecided Status: New ** Tags: crash sigbus xorg -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1775392 Title: at-spi-bus-launcher makes Xorg crash when resuming from suspend Status in at-spi2-core package in Ubuntu: New Bug description: If at-spi2-core is installed, when resuming from suspend messages like these are logged in systemd journal: at-spi-bus-launcher[31720]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0" at-spi-bus-launcher[31720]: after 8065 requests (8065 known processed) with 0 events remaining. The number of requests vary, it can reach more than 15000. Depending on the number of requests, the Xorg server crashes with SIGBUS. Depending on the exact moment Xorg crashes, when lightdm manages to recover, it shows a login greeter, or worst case scenario, it can't recover, a black screen is shown and the desptop session doesn't start. It took me a long time to discover the cause. The visible symptom was: once in a while when resuming from suspend, I got a login greeter instead of an unlock greeter, or a black screen which forced me to power down. Investigating, I found out that whenever that happened, there was a Xorg core left behind. Looking at the journal messages before the crash, there was always that flood of at-spi2-core requests. So I uninstalled at-spi2-core and Xorg never crashed anymore. This is a quite severe bug, which makes it impossible to use at- spi2-core. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: at-spi2-core (not installed) ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Jun 6 09:10:12 2018 InstallationDate: Installed on 2018-04-28 (38 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: at-spi2-core UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1775392/+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 1768905] Re: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed
** Changed in: menu (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1768905 Title: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in apt package in Ubuntu: Incomplete Status in menu package in Ubuntu: Fix Released Status in apt source package in Xenial: New Status in menu source package in Xenial: In Progress Status in apt source package in Artful: New Status in menu source package in Artful: New Status in apt source package in Bionic: New Status in menu source package in Bionic: New Status in menu package in Debian: New Bug description: [Impact] Breaks some upgrades, depending on install order. [Test case] N/A. After consultation with the dpkg maintainer and investigating the situation, it's reasonably safe to assume that noawait is the right thing to do: * the intended use for the trigger is to run _after_ packages with .menu files are configured, not before; therefore * the file trigger is triggered manually from the postinst again, discussion has been that the file trigger is not actually needed. [Regression potential] Menu might not be updated correctly [Original bug report] I get this error when I update to 18.04 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: menu 2.1.47ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Thu May 3 16:51:28 2018 Dependencies: gcc-8-base 8-20180414-1ubuntu2 libc6 2.27-3ubuntu1 libgcc1 1:8-20180414-1ubuntu2 libstdc++6 8-20180414-1ubuntu2 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2018-04-11 (22 days ago) InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 (20180106) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: menu Title: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to bionic on 2018-05-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1768905/+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 1772607] Re: Mesa 18.0.5 stable release
** Changed in: libglvnd (Ubuntu Bionic) Assignee: (unassigned) => Timo Aaltonen (tjaalton) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1772607 Title: Mesa 18.0.5 stable release Status in libglvnd package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in libglvnd source package in Bionic: In Progress Status in mesa source package in Bionic: Fix Committed Bug description: [Impact] Ubuntu 18.04 shipped with mesa 18.0.0~rc5, and deserves to get the last point release of the series. [Test Case] Check on intel/radeon hw that things still work fine. [Regression potential] Mesa stable releases are tested by vendor CI systems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1772607/+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 1771102] Re: 17.10->18.04 LTS hangs, CPU stalls in apt-pkg cache
Does anyone know of anything I can do to move forward? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1771102 Title: 17.10->18.04 LTS hangs, CPU stalls in apt-pkg cache Status in python-apt package in Ubuntu: New Bug description: When I do as root: do-release-upgrade The bionic tarball is downloaded and the python based "bionic" process is forked. On the screen I see the first "Reading cache..." message and then the process spikes the CPU to 100% where it stays there forever (I waited 15-20 minutes and there was no change in CPU state). Here is the dist-upgrade log file: 2018-05-14 07:17:19,308 INFO uname information: 'Linux kitt 4.13.0-41-generic #46-Ubuntu SMP Wed May 2 13:38:30 UTC 2018 x86_64' 2018-05-14 07:17:19,594 INFO apt version: '1.5.1' 2018-05-14 07:17:19,594 INFO python version: '3.6.3 (default, Oct 3 2017, 21:45:48) [GCC 7.2.0]' 2018-05-14 07:17:19,596 INFO release-upgrader version '18.04.17' started 2018-05-14 07:17:19,600 INFO locale: 'en_US' 'UTF-8' 2018-05-14 07:17:19,605 INFO screen could not be run 2018-05-14 07:17:19,744 DEBUG Using 'DistUpgradeViewText' view 2018-05-14 07:17:19,788 DEBUG enable dpkg --force-overwrite 2018-05-14 07:17:19,817 DEBUG creating statefile: '/var/log/dist-upgrade/apt-clone_system_state.tar.gz' strace output of the "bionic" process: $ sudo strace -f -p 6469 strace: Process 6469 attached with 3 threads [pid 6546] restart_syscall(<... resuming interrupted poll ...> [pid 6547] restart_syscall(<... resuming interrupted poll ...>strace: [ Process PID=6469 runs in x32 mode. ] top output: PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 6469 root 20 0 270048 33108 15728 R 99.7 0.1 0:38.85 bionic 6555 pisymbol 20 0 46736 4376 3344 R 0.7 0.0 0:00.04 top Looking at this further, it seems that the installer sets the the "rootdir=/" when it initiates the python-apt's Cache class. This hangs. I can reproduce this by simply changing it's test code to pass rootdir="/" and it hangs. It sorta smells like a deadlock issue though deep in the C++ module (apt_pkg) that backs the python one (GetLock?). But I'm not 100% sure. This behavior is seen on my 32-core Threadripper machine (AMD64). This is 17.10 latest with: $ dpkg -l python-apt libapt-pkg5.0 Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---= ii libapt-pkg5.0:amd641.5.1 amd64package management runtime library ii python-apt 1.4.0~beta3build2 amd64Python interface to libapt-pkg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1771102/+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 1768905] Re: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Hello Nikkus, or anyone else affected, Accepted menu into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/menu/2.1.47ubuntu1.16.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: menu (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-xenial ** Changed in: menu (Ubuntu Artful) Status: New => Fix Committed ** Tags added: verification-needed-artful -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1768905 Title: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in apt package in Ubuntu: Incomplete Status in menu package in Ubuntu: Fix Released Status in apt source package in Xenial: New Status in menu source package in Xenial: Fix Committed Status in apt source package in Artful: New Status in menu source package in Artful: Fix Committed Status in apt source package in Bionic: New Status in menu source package in Bionic: Fix Committed Status in menu package in Debian: New Bug description: [Impact] Breaks some upgrades, depending on install order. [Test case] N/A. After consultation with the dpkg maintainer and investigating the situation, it's reasonably safe to assume that noawait is the right thing to do: * the intended use for the trigger is to run _after_ packages with .menu files are configured, not before; therefore * the file trigger is triggered manually from the postinst again, discussion has been that the file trigger is not actually needed. [Regression potential] Menu might not be updated correctly [Original bug report] I get this error when I update to 18.04 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: menu 2.1.47ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Thu May 3 16:51:28 2018 Dependencies: gcc-8-base 8-20180414-1ubuntu2 libc6 2.27-3ubuntu1 libgcc1 1:8-20180414-1ubuntu2 libstdc++6 8-20180414-1ubuntu2 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2018-04-11 (22 days ago) InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 (20180106) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: menu Title: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to bionic on 2018-05-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1768905/+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 1768905] Please test proposed package
Hello Nikkus, or anyone else affected, Accepted menu into artful-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/menu/2.1.47ubuntu1.17.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-artful to verification-done-artful. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-artful. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: menu (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1768905 Title: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in apt package in Ubuntu: Incomplete Status in menu package in Ubuntu: Fix Released Status in apt source package in Xenial: New Status in menu source package in Xenial: Fix Committed Status in apt source package in Artful: New Status in menu source package in Artful: Fix Committed Status in apt source package in Bionic: New Status in menu source package in Bionic: Fix Committed Status in menu package in Debian: New Bug description: [Impact] Breaks some upgrades, depending on install order. [Test case] N/A. After consultation with the dpkg maintainer and investigating the situation, it's reasonably safe to assume that noawait is the right thing to do: * the intended use for the trigger is to run _after_ packages with .menu files are configured, not before; therefore * the file trigger is triggered manually from the postinst again, discussion has been that the file trigger is not actually needed. [Regression potential] Menu might not be updated correctly [Original bug report] I get this error when I update to 18.04 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: menu 2.1.47ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Thu May 3 16:51:28 2018 Dependencies: gcc-8-base 8-20180414-1ubuntu2 libc6 2.27-3ubuntu1 libgcc1 1:8-20180414-1ubuntu2 libstdc++6 8-20180414-1ubuntu2 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2018-04-11 (22 days ago) InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 (20180106) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: menu Title: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to bionic on 2018-05-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1768905/+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 1768905] Please test proposed package
Hello Nikkus, or anyone else affected, Accepted menu into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/menu/2.1.47ubuntu2.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1768905 Title: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in apt package in Ubuntu: Incomplete Status in menu package in Ubuntu: Fix Released Status in apt source package in Xenial: New Status in menu source package in Xenial: Fix Committed Status in apt source package in Artful: New Status in menu source package in Artful: Fix Committed Status in apt source package in Bionic: New Status in menu source package in Bionic: Fix Committed Status in menu package in Debian: New Bug description: [Impact] Breaks some upgrades, depending on install order. [Test case] N/A. After consultation with the dpkg maintainer and investigating the situation, it's reasonably safe to assume that noawait is the right thing to do: * the intended use for the trigger is to run _after_ packages with .menu files are configured, not before; therefore * the file trigger is triggered manually from the postinst again, discussion has been that the file trigger is not actually needed. [Regression potential] Menu might not be updated correctly [Original bug report] I get this error when I update to 18.04 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: menu 2.1.47ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Thu May 3 16:51:28 2018 Dependencies: gcc-8-base 8-20180414-1ubuntu2 libc6 2.27-3ubuntu1 libgcc1 1:8-20180414-1ubuntu2 libstdc++6 8-20180414-1ubuntu2 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2018-04-11 (22 days ago) InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 (20180106) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: menu Title: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to bionic on 2018-05-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1768905/+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 1722185] Re: Crash installing packages using debconf
> I see the second PackageKit pull request has not yet been approved by upstream - could we get someone reviewing it and merging before we proceed? I think the SRU remains blocked on this question? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1722185 Title: Crash installing packages using debconf Status in packagekit package in Ubuntu: Fix Released Status in packagekit source package in Bionic: In Progress Bug description: [Impact] Installing .deb package via PackageKit (e.g. using GNOME Software) don't work reliably when the packages use debconf. This is due to a faulty implementation of debconf handling in PackageKit. [Test Case] 1. Download opera deb file from opera.com 2. Run the file to launch gnome-software 3. Install it 4. Proceed with the debconf prompt Expected result: A debconf dialog appears asking if you want to "update Opera with the rest of the system?". The dialog closes when completed and the package is installed. Actual result: The dialog shows, but never closes and becomes unresponsive. Force closing the dialog causes a crash. [Regression Potential] The change is quite large, so there is a reasonable chance of introducing new bugs in debconf handling. However, the existing code has some obviously wrong codepaths, so the new code is probably a lower risk than the existing code. Crash reports: https://errors.ubuntu.com/problem/f111546905209e7288c7f8ba5f8f19eea4d97bad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1722185/+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 1769400] Re: suspend no longer functions after update to 18.04
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pm-utils (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1769400 Title: suspend no longer functions after update to 18.04 Status in pm-utils package in Ubuntu: Confirmed Bug description: Suspend does not complete. The system stops in an unknown state without fully suspending and without ability to wake. Problem began on upgrade to Ubuntu 18.04 LTS. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pm-utils 1.4.1-17 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Sat May 5 13:31:03 2018 InstallationDate: Installed on 2015-03-25 (1137 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) PackageArchitecture: all SourcePackage: pm-utils UpgradeStatus: Upgraded to bionic on 2018-05-04 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1769400/+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 1765923] Re: Nvidia driver leads to black screen on bionic 18.04 SDDM LightDM bug?
I had this issue and resolved it by modifying the 10-nvidia.conf file to add the line: Option "PrimaryGPU" "true" The problem that I had was that the system would boot with the Intel GPU and once it go to the X-Display it attempted to use the NVidia drivers which were not properly initialized. ** Attachment added: "10-nvidia.conf" https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1765923/+attachment/5149387/+files/10-nvidia.conf -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1765923 Title: Nvidia driver leads to black screen on bionic 18.04 SDDM LightDM bug? Status in apt package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in sddm package in Ubuntu: Confirmed Bug description: Using the April 19th daily build of Kubuntu 18.04 I installed the Nvidia drivers via the following command. sudo ubuntu-drivers autoinstall The install process proceeds fine and after a logout process I get a black screen. I tried this on the April 17th daily build of bionic and a reboot also results in a black screen. The following is a question which was submitted by a Ubuntu 17.10 user: QUOTE After I installed latest Nvidia driver-390 and tried to boot after shutting down once I faced a black screen problem. since, I'm a noob but something related to nvidia drivers couldn't be started. Then I followed https://askubuntu.com/a/968692/802490 While following these instructions re-installing of nvidia drivers failed. The only things that worked is purging the drivers and changing "WaylandEnable=false" in (/etc/gdm3/custom.conf). Now, I want to re-install nvidia drivers again but I'm afraid that this will lead to that problem again. Can anyone help in re-installing the driver such that I won't face that problem? END QUOTE THE WORK AROUND Use Ctrl-Alt-f6 to get to a login prompt. Login run "startx" The x server will start and Nvidia drivers will function. THE PROBLEM When I try to run SDDM I get an error (Which I will try to copy down to add to this bug when I am on a different computer than the one I am reporting the bug about.). Installing lightDM does not work... it installs but is either will not run or will not actually start a x session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1765923/+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 1765285] Re: systemd-journald crashed with SIGABRT in __GI___pthread_timedjoin_ex()
*** This bug is a duplicate of bug 1754214 *** https://bugs.launchpad.net/bugs/1754214 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- 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/1765285 Title: systemd-journald crashed with SIGABRT in __GI___pthread_timedjoin_ex() Status in systemd package in Ubuntu: Confirmed Bug description: ??? ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu8 ProcVersionSignature: Ubuntu 4.15.0-17.18-generic 4.15.17 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 Date: Thu Apr 19 06:46:33 2018 ExecutablePath: /lib/systemd/systemd-journald InstallationDate: Installed on 2018-03-21 (29 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180319) Lsusb: Bus 002 Device 002: ID 0781:5591 SanDisk Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: innotek GmbH VirtualBox ProcCmdline: /lib/systemd/systemd-journald ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-17-generic root=UUID=624ad287-69d9-4615-a6a0-b840f3ff8c6d ro quiet splash Signal: 6 SourcePackage: systemd StacktraceTop: __GI___pthread_timedjoin_ex (threadid=139717271447296, thread_return=0x0, abstime=0x0, block=) at pthread_join_common.c:89 ?? () from /lib/systemd/libsystemd-shared-237.so ?? () from /lib/systemd/libsystemd-shared-237.so journal_file_append_object () from /lib/systemd/libsystemd-shared-237.so ?? () from /lib/systemd/libsystemd-shared-237.so SystemdDelta: [MASKED] /etc/systemd/system/samba-ad-dc.service → /lib/systemd/system/samba-ad-dc.service [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 3 overridden configuration files found. Title: systemd-journald crashed with SIGABRT in __GI___pthread_timedjoin_ex() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1765285/+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 1759961] Re: Update to bluez 5.50
** Summary changed: - Update to bluez 5.50 (mostly bug-fix release) + Update to bluez 5.50 -- 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/1759961 Title: Update to bluez 5.50 Status in bluez package in Ubuntu: In Progress Bug description: From upstream: http://www.bluez.org/release-of-bluez-5-49/ Release of BlueZ 5.49 This is mostly a bug fix release, with fixes to features such as AVCTP, OBEX, GATT and Mesh. There are however some notable new features also, such as improved heartbeat management support in meshctl as well as a new experimental ConnectDevice D-Bus method on the Adapter interface, which can be used for quick device object creation for testing purpose or when information about the device has been received over some Out-of-Band channel. Upstream changelog: https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/ChangeLog ver 5.49: Fix issue with configuring discoverable advertising flag. Fix issue with bearer selection and single mode controllers. Fix issue with Connect and ConnectProfile returning in progress. Fix issue with missing Paired property change when not bonded. Fix issue with storage for controllers without public address. Fix issue with handling AVCTP disconnecting the channel queue. Fix issue with not clearing connectable setting on power off. Fix issue with creating multiple mgmt socket instances. Fix issue with GATT server and BR/EDR only devices. Fix issue with InterfaceAdded event ordering. Add support for generic ConnectDevice method call. Add support for Mesh heartbeat client functionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1759961/+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 1765285] Re: systemd-journald crashed with SIGABRT in __GI___pthread_timedjoin_ex()
*** This bug is a duplicate of bug 1754214 *** https://bugs.launchpad.net/bugs/1754214 I think it is wrong that you won't tell me what's wrong with MY computer just because someone with wheel bits set found the problem first. -- 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/1765285 Title: systemd-journald crashed with SIGABRT in __GI___pthread_timedjoin_ex() Status in systemd package in Ubuntu: Confirmed Bug description: ??? ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu8 ProcVersionSignature: Ubuntu 4.15.0-17.18-generic 4.15.17 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 Date: Thu Apr 19 06:46:33 2018 ExecutablePath: /lib/systemd/systemd-journald InstallationDate: Installed on 2018-03-21 (29 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180319) Lsusb: Bus 002 Device 002: ID 0781:5591 SanDisk Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: innotek GmbH VirtualBox ProcCmdline: /lib/systemd/systemd-journald ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-17-generic root=UUID=624ad287-69d9-4615-a6a0-b840f3ff8c6d ro quiet splash Signal: 6 SourcePackage: systemd StacktraceTop: __GI___pthread_timedjoin_ex (threadid=139717271447296, thread_return=0x0, abstime=0x0, block=) at pthread_join_common.c:89 ?? () from /lib/systemd/libsystemd-shared-237.so ?? () from /lib/systemd/libsystemd-shared-237.so journal_file_append_object () from /lib/systemd/libsystemd-shared-237.so ?? () from /lib/systemd/libsystemd-shared-237.so SystemdDelta: [MASKED] /etc/systemd/system/samba-ad-dc.service → /lib/systemd/system/samba-ad-dc.service [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 3 overridden configuration files found. Title: systemd-journald crashed with SIGABRT in __GI___pthread_timedjoin_ex() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1765285/+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 1775426] [NEW] [MPOW, playback] fails after a while
Public bug reported: Since upgrade from xenial to bionic I'm having problems with sound via bluetooth, which is reproduced with a lot of glitches and very chocked. My bluetooth is integrated in the laptop motherboard and I'm using an mpow bluetooth headphone. As I said, whith the same laptop and headphone but xenial worked perfectly. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: amateo 2330 F pulseaudio /dev/snd/controlC1: amateo 2330 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Jun 6 18:17:37 2018 InstallationDate: Installed on 2018-05-14 (23 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: MPOW Symptom_PulseAudioLog: jun 06 17:35:29 amateo-EXCALIBUR dbus-daemon[1010]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.30' (uid=120 pid=1314 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") Symptom_Type: Sound works for a while, then breaks Title: [MPOW, playback] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/21/2014 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: h dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EXCALIBUR dmi.board.vendor: SLIMBOOK dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SLIMBOOK dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrh:bd11/21/2014:svnSLIMBOOK:pnEXCALIBUR:pvr1.0:rvnSLIMBOOK:rnEXCALIBUR:rvrType2-BoardVersion:cvnSLIMBOOK:ct10:cvrChassisVersion: dmi.product.family: Type1Family dmi.product.name: EXCALIBUR dmi.product.version: 1.0 dmi.sys.vendor: SLIMBOOK ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1775426 Title: [MPOW, playback] fails after a while Status in alsa-driver package in Ubuntu: New Bug description: Since upgrade from xenial to bionic I'm having problems with sound via bluetooth, which is reproduced with a lot of glitches and very chocked. My bluetooth is integrated in the laptop motherboard and I'm using an mpow bluetooth headphone. As I said, whith the same laptop and headphone but xenial worked perfectly. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: amateo 2330 F pulseaudio /dev/snd/controlC1: amateo 2330 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Jun 6 18:17:37 2018 InstallationDate: Installed on 2018-05-14 (23 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: MPOW Symptom_PulseAudioLog: jun 06 17:35:29 amateo-EXCALIBUR dbus-daemon[1010]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.30' (uid=120 pid=1314 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") Symptom_Type: Sound works for a while, then breaks Title: [MPOW, playback] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/21/2014 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: h dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EXCALIBUR dmi.board.vendor: SLIMBOOK dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SLIMBOOK dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrh:bd11/21/2014:svnSLIMBOOK:pnEXCALIBUR:pvr1.0:rvnSLIMBOOK:rnEXCALIBUR:rvrType2-BoardVersion:cvnSLIMBOOK:ct10:cvrChassisVersion: dmi.product.family: Type1Family dmi.product.name: EXCALIBUR dmi.product.version: 1.0 dmi.sys.vendor: SLIMBOOK To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1775426/+subscriptions -- Mailing list: https://launchpad.net/~touch-pa
[Touch-packages] [Bug 1775432] [NEW] Stackswitcher buttons in gnome-software are not themed alike
Public bug reported: In gnome-software, the theming of the stackswitcher buttons at the top 'Installed' and 'Updates' is different than 'All'. The 3D effect is only visible in 'All' when selected. The three buttons should have the same effect. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: light-themes 16.10+18.04.20180421.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: wl nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 6 18:38:01 2018 InstallationDate: Installed on 2018-06-03 (3 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-themes (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1775432 Title: Stackswitcher buttons in gnome-software are not themed alike Status in ubuntu-themes package in Ubuntu: New Bug description: In gnome-software, the theming of the stackswitcher buttons at the top 'Installed' and 'Updates' is different than 'All'. The 3D effect is only visible in 'All' when selected. The three buttons should have the same effect. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: light-themes 16.10+18.04.20180421.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: wl nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 6 18:38:01 2018 InstallationDate: Installed on 2018-06-03 (3 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1775432/+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 1775429] [NEW] Label in stackswitcher button is not bold when selected
Public bug reported: Steps: 1. Start gnome-software 2. Select and observe the stackswitcher buttons at the top: All, Installed and Updates The label in the stackswitcher button is not bald when selected. That behaviour is inconsistent with the pathbar in Nautilus, where the label is bald when selected. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: light-themes 16.10+18.04.20180421.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: wl nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 6 18:19:35 2018 InstallationDate: Installed on 2018-06-03 (3 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-themes (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1775429 Title: Label in stackswitcher button is not bold when selected Status in ubuntu-themes package in Ubuntu: New Bug description: Steps: 1. Start gnome-software 2. Select and observe the stackswitcher buttons at the top: All, Installed and Updates The label in the stackswitcher button is not bald when selected. That behaviour is inconsistent with the pathbar in Nautilus, where the label is bald when selected. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: light-themes 16.10+18.04.20180421.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: wl nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 6 18:19:35 2018 InstallationDate: Installed on 2018-06-03 (3 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1775429/+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 1772859] Re: Network Manager is not able to manage the devices on Ubuntu 18.04
Since the ticket was opened against 18.04, and since 18.04 installations come with and use netplan by default with again networkd as the default renderer (and not NetworkManager), NetworkManager just cannot work by default. If you want to work with NetworkManager on an 18.04 installation that's using netplan, the described re-configuration is needed and the renderer needs to be changed from networkd to NetworkManager - that's not a bug, that's intended and caused by the introduction of netplan (since about 17.10). With that change NetworkManager should be able to manage qdio devices (see end of comment #3 - devices are listed as managed). If you still have problems managing the devices _after_ doing the re- config there might be a bug, but I don't see that right now (but I for sure didn't covered your entire use case that I just don't know). We understand that behavior is now a bit different compared to other distributions. There were some bugs in the past on NetworkManager and netplan on previous Ubuntu releases, like the one mentioned by you in the bug description: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1638842 which is a duplicate of: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1676547 and already 'Fix Release' (since quite some time). And btw. comment 26: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1676547/comments/26 confirms that the above renderer change works. If issues still occur on other Ubuntu releases (not 18.04, but for example 16.04) that are not yet addressed in an LP bug, please open a separate bug on them. And if there are still issues managing qdio devices after the change above, we may address them is a separate ticket, too. -- 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/1772859 Title: Network Manager is not able to manage the devices on Ubuntu 18.04 Status in Ubuntu on IBM z Systems: Invalid Status in network-manager package in Ubuntu: Invalid Bug description: NetworkManager is not able to manage the devices on latest Ubuntu(18.04) ---uname output--- Linux (none) 4.15.0-12-generic #13-Ubuntu SMP Wed Mar 7 21:36:36 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = z14 s390 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. Install the latest Ubuntu(18.04) with Network Manager(1.10.4). 2. Configure a network device and login to the partition through ssh. 3. Now you can see the following output root@(none):~# nmcli d s DEVICE TYPE STATE CONNECTION eth0ethernet unmanaged -- eth1ethernet unmanaged -- lo loopback unmanaged -- Userspace tool common name: 1.10.6-2ubuntu1: amd64 arm64 armhf i386 ppc64el s390x The userspace tool has the following bit modes: 64-bit Userspace rpm: NetworkManager --version 1.10.4 Userspace tool obtained from project website: na Some more information about the issue: Network device has been configured manually after the image is up from Support Element(SE): - znetconf -a - cat /sys/bus/ccwgroup/drivers/qeth//if_name - ifconfig netmask 255.255.255.0 - route add default gw - SSH service has been configured This helped us to login to the Lpar. In Lpar - output of znetconf -c Device IDs TypeCard Type CHPID Drv. Name State - 0.0.1a80,0.0.1a81,0.0.1a82 1731/01 OSD_10GIG A8 qeth eth0 online 0.0.1810,0.0.1811,0.0.1812 1731/01 OSD_1000 D0 qeth eth1 online - output of nmcli c s root@(none):~# nmcli c s NAME UUID TYPE DEVICE - output of nmcli d s root@(none):~# nmcli d s DEVICE TYPE STATE CONNECTION eth0ethernet unmanaged -- eth1ethernet unmanaged -- lo loopback unmanaged -- * The above output shows that devices are not managed by nmcli After some investigation we found couple of suggestions like 1. Ubuntu(version <17.04): Creating an empty file(/etc/NetworkManager/conf.d/10-globally-managed-devices.conf) and restarting NM, solved the issue. 2. Ubuntu(version 17.10): Copying the said file(10-globally-managed-devices.conf) from /usr/lib to /etc/ and modifying the "unmanaged-devices" to none, resolved the issue. * link for reference: https://bugs.launchpad.net/ubuntu/+source /network-manager/+bug/1638842 For the latest version(18.04), none of the above solutions worked. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-sys
[Touch-packages] [Bug 1774843] Re: apport python exception handler messes up python3.7
** Also affects: python-apt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1774843 Title: apport python exception handler messes up python3.7 Status in apport package in Ubuntu: New Status in python-apt package in Ubuntu: Invalid Bug description: it seems apport installs an exception hook whenever running python3. This hook is apparently installed for python3.7 too. This exception handler has a dependency on apt_pkg, which is a binary that is not compatible with python3.7 it seems (you can't import it, see below) As a result, whenever I run a python3.7 script and run into an exception (which happens often when writing code), I get an additional exception in the exception handler + a copy of the original exception, so three stacktraces in total. A solution would be to only install the exception hook for the system python i.e. python3.6 $ lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 apport: 2.20.9-0ubuntu7 python-apt: 1.6.0 python3.7: 3.7.0~b3-1 Demo with a trivial error: $ python3 -c 'print hello' File "", line 1 print hello ^ SyntaxError: Missing parentheses in call to 'print'. Did you mean print(hello)? $ python3.7 -c 'print hello' File "", line 1 print hello ^ SyntaxError: Missing parentheses in call to 'print'. Did you mean print(hello)? Error in sys.excepthook: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 63, in apport_excepthook from apport.fileutils import likely_packaged, get_recent_crashes File "/usr/lib/python3/dist-packages/apport/__init__.py", line 5, in from apport.report import Report File "/usr/lib/python3/dist-packages/apport/report.py", line 30, in import apport.fileutils File "/usr/lib/python3/dist-packages/apport/fileutils.py", line 23, in from apport.packaging_impl import impl as packaging File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 24, in import apt File "/usr/lib/python3/dist-packages/apt/__init__.py", line 23, in import apt_pkg ModuleNotFoundError: No module named 'apt_pkg' Original exception was: File "", line 1 print hello ^ SyntaxError: Missing parentheses in call to 'print'. Did you mean print(hello)? Python 3.6.5 (default, Apr 1 2018, 05:46:30) [GCC 7.3.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> import sys >>> sys.excepthook >>> import apt_pkg >>> apt_pkg.__file__ '/usr/lib/python3/dist-packages/apt_pkg.cpython-36m-x86_64-linux-gnu.so' >>> Python 3.7.0b3 (default, Mar 30 2018, 04:35:22) [GCC 7.3.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> import sys >>> sys.excepthook >> import apt_pkg Traceback (most recent call last): File "", line 1, in ModuleNotFoundError: No module named 'apt_pkg' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1774843/+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 1774843] Re: apport python exception handler messes up python3.7
python 3.7 is not a supported version, hence modules are not built for it. ** Changed in: python-apt (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1774843 Title: apport python exception handler messes up python3.7 Status in apport package in Ubuntu: New Status in python-apt package in Ubuntu: Invalid Bug description: it seems apport installs an exception hook whenever running python3. This hook is apparently installed for python3.7 too. This exception handler has a dependency on apt_pkg, which is a binary that is not compatible with python3.7 it seems (you can't import it, see below) As a result, whenever I run a python3.7 script and run into an exception (which happens often when writing code), I get an additional exception in the exception handler + a copy of the original exception, so three stacktraces in total. A solution would be to only install the exception hook for the system python i.e. python3.6 $ lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 apport: 2.20.9-0ubuntu7 python-apt: 1.6.0 python3.7: 3.7.0~b3-1 Demo with a trivial error: $ python3 -c 'print hello' File "", line 1 print hello ^ SyntaxError: Missing parentheses in call to 'print'. Did you mean print(hello)? $ python3.7 -c 'print hello' File "", line 1 print hello ^ SyntaxError: Missing parentheses in call to 'print'. Did you mean print(hello)? Error in sys.excepthook: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 63, in apport_excepthook from apport.fileutils import likely_packaged, get_recent_crashes File "/usr/lib/python3/dist-packages/apport/__init__.py", line 5, in from apport.report import Report File "/usr/lib/python3/dist-packages/apport/report.py", line 30, in import apport.fileutils File "/usr/lib/python3/dist-packages/apport/fileutils.py", line 23, in from apport.packaging_impl import impl as packaging File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 24, in import apt File "/usr/lib/python3/dist-packages/apt/__init__.py", line 23, in import apt_pkg ModuleNotFoundError: No module named 'apt_pkg' Original exception was: File "", line 1 print hello ^ SyntaxError: Missing parentheses in call to 'print'. Did you mean print(hello)? Python 3.6.5 (default, Apr 1 2018, 05:46:30) [GCC 7.3.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> import sys >>> sys.excepthook >>> import apt_pkg >>> apt_pkg.__file__ '/usr/lib/python3/dist-packages/apt_pkg.cpython-36m-x86_64-linux-gnu.so' >>> Python 3.7.0b3 (default, Mar 30 2018, 04:35:22) [GCC 7.3.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> import sys >>> sys.excepthook >> import apt_pkg Traceback (most recent call last): File "", line 1, in ModuleNotFoundError: No module named 'apt_pkg' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1774843/+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 1774843] Re: apport python exception handler messes up python3.7
So apport needs to catch the exception and do nothing / not register an excepthook on unsupported python versions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1774843 Title: apport python exception handler messes up python3.7 Status in apport package in Ubuntu: New Status in python-apt package in Ubuntu: Invalid Bug description: it seems apport installs an exception hook whenever running python3. This hook is apparently installed for python3.7 too. This exception handler has a dependency on apt_pkg, which is a binary that is not compatible with python3.7 it seems (you can't import it, see below) As a result, whenever I run a python3.7 script and run into an exception (which happens often when writing code), I get an additional exception in the exception handler + a copy of the original exception, so three stacktraces in total. A solution would be to only install the exception hook for the system python i.e. python3.6 $ lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 apport: 2.20.9-0ubuntu7 python-apt: 1.6.0 python3.7: 3.7.0~b3-1 Demo with a trivial error: $ python3 -c 'print hello' File "", line 1 print hello ^ SyntaxError: Missing parentheses in call to 'print'. Did you mean print(hello)? $ python3.7 -c 'print hello' File "", line 1 print hello ^ SyntaxError: Missing parentheses in call to 'print'. Did you mean print(hello)? Error in sys.excepthook: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 63, in apport_excepthook from apport.fileutils import likely_packaged, get_recent_crashes File "/usr/lib/python3/dist-packages/apport/__init__.py", line 5, in from apport.report import Report File "/usr/lib/python3/dist-packages/apport/report.py", line 30, in import apport.fileutils File "/usr/lib/python3/dist-packages/apport/fileutils.py", line 23, in from apport.packaging_impl import impl as packaging File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 24, in import apt File "/usr/lib/python3/dist-packages/apt/__init__.py", line 23, in import apt_pkg ModuleNotFoundError: No module named 'apt_pkg' Original exception was: File "", line 1 print hello ^ SyntaxError: Missing parentheses in call to 'print'. Did you mean print(hello)? Python 3.6.5 (default, Apr 1 2018, 05:46:30) [GCC 7.3.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> import sys >>> sys.excepthook >>> import apt_pkg >>> apt_pkg.__file__ '/usr/lib/python3/dist-packages/apt_pkg.cpython-36m-x86_64-linux-gnu.so' >>> Python 3.7.0b3 (default, Mar 30 2018, 04:35:22) [GCC 7.3.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> import sys >>> sys.excepthook >> import apt_pkg Traceback (most recent call last): File "", line 1, in ModuleNotFoundError: No module named 'apt_pkg' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1774843/+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 1756238] Re: gdebi-gtk broken in 18.04 error: unable to read filedescriptor flags
Hello Mark-pcnetspec, or anyone else affected, Accepted vte2.91 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/vte2.91/0.52.2-1ubuntu1~18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: vte2.91 (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1756238 Title: gdebi-gtk broken in 18.04 error: unable to read filedescriptor flags Status in gdebi package in Ubuntu: Triaged Status in vte2.91 package in Ubuntu: Fix Released Status in vte2.91 source package in Bionic: Fix Committed Bug description: When using gdebi-gtk to install a .deb the install fails with the message:- dpkg: error: unable to read filedescriptor flags for : Bad file descriptor This only occurs via the gdebi-gtk GUI front end, packages install perfectly if done via the CLI with: sudo gdebi /path/to/packagename.deb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1756238/+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 1775442] [NEW] systemd 237-3ubuntu10 ADT test failure with linux-gcp 4.15.0-1009.9
Public bug reported: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/s/systemd/20180606_154452_00599@/log.gz ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-adt-failure ** Tags added: kernel-adt-failure -- 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/1775442 Title: systemd 237-3ubuntu10 ADT test failure with linux-gcp 4.15.0-1009.9 Status in systemd package in Ubuntu: New Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/s/systemd/20180606_154452_00599@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1775442/+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 1775441] [NEW] 18.04 crashed on startup, hanging at purple login screen handoff to normal screen
Public bug reported: Insanely, the boot before, and the boot after, were perfectly smooth and successful, and stayed on for hours. This single startup required a force restart after hanging on the purple that comes after typing password and hitting enter on login, and just before normal gnome desktop appears. I'm not sure it's lightdm, but I read that lightdm still runs the login screen, and was responsible for previous problems at this stage in the bootup process. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm (not installed) ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 6 12:50:56 2018 InstallationDate: Installed on 2018-04-26 (41 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1775441 Title: 18.04 crashed on startup, hanging at purple login screen handoff to normal screen Status in lightdm package in Ubuntu: New Bug description: Insanely, the boot before, and the boot after, were perfectly smooth and successful, and stayed on for hours. This single startup required a force restart after hanging on the purple that comes after typing password and hitting enter on login, and just before normal gnome desktop appears. I'm not sure it's lightdm, but I read that lightdm still runs the login screen, and was responsible for previous problems at this stage in the bootup process. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm (not installed) ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 6 12:50:56 2018 InstallationDate: Installed on 2018-04-26 (41 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1775441/+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 1583801] Re: No sound via headphones (headset) when Ubuntu boots with them plugged in
To anyone doing something about this bug, it could also be fixed by actually using the selection from the Select Audio Device dialogue and, you know, remembering it and using it. This would improve things for everyone much more than just making this singular Dell hardware problem go away. Nobody should have to use that dialogue every time they plug in the same device. Bad user experience, bad design. -- 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/1583801 Title: No sound via headphones (headset) when Ubuntu boots with them plugged in Status in PulseAudio: Confirmed Status in alsa-driver package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: The bug is twofold, first when computer boots if the headset (headphones with built-in mic, one audio jack) is plugged in, then there is no sound (via headphones or otherwise). If you plug headphones out and back in, then it usually works as expected. The second scenario is the same, except that plugging out and back in again doesn't help. In that case, I just restart the laptop, then plug them back in again and it works. In all cases, microphone works. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crunch 3248 F pulseaudio CurrentDesktop: Unity Date: Thu May 19 22:13:20 2016 InstallationDate: Installed on 2016-05-07 (12 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crunch 3248 F pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_Type: No sound at all Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1583801/+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 1774573] Re: package apport 2.20.7-0ubuntu3.7 failed to install/upgrade: subprocess new pre-removal script returned error exit status 127
** Tags added: pyclean-not-found -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1774573 Title: package apport 2.20.7-0ubuntu3.7 failed to install/upgrade: subprocess new pre-removal script returned error exit status 127 Status in apport package in Ubuntu: New Bug description: The computer prompted me an error when I start it today. I don't know what else happened. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: apport 2.20.7-0ubuntu3.7 ProcVersionSignature: Ubuntu 4.13.0-39.44-generic 4.13.16 Uname: Linux 4.13.0-39-generic x86_64 ApportLog: ApportVersion: 2.20.7-0ubuntu3.7 AptOrdering: python3-apport:amd64: Install apport:amd64: Install NULL: ConfigurePending Architecture: amd64 CrashReports: 600:0:119:103009:2018-06-01 00:27:18.217459917 -0400:2018-06-01 00:27:19.217459917 -0400:/var/crash/apport.0.crash Date: Fri Jun 1 00:27:19 2018 ErrorMessage: subprocess new pre-removal script returned error exit status 127 InstallationDate: Installed on 2018-04-03 (59 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: apport Title: package apport 2.20.7-0ubuntu3.7 failed to install/upgrade: subprocess new pre-removal script returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1774573/+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 1767982] Re: package libmount1:i386 2.31.1-0.4ubuntu3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configura
Does this actually have anything to do with util-linux? What makes dpkg give this error message? ** Also affects: dpkg (Ubuntu) Importance: Undecided Status: New ** Changed in: util-linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1767982 Title: package libmount1:i386 2.31.1-0.4ubuntu3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in dpkg package in Ubuntu: New Status in util-linux package in Ubuntu: Incomplete Bug description: Since my last update, i'm getting this error every time when i want to install something. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libmount1:i386 2.31.1-0.4ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 AptOrdering: NULL: ConfigurePending Architecture: amd64 Date: Mon Apr 30 11:29:35 2018 DpkgTerminalLog: dpkg: error processing package libmount1:i386 (--configure): package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-11-17 (163 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: i386 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-2 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.14-4 RelatedPackageVersions: dpkg 1.19.0.5ubuntu1 apt 1.6~beta1 SourcePackage: util-linux Title: package libmount1:i386 2.31.1-0.4ubuntu3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1767982/+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 1775441] Re: 18.04 crashed on startup, hanging at purple login screen handoff to normal screen
** Package changed: lightdm (Ubuntu) => gdm3 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1775441 Title: 18.04 crashed on startup, hanging at purple login screen handoff to normal screen Status in gdm3 package in Ubuntu: New Bug description: Insanely, the boot before, and the boot after, were perfectly smooth and successful, and stayed on for hours. This single startup required a force restart after hanging on the purple that comes after typing password and hitting enter on login, and just before normal gnome desktop appears. I'm not sure it's lightdm, but I read that lightdm still runs the login screen, and was responsible for previous problems at this stage in the bootup process. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm (not installed) ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 6 12:50:56 2018 InstallationDate: Installed on 2018-04-26 (41 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1775441/+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 1775447] [NEW] Mines counts bombs wrong on edge
Public bug reported: A square on the edge can count neighboring bombs incorrectly as shown in the image. ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Attachment added: "error example" https://bugs.launchpad.net/bugs/1775447/+attachment/5149441/+files/mines%20bug.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1775447 Title: Mines counts bombs wrong on edge Status in apport package in Ubuntu: New Bug description: A square on the edge can count neighboring bombs incorrectly as shown in the image. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1775447/+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 1763822] Re: package software-properties-common 0.96.24.28 failed to install/upgrade: subprocess new pre-removal script returned error exit status 127
** Tags added: pyclean-not-found -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1763822 Title: package software-properties-common 0.96.24.28 failed to install/upgrade: subprocess new pre-removal script returned error exit status 127 Status in software-properties package in Ubuntu: Incomplete Bug description: Package crash after log in ProblemType: Package DistroRelease: Ubuntu 18.04 Package: software-properties-common 0.96.24.28 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 Date: Fri Apr 13 17:34:14 2018 ErrorMessage: subprocess new pre-removal script returned error exit status 127 InstallationDate: Installed on 2017-04-13 (364 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-2 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 RelatedPackageVersions: dpkg 1.19.0.5ubuntu1 apt 1.6~beta1 SourcePackage: software-properties Title: package software-properties-common 0.96.24.28 failed to install/upgrade: subprocess new pre-removal script returned error exit status 127 UpgradeStatus: Upgraded to bionic on 2018-04-13 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1763822/+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 1770327] Re: package python3 3.5.1-3 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 127
** Tags added: pyclean-not-found -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1770327 Title: package python3 3.5.1-3 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 127 Status in python3-defaults package in Ubuntu: New Bug description: I couldn't access ubuntu desktop. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python3 3.5.1-3 ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-41-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Wed May 9 11:52:20 2018 DuplicateSignature: package:python3:3.5.1-3 Removing python3 (3.5.1-3) ... /var/lib/dpkg/info/python3.prerm: 5: /var/lib/dpkg/info/python3.prerm: py3clean: not found dpkg: error processing package python3 (--purge): subprocess installed pre-removal script returned error exit status 127 ErrorMessage: subprocess installed pre-removal script returned error exit status 127 InstallationDate: Installed on 2018-02-27 (71 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: python3-defaults Title: package python3 3.5.1-3 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1770327/+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 1763844] Re: package python3-apt 1.6.0~rc2ubuntu2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 127
** Tags added: pyclean-not-found -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1763844 Title: package python3-apt 1.6.0~rc2ubuntu2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 127 Status in python-apt package in Ubuntu: Incomplete Bug description: Problem occurred setting the displays arrangement ProblemType: Package DistroRelease: Ubuntu 18.04 Package: python3-apt 1.6.0~rc2ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 Date: Fri Apr 13 17:34:14 2018 ErrorMessage: subprocess new pre-removal script returned error exit status 127 InstallationDate: Installed on 2017-04-13 (364 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-2 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 RelatedPackageVersions: dpkg 1.19.0.5ubuntu1 apt 1.6~beta1 SourcePackage: python-apt Title: package python3-apt 1.6.0~rc2ubuntu2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 127 UpgradeStatus: Upgraded to bionic on 2018-04-13 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1763844/+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 1775452] [NEW] Nvidia problems
Public bug reported: I have installed the nvidia driver 390 but when I rollback to nouveau my kern.log e syslog flood with error until have space in my hard drive. My computer doesn't hibernate or sleep. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Jun 6 15:42:57 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.59, 4.15.0-20-generic, x86_64: installed nvidia, 390.59, 4.15.0-22-generic, x86_64: installed GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd HD Graphics 620 [144d:c784] Subsystem: Samsung Electronics Co Ltd GM108M [GeForce 920MX] [144d:c784] InstallationDate: Installed on 2018-05-05 (31 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 2232:1080 Silicon Motion Bus 001 Device 003: ID 0cf3:e500 Atheros Communications, Inc. Bus 001 Device 002: ID 045e:00e1 Microsoft Corp. Wireless Laser Mouse 6000 Reciever Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: SAMSUNG ELECTRONICS CO., LTD. 300E5M/300E5L ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-22-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash nouveau.runpm=0 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/15/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P06RED.019.171215.ZW dmi.board.asset.tag: No Asset Tag dmi.board.name: NP300E5M-XD1BR dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGL9046A07-C01-G001-S0001+10.0.15063 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP06RED.019.171215.ZW:bd12/15/2017:svnSAMSUNGELECTRONICSCO.,LTD.:pn300E5M/300E5L:pvrP06RED:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP300E5M-XD1BR:rvrSGL9046A07-C01-G001-S0001+10.0.15063:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.family: SAMSUNG ATIV dmi.product.name: 300E5M/300E5L dmi.product.version: P06RED dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1775452 Title: Nvidia problems Status in xorg package in Ubuntu: New Bug description: I have installed the nvidia driver 390 but when I rollback to nouveau my kern.log e syslog flood with error until have space in my hard drive. My computer doesn't hibernate or sleep. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Jun 6 15:42:57 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.59, 4.15.0-20-generic, x86_64: installed nvidia, 390.59, 4.15.0-22-generic, x86_64: installed GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd HD Graphics 620 [144d:c784] Subsystem: Samsung Electronics Co Ltd GM108M [GeForce 920MX] [144d:c784] InstallationDate: Installed on 2018-05-05 (31 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 2232:1080 Silicon Motion Bus 001 Device 003: ID 0cf3:e500 Atheros Communications, Inc. Bus 001 Device 002: ID 045e:00e1 Microsoft Corp. Wireless Laser Mouse 6000 Reciever Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[Touch-packages] [Bug 1774915] Re: Video freezes and stutters when using totem (audio continues fine)
I've checked iowait using iotop during lags and revealed no spikes or something like that. So it's not a performance problem at all. I believe gstreamer is just dropping frames due to some bugs. I had 17.10 installed and had no issue that time. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1774915 Title: Video freezes and stutters when using totem (audio continues fine) Status in gnome-shell package in Ubuntu: Incomplete Status in gstreamer1.0 package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: Advised to file a bug report after posting on "Call for testing: Video playback in 18.04". Running 18.04 LTS as fresh install (not upgraded from previous version - older version still installed in separate partition). Xorg session. System: HP Pavillion DV7 (lm726av) - Intel Core i7 2630 processor, integrated Intel video Playing any local video file (regardless of video format - flv, mp4, avi), the video will randomly lag in playback. Audio is not affected, it plays back correctly. Very occasional lags in browsers (Firefox and Chrome) on pages with a lot of active graphics (flash or HTML5). Browser lags significantly improved after installing synaptic driver for touchpad operation (I have no idea why this would affect video playback - I simply note that it happened). I can pick a random video on YouTube and watch it in Firefox or Chrome without lag (even full-screen). However, if I grab a local copy of the video (using, for instance, Clipgrab) and play it using Totem, I get lag. I was also advised to try using mpv - I still get lag in mpv, although not as pronounced. tracy@tracy-hp:~$ sudo apt-cache policy totem [sudo] password for tracy: totem: Installed: 3.26.0-0ubuntu6 Candidate: 3.26.0-0ubuntu6 Version table: *** 3.26.0-0ubuntu6 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status I was also asked to include output of lspci -k - shown below: tracy@tracy-hp:~$ lspci -k 00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family DRAM Controller 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port (rev 09) Kernel driver in use: pcieport Kernel modules: shpchp 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family Integrated Graphics Controller Kernel driver in use: i915 Kernel modules: i915 00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04) Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family MEI Controller Kernel driver in use: mei_me Kernel modules: mei_me 00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05) Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family USB Enhanced Host Controller Kernel driver in use: ehci-pci 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05) Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family High Definition Audio Controller Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5) Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (rev b5) Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 3 (rev b5) Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 (rev b5) Kernel driver in use: pcieport Kernel modules: shpchp 00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05) Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family USB Enhanced Host Controller Kernel driver in use: ehci-pci 00:1f.0 ISA bridge: Intel Corporation HM65 Express Chipset Family LPC Controller (rev 05) Subsystem: Hewlett-Packard Company HM65 Express Chipset Family LPC Controller Kernel driver in use: lpc_ich Kernel m
[Touch-packages] [Bug 1709603] Re: apt {upgrade, install, source} require an update call first
Just a comment...
'apt' indicates that its cli is unstable and should not be relied upon by
scripts.
So fixing this general problem in 'apt' (and not apt-get) means you fix it
possibly for humans who are typing things, but all non-human package
installations needlessly have to 'apt-get update'. :-(
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1709603
Title:
apt {upgrade,install, source} require an update call first
Status in apt package in Ubuntu:
Confirmed
Bug description:
I think that this should be tracked in its own separate bug tracking
my specific UX objection to the current status quo.
See
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1429285/comments/5,
subsequent discussion and
https://twitter.com/chr1sa/status/894048628284604416
We think that the updating of indexes should be an implementation
detail of "apt upgrade" and "apt install", rather than something
exposed to the user. If updating is judged be required (for example
the index is more than X old), then it should be done automatically
before the requested operation commences.
Here's one proposed implementation:
1) Fix bug 1429285 ("apt-get update --if-necessary").
2) Add an option to have "apt install" and "apt upgrade" (also "apt
full-upgrade", etc?) automatically and internally call the
implementation of "apt-get update --if-necessary" first.
3) Enable the option by default on Ubuntu.
This would change the behaviour of "apt", which AIUI is intended to be
the user focused CLI. It wouldn't change the behaviour of "apt-get",
which AIUI needs to retain behavioural backwards compatibility for
existing scripts.
Then we could promote "apt install" and "apt upgrade" as much simpler
commands to operate.
Note that Julian disagreed with this proposed behaviour change in
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1429285/comments/7.
I think that the very user-focused Ubuntu perspective should be to
focus on the common use case for "apt". Hence my (compromise)
suggestion that we implement this as an option upstream, and then
leave it to distros to choose the default behaviour for their users.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1709603/+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 1775442] Re: systemd 237-3ubuntu10 ADT test failure with linux-gcp 4.15.0-1009.9
** Changed in: systemd (Ubuntu) Status: New => Confirmed ** Changed in: systemd (Ubuntu) Assignee: (unassigned) => Dimitri John Ledkov (xnox) -- 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/1775442 Title: systemd 237-3ubuntu10 ADT test failure with linux-gcp 4.15.0-1009.9 Status in systemd package in Ubuntu: Confirmed Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/s/systemd/20180606_154452_00599@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1775442/+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 1773316] Re: /usr/bin/update-manager:ValueError:foreach_cb:packages_are_selected:is_selected:marked_install
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: python-apt (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1773316 Title: Object of different cache passed as argument to apt_pkg.DepCache method Status in python-apt package in Ubuntu: Confirmed Status in update-manager package in Ubuntu: Confirmed Status in python-apt source package in Bionic: Confirmed Status in update-manager source package in Bionic: Confirmed Status in python-apt source package in Cosmic: Confirmed Status in update-manager source package in Cosmic: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding update-manager. This problem was most recently seen with package version 1:18.04.11, the problem page at https://errors.ubuntu.com/problem/e6ff7b5c385c512b7933497ad895c8a19ed063b2 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1773316/+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 1773316] Re: /usr/bin/update-manager:ValueError:foreach_cb:packages_are_selected:is_selected:marked_install
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: update-manager (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1773316 Title: Object of different cache passed as argument to apt_pkg.DepCache method Status in python-apt package in Ubuntu: Confirmed Status in update-manager package in Ubuntu: Confirmed Status in python-apt source package in Bionic: Confirmed Status in update-manager source package in Bionic: Confirmed Status in python-apt source package in Cosmic: Confirmed Status in update-manager source package in Cosmic: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding update-manager. This problem was most recently seen with package version 1:18.04.11, the problem page at https://errors.ubuntu.com/problem/e6ff7b5c385c512b7933497ad895c8a19ed063b2 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1773316/+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 1773316] Re: Object of different cache passed as argument to apt_pkg.DepCache method
** Summary changed: - /usr/bin/update-manager:ValueError:foreach_cb:packages_are_selected:is_selected:marked_install + Object of different cache passed as argument to apt_pkg.DepCache method -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1773316 Title: Object of different cache passed as argument to apt_pkg.DepCache method Status in python-apt package in Ubuntu: Confirmed Status in update-manager package in Ubuntu: Confirmed Status in python-apt source package in Bionic: Confirmed Status in update-manager source package in Bionic: Confirmed Status in python-apt source package in Cosmic: Confirmed Status in update-manager source package in Cosmic: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding update-manager. This problem was most recently seen with package version 1:18.04.11, the problem page at https://errors.ubuntu.com/problem/e6ff7b5c385c512b7933497ad895c8a19ed063b2 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1773316/+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 1773316] Re: /usr/bin/update-manager:ValueError:foreach_cb:packages_are_selected:is_selected:marked_install
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: python-apt (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1773316 Title: Object of different cache passed as argument to apt_pkg.DepCache method Status in python-apt package in Ubuntu: Confirmed Status in update-manager package in Ubuntu: Confirmed Status in python-apt source package in Bionic: Confirmed Status in update-manager source package in Bionic: Confirmed Status in python-apt source package in Cosmic: Confirmed Status in update-manager source package in Cosmic: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding update-manager. This problem was most recently seen with package version 1:18.04.11, the problem page at https://errors.ubuntu.com/problem/e6ff7b5c385c512b7933497ad895c8a19ed063b2 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1773316/+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 1773316] Re: /usr/bin/update-manager:ValueError:foreach_cb:packages_are_selected:is_selected:marked_install
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: update-manager (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1773316 Title: Object of different cache passed as argument to apt_pkg.DepCache method Status in python-apt package in Ubuntu: Confirmed Status in update-manager package in Ubuntu: Confirmed Status in python-apt source package in Bionic: Confirmed Status in update-manager source package in Bionic: Confirmed Status in python-apt source package in Cosmic: Confirmed Status in update-manager source package in Cosmic: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding update-manager. This problem was most recently seen with package version 1:18.04.11, the problem page at https://errors.ubuntu.com/problem/e6ff7b5c385c512b7933497ad895c8a19ed063b2 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1773316/+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 1773316] Re: /usr/bin/update-manager:ValueError:foreach_cb:packages_are_selected:is_selected:marked_install
** Also affects: python-apt (Ubuntu) Importance: Undecided Status: New ** Also affects: python-apt (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: update-manager (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: python-apt (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: update-manager (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1773316 Title: Object of different cache passed as argument to apt_pkg.DepCache method Status in python-apt package in Ubuntu: Confirmed Status in update-manager package in Ubuntu: Confirmed Status in python-apt source package in Bionic: Confirmed Status in update-manager source package in Bionic: Confirmed Status in python-apt source package in Cosmic: Confirmed Status in update-manager source package in Cosmic: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding update-manager. This problem was most recently seen with package version 1:18.04.11, the problem page at https://errors.ubuntu.com/problem/e6ff7b5c385c512b7933497ad895c8a19ed063b2 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1773316/+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 1773316] Re: Object of different cache passed as argument to apt_pkg.DepCache method
** Description changed: + [Impact] + python-apt 1.6 raises an exception when objects of an old cache are passed to a apt_pkg.DepCache methods for a different cache. Prior to that, those would either segfault, succeed, or silently operate on a different object, as they use package/version ids, and e.g. two different packages in the old and new cache might have the same id. + + With 1.6.1, we introduce a remapping algorithm that remaps objects of + apt.Cache() when calling apt.Cache.open(), allowing old objects to be + used after reopening, as long as they exist in the new cache. If they + don't exist in the new cache, apt_pkg.CacheMismatchError will be raised + from the apt_pkg layer. + + [Test case] + import apt + c=apt.Cache() + p=c["apt"] + c.open() + p.mark_install() + + [Regression potential] + Could be remapping to wrong items which would cause us to install a wrong version, for example. Compared to pre-bionic, bionic is a regression already, though, and any regression caused here is less important than + what we have now. + + [Original bug report] The Ubuntu Error Tracker has been receiving reports about a problem regarding update-manager. This problem was most recently seen with package version 1:18.04.11, the problem page at https://errors.ubuntu.com/problem/e6ff7b5c385c512b7933497ad895c8a19ed063b2 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Changed in: update-manager (Ubuntu Bionic) Status: Confirmed => Triaged ** Changed in: update-manager (Ubuntu Bionic) Status: Triaged => Won't Fix ** Changed in: update-manager (Ubuntu Cosmic) Status: Confirmed => Won't Fix ** Changed in: python-apt (Ubuntu Cosmic) Status: Confirmed => Fix Committed ** Changed in: python-apt (Ubuntu Bionic) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1773316 Title: Object of different cache passed as argument to apt_pkg.DepCache method Status in python-apt package in Ubuntu: Fix Committed Status in update-manager package in Ubuntu: Confirmed Status in python-apt source package in Bionic: Triaged Status in update-manager source package in Bionic: Won't Fix Status in python-apt source package in Cosmic: Fix Committed Status in update-manager source package in Cosmic: Won't Fix Bug description: [Impact] python-apt 1.6 raises an exception when objects of an old cache are passed to a apt_pkg.DepCache methods for a different cache. Prior to that, those would either segfault, succeed, or silently operate on a different object, as they use package/version ids, and e.g. two different packages in the old and new cache might have the same id. With 1.6.1, we introduce a remapping algorithm that remaps objects of apt.Cache() when calling apt.Cache.open(), allowing old objects to be used after reopening, as long as they exist in the new cache. If they don't exist in the new cache, apt_pkg.CacheMismatchError will be raised from the apt_pkg layer. [Test case] import apt c=apt.Cache() p=c["apt"] c.open() p.mark_install() [Regression potential] Could be remapping to wrong items which would cause us to install a wrong version, for example. Compared to pre-bionic, bionic is a regression already, though, and any regression caused here is less important than what we have now. [Original bug report] The Ubuntu Error Tracker has been receiving reports about a problem regarding update-manager. This problem was most recently seen with package version 1:18.04.11, the problem page at https://errors.ubuntu.com/problem/e6ff7b5c385c512b7933497ad895c8a19ed063b2 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1773316/+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 1767875] Re: /usr/bin/update-manager:ValueError:restart_icon_renderer_data_func:pkg_requires_restart:__get_candidate
*** This bug is a duplicate of bug 1773316 *** https://bugs.launchpad.net/bugs/1773316 ** This bug has been marked a duplicate of bug 1773316 Object of different cache passed as argument to apt_pkg.DepCache method -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1767875 Title: /usr/bin/update- manager:ValueError:restart_icon_renderer_data_func:pkg_requires_restart:__get_candidate Status in apt package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding update-manager. This problem was most recently seen with package version 1:18.04.11, the problem page at https://errors.ubuntu.com/problem/a2ba8d3ab5e432b3c15f172ded6d473f4c00720a contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1767875/+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 1772859] Comment bridged from LTC Bugzilla
--- Comment From abhir...@in.ibm.com 2018-06-06 14:43 EDT--- Team, We understand Network Manager is good for desktop but not servers. But given the stability NetworkManager is bringing in and ease of use across different operating systems, i assume users are not restricted not to use NetworkManager for servers. The reason being we going with network manager as explained is to reuse the code for all distros. Note : Netplan is not present/installed in our ubuntu. So by default we are expecting network manager to work. root@57fb2571ae8a:~# ls -l /etc | grep netplan root@57fb2571ae8a:~# If we need to start using netplan, probably we have to re-write the code to configure yaml files which can be understood by netplan. So as a workaround, we would like to understand why network manager is failing to manage the devices? This is definitely to do with open issue, https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1638842 Let me know if more data is needed for analysis, 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/1772859 Title: Network Manager is not able to manage the devices on Ubuntu 18.04 Status in Ubuntu on IBM z Systems: Invalid Status in network-manager package in Ubuntu: Invalid Bug description: NetworkManager is not able to manage the devices on latest Ubuntu(18.04) ---uname output--- Linux (none) 4.15.0-12-generic #13-Ubuntu SMP Wed Mar 7 21:36:36 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = z14 s390 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. Install the latest Ubuntu(18.04) with Network Manager(1.10.4). 2. Configure a network device and login to the partition through ssh. 3. Now you can see the following output root@(none):~# nmcli d s DEVICE TYPE STATE CONNECTION eth0ethernet unmanaged -- eth1ethernet unmanaged -- lo loopback unmanaged -- Userspace tool common name: 1.10.6-2ubuntu1: amd64 arm64 armhf i386 ppc64el s390x The userspace tool has the following bit modes: 64-bit Userspace rpm: NetworkManager --version 1.10.4 Userspace tool obtained from project website: na Some more information about the issue: Network device has been configured manually after the image is up from Support Element(SE): - znetconf -a - cat /sys/bus/ccwgroup/drivers/qeth//if_name - ifconfig netmask 255.255.255.0 - route add default gw - SSH service has been configured This helped us to login to the Lpar. In Lpar - output of znetconf -c Device IDs TypeCard Type CHPID Drv. Name State - 0.0.1a80,0.0.1a81,0.0.1a82 1731/01 OSD_10GIG A8 qeth eth0 online 0.0.1810,0.0.1811,0.0.1812 1731/01 OSD_1000 D0 qeth eth1 online - output of nmcli c s root@(none):~# nmcli c s NAME UUID TYPE DEVICE - output of nmcli d s root@(none):~# nmcli d s DEVICE TYPE STATE CONNECTION eth0ethernet unmanaged -- eth1ethernet unmanaged -- lo loopback unmanaged -- * The above output shows that devices are not managed by nmcli After some investigation we found couple of suggestions like 1. Ubuntu(version <17.04): Creating an empty file(/etc/NetworkManager/conf.d/10-globally-managed-devices.conf) and restarting NM, solved the issue. 2. Ubuntu(version 17.10): Copying the said file(10-globally-managed-devices.conf) from /usr/lib to /etc/ and modifying the "unmanaged-devices" to none, resolved the issue. * link for reference: https://bugs.launchpad.net/ubuntu/+source /network-manager/+bug/1638842 For the latest version(18.04), none of the above solutions worked. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1772859/+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 1775457] Re: /usr/bin/pip3:ImportError:/usr/bin/pip3@9
doko tells me that this is due to people installing pip another way and pip10 doesn't include main. Perhaps we should suppress the crashes since there isn't anything we can do about it. ** Also affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags added: rls-cc-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1775457 Title: /usr/bin/pip3:ImportError:/usr/bin/pip3@9 Status in apport package in Ubuntu: New Status in python-pip package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding python-pip. This problem was most recently seen with package version 9.0.1-2.3~ubuntu1, the problem page at https://errors.ubuntu.com/problem/4e26eab10247fe3383fb8c84ca8a0d8eb21abc83 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1775457/+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 1756238] Re: gdebi-gtk broken in 18.04 error: unable to read filedescriptor flags
As far as I was concerned this bug was already fixed in:- 0.52.1-1ubuntu1 in the main repo, so I can't see any need for this in proposed now. But just to answer your question anyway, YES:- 0.52.2-1ubunti1-18.04.1 also fixes the issue (though now it would likely be more accurate to say it doesn't regress the earlier fix). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1756238 Title: gdebi-gtk broken in 18.04 error: unable to read filedescriptor flags Status in gdebi package in Ubuntu: Triaged Status in vte2.91 package in Ubuntu: Fix Released Status in vte2.91 source package in Bionic: Fix Committed Bug description: When using gdebi-gtk to install a .deb the install fails with the message:- dpkg: error: unable to read filedescriptor flags for : Bad file descriptor This only occurs via the gdebi-gtk GUI front end, packages install perfectly if done via the CLI with: sudo gdebi /path/to/packagename.deb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1756238/+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 1772859] Re: Network Manager is not able to manage the devices on Ubuntu 18.04
So your system is obviously not an 18.04 default installation from scratch - otherwise you would have netplan.io installed and this folder and file "/etc/netplan/01-netcfg.yaml" will exist on your system. There is no known way to me to install an 18.04 system without having netplan (initially) as default. Did you have removed netplan manually from that installation? Or is your 18.04 system and upgrade from an older Ubuntu release (like 16.04 or 17.10)? If it's an 18.04 installation from scratch please provide the installation logs. They are during the installation available at /var/log/* and after the installation still available at /var/log/installer/* -- 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/1772859 Title: Network Manager is not able to manage the devices on Ubuntu 18.04 Status in Ubuntu on IBM z Systems: Invalid Status in network-manager package in Ubuntu: Invalid Bug description: NetworkManager is not able to manage the devices on latest Ubuntu(18.04) ---uname output--- Linux (none) 4.15.0-12-generic #13-Ubuntu SMP Wed Mar 7 21:36:36 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = z14 s390 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. Install the latest Ubuntu(18.04) with Network Manager(1.10.4). 2. Configure a network device and login to the partition through ssh. 3. Now you can see the following output root@(none):~# nmcli d s DEVICE TYPE STATE CONNECTION eth0ethernet unmanaged -- eth1ethernet unmanaged -- lo loopback unmanaged -- Userspace tool common name: 1.10.6-2ubuntu1: amd64 arm64 armhf i386 ppc64el s390x The userspace tool has the following bit modes: 64-bit Userspace rpm: NetworkManager --version 1.10.4 Userspace tool obtained from project website: na Some more information about the issue: Network device has been configured manually after the image is up from Support Element(SE): - znetconf -a - cat /sys/bus/ccwgroup/drivers/qeth//if_name - ifconfig netmask 255.255.255.0 - route add default gw - SSH service has been configured This helped us to login to the Lpar. In Lpar - output of znetconf -c Device IDs TypeCard Type CHPID Drv. Name State - 0.0.1a80,0.0.1a81,0.0.1a82 1731/01 OSD_10GIG A8 qeth eth0 online 0.0.1810,0.0.1811,0.0.1812 1731/01 OSD_1000 D0 qeth eth1 online - output of nmcli c s root@(none):~# nmcli c s NAME UUID TYPE DEVICE - output of nmcli d s root@(none):~# nmcli d s DEVICE TYPE STATE CONNECTION eth0ethernet unmanaged -- eth1ethernet unmanaged -- lo loopback unmanaged -- * The above output shows that devices are not managed by nmcli After some investigation we found couple of suggestions like 1. Ubuntu(version <17.04): Creating an empty file(/etc/NetworkManager/conf.d/10-globally-managed-devices.conf) and restarting NM, solved the issue. 2. Ubuntu(version 17.10): Copying the said file(10-globally-managed-devices.conf) from /usr/lib to /etc/ and modifying the "unmanaged-devices" to none, resolved the issue. * link for reference: https://bugs.launchpad.net/ubuntu/+source /network-manager/+bug/1638842 For the latest version(18.04), none of the above solutions worked. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1772859/+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 1775459] [NEW] python2.7-minimal broken in bionic beaver
Public bug reported: My high level goal is to install clang in Ubuntu 18.04 LTS Bionic Beaver, however clang's dependency package python2.7-minimal appears to be broken, at least on my machine: $ sudo apt-get install clang Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: binfmt-support clang-6.0 lib32gcc1 lib32stdc++6 libc6-i386 libclang-common-6.0-dev libclang1-6.0 libffi-dev libgc1c2 libjsoncpp1 libllvm6.0 libncurses5 libncursesw5 libobjc-7-dev libobjc4 libomp-dev libomp5 libpython-stdlib libpython2.7-minimal libpython2.7-stdlib libtinfo-dev libtinfo5 llvm-6.0 llvm-6.0-dev llvm-6.0-runtime python python-minimal python2.7 python2.7-minimal Suggested packages: gnustep gnustep-devel clang-6.0-doc libomp-doc llvm-6.0-doc python-doc python-tk python2.7-doc The following NEW packages will be installed: binfmt-support clang clang-6.0 lib32gcc1 lib32stdc++6 libc6-i386 libclang-common-6.0-dev libclang1-6.0 libffi-dev libgc1c2 libjsoncpp1 libllvm6.0 libobjc-7-dev libobjc4 libomp-dev libomp5 libpython-stdlib libpython2.7-minimal libpython2.7-stdlib libtinfo-dev llvm-6.0 llvm-6.0-dev llvm-6.0-runtime python python-minimal python2.7 python2.7-minimal The following packages will be upgraded: libncurses5 libncursesw5 libtinfo5 3 upgraded, 27 newly installed, 0 to remove and 31 not upgraded. Need to get 70.3 MB of archives. After this operation, 384 MB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://archive.ubuntu.com/ubuntu bionic/main amd64 libpython2.7-minimal amd64 2.7.15~rc1-1 [334 kB] Get:2 http://archive.ubuntu.com/ubuntu bionic/main amd64 python2.7-minimal amd64 2.7.15~rc1-1 [1,292 kB] Get:3 http://archive.ubuntu.com/ubuntu bionic/main amd64 python-minimal amd64 2.7.15~rc1-1 [28.1 kB] Get:4 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libncurses5 amd64 6.1-1ubuntu1.18.04 [95.1 kB] Get:5 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libtinfo5 amd64 6.1-1ubuntu1.18.04 [80.3 kB] Get:6 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libncursesw5 amd64 6.1-1ubuntu1.18.04 [117 kB] Get:7 http://archive.ubuntu.com/ubuntu bionic/main amd64 libpython2.7-stdlib amd64 2.7.15~rc1-1 [1,910 kB] Get:8 http://archive.ubuntu.com/ubuntu bionic/main amd64 python2.7 amd64 2.7.15~rc1-1 [238 kB] Get:9 http://archive.ubuntu.com/ubuntu bionic/main amd64 libpython-stdlib amd64 2.7.15~rc1-1 [7,620 B] Get:10 http://archive.ubuntu.com/ubuntu bionic/main amd64 python amd64 2.7.15~rc1-1 [140 kB] Get:11 http://archive.ubuntu.com/ubuntu bionic/main amd64 binfmt-support amd64 2.1.8-2 [51.6 kB] Get:12 http://archive.ubuntu.com/ubuntu bionic/main amd64 libjsoncpp1 amd64 1.7.4-3 [73.6 kB] Get:13 http://archive.ubuntu.com/ubuntu bionic/main amd64 libllvm6.0 amd64 1:6.0-1ubuntu2 [14.5 MB] Get:14 http://archive.ubuntu.com/ubuntu bionic/main amd64 libgc1c2 amd64 1:7.4.2-8ubuntu1 [81.8 kB] Get:15 http://archive.ubuntu.com/ubuntu bionic/main amd64 libobjc4 amd64 8-20180414-1ubuntu2 [52.5 kB] Get:16 http://archive.ubuntu.com/ubuntu bionic/main amd64 libobjc-7-dev amd64 7.3.0-16ubuntu3 [206 kB] Get:17 http://archive.ubuntu.com/ubuntu bionic/main amd64 libc6-i386 amd64 2.27-3ubuntu1 [2,651 kB] Get:18 http://archive.ubuntu.com/ubuntu bionic/main amd64 lib32gcc1 amd64 1:8-20180414-1ubuntu2 [47.9 kB] Get:19 http://archive.ubuntu.com/ubuntu bionic/main amd64 lib32stdc++6 amd64 8-20180414-1ubuntu2 [414 kB] Get:20 http://archive.ubuntu.com/ubuntu bionic/universe amd64 libclang-common-6.0-dev amd64 1:6.0-1ubuntu2 [3,078 kB] Get:21 http://archive.ubuntu.com/ubuntu bionic/main amd64 libclang1-6.0 amd64 1:6.0-1ubuntu2 [7,067 kB] Get:22 http://archive.ubuntu.com/ubuntu bionic/universe amd64 clang-6.0 amd64 1:6.0-1ubuntu2 [9,292 kB] Get:23 http://archive.ubuntu.com/ubuntu bionic/universe amd64 clang amd64 1:6.0-41~exp4 [3,152 B] Get:24 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libtinfo-dev amd64 6.1-1ubuntu1.18.04 [81.3 kB] Get:25 http://archive.ubuntu.com/ubuntu bionic/main amd64 llvm-6.0-runtime amd64 1:6.0-1ubuntu2 [200 kB] Get:26 http://archive.ubuntu.com/ubuntu bionic/main amd64 llvm-6.0 amd64 1:6.0-1ubuntu2 [4,838 kB] Get:27 http://archive.ubuntu.com/ubuntu bionic/main amd64 libffi-dev amd64 3.2.1-8 [156 kB]
[Touch-packages] [Bug 1774915] Re: Video freezes and stutters when using totem (audio continues fine)
Also when I was on 17.10 beta, there was an update that broke totem (black screen instead of video). Problem appeared after the issue was fixed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1774915 Title: Video freezes and stutters when using totem (audio continues fine) Status in gnome-shell package in Ubuntu: Incomplete Status in gstreamer1.0 package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: Advised to file a bug report after posting on "Call for testing: Video playback in 18.04". Running 18.04 LTS as fresh install (not upgraded from previous version - older version still installed in separate partition). Xorg session. System: HP Pavillion DV7 (lm726av) - Intel Core i7 2630 processor, integrated Intel video Playing any local video file (regardless of video format - flv, mp4, avi), the video will randomly lag in playback. Audio is not affected, it plays back correctly. Very occasional lags in browsers (Firefox and Chrome) on pages with a lot of active graphics (flash or HTML5). Browser lags significantly improved after installing synaptic driver for touchpad operation (I have no idea why this would affect video playback - I simply note that it happened). I can pick a random video on YouTube and watch it in Firefox or Chrome without lag (even full-screen). However, if I grab a local copy of the video (using, for instance, Clipgrab) and play it using Totem, I get lag. I was also advised to try using mpv - I still get lag in mpv, although not as pronounced. tracy@tracy-hp:~$ sudo apt-cache policy totem [sudo] password for tracy: totem: Installed: 3.26.0-0ubuntu6 Candidate: 3.26.0-0ubuntu6 Version table: *** 3.26.0-0ubuntu6 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status I was also asked to include output of lspci -k - shown below: tracy@tracy-hp:~$ lspci -k 00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family DRAM Controller 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port (rev 09) Kernel driver in use: pcieport Kernel modules: shpchp 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family Integrated Graphics Controller Kernel driver in use: i915 Kernel modules: i915 00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04) Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family MEI Controller Kernel driver in use: mei_me Kernel modules: mei_me 00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05) Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family USB Enhanced Host Controller Kernel driver in use: ehci-pci 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05) Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family High Definition Audio Controller Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5) Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (rev b5) Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 3 (rev b5) Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 (rev b5) Kernel driver in use: pcieport Kernel modules: shpchp 00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05) Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family USB Enhanced Host Controller Kernel driver in use: ehci-pci 00:1f.0 ISA bridge: Intel Corporation HM65 Express Chipset Family LPC Controller (rev 05) Subsystem: Hewlett-Packard Company HM65 Express Chipset Family LPC Controller Kernel driver in use: lpc_ich Kernel modules: lpc_ich 00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family 6 por
[Touch-packages] [Bug 1775280] Re: The second user cannot start their session, login screen has low resolution
** Tags added: login -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1775280 Title: The second user cannot start their session, login screen has low resolution Status in lightdm package in Ubuntu: New Bug description: The first user can start their session successfully with autologin. When I try to switch to the second user, the login screen has very low resolution and it cannot start the secondary user session. I tried to change the value of the autologin user, than the other user session start well, but the original user session failed. That's why I think this is not a user related error, always the second user session fail, does not matter which one is the first user. The only differences between the default settings that passwordless login switch on the pam config and use nvidia-340 driver instead of noveau. The strange thing that this lightdm config works well with noveau driver, the problem with noveau driver that the video playing freeze the computer. Previously lightdm and nvidia driver work well on 16.04. This is a clean install not an upgrade from 16.04. I think the problem somewhere virtual X terminals handled by ligthDm. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Tue Jun 5 23:07:11 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-05-27 (9 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.pam.d.lightdm: 2018-05-27T21:23:23.664631 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1775280/+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 1772859] Re: Network Manager is not able to manage the devices on Ubuntu 18.04
"We understand Network Manager is good for desktop but not servers." I would not phrase it this away. On Ubuntu, Desktop defaults to NetworkManager and Server defaults to netplan&networkd. Previously we defaulted to NetworkManager & ifupdown. "But given the stability NetworkManager is bringing in and ease of use across different operating systems, i assume users are not restricted not to use NetworkManager for servers." I would significantly challenge those statements. NetworkManager is extremely flakey, and consistently fails to reliably bring complex network configurations up, as exercised by our stress testing. It also is far from easy to use. Wrt. users restrictions, Ubuntu tries to guide users to an obviously correct, easy, default and obvious ways of doing things. However, we do indeed allow users to break their systems and keep all the broken pieces. "The reason being we going with network manager as explained is to reuse the code for all distros." I don't believe that's the right thing to do, as that does not validate how end customers will use respective distros on z hardware. All customers will most likely use whatever each distro installer sets up, and will not tear that out and go out of their way to use networkmanager in a lowest common denominator configuration (e.g. Ubuntu's network-manager is patched, and is at a different version level than other distros) "Note : Netplan is not present/installed in our ubuntu. So by default we are expecting network manager to work." After installing a system, if you want netplan to be out of the way - and have the ability to use straight-up netwokrd/NM/etc, I'd rather recommend removing /etc/netplan/* configs and rebooting, without uninstalling netplan.io package. This would guarantee that interfaces are undeclared as managed-on-unmanaged by anything. -- 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/1772859 Title: Network Manager is not able to manage the devices on Ubuntu 18.04 Status in Ubuntu on IBM z Systems: Invalid Status in network-manager package in Ubuntu: Invalid Bug description: NetworkManager is not able to manage the devices on latest Ubuntu(18.04) ---uname output--- Linux (none) 4.15.0-12-generic #13-Ubuntu SMP Wed Mar 7 21:36:36 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = z14 s390 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. Install the latest Ubuntu(18.04) with Network Manager(1.10.4). 2. Configure a network device and login to the partition through ssh. 3. Now you can see the following output root@(none):~# nmcli d s DEVICE TYPE STATE CONNECTION eth0ethernet unmanaged -- eth1ethernet unmanaged -- lo loopback unmanaged -- Userspace tool common name: 1.10.6-2ubuntu1: amd64 arm64 armhf i386 ppc64el s390x The userspace tool has the following bit modes: 64-bit Userspace rpm: NetworkManager --version 1.10.4 Userspace tool obtained from project website: na Some more information about the issue: Network device has been configured manually after the image is up from Support Element(SE): - znetconf -a - cat /sys/bus/ccwgroup/drivers/qeth//if_name - ifconfig netmask 255.255.255.0 - route add default gw - SSH service has been configured This helped us to login to the Lpar. In Lpar - output of znetconf -c Device IDs TypeCard Type CHPID Drv. Name State - 0.0.1a80,0.0.1a81,0.0.1a82 1731/01 OSD_10GIG A8 qeth eth0 online 0.0.1810,0.0.1811,0.0.1812 1731/01 OSD_1000 D0 qeth eth1 online - output of nmcli c s root@(none):~# nmcli c s NAME UUID TYPE DEVICE - output of nmcli d s root@(none):~# nmcli d s DEVICE TYPE STATE CONNECTION eth0ethernet unmanaged -- eth1ethernet unmanaged -- lo loopback unmanaged -- * The above output shows that devices are not managed by nmcli After some investigation we found couple of suggestions like 1. Ubuntu(version <17.04): Creating an empty file(/etc/NetworkManager/conf.d/10-globally-managed-devices.conf) and restarting NM, solved the issue. 2. Ubuntu(version 17.10): Copying the said file(10-globally-managed-devices.conf) from /usr/lib to /etc/ and modifying the "unmanaged-devices" to none, resolved the issue. * link for reference: https://bugs.launchpad.net/ubuntu/+source /network-manager/+bug/1638842 For the latest version(18.04), none of the above solutions worked.
[Touch-packages] [Bug 1772859] Re: Network Manager is not able to manage the devices on Ubuntu 18.04
(given architecture-all tag; replace "z hardware" with "any server hardware" - above comments are architecture independent across all Ubuntu products) -- 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/1772859 Title: Network Manager is not able to manage the devices on Ubuntu 18.04 Status in Ubuntu on IBM z Systems: Invalid Status in network-manager package in Ubuntu: Invalid Bug description: NetworkManager is not able to manage the devices on latest Ubuntu(18.04) ---uname output--- Linux (none) 4.15.0-12-generic #13-Ubuntu SMP Wed Mar 7 21:36:36 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = z14 s390 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. Install the latest Ubuntu(18.04) with Network Manager(1.10.4). 2. Configure a network device and login to the partition through ssh. 3. Now you can see the following output root@(none):~# nmcli d s DEVICE TYPE STATE CONNECTION eth0ethernet unmanaged -- eth1ethernet unmanaged -- lo loopback unmanaged -- Userspace tool common name: 1.10.6-2ubuntu1: amd64 arm64 armhf i386 ppc64el s390x The userspace tool has the following bit modes: 64-bit Userspace rpm: NetworkManager --version 1.10.4 Userspace tool obtained from project website: na Some more information about the issue: Network device has been configured manually after the image is up from Support Element(SE): - znetconf -a - cat /sys/bus/ccwgroup/drivers/qeth//if_name - ifconfig netmask 255.255.255.0 - route add default gw - SSH service has been configured This helped us to login to the Lpar. In Lpar - output of znetconf -c Device IDs TypeCard Type CHPID Drv. Name State - 0.0.1a80,0.0.1a81,0.0.1a82 1731/01 OSD_10GIG A8 qeth eth0 online 0.0.1810,0.0.1811,0.0.1812 1731/01 OSD_1000 D0 qeth eth1 online - output of nmcli c s root@(none):~# nmcli c s NAME UUID TYPE DEVICE - output of nmcli d s root@(none):~# nmcli d s DEVICE TYPE STATE CONNECTION eth0ethernet unmanaged -- eth1ethernet unmanaged -- lo loopback unmanaged -- * The above output shows that devices are not managed by nmcli After some investigation we found couple of suggestions like 1. Ubuntu(version <17.04): Creating an empty file(/etc/NetworkManager/conf.d/10-globally-managed-devices.conf) and restarting NM, solved the issue. 2. Ubuntu(version 17.10): Copying the said file(10-globally-managed-devices.conf) from /usr/lib to /etc/ and modifying the "unmanaged-devices" to none, resolved the issue. * link for reference: https://bugs.launchpad.net/ubuntu/+source /network-manager/+bug/1638842 For the latest version(18.04), none of the above solutions worked. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1772859/+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 1775470] [NEW] totem video is unusable, video plays green screen and froze
Public bug reported: I play any video an the system become unresponsive and the playback is green. I have attached a picture from totem playing big buck bunny totally freeze and green francisco@progrest:~$ vainfo libva info: VA-API version 1.1.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_1 libva info: va_openDriver() returns 0 vainfo: VA-API version: 1.1 (libva 2.1.0) vainfo: Driver version: Intel i965 driver for Intel(R) Ironlake Mobile - 2.1.0 vainfo: Supported profile and entrypoints VAProfileMPEG2Simple: VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264Main : VAEntrypointVLD VAProfileH264High : VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc francisco@progrest:~$ lspci -k 00:00.0 Host bridge: Intel Corporation Core Processor DRAM Controller (rev 12) Subsystem: Acer Incorporated [ALI] Core Processor DRAM Controller 00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 12) Subsystem: Acer Incorporated [ALI] Core Processor Integrated Graphics Controller Kernel driver in use: i915 Kernel modules: i915 00:16.0 Communication controller: Intel Corporation 5 Series/3400 Series Chipset HECI Controller (rev 06) Subsystem: Acer Incorporated [ALI] 5 Series/3400 Series Chipset HECI Controller Kernel driver in use: mei_me Kernel modules: mei_me 00:1a.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05) Subsystem: Acer Incorporated [ALI] 5 Series/3400 Series Chipset USB2 Enhanced Host Controller Kernel driver in use: ehci-pci 00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 05) Subsystem: Acer Incorporated [ALI] 5 Series/3400 Series Chipset High Definition Audio Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 (rev 05) Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.1 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 2 (rev 05) Kernel driver in use: pcieport Kernel modules: shpchp 00:1d.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05) Subsystem: Acer Incorporated [ALI] 5 Series/3400 Series Chipset USB2 Enhanced Host Controller Kernel driver in use: ehci-pci 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev a5) 00:1f.0 ISA bridge: Intel Corporation HM55 Chipset LPC Interface Controller (rev 05) Subsystem: Acer Incorporated [ALI] HM55 Chipset LPC Interface Controller Kernel driver in use: lpc_ich Kernel modules: lpc_ich 00:1f.2 SATA controller: Intel Corporation 5 Series/3400 Series Chipset 4 port SATA AHCI Controller (rev 05) Subsystem: Acer Incorporated [ALI] 5 Series/3400 Series Chipset 4 port SATA AHCI Controller Kernel driver in use: ahci Kernel modules: ahci 00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller (rev 05) Subsystem: Acer Incorporated [ALI] 5 Series/3400 Series Chipset SMBus Controller Kernel modules: i2c_i801 00:1f.6 Signal processing controller: Intel Corporation 5 Series/3400 Series Chipset Thermal Subsystem (rev 05) Subsystem: Acer Incorporated [ALI] 5 Series/3400 Series Chipset Thermal Subsystem Kernel driver in use: intel ips Kernel modules: intel_ips 01:00.0 Ethernet controller: Broadcom Limited NetLink BCM57780 Gigabit Ethernet PCIe (rev 01) Subsystem: Acer Incorporated [ALI] NetLink BCM57780 Gigabit Ethernet PCIe Kernel driver in use: tg3 Kernel modules: tg3 02:00.0 Network controller: Qualcomm Atheros AR928X Wireless Network Adapter (PCI-Express) (rev 01) Subsystem: Lite-On Communications Inc AR928X Wireless Network Adapter (PCI-Express) Kernel driver in use: ath9k Kernel modules: ath9k ff:00.0 Host bridge: Intel Corporation Core Processor QuickPath Architecture Generic Non-core Registers (rev 02) Subsystem: Acer Incorporated [ALI] Core Processor QuickPath Architecture Generic Non-core Registers ff:00.1 Host bridge: Intel Corporation Core Processor QuickPath Architecture System Address Decoder (rev 02) Subsystem: Acer Incorporated [ALI] Core Processor QuickPath Architecture System Address Decoder ff:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev 02) Subsystem: Acer Incorporated [ALI] Core Processor QPI Link 0 ff:02.1 Host bridge: Intel Corporation 1st Gener
